Am Samstag 28 Juli 2007 schrieb David Brownell:
> On Friday 27 July 2007, Alan Stern wrote:
> > In my experience this sort of thing tends to be caused by low-level
> > hardware communications errors. Noise in the USB data lines or a
> > missing handshake packet, stuff like that. Not much extra debugging
> > can be done; the "3strikes" indication comes directly from the
> > controller hardware.
I did systematic testing. The hub causes it.
> Well, that's one theory. Thing is, this kind of problem happens
> more often than it should. No matter what causes it, it'd be better
> to recover from it ... or prevent it from happening.
Nevertheless I get an IO error. Our error handling is deficient.
> My theory has been different: that some USB peripherals get deeply
> confused if Linux talks to them "too fast" (i.e. probably anything
> faster than MS-Windows). Notice how the "recovery" that followed
> involved a device reset.
>
> But -- never actually having had both a highspeed USB sniffer *AND*
> hardware exhibiting this problem in the same place -- I've not been
> able to test that theory.
The hub in question is light and small. Give me your address and I'll
put it in the mail.
Regards
Oliver
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
