[Bug 1142380] New: USB 2.0 ports not working after resume from sleep
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380 Bug ID: 1142380 Summary: USB 2.0 ports not working after resume from sleep Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome@forge.provo.novell.com Reporter: avaish92@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- USB 2.0 ports not working after resume from sleep, however usb 3.0 ports are working fine. How to reproduce: Boot into opensuse leap 15.1, put the device to sleep, wake the device up, plug-in any usb device into any one of the 2.0 ports. Kernel - 4.12.14-lp151.28.10-default Harware description - Same as in 1134807 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380
Aman Vaishya
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380#c1
Yifan Jiang
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380#c2
--- Comment #2 from Aman Vaishya
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380#c3
Yifan Jiang
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380#c6
--- Comment #6 from Aman Vaishya
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380#c7
--- Comment #7 from Aman Vaishya
1. Do devices attached before going to sleep keep working? 2. Please attach dmesg and the output of "lspci -v" before and after sleeping.
Hi Oliver, 1. If the usb device(pen-drive in this case) is attached to the usb 2.0 port before putting the system to sleep, it works fine. I tried removing and re-inserting it into a different usb 2.0 port and saw that it was mounted. 2. Attached the outputs of the commands as a zip. The filenames are self explanatory. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380#c8
--- Comment #8 from Oliver Neukum
1. If the usb device(pen-drive in this case) is attached to the usb 2.0 port before putting the system to sleep, it works fine. I tried removing and re-inserting it into a different usb 2.0 port and saw that it was mounted.
OK, please activate dynamic debugging for xhci echo "module xhci_hcd +mfp" > /sys/kernel/debug/dynamic_debug/control And rerun the test without a device and plug it in after resume. Provide dmesg after that. (No zipping) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380#c9
--- Comment #9 from Aman Vaishya
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380#c10
--- Comment #10 from Aman Vaishya
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380#c11
--- Comment #11 from Aman Vaishya
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380#c12
--- Comment #12 from Aman Vaishya
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380#c13
--- Comment #13 from Aman Vaishya
(In reply to Aman Vaishya from comment #7)
1. If the usb device(pen-drive in this case) is attached to the usb 2.0 port before putting the system to sleep, it works fine. I tried removing and re-inserting it into a different usb 2.0 port and saw that it was mounted.
OK, please activate dynamic debugging for xhci
echo "module xhci_hcd +mfp" > /sys/kernel/debug/dynamic_debug/control
And rerun the test without a device and plug it in after resume. Provide dmesg after that. (No zipping)
Done -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380#c14
--- Comment #14 from Oliver Neukum
And rerun the test without a device and plug it in after resume. Provide dmesg after that. (No zipping)
Done
For the record: The device is detected but communications fail [ 306.733689] usb 3-3: new high-speed USB device number 2 using xhci_hcd [ 306.861726] usb 3-3: device descriptor read/64, error -71 [ 307.097814] usb 3-3: device descriptor read/64, error -71 [ 307.333674] usb 3-3: new high-speed USB device number 3 using xhci_hcd [ 307.461738] usb 3-3: device descriptor read/64, error -71 [ 307.697780] usb 3-3: device descriptor read/64, error -71 [ 307.805745] usb usb3-port3: attempt power cycle [ 311.857678] usb 3-3: new high-speed USB device number 5 using xhci_hcd [ 311.985687] usb 3-3: device descriptor read/64, error -71 [ 312.221805] usb 3-3: device descriptor read/64, error -71 [ 312.457679] usb 3-3: new high-speed USB device number 6 using xhci_hcd [ 312.585771] usb 3-3: device descriptor read/64, error -71 [ 312.821759] usb 3-3: device descriptor read/64, error -71 [ 312.929716] usb usb3-port3: attempt power cycle [ 313.581689] usb 3-3: new high-speed USB device number 7 using xhci_hcd [ 313.581867] usb 3-3: Device not responding to setup address. [ 313.789843] usb 3-3: Device not responding to setup address. [ 313.997629] usb 3-3: device not accepting address 7, error -71 [ 314.125617] usb 3-3: new high-speed USB device number 8 using xhci_hcd [ 314.125805] usb 3-3: Device not responding to setup address. [ 314.333847] usb 3-3: Device not responding to setup address. [ 314.541676] usb 3-3: device not accepting address 8, error -71 [ 314.541713] usb usb3-port3: unable to enumerate USB device -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380#c15
Oliver Neukum
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380#c16
Nicolas Patricio Saenz Julienne
Nicolas, caould this be the issue you saw with the docking station?
Note that the Dock issue was seen in tumbleweed. In the docking station case the chip would disconnect (as in appearing as disconnected in the port status) after the remote wakeup, which was triggered by an Ethernet chip. Once disconnected the device was removed altogether. So I'd say it's unlikely, but who knows. To make things more clear it would be nice to get extra debug info. Aman can you provide the dmesg output of a suspend test after having run these two commands: echo "module xhci_hcd +mfp" | sudo tee > /sys/kernel/debug/dynamic_debug/control echo "module usbcore +mfp" | sudo tee
/sys/kernel/debug/dynamic_debug/control
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380#c17
Aman Vaishya
(In reply to Oliver Neukum from comment #15)
Nicolas, caould this be the issue you saw with the docking station?
Note that the Dock issue was seen in tumbleweed.
In the docking station case the chip would disconnect (as in appearing as disconnected in the port status) after the remote wakeup, which was triggered by an Ethernet chip. Once disconnected the device was removed altogether. So I'd say it's unlikely, but who knows.
To make things more clear it would be nice to get extra debug info. Aman can you provide the dmesg output of a suspend test after having run these two commands:
echo "module xhci_hcd +mfp" | sudo tee > /sys/kernel/debug/dynamic_debug/control echo "module usbcore +mfp" | sudo tee > /sys/kernel/debug/dynamic_debug/control
I am unable to reproduce this issue, the device gets mounted everytime. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380
http://bugzilla.opensuse.org/show_bug.cgi?id=1142380#c18
Oliver Neukum
I am unable to reproduce this issue, the device gets mounted everytime.
A regular update to Tumbleweed has fixed the issue. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com