On Wed, May 29, 2024 at 03:20:37PM -0400, Mathieu Desnoyers wrote: > Hi Greg, > > I've been having issues with my WASD keyboard since I've had my T14s > Lenovo laptop (about 1 year). I thought it would eventually solve itself > magically, but it appears that drivers have not developed self-healing > capabilities yet. I'm now investigating to find the culprit and I would > welcome some pointers. > > What does not work: > > - On a Debian kernel 6.6.13+bpo-amd64 (but had this issue for a while > on prior kernels as well), > - WASD keyboard is plugged through a ThinkPad Unversal USB-C Dock v2, > - Laptop (Thinkpad T14s) goes to sleep by unplugging the USB-C cable > between laptop and dock, > - Laptop is resumed by plugging back USB-C cable between laptop and > dock. > > Most of the times (but not always), the keyboard does not come up and > I have to physically unplug the keyboard from the dock and plug it again. > The keyboard is a legacy USB device: Bus 009 Device 108: ID 04d9:0169 > Holtek Semiconductor, Inc. Keyboard, as shown in the lsusbvvv.txt output > taken when the keyboard works (see attached). > > I'm also providing the lsusbvvv-fail.txt output which shows the state > when the keyboard fails to work (see attached). > > This seems to work fine on resume if I plug the keyboard directly into > the laptop USB port. > > I have attached the suspend/resume sequence dmesg log from two cases: > > - success is when the keyboard is connected to the laptop USB port, > - fail is when the keyboard is connected through the dock. > > The following lines from the failed dmesg are interesting: > > [537001.699412] usb 9-1.1.3.2: new low-speed USB device number 103 using xhci_hcd > [537001.831646] usb 9-1.1.3.2: device descriptor read/64, error -32 > [537002.079982] usb 9-1.1.3.2: device descriptor read/64, error -32 > [537002.319449] usb 9-1.1.3.2: new low-speed USB device number 104 using xhci_hcd > [537002.451522] usb 9-1.1.3.2: device descriptor read/64, error -32 > [537002.692000] usb 9-1.1.3.2: device descriptor read/64, error -32 > [537002.800394] usb 9-1.1.3-port2: attempt power cycle > > AFAIU, error -32 points to negative EPIPE. > > Let me know if there is additional information I can collect to help diagnosing, > or configuration tweaks I can try. The problem reproduces easily, to getting more > data should not be an issue. It sounds like the hub that the keyboard is plugged into on the dock doesn't work right all the time. You could try plugging the keyboard into a different hub (interpose one between it and the dock if necessary -- or for that matter, interpose one between it and the laptop, bypassing the dock). Alan Stern
