[Xen-users] Re: DomU crashes after live migration

[ml ml <mliebherr99@xxxxxxxxxxxxxx>]

okay, it may be a bad idea to not sync the swap disk with drbd.  My
migration from ServerA to ServerB now works great, but when i try to
migrate back from ServerB to ServerA i get this:


WARNING: at arch/x86/kernel/microcode_core.c:453 mc_sysdev_resume+0x28/0x52()
Pid: 6, comm: migration/0 Tainted: G        W   2.6.36 #1
Call Trace:
 [<ffffffff8103a5c4>] ? warn_slowpath_common+0x73/0x87
 [<ffffffff8106e901>] ? cpu_stopper_thread+0x131/0x168
 [<ffffffff81026461>] ? mc_sysdev_resume+0x28/0x52
 [<ffffffff812678d4>] ? __sysdev_resume+0x68/0xb5
 [<ffffffff8126797d>] ? sysdev_resume+0x5c/0x97
 [<ffffffff811fb165>] ? xen_suspend+0xb8/0xbe
 [<ffffffff8138d56e>] ? _raw_spin_lock_irq+0x7/0x1c
 [<ffffffff8106e9ab>] ? stop_machine_cpu_stop+0x73/0xa9
 [<ffffffff8106e938>] ? stop_machine_cpu_stop+0x0/0xa9
 [<ffffffff8106e8ad>] ? cpu_stopper_thread+0xdd/0x168
 [<ffffffff8138bd01>] ? schedule+0x64e/0x6f4
 [<ffffffff8106e7d0>] ? cpu_stopper_thread+0x0/0x168
 [<ffffffff8104f5fa>] ? kthread+0x7a/0x82
 [<ffffffff8100a7a4>] ? kernel_thread_helper+0x4/0x10
 [<ffffffff81009ba3>] ? int_ret_from_sys_call+0x7/0x1b
 [<ffffffff8138d95d>] ? retint_restore_args+0x5/0x6
 [<ffffffff8100a7a0>] ? kernel_thread_helper+0x0/0x10
---[ end trace 6d450e935ee1897f ]---
PM: early resume of devices complete after 0.001 msecs
PM: resume of devices complete after 0.001 msecs
Setting capacity to 20971520
Setting capacity to 2097152
Setting capacity to 20971520

Any idea?! :-)

Cheers,
Mario


On Wed, Oct 27, 2010 at 11:49 AM, ml ml <mliebherr99@xxxxxxxxxxxxxx> wrote:
> Hello List,
>
> my Debian Lenny DomU sometimes crashes after a live migration. Here is
> what i get on the console:
>
> WARNING: at arch/x86/kernel/microcode_core.c:453 mc_sysdev_resume+0x28/0x52()
> Pid: 4, comm: migration/0 Not tainted 2.6.35.4 #5
> Call Trace:
>  [<ffffffff81039fec>] ? warn_slowpath_common+0x73/0x87
>  [<ffffffff81068701>] ? cpu_stopper_thread+0x13d/0x16e
>  [<ffffffff810244a9>] ? mc_sysdev_resume+0x28/0x52
>  [<ffffffff8126596c>] ? __sysdev_resume+0x68/0xb5
>  [<ffffffff81265a15>] ? sysdev_resume+0x5c/0x97
>  [<ffffffff811fc99e>] ? xen_suspend+0xb8/0xbe
>  [<ffffffff810687a5>] ? stop_machine_cpu_stop+0x73/0xa9
>  [<ffffffff81068732>] ? stop_machine_cpu_stop+0x0/0xa9
>  [<ffffffff810686a7>] ? cpu_stopper_thread+0xe3/0x16e
>  [<ffffffff8138d0d7>] ? schedule+0x4f4/0x5be
>  [<ffffffff810685c4>] ? cpu_stopper_thread+0x0/0x16e
>  [<ffffffff8104cd69>] ? kthread+0x75/0x7d
>  [<ffffffff810097a4>] ? kernel_thread_helper+0x4/0x10
>  [<ffffffff81008ba3>] ? int_ret_from_sys_call+0x7/0x1b
>  [<ffffffff8138ee9d>] ? retint_restore_args+0x5/0x6
>  [<ffffffff810097a0>] ? kernel_thread_helper+0x0/0x10
> ---[ end trace f89d7f3ec5f33611 ]---
> PM: early resume of devices complete after 0.001 msecs
> PM: resume of devices complete after 0.001 msecs
>
>
> My Dom0 is Debian Squeeze with a 2.6.32.24-pvops kernel.
>
> Any idea?
>
> Thanks,
> Mario
>

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