From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: BUG: soft lockup - CPU#1 stuck for 61s! [udevd:4865] Date: Thu, 02 Sep 2010 17:26:22 -0700 Message-ID: <4C8040AE.7060902@goop.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: James Harper Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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: > [] ? xen_force_evtchn_callback+0x9/0xa > [] ? check_events+0x12/0x20 > [] ? xen_irq_enable_direct_end+0x0/0x7 > [] ? do_page_fault+0x9e/0x27b > [] ? page_fault+0x25/0x30 > [] ? __put_user_4+0x1d/0x30 > [] ? schedule_tail+0x92/0x96 > [] ? 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