System gets stuck randomly

domx93 · 2025-03-18 14:04:06

Hello, I'm using archlinux with kde and wayland on a new laptop since few days. Already three times (two times just today) the screens (internal+usbc) got black, then just internal came back and few seconds after the system got stuck, so that I had to force reboot. I read it can be an issue with mesa, but I'm using the latest one (mesa-1:25.0.1-2). From journalctl -b -1 -p 3 I get:

mar 18 14:48:00 domx-t14s-arch kernel: amdgpu 0000:c3:00.0: amdgpu: ring vcn_unified_0 timeout, signaled seq=3246, emitted seq=3248
mar 18 14:48:00 domx-t14s-arch kernel: amdgpu 0000:c3:00.0: amdgpu: Process information: process RDD Process pid 8887 thread firefox:cs0 pid 22809
mar 18 14:48:02 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: Pageflip timed out! This is a bug in the amdgpu kernel driver
mar 18 14:48:02 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: Please report this at https://gitlab.freedesktop.org/drm/amd/-/issues
mar 18 14:48:02 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: With the output of 'sudo dmesg' and 'journalctl --user-unit plasma-kwin_wayland --boot 0'
mar 18 14:48:03 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: Pageflip timed out! This is a bug in the amdgpu kernel driver
mar 18 14:48:03 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: Please report this at https://gitlab.freedesktop.org/drm/amd/-/issues
mar 18 14:48:03 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: With the output of 'sudo dmesg' and 'journalctl --user-unit plasma-kwin_wayland --boot 0'
mar 18 14:48:04 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: Pageflip timed out! This is a bug in the amdgpu kernel driver
mar 18 14:48:04 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: Please report this at https://gitlab.freedesktop.org/drm/amd/-/issues
mar 18 14:48:04 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: With the output of 'sudo dmesg' and 'journalctl --user-unit plasma-kwin_wayland --boot 0'
mar 18 14:48:05 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: Pageflip timed out! This is a bug in the amdgpu kernel driver
mar 18 14:48:05 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: Please report this at https://gitlab.freedesktop.org/drm/amd/-/issues
mar 18 14:48:05 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: With the output of 'sudo dmesg' and 'journalctl --user-unit plasma-kwin_wayland --boot 0'
mar 18 14:48:06 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: Pageflip timed out! This is a bug in the amdgpu kernel driver
mar 18 14:48:06 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: Please report this at https://gitlab.freedesktop.org/drm/amd/-/issues
mar 18 14:48:06 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: With the output of 'sudo dmesg' and 'journalctl --user-unit plasma-kwin_wayland --boot 0'
mar 18 14:48:07 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: Pageflip timed out! This is a bug in the amdgpu kernel driver
mar 18 14:48:07 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: Please report this at https://gitlab.freedesktop.org/drm/amd/-/issues
mar 18 14:48:07 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: With the output of 'sudo dmesg' and 'journalctl --user-unit plasma-kwin_wayland --boot 0'
mar 18 14:48:08 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: Pageflip timed out! This is a bug in the amdgpu kernel driver
mar 18 14:48:08 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: Please report this at https://gitlab.freedesktop.org/drm/amd/-/issues
mar 18 14:48:08 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: With the output of 'sudo dmesg' and 'journalctl --user-unit plasma-kwin_wayland --boot 0'
mar 18 14:48:09 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: Pageflip timed out! This is a bug in the amdgpu kernel driver
mar 18 14:48:09 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: Please report this at https://gitlab.freedesktop.org/drm/amd/-/issues
mar 18 14:48:09 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: With the output of 'sudo dmesg' and 'journalctl --user-unit plasma-kwin_wayland --boot 0'
mar 18 14:48:11 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: Pageflip timed out! This is a bug in the amdgpu kernel driver
mar 18 14:48:11 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: Please report this at https://gitlab.freedesktop.org/drm/amd/-/issues
mar 18 14:48:11 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: With the output of 'sudo dmesg' and 'journalctl --user-unit plasma-kwin_wayland --boot 0'
mar 18 14:48:11 domx-t14s-arch kernel: amdgpu 0000:c3:00.0: [drm] *ERROR* [CRTC:83:crtc-1] flip_done timed out
mar 18 14:48:12 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: Pageflip timed out! This is a bug in the amdgpu kernel driver
mar 18 14:48:12 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: Please report this at https://gitlab.freedesktop.org/drm/amd/-/issues
mar 18 14:48:12 domx-t14s-arch kwin_wayland[908]: kwin_wayland_drm: With the output of 'sudo dmesg' and 'journalctl --user-unit plasma-kwin_wayland --boot 0'
mar 18 14:48:28 domx-t14s-arch kernel: amdgpu 0000:c3:00.0: [drm] *ERROR* flip_done timed out
mar 18 14:48:28 domx-t14s-arch kernel: amdgpu 0000:c3:00.0: [drm] *ERROR* [CRTC:83:crtc-1] commit wait timed out
mar 18 14:48:38 domx-t14s-arch kernel: amdgpu 0000:c3:00.0: [drm] *ERROR* flip_done timed out
mar 18 14:48:38 domx-t14s-arch kernel: amdgpu 0000:c3:00.0: [drm] *ERROR* [PLANE:52:plane-2] commit wait timed out
mar 18 14:48:38 domx-t14s-arch kernel: [drm:dc_state_remove_stream [amdgpu]] *ERROR* Pipe not found for stream 00000000cc7fba7d !

