From: Rohan Hendrik Jotz-Lean <rohan@rohanlean.de>
To: linux-usb@vger.kernel.org
Subject: Enumeration of USB keyboard connected to dock fails during boot
Date: Mon, 22 Jul 2019 23:31:17 +0200 [thread overview]
Message-ID: <e63353a229a3fc61c2467a87a12064ac876e87b3.camel@rohanlean.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
Hi,
I have a USB keyboard that works in UEFI apps (and grub) but if plugged
into a dock stops working when Linux boots. It works when hotplugged
into the dock or plugged into the laptop directly before or after
booting. A mouse plugged into the dock does not share this problem. (I
have no other keyboard to test at hand.)
Kernel version: 5.1.18-300.fc30.x86_64
XHCI USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1
Hub: 17ef:a38f Lenovo USB2.0 Hub
Keyboard: 04d9:0192 Holtek Semiconductor, Inc. USB-HID Keyboard
Relevant kernel messages are attached.
My ignorant initial thought is that the hub should be transparent to
the keyboard, so that the fault is unlikely to lie with the keyboard. I
have unsuccessfully tried the delayed initialisation quirk on the
keyboard.
I have asked the Fedora kernel developers about this problem first --
they told me to ask here.
Thanks for your help.
[-- Attachment #2: kernel_messages.txt --]
[-- Type: text/plain, Size: 1281 bytes --]
Jul 22 19:16:14 kernel: usb 2-1.3.3.3: new full-speed USB device number 9 using xhci_hcd
Jul 22 19:16:14 kernel: usb 2-1.3.3.3: device descriptor read/64, error -32
Jul 22 19:16:14 kernel: usb 2-1.3.3.3: device descriptor read/64, error -32
Jul 22 19:16:15 kernel: usb 2-1.3.3.3: new full-speed USB device number 10 using xhci_hcd
Jul 22 19:16:15 kernel: usb 2-1.3.3.3: device descriptor read/64, error -32
Jul 22 19:16:15 kernel: usb 2-1.3.3.3: device descriptor read/64, error -32
Jul 22 19:16:15 kernel: usb 2-1.3.3-port3: attempt power cycle
Jul 22 19:16:15 kernel: usb 2-1.3.3.3: new full-speed USB device number 11 using xhci_hcd
Jul 22 19:16:15 kernel: usb 2-1.3.3.3: Device not responding to setup address.
Jul 22 19:16:16 kernel: usb 2-1.3.3.3: Device not responding to setup address.
Jul 22 19:16:16 kernel: usb 2-1.3.3.3: device not accepting address 11, error -71
Jul 22 19:16:16 kernel: usb 2-1.3.3.3: new full-speed USB device number 12 using xhci_hcd
Jul 22 19:16:16 kernel: usb 2-1.3.3.3: Device not responding to setup address.
Jul 22 19:16:16 kernel: usb 2-1.3.3.3: Device not responding to setup address.
Jul 22 19:16:16 kernel: usb 2-1.3.3.3: device not accepting address 12, error -71
Jul 22 19:16:16 kernel: usb 2-1.3.3-port3: unable to enumerate USB device
reply other threads:[~2019-07-22 21:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e63353a229a3fc61c2467a87a12064ac876e87b3.camel@rohanlean.de \
--to=rohan@rohanlean.de \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).