This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: kernel BUG at arch/x86/xen/mmu.c:1860!

To: Joerg Stephan <ml@xxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: kernel BUG at arch/x86/xen/mmu.c:1860!
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Fri, 15 Apr 2011 11:54:22 +0300
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 15 Apr 2011 01:55:21 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.BSF.2.00.1104150931340.9169@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <alpine.BSF.2.00.1104150931340.9169@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
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?


Fix for this bug has been merged to Jeremy's xen.git xen/stable-2.6.32.x branch.


So the upstream xen/stable-2.6.32.x shouldn't be affected of this issue 
Can you verify xen/stable-2.6.32.x works OK for you?

-- Pasi

Xen-devel mailing list