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

Re: [Xen-devel] Re: 2.6.39 dom0 xen power management test



Monday, May 23, 2011, 1:17:07 PM, you wrote:

> On Sat, 21 May 2011, Sander Eikelenboom wrote:
>> Hi Konrad,
>> 
>> First tests looked good, but tonight after approx. 2 hours after boot the 
>> machine crashed.
>> Since my previous setup ran perfectly stable for 55 days, i didn't have a 
>> serial console attached.
>> I shot a photo of what was left onscreen (attached), will attach a serial 
>> console later to get it all.
>> 

> does this patch help?

Nope it doesn't, right after boot i'm getting:

May 23 15:01:02 serveerstertje kernel: [  361.274781] INFO: task xm:6252 
blocked for more than 120 seconds.
May 23 15:01:02 serveerstertje kernel: [  361.275784] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 23 15:01:02 serveerstertje kernel: [  361.277026] xm              D 
ffff88002fdd7400     0  6252   6242 0x00000000
May 23 15:01:02 serveerstertje kernel: [  361.278260]  ffff8800247c3d58 
0000000000000286 000000000000bdb1 0000000000000000
May 23 15:01:02 serveerstertje kernel: [  361.278701]  ffff88002837d580 
0000000000013400 ffff8800247c3fd8 ffff8800247c2010
May 23 15:01:02 serveerstertje kernel: [  361.278701]  ffff8800247c3fd8 
0000000000013400 ffffffff81fe7020 ffff88002837d580
May 23 15:01:02 serveerstertje kernel: [  361.278701] Call Trace:
May 23 15:01:02 serveerstertje kernel: [  361.278701]  [<ffffffff81047323>] ? 
xen_write_msr_safe+0xa3/0xe0
May 23 15:01:02 serveerstertje kernel: [  361.278701]  [<ffffffff8104edaa>] ? 
__switch_to+0x18a/0x3d0
May 23 15:01:02 serveerstertje kernel: [  361.278701]  [<ffffffff8108fdab>] ? 
finish_task_switch+0x5b/0xe0
May 23 15:01:02 serveerstertje kernel: [  361.278701]  [<ffffffff81a8860d>] ? 
schedule+0x44d/0xae0
May 23 15:01:02 serveerstertje kernel: [  361.278701]  [<ffffffff8104c21d>] ? 
xen_force_evtchn_callback+0xd/0x10
May 23 15:01:02 serveerstertje kernel: [  361.278701]  [<ffffffff8104c9d2>] ? 
check_events+0x12/0x20
May 23 15:01:02 serveerstertje kernel: [  361.278701]  [<ffffffff81a89445>] 
schedule_timeout+0x1e5/0x2b0
May 23 15:01:02 serveerstertje kernel: [  361.278701]  [<ffffffff81a8ae30>] ? 
_raw_spin_unlock_irqrestore+0x30/0x70
May 23 15:01:02 serveerstertje kernel: [  361.278701]  [<ffffffff8108f685>] ? 
try_to_wake_up+0xc5/0x420
May 23 15:01:02 serveerstertje kernel: [  361.278701]  [<ffffffff81a8905e>] 
wait_for_common+0xde/0x190
May 23 15:01:02 serveerstertje kernel: [  361.278701]  [<ffffffff8108f9e0>] ? 
try_to_wake_up+0x420/0x420
May 23 15:01:02 serveerstertje kernel: [  361.278701]  [<ffffffff81a891ed>] 
wait_for_completion+0x1d/0x20
May 23 15:01:02 serveerstertje kernel: [  361.278701]  [<ffffffff810b31c0>] 
flush_work+0x30/0x40
May 23 15:01:02 serveerstertje kernel: [  361.278701]  [<ffffffff810b1b60>] ? 
do_work_for_cpu+0x30/0x30
May 23 15:01:02 serveerstertje kernel: [  361.278701]  [<ffffffff810b4803>] 
schedule_on_each_cpu+0xc3/0x100
May 23 15:01:02 serveerstertje kernel: [  361.278701]  [<ffffffff811258d5>] 
lru_add_drain_all+0x15/0x20
May 23 15:01:02 serveerstertje kernel: [  361.278701]  [<ffffffff81141015>] 
sys_mlock+0x45/0x130
May 23 15:01:02 serveerstertje kernel: [  361.278701]  [<ffffffff81a8bcc2>] 
system_call_fastpath+0x16/0x1b
May 23 15:01:02 serveerstertje kernel: [  361.278701] INFO: task xm:6278 
blocked for more than 120 seconds.
May 23 15:01:02 serveerstertje kernel: [  361.278701] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 23 15:01:02 serveerstertje kernel: [  361.278701] xm              D 
ffff88002fdd7400     0  6278   6268 0x00000000
May 23 15:01:02 serveerstertje kernel: [  361.278701]  ffff8800258b1d58 
0000000000000286 000000000000b8df 0000000000000000
May 23 15:01:02 serveerstertje kernel: [  361.278701]  ffff88002837f200 
0000000000013400 ffff8800258b1fd8 ffff8800258b0010
May 23 15:01:02 serveerstertje kernel: [  361.309209]  ffff8800258b1fd8 
0000000000013400 ffffffff81fe7020 ffff88002837f200
May 23 15:01:02 serveerstertje kernel: [  361.309209] Call Trace:
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff81047323>] ? 
xen_write_msr_safe+0xa3/0xe0
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff8104edaa>] ? 
__switch_to+0x18a/0x3d0
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff8108fdab>] ? 
finish_task_switch+0x5b/0xe0
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff81a8860d>] ? 
schedule+0x44d/0xae0
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff8104c21d>] ? 
xen_force_evtchn_callback+0xd/0x10
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff8104c9d2>] ? 
check_events+0x12/0x20
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff81a89445>] 
schedule_timeout+0x1e5/0x2b0
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff81a8ae30>] ? 
_raw_spin_unlock_irqrestore+0x30/0x70
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff8108f685>] ? 
try_to_wake_up+0xc5/0x420
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff81a8905e>] 
wait_for_common+0xde/0x190
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff8108f9e0>] ? 
try_to_wake_up+0x420/0x420
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff81a891ed>] 
wait_for_completion+0x1d/0x20
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff810b31c0>] 
flush_work+0x30/0x40
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff810b1b60>] ? 
do_work_for_cpu+0x30/0x30
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff810b4803>] 
schedule_on_each_cpu+0xc3/0x100
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff811258d5>] 
lru_add_drain_all+0x15/0x20
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff81141015>] 
sys_mlock+0x45/0x130
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff81a8bcc2>] 
system_call_fastpath+0x16/0x1b
May 23 15:01:02 serveerstertje kernel: [  361.309209] INFO: task xentop:6287 
blocked for more than 120 seconds.
May 23 15:01:02 serveerstertje kernel: [  361.309209] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 23 15:01:02 serveerstertje kernel: [  361.309209] xentop          D 
ffff88002fdd7400     0  6287      1 0x00000004
May 23 15:01:02 serveerstertje kernel: [  361.309209]  ffff880025d1dd58 
0000000000000282 0000000000000000 0000000000000000
May 23 15:01:02 serveerstertje kernel: [  361.309209]  ffff880029d65580 
0000000000013400 ffff880025d1dfd8 ffff880025d1c010
May 23 15:01:02 serveerstertje kernel: [  361.309209]  ffff880025d1dfd8 
0000000000013400 ffffffff81fe7020 ffff880029d65580
May 23 15:01:02 serveerstertje kernel: [  361.309209] Call Trace:
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff81047323>] ? 
xen_write_msr_safe+0xa3/0xe0
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff8104edaa>] ? 
__switch_to+0x18a/0x3d0
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff8108fdab>] ? 
finish_task_switch+0x5b/0xe0
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff81a8860d>] ? 
schedule+0x44d/0xae0
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff8104c21d>] ? 
xen_force_evtchn_callback+0xd/0x10
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff8104c9d2>] ? 
check_events+0x12/0x20
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff81a89445>] 
schedule_timeout+0x1e5/0x2b0
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff81a8ae30>] ? 
_raw_spin_unlock_irqrestore+0x30/0x70
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff8108f685>] ? 
try_to_wake_up+0xc5/0x420
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff81a8905e>] 
wait_for_common+0xde/0x190
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff8108f9e0>] ? 
try_to_wake_up+0x420/0x420
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff81a891ed>] 
wait_for_completion+0x1d/0x20
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff810b31c0>] 
flush_work+0x30/0x40
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff810b1b60>] ? 
do_work_for_cpu+0x30/0x30
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff810b4803>] 
schedule_on_each_cpu+0xc3/0x100
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff811258d5>] 
lru_add_drain_all+0x15/0x20
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff81141015>] 
sys_mlock+0x45/0x130
May 23 15:01:02 serveerstertje kernel: [  361.309209]  [<ffffffff81a8bcc2>] 
system_call_fastpath+0x16/0x1b
















> diff --git a/drivers/xen/events.c b/drivers/xen/events.c
> index 7f676f8..9249ed7 100644
> --- a/drivers/xen/events.c
> +++ b/drivers/xen/events.c
> @@ -1644,7 +1644,7 @@ static struct irq_chip xen_percpu_chip __read_mostly = {
>         .irq_mask               = evtchn_noop,
>         .irq_unmask             = evtchn_noop,
>  
> -       .irq_ack                = ack_dynirq,
> +       .irq_eoi                = ack_dynirq,
>  };
>  
>  int xen_set_callback_via(uint64_t via)




-- 
Best regards,
 Sander                            mailto:linux@xxxxxxxxxxxxxx


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.