Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932376AbWETVae (ORCPT ); Sat, 20 May 2006 17:30:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932344AbWETVae (ORCPT ); Sat, 20 May 2006 17:30:34 -0400 Received: from smtp.osdl.org ([65.172.181.4]:2537 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S932376AbWETVad (ORCPT ); Sat, 20 May 2006 17:30:33 -0400 Date: Sat, 20 May 2006 14:30:17 -0700 From: Andrew Morton To: "Rafael J. Wysocki" Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net Subject: Re: 2.6.17-rc4-mm2 (hard lockup after resume from disk on AMD64) Message-Id: <20060520143017.43a87c3a.akpm@osdl.org> In-Reply-To: <200605202322.40214.rjw@sisk.pl> References: <20060520054103.46a6edb5.akpm@osdl.org> <200605202322.40214.rjw@sisk.pl> X-Mailer: Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3298 Lines: 59 "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. 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. - 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/