Just one last thing - and them I’m outta ideas.
Can you uncomment these two lines in your /etc/systemd/logind.conf - restart & try again.
#HandleLidSwitch=suspend
#HandleLidSwitchExternalPower=suspend
A problem in suspend can also be caused by display issue not able to turn off properly.
Check your installed graphics driver by mhwd -li. If you use proprietary driver, then running ls /sys/class/backlight should display your GPU name, not like a generic acpi naming.
But try @frost19k last advice first before troubleshooting your display.
Thanks @frost19k. Unfortunately, uncommenting those lines has no effect on the issue; it still crashes at supsend. I paste below portions of journalctl that show the laptop hitting suspend s2idle, then … nothing until hard reboot.
Also, here is a link to an issue that I started with the amd kernel folks.
Dec 31 09:51:07 ryzen systemd-logind[458]: Lid closed.
Dec 31 09:51:07 ryzen systemd-logind[458]: Suspending...
Dec 31 09:51:07 ryzen ModemManager[515]: <info> [sleep-monitor] system is about to suspend
Dec 31 09:51:07 ryzen NetworkManager[455]: <info> [1640969467.6084] manager: sleep: sleep requested (sleeping: no enabled: yes)
Dec 31 09:51:07 ryzen NetworkManager[455]: <info> [1640969467.6085] manager: NetworkManager state is now ASLEEP
Dec 31 09:51:07 ryzen NetworkManager[455]: <info> [1640969467.6087] device (wlo1): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Dec 31 09:51:07 ryzen dbus-daemon[454]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.3' (uid=0 pid=455 comm="/usr/bin/NetworkManager --no-daemon ")
Dec 31 09:51:07 ryzen systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec 31 09:51:07 ryzen dbus-daemon[454]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec 31 09:51:07 ryzen systemd[1]: Started Network Manager Script Dispatcher Service.
Dec 31 09:51:07 ryzen audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 31 09:51:07 ryzen kernel: audit: type=1130 audit(1640969467.616:102): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 31 09:51:07 ryzen kernel: wlo1: deauthenticating from 94:83:c4:0d:56:c5 by local choice (Reason: 3=DEAUTH_LEAVING)
Dec 31 09:51:07 ryzen kernel: rtw_8821ce 0000:01:00.0: sta 94:83:c4:0d:56:c5 with macid 0 left
Dec 31 09:51:07 ryzen wpa_supplicant[732]: wlo1: CTRL-EVENT-DISCONNECTED bssid=94:83:c4:0d:56:c5 reason=3 locally_generated=1
Dec 31 09:51:07 ryzen wpa_supplicant[732]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Dec 31 09:51:07 ryzen NetworkManager[455]: <info> [1640969467.7944] device (wlo1): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Dec 31 09:51:07 ryzen NetworkManager[455]: <info> [1640969467.8131] dhcp4 (wlo1): canceled DHCP transaction
Dec 31 09:51:07 ryzen NetworkManager[455]: <info> [1640969467.8131] dhcp4 (wlo1): state changed bound -> terminated
Dec 31 09:51:07 ryzen NetworkManager[455]: <info> [1640969467.8144] device (wlo1): set-hw-addr: set MAC address to B6:3B:C1:B2:6A:EC (scanning)
Dec 31 09:51:07 ryzen kernel: rtw_8821ce 0000:01:00.0: stop vif 14:13:33:7e:09:53 on port 0
Dec 31 09:51:07 ryzen gnome-shell[1237]: An active wireless connection, in infrastructure mode, involves no access point?
Dec 31 09:51:08 ryzen kernel: rtw_8821ce 0000:01:00.0: start vif b6:3b:c1:b2:6a:ec on port 0
Dec 31 09:51:08 ryzen NetworkManager[455]: <info> [1640969468.3033] device (wlo1): supplicant interface state: completed -> disconnected
Dec 31 09:51:08 ryzen NetworkManager[455]: <info> [1640969468.3041] device (wlo1): supplicant interface state: disconnected -> interface_disabled
Dec 31 09:51:08 ryzen NetworkManager[455]: <info> [1640969468.3042] device (wlo1): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Dec 31 09:51:08 ryzen NetworkManager[455]: <info> [1640969468.3052] device (wlo1): set-hw-addr: reset MAC address to 14:13:33:7E:09:53 (unmanage)
Dec 31 09:51:08 ryzen kernel: rtw_8821ce 0000:01:00.0: stop vif b6:3b:c1:b2:6a:ec on port 0
Dec 31 09:51:08 ryzen kernel: rtw_8821ce 0000:01:00.0: start vif 14:13:33:7e:09:53 on port 0
Dec 31 09:51:08 ryzen systemd[1]: Reached target Sleep.
Dec 31 09:51:08 ryzen systemd[1]: Starting System Suspend...
Dec 31 09:51:08 ryzen wpa_supplicant[732]: nl80211: deinit ifname=wlo1 disabled_11b_rates=0
Dec 31 09:51:08 ryzen systemd-sleep[1803]: Entering sleep state 'suspend'...
Dec 31 09:51:08 ryzen kernel: PM: suspend entry (s2idle)
-- Boot ecc797f87d56404f88f0f60708908952 --
Dec 31 09:52:11 ryzen kernel: Linux version 5.15.8-1-MANJARO (builduser@fv-az121-204) (gcc (GCC) 11.1.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP PREEMPT Tue Dec 14 17:08:08 UTC 2021
Dec 31 09:52:11 ryzen kernel: Command line: root=UUID=f6d46af1-f1d6-4ecd-b1fd-0a2f7baca1a1 rw quiet splash apparmor=1 security=apparmor udev.log_priority=3 acpi_osi='Windows 2020' acpi_backlight=vendor iommu=soft initrd=\initramfs-5.15-x86_64.img
Thanks @JiaZhang. It does not appear to be a monitor issue, but here are the outputs from your suggested commands.
mhwd -li
Installed PCI configs:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-linux 2018.05.04 true PCI
Warning: No installed USB configs!
ls /sys/class/backlight
amdgpu_bl0
I’m sorry I couldn’t be more helpful - i did my best.
I’ll be honest, I’ve never opened an issue on freedesktop.org. Those people are hardcore & scare me. Half the time they’ll tell you to patch & recompile the kernel - I don’t know how to do that!!!
At any rate, you’re in the hands of someone with an @amd.com email address. Doesn’t get more expert than that 
P.S. Thanks for the link. I’ve enabled notifications, I’m sure there’s tons I’ll learn.
1 Like
similar issue 
So to check one of the things they asked for (CONFIG_AMD_PMC):
cat /proc/config.gz | gunzip > running.config
grep AMD_PMC running.config || echo "Nada :("
But according to gitlab, it does exist as a module:
1 Like
Thanks @cscs. Maybe together we can get them the information they need.
I have – long time ago – built a kernel to get wifi working on a laptop. But I forgot everything that involved. And I don’t even remember how to enable a kernel configuration option (as requested in the other thread). If anyone here has that knowledge, please post back?
For example, where is the kernel config file in Manjaro? It is not in /boot for me – neither on the new laptop or two other machines running Manjaro (it is present on a Pi running Manjaro though).
It is there in that post - /proc/config.gz
Ah, ok. I thought that there would be an editable version somewhere, like /boot.
Its something accomplished at compile time … so it wouldnt much matter if it were a text file.
Again at the post above the link takes you to the source where it is a text file.
Just updating here that there is no update on the freedesktop thread. Still hopeful a solution is forthcoming. This seems like kind a major downside to AMD chips.
There is some measures of progress. Linux516 now sleeps correctly, but still there are bugs in the wake up phase. From what I’ve read, a new batch of patches made their way into 5.17 kernel before the functionnality freeze, so there’s hope.
What Ryzen are you on? My 5500U does not suspend properly with 5.16.2 or 5.16.3.
Mine is an older 3700U ; I didn’t meant it worked flawlessly, but it feels “better” and I have high hopes the remaining bugs are going to be ironed out with the 5.17 kernel.
I noticed you already mentioned iommu=soft, which was the fix for me in grub on my Lenovo tb14 laptop.
Just adding this useful link about that, although im sure you have seen it.
Thanks for the thread, I found information here that was very useful to me.
[edit : WARNING !!! see answer below]
Finally ! The combination of linux517-rc kernel package as released tonight with “iommu=soft” command line parameter works and I have a functional s2idle sleep mode !
I believe my computer was released in 2019, so now about all the functions are working after 3 years of hard work by the kernel team… (Except the fingerprint reader, but this one looks hopeless).
If HP had not messed up with the BIOS, we could have saved 2 years out of those 3, easily.
How did you install the 5.17-rc? I’ve been building kernels over for the freedesktop troubleshooting and could do without building another…