[RESOLVED] 13" Ryzen 5 + Debian 12 fails to wake from sleep

Hi,

I’ve been enjoying messing around the laptop, especially as a newbie to Linux, but this sleep/suspend/whatever problem is really making me pull my hair out.

Closing the laptop lid (or otherwise sleeping it in any way) and opening it again to wake does not bring the screen back, and whenever it does manage to ““come back””, it appears in a very corrupted state, like what you would see with a failing GPU.

This “corrupted” state has (on graphical mode) a bunch of small white blocks repeating in a pattern, where the cursor is a massive block about ~2 inches square with lots of colored vertical lines squished together. In text mode (tty ctrl+alt+f{1…6}) the entire screen appears like the cursor lines, however it still accepts text input as I was able to blindly log on and run startx to see the graphical-mode corruption mentioned earlier.

(I’ll try to get a picture later)

I noticed in the dmesg log (sudo journalctl -k -b -1 -o short-precise | grep -a2 -b2 amdgpu) that after waking back up (black screen, not corruption) there is a mess of:

2xxxxx:Nov 1 xx:xx:xx.x HOSTNAME kernel: [drm:dc_dumb_srv_wait_idle [amdgpu]] *ERROR* Error waiting for DMUB idle: status=3
2xxxxx:Nov 1 xx:xx:xx.x HOSTNAME kernel: [drm:dc_dumb_srv_cmd_queue [amdgpu]] *ERROR* Error waiting for DMUB idle: status=3
2xxxxx:Nov 1 xx:xx:xx.x HOSTNAME kernel: [drm:dc_dumb_srv_cmd_queue [amdgpu]] *ERROR* Error queuing DMUB command: status=2

(This repeats either every second or every keypress, as it seems through either magic or placebo that spamming keys when waking brings me into the corrupted state more often than just a black screen)

There is also a warning early on about failing to load some firmware:

2xxxxx:Nov 1 xx:xx:xx.x HOSTNAME kernel: amdgpu 0000:c1:00.0: firmware: failed to load amdgpu/gc_11_0_1_mes_2.bin (-2)

I saw a thread somewhere here where they also mentioned this log message and downloaded the file from git.kernel.org (I got linux-firmware-20231030.tar.gz) and moved the file to an unspecified location and they didn’t see any difference; I moved the file to /lib/firmware/amdgpu (according to Firmware - Debian Wiki ) but the message still appears.

I’ve tried every type of solution, like (from memory):

  • kernel nvme.noacpi=1 (read later that that might make things worse, but I saw no difference; removed anyways)
  • kernel amdgpu.gpu_recovery=1 (this makes the corruption effect appear much more often, so I think it’s having some effect in recovering the GPU?)
  • kernel amdgpu.sg_display=0 (seemingly only affects Fedora uses experiencing a different graphical wake bug)
  • kernel amdgpu.ppfeaturemask=0xffffffff (saw this one on the Arch wiki, thought “why the hell not”, this has no effect)
  • Sideloading the gc_11_0_1_mes_2.bin file (no effect, not even detected?)
  • Use “optimal defaults” BIOS settings preset (I had messed with the BIOS settings before even booting into the Debian installer)
  • Two other (official Debian) kernels, full list below
  • Fedora 39 live (also had black screen on wake)

Using:

  • Framework Laptop 13 (batch 2)
  • BIOS: 3.03 (update via lvfs)
  • CPU: Ryzen 5 7640U
  • RAM: 16gb Crucial DDR5-5600
  • OS
    • Main: Debian 12.2
      • Kernels used: 6.1.0-9, 6.1.0-13, 6.4.0-0.deb12.2, 6.5.0-3 (via trixie)
      • DE: KDE 5.27.5
      • Upgraded from: Debian 12.0.0 DVD (installed via Ventoy) (just what I had at the time)
    • Tested: (live) Fedora 39 beta 1.1
      • DE: KDE
1 Like

Suspend works well with resume on Fedora 39 GNOME. Should also be fine on KDE, but largely untested.

Also, by the way,

Debian (unless you install a very new kernel) is going to be iffy. Fedora is going to be your best bet. I use it all day, every day on the AMD Ryzen 7040 series.

  • Install forgoing the various tweaks and kernel parameters. Just install Fedora 39, GNOME.
  • Run your updates. Reboot.
  • Test with external displays and other attached devices, detached.
  • Do not, repeat, do not use nvme.noacpi=1 - it will interfere with suspend/resume per AMD themselves.
1 Like

Any news on that front? Having the same issue with my setup

I could fix the amdgpu firmware fallback at boot, with the latest amdgpu-firmware. But sleep and wake does not work at all.

When resuming from sleep, the screen stays black, the powerbtn/fingerprintreader glows continiously. Also nothing happens when cycling through tty with ctrl+alt+f{1-6}.

Below the snippet from the journal when entering sleep.

