Cannot launch UnrealEngine Editor 4 on Fedora 31 after successful build

Community Community & Industry Discussion
1

After a successful build on Fedora 31, I am getting the following error in terminal log when launching the editor. This happens at around 96% of the launch.

INTEL-MESA: error: …/src/intel/vulkan/anv_device.c:2760: GPU hung on one of our command buffers (VK_ERROR_DEVICE_LOST)
[2020.03.23-17.03.13:389] 2]LogVulkanRHI: Error: VulkanRHI::vkQueueSubmit(Queue, 1, &SubmitInfo, Fence->GetHandle()) failed, VkResult=-4
at /home/johndoe/src/UnrealEngine/Engine/Source/Runtime/VulkanRHI/Private/VulkanQueue.cpp:71
with error VK_ERROR_DEVICE_LOST
Fatal error: [File:/home/johndoe/src/UnrealEngine/Engine/Source/Runtime/VulkanRHI/Private/VulkanUtil.cpp] [Line: 772]
VulkanRHI::vkQueueSubmit(Queue, 1, &SubmitInfo, Fence->GetHandle()) failed, VkResult=-4
at /home/johndoe/src/UnrealEngine/Engine/Source/Runtime/VulkanRHI/Private/VulkanQueue.cpp:71
with error VK_ERROR_DEVICE_LOST
Signal 11 caught.
Malloc Size=65538 LargeMemoryPoolOffset=65554

Hardware Specs:

Core™ i5-6200U CPU @ 2.30GHz
with built-in processor Graphics Adapter HD Graphics 520

Tried relaunching a couple of times and also increasing fs.notify.max_user_watches to around 1M. Didn’t work. Anyone has had this experience? Any ideas?

2

I don’t know about the issue, but your GPU is below the minimum requirements to run UE4

3

I am running UE4 on a Macbook with similar CPU and built-in GPU. Since the error seems Vulkan-related, does Vulkan require special hardware specs?

4

I think for some Intel HD graphics chips, you need special drivers for Vulkan to be enabled. This might help:

5

Thanks @, installing vulkan-related packages like vulkan-tools, vulkan-loader, vulkan-headers, vulkan-validation-layers, and vulkan-loader-devel did not help.

I think the following code is where the error occurs:



UE_LOG(LogVulkanRHI, Fatal,TEXT("%s failed, VkResult=%d
 at %s:%u 
 with error %s"),
ANSI_TO_TCHAR(VkFunction),(int32)Result,ANSI_TO_TCHAR(Filename), Line,*ErrorString);
}

File location:
[File:UnrealEngine/Engine/Source/Runtime/VulkanRHI/Private/VulkanUtil.cpp] [Line: 772]

6

Same error occurs in the similar situation on ArchLinux.

INTEL-MESA: error: …/mesa-20.0.7/src/intel/vulkan/anv_device.c:3179: GPU hung on one of our command buffers (VK_ERROR_DEVICE_LOST)
Fatal error: [File:/run/media/sasuseso/2a5b7aef-88e1-4c20-8ee9-a00f30c2a519/UnrealEngine/Engine/Source/Runtime/VulkanRHI/Private/VulkanUtil.cpp] [Line: 786]
VulkanRHI::vkQueueSubmit(Queue, 1, &SubmitInfo, Fence->GetHandle()) failed, VkResult=-4
at /run/media/sasuseso/2a5b7aef-88e1-4c20-8ee9-a00f30c2a519/UnrealEngine/Engine/Source/Runtime/VulkanRHI/Private/VulkanQueue.cpp:71
with error VK_ERROR_DEVICE_LOST

CPU: Intel i7-8550U (8) @ 4.000GHz
GPU: Intel UHD Graphics 620
kernel: 5.6.15-arch1-1

7

Your GPU is below the minimum requirements as well

8

It seems satisfy requirement described here. Linux Game Development in Unreal Engine | Unreal Engine 5.2 Documentation
Am I missing something?

9

Hello,

I wrote a possible solution to this problem on this thread on Reddit.

I believe it comes down to a “problem” in the MESA drivers (2). It is also there that I found a solution (3), although with some caution warnings (4). Basically, the rendering/shader compilation takes too much time and hits a timeout, the solution, for now, is to increase said timeout with the following command:

sudo su
echo "5000" > /sys/class/drm/card0/engine/rcs0/preempt_timeout_ms

This only affects the active session, meaning that it will reset after a restart. After setting the new timeout, the engine works without issues!

My system was running Pop!_OS 20.10 (based on Ubuntu 20.10) with running MESA 21.

1 Like