qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [Applied PATCH] Split TLB addend and target_phys_addr_t


From: Alexander Graf
Subject: Re: [Qemu-devel] [Applied PATCH] Split TLB addend and target_phys_addr_t
Date: Wed, 07 Apr 2010 18:40:38 +0200
User-agent: Thunderbird 2.0.0.23 (X11/20090817)

malc wrote:
> On Wed, 7 Apr 2010, Alexander Graf wrote:
>
>   
>> Alexander Graf wrote:
>>     
>>> [    2.148288] registered taskstats version 1
>>> [    2.148288]   Magic number: 6:65:32
>>> [    2.148288] rtc_cmos 00:01: setting system clock to 2010-04-07
>>> 15:01:35 UTC (1270652495)
>>>
>>> *** sits here in hlt ***
>>>
>>> Almost looks like a timekeeping issue, no? And yes, I tried to revert
>>> 4a9590f32e5692114aaae4ca10da89dac633e164 - no change.
>>>   
>>>       
>> The guest is still alive and reacts to SysRq though. This is sysrq-l
>> (active process) and sysrq-q (timer info) output:
>>
>> [  246.635200] SysRq : Show backtrace of all active CPUs
>> [  246.638500] CPU0:
>> [  246.638500] CPU 0:
>> [  246.638500] Modules linked in:
>> [  246.638500] Pid: 0, comm: swapper Not tainted 2.6.31.5-0.1-default #1
>> Bochs
>> [  246.638500] RIP: 0010:[<ffffffff81039766>]  [<ffffffff81039766>]
>> native_safe_halt+0x6/0x10
>> [  246.638500] RSP: 0018:ffffffff818bfe78  EFLAGS: 00000286
>> [  246.638500] RAX: 0000000000000000 RBX: ffffffff818bfe78 RCX:
>> 0000000000000000
>> [  246.638500] RDX: 0000000000000000 RSI: 0000000000000000 RDI:
>> ffffffff81adb2c8
>> [  246.638500] RBP: ffffffff8100d00e R08: 0000000000000000 R09:
>> 0000000000000001
>> [  246.638500] R10: 0000000000000001 R11: 00000000fffedd21 R12:
>> 008a90db4ea6a915
>> [  246.638500] R13: ffffffff818bfde8 R14: ffffffff81014b7d R15:
>> ffffffff818bfdd8
>> [  246.638500] FS:  0000000000000000(0000) GS:ffff880001ca3000(0000)
>> knlGS:0000000000000000
>> [  246.638500] CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
>> [  246.638500] CR2: 0000000000000000 CR3: 0000000001001000 CR4:
>> 00000000000006f0
>> [  246.638500] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
>> 0000000000000000
>> [  246.638500] DR3: 0000000000000000 DR6: 0000000000000000 DR7:
>> 0000000000000000
>> [  246.638500] Call Trace:
>> [  246.638500] Inexact backtrace:
>> [  246.638500]
>> [  246.638500]  [<ffffffff810168c2>] ? default_idle+0x62/0x120
>> [  246.638500]  [<ffffffff8100b44c>] ? cpu_idle+0xcc/0x120
>> [  246.638500]  [<ffffffff8153da49>] ? rest_init+0x79/0xa0
>> [  246.638500]  [<ffffffff819e4766>] ? start_kernel+0x3db/0x3f8
>> [  246.638500]  [<ffffffff819e370d>] ? x86_64_start_reservations+0x134/0x14f
>> [  246.638500]  [<ffffffff819e3883>] ? x86_64_start_kernel+0x15b/0x17e
>> [  265.202817] SysRq : Show clockevent devices & pending hrtimers (no
>> others)
>> [  265.206127] Timer List Version: v0.4
>> [  265.206127] HRTIMER_MAX_CLOCK_BASES: 2
>> [  265.206127] now at 265207060508 nsecs
>> [  265.206127]
>> [  265.206127] cpu: 0
>> [  265.206127]  clock 0:
>> [  265.206127]   .base:       ffff880001cb1f68
>> [  265.206127]   .index:      0
>> [  265.206127]   .resolution: 1 nsecs
>> [  265.206127]   .get_time:   ktime_get_real
>> [  265.206127]   .offset:     1270652799620743573 nsecs
>> [  265.206127] active timers:
>> [  265.206127]  clock 1:
>> [  265.206127]   .base:       ffff880001cb1fa8
>> [  265.206127]   .index:      1
>> [  265.206127]   .resolution: 1 nsecs
>> [  265.206127]   .get_time:   ktime_get
>> [  265.206127]   .offset:     0 nsecs
>> [  265.206127] active timers:
>> [  265.206127]  #0: <ffff880001cb2040>, tick_sched_timer, S:01,
>> <(null)>, /-1
>> [  265.206127]  # expires at 9223372036854775807-9223372036854775807
>> nsecs [in 9223371771647715299 to 9223371771647715299 nsecs]
>> [  265.206127]   .expires_next   : 9223372036854775807 nsecs
>> [  265.206127]   .hres_active    : 1
>> [  265.206127]   .nr_events      : 82
>> [  265.206127]   .nohz_mode      : 2
>> [  265.206127]   .idle_tick      : 0 nsecs
>> [  265.206127]   .tick_stopped   : 0
>> [  265.206127]   .idle_jiffies   : 0
>> [  265.206127]   .idle_calls     : 7
>> [  265.206127]   .idle_sleeps    : 0
>> [  265.206127]   .idle_entrytime : 246738695612 nsecs
>> [  265.206127]   .idle_waketime  : 0 nsecs
>> [  265.206127]   .idle_exittime  : 0 nsecs
>> [  265.206127]   .idle_sleeptime : 250185168614 nsecs
>> [  265.206127]   .last_jiffies   : 4294892832
>> [  265.206127]   .next_jiffies   : 4294892833
>> [  265.206127]   .idle_expires   : 0 nsecs
>> [  265.206127] jiffies: 4294892832
>> [  265.206127]
>> [  265.206127]
>> [  265.206127] Tick Device: mode:     1
>> [  265.206127] Broadcast device
>> [  265.206127] Clock Event Device: hpet
>> [  265.206127]  max_delta_ns:   21474836500
>> [  265.206127]  min_delta_ns:   5000
>> [  265.206127]  mult:           429496729
>> [  265.206127]  shift:          32
>> [  265.206127]  mode:           3
>> [  265.206127]  next_event:     9223372036854775807 nsecs
>> [  265.206127]  set_next_event: hpet_legacy_next_event
>> [  265.206127]  set_mode:       hpet_legacy_set_mode
>> [  265.206127]  event_handler:  tick_handle_oneshot_broadcast
>> [  265.206127] tick_broadcast_mask: 00000000
>> [  265.206127] tick_broadcast_oneshot_mask: 00000000
>> [  265.206127]
>> [  265.206127]
>> [  265.206127] Tick Device: mode:     1
>> [  265.206127] Per CPU device: 0
>> [  265.206127] Clock Event Device: lapic
>> [  265.206127]  max_delta_ns:   134229000
>> [  265.206127]  min_delta_ns:   1000
>> [  265.206127]  mult:           268412881
>> [  265.206127]  shift:          32
>> [  265.206127]  mode:           3
>> [  265.206127]  next_event:     9223372036854775807 nsecs
>> [  265.206127]  set_next_event: lapic_next_event
>> [  265.206127]  set_mode:       lapic_timer_setup
>> [  265.206127]  event_handler:  hrtimer_interrupt
>> [  265.206127]
>>
>>     
>
> Any chance of bisecting this?
>   


I'm not sure it worked before and I also don't really have time for it
right now either :-(. Sorry.


Alex





reply via email to

[Prev in Thread] Current Thread [Next in Thread]