On Wed, 1 Mar 2006, David Brownell wrote: > > It's getting an error 84. > > > > Wed Mar 1 06:49:26 PST 2006 > > ** Control test cases: > > test 9: ch9 postconfig > > /proc/bus/usb/002/014 test 9, 55.293133 secs > > test 10: control queueing > > /proc/bus/usb/002/014 test 10 --> 84 (error 84) > > == -EILSEQ > > > test 14: control writes > > /proc/bus/usb/002/014 test 14 --> 71 (error 71) > > == -EPROTO > > > Wed Mar 1 09:14:25 PST 2006 > > ** Control test cases: > > test 9: ch9 postconfig > > /proc/bus/usb/002/014 test 9 --> 71 (error 71) > > test 10: control queueing > > /proc/bus/usb/002/014 test 10 --> 71 (error 71) > > test 14: control writes > > /proc/bus/usb/002/014 test 14 --> 71 (error 71) > > > > One oddity here is that these messages didn't appear until I pulled > > the USB cable. Perhaps there's an output flushing problem in the test > > code. > > The "-EPROTO" is common after unplug, but that -EILSEQ suggests you > have a real issue in the lh7a40x_udc driver ...
Not necessarily. -EILSEQ is a normal code used by uhci-hcd when a CRC or timeout error occurs on an IN transaction. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
