Re: [BUG] ASUS ProArt PX13 HN7306WU: amd_pmc s2idle S0ix corrupts AMD 1022:150b root port, NVIDIA dGPU returns header type 7f

[Mario Limonciello <mario.limonciello@amd.com>]

On 4/3/26 9:11 AM, Joyful Lee wrote:
> On Fri, Apr 3, 2026 at 9:23 AM Mario Limonciello
> <mario.limonciello@amd.com> wrote:
>> To your questions in the original post (again sorry for the original
>> knee jerk reaction):
> 
> No worries. You are right to be skeptical.
> 
>> 1) Yes semantics of how AMD-PMC works are correct for this platform.
>> There are lots of other Strix designs that do everything correctly.
>> 2) Yes; there are FW dependencies that are design specific.
>> 3) There are no quirks for working around this bug you've found right now.
>>
>> I believe this issue you're seeing is likely a platform firmware bug.
>> Whether it's AGESA or it's ASUS firmware is unclear right now.
>>
>> I have not seen this specific symptom you mention on other systems
>> (including AMD reference systems) so I am /leaning/ more on ASUS firmware.
>>
>> I notice that the BIOS you have from ASUS is quite old:
>>
>>   > bios_date| 03/18/2025
>>
>> Any chance there is a BIOS update available?
>> Unfortunately ASUS doesn't always make flashing in Linux easy, but
>> hopefully you can find a way to flash the update if one is available.
> 
> A firmware issue is what I was afraid of. That 2025 BIOS version 316 is
> the latest release for this device. I'll reach out to ASUS to see if
> they have an unreleased version they can send me, but I'm not
> optimistic. I'm still in the return period so I'm feeling a sense of
> urgency to either fix this or move on, but I'd rather try to get it
> working because it's a nice little laptop aside from this issue.

That's really unfortunate to hear.  If I was in your shoes - If not 
solved by the end of the return period I would return the machine and 
purchase one from a vendor that has been testing, fixing BIOS issues and 
supporting Linux.

I'm not going to pick favorites, but Dell, Framework, HP, and Lenovo all 
have offerings that they do this.

> 
> Your first idea that the kernel could be racing the firmware prompted me
> to try a few timing hacks--really just shots in the dark like inserting
> a 2s delay immediately after resume prior to the kernel touching the
> devices--but no luck. While I'm waiting for ASUS, I'm happy to try any
> other ideas you got.

By chance does the BIOS offer access to "AMD PBS" or "AMD CBS" menus? 
If so, there may be an option nestled in there for dGPU D3 behavior.