April 18, 2026, 5:56pm 1

I’m running kernel 7.0.0-1-cachyos on a Miniforums Venus UM790 / F7BSC mini‑PC. BIOS version is 1.09 (2023‑11‑20). There are no newer BIOS updates available.

The system continues running normally, but I’m seeing a non‑fatal AMDGPU Oops in the logs. The GPU resets cleanly and the desktop keeps working.

lspci -nn | grep -i vga output:
c4:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev c1)

journalctl -k -p err | grep -i amdgpu output:

Apr 18 11:38:03 cachyos-um790 kernel:  intel_rapl_msr amd_atl intel_rapl_common iwlmvm mac80211 kvm_amd ptp ccp pps_core libarc4 spd5118 kvm r8169 iwlwifi irqbypass realtek ghash_clmulni_intel snd_usb_audio aesni_intel snd_usbmidi_lib mdio_devres rapl pcspkr cfg80211 snd_hwdep uvcvideo i2c_piix4 thunderbolt k10temp libphy snd_ump uvc i2c_smbus snd_rawmidi rfkill mdio_bus videobuf2_vmalloc snd_seq_device videobuf2_memops snd_pcm videobuf2_v4l2 snd_timer i2c_hid_acpi i2c_hid videobuf2_common snd amd_pmc videodev soundcore mousedev mc joydev mac_hid ip6t_REJECT xt_hl ip6t_rt ipt_REJECT xt_LOG nf_log_syslog xt_multiport nft_limit xt_limit xt_addrtype nft_reject_inet nf_reject_ipv6 xt_tcpudp nf_reject_ipv4 nft_reject nft_chain_nat xt_conntrack nf_nat nft_compat nf_conntrack x_tables nf_defrag_ipv6 nf_defrag_ipv4 nf_tables dm_mod ntsync pkcs8_key_parser crypto_user i2c_dev nfnetlink zram 842_decompress 842_compress lz4hc_compress lz4_compress uas usb_storage amdgpu drm_panel_backlight_quirks drm_buddy drm_suballoc_helper i2c_algo_bit drm_exec
Apr 18 11:38:03 cachyos-um790 kernel: RIP: 0010:dcn31_program_compbuf_size+0x20e/0x220 [amdgpu]
Apr 18 11:38:03 cachyos-um790 kernel:  dcn20_optimize_bandwidth+0x110/0x210 [amdgpu d9bec018b441ac14e1335ecd9893829765e51a4c]
Apr 18 11:38:03 cachyos-um790 kernel:  dc_commit_state_no_check+0x14ff/0x18a0 [amdgpu d9bec018b441ac14e1335ecd9893829765e51a4c]
Apr 18 11:38:03 cachyos-um790 kernel:  dc_commit_streams+0x471/0x640 [amdgpu d9bec018b441ac14e1335ecd9893829765e51a4c]
Apr 18 11:38:03 cachyos-um790 kernel:  amdgpu_dm_atomic_commit_tail+0x903/0x4430 [amdgpu d9bec018b441ac14e1335ecd9893829765e51a4c]
Apr 18 11:38:03 cachyos-um790 kernel:  ? dm_read_reg_func+0x64/0xd0 [amdgpu d9bec018b441ac14e1335ecd9893829765e51a4c]
Apr 18 11:38:03 cachyos-um790 kernel:  ? generic_reg_get+0x21/0x40 [amdgpu d9bec018b441ac14e1335ecd9893829765e51a4c]
Apr 18 11:38:03 cachyos-um790 kernel:  ? optc1_get_crtc_scanoutpos+0xeb/0x120 [amdgpu d9bec018b441ac14e1335ecd9893829765e51a4c]
Apr 18 11:38:03 cachyos-um790 kernel:  ? dc_stream_get_scanoutpos+0x10a/0x130 [amdgpu d9bec018b441ac14e1335ecd9893829765e51a4c]
Apr 18 11:38:03 cachyos-um790 kernel:  ? dm_crtc_get_scanoutpos+0xd0/0x130 [amdgpu d9bec018b441ac14e1335ecd9893829765e51a4c]
Apr 18 11:38:03 cachyos-um790 kernel:  ? amdgpu_crtc_get_scanout_position+0x8b/0x130 [amdgpu d9bec018b441ac14e1335ecd9893829765e51a4c]
Apr 18 11:38:03 cachyos-um790 kernel:  ? __pfx_amdgpu_crtc_get_scanout_position+0x10/0x10 [amdgpu d9bec018b441ac14e1335ecd9893829765e51a4c]
Apr 18 11:38:03 cachyos-um790 kernel:  amdgpu_drm_ioctl+0x42/0x80 [amdgpu d9bec018b441ac14e1335ecd9893829765e51a4c]

This appears to be a DCN (display engine) crash during an atomic commit. The same hardware was stable on earlier kernels. This may be a regression in AMDGPU DCN interacting with older AGESA firmware.

It happened when I came back to my desk after being away for 30 minutes. I don’t think the screens had gone to sleep or powersaved, but I can’t remember, I just saw the error triggered when I moved the mouse (habit because it’s the wake up trigger) for the first time after returning.

If needed, I can provide full dmesg logs or test additional kernels.

Hi

I used to have CachyOS installed with the exact same problem with a previous kernel one or two months back. I found out, that it happend most when the GPU switches power states. For example, if I’m in a game and switch to the desktop and back to the game. It starts with flickering and artifacts then it crashs. I’m pretty sure, it has to do with the power states of the GPU, because….. I am right now on Windows 11 and it happens here in the exact same way with the exact same game. But it’s not just this particular game. It happened on other games too. This must be a bug in the driver somewhere.

Edit: I have a AMD RX 9070XT

1 Like