From: Bjorn Helgaas <helgaas@kernel.org>
To: linux-pci@vger.kernel.org
Cc: Lukas Wunner <lukas@wunner.de>,
Andreas Noever <andreas.noever@gmail.com>,
Michael Jamet <michael.jamet@intel.com>,
Mika Westerberg <westeri@kernel.org>,
Yehezkel Bernat <YehezkelShB@gmail.com>,
Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
linux-usb@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: [bugzilla-daemon@kernel.org: [Bug 220175] New: NVMe SSD doesn't work via Thunderbolt enclosure on Framework 13 (Ryzen AI 300)]
Date: Thu, 29 May 2025 17:22:23 -0500 [thread overview]
Message-ID: <20250529222223.GA119209@bhelgaas> (raw)
[+cc pciehp, thunderbolt, nvme folks;
+bcc Andrey (reporter)]
Andrey, sorry that you tripped over this, and thank you very much for
reporting it. I'm forwarding this to the mailing lists because most
subsystems don't really pay attention to the bugzilla.
Obviously we don't want to have to use kernel args to make things
work, and we also don't want to have to use /sys/bus/pci/rescan after
a hot-add.
IIUC, if you boot while the SSD in the enclosure is already attached
to the USB 3.2 port, everything works fine? Could you please attach a
complete dmesg log from such a boot to the bugzilla, just as a
baseline?
----- Forwarded message from bugzilla-daemon@kernel.org -----
https://bugzilla.kernel.org/show_bug.cgi?id=220175
Summary: NVMe SSD doesn't work via Thunderbolt enclosure on
Framework 13 (Ryzen AI 300)
Created attachment 308180
--> https://bugzilla.kernel.org/attachment.cgi?id=308180&action=edit
lspci -vvv
I have a Samsung 970 Evo Plus SSD installed in an ACASIS TBU401E USB4
enclosure. When I connect it to the USB 3.2 port, everything is fine, the SSD
is detected by the scsi driver and shows up in the system as /dev/sdb. But when
I plug it into the USB4 port, the device doesn't show up.
However, I can connect and use this disk by using kernel args
`nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off` and
doing `echo 1 | sudo tee /sys/bus/pci/rescan` after connecting the SSD.
Solution described in https://bugzilla.kernel.org/show_bug.cgi?id=216000#c65
doesn't help and breaks most of the PCIe devices in the system.
More info:
```
$ uname -r
6.14.6-300.fc42.x86_64
$ ls /dev/nvme*
zsh: no matches found: /dev/nvme*
$ cat /sys/bus/thunderbolt/devices/1-2/vendor_name
ACASIS
$ cat /sys/bus/thunderbolt/devices/1-2/authorized
1
$ inxi -MC
Machine:
Type: Laptop System: Framework product: Laptop 13 (AMD Ryzen AI 300 Series)
v: A9 serial: <superuser required>
Mobo: Framework model: FRANMGCP09 v: A9 serial: <superuser required>
UEFI: INSYDE v: 03.03 date: 03/10/2025
CPU:
Info: 12-core model: AMD Ryzen AI 9 HX 370 w/ Radeon 890M bits: 64
```
next reply other threads:[~2025-05-29 22:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 22:22 Bjorn Helgaas [this message]
2025-06-02 1:09 ` [bugzilla-daemon@kernel.org: [Bug 220175] New: NVMe SSD doesn't work via Thunderbolt enclosure on Framework 13 (Ryzen AI 300)] Andrey Brusnik
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=20250529222223.GA119209@bhelgaas \
--to=helgaas@kernel.org \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=michael.jamet@intel.com \
--cc=sagi@grimberg.me \
--cc=westeri@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