On Tue, Jun 18, 2002 at 04:41:05PM +0200, Duncan Sands wrote:
> Hi Georg, thanks for answering. Things are different with uhci. I get similar
> messages, but only a few hundred (rather than an infinite number). For example,
>
> 16:04:10 kernel: usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 490 ret
>-110
> 16:04:10 kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x7 len 106 ret -110
> 16:04:10 kernel: usb_control/bulk_msg: timeout
>
> I don't get any "usb-uhci.c: interrupt, status 2, frame# 1349" type messages.
These are usb-uhci-specific and AFAIK suppressed in uhci. Appearing only
once in a while, the messages can be considered harmless, but when they are
coming regularely, the device is dead. So one command kills the whole
device.
> However, after these messages stop, all is not well. For example, if I do
> cat /proc/bus/usb/devices then I get messages saying
> "usb.c: error getting string descriptor 0 (error=-110)". Here is what appears
> on screen (just the last bit, the bit where the errors show):
Looks like the same disease, so usb-uhci and uhci have the same problem...
Have you tried it with an OHCI board? Was there a version, where the device
worked?
--
Georg Acher, [EMAIL PROTECTED]
http://www.in.tum.de/~acher/
"Oh no, not again !" The bowl of petunias
----------------------------------------------------------------------------
Bringing you mounds of caffeinated joy
>>> http://thinkgeek.com/sf <<<
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
