Hmmm... Now it doesn't crash. But I lose network access and I get a stack trace
[7744382.224271] eth0: no IPv6 routers present [7744715.716789] PM: suspend of devices complete after 0.119 msecs [7744715.716794] suspending xenstore... [7744715.716825] PM: late suspend of devices complete after 0.026 msecs [7746693.008996] trying to map vcpu_info 0 at ffff8800034ab020, mfn 18aa756, offset 32 [7746693.009004] cpu 0 using vcpu_info at ffff8800034ab020 [7746693.009359] PM: early resume of devices complete after 0.034 msecs [7746693.016403] PM: resume of devices complete after 5.629 msecs [7746827.319483] INFO: task xenwatch:11 blocked for more than 120 seconds. [7746827.319498] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [7746827.319508] xenwatch D ffff8800034b5f00 0 11 2 0x00000000 [7746827.319516] ffff88001fd9bbf0 0000000000000246 0000000000015f00 0000000000015f00 [7746827.319524] ffff88001fda03d0 ffff88001fd9bfd8 0000000000015f00 ffff88001fda0000 [7746827.319531] 0000000000015f00 ffff88001fd9bfd8 0000000000015f00 ffff88001fda03d0 [7746827.319539] Call Trace: [7746827.319551] [<ffffffff81559aed>] schedule_timeout+0x22d/0x300 [7746827.319559] [<ffffffff81062549>] ? __enqueue_rt_entity+0x129/0x240 [7746827.319565] [<ffffffff81558c66>] wait_for_common+0xd6/0x180 [7746827.319577] [<ffffffff8105deb0>] ? default_wake_function+0x0/0x20 [7746827.319583] [<ffffffff81558dcd>] wait_for_completion+0x1d/0x20 [7746827.319589] [<ffffffff81085e1b>] kthread_stop+0x4b/0xd0 [7746827.319595] [<ffffffff8108914f>] ? hrtimer_force_reprogram+0x7f/0x90 [7746827.319600] [<ffffffff81081aae>] cleanup_workqueue_thread+0x3e/0x80 [7746827.319605] [<ffffffff81081c93>] destroy_workqueue+0x93/0xe0 [7746827.319612] [<ffffffff810b7d44>] stop_machine_destroy+0x34/0x50 [7746827.319619] [<ffffffff8132431f>] do_suspend+0xaf/0x120 [7746827.319623] [<ffffffff81324499>] shutdown_handler+0x109/0x160 [7746827.319628] [<ffffffff81325812>] xenwatch_thread+0xc2/0x190 [7746827.319634] [<ffffffff81086140>] ? autoremove_wake_function+0x0/0x40 [7746827.319639] [<ffffffff81325750>] ? xenwatch_thread+0x0/0x190 [7746827.319644] [<ffffffff81085dc6>] kthread+0x96/0xa0 [7746827.319650] [<ffffffff810141aa>] child_rip+0xa/0x20 [7746827.319658] [<ffffffff81013391>] ? int_ret_from_sys_call+0x7/0x1b [7746827.319663] [<ffffffff81013b1d>] ? retint_restore_args+0x5/0x6 [7746827.319668] [<ffffffff810141a0>] ? child_rip+0x0/0x20 Linux x 2.6.32-37-server #81-Ubuntu SMP Fri Dec 2 20:49:12 UTC 2011 x86_64 GNU/Linux @ XenServer 5.6 SP2 Gonna test on XS 6.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/681083 Title: Ubuntu Crashes/Freeze on XenMotion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/681083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
