Comment 9 for bug 929941
Revision history for this message
| Stefan Bader (smb) wrote Re: Kernel deadlock in scheduler on m2.{2,4}xlarge EC2 instance | #9 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
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 84eb950db13ca40
x86, ticketlock: Clean up types and accessors
for breaking and
commit 7a7546b377bdaa2
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.