Random Indefinite System Hang

  1. Problem

    My display shall apparently randomly freeze when I’ve been using anything in fullscreen for a while. This can be a Steam game, or even (yesterday) a video on Firefox. I thought that this was due to package corruption in my old openSUSE Tumbleweed installation. However, this appears to occur on fedora-kde workstation-wg f40 too, barely a day after installation.

    Nothing appears in journalctl -b -1 due to the system not even respond to SysRq commands, necessitating that I utilize the motherboard’s reset switch, so I’ve no useful logging. Leaving the system (in the times when SysRq doesn’t work) appears to cause it to indefinitely hang.

    I am confident that this relates to my hardware somehow.

  2. Cause

    It appears to coincide with new hardware. However, a kernel change could well have occurred when I reinstalled to my new hardware, too:

    is all which I know changed when this first occurred.

  3. Related Issues

    1. Prism Launcher consistently kills X, sometimes Wayland too. · Issue #2139 · PrismLauncher/PrismLauncher · GitHub
    2. Where to report XWayland crash? The cause matters, right? - Applications - openSUSE Forums
    3. I’ve not reported it yet [1] to Sign in · GitLab, but I intend to.
  4. Workarounds

    Not rendering anything in fullscreen appears to work.


  1. Issues · Mesa / mesa · GitLab ↩︎

Something very similar happened again today, but it was different - I could only see the mouse (stuck to the bottom left corner of the display) and all else was suddenly black.

Unusually, the system remained operative (solely ascertainable in retrospect, since as the SysRq command outputs demonstrate, it didn’t respond to Alt+SysRq+B for reinitialization) so I have logs:

