X4 always displays random screen garbage from other applications on load, right after the black screen. Sometimes, it doesn't get to that stage but instead fails with a SIGBUS.
Program terminated with signal SIGBUS, Bus error.
#0 0x000072b90eb1ecf9 in write_buffer_descriptor () at ../mesa-24.1.1/src/amd/vulkan/radv_descriptor_set.c:1093
1093 dst[0] = va;
[Current thread is 1 (Thread 0x72b959c95cc0 (LWP 111984))]
(gdb) bt
#0 0x000072b90eb1ecf9 in write_buffer_descriptor () at ../mesa-24.1.1/src/amd/vulkan/radv_descriptor_set.c:1093
#1 write_buffer_descriptor_impl () at ../mesa-24.1.1/src/amd/vulkan/radv_descriptor_set.c:1117
#2 radv_update_descriptor_sets_impl () at ../mesa-24.1.1/src/amd/vulkan/radv_descriptor_set.c:1311
#3 radv_UpdateDescriptorSets () at ../mesa-24.1.1/src/amd/vulkan/radv_descriptor_set.c:1440
#4 0x00000000023aba51 in ?? ()
#5 0x00000000023abcc9 in ?? ()
#6 0x000000000239224e in ?? ()
#7 0x0000000002393fa3 in ?? ()
#8 0x0000000002348249 in ?? ()
#9 0x0000000001f933ae in ?? ()
#10 0x0000000001f9c551 in ?? ()
#11 0x00000000007a941d in ?? ()
#12 0x000072b9596cbc88 in __libc_start_call_main (main=main@entry=0x7a9220, argc=argc@entry=1, argv=argv@entry=0x7ffde687bdb8)
at ../sysdeps/nptl/libc_start_call_main.h:58
#13 0x000072b9596cbd4c in __libc_start_main_impl (main=0x7a9220, argc=1, argv=0x7ffde687bdb8, init=<optimized out>,
fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffde687bda8) at ../csu/libc-start.c:360
#14 0x00000000007c0669 in _start ()
Hello. The dumpfile indicates a Vulkan issue, and the VulkanInfo says that your AMD driver version (and hence Vulkan version) is 24.1.1 which is a bit outdated - current WHQL AMD driver is 24.5.1. I would do two things to start with and then see; first verify your Steam X4 game installation and then do a clean update of your AMD graphics driver. Good luck.
I tried with amdvlk too, same behavior of previously used video memory being accessed, in this case a twitch stream. This indicates access to uninitialized GPU memory on startup, which sometimes works, and sometimes fails with a SIGBUS because the memory address is fully invalid.
Thanks. To my inexperienced eye, it looks as if the OS/graphics are using consecutive batches of fragmented graphics memory for the display instead of (or before) the game loading screen being in that memory. I'll see if a Linux-savvy dev can help more.
reactormonk wrote: ↑Tue, 11. Jun 24, 08:02
I'm running the Linux version
Hey there.
I've seen reports of the graphical corruption at boot, but been unable to reproduce it. I've not seen a SIGBUS though. As it's coming from somewhere within vulkan code, my gut feeling is that this is also a driver issue, as it feels odd that this isn't happening more frequently.
Could you please provide more information about your setup (distro etc) so that I can see if I can put together a similar setup to test and hopefully repro.
Sure, it's an Archlinux, newest everything except for kernel, which is at 6.8.9 for reasons. I'm running the plasma desktop on wayland. I've had the graphical glitch startup screen since I started playing X4 (a month ago), never seen it otherwise.
, the AMD version numbers just happen to look similar.
