On Tue, 22 Jun 2004, Ian E. Morgan wrote: > I concur with your assessment, but I am at a loss to explain it, or where to > start digging to further debug the issue. > > Do you have any patches I could test out now? I'm getting desperate. > > I've discovered that the deadlock does NOT occur with a 2.4 kernel (FC2's > ugly-as-sin 2.4.22-1.2194.nptl). But of course that means I don't get > block-device hotplug events, and 2.4's usb-storage is about as close to > completely busted as you can get, which is going to mean a tonne more coding > to get this project working cleanly. I'd would really like to stick with > 2.6.x if possible. Any help is greatly appreciated. > > Regards, > Ian Morgan
I don't have any patches for you yet (difficulty getting code updates in BitKeeper). However, my not-very-reliable memory is that the logs you posted before didn't include much detail from the time period when the bus reset took place. Can you provide a debugging log showing what happens at that time? Alan Stern ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel