[Bug 212333] New: Bisected: 5.11.7 breaks amdgpu resume from S3

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Thu Mar 18 16:48:01 UTC 2021


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

            Bug ID: 212333
           Summary: Bisected: 5.11.7 breaks amdgpu resume from S3
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.11.7
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri at kernel-bugs.osdl.org
          Reporter: timo.valtoaho at gmail.com
        Regression: No

Created attachment 295921
  --> https://bugzilla.kernel.org/attachment.cgi?id=295921&action=edit
Working kernel config with CONFIG_AMD_PMC is not set

After upgrading kernel 5.11.6 => 5.11.7 my Asus Vivobook S14 (Model M433I,
Ryzen 5 4500U), resume from S3 suspend is broken.

Asus has disabled S3 completely, it is not shown in BIOS/UEFI at all. I have
modified DSDT table which works fine providing working S3.

Now, after upgrade, suspend seems to happen just fine but resume gives me
scrambled screen for few seconds, then screen goes completely black and mouse
cursor shows up and is fully alive.I have to do a hard reboot to get away.

Bisecting led to this:

# first bad commit: [084b4f3304f923e39e64216a818a8bbf398dd896] drm/amdgpu: fix
S0ix handling when the CONFIG_AMD_PMC=m

When I change "CONFIG_AMD_PMC is not set" all is working again.
CONFIG_AMD_PMC=y also breaks resume. All of this applies also to 5.12-rc3 which
I tested too.

Also, removing modified DSDT and using S2idle instead of deep, is broken too.
It has never worked on this laptop. Now s2idle suspends, but resume scrambles
screen for few seconds, then it works fine on first round. Suspending second
time will end up on black screen on resume and I have to hard reboot.

OS is Kubuntu 20.10 and firmware is the latest (linux-firmware package v1.195)
taken from next release.

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

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


More information about the dri-devel mailing list