The most interesting part of the dmesg for me is to give a rough idea about what Xen version it has. And usually it is helping to make sure whether this correlates on all the cases where the hang happens. It looks like some interaction problem but the only code I can look at is the guest. Recently there has been a fix to upstream and 3.2.y about a spinlock problem but it blamed a commit in 3.2 to have caused that regression. And the ec2 kernels don't have that patch and I guess the dom0 kernel neither. Just for reference those would have been:
commit 84eb950db13ca40a0572ce9957e14723500943d6 x86, ticketlock: Clean up types and accessors for breaking and commit 7a7546b377bdaa25ac77f33d9433c59f259b9688 x86: xen: size struct xen_spinlock to always fit in arch_spinlock_t But maybe we should make sure it is not something similar. I'll check the ec2 kernel code and post the numbers here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/929941 Title: Kernel deadlock in scheduler on m2.{2,4}xlarge EC2 instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/929941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
