[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] BUG: soft lockup - CPU#0 stuck for 61s!

  • To: xen-devel@xxxxxxxxxxxxx
  • From: "Andres Lagar-Cavilla" <andres@xxxxxxxxxxxxxxxx>
  • Date: Thu, 29 Mar 2012 08:43:23 -0700
  • Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, ian.campbell@xxxxxxxxxx, jingsu@xxxxxxxxxxxxxx, konrad.wilk@xxxxxxxxxx
  • Delivery-date: Thu, 29 Mar 2012 15:43:37 +0000
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=lagarcavilla.org; h=message-id :date:subject:from:to:cc:reply-to:mime-version:content-type: content-transfer-encoding; q=dns; s=lagarcavilla.org; b=HbD+EiTG qYYTh3smAgV0K/fQhR/gJQKaiMHGaixxVTV3X8Ct2jQuTbK5XGyim9HXdElRnMDI MDL04jzcmOJm2xL8siTNvfy1KxbbQJDU0Ic90m8JOioRSykazHgQEwJfNaxvyxsX ykoyVWLN3o0niD2RKgnBlYgBX4T7PZ3KYhE=
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>


I came across the subject line on a 96GB server with over 85 VMs running.
Completely frozen and unresponsive, qemu-dm processes hung on event
channels. I'm using the XenServer 6.0 dom0 kernel on top of the
xen-unstable tip hypervisor.

I believe you solved the issue backporting some event channel patches to
the 2.6.32 kernel, as described in this thread

I am missing a bit of context in order to retrieve the patches and apply
them to my setup. What trees are involved here? I'm looking in particular
for "multiple fixes to PIRQ event channel handling" and friends, but I
don't have commit identifiers, nor a tree URL (neither I am too sure what
changesets from which upstream tree do the backports aggregate).

Any help appreciated. Thanks

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.