(SOLVED) Troubles with resuming after suspend

thedigitalpixel · 2026-01-25 01:17:22

About 6 months ago, I encountered an issue where I was not able to wake my computer after suspend. It was effectively frozen and the only way to fix it was a hard reboot. I suspect the culprit was some update but I have no idea what started the issue. I have tried searching the internet and the forums with no success for a fix so here we are.

My computer:
AMD 5600x cpu
AMD 6700xt GPU
running arch linux of course.
I have a thinkpad running arch linux too that doesn't have any issues like this so it's something with this computer specifically.

Lately I've been on the Cosmic DE but this issue is agnostic to whatever DE or wm I try, hyprland, KDE, you name it. That included changing login managers such as cosmic, ly, and sddm.

Let me describe the symptoms in detail:
Whenever I would suspend, the monitor feed would turn off and the keyboard backlight would briefly turn off than back on than off again. (keyboard backlight is always on when the computer is awake). I would take a key on the keyboard and the backlight would turn on indicating the computer is trying to wake up but I never get a signal to the monitor. At that point the only think I can do is a hard reboot via holding the power button. I have since figured out that sleep by default is configured to try deep sleep first (s3) and then try s2idle if that fails. This corresponds to the behavior I'm seeing with the keyboard backlight turning off and on. Naturally I've tried setting the default sleep mode to s2idle and that solves nothing as it just skips the initial deep sleep attempt and the computer still gets stuck.

I have also tried changing kernel parameters of the GPU via the grub.cfg file to disable various gpu modes and none of that fixed the issue. After this I have been unable to find any fixes so far.

Bonus round:
since I cannot suspend I just lock my computer. However upon returning after a long time the computer will not send a monitor signal until I switch ttys. Switching back to tty1 the first time doesn't give a signal. But only on the second switch back from tty2 to tty1 where I had locked the system do I get a monitor signal and I can resume using my computer. Perhaps this behavior is related to why I cannot suspend idk.

So, short of nuking my os install I post here as a last resort.

Last edited by thedigitalpixel (2026-01-31 21:31:06)

seth · 2026-01-25 09:36:37

a key on the keyboard and the backlight would turn on … At that point the only think I can do is a hard reboot via holding the power button.

Assuming you tried to just switch the VT see whether https://wiki.archlinux.org/title/Keyboa … el_(SysRq) + REISUB works (nb. that you'll have to explicitly enable that first)

thedigitalpixel · 2026-01-25 22:24:30

seth wrote:

a key on the keyboard and the backlight would turn on … At that point the only think I can do is a hard reboot via holding the power button.
Assuming you tried to just switch the VT see whether https://wiki.archlinux.org/title/Keyboa … el_(SysRq) + REISUB works (nb. that you'll have to explicitly enable that first)

So I enabled that sysrq key via kernel parameters and while I was there I also switched back to deep sleep. Interestingly, the computer does successfully go to deep sleep. But when I try waking it still goes to the on frozen state. Putting in shortcuts to switch ttys does nothing. But the Alt+SysRq+b shortcut did force a reboot. Trying to terminate/kill processes with Alt+SysRq+e and Alt+SysRq+i does nothing.

seth · 2026-01-25 22:29:52

But the Alt+SysRq+b shortcut did force a reboot.

But seth wrote:

(SysRq) + REISUB

Specifically the S and the U will help to preserve the journal so after the reboot you can check that to see what went wrong.

thedigitalpixel · 2026-01-26 05:03:39

These are the first errors I could find in journalctl post waking from suspend. It's something to do with the gpu driver? I don't know the solution here as all the graphics drivers are up to date. Thoughts?

