Suspend to RAM does not work

English Install/Boot/Login
1

Hi,
I am currently assembling a new desktop computer and have installed Leap 15.6. All running smoothly except for when I try to make it “sleep” it does not comply. The screen goes dark but the fans are still spinning, the power LED stays on, remote SSH access has been terminated. So the CPU appears to be sleeping.

When I press a key on the keyboard, the computer seems to wake up but not always into the GUI. What the screen shows is somewhat different each time. If it shows the GUI (KDE) login screen, every interaction is extremely slow like typing the password and every mouse click after that.
When it does not enter the GUI, I get a console login screen which is not slow and workable, so I can reboot.

I had a look at the computer’s logfile and the following line caught my eye:

amdgpu 0000:05:00.0: amdgpu: Power consumption will be higher as BIOS has not been configured for suspend-to-idle. To use suspend-to-idle change the sleep mode in BIOS setup.

I checked the BIOS but I could not find anything relevant. By the way, the hardware is a Gigabyte B550M K motherboard with an AMD Ryzen 7 5700G CPU with integrated graphics.

The file /sys/power/mem_sleep has the line “s2idle [deep]”, so I understand the computer should go into a suspend-to-ram sleep state. Why is there the “suspend-to-idle” complaint in the log?

On a different desktop computer with the same chipset, also running Leap 15.6 and otherwise mostly the same configuration, I do not have any issues with sleep at all.

What can I do? Any tip would be appreciated. Thanks.

2

Reboot, try to suspend, upload to the https://paste.opensuse.org/ the full output of the command run as root

journalctl -b --no-pager --full
3

Done and uploaded as instructed.

4

Where’s the online link to the output?

5

Sorry, missed that one. Hope, that is correct.
https://paste.opensuse.org/pastes/b1f6f16d975c

6

The system attempts to suspend;

Jun 22 17:02:59 maike-linux systemd-sleep[15716]: Entering sleep state 'suspend'...
Jun 22 17:02:59 maike-linux kernel: PM: suspend entry (deep)

but something wakes it up before suspend can complete

Jun 22 17:03:02 maike-linux kernel: Disabling non-boot CPUs ...
Jun 22 17:03:02 maike-linux kernel: Wakeup pending. Abort CPU freeze
Jun 22 17:03:02 maike-linux kernel: Non-boot CPUs are not disabled
Jun 22 17:03:02 maike-linux kernel: ACPI: PM: Waking up from system sleep state S3

and apparently something goes wrong with GPU

Jun 22 17:03:02 maike-linux kernel: amdgpu 0000:05:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx test failed (-110)
Jun 22 17:03:02 maike-linux kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <gfx_v9_0> failed -110
Jun 22 17:03:02 maike-linux kernel: amdgpu 0000:05:00.0: amdgpu: amdgpu_device_ip_resume failed (-110).

You can try disabling wake up for devices one by one. See

/proc/acpi/wakeup

Irrespectively, there is obviously a problem with GPU during such “incomplete suspend”.

7

Thanks. Agreed, there seems to be GPU problem. Is only the IGP in the CPU at fault, or could be the motherboard involved, too. Should I try a separate graphics card? But first I try the /proc/acpi/wakeup disabling devices option.

8

In /proc/acpi/wakeup I found the line “serio0:serio0” which, according to Google, pointed to a serial device like a PS/2 keyboard. Indeed, I had used an old keyboard during the installation/setup phase of this computer. When I swapped that against a USB keyboard the “serio0” line had disappeared, and, lo and behold, the computer is going to sleep nicely and waking up without any issues. Problem sorted. Thanks for your assistance.

9

I remember my desktop had BIOS setting to enable/disable wakeup by keyboard and mouse.