On Tuesday 15 October 2002 01:02, Martin Diehl wrote: > I't looks to me like some kind of donelist corruption but might be td > hashbin or pci_pool as well. Maybe the output below would tell you > something. It was obtained during re-enumeration after firmware download > where a firmware bug caused the device to hang in the GetDescriptor > request. > > I've no idea if this is related to Lars's problem, but I've also seen this > happen during reboot with the FX+broken firmware still connected.
I indeed have FX and firmware attached that one might question, and from the time i developed it, i know too well how poisoness it can be for the usb stack. I can exclude this issue almost certainly for this case. As i plan to continue working on the firmware i might perhaps be able to report crashes or oops in 2.5.* coused by evily behaving devices in case the development can done under this version, which i'd better not dare given the state of the kernel i found. Especially the probs seen in the fs scare me too much. I booted with the device in question attached and the whole process went through fine. No - i believe that David's patch really hits the spot. -lars ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
