Description of problem: I've previously raised a report about USB errors on booting... https://bugzilla.redhat.com/show_bug.cgi?id=250545 This case reports similar problems but as applied to a USB device hot-plugged in after the system is already booted. My USB mouse looks like this when it has properly configured (from /proc/bus/usb/devices): T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 8 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=1267 ProdID=0210 Rev= 0.01 S: Product=PS/2+USB Mouse C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA I:* If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=10ms Notice that the first interface number is 1, which isn't strictly compliant with the USB spec, but is compatible with the loosening up of the interpretation made by a certain popular operating system vendor, see http://www.microsoft.com/whdc/system/bus/USB/USBFAQ_intermed.mspx where it says: Windows XP Service Pack 2 (SP2) relaxed the requirement that interface numbers be consecutive by making changes to the driver Usbccgp.sys. Beginning with SP2, interface numbers need only be increasing. So I guess now we're likely to see a new army of USB devices that are compatible with windows but not strictly with the USB spec. Groan. Anyway, linux usually seems to understand the device, but does give a warning. Version-Release number of selected component (if applicable): kernel 2.6.22.4-65.fc7 How reproducible: Intermittent Steps to Reproduce: 1. Plug in USB mouse 2. Observe behaviour....if it works then problem is not reproducable this time, but if it doesn't work continue with subsequent steps 3. Unplug mouse and retry again and again...consistent behaviour each time 4. Plug in USB pen...works 5. Plug in USB mouse...now works Actual results: USB device sometimes doesn't work Expected results: Works every time Additional info: When the USB mouse fails to be recognised, dmesg reports this: usb 2-1: new low speed USB device using uhci_hcd and address 4 usb 2-1: device descriptor read/64, error -71 usb 2-1: device descriptor read/64, error -71 usb 2-1: new low speed USB device using uhci_hcd and address 5 usb 2-1: device descriptor read/64, error -71 usb 2-1: device descriptor read/64, error -71 usb 2-1: new low speed USB device using uhci_hcd and address 6 usb 2-1: device not accepting address 6, error -71 usb 2-1: new low speed USB device using uhci_hcd and address 7 usb 2-1: device not accepting address 7, error -71 When it does work, dmesg reports this: usb 2-1: new low speed USB device using uhci_hcd and address 8 usb 2-1: config 1 has an invalid interface number: 1 but max is 0 usb 2-1: config 1 has no interface number 0 usb 2-1: configuration #1 chosen from 1 choice input: PS/2+USB Mouse as /class/input/input8 input: USB HID v1.00 Mouse [PS/2+USB Mouse] on usb-0000:00:1d.1-1
Interesting. I'll poke Alan Stern about the strange maximum number.
I suppose that interface number message will remain: http://marc.info/?t=118853065000002&r=1&w=2 The summary is, as long as the device ultimately works, there's nothing to be concerned about. The -71 part is bad, if it means the failure of enumeration. But this usually means that something is broken, often a cable.
I haven't seen this issue for a while. It may have been fixed in newer kernel releases. If I notice anything I'll add it here.
Hello David, (As you know by now) I'm reviewing this bug as part of the kernel bug triage project, an attempt to isolate current bugs in the fedora kernel. http://fedoraproject.org/wiki/KernelBugTriage If you're not seeing this issue any longer could you please close CURRENTRELEASE indicating what you think may have fixed the problem for you. Cheers Chris
Created attachment 212951 [details] behaviour seen in 2.6.22.5-76.fc7 I did further testing and I was able to reproduce the problem, in 2.6.22.5-76.fc7 I see errors as attached, now saying "Maybe the USB cable is bad?" which is a more friendly message from last time. However I believe the root of this problem to be a faulty mouse, as I have also been able to reproduce similar problems on my wife's WinXP computer. Connecting the mouse seems to be intermittently bad and good. So I am happy to close this case.
I can resolve this case to closed, but given that there seem to have been useful recent changes (perhaps made due to this case??) in the log reporting, indicating the possibility of a faulty cable, how should this case be resolved?
Since you suspect it is bad hardware (and Pete Zaitcev's comment backs this up), I'm closing NOTABUG as it isn't something the kernel can really do anything about. Cheers Chris