Bug 497386 - KDE 6 with wayland random freezing (GPU hang) with intel i915 DRM driver
Summary: KDE 6 with wayland random freezing (GPU hang) with intel i915 DRM driver
Status: REPORTED
Alias: None
Product: neon
Classification: KDE Neon
Component: Packages User Edition (other bugs)
Version First Reported In: unspecified
Platform: Neon Linux
: NOR grave
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-12 18:47 UTC by Alfeno Rodrigues
Modified: 2025-06-09 12:49 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
attachment-3280632-0.html (1.94 KB, text/html)
2025-06-09 12:49 UTC, Alfeno Rodrigues
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alfeno Rodrigues 2024-12-12 18:47:25 UTC
***
Unfortunately, I don't have much information about this bug.  After release KDE 6 with Wayland, I'm having random screen freezing caused by DRM Driver hang.

Below, I have DRM output on dmesg.

[12433.110335] i915 0000:00:02.0: [drm] GPU HANG: ecode 8:0:00000000
[12433.111350] i915 0000:00:02.0: [drm] Resetting rcs0 for stopped heartbeat on rc
***

SUMMARY

STEPS TO REPRODUCE
1.  I don't have the steps to reproduce. It's happening random form.

OBSERVED RESULT
     Screen random freezing

SOFTWARE/OS VERSIONS

   Linux/KDE Plasma:  KDE Neon 24.04 (noble)
   KDE Plasma Version:  6.2.4
   KDE Frameworks Version: 6.8.0
   Qt Version: 6.8.1

ADDITIONAL INFORMATION

   Operating System: KDE neon 6.2
   Kernel Version: 6.8.0-50-generic (64-bit)
   Graphics Platform: Wayland
   Processors: 4 × Intel® Core™ i7-5500U CPU @ 2.40GHz
   Memory: 11,6 GB of RAM
   Graphics Processor: Mesa Intel® HD Graphics 5500
   Manufacturer: Dell Inc.
   Product Name: Inspiron 5548
   System Version: A10
Comment 1 Marco Schmidlin 2025-06-09 07:18:03 UTC
Having the same issue with the latest 6.4 beta 2 on kubuntu 25.04

some logs:
```
1password[4980]: [4980:0609/091032.652545:ERROR:gpu_process_host.cc(953)] GPU process exited unexpectedly: exit_code=512
kwin_wayland_wrapper[4583]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
kernel: Fence expiration time out i915-0000:00:02.0:1password[38455]:2!
kernel: Fence expiration time out i915-0000:00:02.0:Xwayland[4659]:53c!
kernel: Fence expiration time out i915-0000:00:02.0:konsole<37864>:2!
kernel: i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
kernel: i915 0000:00:02.0: [drm] 1password[38455] context reset due to GPU hang
kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:1:84dfbffc, in 1password [38455]

``` 

I have these glitches now and then. Not only related to 1password (running on xwayland)
Comment 2 Alfeno Rodrigues 2025-06-09 12:49:53 UTC
Created attachment 182113 [details]
attachment-3280632-0.html

My notebook has two GPU (intel & AMD). Both GPU hang.

KDE teams wish some AMD's GPU hang logs?

Em seg., 9 de jun. de 2025 às 04:18, Marco Schmidlin <
bugzilla_noreply@kde.org> escreveu:

> https://bugs.kde.org/show_bug.cgi?id=497386
>
> --- Comment #1 from Marco Schmidlin <nerumo@gmail.com> ---
> Having the same issue with the latest 6.4 beta 2 on kubuntu 25.04
>
> some logs:
> ```
> 1password[4980]: [4980:0609/091032.652545:ERROR:gpu_process_host.cc(953)]
> GPU
> process exited unexpectedly: exit_code=512
> kwin_wayland_wrapper[4583]: kf.windowsystem: static bool
> KX11Extras::mapViewport() may only be used on X11
> kernel: Fence expiration time out i915-0000:00:02.0:1password[38455]:2!
> kernel: Fence expiration time out i915-0000:00:02.0:Xwayland[4659]:53c!
> kernel: Fence expiration time out i915-0000:00:02.0:konsole<37864>:2!
> kernel: i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
> kernel: i915 0000:00:02.0: [drm] 1password[38455] context reset due to GPU
> hang
> kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:1:84dfbffc, in
> 1password
> [38455]
>
> ```
>
> I have these glitches now and then. Not only related to 1password (running
> on
> xwayland)
>
> --
> You are receiving this mail because:
> You reported the bug.