From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Freeman Z <SHD-ISAC@outlook.com>
Cc: "Kovacs, Alexander" <Alexander.Kovacs@amd.com>,
"Limonciello, Mario" <Mario.Limonciello@amd.com>,
"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>,
"S, Sanath" <Sanath.S@amd.com>,
"Natikar, Basavaraj" <Basavaraj.Natikar@amd.com>,
"Martinez, Juan" <Juan.Martinez@amd.com>
Subject: Re: [BUG] PCI/USB4: AMD Phoenix 1022:14ef runtime suspend prevents JHL9480 downstream enumeration
Date: Fri, 25 Sep 2026 13:50:41 +0200 [thread overview]
Message-ID: <20260925115041.GX106095@black.igk.intel.com> (raw)
In-Reply-To: <TYCPR01MB1092798A529672215ACC586BA96802@TYCPR01MB10927.jpnprd01.prod.outlook.com>
Hi,
On Fri, Sep 25, 2026 at 11:31:55AM +0000, Freeman Z wrote:
> Hi Mika, Alex and Mario,
>
> I tested v7.3-rc4 with the following Ubuntu SAUCE patch from
> Chia-Lin Kao (AceLan) at Canonical:
>
> thunderbolt: Fix PCIe device enumeration with delayed rescan
>
> Ubuntu SRU posting:
> https://lists.ubuntu.com/archives/kernel-team/2026-April/166926.html
>
> Launchpad:
> https://bugs.launchpad.net/bugs/2139572
>
> The Ubuntu posting says this was cherry-picked from the corresponding
> upstream submission:
>
> https://lore.kernel.org/lkml/20260121060857.237777-1-acelan.kao@canonical.com/T/#u
>
> The patch schedules a delayed pci_rescan_bus() 300 ms after the
> Thunderbolt PCIe tunnel has been activated, to recover devices that
> pciehp did not enumerate.
Oh I remember that. It's a horrible hack that is never going to applied.
Based on this we now know why it "works" in Ubuntu. Thanks for finding it.
I think the real issue is that the PME is not propagated as it should,
either missing wake or something else but that's what the AMD folks can
hopefully help us to figure out.
next prev parent reply other threads:[~2026-09-25 11:50 UTC|newest]
Thread overview: 41+ 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
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 [this message]
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-10-09 14:54 ` Freeman Z
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=20260925115041.GX106095@black.igk.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=Alexander.Kovacs@amd.com \
--cc=Basavaraj.Natikar@amd.com \
--cc=Juan.Martinez@amd.com \
--cc=Mario.Limonciello@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=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