On Mon, 13 Feb 2006, Pedro Monjo Florit wrote: > Thanks again for your time and help. I really appreciate it. > > Of course I understand that the kernel might have bugs. Maybe I did not > asked the question correctly (I am not an English native speaker). What > I wanted to know if there were some reports of errors of the same kind, > but that could not be solved since they were not easily reproduced.
I understand. No, I'm not aware of any other error reports of the same kind. > In > any case, I have finally found out that it is the USB device that is > failing. > > What I would suggest is that the USB device driver should protect itself > from failing devices (or hubs, cables, etc.) I think that there is no > point in trying to contact again and again with a device that is not > respoding. After 10/100/1000/?? times, the device driver should stop > trying. Filling the syslog with repeated error messages is useless. We've known about this weakness in the hub driver for a long time, but no one has done anything about it. Probably because it doesn't come up very often, so it doesn't bother many people. And when it does happen, it generally turns out to be bad hardware (as in your case), so replacing the hardware fixes the problem with no need for code changes. Alan Stern ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
