From: Jeremy Fitzhardinge <jeremy@goop.org>
To: James Harper <james.harper@bendigoit.com.au>
Cc: xen-devel@lists.xensource.com
Subject: Re: BUG: soft lockup - CPU#1 stuck for 61s! [udevd:4865]
Date: Thu, 02 Sep 2010 17:26:22 -0700 [thread overview]
Message-ID: <4C8040AE.7060902@goop.org> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D01A92A28@trantor>
On 09/02/2010 05:20 PM, James Harper wrote:
> I've had "BUG: soft lockup - CPU#1 stuck for 61s! [udevd:4865]" happen
> twice now and the server fairly quickly (over the course of 5-10
> minutes) becomes unusable after that happens. The call trace appears to
> be:
>
> Call Trace:
> [<ffffffff8100e8e9>] ? xen_force_evtchn_callback+0x9/0xa
> [<ffffffff8100ef72>] ? check_events+0x12/0x20
> [<ffffffff8100ef19>] ? xen_irq_enable_direct_end+0x0/0x7
> [<ffffffff8102fcc1>] ? do_page_fault+0x9e/0x27b
> [<ffffffff812b39a5>] ? page_fault+0x25/0x30
> [<ffffffff8116f28d>] ? __put_user_4+0x1d/0x30
> [<ffffffff81045265>] ? schedule_tail+0x92/0x96
> [<ffffffff81011983>] ? ret_from_fork+0x13/0x80
>
> That was under 2.6.32.17-g69a73fa. I've since upgraded to
> 2.6.32.18-ge6b9b2c but the changelogs don't show anything obviously
> related to the crash (but as usual there are a lot of them so maybe I've
> missed something?)
>
> Is this a known problem under 2.6.32.17-g69a73fa that has since been
> fixed?
Hard to know; nothing springs to mind right now. What else is going on
at the time? What's the full softlockup message? Is there any more
context?
There have been some fixes relating to long-standing interrupt migration
bugs, but they're after 69a73fa.
J
next prev parent reply other threads:[~2010-09-03 0:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 0:20 BUG: soft lockup - CPU#1 stuck for 61s! [udevd:4865] James Harper
2010-09-03 0:26 ` Jeremy Fitzhardinge [this message]
2010-09-03 0:35 ` James Harper
2010-09-05 23:44 ` James Harper
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=4C8040AE.7060902@goop.org \
--to=jeremy@goop.org \
--cc=james.harper@bendigoit.com.au \
--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.