You are not logged in.

#1 2021-04-07 06:54:03

temp-cb
Member
Registered: 2021-04-07
Posts: 4

Lenovo Ideapad 5 14are05 S3 Suspend Patch Does Not Work Anymore

Ever since I upgraded to kernel 5.11, the laptop won't suspend properly anymore. There are no issues going INTO suspend (can see a slow pulsing light). However, the issue arises when I wake the laptop up. The screen turns glitchy, full of static colors, and I cannot log back in. It's totally unresponsive.

I have to force-shutdown the laptop and boot again.

The S3 patch (https://wiki.archlinux.org/index.php/Le … _5_14are05) still works for 5.10. I had to downgrade to the LTS version.

Any idea on how to make the patch work with kernels>=5.11?

Last edited by temp-cb (2021-04-08 02:37:59)

Offline

#2 2021-04-11 07:16:05

yugge
Member
Registered: 2021-04-11
Posts: 1

Re: Lenovo Ideapad 5 14are05 S3 Suspend Patch Does Not Work Anymore

I can confirm as I have the same issue. Following this thread if someone comes up with a fix.

One thing I can add is that at times the glitches goes away and it shows my login screen with the clock set to the time of suspend, I can still move my cursor and see it move, but I can't interact with anything. Looking at kern.log it is complaining about the amdgpu not being able to resume, so it might be a graphical issue?

kern.log snippet:

Apr  9 02:32:01 adminicle kernel: [  121.487088] PM: suspend entry (deep)
Apr  9 02:32:01 adminicle kernel: [  121.491958] Filesystems sync: 0.004 seconds
Apr  9 02:32:15 adminicle kernel: [  121.618611] Freezing user space processes ... (elapsed 0.002 seconds) done.
Apr  9 02:32:15 adminicle kernel: [  121.620999] OOM killer disabled.
Apr  9 02:32:15 adminicle kernel: [  121.621000] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Apr  9 02:32:15 adminicle kernel: [  121.622405] printk: Suspending console(s) (use no_console_suspend to debug)
Apr  9 02:32:15 adminicle kernel: [  125.652442] amdgpu: cp queue preemption time out.
Apr  9 02:32:15 adminicle kernel: [  125.822971] ACPI: EC: interrupt blocked
Apr  9 02:32:15 adminicle kernel: [  125.880104] ACPI: Preparing to enter system sleep state S3
Apr  9 02:32:15 adminicle kernel: [  125.880779] ACPI: EC: event blocked
Apr  9 02:32:15 adminicle kernel: [  125.880781] ACPI: EC: EC stopped
Apr  9 02:32:15 adminicle kernel: [  125.880782] PM: Saving platform NVS memory
Apr  9 02:32:15 adminicle kernel: [  125.881048] Disabling non-boot CPUs ...
Apr  9 02:32:15 adminicle kernel: [  125.881978] IRQ 33: no longer affine to CPU1
Apr  9 02:32:15 adminicle kernel: [  125.881998] IRQ 41: no longer affine to CPU1
Apr  9 02:32:15 adminicle kernel: [  125.882007] IRQ 52: no longer affine to CPU1
Apr  9 02:32:15 adminicle kernel: [  125.882015] IRQ 74: no longer affine to CPU1
Apr  9 02:32:15 adminicle kernel: [  125.882023] IRQ 80: no longer affine to CPU1
Apr  9 02:32:15 adminicle kernel: [  125.883054] smpboot: CPU 1 is now offline
Apr  9 02:32:15 adminicle kernel: [  125.884892] IRQ 45: no longer affine to CPU2
Apr  9 02:32:15 adminicle kernel: [  125.884911] IRQ 47: no longer affine to CPU2
Apr  9 02:32:15 adminicle kernel: [  125.884919] IRQ 51: no longer affine to CPU2
Apr  9 02:32:15 adminicle kernel: [  125.884942] IRQ 84: no longer affine to CPU2
Apr  9 02:32:15 adminicle kernel: [  125.885969] smpboot: CPU 2 is now offline
Apr  9 02:32:15 adminicle kernel: [  125.887281] IRQ 36: no longer affine to CPU3
Apr  9 02:32:15 adminicle kernel: [  125.888366] smpboot: CPU 3 is now offline
Apr  9 02:32:15 adminicle kernel: [  125.891023] smpboot: CPU 4 is now offline
Apr  9 02:32:15 adminicle kernel: [  125.893837] smpboot: CPU 5 is now offline
Apr  9 02:32:15 adminicle kernel: [  125.895195] ACPI: Low-level resume complete
Apr  9 02:32:15 adminicle kernel: [  125.895236] ACPI: EC: EC started
Apr  9 02:32:15 adminicle kernel: [  125.895237] PM: Restoring platform NVS memory
Apr  9 02:32:15 adminicle kernel: [  125.895511] LVT offset 0 assigned for vector 0x400
Apr  9 02:32:15 adminicle kernel: [  125.895977] Enabling non-boot CPUs ...
Apr  9 02:32:15 adminicle kernel: [  125.896018] x86: Booting SMP configuration:
Apr  9 02:32:15 adminicle kernel: [  125.896019] smpboot: Booting Node 0 Processor 1 APIC 0x1
Apr  9 02:32:15 adminicle kernel: [  125.896128] microcode: CPU1: patch_level=0x08600106
Apr  9 02:32:15 adminicle kernel: [  125.898322] ACPI: \_SB_.PLTF.C001: Found 3 idle states
Apr  9 02:32:15 adminicle kernel: [  125.898602] CPU1 is up
Apr  9 02:32:15 adminicle kernel: [  125.898627] smpboot: Booting Node 0 Processor 2 APIC 0x2
Apr  9 02:32:15 adminicle kernel: [  125.899076] microcode: CPU2: patch_level=0x08600106
Apr  9 02:32:15 adminicle kernel: [  125.901298] ACPI: \_SB_.PLTF.C002: Found 3 idle states
Apr  9 02:32:15 adminicle kernel: [  125.901626] CPU2 is up
Apr  9 02:32:15 adminicle kernel: [  125.901657] smpboot: Booting Node 0 Processor 3 APIC 0x4
Apr  9 02:32:15 adminicle kernel: [  125.901951] microcode: CPU3: patch_level=0x08600106
Apr  9 02:32:15 adminicle kernel: [  125.904145] ACPI: \_SB_.PLTF.C003: Found 3 idle states
Apr  9 02:32:15 adminicle kernel: [  125.904404] CPU3 is up
Apr  9 02:32:15 adminicle kernel: [  125.904429] smpboot: Booting Node 0 Processor 4 APIC 0x5
Apr  9 02:32:15 adminicle kernel: [  125.904678] microcode: CPU4: patch_level=0x08600106
Apr  9 02:32:15 adminicle kernel: [  125.906981] ACPI: \_SB_.PLTF.C004: Found 3 idle states
Apr  9 02:32:15 adminicle kernel: [  125.907225] CPU4 is up
Apr  9 02:32:15 adminicle kernel: [  125.907246] smpboot: Booting Node 0 Processor 5 APIC 0x6
Apr  9 02:32:15 adminicle kernel: [  125.907502] microcode: CPU5: patch_level=0x08600106
Apr  9 02:32:15 adminicle kernel: [  125.909754] ACPI: \_SB_.PLTF.C005: Found 3 idle states
Apr  9 02:32:15 adminicle kernel: [  125.910014] CPU5 is up
Apr  9 02:32:15 adminicle kernel: [  125.910638] ACPI: Waking up from system sleep state S3
Apr  9 02:32:15 adminicle kernel: [  125.917314] ACPI: EC: interrupt unblocked
Apr  9 02:32:15 adminicle kernel: [  126.181858] ACPI: EC: event unblocked
Apr  9 02:32:15 adminicle kernel: [  126.182357] pci 0000:00:00.2: can't derive routing for PCI INT A
Apr  9 02:32:15 adminicle kernel: [  126.182361] pci 0000:00:00.2: PCI INT A: no GSI
Apr  9 02:32:15 adminicle kernel: [  126.287614] [drm] Wait for DMUB auto-load failed: 3
Apr  9 02:32:15 adminicle kernel: [  126.287637] [drm] DMUB hardware initialized: version=0x01000000
Apr  9 02:32:15 adminicle kernel: [  126.295329] nvme nvme0: Shutdown timeout set to 8 seconds
Apr  9 02:32:15 adminicle kernel: [  126.310494] nvme nvme0: 16/0/0 default/read/poll queues
Apr  9 02:32:15 adminicle kernel: [  126.445571] amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
Apr  9 02:32:15 adminicle kernel: [  126.445577] amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Apr  9 02:32:15 adminicle kernel: [  126.445579] amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Apr  9 02:32:15 adminicle kernel: [  126.445580] amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Apr  9 02:32:15 adminicle kernel: [  126.445581] amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Apr  9 02:32:15 adminicle kernel: [  126.445582] amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Apr  9 02:32:15 adminicle kernel: [  126.445583] amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Apr  9 02:32:15 adminicle kernel: [  126.445584] amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Apr  9 02:32:15 adminicle kernel: [  126.445585] amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
Apr  9 02:32:15 adminicle kernel: [  126.445587] amdgpu 0000:04:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
Apr  9 02:32:15 adminicle kernel: [  126.445588] amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
Apr  9 02:32:15 adminicle kernel: [  126.445589] amdgpu 0000:04:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
Apr  9 02:32:15 adminicle kernel: [  126.445591] amdgpu 0000:04:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
Apr  9 02:32:15 adminicle kernel: [  126.445592] amdgpu 0000:04:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
Apr  9 02:32:15 adminicle kernel: [  126.445593] amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
Apr  9 02:32:15 adminicle kernel: [  127.467790] amdgpu 0000:04:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on gfx (-110).
Apr  9 02:32:15 adminicle kernel: [  127.468082] [drm:amdgpu_device_delayed_init_work_handler [amdgpu]] *ERROR* ib ring test failed (-110).
Apr  9 02:32:15 adminicle kernel: [  127.471871] acpi LNXPOWER:08: Turning OFF
Apr  9 02:32:15 adminicle kernel: [  127.471919] acpi LNXPOWER:07: Turning OFF
Apr  9 02:32:15 adminicle kernel: [  127.471971] acpi LNXPOWER:05: Turning OFF
Apr  9 02:32:15 adminicle kernel: [  127.472729] OOM killer enabled.
Apr  9 02:32:15 adminicle kernel: [  127.472731] Restarting tasks ... done.
Apr  9 02:32:15 adminicle kernel: [  127.474762] thermal thermal_zone1: failed to read out thermal zone (-61)
Apr  9 02:32:15 adminicle kernel: [  127.621336] [drm] Failed to add display topology, DTM TA is not initialized.
Apr  9 02:32:15 adminicle kernel: [  127.731006] PM: suspend exit
Apr  9 02:32:21 adminicle kernel: [  132.775396] [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out!
Apr  9 02:32:21 adminicle kernel: [  132.973281] wlo1: authenticate with 14:59:c0:57:85:86
Apr  9 02:32:21 adminicle kernel: [  132.977756] wlo1: send auth to 14:59:c0:57:85:86 (try 1/3)
Apr  9 02:32:21 adminicle kernel: [  133.005333] wlo1: authenticated
Apr  9 02:32:21 adminicle kernel: [  133.011405] wlo1: associate with 14:59:c0:57:85:86 (try 1/3)
Apr  9 02:32:21 adminicle kernel: [  133.015217] wlo1: RX AssocResp from 14:59:c0:57:85:86 (capab=0x1411 status=0 aid=3)
Apr  9 02:32:21 adminicle kernel: [  133.020952] wlo1: associated
Apr  9 02:32:21 adminicle kernel: [  133.041375] IPv6: ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready
Apr  9 02:32:21 adminicle kernel: [  133.097982] wlo1: Limiting TX power to 17 (20 - 3) dBm as advertised by 14:59:c0:57:85:86
Apr  9 02:32:24 adminicle kernel: [  136.612826] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=1807, emitted seq=1810
Apr  9 02:32:24 adminicle kernel: [  136.613169] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process  pid 0 thread  pid 0
Apr  9 02:32:24 adminicle kernel: [  136.613466] amdgpu 0000:04:00.0: amdgpu: GPU reset begin!
Apr  9 02:32:24 adminicle kernel: [  136.847003] amdgpu 0000:04:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
Apr  9 02:32:24 adminicle kernel: [  136.856640] [drm] free PSP TMR buffer
Apr  9 02:32:25 adminicle kernel: [  136.889726] amdgpu 0000:04:00.0: amdgpu: MODE2 reset
Apr  9 02:32:25 adminicle kernel: [  136.889816] amdgpu 0000:04:00.0: amdgpu: GPU reset succeeded, trying to resume
Apr  9 02:32:25 adminicle kernel: [  136.890014] [drm] PCIE GART of 1024M enabled (table at 0x000000F400900000).
Apr  9 02:32:25 adminicle kernel: [  136.890284] [drm] PSP is resuming...
Apr  9 02:32:25 adminicle kernel: [  136.910139] [drm] reserve 0x400000 from 0xf41f800000 for PSP TMR
Apr  9 02:32:25 adminicle kernel: [  137.340661] amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
Apr  9 02:32:25 adminicle kernel: [  137.341742] amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
Apr  9 02:32:25 adminicle kernel: [  137.343705] [drm] kiq ring mec 2 pipe 1 q 0
Apr  9 02:32:25 adminicle kernel: [  137.356528] [drm] DMUB hardware initialized: version=0x01000000
Apr  9 02:32:25 adminicle kernel: [  137.633365] [drm] Failed to add display topology, DTM TA is not initialized.
Apr  9 02:32:25 adminicle kernel: [  137.674155] [drm] VCN decode and encode initialized successfully(under DPG Mode).
Apr  9 02:32:25 adminicle kernel: [  137.674711] [drm] JPEG decode initialized successfully.
Apr  9 02:32:25 adminicle kernel: [  137.674715] amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
Apr  9 02:32:25 adminicle kernel: [  137.674718] amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Apr  9 02:32:25 adminicle kernel: [  137.674719] amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Apr  9 02:32:25 adminicle kernel: [  137.674720] amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Apr  9 02:32:25 adminicle kernel: [  137.674721] amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Apr  9 02:32:25 adminicle kernel: [  137.674722] amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Apr  9 02:32:25 adminicle kernel: [  137.674723] amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Apr  9 02:32:25 adminicle kernel: [  137.674724] amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Apr  9 02:32:25 adminicle kernel: [  137.674725] amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
Apr  9 02:32:25 adminicle kernel: [  137.674726] amdgpu 0000:04:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
Apr  9 02:32:25 adminicle kernel: [  137.674727] amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
Apr  9 02:32:25 adminicle kernel: [  137.674728] amdgpu 0000:04:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
Apr  9 02:32:25 adminicle kernel: [  137.674729] amdgpu 0000:04:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
Apr  9 02:32:25 adminicle kernel: [  137.674730] amdgpu 0000:04:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
Apr  9 02:32:25 adminicle kernel: [  137.674731] amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
Apr  9 02:32:25 adminicle kernel: [  137.680196] amdgpu 0000:04:00.0: amdgpu: recover vram bo from shadow start
Apr  9 02:32:25 adminicle kernel: [  137.680203] amdgpu 0000:04:00.0: amdgpu: recover vram bo from shadow done
Apr  9 02:32:25 adminicle kernel: [  137.680245] amdgpu 0000:04:00.0: amdgpu: GPU reset(1) succeeded!
Apr  9 02:32:25 adminicle kernel: [  137.711082] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* got no status for stream 00000000eacd9406 on acrtc00000000d7a22db5
Apr  9 02:32:57 adminicle kernel: [  169.287357] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* got no status for stream 00000000eacd9406 on acrtc00000000d7a22db5

Offline

#3 2021-04-12 07:56:36

temp-cb
Member
Registered: 2021-04-07
Posts: 4

Re: Lenovo Ideapad 5 14are05 S3 Suspend Patch Does Not Work Anymore

Occasionally, something similar happens to me as well. However, I've never been able to move the mouse. My display manager, SDDM, shows up, but it's like it's behind a dark veil. Totally unresponsive to any input.

Here, someone with a 4700U is facing an S4 (hibernation) issue—https://bbs.archlinux.org/viewtopic.php?id=264044

I hope this issue is fixed in 5.12.

Last edited by temp-cb (2021-04-12 07:56:58)

Offline

#4 Yesterday 02:37:17

devmrfitz
Member
Registered: 2021-01-13
Posts: 54

Re: Lenovo Ideapad 5 14are05 S3 Suspend Patch Does Not Work Anymore

Offline

#5 Yesterday 13:13:30

korikori
Member
Registered: 2020-09-30
Posts: 4

Re: Lenovo Ideapad 5 14are05 S3 Suspend Patch Does Not Work Anymore

The issue with resuming from suspend on 5.11.x and later kernels is discussed here: https://bugs.archlinux.org/task/69764 - it is actually a GPU driver problem, and the S3 suspend mode is still available (if tables are patched). The most common workaround has been to fall back to linux-lts, but there is also a working kernel patch in that bug report.

Unfortunately, in addition to this bug, the most recent 5.11 and 5.10 versions all suffer from another issue - the S3 sleep mode is not available at all (even with the ACPI tables patch). You can easily tell the difference between the behavior that you have described as now, the power light no longer pulses, and worst of all, if you leave your laptop suspended for the night, its battery will be fully drained by morning.

I had to downgrade to 5.10.25 via https://archive.archlinux.org/packages/l/linux-lts/ to resolve this.

devmrfitz, your issue may be related to the lack of S3 in the most recent kernel version, so please try going back to 5.10.25 and see if you can patch your tables there.

Last edited by korikori (Yesterday 13:22:57)

Offline

#6 Today 02:45:13

devmrfitz
Member
Registered: 2021-01-13
Posts: 54

Re: Lenovo Ideapad 5 14are05 S3 Suspend Patch Does Not Work Anymore

@korikori I'm already using LTS. Do I still have to downgrade or is there a solution available? Also, can we expect the next kernel update to have a solution for this?

Offline

#7 Today 09:59:05

korikori
Member
Registered: 2020-09-30
Posts: 4

Re: Lenovo Ideapad 5 14are05 S3 Suspend Patch Does Not Work Anymore

devmrfitz wrote:

@korikori I'm already using LTS. Do I still have to downgrade or is there a solution available? Also, can we expect the next kernel update to have a solution for this?

Yes, this ocurred to me on LTS again with the most recent version - 5.10.29-1 - or possibly even earlier, which is why I chose to go back a few versions to 5.10.25-1. You can grab an older LTS kernel from https://archive.archlinux.org/packages/l/linux-lts/ (you probably need a matching linux-lts-headers too).

I still haven't found too much other mentions of the same issue, and I also haven't dug up further than confirming that downgrading resolves it, which is why I haven't opened a bug report yet. I looked through the last few LTS kernels' changelogs, but didn't find anything obvious that could cause this.

Offline

#8 Today 11:46:03

temp-cb
Member
Registered: 2021-04-07
Posts: 4

Re: Lenovo Ideapad 5 14are05 S3 Suspend Patch Does Not Work Anymore

@korikori Thanks for that information!

This situation with lack of S3 support is a pain. I just want something that works; I don't want to go through hoops, just to get the suspend feature working!

Offline

Board footer

Powered by FluxBB