I’m a little late to the party, but I’m experiencing what appears to be the same Vulkan device loss issue on Linux, although with different AMD hardware.
When I first downloaded 5.8 on Fedora 42, it was crashing until I disabled SM6. It worked, but it was wonky. On Fedora 44 (with SM6 disabled), performance is better until the editor freezes.
My current system is:
- OS: Fedora 44 Workstation
- Kernel tested:
- 7.1.3-201.fc44
- 7.1.3-200.fc44
- 6.19.10-300.fc44
- GPU: PowerColor Radeon RX 6800 XT Red Devil (RDNA2)
- CPU: AMD Ryzen 7 5800X
- Mesa tested:
- 26.1.4
- 26.0.3
- Vulkan: 1.4.341
- Driver: RADV
- Firmware: linux-firmware-20260622-1.fc44
The editor starts normally, but eventually freezes or exits after interacting with the editor UI.
Typical triggers include:
- opening menus
- opening dropdowns
- typing into the console
- running commands such as:
stat fps
Sometimes the crash happens immediately after a project loads while shaders and engine assets are being initialized.
The failure always ends with:
LogVulkanRHI: Error: VulkanRHI::vkQueueSubmit(...)
VkResult=-4
VK_ERROR_DEVICE_LOST
The kernel reports:
amdgpu: [gfxhub] page fault
Process UnrealEditor
GPUVM fault detected
ring gfx_0.0.0 timeout
Ring reset succeeded
The GPUVM fault occurs at the same virtual address every run:
0x0000008001050000
I tried different things to isolate the issue:
Display server
- Wayland
- X11 (
SDL_VIDEODRIVER=x11)
Mesa
- 26.1.4
- 26.0.3
Kernel
- 7.1.3
- 6.19.10
Unreal
- Cleared:
- DerivedDataCache
- Intermediate
- Saved
- Created a brand-new Blank project.
RADV options
RADV_DEBUG=sync
RADV_DEBUG=nodcc
RADV_PERFTEST=llvm
Behaves exactly the same.
The last version that worked flawlessly for me was 5.5.4.
I can see that this is a thread for RDNA4, but I can reproduce the issue consistently on RDNA2 as well.