Comment 28 for bug 1856608

Revision history for this message
Matthew Ruffell (mruffell) wrote :

@jeremyn54

Thanks for testing the test kernel. I suppose this means that "usb: handle warm-reset port requests on hub resume" is still causing us trouble.

@everyone

Can you please unplug all USB devices from your computer, and connect them one by one until you find the device which causes the "usb usb2-port2: Cannot enable. Maybe the USB cable is bad?" in dmesg?

When you find the device which is causing problems, can you write back with
1) What it is: Manufacturer, Make, Model etc.
2) The output the kernel has for it in demsg when you plug it in.

E.g. The device which started this whole thing:
https://www.spinics.net/lists/linux-usb/msg175832.html

Sandisk Ultra T C.
[ 1.868336] usb 3-3: New USB device found, idVendor=0781, idProduct=5596, bcdDevice= 1.00
[ 1.868337] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1.868338] usb 3-3: Product: Ultra T C
[ 1.868339] usb 3-3: Manufacturer: SanDisk
[ 1.868340] usb 3-3: SerialNumber: 4C530001090830111403

The above device is an example of a device that only works when "usb: handle warm-reset port requests on hub resume" is applied, and is the reason for the commit to exist in the first place.

We want to collect a list of devices that now fail to work when "usb: handle warm-reset port requests on hub resume" has been applied.

We will take the list of devices that fail, and write to the USB maintainer on linux-usb mailing list and see what we can do to fix things.

As a final note, if you can, please change out any USB cables for different ones, since they may be broken or not spec complaint, and testing with different cables can rule out hardware failures.

Thanks,
Matthew