FS#66071 - [linux] Unplugged USB to Serial devices won't unbind

Attached to Project: Arch Linux
Opened by Neal (meltdown) - Thursday, 02 April 2020, 00:25 GMT
Last edited by freswa (frederik) - Thursday, 02 April 2020, 12:23 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
All Linux kernels versions since 5.5.7 are giving me an issue on my T440 ThinkPad. Physically unplugging a CP2102N, FTDI, ESP8266, or ESP32 doesn't seem to be detected by the xHCI host. lsusb shows it listed still. Plugging it back in doesn't add duplicates, but I am unable to communicate with them. Minicom reports Input/Output Error.
Downgrading to Linux 5.5.6 allows them to work perfectly, lsusb doesn't show them immediately after removal.
journalctl and dmesg don't report errors or the dusconnects

Additional info:
* package version - 5.5.7 to 5.6
* config and/or logs - attached is lsusb command results after unplugging
* link to upstream bug report, if any - can't find any

Steps to reproduce:
Plug in a cp210x device, unplug, check lsusb to see if it is still listed.
   lsusb.txt (0.5 KiB)
This task depends upon

Closed by  freswa (frederik)
Thursday, 02 April 2020, 12:23 GMT
Reason for closing:  Upstream
Comment by Neal (meltdown) - Thursday, 02 April 2020, 00:53 GMT
I use the attached script (sudo ~/resetusb.sh) to reset the eHCI and xHCI binds. This removes all usb devices and allows me to use the devices as normal until I unplug them again. I also attached the results of lsusb/lsusb -t after replugging the unplugged device into a different port. It's on the list twice, which I thought did not happen, and it works. Replugging into the same port doesn't work or create duplicates
   resetusb.sh (0.4 KiB)
   lsusb.txt (0.6 KiB)
   lsusb -t.txt (0.7 KiB)
Comment by Jonas Witschel (diabonas) - Thursday, 02 April 2020, 07:19 GMT
Please report this issue upstream to the Linux kernel, this is not a problem with the Arch Linux packaging of the kernel since there have been no configuration changes between 5.5.6 and 5.5.7. The correct mailing list for the USB subsystem is linux-usb@vger.kernel.org, see https://www.kernel.org/doc/html/latest/admin-guide/reporting-bugs.html on how to report bugs to the kernel. Your report will be much more useful if you can provide the commit between 5.5.6 and 5.5.7 that is causing the issue, see https://wiki.archlinux.org/index.php/Bisecting_bugs_with_Git on how to use git bisect to find it.

Loading...