On Wed, 16 Mar 2016, ais523 wrote: > One line summary of the problem: > Connecting an Osprey 2 Mini sometimes causes it to reset every 200ms > > Full description of the problem/report: > This report is about a hardware compatibility issue related to the > Osprey 2 Mini, a cellular router that can connect to a computer either > wirelessly or via USB. I am running Linux 4.5.0-040500, turning the > device on, then connecting it to the computer via the USB port (it is > typically also connected to the computer via wifi). When I do this, > there is around a 20-30% chance that the device is repeatedly reset > approximately every 200 milliseconds (which is visible on the device as > one of the LEDs on the device flashes when it resets); on occasion this > loop (when it happens) ends naturally, either almost immediately or > after several seconds, but normally, if a loop starts, it continues > until I disconnect or switch off the device. Similar results are seen > if I connect the device and then turn it on, although I have tested > this situation less extensively. The resets seem to be most likely to > happen on the first attempt I make to connect the device, and to be > more likely to happen after a disconnection if they happened > beforehand, but I am not confident that either pattern is anything > other than chance/confirmation bias. > > While a reset loop is occurring, the line > > usb 1-1.2: reset high-speed USB device number # using ehci-pci > > (where # is a number that stays constant in any given reset loop, but > becomes higher if I disconnect and reconnect the device) occurs > repeatedly in the kernel log, at the same intervals as the device > resetting. Additionally, my userspace desktop environment sometimes > acts as though I had connected a CD drive containing a (corrupted) > audio CD. Please post a usbmon trace showing what happens when you plug in the device. (See Documentation/usb/usbmon.txt for instructions). Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
