From: Bjorn Helgaas <helgaas@kernel.org>
To: Alex Williamson <alex.williamson@redhat.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Sanath S <Sanath.S@amd.com>,
shyam-sundar.s-k@amd.com,
Andreas Noever <andreas.noever@gmail.com>,
Michael Jamet <michael.jamet@intel.com>,
Yehezkel Bernat <YehezkelShB@gmail.com>,
linux-usb@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [bugzilla-daemon@kernel.org: [Bug 218360] New: Disk drive of TBT3/USB4 storage device can’t show up if connecting behind TBT3 dock or some USB4 docks DFP TBT port]
Date: Wed, 10 Jan 2024 13:00:21 -0600 [thread overview]
Message-ID: <20240110190021.GA2113949@bhelgaas> (raw)
#regzbot introduced: d3fcd7360338 ("PCI: Fix runtime PM race with PME polling")
Sanath, thank you very much for this report and the bisection!
I assume this happens on hot-adds, i.e., you boot the kernel, then
connect a USB4 dock, then connect the TBT3/USB4 storage device to the
dock?
Would you be able to attach the complete dmesgs log from working and
failing kernels? The ideal would be from d3fcd7360338 ("PCI: Fix
runtime PM race with PME polling"), which fails, and 5cd903bce9dd
("PCI/VPD: Add runtime power management to sysfs interface"), which
presumably works. But v6.7 and v6.5 is OK too.
Also the output of "sudo lspci -vv", which I assume doesn't depend on
which kernel you're running.
Bjorn
----- Forwarded message from bugzilla-daemon@kernel.org -----
Date: Wed, 10 Jan 2024 10:52:40 +0000
From: bugzilla-daemon@kernel.org
To: bjorn@helgaas.com
Subject: [Bug 218360] New: Disk drive of TBT3/USB4 storage device can’t show up if connecting behind TBT3 dock
or some USB4 docks DFP TBT port
Message-ID: <bug-218360-41252@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218360
Bug ID: 218360
Summary: Disk drive of TBT3/USB4 storage device can’t show up
if connecting behind TBT3 dock or some USB4 docks DFP
TBT port
Reporter: Sanath.S@amd.com
The disk drive of the TBT3/USB4 storage device can’t show up behind TBT3 dock
and some USB4 docks have a DFP TBT port.
TBT3/USB4 storage device can be authorized, the disk drive doesn’t show up.
Issue reproduce sequence: Connect USB4 dock to host → Connect TBT3/USB4 storage
device to dock DFP TBT3 port → TBT3/USB4 storage device disk driver can’t show
up.
The issue was observed in the latest mainline kernel 6.7.
Failing on all the below combination
HP Thunderbolt Dock 120W G2 HSN-IX01
HP Hook 2.0 USB4/TBT4 Dock (PV Phase)
CalDigit TS3Plus+ Thunderbolt Station 3 Plus
Dell Thunderbolt Dock – WD19TB
next reply other threads:[~2024-01-10 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 19:00 Bjorn Helgaas [this message]
2024-01-11 2:32 ` [bugzilla-daemon@kernel.org: [Bug 218360] New: Disk drive of TBT3/USB4 storage device can’t show up if connecting behind TBT3 dock or some USB4 docks DFP TBT port] Sanath S
2024-01-11 4:50 ` Sanath S
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=20240110190021.GA2113949@bhelgaas \
--to=helgaas@kernel.org \
--cc=Sanath.S@amd.com \
--cc=YehezkelShB@gmail.com \
--cc=alex.williamson@redhat.com \
--cc=andreas.noever@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=shyam-sundar.s-k@amd.com \
/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