Jan 25 20:39:00 archdesktop cosmic-comp[1050]: Error while handling udev event.
Jan 25 20:39:00 archdesktop kernel: #PF: error_code(0x0002) - not-present page
Jan 25 20:39:00 archdesktop rtkit-daemon[1016]: Resuming known real-time threads.
Jan 25 20:39:00 archdesktop cosmic-comp[1050]: Error while handling udev event.
Jan 25 20:39:00 archdesktop kernel: #PF: supervisor write access in kernel mode
Jan 25 20:39:00 archdesktop kernel: BUG: kernel NULL pointer dereference, address: 0000000000000050
Jan 25 20:39:00 archdesktop kernel: amdgpu 0000:07:00.0: probe with driver amdgpu failed with error -62
Jan 25 20:39:00 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: amdgpu: finishing device.
Jan 25 20:39:00 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: Fatal error during GPU init
Jan 25 20:39:00 archdesktop (system-sleep)[78190]: /usr/lib/systemd/system-sleep/force-display-reset terminated by signal KILL.
Jan 25 20:39:00 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: asic reset on init failed
Jan 25 20:39:00 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: GPU mode1 reset failed
Jan 25 20:38:56 archdesktop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: GPU smu mode1 reset
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: GPU mode1 reset
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: MODE1 reset
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: Trusted Memory Zone (TMZ) feature disabled as experimental (default)
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: vgaarb: deactivate vga console
Jan 25 20:38:54 archdesktop kernel: amdgpu: ATOM BIOS: 113-EXT800255-L05
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: Fetched VBIOS from VFCT
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: detected ip block number 9 <jpeg_v3_0_0> (jpeg_v3_0)
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: detected ip block number 8 <vcn_v3_0_0> (vcn_v3_0)
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: detected ip block number 7 <sdma_v5_2_0> (sdma_v5_2)
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: detected ip block number 6 <gfx_v10_0_0> (gfx_v10_0)
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: detected ip block number 5 <dce_v1_0_0> (dm)
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: detected ip block number 4 <smu_v11_0_0> (smu)
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: detected ip block number 3 <psp_v11_0_0> (psp)
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: detected ip block number 2 <ih_v5_0_0> (navi10_ih)
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: detected ip block number 1 <gmc_v10_0_0> (gmc_v10_0)
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: detected ip block number 0 <common_v1_0_0> (nv_common)
Jan 25 20:38:54 archdesktop kernel: [drm:amdgpu_discovery_set_ip_blocks [amdgpu]] *ERROR* Couldn't init and add ip_discovery/
Jan 25 20:38:54 archdesktop kernel: kobject: kobject_add_internal failed for ip_discovery with -EEXIST, don't try to register things with the same name in the same directory.
Jan 25 20:38:54 archdesktop kernel:  </TASK>
Jan 25 20:38:54 archdesktop kernel: R13: 000000000000000d R14: 0000564f492145f0 R15: 0000564f492133b0
Jan 25 20:38:54 archdesktop kernel: R10: 0000000000000000 R11: 0000000000000202 R12: 000000000000000d
Jan 25 20:38:54 archdesktop kernel: RBP: 00007ffee73659e0 R08: 0000000000000000 R09: 0000000000000000
Jan 25 20:38:54 archdesktop kernel: RDX: 000000000000000d RSI: 0000564f492145f0 RDI: 0000000000000001

seth · 2026-01-26 07:29:44

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

The nullptr deref will hopefully have provided a backtrace.

thedigitalpixel · 2026-01-27 01:44:44

http://0x0.st/PNaZ.txt here is the whole log from previous boot.

seth · 2026-01-27 08:31:45

