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

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


  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
  • Date: Fri, 3 Sep 2010 10:20:56 +1000
  • Delivery-date: Thu, 02 Sep 2010 17:21:40 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: ActK/eBjh8+rxEEES5+b9YEl7QuJ3g==
  • Thread-topic: BUG: soft lockup - CPU#1 stuck for 61s! [udevd:4865]

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?

Thanks

James


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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