Nov 10 01:12:36 titan systemd-sleep[5729]: Entering sleep state 'suspend'...
Nov 10 01:12:36 titan kernel: PM: suspend entry (s2idle)
Nov 10 01:12:36 titan kernel: Filesystems sync: 0.011 seconds
Nov 10 01:12:36 titan kernel: (NULL device *): firmware: direct-loading firmware mediatek/WIFI_MT7922_patch_mcu_1_1_hdr.bin
Nov 10 01:12:36 titan kernel: (NULL device *): firmware: direct-loading firmware mediatek/WIFI_RAM_CODE_MT7922_1.bin
Nov 10 01:12:36 titan kernel: (NULL device *): firmware: direct-loading firmware regulatory.db.p7s
Nov 10 01:12:36 titan kernel: (NULL device *): firmware: direct-loading firmware regulatory.db
Nov 10 01:12:36 titan kernel: (NULL device *): firmware: direct-loading firmware mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin
Nov 10 01:13:29 titan kernel: Freezing user space processes
Nov 10 01:13:29 titan kernel: Freezing user space processes completed (elapsed 0.027 seconds)
Nov 10 01:13:29 titan kernel: OOM killer disabled.
Nov 10 01:13:29 titan kernel: Freezing remaining freezable tasks
Nov 10 01:13:29 titan kernel: Freezing remaining freezable tasks completed (elapsed 0.002 seconds)
Nov 10 01:13:29 titan kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Nov 10 01:13:29 titan kernel: queueing ieee80211 work while going to suspend
Nov 10 01:13:29 titan kernel: ACPI: EC: interrupt blocked
Nov 10 01:13:29 titan kernel: ACPI: EC: interrupt unblocked
Nov 10 01:13:29 titan kernel: nvme nvme0: Shutdown timeout set to 10 seconds
Nov 10 01:13:29 titan kernel: nvme nvme0: 16/0/0 default/read/poll queues
Nov 10 01:13:29 titan kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0x6b on isa0060/serio0).
Nov 10 01:13:29 titan kernel: atkbd serio0: Use 'setkeycodes 6b <keycode>' to make it known.
Nov 10 01:13:29 titan kernel: atkbd serio0: Unknown key released (translated set 2, code 0x6b on isa0060/serio0).
Nov 10 01:13:29 titan kernel: atkbd serio0: Use 'setkeycodes 6b <keycode>' to make it known.
Nov 10 01:13:29 titan kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Nov 10 01:13:29 titan kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Nov 10 01:13:29 titan kernel: [drm] PCIE GART of 512M enabled (table at 0x000000801FD00000).
Nov 10 01:13:29 titan kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is resuming...
Nov 10 01:13:29 titan kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is resumed successfully!
Nov 10 01:13:29 titan kernel: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:264
Nov 10 01:13:29 titan kernel: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:272
Nov 10 01:13:29 titan kernel: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:280
Nov 10 01:13:29 titan kernel: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:288
Nov 10 01:13:29 titan kernel: [drm] Failed to enable ASSR
Nov 10 01:13:29 titan kernel: ------------[ cut here ]------------
Nov 10 01:13:29 titan kernel: WARNING: CPU: 6 PID: 5740 at drivers/gpu/drm/amd/amdgpu/../display/dc/link/protocols/link_edp_panel_control.c:83 dp_>
Nov 10 01:13:29 titan kernel: Modules linked in: ctr ccm rfcomm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device cmac algif_hash algif_skcipher af>
Nov 10 01:13:29 titan kernel:  serio_raw msr parport_pc ppdev lp parport fuse loop efi_pstore configfs ip_tables x_tables autofs4 ext4 crc16 mbcac>
Nov 10 01:13:29 titan kernel: CPU: 6 PID: 5740 Comm: kworker/u32:18 Not tainted 6.5.0-0.deb12.1-rt-amd64 #1  Debian 6.5.3-1~bpo12+1
Nov 10 01:13:29 titan kernel: Hardware name: Framework Laptop 13 (AMD Ryzen 7040Series)/FRANMDCP05, BIOS 03.03 10/17/2023
Nov 10 01:13:29 titan kernel: Workqueue: events_unbound async_run_entry_fn
Nov 10 01:13:29 titan kernel: RIP: 0010:dp_set_panel_mode+0xca/0xe0 [amdgpu]
Nov 10 01:13:29 titan kernel: Code: 00 48 c7 c2 a0 20 4d c1 e8 63 9b 7c ff 48 8b 44 24 08 65 48 2b 04 25 28 00 00 00 75 11 48 83 c4 10 5b 5d 41 5c>
Nov 10 01:13:29 titan kernel: RSP: 0018:ffffa86cc2acf390 EFLAGS: 00010282
Nov 10 01:13:29 titan kernel: RAX: 00000000ffffffff RBX: ffff94424c56e800 RCX: ffffffffc0b42b10
Nov 10 01:13:29 titan kernel: RDX: 00000000fffffffb RSI: ffff9442419a50d0 RDI: 0000000000000000
Nov 10 01:13:29 titan kernel: RBP: 0000000000000001 R08: ffff944265d8abc0 R09: 000000000000010a
Nov 10 01:13:29 titan kernel: R10: 0000000000000002 R11: 0000000000000000 R12: 0000000000000001
Nov 10 01:13:29 titan kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Nov 10 01:13:29 titan kernel: FS:  0000000000000000(0000) GS:ffff94499e780000(0000) knlGS:0000000000000000
Nov 10 01:13:29 titan kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 10 01:13:29 titan kernel: CR2: 00007f00f03100e8 CR3: 00000005f6c2a000 CR4: 0000000000750ee0
Nov 10 01:13:29 titan kernel: PKRU: 55555554
Nov 10 01:13:29 titan kernel: Call Trace:
Nov 10 01:13:29 titan kernel:  <TASK>
Nov 10 01:13:29 titan kernel:  ? __warn+0x99/0x190
Nov 10 01:13:29 titan kernel:  ? dp_set_panel_mode+0xca/0xe0 [amdgpu]
Nov 10 01:12:36 titan avahi-daemon[1326]: Withdrawing address record for 192.168.4.213 on wlp1s0.
Nov 10 01:12:36 titan NetworkManager[1366]: <info>  [1699575156.4627] device (wlp1s0): set-hw-addr: set MAC address to AE:03:D0:28:DB:41 (scanning)
Nov 10 01:12:36 titan avahi-daemon[1326]: Joining mDNS multicast group on interface wlp1s0.IPv4 with address 192.168.4.213.
Nov 10 01:12:36 titan avahi-daemon[1326]: New relevant interface wlp1s0.IPv4 for mDNS.
Nov 10 01:12:36 titan avahi-daemon[1326]: Registering new address record for 192.168.4.213 on wlp1s0.IPv4.
Nov 10 01:12:36 titan kwin_wayland_wrapper[5667]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Nov 10 01:12:36 titan avahi-daemon[1326]: Withdrawing address record for 192.168.4.213 on wlp1s0.
Nov 10 01:12:36 titan avahi-daemon[1326]: Leaving mDNS multicast group on interface wlp1s0.IPv4 with address 192.168.4.213.
Nov 10 01:12:36 titan avahi-daemon[1326]: Interface wlp1s0.IPv4 no longer relevant for mDNS.
Nov 10 01:12:36 titan NetworkManager[1366]: <info>  [1699575156.6249] device (wlp1s0): supplicant interface state: completed -> disconnected
Nov 10 01:12:36 titan NetworkManager[1366]: <info>  [1699575156.6250] device (wlp1s0): supplicant interface state: disconnected -> interface_disab>
Nov 10 01:12:36 titan NetworkManager[1366]: <info>  [1699575156.6251] device (wlp1s0): supplicant interface state: interface_disabled -> disconnec>
Nov 10 01:12:36 titan NetworkManager[1366]: <info>  [1699575156.6253] device (wlp1s0): state change: disconnected -> unmanaged (reason 'sleeping',>
Nov 10 01:12:36 titan NetworkManager[1366]: <info>  [1699575156.8002] device (wlp1s0): set-hw-addr: reset MAC address to 14:AC:60:46:9C:55 (unmana>
Nov 10 01:12:36 titan systemd[1]: Reached target sleep.target - Sleep.
Nov 10 01:12:36 titan wpa_supplicant[1371]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
Nov 10 01:12:36 titan systemd[1]: Starting systemd-suspend.service - System Suspend...
Nov 10 01:12:36 titan systemd-sleep[5729]: Entering sleep state 'suspend'...
Nov 10 01:12:36 titan kernel: PM: suspend entry (s2idle)
Nov 10 01:12:36 titan kernel: Filesystems sync: 0.011 seconds
Nov 10 01:12:36 titan kernel: (NULL device *): firmware: direct-loading firmware mediatek/WIFI_MT7922_patch_mcu_1_1_hdr.bin
Nov 10 01:12:36 titan kernel: (NULL device *): firmware: direct-loading firmware mediatek/WIFI_RAM_CODE_MT7922_1.bin
Nov 10 01:12:36 titan kernel: (NULL device *): firmware: direct-loading firmware regulatory.db.p7s
Nov 10 01:12:36 titan kernel: (NULL device *): firmware: direct-loading firmware regulatory.db
Nov 10 01:12:36 titan kernel: (NULL device *): firmware: direct-loading firmware mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin
Nov 10 01:13:29 titan kernel: Freezing user space processes
Nov 10 01:13:29 titan kernel: Freezing user space processes completed (elapsed 0.027 seconds)
Nov 10 01:13:29 titan kernel: OOM killer disabled.
Nov 10 01:13:29 titan kernel: Freezing remaining freezable tasks
Nov 10 01:13:29 titan kernel: Freezing remaining freezable tasks completed (elapsed 0.002 seconds)
Nov 10 01:13:29 titan kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Nov 10 01:13:29 titan kernel: queueing ieee80211 work while going to suspend
Nov 10 01:13:29 titan kernel: ACPI: EC: interrupt blocked
Nov 10 01:13:29 titan kernel: ACPI: EC: interrupt unblocked
Nov 10 01:13:29 titan kernel: nvme nvme0: Shutdown timeout set to 10 seconds
Nov 10 01:13:29 titan kernel: nvme nvme0: 16/0/0 default/read/poll queues
Nov 10 01:13:29 titan kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0x6b on isa0060/serio0).
Nov 10 01:13:29 titan kernel: atkbd serio0: Use 'setkeycodes 6b <keycode>' to make it known.
Nov 10 01:13:29 titan kernel: atkbd serio0: Unknown key released (translated set 2, code 0x6b on isa0060/serio0).
Nov 10 01:13:29 titan kernel: atkbd serio0: Use 'setkeycodes 6b <keycode>' to make it known.
Nov 10 01:13:29 titan kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Nov 10 01:13:29 titan kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Nov 10 01:13:29 titan kernel: [drm] PCIE GART of 512M enabled (table at 0x000000801FD00000).
Nov 10 01:13:29 titan kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is resuming...
Nov 10 01:13:29 titan kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is resumed successfully!
Nov 10 01:13:29 titan kernel: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:264
Nov 10 01:13:29 titan kernel: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:272
Nov 10 01:13:29 titan kernel: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:280
Nov 10 01:13:29 titan kernel: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:288
Nov 10 01:13:29 titan kernel: [drm] Failed to enable ASSR
Nov 10 01:13:29 titan kernel: ------------[ cut here ]------------
Nov 10 01:13:29 titan kernel: WARNING: CPU: 6 PID: 5740 at drivers/gpu/drm/amd/amdgpu/../display/dc/link/protocols/link_edp_panel_control.c:83 dp_>
Nov 10 01:13:29 titan kernel: Modules linked in: ctr ccm rfcomm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device cmac algif_hash algif_skcipher af>
Nov 10 01:13:29 titan kernel:  serio_raw msr parport_pc ppdev lp parport fuse loop efi_pstore configfs ip_tables x_tables autofs4 ext4 crc16 mbcac>
Nov 10 01:13:29 titan kernel: CPU: 6 PID: 5740 Comm: kworker/u32:18 Not tainted 6.5.0-0.deb12.1-rt-amd64 #1  Debian 6.5.3-1~bpo12+1
Nov 10 01:13:29 titan kernel: Hardware name: Framework Laptop 13 (AMD Ryzen 7040Series)/FRANMDCP05, BIOS 03.03 10/17/2023
Nov 10 01:13:29 titan kernel: Workqueue: events_unbound async_run_entry_fn
Nov 10 01:13:29 titan kernel: RIP: 0010:dp_set_panel_mode+0xca/0xe0 [amdgpu]
Nov 10 01:13:29 titan kernel: Code: 00 48 c7 c2 a0 20 4d c1 e8 63 9b 7c ff 48 8b 44 24 08 65 48 2b 04 25 28 00 00 00 75 11 48 83 c4 10 5b 5d 41 5c>
Nov 10 01:13:29 titan kernel: RSP: 0018:ffffa86cc2acf390 EFLAGS: 00010282
Nov 10 01:13:29 titan kernel: RAX: 00000000ffffffff RBX: ffff94424c56e800 RCX: ffffffffc0b42b10
Nov 10 01:13:29 titan kernel: RDX: 00000000fffffffb RSI: ffff9442419a50d0 RDI: 0000000000000000
Nov 10 01:13:29 titan kernel: RBP: 0000000000000001 R08: ffff944265d8abc0 R09: 000000000000010a
Nov 10 01:13:29 titan kernel: R10: 0000000000000002 R11: 0000000000000000 R12: 0000000000000001
Nov 10 01:13:29 titan kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Nov 10 01:13:29 titan kernel: FS:  0000000000000000(0000) GS:ffff94499e780000(0000) knlGS:0000000000000000
Nov 10 01:13:29 titan kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 10 01:13:29 titan kernel: CR2: 00007f00f03100e8 CR3: 00000005f6c2a000 CR4: 0000000000750ee0
Nov 10 01:13:29 titan kernel: PKRU: 55555554
Nov 10 01:13:29 titan kernel: Call Trace:
Nov 10 01:13:29 titan kernel:  <TASK>
Nov 10 01:13:29 titan kernel:  ? __warn+0x99/0x190
Nov 10 01:13:29 titan kernel:  ? dp_set_panel_mode+0xca/0xe0 [amdgpu]
Nov 10 01:13:29 titan kernel:  ? report_bug+0x1bd/0x1f0
Nov 10 01:13:29 titan kernel:  ? handle_bug+0x41/0x70
Nov 10 01:13:29 titan kernel:  ? exc_invalid_op+0x17/0x70
Nov 10 01:13:29 titan kernel:  ? asm_exc_invalid_op+0x1a/0x20
Nov 10 01:13:29 titan kernel:  ? dp_set_panel_mode+0xca/0xe0 [amdgpu]
Nov 10 01:13:29 titan kernel:  perform_link_training_with_retries+0x203/0x560 [amdgpu]
Nov 10 01:13:29 titan kernel:  ? core_link_write_dpcd+0x8f/0x100 [amdgpu]
Nov 10 01:13:29 titan kernel:  enable_link_dp+0x13a/0x2c0 [amdgpu]
Nov 10 01:13:29 titan kernel:  link_set_dpms_on+0x743/0xcc0 [amdgpu]
Nov 10 01:13:29 titan kernel:  dce110_apply_ctx_to_hw+0x531/0x700 [amdgpu]
Nov 10 01:13:29 titan kernel:  ? dm_read_reg_func+0x3c/0xe0 [amdgpu]
Nov 10 01:13:29 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 10 01:13:29 titan kernel:  ? dcn10_verify_allow_pstate_change_high+0x36/0x3c0 [amdgpu]
Nov 10 01:13:29 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 10 01:13:29 titan kernel:  ? dcn10_wait_for_mpcc_disconnect+0x3a/0x160 [amdgpu]
Nov 10 01:13:29 titan kernel:  dc_commit_state_no_check+0x3ca/0xf20 [amdgpu]
Nov 10 01:13:29 titan kernel:  dc_commit_streams+0x259/0x3c0 [amdgpu]
Nov 10 01:13:29 titan kernel:  amdgpu_dm_atomic_commit_tail+0x630/0x3a60 [amdgpu]
Nov 10 01:13:29 titan kernel:  ? calculate_init_and_vp+0x101/0x210 [amdgpu]
Nov 10 01:13:29 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 10 01:13:29 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 10 01:13:29 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 10 01:13:29 titan kernel:  ? migrate_enable+0xd9/0x150
Nov 10 01:13:29 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 10 01:13:29 titan kernel:  ? dcn314_validate_bandwidth+0x1fe/0x320 [amdgpu]
Nov 10 01:13:29 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 10 01:13:29 titan kernel:  ? ___slab_alloc+0x622/0xaf0
Nov 10 01:13:29 titan kernel:  ? drm_atomic_helper_setup_commit+0x42d/0x840 [drm_kms_helper]
Nov 10 01:13:29 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 10 01:13:29 titan kernel:  ? dma_resv_iter_first_unlocked+0x66/0x70
Nov 10 01:13:29 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 10 01:13:29 titan kernel:  ? dma_resv_get_fences+0x61/0x220
Nov 10 01:13:29 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 10 01:13:29 titan kernel:  ? dma_resv_get_singleton+0x46/0x140
Nov 10 01:13:29 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 10 01:13:29 titan kernel:  ? migrate_enable+0xd9/0x150
Nov 10 01:13:29 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 10 01:13:29 titan kernel:  commit_tail+0x91/0x130 [drm_kms_helper]
Nov 10 01:13:29 titan kernel:  drm_atomic_helper_commit+0x116/0x140 [drm_kms_helper]
Nov 10 01:13:29 titan kernel:  drm_atomic_commit+0x97/0xd0 [drm]
Nov 10 01:13:29 titan kernel:  ? __pfx___drm_printfn_info+0x10/0x10 [drm]
Nov 10 01:13:29 titan kernel:  drm_atomic_helper_commit_duplicated_state+0xcd/0xe0 [drm_kms_helper]
Nov 10 01:13:29 titan kernel:  drm_atomic_helper_resume+0xa8/0x160 [drm_kms_helper]
Nov 10 01:13:29 titan kernel:  dm_resume+0x321/0x7a0 [amdgpu]
Nov 10 01:13:29 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 10 01:13:29 titan kernel:  ? _dev_info+0x79/0xa0
Nov 10 01:13:29 titan kernel:  amdgpu_device_ip_resume_phase2+0x4f/0xc0 [amdgpu]
Nov 10 01:13:29 titan kernel:  amdgpu_device_resume+0xbb/0x2c0 [amdgpu]
Nov 10 01:13:29 titan kernel:  ? __pfx_pci_pm_resume+0x10/0x10
Nov 10 01:13:29 titan kernel:  amdgpu_pmops_resume+0x4a/0x80 [amdgpu]
Nov 10 01:13:29 titan kernel:  ? __pfx_pci_pm_resume+0x10/0x10
Nov 10 01:13:29 titan kernel:  dpm_run_callback+0x8c/0x240
Nov 10 01:13:29 titan kernel:  device_resume+0x88/0x190
Nov 10 01:13:29 titan kernel:  async_resume+0x1e/0x60
Nov 10 01:13:29 titan kernel:  async_run_entry_fn+0x2f/0x130
Nov 10 01:13:29 titan kernel:  process_one_work+0x1df/0x440
Nov 10 01:13:29 titan kernel:  worker_thread+0x51/0x390
Nov 10 01:13:29 titan kernel:  ? __pfx_worker_thread+0x10/0x10
Nov 10 01:13:29 titan kernel:  kthread+0x114/0x140
Nov 10 01:13:29 titan kernel:  ? __pfx_kthread+0x10/0x10
Nov 10 01:13:29 titan kernel:  ret_from_fork+0x31/0x50
Nov 10 01:13:29 titan kernel:  ? __pfx_kthread+0x10/0x10
Nov 10 01:13:29 titan kernel:  ret_from_fork_asm+0x1b/0x30
Nov 10 01:13:29 titan kernel:  </TASK>
Nov 10 01:13:29 titan kernel: ---[ end trace 0000000000000000 ]---
Nov 10 01:13:29 titan kernel: [drm] Failed to enable ASSR
Nov 10 01:13:29 titan kernel: [drm] Failed to enable ASSR
Nov 10 01:13:29 titan kernel: [drm] Failed to enable ASSR
Nov 10 01:13:29 titan kernel: [drm] enabling link 0 failed: 15
Nov 10 01:13:29 titan kernel: [drm:dc_dmub_srv_cmd_run_list [amdgpu]] *ERROR* Error queueing DMUB command: status=2
Nov 10 01:13:29 titan kernel: [drm:dc_dmub_srv_cmd_run_list [amdgpu]] *ERROR* Error queueing DMUB command: status=2
Nov 10 01:13:29 titan kernel: [drm:dc_dmub_srv_cmd_run_list [amdgpu]] *ERROR* Error queueing DMUB command: status=2
Nov 10 01:13:29 titan kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Nov 10 01:13:29 titan kernel: amdgpu 0000:c1:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
Nov 10 01:13:29 titan kernel: amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Nov 10 01:13:29 titan kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Nov 10 01:13:29 titan kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Nov 10 01:13:29 titan kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Nov 10 01:13:29 titan kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Nov 10 01:13:29 titan kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Nov 10 01:13:29 titan kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Nov 10 01:13:29 titan kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Nov 10 01:13:29 titan kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Nov 10 01:13:29 titan kernel: amdgpu 0000:c1:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Nov 10 01:13:29 titan kernel: amdgpu 0000:c1:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Nov 10 01:13:29 titan kernel: amdgpu 0000:c1:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
Nov 10 01:13:29 titan kernel: amdgpu 0000:c1:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
Nov 10 01:13:29 titan kernel: [drm:dc_dmub_srv_cmd_run_list [amdgpu]] *ERROR* Error queueing DMUB command: status=2
Nov 10 01:13:29 titan kernel: [drm] ring gfx_32790.1.1 was added
Nov 10 01:13:29 titan kernel: [drm] ring compute_32790.2.2 was added
Nov 10 01:13:29 titan kernel: [drm] ring sdma_32790.3.3 was added
Nov 10 01:13:29 titan kernel: [drm] ring gfx_32790.1.1 ib test pass
Nov 10 01:13:29 titan kernel: [drm] ring compute_32790.2.2 ib test pass
Nov 10 01:13:29 titan kernel: [drm] ring sdma_32790.3.3 ib test pass
Nov 10 01:13:29 titan kernel: [drm:dc_dmub_srv_cmd_run_list [amdgpu]] *ERROR* Error queueing DMUB command: status=2
Nov 10 01:13:29 titan kernel: [drm:dc_dmub_srv_cmd_run_list [amdgpu]] *ERROR* Error queueing DMUB command: status=2
Nov 10 01:13:29 titan kernel: OOM killer enabled.
Nov 10 01:13:29 titan kernel: Restarting tasks ... done.
Nov 10 01:13:29 titan kernel: random: crng reseeded on system resumption
Nov 10 01:13:29 titan kwin_wayland_wrapper[2204]: kwin_libinput: Libinput: event0  - AT Translated Set 2 keyboard: client bug: event processing la>
Nov 10 01:13:29 titan rtkit-daemon[1542]: The canary thread is apparently starving. Taking action.
Nov 10 01:13:29 titan systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Nov 10 01:13:29 titan rtkit-daemon[1542]: Demoting known real-time threads.
Nov 10 01:13:29 titan wpa_supplicant[1371]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
Nov 10 01:13:29 titan rtkit-daemon[1542]: Successfully demoted thread 2964 of process 2590.
Nov 10 01:13:29 titan wpa_supplicant[1371]: nl80211: deinit ifname=wlp1s0 disabled_11b_rates=0
Nov 10 01:13:29 titan rtkit-daemon[1542]: Successfully demoted thread 2103 of process 2064.
Nov 10 01:13:29 titan rtkit-daemon[1542]: Successfully demoted thread 2064 of process 2064.
Nov 10 01:13:29 titan rtkit-daemon[1542]: Successfully demoted thread 2101 of process 2066.
Nov 10 01:13:29 titan rtkit-daemon[1542]: Successfully demoted thread 2066 of process 2066.
Nov 10 01:13:29 titan rtkit-daemon[1542]: Successfully demoted thread 2102 of process 2067.
Nov 10 01:13:29 titan rtkit-daemon[1542]: Successfully demoted thread 2067 of process 2067.
Nov 10 01:13:29 titan rtkit-daemon[1542]: Demoted 7 threads.
Nov 10 01:13:29 titan systemd-sleep[5729]: System returned from sleep state.
Nov 10 01:13:29 titan kernel: PM: suspend exit
Nov 10 01:13:29 titan bluetoothd[1329]: Controller resume with wake event 0x0
Nov 10 01:13:29 titan systemd[1]: systemd-suspend.service: Deactivated successfully.
Nov 10 01:13:29 titan systemd[1]: Finished systemd-suspend.service - System Suspend.
Nov 10 01:13:29 titan systemd[1]: Stopped target sleep.target - Sleep.
Nov 10 01:13:29 titan systemd[1]: Reached target suspend.target - Suspend.
Nov 10 01:13:29 titan systemd[1]: Stopped target suspend.target - Suspend.
Nov 10 01:13:29 titan systemd-logind[1349]: Operation 'sleep' finished.
Nov 10 01:13:29 titan ModemManager[1382]: <info>  [sleep-monitor-systemd] system is resuming
Nov 10 01:13:29 titan NetworkManager[1366]: <info>  [1699575209.9216] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Nov 10 01:13:29 titan NetworkManager[1366]: <info>  [1699575209.9217] device (wlp1s0): state change: unmanaged -> unavailable (reason 'managed', s>
Nov 10 01:13:29 titan NetworkManager[1366]: <info>  [1699575209.9225] device (p2p-dev-wlp1s0): state change: unmanaged -> unavailable (reason 'man>
Nov 10 01:13:29 titan NetworkManager[1366]: <info>  [1699575209.9227] manager: NetworkManager state is now DISCONNECTED
Nov 10 01:13:29 titan kernel: [drm:dc_dmub_srv_cmd_run_list [amdgpu]] *ERROR* Error queueing DMUB command: status=2
Nov 10 01:13:29 titan NetworkManager[1366]: <info>  [1699575209.9809] device (wlp1s0): supplicant interface state: internal-starting -> disconnect>
Nov 10 01:13:29 titan NetworkManager[1366]: <info>  [1699575209.9809] device (p2p-dev-wlp1s0): state change: unavailable -> unmanaged (reason 'rem>
Nov 10 01:13:29 titan NetworkManager[1366]: <info>  [1699575209.9812] Wi-Fi P2P device controlled by interface wlp1s0 created
Nov 10 01:13:29 titan NetworkManager[1366]: <info>  [1699575209.9813] manager: (p2p-dev-wlp1s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/Net>
Nov 10 01:13:29 titan NetworkManager[1366]: <info>  [1699575209.9814] device (p2p-dev-wlp1s0): state change: unmanaged -> unavailable (reason 'man>
Nov 10 01:13:29 titan NetworkManager[1366]: <info>  [1699575209.9816] device (wlp1s0): state change: unavailable -> disconnected (reason 'supplica>
Nov 10 01:13:29 titan NetworkManager[1366]: <info>  [1699575209.9820] device (p2p-dev-wlp1s0): state change: unavailable -> disconnected (reason '>
Nov 10 01:13:30 titan kernel: [drm:dc_dmub_srv_cmd_run_list [amdgpu]] *ERROR* Error queueing DMUB command: status=2
Nov 10 01:13:30 titan kernel: [drm:dc_dmub_srv_cmd_run_list [amdgpu]] *ERROR* Error queueing DMUB command: status=2
Nov 10 01:13:30 titan kernel: [drm:dc_dmub_srv_cmd_run_list [amdgpu]] *ERROR* Error queueing DMUB command: status=2
Nov 10 01:13:31 titan kernel: [drm:dc_dmub_srv_cmd_run_list [amdgpu]] *ERROR* Error queueing DMUB command: status=2
Nov 10 01:13:31 titan kernel: [drm:dc_dmub_srv_cmd_run_list [amdgpu]] *ERROR* Error queueing DMUB command: status=2
Nov 10 01:13:31 titan kernel: [drm:dc_dmub_srv_cmd_run_list [amdgpu]] *ERROR* Error queueing DMUB command: status=2
Nov 10 01:13:31 titan kernel: [drm:dc_dmub_srv_cmd_run_list [amdgpu]] *ERROR* Error queueing DMUB command: status=2
Nov 10 01:13:32 titan kernel: [drm:dc_dmub_srv_cmd_run_list [amdgpu]] *ERROR* Error queueing DMUB command: status=2
Nov 10 01:13:32 titan NetworkManager[1366]: <info>  [1699575212.1916] policy: auto-activating connection 'Darknet' (0cebbc3f-b374-43bb-bb58-98315d>
Nov 10 01:13:32 titan NetworkManager[1366]: <info>  [1699575212.1919] device (wlp1s0): Activation: starting connection 'Darknet' (0cebbc3f-b374-43>
Nov 10 01:13:32 titan NetworkManager[1366]: <info>  [1699575212.1919] device (wlp1s0): state change: disconnected -> prepare (reason 'none', sys-i>
Nov 10 01:13:32 titan NetworkManager[1366]: <info>  [1699575212.1920] manager: NetworkManager state is now CONNECTING
Nov 10 01:13:32 titan NetworkManager[1366]: <info>  [1699575212.1921] device (wlp1s0): state change: prepare -> config (reason 'none', sys-iface-s>
Nov 10 01:13:32 titan NetworkManager[1366]: <info>  [1699575212.1923] device (wlp1s0): Activation: (wifi) access point 'Darknet' has security, but>
Nov 10 01:13:32 titan NetworkManager[1366]: <info>  [1699575212.1923] device (wlp1s0): state change: config -> need-auth (reason 'none', sys-iface>
Nov 10 01:13:32 titan NetworkManager[1366]: <info>  [1699575212.1927] device (wlp1s0): state change: need-auth -> prepare (reason 'none', sys-ifac>
Nov 10 01:13:32 titan NetworkManager[1366]: <info>  [1699575212.1928] device (wlp1s0): state change: prepare -> config (reason 'none', sys-iface-s>
Nov 10 01:13:32 titan NetworkManager[1366]: <info>  [1699575212.1929] device (wlp1s0): Activation: (wifi) connection 'Darknet' has security, and s>
Nov 10 01:13:32 titan NetworkManager[1366]: <info>  [1699575212.1930] Config: added 'ssid' value 'Darknet'
Nov 10 01:13:32 titan NetworkManager[1366]: <info>  [1699575212.1930] Config: added 'scan_ssid' value '1'
Nov 10 01:13:32 titan NetworkManager[1366]: <info>  [1699575212.1930] Config: added 'bgscan' value 'simple:30:-70:86400'
Nov 10 01:13:32 titan NetworkManager[1366]: <info>  [1699575212.1930] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Nov 10 01:13:32 titan NetworkManager[1366]: <info>  [1699575212.1930] Config: added 'psk' value '<hidden>'
Nov 10 01:13:32 titan kded5[2263]: "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/2”"
Nov 10 01:13:32 titan DiscoverNotifier[2588]: "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/2”"
Nov 10 01:13:32 titan org.kde.kdeconnect[2532]: "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/2”"
Nov 10 01:13:32 titan plasmashell[3241]: "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/2”"
Nov 10 01:13:32 titan wpa_supplicant[1371]: wlp1s0: SME: Trying to authenticate with b6:fb:e4:0c:c7:e4 (SSID='Darknet' freq=2462 MHz)
Nov 10 01:13:32 titan kernel: wlp1s0: authenticate with b6:fb:e4:0c:c7:e4
Nov 10 01:13:32 titan NetworkManager[1366]: <info>  [1699575212.2314] device (wlp1s0): supplicant interface state: disconnected -> authenticating
Nov 10 01:13:32 titan NetworkManager[1366]: <info>  [1699575212.2314] device (p2p-dev-wlp1s0): supplicant management interface state: disconnected>
Nov 10 01:13:32 titan kernel: wlp1s0: send auth to b6:fb:e4:0c:c7:e4 (try 1/3)
Nov 10 01:13:32 titan wpa_supplicant[1371]: wlp1s0: Trying to associate with b6:fb:e4:0c:c7:e4 (SSID='Darknet' freq=2462 MHz)
Nov 10 01:13:32 te or paste code here

Run scripts/amd_s2idle.py · master · drm / amd · GitLab and look at the report it produces for ideas.

1 Like

@Michael_Schmid please do as suggested above for AMD.

Also, this may be the right path:

So I ran the amd_s2idle.py script for multiple cycles (4) and at the second suspend/cycle my display displayed something but not what I expected:


so thats a nice view to have.

Also here the kernel messages during one cylce:

Nov 14 20:13:33 titan kernel: PM: suspend entry (s2idle)
Nov 14 20:13:33 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:13:33 titan kernel: Filesystems sync: 0.020 seconds
Nov 14 20:13:33 titan kernel: (NULL device *): firmware: direct-loading firmware mediatek/WIFI_MT7922_patch_mcu_1_1_hdr.bin
Nov 14 20:13:33 titan kernel: (NULL device *): firmware: direct-loading firmware mediatek/WIFI_RAM_CODE_MT7922_1.bin
Nov 14 20:13:33 titan kernel: (NULL device *): firmware: direct-loading firmware regulatory.db
Nov 14 20:13:33 titan kernel: (NULL device *): firmware: direct-loading firmware regulatory.db.p7s
Nov 14 20:13:33 titan kernel: (NULL device *): firmware: direct-loading firmware mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin
Nov 14 20:14:22 titan kernel: Freezing user space processes
Nov 14 20:14:22 titan kernel: Freezing user space processes completed (elapsed 0.003 seconds)
Nov 14 20:14:22 titan kernel: OOM killer disabled.
Nov 14 20:14:22 titan kernel: Freezing remaining freezable tasks
Nov 14 20:14:22 titan kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Nov 14 20:14:22 titan kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: wlp1s0: deauthenticating from b6:fb:e4:0c:c7:e4 by local choice (Reason: 3=DEAUTH_LEAVING)
Nov 14 20:14:22 titan kernel: PM: suspend of devices complete after 390.824 msecs
Nov 14 20:14:22 titan kernel: PM: start suspend of devices complete after 393.361 msecs
Nov 14 20:14:22 titan kernel: PM: late suspend of devices complete after 1.646 msecs
Nov 14 20:14:22 titan kernel: ACPI: EC: interrupt blocked
Nov 14 20:14:22 titan kernel: PM: noirq suspend of devices complete after 108.341 msecs
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GP11: LPI: required min power state:D3hot current power state:D3cold
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GP12: LPI: required min power state:D3hot current power state:D3cold
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GPP0: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GPP0: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GPP2: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GPP2: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GPP6: LPI: required min power state:D1 current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GPP6: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GPP5: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GPP5: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GPP7: LPI: required min power state:D1 current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GPP7: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GP11.SWUS: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GP11.SWUS: LPI: Constraint not met; min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GP12.SWUS: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GP12.SWUS: LPI: Constraint not met; min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GPP7.DEV0: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GPP7.DEV0: LPI: Constraint not met; min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GPP2.WWAN: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GPP2.WWAN: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GPP5.RTL8: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GPP5.RTL8: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GPP5.RUSB: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GPP5.RUSB: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GPP6.WLAN: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GPP6.WLAN: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GPP8.NVME: LPI: required min power state:D3hot current power state:D3cold
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GP17.VGA_: LPI: required min power state:D3hot current power state:D3cold
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GP17.AZAL: LPI: required min power state:D3hot current power state:D3cold
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: Constraint not met; min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GP17.HDAU: LPI: required min power state:D3hot current power state:D3cold
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GP17.XHC0: LPI: required min power state:D3hot current power state:D3cold
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GP17.XHC1: LPI: required min power state:D3hot current power state:D3cold
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GP18.IPU_: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GP18.IPU_: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GP19.XHC2: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GP19.XHC2: LPI: Constraint not met; min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GP19.XHC3: LPI: required min power state:D3hot current power state:D3cold
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GP19.XHC4: LPI: required min power state:D3hot current power state:D3cold
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GP19.NHI0: LPI: required min power state:D3hot current power state:D3cold
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PCI0.GP19.NHI1: LPI: required min power state:D3hot current power state:D3cold
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C000: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C000: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C001: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C001: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C002: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C002: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C003: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C003: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C004: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C004: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C005: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C005: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C006: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C006: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C007: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C007: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C008: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C008: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C009: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C009: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C00A: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C00A: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C00B: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C00B: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C00C: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C00C: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C00D: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C00D: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C00E: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C00E: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C00F: LPI: required min power state:D3hot current power state:D0
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C00F: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PLTF.C00F: LPI: Device not power manageable
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PEP_: Successfully transitioned to state screen off
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PEP_: Successfully transitioned to state lps0 ms entry
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PEP_: Successfully transitioned to state lps0 entry
Nov 14 20:14:22 titan kernel: amd_pmc AMDI0009:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 14 20:14:22 titan kernel: amd_pmc AMDI0009:00: AMD_PMC_REGISTER_ARGUMENT:1fe779
Nov 14 20:14:22 titan kernel: amd_pmc AMDI0009:00: AMD_PMC_REGISTER_MESSAGE:9
Nov 14 20:14:22 titan kernel: amd_pmc AMDI0009:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 14 20:14:22 titan kernel: amd_pmc AMDI0009:00: AMD_PMC_REGISTER_ARGUMENT:7e300920
Nov 14 20:14:22 titan kernel: amd_pmc AMDI0009:00: AMD_PMC_REGISTER_MESSAGE:5
Nov 14 20:14:22 titan kernel: amd_pmc AMDI0009:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 14 20:14:22 titan kernel: amd_pmc AMDI0009:00: AMD_PMC_REGISTER_ARGUMENT:8
Nov 14 20:14:22 titan kernel: amd_pmc AMDI0009:00: AMD_PMC_REGISTER_MESSAGE:4
Nov 14 20:14:22 titan kernel: amd_pmc AMDI0009:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 14 20:14:22 titan kernel: amd_pmc AMDI0009:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 14 20:14:22 titan kernel: amd_pmc AMDI0009:00: AMD_PMC_REGISTER_MESSAGE:7
Nov 14 20:14:22 titan kernel: amd_pmc AMDI0009:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 14 20:14:22 titan kernel: amd_pmc AMDI0009:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 14 20:14:22 titan kernel: amd_pmc AMDI0009:00: AMD_PMC_REGISTER_MESSAGE:6
Nov 14 20:14:22 titan kernel: amd_pmc AMDI0009:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 14 20:14:22 titan kernel: amd_pmc AMDI0009:00: AMD_PMC_REGISTER_ARGUMENT:1
Nov 14 20:14:22 titan kernel: amd_pmc AMDI0009:00: AMD_PMC_REGISTER_MESSAGE:3
Nov 14 20:14:22 titan kernel: PM: suspend-to-idle
Nov 14 20:14:22 titan kernel: amd_pmc: SMU idlemask s0i3: 0xffbbeb5
Nov 14 20:14:22 titan kernel: Timekeeping suspended for 7.914 seconds
Nov 14 20:14:22 titan kernel: PM: Triggering wakeup from IRQ 1
Nov 14 20:14:22 titan kernel: PM: Triggering wakeup from IRQ 9
Nov 14 20:14:22 titan kernel: ACPI: PM: ACPI fixed event wakeup
Nov 14 20:14:22 titan kernel: PM: resume from suspend-to-idle
Nov 14 20:14:22 titan kernel: amd_pmc AMDI0009:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 14 20:14:22 titan kernel: amd_pmc AMDI0009:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 14 20:14:22 titan kernel: amd_pmc AMDI0009:00: AMD_PMC_REGISTER_MESSAGE:3
Nov 14 20:14:22 titan kernel: amd_pmc AMDI0009:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 14 20:14:22 titan kernel: amd_pmc AMDI0009:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 14 20:14:22 titan kernel: amd_pmc AMDI0009:00: AMD_PMC_REGISTER_MESSAGE:8
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PEP_: Successfully transitioned to state lps0 exit
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PEP_: Successfully transitioned to state lps0 ms exit
Nov 14 20:14:22 titan kernel: ACPI: \_SB_.PEP_: Successfully transitioned to state screen on
Nov 14 20:14:22 titan kernel: ACPI: EC: interrupt unblocked
Nov 14 20:14:22 titan kernel: PM: noirq resume of devices complete after 171.259 msecs
Nov 14 20:14:22 titan kernel: PM: early resume of devices complete after 3.502 msecs
Nov 14 20:14:22 titan kernel: hpet_rtc_timer_reinit: 18 callbacks suppressed
Nov 14 20:14:22 titan kernel: hpet: Lost 4387 RTC interrupts
Nov 14 20:14:22 titan kernel: nvme nvme0: Shutdown timeout set to 10 seconds
Nov 14 20:14:22 titan kernel: nvme nvme0: 16/0/0 default/read/poll queues
Nov 14 20:14:22 titan kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Nov 14 20:14:22 titan kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Nov 14 20:14:22 titan kernel: [drm] PCIE GART of 512M enabled (table at 0x000000801FD00000).
Nov 14 20:14:22 titan kernel: [drm] PCIE GART of 512M enabled (table at 0x000000801FD00000).
Nov 14 20:14:22 titan kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is resuming...
Nov 14 20:14:22 titan kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is resumed successfully!
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:264
Nov 14 20:14:22 titan kernel: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:272
Nov 14 20:14:22 titan kernel: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:280
Nov 14 20:14:22 titan kernel: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:288
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: [drm] Failed to enable ASSR
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: ------------[ cut here ]------------
Nov 14 20:14:22 titan kernel: WARNING: CPU: 4 PID: 3899 at drivers/gpu/drm/amd/amdgpu/../display/dc/link/protocols/link_edp_panel_control.c:83 dp_>
Nov 14 20:14:22 titan kernel: Modules linked in: ctr ccm rfcomm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device cmac algif_hash algif_skcipher af>
Nov 14 20:14:22 titan kernel:  serio_raw msr parport_pc ppdev lp parport fuse loop efi_pstore configfs ip_tables x_tables autofs4 ext4 crc16 mbcac>
Nov 14 20:14:22 titan kernel: CPU: 4 PID: 3899 Comm: kworker/u32:32 Not tainted 6.5.0-0.deb12.1-rt-amd64 #1  Debian 6.5.3-1~bpo12+1
Nov 14 20:14:22 titan kernel: Hardware name: Framework Laptop 13 (AMD Ryzen 7040Series)/FRANMDCP05, BIOS 03.03 10/17/2023
Nov 14 20:14:22 titan kernel: Workqueue: events_unbound async_run_entry_fn
Nov 14 20:14:22 titan kernel: RIP: 0010:dp_set_panel_mode+0xca/0xe0 [amdgpu]
Nov 14 20:14:22 titan kernel: Code: 00 48 c7 c2 a0 a0 20 c1 e8 63 db 74 ff 48 8b 44 24 08 65 48 2b 04 25 28 00 00 00 75 11 48 83 c4 10 5b 5d 41 5c>
Nov 14 20:14:22 titan kernel: RSP: 0018:ffffb4da84eeb390 EFLAGS: 00010282
Nov 14 20:14:22 titan kernel: RAX: 00000000ffffffff RBX: ffff8bf0413f6800 RCX: ffffffffc0827b10
Nov 14 20:14:22 titan kernel: RDX: 00000000fffffffb RSI: ffff8bf0419c80d0 RDI: 0000000000000000
Nov 14 20:14:22 titan kernel: RBP: 0000000000000001 R08: ffff8bf092da3f20 R09: 000000000000010a
Nov 14 20:14:22 titan kernel: R10: 0000000000000002 R11: 0000000000000000 R12: 0000000000000001
Nov 14 20:14:22 titan kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Nov 14 20:14:22 titan kernel: FS:  0000000000000000(0000) GS:ffff8bf79e700000(0000) knlGS:0000000000000000
Nov 14 20:14:22 titan kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 14 20:14:22 titan kernel: CR2: 00007f9d327fed46 CR3: 000000044a62a000 CR4: 0000000000750ee0
Nov 14 20:14:22 titan kernel: PKRU: 55555554
Nov 14 20:14:22 titan kernel: Call Trace:
Nov 14 20:14:22 titan kernel:  <TASK>
Nov 14 20:14:22 titan kernel:  ? __warn+0x99/0x190
Nov 14 20:14:22 titan kernel:  ? dp_set_panel_mode+0xca/0xe0 [amdgpu]
Nov 14 20:14:22 titan kernel:  ? report_bug+0x1bd/0x1f0
Nov 14 20:14:22 titan kernel:  ? handle_bug+0x41/0x70
Nov 14 20:14:22 titan kernel:  ? exc_invalid_op+0x17/0x70
Nov 14 20:14:22 titan kernel:  ? asm_exc_invalid_op+0x1a/0x20
Nov 14 20:14:22 titan kernel:  ? dp_set_panel_mode+0xca/0xe0 [amdgpu]
Nov 14 20:14:22 titan kernel:  perform_link_training_with_retries+0x203/0x560 [amdgpu]
Nov 14 20:14:22 titan kernel:  ? core_link_write_dpcd+0x8f/0x100 [amdgpu]
Nov 14 20:14:22 titan kernel:  enable_link_dp+0x13a/0x2c0 [amdgpu]
Nov 14 20:14:22 titan kernel:  link_set_dpms_on+0x743/0xcc0 [amdgpu]
Nov 14 20:14:22 titan kernel:  dce110_apply_ctx_to_hw+0x531/0x700 [amdgpu]
Nov 14 20:14:22 titan kernel:  ? dm_read_reg_func+0x3c/0xe0 [amdgpu]
Nov 14 20:14:22 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 14 20:14:22 titan kernel:  ? dcn10_verify_allow_pstate_change_high+0x36/0x3c0 [amdgpu]
Nov 14 20:14:22 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 14 20:14:22 titan kernel:  ? dcn10_wait_for_mpcc_disconnect+0x3a/0x160 [amdgpu]
Nov 14 20:14:22 titan kernel:  dc_commit_state_no_check+0x3ca/0xf20 [amdgpu]
Nov 14 20:14:22 titan kernel:  dc_commit_streams+0x259/0x3c0 [amdgpu]
Nov 14 20:14:22 titan kernel:  amdgpu_dm_atomic_commit_tail+0x630/0x3a60 [amdgpu]
Nov 14 20:14:22 titan kernel:  ? calculate_init_and_vp+0x101/0x210 [amdgpu]
Nov 14 20:14:22 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 14 20:14:22 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 14 20:14:22 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 14 20:14:22 titan kernel:  ? migrate_enable+0xd9/0x150
Nov 14 20:14:22 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 14 20:14:22 titan kernel:  ? dcn314_validate_bandwidth+0x1fe/0x320 [amdgpu]
Nov 14 20:14:22 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 14 20:14:22 titan kernel:  ? ___slab_alloc+0x622/0xaf0
Nov 14 20:14:22 titan kernel:  ? drm_atomic_helper_setup_commit+0x42d/0x840 [drm_kms_helper]
Nov 14 20:14:22 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 14 20:14:22 titan kernel:  ? dma_resv_iter_first_unlocked+0x66/0x70
Nov 14 20:14:22 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 14 20:14:22 titan kernel:  ? dma_resv_get_fences+0x61/0x220
Nov 14 20:14:22 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 14 20:14:22 titan kernel:  ? hubbub31_get_dcc_compression_cap+0xac/0x2a0 [amdgpu]
Nov 14 20:14:22 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 14 20:14:22 titan kernel:  ? amdgpu_dm_plane_fill_plane_buffer_attributes+0x42f/0x510 [amdgpu]
Nov 14 20:14:22 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 14 20:14:22 titan kernel:  ? migrate_enable+0xd9/0x150
Nov 14 20:14:22 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 14 20:14:22 titan kernel:  commit_tail+0x91/0x130 [drm_kms_helper]
Nov 14 20:14:22 titan kernel:  drm_atomic_helper_commit+0x116/0x140 [drm_kms_helper]
Nov 14 20:14:22 titan kernel:  drm_atomic_commit+0x97/0xd0 [drm]
Nov 14 20:14:22 titan kernel:  ? __pfx___drm_printfn_info+0x10/0x10 [drm]
Nov 14 20:14:22 titan kernel:  drm_atomic_helper_commit_duplicated_state+0xcd/0xe0 [drm_kms_helper]
Nov 14 20:14:22 titan kernel:  drm_atomic_helper_resume+0xa8/0x160 [drm_kms_helper]
Nov 14 20:14:22 titan kernel:  dm_resume+0x321/0x7a0 [amdgpu]
Nov 14 20:14:22 titan kernel:  ? srso_alias_return_thunk+0x5/0x7f
Nov 14 20:14:22 titan kernel:  ? _dev_info+0x79/0xa0
Nov 14 20:14:22 titan kernel:  amdgpu_device_ip_resume_phase2+0x4f/0xc0 [amdgpu]
Nov 14 20:14:22 titan kernel:  amdgpu_device_resume+0xbb/0x2c0 [amdgpu]
Nov 14 20:14:22 titan kernel:  ? __pfx_pci_pm_resume+0x10/0x10
Nov 14 20:14:22 titan kernel:  amdgpu_pmops_resume+0x4a/0x80 [amdgpu]
Nov 14 20:14:22 titan kernel:  ? __pfx_pci_pm_resume+0x10/0x10
Nov 14 20:14:22 titan kernel:  dpm_run_callback+0x8c/0x240
Nov 14 20:14:22 titan kernel:  device_resume+0x88/0x190
Nov 14 20:14:22 titan kernel:  async_resume+0x1e/0x60
Nov 14 20:14:22 titan kernel:  async_run_entry_fn+0x2f/0x130
Nov 14 20:14:22 titan kernel:  process_one_work+0x1df/0x440
Nov 14 20:14:22 titan kernel:  worker_thread+0x51/0x390
Nov 14 20:14:22 titan kernel:  ? _raw_spin_lock_irqsave+0x27/0x60
Nov 14 20:14:22 titan kernel:  ? __pfx_worker_thread+0x10/0x10
Nov 14 20:14:22 titan kernel:  kthread+0x114/0x140
Nov 14 20:14:22 titan kernel:  ? __pfx_kthread+0x10/0x10
Nov 14 20:14:22 titan kernel:  ret_from_fork+0x31/0x50
Nov 14 20:14:22 titan kernel:  ? __pfx_kthread+0x10/0x10
Nov 14 20:14:22 titan kernel:  ret_from_fork_asm+0x1b/0x30
Nov 14 20:14:22 titan kernel:  </TASK>
Nov 14 20:14:22 titan kernel: ---[ end trace 0000000000000000 ]---
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: [drm] enabling link 0 failed: 15
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Nov 14 20:14:22 titan kernel: amdgpu 0000:c1:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
Nov 14 20:14:22 titan kernel: amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Nov 14 20:14:22 titan kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Nov 14 20:14:22 titan kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Nov 14 20:14:22 titan kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Nov 14 20:14:22 titan kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Nov 14 20:14:22 titan kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Nov 14 20:14:22 titan kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Nov 14 20:14:22 titan kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Nov 14 20:14:22 titan kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Nov 14 20:14:22 titan kernel: amdgpu 0000:c1:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Nov 14 20:14:22 titan kernel: amdgpu 0000:c1:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Nov 14 20:14:22 titan kernel: amdgpu 0000:c1:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
Nov 14 20:14:22 titan kernel: amdgpu 0000:c1:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: [drm] ring gfx_32791.1.1 was added
Nov 14 20:14:22 titan kernel: [drm] ring compute_32791.2.2 was added
Nov 14 20:14:22 titan kernel: [drm] ring sdma_32791.3.3 was added
Nov 14 20:14:22 titan kernel: [drm] ring gfx_32791.1.1 ib test pass
Nov 14 20:14:22 titan kernel: [drm] ring compute_32791.2.2 ib test pass
Nov 14 20:14:22 titan kernel: [drm] ring sdma_32791.3.3 ib test pass
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: PM: resume of devices complete after 39493.934 msecs
Nov 14 20:14:22 titan kernel: GPIO 5 is active: 0x10141b00
Nov 14 20:14:22 titan kernel: OOM killer enabled.
Nov 14 20:14:22 titan kernel: Restarting tasks ... done.
Nov 14 20:14:22 titan kernel: random: crng reseeded on system resumption
Nov 14 20:14:22 titan kernel: PM: suspend exit

Can you please reproduce using the latest linux-firmware? kernel-firmware / Linux Firmware · GitLab

After you’ve upgraded if you can reproduce a failure still can you upload full report?

1 Like

As mentioned in my initial comment, I already use the latest firmware and still get this error, so an upgrade wouldn’t really help, would it?
But I will reproduce the error later today.

Since you first posted there was a newer DMUB firmware for Phoenix posted. If you can still reproduce this with that updated firmware I suggest opening a bug report in amd gitlab and attaching a full dmesg.

1 Like

Okay thanks for the feedback, I will look into it, maybe kernel.org has a newer then 30th October firmware archive.

Did that and turns out on the 11th november there was an new firmware archive, so I applied that, updated initramfs and et voila it works now. Everything sorted out, thanks everyone! :grin: Happy to have a framework! :blush:

2 Likes

Glad to hear that!
Can you file some bugs with Debian to get the default firmware fixed so more people don’t hit this?

1 Like

Nothing to add, but following. Thanks Mario!

Delighted to hear this. Marking resolved.

1 Like

Hello, I had the same problem with Debian 12,
successfully resolved by exctracting last tarball from here (kernel/git/firmware/linux-firmware.git - Repository of firmware blobs for use with the Linux kernel) into /usr/lib/firmware/

And I comment to tell that updating initramfs is mandatory (didn’t work before with this error in dmesg: firmware: failed to load amdgpu/gc_11_0_1_mes_2.bin (-2) )

So do : update-initramfs -u

Thank you

4 Likes

I installed this package from trixie and the resume issue was resolved: Debian -- Details of package firmware-amd-graphics in trixie

1 Like