Jan 25 20:38:46 archdesktop kernel: PM: suspend exit
…
Jan 25 20:38:49 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: amdgpu: finishing device.
Jan 25 20:38:50 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: initializing kernel modesetting (NAVY_FLOUNDER 0x1002:0x73DF 0x1849:0x5210 0xC5).
Jan 25 20:38:50 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: register mmio base: 0xFCA00000
Jan 25 20:38:50 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: register mmio size: 1048576
Jan 25 20:38:52 archdesktop systemd[1]: systemd-rfkill.service: Deactivated successfully.
Jan 25 20:38:54 archdesktop kernel: sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:03.1/0000:05:00.0/0000:06:00.0/0000:07:00.0/ip_discovery'
Jan 25 20:38:54 archdesktop kernel: CPU: 1 UID: 0 PID: 78191 Comm: force-display-r Not tainted 6.18.6-arch1-1 #1 PREEMPT(full)  584c6d92e877db628252daf0f27a9ca84a3f90d3
Jan 25 20:38:54 archdesktop kernel: Hardware name: To Be Filled By O.E.M. B550M-ITX/ac/B550M-ITX/ac, BIOS P2.20 12/27/2022
Jan 25 20:38:54 archdesktop kernel: Call Trace:
Jan 25 20:38:54 archdesktop kernel:  <TASK>
Jan 25 20:38:54 archdesktop kernel:  dump_stack_lvl+0x5d/0x80
Jan 25 20:38:54 archdesktop kernel:  sysfs_warn_dup.cold+0x17/0x23
Jan 25 20:38:54 archdesktop kernel:  sysfs_create_dir_ns+0xcc/0xe0
Jan 25 20:38:54 archdesktop kernel:  kobject_add_internal+0xc2/0x260
Jan 25 20:38:54 archdesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 25 20:38:54 archdesktop kernel:  kobject_init_and_add+0x8e/0xc0
Jan 25 20:38:54 archdesktop kernel:  amdgpu_discovery_set_ip_blocks+0x3ba/0x2790 [amdgpu f83b8785171be58c86cccd3c33e944c4fac66e6b]
Jan 25 20:38:54 archdesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 25 20:38:54 archdesktop kernel:  ? pci_bus_read_config_dword+0x4c/0x80
Jan 25 20:38:54 archdesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 25 20:38:54 archdesktop kernel:  ? pcie_capability_read_dword+0x71/0x90
Jan 25 20:38:54 archdesktop kernel:  amdgpu_device_init.cold+0xf2a/0x24ed [amdgpu f83b8785171be58c86cccd3c33e944c4fac66e6b]
Jan 25 20:38:54 archdesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 25 20:38:54 archdesktop kernel:  ? pci_bus_read_config_word+0x4c/0x80
Jan 25 20:38:54 archdesktop kernel:  amdgpu_driver_load_kms+0x13/0x70 [amdgpu f83b8785171be58c86cccd3c33e944c4fac66e6b]
Jan 25 20:38:54 archdesktop kernel:  amdgpu_pci_probe+0x1ef/0x4d0 [amdgpu f83b8785171be58c86cccd3c33e944c4fac66e6b]
Jan 25 20:38:54 archdesktop kernel:  local_pci_probe+0x42/0x90
Jan 25 20:38:54 archdesktop kernel:  pci_device_probe+0xda/0x280
Jan 25 20:38:54 archdesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 25 20:38:54 archdesktop kernel:  ? sysfs_do_create_link_sd+0x6d/0xd0
Jan 25 20:38:54 archdesktop kernel:  really_probe+0xde/0x340
Jan 25 20:38:54 archdesktop kernel:  ? pm_runtime_barrier+0x55/0x90
Jan 25 20:38:54 archdesktop kernel:  __driver_probe_device+0x78/0x140
Jan 25 20:38:54 archdesktop kernel:  device_driver_attach+0x42/0xb0
Jan 25 20:38:54 archdesktop kernel:  bind_store+0x77/0xc0
Jan 25 20:38:54 archdesktop kernel:  kernfs_fop_write_iter+0x14d/0x200
Jan 25 20:38:54 archdesktop kernel:  vfs_write+0x25d/0x480
Jan 25 20:38:54 archdesktop kernel:  ksys_write+0x73/0xf0
Jan 25 20:38:54 archdesktop kernel:  do_syscall_64+0x81/0x7f0
Jan 25 20:38:54 archdesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 25 20:38:54 archdesktop kernel:  ? __x64_sys_fcntl+0x80/0x110
Jan 25 20:38:54 archdesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 25 20:38:54 archdesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 25 20:38:54 archdesktop kernel:  ? do_syscall_64+0x81/0x7f0
Jan 25 20:38:54 archdesktop kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 25 20:38:54 archdesktop kernel:  ? exc_page_fault+0x7e/0x1a0
Jan 25 20:38:54 archdesktop kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Jan 25 20:38:54 archdesktop kernel: RIP: 0033:0x7f5ecb69318e
Jan 25 20:38:54 archdesktop kernel: Code: 4d 89 d8 e8 44 be 00 00 4c 8b 5d f8 41 8b 93 08 03 00 00 59 5e 48 83 f8 fc 74 11 c9 c3 0f 1f 80 00 00 00 00 48 8b 45 10 0f 05 <c9> c3 83 e2 39 83 fa 08 75 e7 e8 13 ff ff ff 0f 1f 00 f3 0f 1e fa
Jan 25 20:38:54 archdesktop kernel: RSP: 002b:00007ffee73659d0 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
Jan 25 20:38:54 archdesktop kernel: RAX: ffffffffffffffda RBX: 00007f5ecb8095c0 RCX: 00007f5ecb69318e
Jan 25 20:38:54 archdesktop kernel: RDX: 000000000000000d RSI: 0000564f492145f0 RDI: 0000000000000001
Jan 25 20:38:54 archdesktop kernel: RBP: 00007ffee73659e0 R08: 0000000000000000 R09: 0000000000000000
Jan 25 20:38:54 archdesktop kernel: R10: 0000000000000000 R11: 0000000000000202 R12: 000000000000000d
Jan 25 20:38:54 archdesktop kernel: R13: 000000000000000d R14: 0000564f492145f0 R15: 0000564f492133b0
Jan 25 20:38:54 archdesktop kernel:  </TASK>
Jan 25 20:38:54 archdesktop kernel: kobject: kobject_add_internal failed for ip_discovery with -EEXIST, don't try to register things with the same name in the same directory.
Jan 25 20:38:54 archdesktop kernel: [drm:amdgpu_discovery_set_ip_blocks [amdgpu]] *ERROR* Couldn't init and add ip_discovery/
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: detected ip block number 0 <common_v1_0_0> (nv_common)
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: detected ip block number 1 <gmc_v10_0_0> (gmc_v10_0)
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: detected ip block number 2 <ih_v5_0_0> (navi10_ih)
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: detected ip block number 3 <psp_v11_0_0> (psp)
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: detected ip block number 4 <smu_v11_0_0> (smu)
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: detected ip block number 5 <dce_v1_0_0> (dm)
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: detected ip block number 6 <gfx_v10_0_0> (gfx_v10_0)
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: detected ip block number 7 <sdma_v5_2_0> (sdma_v5_2)
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: detected ip block number 8 <vcn_v3_0_0> (vcn_v3_0)
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: detected ip block number 9 <jpeg_v3_0_0> (jpeg_v3_0)
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: Fetched VBIOS from VFCT
Jan 25 20:38:54 archdesktop kernel: amdgpu: ATOM BIOS: 113-EXT800255-L05
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: vgaarb: deactivate vga console
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: Trusted Memory Zone (TMZ) feature disabled as experimental (default)
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: MODE1 reset
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: GPU mode1 reset
Jan 25 20:38:54 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: GPU smu mode1 reset
Jan 25 20:38:56 archdesktop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jan 25 20:39:00 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: GPU mode1 reset failed
Jan 25 20:39:00 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: asic reset on init failed
Jan 25 20:39:00 archdesktop (system-sleep)[78190]: /usr/lib/systemd/system-sleep/force-display-reset terminated by signal KILL.
Jan 25 20:39:00 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: Fatal error during GPU init
Jan 25 20:39:00 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: amdgpu: finishing device.
Jan 25 20:39:00 archdesktop kernel: amdgpu 0000:07:00.0: probe with driver amdgpu failed with error -62
Jan 25 20:39:00 archdesktop kernel: BUG: kernel NULL pointer dereference, address: 0000000000000050
Jan 25 20:39:00 archdesktop kernel: #PF: supervisor write access in kernel mode
Jan 25 20:39:00 archdesktop cosmic-comp[1050]: Error while handling udev event.
Jan 25 20:39:00 archdesktop rtkit-daemon[1016]: Resuming known real-time threads.
Jan 25 20:39:00 archdesktop kernel: #PF: error_code(0x0002) - not-present page
Jan 25 20:39:00 archdesktop cosmic-comp[1050]: Error while handling udev event.

