Tom Collins wrote:
I replaced drivers/usb/* and include/linux/usb*.h in my 2.4.19 tree with the versions from 2.4.21-pre3. I was able to compile the kernel, but when I installed it I got the following errors when I turned on my USB 2.0 hard drive:
hub.c: new USB device 00:13.2-2, assigned address 2
ehci-hcd 00:13.2: fatal error
So the hardware threw up its hands because something happened that it didn't like at all. At that point it's hard to say just what, particularly since you haven't included the debug messages. The register dumps can help, but I suspect you'd need more detailed diagnostics than you'd get by default.
I'd suspect something went goofy when you swapped out the USB code, unless you get the same failure on a generic 2.4.21-pre3 or 2.5.58+ kernel.
pci_pool_free 00:13.2/ehci_qtd, a03ee120/3ee120 (bad dma) pci_pool_free 00:13.2/ehci_qtd, a03ee0c0/3ee0c0 (bad dma)
This might indicate some corruption in the kmalloc pool (used to track pages in that qtd pool), or else suggest that the reason the hardware got unhappy is because it was somehow given bogus DMA addresses.
ehci-hcd 00:13.2: stopped in_interrupt!
There's a small patch that "hcd.c" needs to get, basically after an HCD dies in_interrupt() it's got to cause the cleanup to happen in a task context (keventd). Lacking that, the rest of the messages will be meaningless, since the hcd was supposed to clean up but it's been left in a "dead" state. - Dave ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
