On Thu, 17 May 2007, Yum Rayan wrote: > Hi, > > I have a bunch of USB devices configured for ethernet over USB > connected to my machine. The host is running a 2.6.16 based kernel and > I notice that rx errors reported via /proc/net/dev keep increasing > infinitely. Initially the device responds without any problems, but at > some random time, eventually the device and USB subsystem seem to lock > up, i.e. commands like lsusb begin to fail. The USB device itself is > also running a 2.6.9 based kernel, but during the time the RX errors > are seen there is no TX or RX from the device side. Neither are any > errors reported via /proc/net/dev on the USB side. > > After some debug statements, I see that the RX errors are due to -71 > EPROTO errors. Any help appreciated in understanding what is happening > here. Here are the related messages (the messages keep repeating): > > ohci_hcd 0000:00:04.0: urb c7881c60 path 2 ep1in 6d160000 cc 6 --> status -71 > mydev3: rx throttle -71 > mydev3: rxqlen 3 --> 4 > ohci_hcd 0000:00:04.0: urb c3a33ce0 path 2 ep1in 6d160000 cc 6 --> status -71 > mydev3: rx throttle -71 > mydev3: rxqlen 3 --> 4 > ohci_hcd 0000:00:04.0: urb c3a33e00 path 1 ep1in 6d160000 cc 6 --> status -71 > mydev1: rx throttle -71 > mydev1: rxqlen 3 --> 4 > ohci_hcd 0000:00:04.0: urb c7881cc0 path 2 ep1in 6d160000 cc 6 --> status -71 > mydev3: rx throttle -71 > ohci_hcd 0000:00:04.0: urb c3a33da0 path 1 ep1in 6d160000 cc 6 --> status -71 > mydev1: rx throttle -71 > mydev3: rxqlen 3 --> 4 > mydev1: rxqlen 3 --> 4 > ohci_hcd 0000:00:04.0: urb c7881d20 path 1 ep1in 6d160000 cc 6 --> status -71 > mydev1: rx throttle -71 > mydev1: rxqlen 3 --> 4 > ohci_hcd 0000:00:04.0: urb c7881c00 path 2 ep1in 6d160000 cc 6 --> status -71 > mydev3: rx throttle -71 > mydev3: rxqlen 3 --> 4 > ohci_hcd 0000:00:04.0: urb c3a33d40 path 1 ep1in 6d160000 cc 6 --> status -71 > mydev1: rx throttle -71 > mydev1: rxqlen 3 --> 4 > ohci_hcd 0000:00:04.0: urb c7881c60 path 2 ep1in 6d160000 cc 6 --> status -71 > mydev3: rx throttle -71
These error codes indicate low-level USB communication problems. There may be something wrong with the USB cable, or the device's USB interface may have stopped running. Alan Stern ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
