Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751534AbWEUMLJ (ORCPT ); Sun, 21 May 2006 08:11:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751536AbWEUMLI (ORCPT ); Sun, 21 May 2006 08:11:08 -0400 Received: from ogre.sisk.pl ([217.79.144.158]:32161 "EHLO ogre.sisk.pl") by vger.kernel.org with ESMTP id S1751534AbWEUMLH (ORCPT ); Sun, 21 May 2006 08:11:07 -0400 From: "Rafael J. Wysocki" To: Andrew Morton Subject: Re: 2.6.17-rc4-mm2 (hard lockup after resume from disk on AMD64) Date: Sun, 21 May 2006 14:07:32 +0200 User-Agent: KMail/1.9.1 Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net References: <20060520054103.46a6edb5.akpm@osdl.org> <200605202322.40214.rjw@sisk.pl> <20060520143017.43a87c3a.akpm@osdl.org> In-Reply-To: <20060520143017.43a87c3a.akpm@osdl.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605211407.33124.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3673 Lines: 64 On Saturday 20 May 2006 23:30, Andrew Morton wrote: > "Rafael J. Wysocki" wrote: > > > > On Saturday 20 May 2006 14:41, Andrew Morton wrote: > > > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.17-rc4/2.6.17-rc4-mm2/ > > > > My box (Asus L5D, x86_64 kernel) locks up hard after the resume from suspend > > to disk. This happens right after the console has been restored and only if > > all modules are loaded before suspend (eg. it doesn't lock up when booted with > > init=/bin/bash). Also it's caught by the softlockup watchdog which produces > > traces similar to the appended one. > > > > Greetings, > > Rafael > > > > > > BUG: soft lockup detected on CPU#0! > > > > Call Trace: {softlockup_tick+193} > > {run_local_timers+19} {update_process_times+87} > > {main_timer_handler+548} {timer_interrupt+21} > > {handle_IRQ_event+51} {__do_IRQ+162} > > {do_IRQ+65} {ret_from_intr+0} > > {urb_destroy+0} {usb_hcd_poll_rh_status+250} > > {:ohci_hcd:ohci_irq+194} {usb_hcd_irq+50} > > {handle_IRQ_event+51} {__do_IRQ+162} > > {do_IRQ+65} {ret_from_intr+0} > > {handle_IRQ_event+36} {__do_IRQ+162} > > {do_IRQ+65} {ret_from_intr+0} > > {handle_IRQ_event+36} {__do_IRQ+162} > > {do_IRQ+65} {ret_from_intr+0} > > {urb_destroy+0} {hcd_submit_urb+2072} > > {_spin_unlock_irqrestore+29} {usb_free_urb+21} > > {usb_hcd_giveback_urb+315} {_spin_unlock_irqrestore+29} > > {usb_submit_urb+859} {usb_start_wait_urb+122} > > {dbg_redzone1+29} {cache_alloc_debugcheck_after+532} > > {dbg_redzone1+29} {usb_control_msg+240} > > {set_port_feature+68} {hub_port_reset+57} > > {hub_port_init+129} {hub_thread+2241} > > {autoremove_wake_function+0} {hub_thread+0} > > {kthread+217} {_spin_unlock_irq+20} > > {schedule_tail+73} {child_rip+8} > > {kthread+0} {child_rip+0} > > BUG: soft lockup detected on CPU#0! > > What a revolting backtrace. There were some x86_64 precise-backtrace > patches floating around on the list this week. They seem to reappear and get squashed by Andi on a regular basis. ;-) > Still, it would appear that USB has become confused. If you have the time > to do a bisection search, I'd start in on gregkh-usb-*.patch. Obviously it's this one: gregkh-usb-usb-ohci-avoids-root-hub-timer-polling.patch [Well, looks like it hasn't been tested properly before posting ... :-(] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/