From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <ijc@hellion.org.uk>
Cc: 638172@bugs.debian.org, Ben Hutchings <ben@decadent.org.uk>,
xen-devel <xen-devel@lists.xensource.com>,
Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>
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 [thread overview]
Message-ID: <20110824202400.GA27448@dumpdata.com> (raw)
In-Reply-To: <1314003611.5010.400.camel@zakaz.uk.xensource.com>
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.
next prev parent reply other threads:[~2011-08-24 20:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1313577856.13030.17.camel@scarafaggio>
2011-08-22 9:00 ` Bug#638172: BUG: soft lockup - CPU#0 stuck for 61s! [qemu-dm:3205] Ian Campbell
2011-08-22 9:49 ` Giuseppe Sacco
2011-08-24 20:24 ` Konrad Rzeszutek Wilk [this message]
2011-08-24 21:24 ` Ian Campbell
2011-08-25 6:52 ` Bug#638172: [Xen-devel] " Giuseppe Sacco
2011-08-25 6:56 ` Ian Campbell
2011-08-25 7:23 ` Bug#638172: [Xen-devel] " Giuseppe Sacco
2011-08-26 7:25 ` Bug#638172: " Ian Campbell
2011-08-26 8:28 ` Giuseppe Sacco
2011-08-26 8:31 ` Ian Campbell
2011-10-18 10:54 ` Ian Campbell
2011-10-18 11:00 ` Giuseppe Sacco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110824202400.GA27448@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=638172@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=giuseppe@eppesuigoccas.homedns.org \
--cc=ijc@hellion.org.uk \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.