From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 206603] New: Regression: Thunderbolt 3 Dock USB not working when connecting it for the second time
Date: Wed, 19 Feb 2020 19:02:17 +0000 [thread overview]
Message-ID: <bug-206603-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=206603
Bug ID: 206603
Summary: Regression: Thunderbolt 3 Dock USB not working when
connecting it for the second time
Product: Drivers
Version: 2.5
Kernel Version: 5.4.12
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: D-12twm7qq8vgi7o@maildrop.cc
Regression: No
Created attachment 287515
--> https://bugzilla.kernel.org/attachment.cgi?id=287515&action=edit
kernel-5.4.10-200.fc31.x86_64.log
I did submit this bug to the Fedora bug tracker in January. Since the latest
update this is now happening on Ubuntu too, which is why I'm now submitting
this to the Kernel bug tracker.
Bug at Red Hat Bugzilla for reference:
https://bugzilla.redhat.com/show_bug.cgi?id=1790889
---
I'm using this Thunderbolt 3 Dock together together with my ThinkPad T480s:
https://i-tec.cz/de/produkt/tb3hdmidock-3/ (P/N TB3HDMIDOCK)
https://web.archive.org/web/20180929103728/https://i-tec.cz/de/produkt/tb3hdmidock-3/
It contains HDMI and USB outputs.
When connecting the Dock for the second time after boot (boot, plug, unplug,
and plug again), USB devices connected to
the Dock are not working (at least I've tried keyboard, mouse and mass storage
devices).
The HDMI output continues to work.
This did work before using the following kernel versions:
- 5.4.7-200.fc31 (Fedora)
- 5.3.0-29-generic (Ubuntu)
When upgrading the Kernel, it breaks:
- 5.4.7-200.fc31 (Fedora)
- 5.3.0-40-generic (Ubuntu)
Both Fedora and Ubuntu keep old Kernel versions for a while. I can still boot
one of the older kernels and then the bug is not happening.
Steps to reproduce:
1. Boot Notebook
2. Connect Dock
(HDMI and USB devices connected to the Dock are now working.)
3. Disconnect Dock
4. Connect Dock again
(HDMI device connected to the Dock is now working again, USB devices connected
to the Dock are not working until reboot.)
This is from the kernel log:
> Jan 14 08:04:48 kernel: Registered IR keymap rc-cec
> Jan 14 08:04:48 kernel: rc rc0: DP-1 as
> /devices/pci0000:00/0000:00:02.0/rc/rc0
> Jan 14 08:04:48 kernel: input: DP-1 as
> /devices/pci0000:00/0000:00:02.0/rc/rc0/input38
> Jan 14 08:04:48 kernel: typec_displayport port1-partner.0: failed to enter
> mode
> Jan 14 08:04:48 kernel: thunderbolt 0-1: new device found, vendor=0x16b
> device=0x9003
> Jan 14 08:04:48 kernel: thunderbolt 0-1: ComDis TB3HDMIDOCK
Full log is attached.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2020-02-19 19:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 19:02 bugzilla-daemon [this message]
2020-12-08 7:21 ` [Bug 206603] Regression: Thunderbolt 3 Dock USB not working when connecting it for the second time 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-206603-208809@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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).