Re: ehci problem triggerable by storage
Oliver Neukum <[email protected]>
| Newsgroups | gmane.linux.usb.devel |
|---|---|
| Message-ID | <[email protected]> |
Am Freitag 03 August 2007 schrieb Greg KH: > On Mon, Jul 30, 2007 at 11:11:54AM -0700, David Brownell wrote: > > On Monday 30 July 2007, Oliver Neukum wrote: > > > > > > > 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. > > > > You'd need to send a high speed sniffer with it. ;) > > > > I was thinking that "Oliver Neukum <[email protected]>" ought > > to have ready access to such a sniffer. SuSE certainly > > should have sprung for one by now. > > Hahahahaha, oh, that's a good one... > > Heck, when I worked at a company that made huge systems that relied on > USB to work properly, such sniffers were not available. So for a > company that only creates software to be able to buy such a thing, well, > that's a very nice dream... 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. 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/ _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel