Joerg Stephan
2011-Apr-15 07:37 UTC
[Xen-devel] Re: kernel BUG at arch/x86/xen/mmu.c:1860!
Hey guys, i just wanne report that our debian squeeze xen machines are also influenced by this bug, and we tried the workaround with the debug option by building our own linux-image-2.6.32-5-xen-amd64_2.6.32-31_amd64.deb but this isnt a workaround really, we tested it on an 40 vmachines dom0 and it just dont work, of course the lvm works but the machine is slow as hell and runs into several kernel errors within a few hours [46566.052925] BUG: soft lockup - CPU#0 stuck for 61s! [qemu-dm:6292] in this case xentop shows an 500% CPU usage by the dom0, we experience an 85%st value. So, i think this should be fixed soon, so what is the status of the issue? Best whishes Joerg _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2011-Apr-15 08:54 UTC
Re: [Xen-devel] Re: kernel BUG at arch/x86/xen/mmu.c:1860!
On Fri, Apr 15, 2011 at 09:37:28AM +0200, Joerg Stephan wrote:> Hey guys, > > i just wanne report that our debian squeeze xen machines are also > influenced by this bug, and we tried the workaround with the debug option > by building our own > > linux-image-2.6.32-5-xen-amd64_2.6.32-31_amd64.deb > > but this isnt a workaround really, we tested it on an 40 vmachines dom0 > and it just dont work, of course the lvm works but the machine is slow as > hell and runs into several kernel errors within a few hours > > [46566.052925] BUG: soft lockup - CPU#0 stuck for 61s! [qemu-dm:6292] > > in this case xentop shows an 500% CPU usage by the dom0, we experience an > 85%st value. > > So, i think this should be fixed soon, so what is the status of the issue? >Hello, Fix for this bug has been merged to Jeremy''s xen.git xen/stable-2.6.32.x branch. See: http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=ae333e97552c81ab10395ad1ffc6d6daaadb144a in: http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=xen/stable-2.6.32.x So the upstream xen/stable-2.6.32.x shouldn''t be affected of this issue anymore.. Can you verify xen/stable-2.6.32.x works OK for you? -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel