WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Issue with 2.6.37 DomU kernel

On Fri, 2011-02-04 at 19:54 +0000, Anirban Sinha wrote:
> >The patch below works for me in so much as it
> > doesn't make anything worse, but I wasn't seeing the issue to start
> > with. Does it work for you?
> 
> yes, it does , thanks.

Unfortunately testing a bit further against origin/master I get:

[  262.720078] BUG: sleeping function called from invalid context at 
/local/scratch/ianc/devel/kernels/linux-2.6/kernel/mutex.c:278
[  262.720078] in_atomic(): 0, irqs_disabled(): 1, pid: 6, name: migration/0
[  262.720078] INFO: lockdep is turned off.
[  262.720078] irq event stamp: 12
[  262.720078] hardirqs last  enabled at (11): [<c12f7d02>] 
_raw_spin_unlock_irq+0x22/0x40
[  262.720078] hardirqs last disabled at (12): [<c12f769d>] 
_raw_spin_lock_irq+0x1d/0x60
[  262.720078] softirqs last  enabled at (0): [<c103c2c6>] 
copy_process+0x266/0xf80
[  262.720078] softirqs last disabled at (0): [<  (null)>]   (null)
[  262.720078] Pid: 6, comm: migration/0 Tainted: G        W   
2.6.38-rc3-x86_32p-xenU-00239-g7cb27bf #412
[  262.720078] Call Trace:
[  262.720078]  [<c1035b5c>] ? __might_sleep+0x11c/0x130
[  262.720078]  [<c12f64ee>] ? mutex_lock_nested+0x1e/0x380
[  262.720078]  [<c107bb21>] ? synchronize_irq+0x31/0xa0
[  262.720078]  [<c107afcc>] ? disable_irq_nosync+0x4c/0x70
[  262.720078]  [<c118d806>] ? rebind_evtchn_irq+0x26/0xc0
[  262.720078]  [<c11af1dd>] ? xen_console_resume+0x1d/0x40
[  262.720078]  [<c118ebfa>] ? xen_suspend+0xaa/0x100
[  262.720078]  [<c10070e4>] ? check_events+0x8/0xc
[  262.720078]  [<c1079efa>] ? stop_machine_cpu_stop+0x9a/0xf0
[  262.720078]  [<c1079d8e>] ? cpu_stopper_thread+0x8e/0x160
[  262.720078]  [<c12f4dc1>] ? schedule+0x301/0x820
[  262.720078]  [<c1079e60>] ? stop_machine_cpu_stop+0x0/0xf0
[  262.720078]  [<c10068da>] ? xen_force_evtchn_callback+0x1a/0x30
[  262.720078]  [<c10070c0>] ? xen_restore_fl_direct+0x0/0x17
[  262.720078]  [<c10068da>] ? xen_force_evtchn_callback+0x1a/0x30
[  262.720078]  [<c10070e4>] ? check_events+0x8/0xc
[  262.720078]  [<c10070db>] ? xen_restore_fl_direct_end+0x0/0x1
[  262.720078]  [<c12f7d7e>] ? _raw_spin_unlock_irqrestore+0x5e/0x70
[  262.720078]  [<c1030299>] ? complete+0x49/0x60
[  262.720078]  [<c1079d00>] ? cpu_stopper_thread+0x0/0x160
[  262.720078]  [<c10577e4>] ? kthread+0x74/0x80
[  262.720078]  [<c1057770>] ? kthread+0x0/0x80
[  262.720078]  [<c100aafa>] ? kernel_thread_helper+0x6/0x10

so back to the drawing board...

>  Although the domain boot process just hangs
> half way through. It could be a different issue. Need to investigate.

OK.


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

<Prev in Thread] Current Thread [Next in Thread>