From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 216497] New: USB connections through thunderbolt dock broken
Date: Sat, 17 Sep 2022 00:24:52 +0000 [thread overview]
Message-ID: <bug-216497-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216497
Bug ID: 216497
Summary: USB connections through thunderbolt dock broken
Product: Drivers
Version: 2.5
Kernel Version: 5.19.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 15 Sep 2022
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: jhnmlkvch9@gmail.com
Regression: No
Created attachment 301819
--> https://bugzilla.kernel.org/attachment.cgi?id=301819&action=edit
dmesg log for thunderbolt dock re-plug
After updating to kernel v5.19.9-arch1-1, usb ports on HP Thunderbolt Dock G2
stopped working. dmesg is getting flooded with the message:
xhci_hcd 0000:30:00.0: Error while assigning device slot ID
xhci_hcd 0000:30:00.0: Max number of devices this xHCI host supports is 64.
usb usb6-port1: couldn't allocate usb_device
Obviously I don't have 64+ devices connected. Strangely, if I boot with the
thunderbolt dock connected, everything works fine. Unplugging and re-plugging
the dock again results in unrecognized usb.
I'm attaching the part of dmesg where I unplug and re-plug the thunderbolt
dock. Note that all usb devices that are connected are correctly enumerated
while unplugging.
Rolling back to previous version of the kernel fixes the issue.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2022-09-17 0:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 0:24 bugzilla-daemon [this message]
2022-09-17 17:12 ` [Bug 216497] USB connections through thunderbolt dock broken bugzilla-daemon
2022-09-17 22:41 ` bugzilla-daemon
2022-09-19 5:32 ` bugzilla-daemon
2022-09-19 7:42 ` bugzilla-daemon
2022-09-19 8:11 ` bugzilla-daemon
2022-09-19 14:15 ` bugzilla-daemon
2022-09-20 1:04 ` bugzilla-daemon
2022-09-20 9:22 ` bugzilla-daemon
2022-09-20 9:29 ` bugzilla-daemon
2022-09-20 11:40 ` bugzilla-daemon
2022-09-26 1:24 ` bugzilla-daemon
2022-09-26 5:21 ` bugzilla-daemon
2022-09-26 11:10 ` bugzilla-daemon
2022-10-07 13:54 ` bugzilla-daemon
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=bug-216497-208809@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--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).