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] BUG: soft lockup - CPU#1 stuck for 61s! [udevd:4865]

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] BUG: soft lockup - CPU#1 stuck for 61s! [udevd:4865]
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Thu, 02 Sep 2010 17:26:22 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 02 Sep 2010 17:26:59 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D01A92A28@trantor>
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: <AEC6C66638C05B468B556EA548C1A77D01A92A28@trantor>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100806 Fedora/3.1.2-1.fc13 Lightning/1.0b2pre Thunderbird/3.1.2
 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 I've since upgraded to
> 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 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

There have been some fixes relating to long-standing interrupt migration
bugs, but they're after 69a73fa.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>