Re: ehci problem triggerable by storage

On Friday 03 August 2007, Oliver Neukum wrote:
> Well, I've thought a bit about this. I know a hub is to blame. Even if I did
> learn what causes this specific error, it wouldn't help in the other cases.
> IMHO improving error handling is better than avoiding this fault.

But do you know *how* a hub is to blame?  A sniffer is invaluable
for sorting out many errors.  This is the kind of thing where you
could waste a week or more trying to figure out what would become
apparent with just five or ten minutes with such a sniffer.

By the way ... that kind of equipment is rentable, probably even
leasable.

- Dave



-------------------------------------------------------------------------
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/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel