https://bugzilla.kernel.org/show_bug.cgi?id=216473

--- Comment #4 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
Your system definitely has some ASL that isn't called for the AMD paths that is
called for the Microsoft path.

On the way "down", the Microsoft side calls:

Screen Off:
                            WECM (0x6F, 0xEC)
                            M000 (0x3E03)
                            M460 ("    Return (0x00)\n", Zero, Zero, Zero,
Zero, Zero, Zero)
                            \_SB.PCI0.LPC0.EC0.PLED = One
                            \_SB.PCI0.LPC0.EC0.G140 = Zero
                            \_SB.PCI0.LPC0.EC0.G155 = Zero
                            Return (Zero)

Modern Standby Entry:
                            \_SB.PCI0.LPC0.EC0.ECMO = One
                            M000 (0x3E07)
                            M460 ("    Return (0x00)\n", Zero, Zero, Zero,
Zero, Zero, Zero)
                            Return (Zero)

On AMD path it calls:

Screen Off:
                            M000 (0x3E02)
                            M460 ("    Return (0x00)\n", Zero, Zero, Zero,
Zero, Zero, Zero)
                            Return (Zero)

Modern Standby entry:

                            M000 (0x3E04)
                            M460 ("    Return (0x00)\n", Zero, Zero, Zero,
Zero, Zero, Zero)
                            Return (Zero)

So with the patches from #216101 can you please apply
acpi.prefer_microsoft_guid=1?
I noticed you used s2idle.prefer_microsoft_guid=1 in the other bug.

Share an updated dmesg log with the same other debug parameters.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to