From: Mario Limonciello <mario.limonciello@amd.com>
To: Joyful Lee <joy@joyfullee.me>, platform-driver-x86@vger.kernel.org
Cc: "Shyam Sundar S K" <Shyam-sundar.S-k@amd.com>,
"Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
linux-pci@vger.kernel.org, "Bjorn Helgaas" <bhelgaas@google.com>,
linux-acpi@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] ASUS ProArt PX13 HN7306WU: amd_pmc s2idle S0ix corrupts AMD 1022:150b root port, NVIDIA dGPU returns header type 7f
Date: Thu, 2 Apr 2026 14:58:04 -0500 [thread overview]
Message-ID: <a935b2e3-e11d-47ec-af47-7eb7e86a9dd0@amd.com> (raw)
In-Reply-To: <CADj6jrgK+sRXoNaYH90Rdc8DYEFK2iSF4vkJC=KE4UaZ73y67A@mail.gmail.com>
On 4/2/26 1:49 PM, Joyful Lee wrote:
> [You don't often get email from joy@joyfullee.me. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> (LLM garbage)
>
> So far, every path that reaches real S0ix through the normal 0x03/arg=1 PMC
> flow still corrupts the root port, while every path that avoids real S0ix keeps
> the root port healthy.
>
> (LLM garbage)
What does corruption mean in your context? Because I don't have any
idea what a root port being corrupted means.
Basically I don't trust a single assumption that was made by that LLM.
Can you please get an amd-s2idle report from an unpatched mainline kernel:
https://origin.kernel.org/doc/html/next/arch/x86/amd-debugging.html#s2idle-debugging-tool
*Then* let's talk like people used to before LLMs came into the picture
about your problem.
next prev parent reply other threads:[~2026-04-02 19:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 18:49 [BUG] ASUS ProArt PX13 HN7306WU: amd_pmc s2idle S0ix corrupts AMD 1022:150b root port, NVIDIA dGPU returns header type 7f Joyful Lee
2026-04-02 19:58 ` Mario Limonciello [this message]
2026-04-02 20:59 ` Joyful Lee
2026-04-02 21:14 ` Mario Limonciello
2026-04-02 21:32 ` Joyful Lee
2026-04-03 13:23 ` Mario Limonciello
2026-04-03 14:11 ` Joyful Lee
2026-04-03 14:24 ` Mario Limonciello
2026-04-03 16:19 ` Joyful Lee
2026-04-03 16:48 ` Mario Limonciello
2026-04-03 18:04 ` Bjorn Helgaas
2026-04-03 18:41 ` Mario Limonciello
2026-04-03 19:10 ` Bjorn Helgaas
2026-04-03 19:11 ` Mario Limonciello
2026-04-03 19:07 ` Joyful Lee
2026-04-03 20:02 ` Mario Limonciello
2026-04-03 20:47 ` Joyful Lee
2026-04-03 21:05 ` Mario Limonciello
2026-04-03 21:28 ` Mario Limonciello
2026-04-05 7:16 ` Lukas Wunner
2026-04-05 7:05 ` Lukas Wunner
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=a935b2e3-e11d-47ec-af47-7eb7e86a9dd0@amd.com \
--to=mario.limonciello@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=bhelgaas@google.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=joy@joyfullee.me \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.