Hello! I'm observing a bug where the most prominent symptom is that the built-in SD card reader disappears after waking up from suspend. Laptop: MacBookPro11,3 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) (prog-if 30 [XHCI]) SD card reader: Apple Card Reader 05ac:8406 The bug was reported previously on bugzilla but never followed up on: https://bugzilla.kernel.org/show_bug.cgi?id=111201 Steps to reproduce: $ lsusb Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 05ac:8289 Apple, Inc. Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 001 Device 003: ID 05ac:0263 Apple, Inc. Apple Internal Keyboard / Trackpad (MacBook Retina) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub $ sudo systemctl suspend [Wait 10s, then wake the system up] $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 05ac:8289 Apple, Inc. Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 001 Device 003: ID 05ac:0263 Apple, Inc. Apple Internal Keyboard / Trackpad (MacBook Retina) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub $ lsusb -vvv Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub [long hang, on the order of three minutes] can't get hub descriptor, LIBUSB_ERROR_TIMEOUT (Resource temporarily unavailable) [and a couple of more errors] Expected result: The output of both lsusb commands should be equal. Actual results: - The SD card reader (05ac:8406) is missing from the second lsusb. - Running lsusb -vvv hangs for a long time - lots of error messages in kernel log Logs: https://gist.github.com/samuelsadok/6d7b3e3015d3370a92ed4702e4d3c4b5 I'm happy to provide more data, do tests or patch around the kernel if it helps. Best, Samuel -- 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
