From: Greg KH <gregkh@linuxfoundation.org>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"Kovacs, Alexander" <Alexander.Kovacs@amd.com>,
"Pananchikkal, Renjith" <Renjith.Pananchikkal@amd.com>
Subject: Re: [6.18.y] Fixes for USB4/NVME hotplugging
Date: Sat, 7 Feb 2026 16:20:03 +0100 [thread overview]
Message-ID: <2026020755-stuck-rinse-89ff@gregkh> (raw)
In-Reply-To: <48e48a86-f88a-49e3-a9a0-29f8f43175cf@amd.com>
On Wed, Feb 04, 2026 at 02:06:15PM -0600, Mario Limonciello wrote:
> Hi,
>
> Some of my colleagues (on CC) have been chasing an issue where some
> percentage of the time USB4 NVME enclosures weren't working properly on
> hotplug. They narrowed down the PCIe traces and found that it was caused by
> a race condition between multiple drivers shortly after link training.
>
> This issue traces back a while, they reproduced it as far back as 6.14, but
> that's mostly because the hardware it was first reproduced on had graphics
> enabled in 6.14. Given the root cause, I strongly hardware enabled with
> earlier kernels would also reproduce it. Nonetheless the issue has actually
> already been fixed though by a series that went into 6.19.
>
> commit a2f1e22390ac ("PCI/ERR: Ensure error recoverability at all times")
> commit 383d89699c50 ("treewide: Drop pci_save_state() after
> pci_restore_state()")
>
> Can we bring this back to 6.18.y too?
>
> If any questions about the methodology or details, they can add more.
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2026-02-07 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 20:06 [6.18.y] Fixes for USB4/NVME hotplugging Mario Limonciello
2026-02-07 15:20 ` Greg KH [this message]
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=2026020755-stuck-rinse-89ff@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Alexander.Kovacs@amd.com \
--cc=Renjith.Pananchikkal@amd.com \
--cc=mario.limonciello@amd.com \
--cc=stable@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