Unable to launch a match (Arcade, RB, SB and Test-drive) due to Vulkan crash

Hi

I’ve been unable to play the game for the last days - any gamemode, any test-drive - due to Vulkan GPU Crash (error message in picture).

Specs:
openSUSE Tumbleweed (Linux client)
6.9.9-1-default #1 SMP PREEMPT_DYNAMIC Thu Jul 11 11:31:54 UTC 2024 (8c0f797) x86_64 x86_64 x86_64 GNU/Linux

AMD Ryzen 5 5600 6-Core Processor
Intel ARC a770
16GB of RAM

vulkaninfo --summary output:

DISPLAY' environment variable not set... skipping surface info
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
==========
VULKANINFO
==========

Vulkan Instance Version: 1.3.290


Instance Extensions: count = 24
-------------------------------
VK_EXT_acquire_drm_display             : extension revision 1
VK_EXT_acquire_xlib_display            : extension revision 1
VK_EXT_debug_report                    : extension revision 10
VK_EXT_debug_utils                     : extension revision 2
VK_EXT_direct_mode_display             : extension revision 1
VK_EXT_display_surface_counter         : extension revision 1
VK_EXT_headless_surface                : extension revision 1
VK_EXT_surface_maintenance1            : extension revision 1
VK_EXT_swapchain_colorspace            : extension revision 4
VK_KHR_device_group_creation           : extension revision 1
VK_KHR_display                         : extension revision 23
VK_KHR_external_fence_capabilities     : extension revision 1
VK_KHR_external_memory_capabilities    : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2         : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2       : extension revision 1
VK_KHR_portability_enumeration         : extension revision 1
VK_KHR_surface                         : extension revision 25
VK_KHR_surface_protected_capabilities  : extension revision 1
VK_KHR_wayland_surface                 : extension revision 6
VK_KHR_xcb_surface                     : extension revision 6
VK_KHR_xlib_surface                    : extension revision 6
VK_LUNARG_direct_driver_loading        : extension revision 1

Instance Layers: count = 1
--------------------------
VK_LAYER_MESA_device_select Linux device selection layer 1.3.211  version 1

Devices:
========
GPU0:
	apiVersion         = 1.3.278
	driverVersion      = 24.1.3
	vendorID           = 0x8086
	deviceID           = 0x56a0
	deviceType         = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
	deviceName         = Intel(R) Arc(tm) A770 Graphics (DG2)
	driverID           = DRIVER_ID_INTEL_OPEN_SOURCE_MESA
	driverName         = Intel open-source Mesa driver
	driverInfo         = Mesa 24.1.3
	conformanceVersion = 1.3.6.0
	deviceUUID         = 8680a056-0800-0000-0800-000000000000
	driverUUID         = 16a66cdc-9b65-6216-473e-01cdc1cbc2fa

Thankful for any pointer. Or tools so I can help out with debugging this more :)

crash240915

Hello @Wioxjk,

Are these random crashes or do they happen at a specific point? Also I see your on Mesa 24.1.3 right? The latest version of Mesa in openSUSE Tumbleweed is 24.1.7 from what I can tell so have you tried making sure your system is fully up to date?

2 Likes

The client basically loads the first frames when entering the map - then crashes.
The hangar works perfectly fine.

Also I see your on Mesa 24.1.3 right? The latest version of Mesa in openSUSE Tumbleweed is 24.1.7 from what I can tell so have you tried making sure your system

Hmm, let me investigate this.

EDIT:

According to mesa package versions - Repology
Tumbleweed have the 24.1.3 version only.
Where did you find information about the 24.1.7 version? @apemax

Anyway, it looks like Tumbleweed is usually a couple of versions behind here…
I wonder why

Right, On the package information page for Mesa it says 24.1.7:

https://software.opensuse.org/package/Mesa

When you check for package updates on your system do you get any?

According to Suse - it was just submitted to the suse factory - yesterday, thus not available in any repo yet.
The link you provided is to OpenSuse Factory for Tumbleweed too, so it is not ready for Tumbleweed just yet, hopefully later today or tomorrow.

Right, I’m not very familiar with openSUSE and how it’s packages work. Well when it does because available could you please update to it and let me know if that helps?

Also do you get any error messages in your journalctl or dmesg log from the same as the crashes?