Bug 465121 - Hangs / freeze on Wayland when opening/closing apps
Summary: Hangs / freeze on Wayland when opening/closing apps
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: 5.26.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-01 14:28 UTC by Thiago Sueto
Modified: 2023-02-01 15:10 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thiago Sueto 2023-02-01 14:28:39 UTC
SUMMARY
Since a few versions ago I've been experiencing a few hangs / freezes when closing apps. Only now did I get logs for it.

Here's the error message from `sudo journalctl -f` (lapinetouch is the machine hostname):

fev 01 11:12:55 lapinetouch kernel: Asynchronous wait on fence 0000:00:02.0:kwin_wayland[1936]:6330 timed out (hint:intel_atomic_commit_ready [i915])
fev 01 11:12:55 lapinetouch kernel: Asynchronous wait on fence 0000:00:02.0:kwin_wayland[1936]:632e timed out (hint:intel_atomic_commit_ready [i915])
fev 01 11:12:59 lapinetouch kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 8:0:00000000
fev 01 11:12:59 lapinetouch kernel: i915 0000:00:02.0: [drm] Resetting rcs0 for stopped heartbeat on rcs0

STEPS TO REPRODUCE

Open or close a lot windows at a time, eventually you can reproduce the issue

SOFTWARE/OS VERSIONS

Operating System: openSUSE Tumbleweed 20230118
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 6.1.6-1-vanilla (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i7-5500U CPU @ 2.40GHz
Memory: 7.7 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500
Manufacturer: Dell Inc.
Product Name: Inspiron 7348
System Version: A13

ADDITIONAL INFORMATION

Just today a user on reddit mentioned a similar thing with the same log message: https://www.reddit.com/r/kde/comments/10qquun/comment/j6rs0dk/?utm_source=share&utm_medium=web2x&context=3
Comment 1 Zamundaaa 2023-02-01 14:39:06 UTC
This looks like a driver bug: https://gitlab.freedesktop.org/drm/intel/-/issues/4948
Comment 2 AWK 2023-02-01 14:41:12 UTC
I'm the reddit user mentioned in the comment. I see a similar log:

jan 29 22:22:05 fedora kernel: Asynchronous wait on fence 0000:00:02.0:kwin_wayland[1362]:13860f4 timed out (hint:intel_atomic_commit_ready [i915])
jan 29 22:22:05 fedora kernel: Asynchronous wait on fence 0000:00:02.0:kwin_wayland[1362]:13860f2 timed out (hint:intel_atomic_commit_ready [i915])
jan 29 22:22:09 fedora kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:1:859ffffb, in chrome [173607]
jan 29 22:22:09 fedora kernel: i915 0000:00:02.0: [drm] Resetting rcs0 for stopped heartbeat on rcs0
jan 29 22:22:09 fedora kernel: i915 0000:00:02.0: [drm] chrome[173607] context reset due to GPU hang

My system is 

OS: Fedora Linux 36 (Thirty Six) x86_64 
Host: XPS 13 9310 2-in-1 
Kernel: 6.1.6-100.fc36.x86_64 
Resolution: 2560x1080 
DE: Plasma 5.26.4 
WM: kwin 
Theme: [Plasma], Adwaita [GTK2] 
Icons: [Plasma], breeze [GTK2/3] 
CPU: 11th Gen Intel i7-1165G7 (8) @ 4.700GHz 
GPU: Intel TigerLake-LP GT2 [Iris Xe Graphics] 
Memory: 10274MiB / 31811MiB
Comment 3 Zamundaaa 2023-02-01 15:10:18 UTC
Please add that information to the Intel issue