(Gary, your system clock is set well into the future; UTC?)
Gary A. Gorgen wrote:
David Brownell wrote:
Thanks for the info about what 2.5.61 shows ... seems more polite.
It doesn't seem to be giving you "Unrecoverable Error" (UE) failures,
unlike the 2.4 "usb-ohci" code. (At least, not without more work!)
The (UE) are very rare. 2 out of 100 maybe.
They should be so rare that they never happen ... ;)
<7>usb 5-1: urb ce02e500 usb-00:12.0-1 ep-2-IN cc 5 --> status -110
<4>usbfs: USBDEVFS_BULK failed dev 5 ep 0x82 len 4096 ret -110
... so basically the I/O is timing out on USB. Do you know why?
Not a clue. :-(
The timeout to the read is 3 sec.
That's a higher level timeout, in software. You're getting
a lower level USB level timeout: device is not responding.
If your devices are misbehaving, that can trigger other errors.
I've tried everything I can think of to recover form the error,
nothing works short of a power cycle on the part.
You should find out more about this error. Can you put some kind
of sniffer on the USB and watch the traffic? Resolving that issue
might mean the other ones don't show up any more for you.
The 2.4 urb error code, spit out what looks like, response/request lengths.
Should this be added to 2.5 ?
I saw some strange numbers come out of 2.4
The 2.5 code should have some more verbose diagnostic options
already. Enable them. I think those strange numbers on 2.4
were symptoms of some previous problem ... and wouldn't be very
surprised to know that both driver versions have the same bug.
- Dave
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