"Comm: force-display-r" sounds like some local script to enforce the display rotation?
Udev triggered?

thedigitalpixel · 2026-01-31 06:21:51

so I opened up /usr/lib/systemd/system-sleep/force-display-reset. It's a bash script that looks like this:

#!/bin/bash

case $1/$2 in
  post/*)
    # Wait a moment for system to stabilize
    sleep 2
    # Unbind and rebind the GPU
    echo "0000:07:00.0" > /sys/bus/pci/drivers/amdgpu/unbind
    sleep 1
    echo "0000:07:00.0" > /sys/bus/pci/drivers/amdgpu/bind
    ;;
esac

the name entails it's supposed to reset the display so there's some reason this aint working. I have no idea I'm no software engineer.

thedigitalpixel · 2026-01-31 06:46:20

I did another suspend wake attempt it did the following:
Computer woke up and I briefly saw grey on the screen. Interestingly, the computer rebooted itself without inputing a keyboard command

journalctl ended with:

Jan 30 22:36:53 archdesktop kernel: Enabling non-boot CPUs ...
Jan 30 22:36:53 archdesktop kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Jan 30 22:36:53 archdesktop kernel: CPU1 is up
Jan 30 22:36:53 archdesktop kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Jan 30 22:36:53 archdesktop kernel: CPU2 is up
Jan 30 22:36:53 archdesktop kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Jan 30 22:36:53 archdesktop kernel: CPU3 is up
Jan 30 22:36:53 archdesktop kernel: smpboot: Booting Node 0 Processor 4 APIC 0x8
Jan 30 22:36:53 archdesktop kernel: CPU4 is up
Jan 30 22:36:53 archdesktop kernel: smpboot: Booting Node 0 Processor 5 APIC 0xa
Jan 30 22:36:53 archdesktop kernel: CPU5 is up
Jan 30 22:36:53 archdesktop kernel: smpboot: Booting Node 0 Processor 6 APIC 0x1
Jan 30 22:36:53 archdesktop kernel: Spectre V2 : Update user space SMT mitigation: STIBP always-on
Jan 30 22:36:53 archdesktop kernel: CPU6 is up
Jan 30 22:36:53 archdesktop kernel: smpboot: Booting Node 0 Processor 7 APIC 0x3
Jan 30 22:36:53 archdesktop kernel: CPU7 is up
Jan 30 22:36:53 archdesktop kernel: smpboot: Booting Node 0 Processor 8 APIC 0x5
Jan 30 22:36:53 archdesktop kernel: CPU8 is up
Jan 30 22:36:53 archdesktop kernel: smpboot: Booting Node 0 Processor 9 APIC 0x7
Jan 30 22:36:53 archdesktop kernel: CPU9 is up
Jan 30 22:36:53 archdesktop kernel: smpboot: Booting Node 0 Processor 10 APIC 0x9
Jan 30 22:36:53 archdesktop kernel: CPU10 is up
Jan 30 22:36:53 archdesktop kernel: smpboot: Booting Node 0 Processor 11 APIC 0xb
Jan 30 22:36:53 archdesktop kernel: CPU11 is up
Jan 30 22:36:53 archdesktop kernel: ACPI: PM: Waking up from system sleep state S3
Jan 30 22:36:53 archdesktop kernel: xhci_hcd 0000:01:00.0: xHC error in resume, USBSTS 0x401, Reinit
Jan 30 22:36:53 archdesktop kernel: usb usb1: root hub lost power or was reset
Jan 30 22:36:53 archdesktop kernel: usb usb2: root hub lost power or was reset
Jan 30 22:36:53 archdesktop kernel: serial 00:05: activated
Jan 30 22:36:53 archdesktop kernel: [drm] PCIE GART of 512M enabled (table at 0x00000082FEB00000).
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: PSP is resuming...
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: reserve 0xa00000 from 0x82fd000000 for PSP TMR
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: RAS: optional ras ta ucode is not available
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: SECUREDISPLAY: optional securedisplay ta ucode is not available
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: SMU is resuming...
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: smu driver if version = 0x0000000e, smu fw if version = 0x00000012, smu fw program = 0, version = 0x00413f00 (65.63.0)
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: SMU driver if version not matched
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: use vbios provided pptable
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: SMU is resumed successfully!
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: kiq ring mec 2 pipe 1 q 0
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: [drm] DMUB hardware initialized: version=0x02020021
Jan 30 22:36:53 archdesktop kernel: ata3: SATA link down (SStatus 0 SControl 330)
Jan 30 22:36:53 archdesktop kernel: ata6: SATA link down (SStatus 0 SControl 330)
Jan 30 22:36:53 archdesktop kernel: ata4: SATA link down (SStatus 0 SControl 330)
Jan 30 22:36:53 archdesktop kernel: ata5: SATA link down (SStatus 0 SControl 330)
Jan 30 22:36:53 archdesktop kernel: usb 1-4: reset high-speed USB device number 3 using xhci_hcd
Jan 30 22:36:53 archdesktop kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 30 22:36:53 archdesktop kernel: ata2.00: supports DRM functions and may not be fully accessible
Jan 30 22:36:53 archdesktop kernel: sd 1:0:0:0: [sdb] Starting disk
Jan 30 22:36:53 archdesktop kernel: ata2.00: supports DRM functions and may not be fully accessible
Jan 30 22:36:53 archdesktop kernel: ata2.00: configured for UDMA/133
Jan 30 22:36:53 archdesktop kernel: ahci 0000:01:00.1: port does not support device sleep
Jan 30 22:36:53 archdesktop kernel: usb 1-8: WARN: invalid context state for evaluate context command.
Jan 30 22:36:53 archdesktop kernel: usb 1-8: reset full-speed USB device number 4 using xhci_hcd
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: ring gfx_0.1.0 uses VM inv eng 1 on hub 0
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 4 on hub 0
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 5 on hub 0
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 12 on hub 0
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: ring sdma0 uses VM inv eng 13 on hub 0
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: ring sdma1 uses VM inv eng 14 on hub 0
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
Jan 30 22:36:53 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8
Jan 30 22:36:53 archdesktop kernel: usb 1-1: WARN: invalid context state for evaluate context command.
Jan 30 22:36:53 archdesktop kernel: usb 1-1: reset full-speed USB device number 2 using xhci_hcd
Jan 30 22:36:53 archdesktop kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 30 22:36:53 archdesktop kernel: sd 0:0:0:0: [sda] Starting disk
Jan 30 22:36:53 archdesktop kernel: ata1.00: configured for UDMA/100
Jan 30 22:36:53 archdesktop kernel: usb 1-9: WARN: invalid context state for evaluate context command.
Jan 30 22:36:53 archdesktop kernel: usb 1-9: reset full-speed USB device number 5 using xhci_hcd
Jan 30 22:36:53 archdesktop kernel: OOM killer enabled.
Jan 30 22:36:53 archdesktop kernel: Restarting tasks: Starting
Jan 30 22:36:53 archdesktop kernel: Restarting tasks: Done
Jan 30 22:36:53 archdesktop kernel: efivarfs: resyncing variable state
Jan 30 22:36:53 archdesktop kernel: efivarfs: finished resyncing variable state
Jan 30 22:36:53 archdesktop kernel: random: crng reseeded on system resumption
Jan 30 22:36:53 archdesktop kernel: PM: suspend exit
Jan 30 22:36:53 archdesktop kernel: Bluetooth: hci0: Legacy ROM 2.x revision 5.0 build 25 week 20 2015
Jan 30 22:36:53 archdesktop kernel: Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-22.50.19.14.f.bseq
Jan 30 22:36:53 archdesktop systemd[1]: Stopped target Bluetooth Support.
Jan 30 22:36:53 archdesktop systemd[1]: Reached target Bluetooth Support.
Jan 30 22:36:53 archdesktop systemd[1]: Started Load/Save RF Kill Switch Status.
Jan 30 22:36:55 archdesktop kernel: Bluetooth: hci0: Intel BT fw patch 0x43 completed & activated
Jan 30 22:36:55 archdesktop bluetoothd[643]: Battery Provider Manager created
Jan 30 22:36:55 archdesktop kernel: Bluetooth: MGMT ver 1.23
Jan 30 22:36:56 archdesktop kernel: Console: switching to colour dummy device 80x25
Jan 30 22:36:56 archdesktop kernel: amdgpu 0000:07:00.0: amdgpu: amdgpu: finishing device.
Jan 30 22:36:59 archdesktop systemd[1]: systemd-rfkill.service: Deactivated successfully.
Jan 30 22:37:03 archdesktop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jan 30 22:37:24 archdesktop kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 26s! [force-display-r:5539]
Jan 30 22:37:24 archdesktop kernel: CPU#2 Utilization every 4000ms during lockup:
Jan 30 22:37:24 archdesktop kernel:         #1:   1% system,          0% softirq,          0% hardirq,          0% idle
Jan 30 22:37:24 archdesktop kernel:         #2:   1% system,          0% softirq,          0% hardirq,          0% idle
Jan 30 22:37:24 archdesktop kernel:         #3:   1% system,          0% softirq,          0% hardirq,          0% idle
Jan 30 22:37:24 archdesktop kernel:         #4:   1% system,          0% softirq,          0% hardirq,          0% idle
Jan 30 22:37:24 archdesktop kernel:         #5:   1% system,          0% softirq,          0% hardirq,          0% idle

there's that script again.

thedigitalpixel · 2026-01-31 07:14:18

Well, I'm more angry than happy even though I FIXED THE ISSUE.
I learned that bash scripts in that system-sleep folder run when you suspend. I think I never put that bash script there so I'm guessing some package decided to put that script there or I put it there a long time ago trying to fix this issue idk. Well, removing it fixed the issue. If I did put this script there months ago, the original issue has probably been fixed in the kernel/gpu drivers by now.

seth · 2026-01-31 09:49:05

pacman -Qo /usr/lib/systemd/system-sleep/force-display-reset

but I suspect

put it there a long time ago trying to fix this issue idk

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Arch Linux

#1 2026-01-25 01:17:22

(SOLVED) Troubles with resuming after suspend

#2 2026-01-25 09:36:37

Re: (SOLVED) Troubles with resuming after suspend

#3 2026-01-25 22:24:30

Re: (SOLVED) Troubles with resuming after suspend

#4 2026-01-25 22:29:52

Re: (SOLVED) Troubles with resuming after suspend

#5 2026-01-26 05:03:39

Re: (SOLVED) Troubles with resuming after suspend

#6 2026-01-26 07:29:44

Re: (SOLVED) Troubles with resuming after suspend

#7 2026-01-27 01:44:44

Re: (SOLVED) Troubles with resuming after suspend

#8 2026-01-27 08:31:45

Re: (SOLVED) Troubles with resuming after suspend

#9 2026-01-31 06:21:51

Re: (SOLVED) Troubles with resuming after suspend

#10 2026-01-31 06:46:20

Re: (SOLVED) Troubles with resuming after suspend

#11 2026-01-31 07:14:18

Re: (SOLVED) Troubles with resuming after suspend

#12 2026-01-31 09:49:05

Re: (SOLVED) Troubles with resuming after suspend

Board footer