5.8 "Stable" - Vulkan crash on Linux

General Issues and Bug Reporting (Unreal Engine)
,
1

Summary

Loading any project will lead to crashing

What Type of Bug are you experiencing?

Editor

Steps to Reproduce

Open any project on a similar setup:
OS: Arch Linux x86_64
Kernel: Linux 7.0.12 Zen
DE: KDE Plasma 6.7.0 (Wayland)
GPU: AMD Radeon RX 6900 XT [Mesa 26.1.3]

Expected Result

Not crash?

Observed Result

radv: GPUVM fault detected at address 0x8001050000.
GCVM_L2_PROTECTION_FAULT_STATUS: 0x701430
	CLIENT_ID: (SQC (data)) 0xa
	MORE_FAULTS: 0
	WALKER_ERROR: 0
	PERMISSION_FAULTS: 3
	MAPPING_ERROR: 0
	RW: 0
[2026.06.19-20.56.49:470][  0]LogVulkanRHI: Error: VulkanRHI::vkQueueSubmit(Queue, InSubmitInfos.Num(), InSubmitInfos.GetData(), FenceHandle) failed, VkResult=-4
 at ./Runtime/VulkanRHI/Private/VulkanQueue.cpp:486 
 with error VK_ERROR_DEVICE_LOST
[2026.06.19-20.56.49:472][  0]LogVulkanRHI: Error: Shader diagnostic messages and asserts:

	Device: 0, Queue Graphics:
		No shader diagnostics found for this queue.

	Device: 0, Queue AsyncCompute:
		No shader diagnostics found for this queue.

[2026.06.19-20.56.49:473][  0]LogVulkanRHI: Error: 
DEVICE FAULT REPORT:
* Description: A GPUVM fault has been detected
* Address Info: 
    - VK_DEVICE_FAULT_ADDRESS_TYPE_READ_INVALID_EXT : 0x0000008001050000 (range:0x0000008001050000-0x0000008001050FFF)
* Vendor Info: 
* Vendor Binary Size: 0

[2026.06.19-20.56.49:474][  0]LogRHI: Error: Active GPU breadcrumbs:

	Device 0, Pipeline Graphics: (In: 0x8000001d, Out: 0x80000021)
		(ID: 0x80000017) [   Finished]	RenderGraphExecute - UpdateAllPrimitiveSceneInfos
		(ID: 0x80000018) [   Finished]		FRDGBuilder::SubmitBufferUploads
		(ID: 0x80000019) [   Finished]	GPUSkinCache_UpdateSkinningBatches
		(ID: 0x80000020) [     Active]	RenderGraphExecute - UpdateAllPrimitiveSceneInfos
		(ID: 0x80000021) [     Active]		FRDGBuilder::SubmitBufferUploads
		(ID: 0x8000001a) [     Active]		UpdateAllPrimitiveSceneInfos
		(ID: 0x8000001c) [     Active]			GPUSceneUpdate
		(ID: 0x8000001d) [     Active]				GPUScene.Update
		(ID: 0x8000001e) [Not Started]					UpdateGPUScene NumPrimitiveDataUploads 4

	Device 0, Pipeline AsyncCompute: (In: 0x80000020, Out: 0x80000017)
		No breadcrumb nodes found for this queue.

[2026.06.19-20.56.49:474][  0]LogCore: FUnixPlatformMisc::RequestExit(1, FVulkanDynamicRHI.TerminateOnGPUCrash)

Affects Versions

5.8

Platform(s)

Linux

Vulkan RHI submits batches that wait on binary semaphores before the corresponding signal operations are submitted (violates VUID-vkQueueSubmit-pWaitSemaphores-03238); deadlocks on Mesa/RADV Linux
2

(post deleted by author)

3

Hello, I managed to fix UE 5.8 black screen/crash on AMD graphs cards and the constant freezing that happens when using UE 5.7 or UE 5.8.

I created 2 MRs on Mesa to accomplish this fix:
MR1 black-screen/crash: Making sure you're not a bot!
MR2 freezes: Making sure you're not a bot!

I created a stacked branch because AMD users needs both MRs to UE 5.8 be usable.

you will need the packages to build it

ninja
meson
python-mako
python-yaml
python-packaging

meson setup build . \
    -Dgallium-drivers= -Dvulkan-drivers=amd -Dllvm=disabled \
    -Dplatforms=x11,wayland -Dbuildtype=debugoptimized -Dbuild-tests=true \
    -Dprefix="$HOME/.local/mesa-radv-test"

ninja -C build
meson test -C build
meson install -C build >/dev/null

echo "Installed: VK_DRIVER_FILES=$HOME/.local/mesa-radv-test/share/vulkan/icd.d/radeon_icd.x86_64.json"

then you can run UE with your new compiled mesa

VK_DRIVER_FILES="$HOME/.local/mesa-radv-test/share/vulkan/icd.d/radeon_icd.x86_64.json" SDL_VIDEODRIVER=x11 /opt/unreal-engine/Engine/Binaries/Linux/UnrealEditor

Hope Mesa devs review those MRs and it gets merged/fixed to everyone.

4

I am facing the same error on my end as well with the following:

  • OS: Ubuntu 26.04 LTS
  • Kernel: 7.0.0-27-generic
  • CPU: AMD 7800 X3D
  • GPU: AMD 7900 XTX
  • URE: 5.8

All drivers are current updated and stable releases. My issue with the above fix from @bertonha is that the newest version of Mesa requires a DRM version that is not currently released on apt repository. This was a non issue for older releases of URE5. I am hoping there will be fix that does not required system level package replacement and bleeding edge versions of mesa that could be unstable.

5

Everything seems to be fine, including Wayland support, on the branch dev-5.8.1 if you compile it. Seemed to work for me, found this solution in another thread.

6

it will part of the ddriver but there will be no soluition if you are not updating your driver. the posted stuff is a solution from a Mesa driver developer so it is fresh and it must go throug the officiasl way. So you can now use this workaround or wait till it will be released officialy.