From: Mario Limonciello <mario.limonciello@amd.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>,
Freeman Z <SHD-ISAC@outlook.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"westeri@kernel.org" <westeri@kernel.org>,
"andreas.noever@gmail.com" <andreas.noever@gmail.com>,
"YehezkelShB@gmail.com" <yehezkelshb@gmail.com>,
"rafael@kernel.org" <rafael@kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Sanath S <Sanath.S@amd.com>,
Basavaraj Natikar <Basavaraj.Natikar@amd.com>,
"Kovacs, Alexander" <Alexander.Kovacs@amd.com>
Subject: Re: [BUG] PCI/USB4: AMD Phoenix 1022:14ef runtime suspend prevents JHL9480 downstream enumeration
Date: Mon, 21 Sep 2026 10:24:52 -0500 [thread overview]
Message-ID: <f8b929da-b4ae-48ae-9667-3eb93aa0a4bd@amd.com> (raw)
In-Reply-To: <20260921050450.GM106095@black.igk.intel.com>
+Alex K
On 9/21/26 00:04, Mika Westerberg wrote:
> Hi,
>
> Adding AMD folks in case this is known issue.
>
> On Sat, Sep 19, 2026 at 12:39:37PM +0000, Freeman Z wrote:
>> Hello,
>>
>> I am seeing a reproducible USB4/PCIe runtime-PM problem on an ASUS ROG
>> Flow X13 GV302XV (Ryzen 9 7940HS / Phoenix) with a Kensington SD5000T5
>> EQ Thunderbolt 5 dock connected to the laptop's USB4 host port.
>>
>> The failure is reproducible with the official Arch Linux Live ISO using
>> Arch's stock `linux` kernel:
>>
>> 7.2.2-arch1-1
>>
>> I have not yet tested a self-built kernel.org mainline/vanilla kernel.
>> I can test patches, or collect additional traces if requested.
>
> Can you provide full dmesg with "thunderbolt.dyndbg=+p" in the kernel
> command line?
>
> With the below steps (following your description):
>
> 0. Drop all non-standard command line options except the above.
> 1. Boot the system up, nothing connected.
> 2. Once up let the TB and the related PCIe root ports enter D3cold (don't
> run lspci it will wake them up but you can look at the runtime status that
> they are all suspended).
> 3. Plug in the dock.
>
> We should see in the dmesg the PME if it works as expected. If not then it
> may be that there is something wrong with the wakeup path.
There was something like this that was reported in the past, but it was
a race condition of some sort. It ended up being fixed by a non-obvious
optimization (I forget the specific commit).
But it was definitely older than 7.2, so it sounds like it might have
regressed again.
next prev parent reply other threads:[~2026-09-21 15:24 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 12:39 [BUG] PCI/USB4: AMD Phoenix 1022:14ef runtime suspend prevents JHL9480 downstream enumeration Freeman Z
2026-09-21 5:04 ` Mika Westerberg
2026-09-21 15:24 ` Mario Limonciello [this message]
2026-09-22 16:40 ` Freeman Z
2026-09-22 17:02 ` Kovacs, Alexander
2026-09-22 17:03 ` Kovacs, Alexander
2026-09-22 19:54 ` Kovacs, Alexander
2026-09-22 20:00 ` Mario Limonciello
2026-09-23 11:51 ` Freeman Z
2026-09-23 12:26 ` Kovacs, Alexander
2026-09-23 12:35 ` Mario Limonciello
2026-09-23 19:37 ` Kovacs, Alexander
2026-09-24 7:18 ` Freeman Z
2026-09-25 5:27 ` Mika Westerberg
2026-09-25 9:38 ` Freeman Z
2026-09-25 11:31 ` Freeman Z
2026-09-25 11:50 ` Mika Westerberg
2026-09-25 14:10 ` Mario Limonciello
2026-09-25 15:12 ` Freeman Z
2026-09-25 15:24 ` Mario Limonciello
2026-09-25 15:48 ` Freeman Z
2026-10-01 14:54 ` Kovacs, Alexander
2026-10-01 18:28 ` Freeman Z
2026-10-05 14:35 ` Kovacs, Alexander
2026-10-05 15:39 ` Freeman Z
2026-10-05 17:01 ` Kovacs, Alexander
2026-10-05 17:10 ` Freeman Z
2026-10-06 14:33 ` Kovacs, Alexander
2026-10-06 14:37 ` Mario Limonciello
2026-10-06 16:33 ` Freeman Z
2026-10-06 17:12 ` Kovacs, Alexander
2026-10-06 18:45 ` Freeman Z
2026-10-06 19:18 ` Kovacs, Alexander
2026-10-06 19:33 ` Freeman Z
2026-10-06 19:53 ` Kovacs, Alexander
2026-10-06 21:04 ` Freeman Z
2026-10-09 12:47 ` Kovacs, Alexander
2026-10-09 13:02 ` Freeman Z
2026-10-09 13:39 ` Kovacs, Alexander
2026-09-25 14:03 ` Kovacs, Alexander
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=f8b929da-b4ae-48ae-9667-3eb93aa0a4bd@amd.com \
--to=mario.limonciello@amd.com \
--cc=Alexander.Kovacs@amd.com \
--cc=Basavaraj.Natikar@amd.com \
--cc=SHD-ISAC@outlook.com \
--cc=Sanath.S@amd.com \
--cc=andreas.noever@gmail.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael@kernel.org \
--cc=westeri@kernel.org \
--cc=yehezkelshb@gmail.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