You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Godot 4 has been causing this error to appear in dmesg since some time after March 12th 2021 (some time after Godot Wild Jam #31 and commit bf309b8).
[1186.885461] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered
Now, it makes KWin spam notifications about a GPU reset, and flickering the the screen until I turn off compositing. VLC used to do something, so I assumed to was a mesa issue and didn't report it. However, now Godot 4 is the only app I use that causes this. This only happens on X11, no issues on Plasma Wayland. Restarting KWin allows me to turn on compositing again.
Steps to reproduce
Opening a 3D project in the editor or running one from the launcher will cause this.
Edit: It only seems to be a few projects that are causing this and it doesn't happen unless I reboot and go into X11 first, it wouldn't happen when I only logged out of Wayland and logged into X11...
Edit 2: Also, I appears the issue I had a few months ago with the strange colors was a separate issue entirely, which is still reproducible (only once somehow, this is terrifying) and has something to do with a shader I made in the visual shader editor.
Here's the dmesg log from that: dmesg_godot_lockup.txt, although I should probably move that into a new issue?
The text was updated successfully, but these errors were encountered:
Calinou
changed the title
Opening a 3D project on X11 causes a GPU Reset
Vulkan: Opening a 3D project on X11 causes a GPU Reset
Feb 17, 2022
Calinou
changed the title
Vulkan: Opening a 3D project on X11 causes a GPU Reset
Vulkan: Opening a 3D project on X11 causes a GPU Reset (AMDGPU)
Feb 17, 2022
Godot version
4.0 alpha 2
System information
Arch Linux, KDE 5.24.1, Mesa 21.3.6, AMD Radeon RX 460 Graphics (POLARIS11, DRM 3.44.0, 5.16.9-zen1-1-zen, LLVM 13.0.1)
Issue description
Godot 4 has been causing this error to appear in dmesg since some time after March 12th 2021 (some time after Godot Wild Jam #31 and commit bf309b8).
Now, it makes KWin spam notifications about a GPU reset, and flickering the the screen until I turn off compositing. VLC used to do something, so I assumed to was a mesa issue and didn't report it. However, now Godot 4 is the only app I use that causes this. This only happens on X11, no issues on Plasma Wayland. Restarting KWin allows me to turn on compositing again.
Steps to reproduce
Opening a 3D project in the editor or running one from the launcher will cause this.Edit: It only seems to be a few projects that are causing this and it doesn't happen unless I reboot and go into X11 first, it wouldn't happen when I only logged out of Wayland and logged into X11...
Edit 2: Also, I appears the issue I had a few months ago with the strange colors was a separate issue entirely, which is still reproducible (only once somehow, this is terrifying) and has something to do with a shader I made in the visual shader editor.
Here's the dmesg log from that: dmesg_godot_lockup.txt, although I should probably move that into a new issue?
The text was updated successfully, but these errors were encountered: