Impossible to resume after a suspend to ram.

ytterbium · 2021-03-22 10:35:03

Hello,

My computer does not more resume after a suspend (to ram). It worked fine until a few weeks ago. Now when I try to resume, nothing happens : my screen remains black and even the activity led stay off, however my ventilators are on again. I have to do a hard reboot to use again my computer. So I strongly suspect a hardware issue
The log does not show anything interesting, it goes directly from the suspend operation to the reboot.

mars 22 11:06:36 sagittarius systemd[1]: Reached target Sleep.
mars 22 11:06:36 sagittarius systemd[1]: Starting Suspend...
mars 22 11:06:36 sagittarius polkitd[915]: Unregistered Authentication Agent for unix-process:911:17182 (system bus name :1.7, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8) (disconnected from bus)
mars 22 11:06:36 sagittarius systemd-sleep[930]: Suspending system...
-- Boot db1f464b82c14d9080b4fb52e69bf27b --
mars 22 11:10:53 sagittarius kernel: Linux version 5.11.7-arch1-1 (linux@archlinux) (gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP PREEMPT Wed, 17 Mar 2021 16:59:58 +0000
mars 22 11:10:53 sagittarius kernel: Command line: cryptdevice=UUID=41639e2f-c9bc-41e6-827e-74ad233be334:cryptlvm root=/dev/VGroup/Root rw initrd=\amd-ucode.img initrd=\initramfs-linux.img

I tried using the the 5.10 lts kernel but I still get the exact same issue. I do not remember manually upgrading my bios or other microcode since the last time the suspend worked.
I have a Ryzen 5600X and a MSIB550 A pro motherboard.

Do you have any hint to investigate this issue ?

Last edited by ytterbium (2021-03-22 10:37:14)

seth · 2021-03-22 11:55:46

https://01.org/blogs/rzhang/2015/best-p … ate-issues

ytterbium · 2021-03-22 19:15:58

Well, I did not find this document very useful in my case. For my symptoms the only advices I can get are : check if this is a regression ; and fill a bug report. Even if it worked fine some time ago, I could not find a kernel which works now, and I am a bit intimated to fill a bug report to the kernel.
The diagnosis options did not help me: the initcall_debug and no_console_suspend did not raise any more pertinent information in journalctl, and I did not succeed to keep the rtc trace information in dmesg through the reboot.

EDIT:
I finally found how to use the rtc trace. I got in my dmesg the following output :

[    0.658982] PM:   Magic number: 13:232:648
[    0.658984] scsi_host host2: hash matches
[    0.658984] scsi host2: hash matches
[    0.658997] pci 0000:2f:00.3: hash matches

With lspci I get

2f:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller

So does it mean that usb3 driver block my resume ?

Last edited by ytterbium (2021-03-22 20:13:17)

seth · 2021-03-22 22:05:26

Or a device on that controller - did you add one?
Also, ceterum censeo: 3rd link in my signature.

ytterbium · 2021-03-22 22:14:17

I tried to suspend and resume with no usb device connected, only a PS2 keyboard, and still cannot resume. And the Windows fast-boot might have been the solution, but I have no Widows installed, only Arch,

seth · 2021-03-22 22:38:02

Does it lead to the same rtc trace?
Then there's oc also the scsi host (some drive…)

ytterbium · 2021-03-22 23:06:21

In that case the rtc trace is nonexistent : I only have the Magic number and no hash matches.
I do not see what could be the scsi host, my only internal devices are a AMD Radeon and a PCIe4 SSD.

After another suspend/rtc trace, I get an other trace : "memory memory82: hash matches:"

What is oc ? Overclocking ?

seth · 2021-03-23 06:42:58

"of course", sorry i'm lazy :-P

ls /sys/bus/scsi/devices/host2/*/*/block

amdgpu?
Try passing "amdgpu.dc=0 amdgpu.audio=0 amdgpu.dpm=0 amdgpu.aspm=0 amdgpu.runpm=0 amdgpu.bapm=0" to the kernel commandline (usual suspects, but it's more likely one of the pm features - if at all)

Arch Linux

#1 2021-03-22 10:35:03

Impossible to resume after a suspend to ram.

#2 2021-03-22 11:55:46

Re: Impossible to resume after a suspend to ram.

#3 2021-03-22 19:15:58

Re: Impossible to resume after a suspend to ram.

#4 2021-03-22 22:05:26

Re: Impossible to resume after a suspend to ram.

#5 2021-03-22 22:14:17

Re: Impossible to resume after a suspend to ram.

#6 2021-03-22 22:38:02

Re: Impossible to resume after a suspend to ram.

#7 2021-03-22 23:06:21

Re: Impossible to resume after a suspend to ram.

#8 2021-03-23 06:42:58

Re: Impossible to resume after a suspend to ram.

Board footer