Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751247AbVLLUyY (ORCPT ); Mon, 12 Dec 2005 15:54:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751255AbVLLUyY (ORCPT ); Mon, 12 Dec 2005 15:54:24 -0500 Received: from anf141.internetdsl.tpnet.pl ([83.17.87.141]:15579 "EHLO anf141.internetdsl.tpnet.pl") by vger.kernel.org with ESMTP id S1751247AbVLLUyX (ORCPT ); Mon, 12 Dec 2005 15:54:23 -0500 From: "Rafael J. Wysocki" To: Andrew Morton Subject: Re: 2.6.15-rc5-mm2: ehci_hcd crashes on load sometimes Date: Mon, 12 Dec 2005 21:55:43 +0100 User-Agent: KMail/1.9 Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net References: <20051211041308.7bb19454.akpm@osdl.org> <200512122053.39970.rjw@sisk.pl> <20051212122914.1bd36f32.akpm@osdl.org> In-Reply-To: <20051212122914.1bd36f32.akpm@osdl.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512122155.43632.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2060 Lines: 55 On Monday, 12 December 2005 21:29, Andrew Morton wrote: > "Rafael J. Wysocki" wrote: > > > > On Sunday, 11 December 2005 21:38, Andrew Morton wrote: > > > "Rafael J. Wysocki" wrote: > > > > > > > > The ehci_hcd driver causes problems like this: > > > > > > > > ehci_hcd 0000:00:02.2: EHCI Host Controller > > > > ehci_hcd 0000:00:02.2: debug port 1 > > > > ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 3 > > > > ehci_hcd 0000:00:02.2: irq 5, io mem 0xfebfdc00 > > > > usb 2-2: Product: USB Receiver > > > > usb 2-2: Manufacturer: Logitech > > > > usb 2-2: configuration #1 chosen from 1 choice > > > > ehci_hcd 0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 > > > > Unable to handle kernel NULL pointer dereference at 00000000000002a4 RIP: > > > > {:ehci_hcd:ehci_irq+224} > > > > > > Can you poke around in gdb, see which line it's dying at? > > > > It looks like at the line 620. At least here's what gdb told me: > > > > Line 620 of "ehci-hcd.c" starts at address 0x69c3 > > and ends at 0x69e2 . > > On my tree that's > > if ((status & STS_PCD) && device_may_wakeup(&hcd->self.root_hub->dev)) { Yes, that's it. > It's best to actually send a copy of line 620 - kernels vary a lot, and > many developers won't have that particualr -mm tree handy. > > The way I normally do this is to do `gdb vmlinux' and then `l > *0xffffffff880ad9d0'. Does it work for modules too? > If that lands you in some inline function then poke > around, displacing the EIP by +/- amounts until it lands outside the > inlined function so you can see the callsite. > > Anyway. Greg's tree seems rather buggy lately.. Well ... -- Beer is proof that God loves us and wants us to be happy - Benjamin Franklin - 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/