Can someone help me? Thanks in advance!

domx93 · 2025-03-19 10:25:38

Update: I realized better what happens: both the screens get dark, then just the integrated screen comes back, so I disconnect and reconnect the usb c screen and everything get stuck. I cannot even open a text shell...

pm3840 · 2025-03-20 20:47:06

I got these errors just freeze of display:

Mar 20 15:43:26 kwin_wayland[908]: kwin_wayland_drm: The main thread was hanging temporarily!
Mar 20 16:38:23 kwin_wayland[908]: kwin_wayland_drm: The main thread was hanging temporarily!

domx93 · 2025-03-25 14:00:46

Up

WorMzy · 2025-03-25 15:03:17

Please do not bump. Furthermore, please do not create more than one account.

https://wiki.archlinux.org/title/Genera … es#Bumping
https://terms.archlinux.org/docs/code-o … ckpuppetry

Mod note: Banning the newer account, please continue with your pm3840 account.

seth · 2025-03-25 16:43:02

https://bbs.archlinux.org/viewtopic.php … 8#p2233448 ?

domx93 · 2025-03-28 14:54:12

WorMzy wrote:

Please do not bump. Furthermore, please do not create more than one account.
https://wiki.archlinux.org/title/Genera … es#Bumping
https://terms.archlinux.org/docs/code-o … ckpuppetry
Mod note: Banning the newer account, please continue with your pm3840 account.

I'm sorry for bumping, but the other account is not me, and in my log I have not the error that pm3840 reports.

Anyway I received an update of mesa a couple of days ago, and I hope this solved. I don't know since the problem appears just randomly and not so often, so I'll monitor the situation in the next days. I'll let you know if the problem can be considered solved.

domx93 · 2025-03-31 14:09:19

Not solved
but it happened without external screen, just when I put a youtube video on fullscreen. it's frustrating since I don't even understand what is causing the problem...

seth · 2025-03-31 15:54:07

Did you see the thread I linked in #6 ?

domx93 · 2025-04-03 09:12:41

seth wrote:

Did you see the thread I linked in #6 ?

Hello, in my log there is not "kwin_wayland_drm: The main thread was hanging temporarily!". This was the problem of user pm3840.

domx93 · 2025-04-03 10:08:00

I found out that this bug exist since one year and it looks like there is no solution: https://gitlab.freedesktop.org/drm/amd/-/issues/2950
this is really bad, basically this computer is not seriously usable with linux, I cannot risk it stucks while I'm in a serious meeting - it happened - or before I saved my work. I just regret I didn't buy the intel version, I will never buy again an amd, it's crazy they haven't solved this issue in one year.

seth · 2025-04-03 15:45:11

"processor.max_cstate=1 amdgpu.aspm=0 amdgpu.runpm=0 amdgpu.bapm=0", https://wiki.archlinux.org/title/Kernel_parameters

domx93 · Yesterday 22:48:01

seth wrote:

"processor.max_cstate=1 amdgpu.aspm=0 amdgpu.runpm=0 amdgpu.bapm=0", https://wiki.archlinux.org/title/Kernel_parameters

Thank a lot, I will try to pass these parameters to the kernel, even if I'm not too optimistic since someone reported that disabling the energy saving options didn't solve...

Arch Linux

#1 2025-03-18 14:04:06

System gets stuck randomly

#2 2025-03-19 10:25:38

Re: System gets stuck randomly

#3 2025-03-20 20:47:06

Re: System gets stuck randomly

#4 2025-03-25 14:00:46

Re: System gets stuck randomly

#5 2025-03-25 15:03:17

Re: System gets stuck randomly

#6 2025-03-25 16:43:02

Re: System gets stuck randomly

#7 2025-03-28 14:54:12

Re: System gets stuck randomly

#8 2025-03-31 14:09:19

Re: System gets stuck randomly

#9 2025-03-31 15:54:07

Re: System gets stuck randomly

#10 2025-04-03 09:12:41

Re: System gets stuck randomly

#11 2025-04-03 10:08:00

Re: System gets stuck randomly

#12 2025-04-03 15:45:11

Re: System gets stuck randomly

#13 Yesterday 22:48:01

Re: System gets stuck randomly

Board footer