Occasionally, after a disconnect, some reported to me that he immediately sees a low-speed device try to enumerate (and fail), followed up by a few more high speed enumeration events (that fail) that occur every 15 seconds. I don't see any USB traffic when these messages occur (verified with an o-scope and logic analyzer). After this, the host will not even try to enumerate our HID device when we plug it back in. If we reset the USB hub or unload the driver the reload the driver, it seems to correct itself. Has anyone else experienced this? Any luck alleviating it? Aug 2 18:15:16 DM-37x user.info kernel: [ 1216.669097] usb 1-1: USB disconnect, device number 43 // <- This is when we unplug our HID Aug 2 18:15:16 DM-37x user.info kernel: [ 1217.046112] usb 1-1: new low speed USB device number 44 using musb-hdrc Aug 2 18:15:31 DM-37x user.info kernel: [ 1232.296264] usb 1-1: new high speed USB device number 45 using musb-hdrc Aug 2 18:15:46 DM-37x user.err kernel: [ 1247.429077] usb 1-1: device descriptor read/64, error -110 Aug 2 18:16:02 DM-37x user.err kernel: [ 1262.663482] usb 1-1: device descriptor read/64, error -110 Aug 2 18:16:02 DM-37x user.info kernel: [ 1262.898040] usb 1-1: new high speed USB device number 46 using musb-hdrc Aug 2 18:16:12 DM-37x user.err kernel: [ 1273.327362] usb 1-1: device not accepting address 46, error -110 Aug 2 18:16:12 DM-37x user.info kernel: [ 1273.460906] usb 1-1: new high speed USB device number 47 using musb-hdrc [ 1283.896667] hub 1-0:1.0: unable to enumerate USB device on port 1 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