Mar 29 18:08:24 sayw4i kernel: amdgpu 0000:5a:00.0: [drm] Cannot find any crtc or sizes
Mar 29 18:08:24 sayw4i kwin_wayland[1729]: kwin_core: Applying output config failed!
Mar 29 18:08:27 sayw4i kernel: amdgpu 0000:5a:00.0: [drm] Cannot find any crtc or sizes
Mar 29 18:08:27 sayw4i kwin_wayland[1729]: kwin_core: Applying output config failed!
Mar 29 18:08:30 sayw4i kernel: amdgpu 0000:5a:00.0: [drm] Cannot find any crtc or sizes
Mar 29 18:08:30 sayw4i kwin_wayland[1729]: kwin_core: Applying output config failed!
Mar 29 18:08:34 sayw4i kernel: amdgpu 0000:5a:00.0: [drm] Cannot find any crtc or sizes
Mar 29 18:08:34 sayw4i kwin_wayland[1729]: kwin_core: Applying output config failed!
Mar 29 18:08:37 sayw4i kernel: amdgpu 0000:5a:00.0: [drm] Cannot find any crtc or sizes
Mar 29 18:08:37 sayw4i kwin_wayland[1729]: kwin_core: Applying output config failed!
Mar 29 18:08:40 sayw4i kernel: amdgpu 0000:5a:00.0: [drm] Cannot find any crtc or sizes
Mar 29 18:08:40 sayw4i kwin_wayland[1729]: kwin_core: Applying output config failed!
Mar 29 18:08:44 sayw4i kernel: amdgpu 0000:5a:00.0: [drm] Cannot find any crtc or sizes
Mar 29 18:08:44 sayw4i kwin_wayland[1729]: kwin_core: Applying output config failed!
Mar 29 18:08:47 sayw4i kernel: amdgpu 0000:5a:00.0: [drm] Cannot find any crtc or sizes
Mar 29 18:08:47 sayw4i kwin_wayland[1729]: kwin_core: Applying output config failed!
Mar 29 18:08:50 sayw4i kernel: amdgpu 0000:5a:00.0: [drm] Cannot find any crtc or sizes
Mar 29 18:08:50 sayw4i kwin_wayland[1729]: kwin_core: Applying output config failed!
Mar 29 18:08:54 sayw4i code-tunnel-insiders[44544]: [2024-03-29 18:08:54] debug [tunnels::connections::ws] sent liveness ping
Mar 29 18:08:54 sayw4i code-tunnel-insiders[44544]: [2024-03-29 18:08:54] debug [tunnels::connections::ws] received liveness pong
Mar 29 18:08:54 sayw4i kernel: amdgpu 0000:5a:00.0: [drm] Cannot find any crtc or sizes
Mar 29 18:08:54 sayw4i kwin_wayland[1729]: kwin_core: Applying output config failed!
Mar 29 18:08:57 sayw4i kernel: amdgpu 0000:5a:00.0: [drm] Cannot find any crtc or sizes
Mar 29 18:08:57 sayw4i kwin_wayland[1729]: kwin_core: Applying output config failed!
Mar 29 18:08:59 sayw4i pcscd[17230]: 00000000 auth.c:143:IsClientAuthorized() Process 114737 (user: 1000) is NOT authorized for action: access_pcsc
Mar 29 18:08:59 sayw4i pcscd[17230]: 00000090 winscard_svc.c:355:ContextThread() Rejected unauthorized PC/SC client
Mar 29 18:08:59 sayw4i pcscd[17230]: 00010921 auth.c:143:IsClientAuthorized() Process 114737 (user: 1000) is NOT authorized for action: access_pcsc
Mar 29 18:08:59 sayw4i pcscd[17230]: 00000035 winscard_svc.c:355:ContextThread() Rejected unauthorized PC/SC client
Mar 29 18:08:59 sayw4i pcscd[17230]: 00010711 auth.c:143:IsClientAuthorized() Process 114737 (user: 1000) is NOT authorized for action: access_pcsc
Mar 29 18:08:59 sayw4i pcscd[17230]: 00000044 winscard_svc.c:355:ContextThread() Rejected unauthorized PC/SC client
Mar 29 18:08:59 sayw4i pcscd[17230]: 00010179 auth.c:143:IsClientAuthorized() Process 114737 (user: 1000) is NOT authorized for action: access_pcsc
Mar 29 18:08:59 sayw4i pcscd[17230]: 00000039 winscard_svc.c:355:ContextThread() Rejected unauthorized PC/SC client
Mar 29 18:09:00 sayw4i kernel: amdgpu 0000:5a:00.0: [drm] Cannot find any crtc or sizes
Mar 29 18:09:00 sayw4i kwin_wayland[1729]: kwin_core: Applying output config failed!
Mar 29 18:09:03 sayw4i kernel: sysrq: Emergency Sync
Mar 29 18:09:03 sayw4i kernel: Emergency Sync complete
Mar 29 18:09:04 sayw4i kernel: amdgpu 0000:5a:00.0: [drm] Cannot find any crtc or sizes
Mar 29 18:09:04 sayw4i kwin_wayland[1729]: kwin_core: Applying output config failed!
Mar 29 18:09:06 sayw4i kernel: sysrq: This sysrq operation is disabled.
Mar 29 18:09:07 sayw4i kernel: sysrq: This sysrq operation is disabled.
Mar 29 18:09:07 sayw4i kernel: amdgpu 0000:5a:00.0: [drm] Cannot find any crtc or sizes
Mar 29 18:09:07 sayw4i kwin_wayland[1729]: kwin_core: Applying output config failed!
Mar 29 18:09:10 sayw4i kernel: amdgpu 0000:5a:00.0: [drm] Cannot find any crtc or sizes
Mar 29 18:09:10 sayw4i kwin_wayland[1729]: kwin_core: Applying output config failed!
Mar 29 18:09:12 sayw4i kernel: sysrq: This sysrq operation is disabled.
Mar 29 18:09:14 sayw4i kernel: amdgpu 0000:5a:00.0: [drm] Cannot find any crtc or sizes
Mar 29 18:09:14 sayw4i kwin_wayland[1729]: kwin_core: Applying output config failed!
Mar 29 18:09:17 sayw4i kernel: amdgpu 0000:5a:00.0: [drm] Cannot find any crtc or sizes
Mar 29 18:09:17 sayw4i kwin_wayland[1729]: kwin_core: Applying output config failed!
Mar 29 18:09:21 sayw4i kernel: amdgpu 0000:5a:00.0: [drm] Cannot find any crtc or sizes
Mar 29 18:09:21 sayw4i kwin_wayland[1729]: kwin_core: Applying output config failed!
Mar 29 18:09:24 sayw4i kernel: amdgpu 0000:5a:00.0: [drm] Cannot find any crtc or sizes
Mar 29 18:09:24 sayw4i kwin_wayland[1729]: kwin_core: Applying output config failed!
Mar 29 18:09:27 sayw4i kernel: amdgpu 0000:5a:00.0: [drm] Cannot find any crtc or sizes
Mar 29 18:09:27 sayw4i kwin_wayland[1729]: kwin_core: Applying output config failed!
Mar 29 18:09:31 sayw4i kernel: amdgpu 0000:5a:00.0: [drm] Cannot find any crtc or sizes
Mar 29 18:09:31 sayw4i kwin_wayland[1729]: kwin_core: Applying output config failed!
Mar 29 18:09:34 sayw4i systemd-logind[1124]: Power key pressed short.
Mar 29 18:09:34 sayw4i kernel: amdgpu 0000:5a:00.0: [drm] Cannot find any crtc or sizes
Mar 29 18:09:34 sayw4i kwin_wayland[1729]: kwin_core: Applying output config failed!

I think there’s something going on with KWin or my graphics driver, or both.

Please, stop proposing all your issues as Common Issues . So far, none of your issues were shown to be common enough to be placed in that category. Start asking and debugging them in Ask Fedora , and if one proves to be a general problem, it can be nominated afterwards.

3 Likes

From Proposed Common Issues to Ask Fedora

@kparal, I’ll do that.

I was under the impression that asking at the forum was standard protocol for bug reports. It is for KDE and openSUSE. Is that true, and these are mere miscategorized, or should they go straight to Bugzilla first?

I ask because Navigating Fedora Discussion — Tags, Categories, and Concepts doesn’t appear to cover this.

Regardless, these aren’t questions per se, so is Ask Fedora certainly correct?

Yes, I think that’s the best approach.

It is. And thanks for this comment — it helps explain why people keep landing these kinds of posts here instead of there. The “Ask Fedora” name has some nice history now, so I’m hesitant to suggest a change to that. In my mind, bug reports like this do have an implicit question — or, in fact, questions:

  • What’s going wrong?
  • Does anyone else have a similar problem?
  • How can I fix it?
  • If there’s no fix yet, what’s next in finding one?

and so on. But, I get how that might not be obvious!

And speaking of categorizing things… If we want to continue this topic, it should probably go to Site Help & Feedback :classic_smiley:

2 Likes

Thank you, @mattdm. That was comprehensive.

1 Like