... Any long-living transfer might run into this problem. F.e. if there is an INT IN scheduled to poll some input activity, this transfer might be active for seconds, minutes or even longer. All it needs is three spikes on the wire to make the urb failing with EILSEQ.
...
IMHO it's the drivers job to be prepared to get these errors and recover appropriately.
I agree. For example, EILSEQ is also what UHCI reports during the period before khubd starts disconnect processing and after the device was physically disconnected.
Good policy for such long-lived transfers would be to hold off for a while, maybe HZ/8, before retrying. Because long-lived transfers must after all be smart enough to retry ... :)
- Dave
------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
