[kwin] [Bug 455771] Plasma Wayland (5.25.1) freezing glitches on gaming
https://bugs.kde.org/show_bug.cgi?id=455771 Zamundaaa changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #9 from Zamundaaa --- good, let's continue tracking it there then -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455771] Plasma Wayland (5.25.1) freezing glitches on gaming
https://bugs.kde.org/show_bug.cgi?id=455771 --- Comment #8 from McCak --- - Dmesg log (full log) - Xorg log - Any other log(In reply to Zamundaaa from comment #7) > (In reply to McCak from comment #5) > > (In reply to Zamundaaa from comment #4) > > > Where did you export them? kwin_wayland needs to get them. Easiest way to > > > ensure that is to put them into /etc/environment and rebooting > > > > oh yeah turns out the testing was wrong on my end.. yeah after adding those > > env var the problem seems gone..Do u know exactly what happen here? > > Sorry about missing your response. The issue is caused by KWin directly > using buffers from the game to drive the display (direct scanout); the > driver tells KWin that doing that will work and yet when actually trying to > present an image it fails. > > I'll ask around if compositors are expected to handle this situation but I > think this is something the driver has to prevent 100% of the time or things > will get a lot more complicated for compositors. > > Either way, this is a driver bug, can you report it to > https://gitlab.freedesktop.org/drm/amd/-/issues? > The relevant things to mention are that atomic commits fail with direct > scanout on the dedicated GPU, and the error message you found before > (kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin > framebuffer with error -22). If you link the issue here I'll try to provide > any additional information that could help I already report it to there and this is the link https://gitlab.freedesktop.org/drm/amd/-/issues/2075 just ask me there if u need some info.. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455771] Plasma Wayland (5.25.1) freezing glitches on gaming
https://bugs.kde.org/show_bug.cgi?id=455771 --- Comment #7 from Zamundaaa --- (In reply to McCak from comment #5) > (In reply to Zamundaaa from comment #4) > > Where did you export them? kwin_wayland needs to get them. Easiest way to > > ensure that is to put them into /etc/environment and rebooting > > oh yeah turns out the testing was wrong on my end.. yeah after adding those > env var the problem seems gone..Do u know exactly what happen here? Sorry about missing your response. The issue is caused by KWin directly using buffers from the game to drive the display (direct scanout); the driver tells KWin that doing that will work and yet when actually trying to present an image it fails. I'll ask around if compositors are expected to handle this situation but I think this is something the driver has to prevent 100% of the time or things will get a lot more complicated for compositors. Either way, this is a driver bug, can you report it to https://gitlab.freedesktop.org/drm/amd/-/issues? The relevant things to mention are that atomic commits fail with direct scanout on the dedicated GPU, and the error message you found before (kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22). If you link the issue here I'll try to provide any additional information that could help -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455771] Plasma Wayland (5.25.1) freezing glitches on gaming
https://bugs.kde.org/show_bug.cgi?id=455771 Matej Starc changed: What|Removed |Added CC||matej.sta...@gmail.com --- Comment #6 from Matej Starc --- Had the same issue, and it has been fixed by those env variables (at least it hasn't crashed so far). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455771] Plasma Wayland (5.25.1) freezing glitches on gaming
https://bugs.kde.org/show_bug.cgi?id=455771 --- Comment #5 from McCak --- (In reply to Zamundaaa from comment #4) > Where did you export them? kwin_wayland needs to get them. Easiest way to > ensure that is to put them into /etc/environment and rebooting oh yeah turns out the testing was wrong on my end.. yeah after adding those env var the problem seems gone..Do u know exactly what happen here? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455771] Plasma Wayland (5.25.1) freezing glitches on gaming
https://bugs.kde.org/show_bug.cgi?id=455771 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455771] Plasma Wayland (5.25.1) freezing glitches on gaming
https://bugs.kde.org/show_bug.cgi?id=455771 --- Comment #4 from Zamundaaa --- Where did you export them? kwin_wayland needs to get them. Easiest way to ensure that is to put them into /etc/environment and rebooting -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455771] Plasma Wayland (5.25.1) freezing glitches on gaming
https://bugs.kde.org/show_bug.cgi?id=455771 --- Comment #3 from McCak --- (In reply to Zamundaaa from comment #1) > This sounds a lot like a driver bug, if the atomic test works, the atomic > commit must not fail. > > I assume you're running the games on the dedicated GPU, but displaying them > on the laptop screen? > Does setting one or both of these environment variables make a difference? > KWIN_DRM_USE_MODIFIERS=0 > KWIN_DRM_NO_DIRECT_SCANOUT=1 Alr.. tried that by exporting those env var and making sure its already loaded.. same issue still happen.. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455771] Plasma Wayland (5.25.1) freezing glitches on gaming
https://bugs.kde.org/show_bug.cgi?id=455771 --- Comment #2 from McCak --- (In reply to Zamundaaa from comment #1) > This sounds a lot like a driver bug, if the atomic test works, the atomic > commit must not fail. > > I assume you're running the games on the dedicated GPU, but displaying them > on the laptop screen? > Does setting one or both of these environment variables make a difference? > KWIN_DRM_USE_MODIFIERS=0 > KWIN_DRM_NO_DIRECT_SCANOUT=1 No.. I try to run the game on dedicated GPU but on external monitor which is connected directly to the dGPU.. the laptop monitor is disabled.. but i will try your method and will report it.. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455771] Plasma Wayland (5.25.1) freezing glitches on gaming
https://bugs.kde.org/show_bug.cgi?id=455771 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com --- Comment #1 from Zamundaaa --- This sounds a lot like a driver bug, if the atomic test works, the atomic commit must not fail. I assume you're running the games on the dedicated GPU, but displaying them on the laptop screen? Does setting one or both of these environment variables make a difference? KWIN_DRM_USE_MODIFIERS=0 KWIN_DRM_NO_DIRECT_SCANOUT=1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455771] Plasma Wayland (5.25.1) freezing glitches on gaming
https://bugs.kde.org/show_bug.cgi?id=455771 Vlad Zahorodnii changed: What|Removed |Added Component|wayland-generic |platform-drm Severity|major |normal -- You are receiving this mail because: You are watching all bug changes.
