From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Re: Bug#638172: BUG: soft lockup - CPU#0 stuck for 61s! [qemu-dm:3205] Date: Wed, 24 Aug 2011 16:24:00 -0400 Message-ID: <20110824202400.GA27448@dumpdata.com> References: <1313577856.13030.17.camel@scarafaggio> <1314003611.5010.400.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1314003611.5010.400.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Campbell Cc: 638172@bugs.debian.org, Ben Hutchings , xen-devel , Giuseppe Sacco List-Id: xen-devel@lists.xenproject.org On Mon, Aug 22, 2011 at 10:00:11AM +0100, Ian Campbell wrote: > @xen-devel: > > Does this look familiar to anyone, this is (I expect, hopefully Giuseppe > will confirm) from Debian Squeeze which has a Xen 4.0.x with a PVops > dom0 kernel based on xen.git from last summer (e73f4955a821) with more > recent upstream longterm kernels (up to and including 2.6.32.41) merged > in. While it does seem to have the switch from level to edge triggered > interrupt the Debian kernel doesn't appear to have the switch to fasteoi > for pirqs (0672fb44a111 plus a few followups) -- could that be related > to this? (I'm not sure if that was a cleanup or a fix) It was a fix. We had some interrupts getting wedged - but I don't recall the stack exactly. But there are some follows - like e5ac0bda96c495321dbad9b57a4b1a93a5a72e7f 7e186bdd0098b34c69fb8067c67340ae610ea499 > > Might the tsc unstable message be relevant? Hm, not sure. I keep on getting those on my guests but life seems to go on. The interesting about the stack trace is that it looks similiar to: http://groups.google.com/group/linux.kernel/browse_thread/thread/39a397566cafc979 which has some fixes https://patchwork.kernel.org/patch/1091772/ but they may not help.