[kwin] [Bug 479845] The current Wayland GPU recovery experience (AMD) is not ideal with AMS disabled

https://bugs.kde.org/show_bug.cgi?id=479845 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED

[kwin] [Bug 479845] The current Wayland GPU recovery experience (AMD) is not ideal with AMS disabled

https://bugs.kde.org/show_bug.cgi?id=479845 Gurenko Alex changed: What|Removed |Added CC||agure...@protonmail.com -- You are receiving th

[kwin] [Bug 479845] The current Wayland GPU recovery experience (AMD) is not ideal with AMS disabled

https://bugs.kde.org/show_bug.cgi?id=479845 --- Comment #7 from fililip --- Personally, I don't think there's a point to maintaining legacy modesetting (even if there's still no tearing support for atomic), unless it's actually used on some devices (it's great for my non-VRR laptop; with a 60Hz d

[kwin] [Bug 479845] The current Wayland GPU recovery experience (AMD) is not ideal with AMS disabled

https://bugs.kde.org/show_bug.cgi?id=479845 Nate Graham changed: What|Removed |Added Summary|The current Wayland GPU |The current Wayland GPU |recove

[kwin] [Bug 479845] The current Wayland GPU recovery experience (AMD) is not ideal

https://bugs.kde.org/show_bug.cgi?id=479845 --- Comment #5 from fililip --- Oh, I noticed one important thing - I was using the legacy DRM API (KWIN_DRM_NO_AMS=1) for tearing support. After disabling it, on latest Mesa 24.1 (dev) stuff works fine even on Plasma 5. Sorry for the trouble. > amdgpu

[kwin] [Bug 479845] The current Wayland GPU recovery experience (AMD) is not ideal

https://bugs.kde.org/show_bug.cgi?id=479845 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com --- Comment #4 from Zamundaaa

[kwin] [Bug 479845] The current Wayland GPU recovery experience (AMD) is not ideal

https://bugs.kde.org/show_bug.cgi?id=479845 Nate Graham changed: What|Removed |Added Resolution|UPSTREAM|--- Status|NEEDSINFO

[kwin] [Bug 479845] The current Wayland GPU recovery experience (AMD) is not ideal

https://bugs.kde.org/show_bug.cgi?id=479845 --- Comment #3 from fililip --- > GPU reset handling is something that's very WIP throughout the stack By the stack do you mean kwin, upstream, or both? I thought kwin already had GPU recovery support for Wayland, I might be wrong though (unless what's

[kwin] [Bug 479845] The current Wayland GPU recovery experience (AMD) is not ideal

https://bugs.kde.org/show_bug.cgi?id=479845 David Edmundson changed: What|Removed |Added Resolution|--- |UPSTREAM CC|

[kwin] [Bug 479845] The current Wayland GPU recovery experience (AMD) is not ideal

https://bugs.kde.org/show_bug.cgi?id=479845 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail beca

[kwin] [Bug 479845] The current Wayland GPU recovery experience (AMD) is not ideal

https://bugs.kde.org/show_bug.cgi?id=479845 --- Comment #1 from fililip --- Don't know if it's related to the issue (sorry if it isn't), but I tried applying this MR: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27097 on top of Mesa 24.0.0-rc1 (and the linked patches against Linux 6.

[kwin] [Bug 479845] The current Wayland GPU recovery experience (AMD) is not ideal

https://bugs.kde.org/show_bug.cgi?id=479845 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail becau