Bug 470581 - kwin_scene_opengl: A graphics reset not attributable to the current GL context occurred
Summary: kwin_scene_opengl: A graphics reset not attributable to the current GL contex...
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (other bugs)
Version First Reported In: 5.27.5
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
: 475174 (view as bug list)
Depends on:
Blocks:
 
Reported: 2023-06-03 10:13 UTC by Germano Massullo (Thetra)
Modified: 2023-10-04 23:03 UTC (History)
3 users (show)

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


Attachments
journalctl (2.40 MB, text/plain)
2023-06-03 10:13 UTC, Germano Massullo (Thetra)
Details
glxinfo (87.48 KB, text/plain)
2023-06-03 10:13 UTC, Germano Massullo (Thetra)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Germano Massullo (Thetra) 2023-06-03 10:13:39 UTC
Created attachment 159433 [details]
journalctl

This [1] amdgpu driver transient crash caused kwin to no longer recover, flooding logs with
=====
kwin_scene_opengl: A graphics reset not attributable to the current GL context occurred
[...]
=====
messages. To recover the machine I had to terminate the Plasma session from TTY console.
plasma-desktop-5.27.5
Logs attached


[1]: https://gitlab.freedesktop.org/drm/amd/-/issues/2606
Comment 1 Germano Massullo (Thetra) 2023-06-03 10:13:59 UTC
Created attachment 159434 [details]
glxinfo
Comment 2 Zamundaaa 2023-06-06 14:03:46 UTC
This is a driver bug, should be fixed with https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/22290
Comment 3 postix 2023-10-03 14:43:22 UTC
*** Bug 475174 has been marked as a duplicate of this bug. ***
Comment 4 postix 2023-10-03 14:44:58 UTC
(In reply to Zamundaaa from comment #2)
> This is a driver bug, should be fixed with
> https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/22290

Do you know if this fix is part Mesa 23.1.8? 
I'd have expected it as the MR was merged 5 months ago and 23.1.8 tagged a week ago, but as of the duplicate #475174 the issue still occurs.
Comment 5 Zamundaaa 2023-10-04 23:03:15 UTC
Sadly it was not backported, it's only in 23.2