Any news on this? I posted to Fatshark forums after discovering the workaround. Fatshark will unfortunately be putting no resources into it, I have a feeling it is something to do with VKD3D as Halo Infinite is having issues with this as well.

As of latest game update, I am having extreme graphics glitches; either complete darkness or torn up yellow lighting Seen here:

system info: https://gist.github.com/alvord-industrial/4bb1172db56c4e3a96002244090f29a6
log: steam-1361210.log

Getting some graphics vertex issues, It'll load in fine, then after a minor stutter, the models on my weapon's ironsites (as well as other things appear to get messy:

Then after adjusting the Model LOD slider back and forth, it loads back in properly, only to break later.

This was tested on ProtonGE 8-15 as well as Proton 8.0.4

OS: EndeavourOS Linux x86_64
Kernel: 6.1.55-273-tkg-pds
Resolution: 2560x1440
DE: Plasma 5.27.8
WM: kwin
AMD Ryzen 5 3600 (12) @
AMD ATI Radeon RX 5700XT
Memory: 6130MiB / 15901MiB

I think the problem is LOD related issue, I think that somehow the graphics get stuck on the lowest LOD model.

I also want to report, since the most recent major update (Class tree update) The game has been unstable, I can get through a single game before it crashes.

Manufacturer: ASUSTeK COMPUTER INC.
Model: ROG STRIX B650E-I GAMING WIFI
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen 5 7600X 6-Core Processor
CPU Family: 0x19
CPU Model: 0x61
CPU Stepping: 0x2
CPU Type: 0x0
Speed: 5453 MHz
12 logical processors
6 physical processors
Hyper-threading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Supported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Supported
AVX512VNNI: Supported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
"EndeavourOS Linux" (64 bit)
Kernel Name: Linux
Kernel Version: 6.5.5-zen1-1-zen
X Server Vendor: The X.Org Foundation
X Server Release: 12101008
X Window Manager: Xfwm4
Steam Runtime Version: steam-runtime_0.20230801.56012
Video Card:
Driver: AMD AMD Radeon RX 7900 XTX (gfx1100, LLVM 16.0.6, DRM 3.54, 6.5.5-zen1-1-zen)
Driver Version: 4.6 (Compatibility Profile) Mesa 23.2.1-arch1.1
OpenGL Version: 4.6
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 143 Hz
VendorID: 0x1002
DeviceID: 0x744c
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 1
Primary Display Resolution: 1920 x 1080
Desktop Resolution: 1920 x 1080
Primary Display Size: 20.94" x 11.97" (24.09" diag), 53.2cm x 30.4cm (61.2cm diag)
Primary VRAM: 24576 MB
Sound card:
Audio device: ATI R6xx HDMI
Memory:
RAM: 31836 Mb
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
LANG: en_GB.UTF-8
Total Hard Disk Space Available: 319390 MB
Largest Free Hard Disk Block: 225354 MB
Storage:
Number of SSDs: 2
SSD sizes: 0B,0B
Number of HDDs: 0
Number of removable drives: 0

@tlneondo The look like the mesh streaming issue.known issue

Change line 57 to

	disable = true

in
steamapps\common\Warhammer 40,000 DARKTIDE\bundle\application_settings\settings_common.ini
should fix the problem.

Hello there, I'm getting this crash on the steamdeck after I click play on their launcher

`
Oct 15 01:50:49 steamdeck systemd-coredump[37552]: [🡕] Process 35891 (gamescope-wl) of user 1000 dumped core.

                                               Stack trace of thread 35925:
                                               #0  0x0000564427a08301 n/a (gamescope + 0x5e301)
                                               #1  0x0000564427a1a9a0 n/a (gamescope + 0x709a0)
                                               #2  0x00007f5b134e1943 execute_native_thread_routine (libstdc++.so.6 + 0xe1943)
                                               #3  0x00007f5b1329d44b n/a (libc.so.6 + 0x8744b)
                                               #4  0x00007f5b13320e40 n/a (libc.so.6 + 0x10ae40)
                                               
                                               Stack trace of thread 35891:
                                               #0  0x00007f5b13313c0f __poll (libc.so.6 + 0xfdc0f)
                                               #1  0x0000564427a16dff n/a (gamescope + 0x6cdff)
                                               #2  0x00005644279cc0cf n/a (gamescope + 0x220cf)
                                               #3  0x00007f5b13239850 n/a (libc.so.6 + 0x23850)
                                               #4  0x00007f5b1323990a __libc_start_main (libc.so.6 + 0x2390a)
                                               #5  0x00005644279edeb5 n/a (gamescope + 0x43eb5)
                                               
                                               Stack trace of thread 35924:
                                               #0  0x00007f5b13313c0f __poll (libc.so.6 + 0xfdc0f)
                                               #1  0x0000564427a40402 n/a (gamescope + 0x96402)
                                               #2  0x00007f5b134e1943 execute_native_thread_routine (libstdc++.so.6 + 0xe1943)
                                               #3  0x00007f5b1329d44b n/a (libc.so.6 + 0x8744b)
                                               #4  0x00007f5b13320e40 n/a (libc.so.6 + 0x10ae40)
                                               
                                               Stack trace of thread 35895:
                                               #0  0x00007f5b132e59e5 clock_nanosleep (libc.so.6 + 0xcf9e5)
                                               #1  0x00007f5b132ea5e7 __nanosleep (libc.so.6 + 0xd45e7)
                                               #2  0x00007f5b12100455 n/a (libvulkan_radeon.so + 0x100455)
                                               #3  0x00007f5b1225c34c n/a (libvulkan_radeon.so + 0x25c34c)
                                               #4  0x00007f5b1329d44b n/a (libc.so.6 + 0x8744b)
                                               #5  0x00007f5b13320e40 n/a (libc.so.6 + 0x10ae40)
                                               
                                               Stack trace of thread 35894:
                                               #0  0x00007f5b13299f0e n/a (libc.so.6 + 0x83f0e)
                                               #1  0x00007f5b1329c7a0 pthread_cond_wait (libc.so.6 + 0x867a0)
                                               #2  0x00007f5b1225c41e n/a (libvulkan_radeon.so + 0x25c41e)
                                               #3  0x00007f5b1223998c n/a (libvulkan_radeon.so + 0x23998c)
                                               #4  0x00007f5b1225c34c n/a (libvulkan_radeon.so + 0x25c34c)
                                               #5  0x00007f5b1329d44b n/a (libc.so.6 + 0x8744b)
                                               #6  0x00007f5b13320e40 n/a (libc.so.6 + 0x10ae40)
                                               
                                               Stack trace of thread 35893:
                                               #0  0x00007f5b13313c0f __poll (libc.so.6 + 0xfdc0f)
                                               #1  0x0000564427a1c607 n/a (gamescope + 0x72607)
                                               #2  0x00007f5b134e1943 execute_native_thread_routine (libstdc++.so.6 + 0xe1943)
                                               #3  0x00007f5b1329d44b n/a (libc.so.6 + 0x8744b)
                                               #4  0x00007f5b13320e40 n/a (libc.so.6 + 0x10ae40)
                                               
                                               Stack trace of thread 35928:
                                               #0  0x00007f5b13299f0e n/a (libc.so.6 + 0x83f0e)
                                               #1  0x00007f5b1329c7a0 pthread_cond_wait (libc.so.6 + 0x867a0)
                                               #2  0x00007f5b134d9e11 __gthread_cond_wait (libstdc++.so.6 + 0xd9e11)
                                               #3  0x00005644279f69d5 n/a (gamescope + 0x4c9d5)
                                               #4  0x00007f5b134e1943 execute_native_thread_routine (libstdc++.so.6 + 0xe1943)
                                               #5  0x00007f5b1329d44b n/a (libc.so.6 + 0x8744b)
                                               #6  0x00007f5b13320e40 n/a (libc.so.6 + 0x10ae40)
                                               
                                               Stack trace of thread 35923:
                                               #0  0x00007f5b13321266 epoll_wait (libc.so.6 + 0x10b266)
                                               #1  0x00007f5b0a439579 n/a (libspa-support.so + 0x13579)
                                               #2  0x00007f5b0a42cbe3 n/a (libspa-support.so + 0x6be3)
                                               #3  0x00007f5b1383c26f n/a (libpipewire-0.3.so.0 + 0x4126f)
                                               #4  0x00007f5b1329d44b n/a (libc.so.6 + 0x8744b)
                                               #5  0x00007f5b13320e40 n/a (libc.so.6 + 0x10ae40)
                                               
                                               Stack trace of thread 35927:
                                               #0  0x00007f5b132e59e5 clock_nanosleep (libc.so.6 + 0xcf9e5)
                                               #1  0x00007f5b132ea5e7 __nanosleep (libc.so.6 + 0xd45e7)
                                               #2  0x0000564427a1de67 n/a (gamescope + 0x73e67)
                                               #3  0x00007f5b134e1943 execute_native_thread_routine (libstdc++.so.6 + 0xe1943)
                                               #4  0x00007f5b1329d44b n/a (libc.so.6 + 0x8744b)
                                               #5  0x00007f5b13320e40 n/a (libc.so.6 + 0x10ae40)
                                               
                                               Stack trace of thread 35926:
                                               #0  0x00007f5b1330f900 __open64 (libc.so.6 + 0xf9900)
                                               #1  0x00005644279efb05 n/a (gamescope + 0x45b05)
                                               #2  0x00007f5b134e1943 execute_native_thread_routine (libstdc++.so.6 + 0xe1943)
                                               #3  0x00007f5b1329d44b n/a (libc.so.6 + 0x8744b)
                                               #4  0x00007f5b13320e40 n/a (libc.so.6 + 0x10ae40)
                                               ELF object binary architecture: AMD x86-64

Oct 15 01:50:49 steamdeck systemd[1]: [email protected]: Deactivated successfully.
`

I'm running the preview branch, 3.5.1

The game is becoming more and more unstable with each release of dark tide, and recently the game crashed (in this particular case, I'm reasonably sure it wasn't a proton issue, comp overheated) and then got stuck on the authentication screen and wouldn't let me back in until after the game I was in had concluded, because of course the game crashes in the last section (again, reasonably sure it wasn't a proton issue, what I'm frustrated about is that the game wouldn't let me back in until it was too late).

On the Steam Deck, the game is for me consistently crashing just after the initial window, right after when it completes the "compiling shaders" progress bar. It gets completely black then after a few seconds reboot the Steam Deck. Tried regular proton, experimental, hotfix and GE and had the same issue every time.

On the other hand, on my full-AMD PC with Archlinux, the game runs smooth, no issues. Can play for hours on end.

What diagnostic data I can send to help on troubleshooting this one?

@Patola Try running it in desktop mode.

there are open issue in gamescope's github https://github.com/ValveSoftware/gamescope/issues/993 about darktide crashing with gamescope.

Good point, I haven't tried that. Will try.

It did indeed work in Desktop mode.

The game does not start with proton 9 and latest mesa on Fedora 39

I get this message

wine: Call from 00006FFFFFC1CE87 to unimplemented function amd_ags_x64.dll.agsDriverExtensionsDX12_PushMarker, aborting

Edit: After proton beta 14, the game is back on proton 9, thanks volvo

I'm unable to play this game due to networking issues. Also getting something similar with 6 days in Fallujah. See issue: https://github.com/ValveSoftware/steam-for-linux/issues/10598

Steam networking failure on Warhammer 40k: Darktide and Six days in Fallujah

Issue transferred from https://github.com/ValveSoftware/steam-for-linux/issues/10598.
@soypat posted on 2024-03-09T20:55:05:

Your system information

Steam Beta Branch: Stable Client
Steam Version: 1709846872
Steam Client Build Date: Wed, Mar 6 5:28 PM UTC -03:00
Steam Web Build Date: Thu, Mar 7 6:17 PM UTC -03:00
Steam API Version: SteamClient021

$ neofetch
             ...-:::::-...                 pato@qtpi 
          .-MMMMMMMMMMMMMMM-.              --------- 
      .-MMMM`..-:::::::-..`MMMM-.          OS: Linux Mint 21 x86_64 
    .:MMMM.:MMMMMMMMMMMMMMM:.MMMM:.        Host: B660M DS3H DDR4 
   -MMM-M---MMMMMMMMMMMMMMMMMMM.MMM-       Kernel: 5.15.0-100-generic 
 `:MMM:MM`  :MMMM:....::-...-MMMM:MMM:`    Uptime: 4 hours, 13 mins 
 :MMM:MMM`  :MM:`  ``    ``  `:MMM:MMM:    Packages: 3188 (dpkg), 23 (flatpak), 
.MMM.MMMM`  :MM.  -MM.  .MM-  `MMMM.MMM.   Shell: bash 5.1.16 
:MMM:MMMM`  :MM.  -MM-  .MM:  `MMMM-MMM:   Resolution: 1920x1080, 1920x1080 
:MMM:MMMM`  :MM.  -MM-  .MM:  `MMMM:MMM:   DE: Xfce 4.16 
:MMM:MMMM`  :MM.  -MM-  .MM:  `MMMM-MMM:   WM: Xfwm4 
.MMM.MMMM`  :MM:--:MM:--:MM:  `MMMM.MMM.   WM Theme: Mint-Y 
 :MMM:MMM-  `-MMMMMMMMMMMM-`  -MMM-MMM:    Theme: Mint-Y-Dark-Purple [GTK2/3] 
  :MMM:MMM:`                `:MMM:MMM:     Icons: Mint-Y [GTK2/3] 
   .MMM.MMMM:--------------:MMMM.MMM.      Terminal: xfce4-terminal 
     '-MMMM.-MMMMMMMMMMMMMMM-.MMMM-'       Terminal Font: Monospace 17 
       '.-MMMM``--:::::--``MMMM-.'         CPU: 12th Gen Intel i5-12400F (12) @ 
            '-MMMMMMMMMMMMM-'              GPU: AMD ATI Radeon RX 6800/6800 XT  
               ``-:::::-``                 Memory: 13502MiB / 31933MiB 

steam-logs.tar.gz

Just ran

sudo apt update -y && sudo apt upgrade -y

and still happening.

Please describe your issue in as much detail as possible:

Games that previously worked (Six days fallujah) now throwing a cloud error (I assume it is related to steam) on startup screen. I am not able to play online or invite friends to my game. See images.

Warhammer 40k: Darktide also throws a network error on startup and fails to run entirely.

I've tried several other games such as Counter Strike 2, Lethal Company, Broforce, Sid Meier's Civ VI, Ready Or Not, among others in online play and they seem to work OK, no errors. This is the behaviour I was expecting.

Warhammer 40,000: Darktide

After first startup cutscene (only option is to close it):

Six Days in Fallujah

On loading game:

On clicking "Fireteams" or "Wargames":

On trying to invite friends:

Steps for reproducing this issue:

1. Run Warhammer Dark Tide. Skip or dont skip cutscenes. Also run 6 days and observe message on load.

Done!
steam-1361210.log.zip

I am having an issue with the game crashing on the loading screen after launching that says 'Processing Inquisitorial Clearance'. Logs and system info below.

System info:
GPU: RX 7800 XT
Video Driver Version: Mesa 24.0.8-arch1.1
Kernel Version: 6.9.2-arch1-1
Steam Version: 1716584667
Proton Version: 9.0-1 and Experimental
Full system report

steam-1361210.log

Switching to RADV fixed the problem, the game seems to run fine now. Thank you.

I'll try a current release mesa and see what happens. Many thanks!

I checked dmesg, sadly I'm a newb and understand little. However, I did see this over and over again and something tells me even a newb knows this could be an issue.

[ 329.149588] [drm] Skip scheduling IBs!
[ 329.149588] [drm] Skip scheduling IBs!
[ 329.149589] [drm] Skip scheduling IBs!
[ 329.149590] [drm] Skip scheduling IBs!

Since the release of Proton 9.0-2, Darktide is exhibiting a new problem on my Steam Deck (running the "stable" SteamOS), namely after the launcher about 2/3 of the time it shows the "Building shader cache" dialog and then hangs at 0% (not the usual crashing behaviour on other platforms where it crashes after this finishes).

I've tested with Proton experimental and it has the same problem, but forcing the most up to date version of Proton 8 (8.0-5) resolves this issue. I did not have this problem with 9.0 before 9.0-2 so something fixed in that must have broken shader cache generation sometimes in Darktide.

It's not a super serious issue as you can just kill it and relaunch until it works (and the game is stable after that), or force 8.0-5 but it probably implies there's a bug that will impact other titles (I would guess in the improved d3d->vulkan stuff?) and it's reproducible with Darktide.

I do have shader precaching turned off in Steam so it's possible turning that on would fix it but oh my the storage space!

Since the release of Proton 9.0-2, Darktide is exhibiting a new problem on my Steam Deck (running the "stable" SteamOS), namely after the launcher about 2/3 of the time it shows the "Building shader cache" dialog and then hangs at 0% (not the usual crashing behaviour on other platforms where it crashes after this finishes).

Actually, I also had this problem with Proton 9.0 on my PC. My current quick & dirty solution is to rename the file shader_cache\bundled_shader_cache.hans to somethinge else. Then the cache building is replaced by an error message that you can click away without any negative effects in my experience.

@kisak-valve sorry to be picky about this but do the logs contain any private information? (I'm thinking things like authentication with the Steam servers etc.)?

hmm: https://github.com/ValveSoftware/Proton/issues/5484

@kisak-valve sorry to be picky about this but do the logs contain any private information? (I'm thinking things like authentication with the Steam servers etc.)?

hmm: #5484

From what I can see it is just your steam profile ID which can be found publicly as long as you know the Steam Username. If you Ctrl +F "Steam_SetMinidumpSteamID:" in the proton logs. you can find this ID and remove it which will remove the "private information" in the proton log.

I'm running into the same issue. Dropping down to Proton 8 works fine, but both stable Proton 9 and latest Proton-GE get stuck at "Building shader cache" after the launcher.
Notably, while playing around with settings and startup options, I sometimes got it to run once. But a consecutive attempt right after would always fail.
Presumably the game gets stuck at validating an existing cache, rather than at building a new one. So if the changes are significant enough to invalidate the cache, it will work once.

Log of a failing attempt: https://gist.github.com/sclu1034/71516d0e98b13d70f78c5f4181368e67

For what it's worth - I've not experienced the problem with the latest two releases of Proton experimental, but not entirely sure if that's luck or not so it may be fixed?

So I don't know if this issue is with my computer/install or what but, I've started encountering an issue, I get to the initial screen after the intro movie and I press space to authenticate and then suddenly performance tanks to the point it affects system performance and then the game just crashes to desktop.

I think I may have forgotten to install something or forgotten something else (and I don't recall what it might be if this were indeed the case) but the game used to run perfectly fine but I have since reinstalled the OS (EndevourOS) and now I'm getting this issue.

Other games work fine without any issue (tested Cyberpunk 2077 at max settings).

I have installed the latest version of Mesa.

Same issue no matter which version of proton I'm using, so I concede It might not be a proton issue which was why I was reluctant to add this post.

Don't know what info is needed to debug.

                     ./o.                  thermatix@black-tower 
                   ./sssso-                --------------------- 
                 `:osssssss+-              OS: EndeavourOS Linux x86_64 
               `:+sssssssssso/.            Kernel: 6.10.2-arch1-1 
             `-/ossssssssssssso/.          Uptime: 5 hours, 23 mins 
           `-/+sssssssssssssssso+:`        Packages: 1344 (pacman) 
         `-:/+sssssssssssssssssso+/.       Shell: bash 5.2.26 
       `.://osssssssssssssssssssso++-      Resolution: 2560x1440 
      .://+ssssssssssssssssssssssso++:     DE: Plasma 6.1.3 
    .:///ossssssssssssssssssssssssso++:    WM: KWin 
  `:////ssssssssssssssssssssssssssso+++.   Theme: Breeze-Dark [GTK2], Breeze [GTK3] 
`-////+ssssssssssssssssssssssssssso++++-   Icons: breeze-dark [GTK2/3] 
 `..-+oosssssssssssssssssssssssso+++++/`   Terminal: konsole 
   ./++++++++++++++++++++++++++++++/:.     CPU: AMD Ryzen 5 7600X (12) @ 5.453GHz 
  `:::::::::::::::::::::::::------``       GPU: AMD ATI Radeon RX 7900 XT/7900 XTX/7900M 
                                           Memory: 9951MiB / 31834MiB 

glxinfo.txt
steam-1361210.log

EDIT:

So I don't know why but the game it seams refused to run with AMDVLK which I hadn't realised was a thing (The it not running with AMDVLK, not that AMDVLK exists) as I normally use the Mesa drivers but well, when I re-installed steam this time I installed them without realising (I honestly forget which one is which since I only have to this once every time I install steam...).

So I switched to the Mesa equivlents and the game started. Yay.

I've been getting very frequent GPU resets (ring gfx_0.0.0 timeout), making it nearly unplayable. I end up crashing every other match I play, and if I re-join a match in which I crashed, the crash usually occurs again very quickly (I've had it happen 6+ times in a single match). I've always had GPU reset issues with this game, but it has become so much worse lately.

I don't have this issue with any other games I play.

Aug 20 17:09:39 peelz-pc kernel: [drm:gfx_v10_0_priv_reg_irq [amdgpu]] *ERROR* Illegal register access in command stream
Aug 20 17:09:39 peelz-pc kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=8247416, emitted seq=8247419
Aug 20 17:09:39 peelz-pc kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process main pid 77680 thread vkd3d_queue pid 77736
Aug 20 17:09:39 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: GPU reset begin!
Aug 20 17:09:39 peelz-pc kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Aug 20 17:09:39 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: MODE1 reset
Aug 20 17:09:39 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: GPU mode1 reset
Aug 20 17:09:39 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: GPU smu mode1 reset
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: GPU reset succeeded, trying to resume
Aug 20 17:09:40 peelz-pc kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000300000).
Aug 20 17:09:40 peelz-pc kernel: [drm] VRAM is lost due to GPU reset!
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: PSP is resuming...
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: reserve 0xa00000 from 0x83fd000000 for PSP TMR
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: SMU is resuming...
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: smu driver if version = 0x00000040, smu fw if version = 0x00000041, smu fw program = 0, version = 0x003a5a00 (58.90.0)
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: SMU driver if version not matched
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: use vbios provided pptable
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: SMU is resumed successfully!
Aug 20 17:09:40 peelz-pc kernel: [drm] DMUB hardware initialized: version=0x02020020
Aug 20 17:09:40 peelz-pc kernel: [drm] kiq ring mec 2 pipe 1 q 0
Aug 20 17:09:40 peelz-pc kernel: [drm] JPEG decode initialized successfully.
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: ring gfx_0.1.0 uses VM inv eng 1 on hub 0
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 4 on hub 0
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 5 on hub 0
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 12 on hub 0
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: ring sdma0 uses VM inv eng 13 on hub 0
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: ring sdma1 uses VM inv eng 14 on hub 0
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: ring sdma2 uses VM inv eng 15 on hub 0
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: ring sdma3 uses VM inv eng 16 on hub 0
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: ring vcn_dec_1 uses VM inv eng 5 on hub 8
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: ring vcn_enc_1.0 uses VM inv eng 6 on hub 8
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: ring vcn_enc_1.1 uses VM inv eng 7 on hub 8
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: ring jpeg_dec uses VM inv eng 8 on hub 8
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: recover vram bo from shadow start
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: recover vram bo from shadow done
Aug 20 17:09:40 peelz-pc kernel: amdgpu 0000:0b:00.0: amdgpu: GPU reset(2) succeeded!
Aug 20 17:09:52 peelz-pc kernel: amdgpu 0000:0b:00.0: [drm] *ERROR* [CRTC:95:crtc-1] flip_done timed out
Aug 20 17:09:55 peelz-pc kernel: [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:95:crtc-1] hw_done or flip_done timed out
Aug 20 17:10:05 peelz-pc kernel: amdgpu 0000:0b:00.0: [drm] *ERROR* flip_done timed out
Aug 20 17:10:05 peelz-pc kernel: amdgpu 0000:0b:00.0: [drm] *ERROR* [CRTC:95:crtc-1] commit wait timed out
Aug 20 17:10:15 peelz-pc kernel: amdgpu 0000:0b:00.0: [drm] *ERROR* flip_done timed out
Aug 20 17:10:15 peelz-pc kernel: amdgpu 0000:0b:00.0: [drm] *ERROR* [CONNECTOR:127:DP-3] commit wait timed out
Aug 20 17:10:25 peelz-pc kernel: amdgpu 0000:0b:00.0: [drm] *ERROR* flip_done timed out
Aug 20 17:10:25 peelz-pc kernel: amdgpu 0000:0b:00.0: [drm] *ERROR* [PLANE:64:plane-4] commit wait timed out
Aug 20 17:10:25 peelz-pc kernel: ------------[ cut here ]------------
Aug 20 17:10:25 peelz-pc kernel: WARNING: CPU: 3 PID: 803 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:8600 amdgpu_dm_atomic_commit_tail+0x3bb9/0x3d30 [amdgpu]
Aug 20 17:10:25 peelz-pc kernel: Modules linked in: snd_seq_dummy snd_hrtimer snd_seq nft_masq nft_chain_nat nf_nat wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel udp_tunnel bridge veth stp llc dummy nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_limit nft_ct nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables vfat fat amd_atl intel_rapl_msr intel_rapl_common snd_hda_codec_realtek snd_hda_codec_generic eeepc_wmi snd_hda_scodec_component snd_hda_codec_hdmi asus_wmi platform_profile snd_hda_intel snd_usb_audio snd_intel_dspcfg kvm_amd snd_usbmidi_lib snd_intel_sdw_acpi snd_ump snd_hda_codec snd_rawmidi i8042 kvm asus_ec_sensors snd_hda_core snd_seq_device sparse_keymap mc snd_hwdep r8169 serio rapl sp5100_tco snd_pcm wmi_bmof igb acpi_cpufreq pcspkr k10temp i2c_piix4 realtek ptp snd_timer mdio_devres pps_core snd libphy soundcore dca cdc_acm mousedev joydev mac_hid pkcs8_key_parser mt76 mac80211 libarc4 cfg80211 rfkill tun i2c_dev crypto_user loop
Aug 20 17:10:25 peelz-pc kernel:  nfnetlink ip_tables x_tables raid10 raid1 raid0 dm_integrity dm_bufio dm_raid raid456 md_mod async_raid6_recov async_memcpy async_pq async_xor async_tx vfio_pci vfio_pci_core vfio_iommu_type1 vfio iommufd hid_corsair ext4 crc16 mbcache jbd2 btrfs blake2b_generic xor hid_generic raid6_pq libcrc32c crct10dif_pclmul crc32c_generic crc32_pclmul crc32c_intel polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel dm_mod usbhid sha512_ssse3 sha256_ssse3 sha1_ssse3 aesni_intel nvme crypto_simd cryptd nvme_core ccp xhci_pci xhci_pci_renesas nvme_auth amdgpu amdxcp drm_exec gpu_sched drm_buddy video mxm_wmi wmi i2c_algo_bit drm_suballoc_helper drm_ttm_helper ttm drm_display_helper cec
Aug 20 17:10:25 peelz-pc kernel: CPU: 3 PID: 803 Comm: systemd-logind Not tainted 6.10.5-arch1-1 #1 d3097fc3f639001630e5fb5d7653624655f00867
Aug 20 17:10:25 peelz-pc kernel: Hardware name: ASUS System Product Name/ROG CROSSHAIR VIII HERO, BIOS 4702 10/20/2023
Aug 20 17:10:25 peelz-pc kernel: RIP: 0010:amdgpu_dm_atomic_commit_tail+0x3bb9/0x3d30 [amdgpu]
Aug 20 17:10:25 peelz-pc kernel: Code: 80 fe ff ff 48 8d 95 c4 fe ff ff 48 8b b1 50 01 00 00 48 8b b8 c8 29 04 00 e8 e3 d2 28 00 4c 8b 9d 68 fe ff ff e9 a4 f7 ff ff <0f> 0b e9 bd f4 ff ff 0f 0b 0f 0b e9 e1 f4 ff ff 0f 0b e9 a1 ca ff
Aug 20 17:10:25 peelz-pc kernel: RSP: 0018:ffffa71506083598 EFLAGS: 00010002
Aug 20 17:10:25 peelz-pc kernel: RAX: 0000000000000286 RBX: 0000000000000286 RCX: ffff8c1953470118
Aug 20 17:10:25 peelz-pc kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8c1954c80178
Aug 20 17:10:25 peelz-pc kernel: RBP: ffffa715060837f0 R08: ffffa71506083484 R09: 0000000000000000
Aug 20 17:10:25 peelz-pc kernel: R10: ffffa715060834f0 R11: 0000000000000002 R12: ffff8c1953470118
Aug 20 17:10:25 peelz-pc kernel: R13: 0000000000000001 R14: ffff8c1953470000 R15: ffff8c1d79d10000
Aug 20 17:10:25 peelz-pc kernel: FS:  00007b357aae9f40(0000) GS:ffff8c204e780000(0000) knlGS:0000000000000000
Aug 20 17:10:25 peelz-pc kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 20 17:10:25 peelz-pc kernel: CR2: 00007b5939c331f0 CR3: 0000000105078000 CR4: 0000000000350ef0
Aug 20 17:10:25 peelz-pc kernel: Call Trace:
Aug 20 17:10:25 peelz-pc kernel:  <TASK>
Aug 20 17:10:25 peelz-pc kernel:  ? amdgpu_dm_atomic_commit_tail+0x3bb9/0x3d30 [amdgpu aca26f062e7a11d5f580981bef229896ff3bf81a]
Aug 20 17:10:25 peelz-pc kernel:  ? __warn.cold+0x8e/0xe8
Aug 20 17:10:25 peelz-pc kernel:  ? amdgpu_dm_atomic_commit_tail+0x3bb9/0x3d30 [amdgpu aca26f062e7a11d5f580981bef229896ff3bf81a]
Aug 20 17:10:25 peelz-pc kernel:  ? report_bug+0xff/0x140
Aug 20 17:10:25 peelz-pc kernel:  ? handle_bug+0x3c/0x80
Aug 20 17:10:25 peelz-pc kernel:  ? exc_invalid_op+0x17/0x70
Aug 20 17:10:25 peelz-pc kernel:  ? asm_exc_invalid_op+0x1a/0x20
Aug 20 17:10:25 peelz-pc kernel:  ? amdgpu_dm_atomic_commit_tail+0x3bb9/0x3d30 [amdgpu aca26f062e7a11d5f580981bef229896ff3bf81a]
Aug 20 17:10:25 peelz-pc kernel:  ? amdgpu_dm_atomic_commit_tail+0x306a/0x3d30 [amdgpu aca26f062e7a11d5f580981bef229896ff3bf81a]
Aug 20 17:10:25 peelz-pc kernel:  commit_tail+0x94/0x130
Aug 20 17:10:25 peelz-pc kernel:  drm_atomic_helper_commit+0x11a/0x140
Aug 20 17:10:25 peelz-pc kernel:  drm_atomic_commit+0xa0/0xd0
Aug 20 17:10:25 peelz-pc kernel:  ? __pfx___drm_printfn_info+0x10/0x10
Aug 20 17:10:25 peelz-pc kernel:  drm_client_modeset_commit_atomic+0x203/0x250
Aug 20 17:10:25 peelz-pc kernel:  drm_client_modeset_commit_locked+0x5a/0x160
Aug 20 17:10:25 peelz-pc kernel:  __drm_fb_helper_restore_fbdev_mode_unlocked+0x5e/0xd0
Aug 20 17:10:25 peelz-pc kernel:  drm_fb_helper_set_par+0x30/0x40
Aug 20 17:10:25 peelz-pc kernel:  fb_set_var+0x25f/0x460
Aug 20 17:10:25 peelz-pc kernel:  ? srso_return_thunk+0x5/0x5f
Aug 20 17:10:25 peelz-pc kernel:  ? update_load_avg+0x7e/0x7b0
Aug 20 17:10:25 peelz-pc kernel:  ? srso_return_thunk+0x5/0x5f
Aug 20 17:10:25 peelz-pc kernel:  ? psi_group_change+0x1b0/0x350
Aug 20 17:10:25 peelz-pc kernel:  fbcon_blank+0x200/0x2f0
Aug 20 17:10:25 peelz-pc kernel:  do_unblank_screen+0xb0/0x150
Aug 20 17:10:25 peelz-pc kernel:  complete_change_console+0x54/0x120
Aug 20 17:10:25 peelz-pc kernel:  vt_ioctl+0xec3/0x12c0
Aug 20 17:10:25 peelz-pc kernel:  tty_ioctl+0xe8/0x8a0
Aug 20 17:10:25 peelz-pc kernel:  ? srso_return_thunk+0x5/0x5f
Aug 20 17:10:25 peelz-pc kernel:  ? __seccomp_filter+0x303/0x520
Aug 20 17:10:25 peelz-pc kernel:  __x64_sys_ioctl+0x97/0xd0
Aug 20 17:10:25 peelz-pc kernel:  do_syscall_64+0x82/0x190
Aug 20 17:10:25 peelz-pc kernel:  ? srso_return_thunk+0x5/0x5f
Aug 20 17:10:25 peelz-pc kernel:  ? syscall_exit_to_user_mode+0x72/0x200
Aug 20 17:10:25 peelz-pc kernel:  ? srso_return_thunk+0x5/0x5f
Aug 20 17:10:25 peelz-pc kernel:  ? do_syscall_64+0x8e/0x190
Aug 20 17:10:25 peelz-pc kernel:  ? srso_return_thunk+0x5/0x5f
Aug 20 17:10:25 peelz-pc kernel:  ? evdev_ioctl+0x72/0x90
Aug 20 17:10:25 peelz-pc kernel:  ? srso_return_thunk+0x5/0x5f
Aug 20 17:10:25 peelz-pc kernel:  ? syscall_exit_to_user_mode+0x72/0x200
Aug 20 17:10:25 peelz-pc kernel:  ? srso_return_thunk+0x5/0x5f
Aug 20 17:10:25 peelz-pc kernel:  ? do_syscall_64+0x8e/0x190
Aug 20 17:10:25 peelz-pc kernel:  ? syscall_exit_to_user_mode+0x72/0x200
Aug 20 17:10:25 peelz-pc kernel:  ? srso_return_thunk+0x5/0x5f
Aug 20 17:10:25 peelz-pc kernel:  ? do_syscall_64+0x8e/0x190
Aug 20 17:10:25 peelz-pc kernel:  ? srso_return_thunk+0x5/0x5f
Aug 20 17:10:25 peelz-pc kernel:  ? __irq_exit_rcu+0x4a/0xb0
Aug 20 17:10:25 peelz-pc kernel:  ? srso_return_thunk+0x5/0x5f
Aug 20 17:10:25 peelz-pc kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Aug 20 17:10:25 peelz-pc kernel: RIP: 0033:0x7b357ad23ced
Aug 20 17:10:25 peelz-pc kernel: Code: 04 25 28 00 00 00 48 89 45 c8 31 c0 48 8d 45 10 c7 45 b0 10 00 00 00 48 89 45 b8 48 8d 45 d0 48 89 45 c0 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1a 48 8b 45 c8 64 48 2b 04 25 28 00 00 00
Aug 20 17:10:25 peelz-pc kernel: RSP: 002b:00007ffe0aaac210 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Aug 20 17:10:25 peelz-pc kernel: RAX: ffffffffffffffda RBX: 000000000000000b RCX: 00007b357ad23ced
Aug 20 17:10:25 peelz-pc kernel: RDX: 0000000000000001 RSI: 0000000000005605 RDI: 000000000000000b
Aug 20 17:10:25 peelz-pc kernel: RBP: 00007ffe0aaac260 R08: 00007ffe0aaac1f0 R09: 000062e05869c7f0
Aug 20 17:10:25 peelz-pc kernel: R10: 00007ffe0aaac240 R11: 0000000000000246 R12: 0000000000000000
Aug 20 17:10:25 peelz-pc kernel: R13: 00007ffe0aaac2f0 R14: 000062e05869d120 R15: 000062e05869f600
Aug 20 17:10:25 peelz-pc kernel:  </TASK>
Aug 20 17:10:25 peelz-pc kernel: ---[ end trace 0000000000000000 ]---
Aug 20 17:10:25 peelz-pc kernel: ------------[ cut here ]------------
Aug 20 17:10:25 peelz-pc kernel: WARNING: CPU: 3 PID: 803 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:8131 amdgpu_dm_atomic_commit_tail+0x3bc2/0x3d30 [amdgpu]
Aug 20 17:10:25 peelz-pc kernel: Modules linked in: snd_seq_dummy snd_hrtimer snd_seq nft_masq nft_chain_nat nf_nat wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel udp_tunnel bridge veth stp llc dummy nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_limit nft_ct nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables vfat fat amd_atl intel_rapl_msr intel_rapl_common snd_hda_codec_realtek snd_hda_codec_generic eeepc_wmi snd_hda_scodec_component snd_hda_codec_hdmi asus_wmi platform_profile snd_hda_intel snd_usb_audio snd_intel_dspcfg kvm_amd snd_usbmidi_lib snd_intel_sdw_acpi snd_ump snd_hda_codec snd_rawmidi i8042 kvm asus_ec_sensors snd_hda_core snd_seq_device sparse_keymap mc snd_hwdep r8169 serio rapl sp5100_tco snd_pcm wmi_bmof igb acpi_cpufreq pcspkr k10temp i2c_piix4 realtek ptp snd_timer mdio_devres pps_core snd libphy soundcore dca cdc_acm mousedev joydev mac_hid pkcs8_key_parser mt76 mac80211 libarc4 cfg80211 rfkill tun i2c_dev crypto_user loop
Aug 20 17:10:25 peelz-pc kernel:  nfnetlink ip_tables x_tables raid10 raid1 raid0 dm_integrity dm_bufio dm_raid raid456 md_mod async_raid6_recov async_memcpy async_pq async_xor async_tx vfio_pci vfio_pci_core vfio_iommu_type1 vfio iommufd hid_corsair ext4 crc16 mbcache jbd2 btrfs blake2b_generic xor hid_generic raid6_pq libcrc32c crct10dif_pclmul crc32c_generic crc32_pclmul crc32c_intel polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel dm_mod usbhid sha512_ssse3 sha256_ssse3 sha1_ssse3 aesni_intel nvme crypto_simd cryptd nvme_core ccp xhci_pci xhci_pci_renesas nvme_auth amdgpu amdxcp drm_exec gpu_sched drm_buddy video mxm_wmi wmi i2c_algo_bit drm_suballoc_helper drm_ttm_helper ttm drm_display_helper cec
Aug 20 17:10:25 peelz-pc kernel: CPU: 3 PID: 803 Comm: systemd-logind Tainted: G        W          6.10.5-arch1-1 #1 d3097fc3f639001630e5fb5d7653624655f00867
Aug 20 17:10:25 peelz-pc kernel: Hardware name: ASUS System Product Name/ROG CROSSHAIR VIII HERO, BIOS 4702 10/20/2023
Aug 20 17:10:25 peelz-pc kernel: RIP: 0010:amdgpu_dm_atomic_commit_tail+0x3bc2/0x3d30 [amdgpu]
Aug 20 17:10:25 peelz-pc kernel: Code: ff ff 48 8b b1 50 01 00 00 48 8b b8 c8 29 04 00 e8 e3 d2 28 00 4c 8b 9d 68 fe ff ff e9 a4 f7 ff ff 0f 0b e9 bd f4 ff ff 0f 0b <0f> 0b e9 e1 f4 ff ff 0f 0b e9 a1 ca ff ff 48 89 f9 49 8b 7d 28 48
Aug 20 17:10:25 peelz-pc kernel: RSP: 0018:ffffa71506083598 EFLAGS: 00010086
Aug 20 17:10:25 peelz-pc kernel: RAX: ffff8c1953470000 RBX: 0000000000000286 RCX: ffff8c1953470118
Aug 20 17:10:25 peelz-pc kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8c1954c80178
Aug 20 17:10:25 peelz-pc kernel: RBP: ffffa715060837f0 R08: ffffa71506083484 R09: 0000000000000000
Aug 20 17:10:25 peelz-pc kernel: R10: ffffa715060834f0 R11: 0000000000000002 R12: ffff8c1953470118
Aug 20 17:10:25 peelz-pc kernel: R13: 0000000000000001 R14: ffff8c1953470000 R15: ffff8c1d79d10000
Aug 20 17:10:25 peelz-pc kernel: FS:  00007b357aae9f40(0000) GS:ffff8c204e780000(0000) knlGS:0000000000000000
Aug 20 17:10:25 peelz-pc kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 20 17:10:25 peelz-pc kernel: CR2: 00007b5939c331f0 CR3: 0000000105078000 CR4: 0000000000350ef0
Aug 20 17:10:25 peelz-pc kernel: Call Trace:
Aug 20 17:10:25 peelz-pc kernel:  <TASK>
Aug 20 17:10:25 peelz-pc kernel:  ? amdgpu_dm_atomic_commit_tail+0x3bc2/0x3d30 [amdgpu aca26f062e7a11d5f580981bef229896ff3bf81a]
Aug 20 17:10:25 peelz-pc kernel:  ? __warn.cold+0x8e/0xe8
Aug 20 17:10:25 peelz-pc kernel:  ? amdgpu_dm_atomic_commit_tail+0x3bc2/0x3d30 [amdgpu aca26f062e7a11d5f580981bef229896ff3bf81a]
Aug 20 17:10:25 peelz-pc kernel:  ? report_bug+0xff/0x140
Aug 20 17:10:25 peelz-pc kernel:  ? handle_bug+0x3c/0x80
Aug 20 17:10:25 peelz-pc kernel:  ? exc_invalid_op+0x17/0x70
Aug 20 17:10:25 peelz-pc kernel:  ? asm_exc_invalid_op+0x1a/0x20
Aug 20 17:10:25 peelz-pc kernel:  ? amdgpu_dm_atomic_commit_tail+0x3bc2/0x3d30 [amdgpu aca26f062e7a11d5f580981bef229896ff3bf81a]
Aug 20 17:10:25 peelz-pc kernel:  ? amdgpu_dm_atomic_commit_tail+0x306a/0x3d30 [amdgpu aca26f062e7a11d5f580981bef229896ff3bf81a]
Aug 20 17:10:25 peelz-pc kernel:  commit_tail+0x94/0x130
Aug 20 17:10:25 peelz-pc kernel:  drm_atomic_helper_commit+0x11a/0x140
Aug 20 17:10:25 peelz-pc kernel:  drm_atomic_commit+0xa0/0xd0
Aug 20 17:10:25 peelz-pc kernel:  ? __pfx___drm_printfn_info+0x10/0x10
Aug 20 17:10:25 peelz-pc kernel:  drm_client_modeset_commit_atomic+0x203/0x250
Aug 20 17:10:25 peelz-pc kernel:  drm_client_modeset_commit_locked+0x5a/0x160
Aug 20 17:10:25 peelz-pc kernel:  __drm_fb_helper_restore_fbdev_mode_unlocked+0x5e/0xd0
Aug 20 17:10:25 peelz-pc kernel:  drm_fb_helper_set_par+0x30/0x40
Aug 20 17:10:25 peelz-pc kernel:  fb_set_var+0x25f/0x460
Aug 20 17:10:25 peelz-pc kernel:  ? srso_return_thunk+0x5/0x5f
Aug 20 17:10:25 peelz-pc kernel:  ? update_load_avg+0x7e/0x7b0
Aug 20 17:10:25 peelz-pc kernel:  ? srso_return_thunk+0x5/0x5f
Aug 20 17:10:25 peelz-pc kernel:  ? psi_group_change+0x1b0/0x350
Aug 20 17:10:25 peelz-pc kernel:  fbcon_blank+0x200/0x2f0
Aug 20 17:10:25 peelz-pc kernel:  do_unblank_screen+0xb0/0x150
Aug 20 17:10:25 peelz-pc kernel:  complete_change_console+0x54/0x120
Aug 20 17:10:25 peelz-pc kernel:  vt_ioctl+0xec3/0x12c0
Aug 20 17:10:25 peelz-pc kernel:  tty_ioctl+0xe8/0x8a0
Aug 20 17:10:25 peelz-pc kernel:  ? srso_return_thunk+0x5/0x5f
Aug 20 17:10:25 peelz-pc kernel:  ? __seccomp_filter+0x303/0x520
Aug 20 17:10:25 peelz-pc kernel:  __x64_sys_ioctl+0x97/0xd0
Aug 20 17:10:25 peelz-pc kernel:  do_syscall_64+0x82/0x190
Aug 20 17:10:25 peelz-pc kernel:  ? srso_return_thunk+0x5/0x5f
Aug 20 17:10:25 peelz-pc kernel:  ? syscall_exit_to_user_mode+0x72/0x200
Aug 20 17:10:25 peelz-pc kernel:  ? srso_return_thunk+0x5/0x5f
Aug 20 17:10:25 peelz-pc kernel:  ? do_syscall_64+0x8e/0x190
Aug 20 17:10:25 peelz-pc kernel:  ? srso_return_thunk+0x5/0x5f
Aug 20 17:10:25 peelz-pc kernel:  ? evdev_ioctl+0x72/0x90
Aug 20 17:10:25 peelz-pc kernel:  ? srso_return_thunk+0x5/0x5f
Aug 20 17:10:25 peelz-pc kernel:  ? syscall_exit_to_user_mode+0x72/0x200
Aug 20 17:10:25 peelz-pc kernel:  ? srso_return_thunk+0x5/0x5f
Aug 20 17:10:25 peelz-pc kernel:  ? do_syscall_64+0x8e/0x190
Aug 20 17:10:25 peelz-pc kernel:  ? syscall_exit_to_user_mode+0x72/0x200
Aug 20 17:10:25 peelz-pc kernel:  ? srso_return_thunk+0x5/0x5f
Aug 20 17:10:25 peelz-pc kernel:  ? do_syscall_64+0x8e/0x190
Aug 20 17:10:25 peelz-pc kernel:  ? srso_return_thunk+0x5/0x5f
Aug 20 17:10:25 peelz-pc kernel:  ? __irq_exit_rcu+0x4a/0xb0
Aug 20 17:10:25 peelz-pc kernel:  ? srso_return_thunk+0x5/0x5f
Aug 20 17:10:25 peelz-pc kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Aug 20 17:10:25 peelz-pc kernel: RIP: 0033:0x7b357ad23ced
Aug 20 17:10:25 peelz-pc kernel: Code: 04 25 28 00 00 00 48 89 45 c8 31 c0 48 8d 45 10 c7 45 b0 10 00 00 00 48 89 45 b8 48 8d 45 d0 48 89 45 c0 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1a 48 8b 45 c8 64 48 2b 04 25 28 00 00 00
Aug 20 17:10:25 peelz-pc kernel: RSP: 002b:00007ffe0aaac210 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Aug 20 17:10:25 peelz-pc kernel: RAX: ffffffffffffffda RBX: 000000000000000b RCX: 00007b357ad23ced
Aug 20 17:10:25 peelz-pc kernel: RDX: 0000000000000001 RSI: 0000000000005605 RDI: 000000000000000b
Aug 20 17:10:25 peelz-pc kernel: RBP: 00007ffe0aaac260 R08: 00007ffe0aaac1f0 R09: 000062e05869c7f0
Aug 20 17:10:25 peelz-pc kernel: R10: 00007ffe0aaac240 R11: 0000000000000246 R12: 0000000000000000
Aug 20 17:10:25 peelz-pc kernel: R13: 00007ffe0aaac2f0 R14: 000062e05869d120 R15: 000062e05869f600
Aug 20 17:10:25 peelz-pc kernel:  </TASK>
Aug 20 17:10:25 peelz-pc kernel: ---[ end trace 0000000000000000 ]---

System info:

• Distro: Arch Linux
• Kernel: 6.10.5-arch1-1 (also tried 6.6.46 LTS)
• mesa: 24.1.6-1 (using RADV)
• Proton: GE-Proton9-11
• GPU: Radeon 6900 XT

I've been getting very frequent GPU resets (ring gfx_0.0.0 timeout), making it nearly unplayable.

Did you try to set Textures to Medium like suggested in the OP? It fixed the GPU resets for me completely.

Did you try to set Textures to Medium like suggested in the OP? It fixed the GPU resets for me completely.

Just tested it. I crashed within 5 minutes of joining a match.

Edit: I've set textures to "low" and I was able to play 5+ matches without crashing. Nevermind, it still crashes.

Hello, I'm running into a black screen after clicking play on the launcher then building shaders, info below:

Compatibility Report

Name of the game with compatibility issues: Warhammer 40,000: Darktide
Steam AppID of the game: 1361210

System Information

GPU: RX 6800XT
Driver/LLVM version: Mesa 24.3.0-devel
Kernel version: 6.11.0-201.fsync.fc40.x86_64
Proton version: Proton 8.0.5, Proton 9-14, Proton Experimental --- I was able to get this working w/ Proton 8.0-5

I confirm:

[] that I haven't found an existing compatibility report for this game.
[x] that I have checked whether there are updates for my system available.

Symptoms

Fresh install; Click play in launcher, "building shader cache", launcher pops up again with windowed black screen.

steam-1361210.log.gz

Launch params: PROTON_LOG=1 gamemoderun %command%

I want to inform you that after I updated the OS from ubuntu 22.10 to 24.04 I can play the game, with no problems whatsoever, 1080p to 1440p with FSR 3.1 enabled and quality set to medium. The only thing that's missing are the news and the settings button in the splash screen when launching the game. Proton 9.0-3.

Compatibility Report

• Name of the game with compatibility issues: Warhammer 40,000: Darktide
• Steam AppID of the game: 1361210

System Information

• GPU: NVIDIA GeForce RTX 3060
• Video driver version: 4.6.0 NVIDIA 560.35.03
• Kernel version: 5.19.0-43-generic
• Link to full system information report as Gist: System Information
• Proton version: Tested in 6.3-8, 7.0-6, 8.0-5, 9.0-3, Experimental and Hotfix, with gamemoderun and without it. Could reproduce in all of them.

I confirm:

• [ ] that I haven't found an existing compatibility report for this game.
• [x] that I have checked whether there are updates for my system available.

steam-1361210.log

Symptoms

Black screen followed by not responding message right after building shader cache; Seems like the same symptoms as this comment, but in my case 8.0-5 didn't work either.

Reproduction

1. Open the game;
2. Click "Play";
3. Wait for shader cache to build;
4. Black screen pops up and stays there forever (kept it open for about 20 minutes and nothing happened);
5. When alt-tabbed it stops responding too.

Having strange lag in-game, happens in missions and starts randomly (restarting the game fixes the lag until another map, and couple of in-game minutes) and Game comes to slag fest, but does not crash.

Log is full of, not sure if related.

14039.614:0270:031c:warn:vkd3d-proton:d3d12_command_list_QueryInterface: {5b2662fb-eb28-4aec-819e-1c1b4de060f6} not implemented, returning E_NOINTERFACE.
14039.615:0270:03b8:warn:vkd3d-proton:vkd3d_native_sync_handle_release: Failed to release semaphore (#12a).

steam-1361210.zip

EDIT: Tried Experimental, Experimental (BE), 8.0-5, 9.0-3 and GE_18
EDIT2: Happens in all the map, edited the main info.

Replying to https://github.com/ValveSoftware/Proton/issues/6573#issuecomment-2453049928.

I'm having the exact same issue. I've tried Experimental, Hotfix, the last 6 versions of GE - same issue on all. I've also tried launching with gamescope and it's the same issue. I've tried changing in game settings too, including disabling FSR frame gen. Seems to happen at random while in the middle of a match. The game seems to suddenly start only rendering every other frame, causing heavy lag.

I remember having a similar issue in Space Marine (the first one) and that was solved by installing some DX9 dlls. I think this might be to do with dxkv and the DX12 implementation in the game. I can try and take logs next time I play.

Replying to https://github.com/ValveSoftware/Proton/issues/6573#issuecomment-2453049928

I'm having this exact issue, it doesn't crash, only gets insane stuttering after one map. Restarting does fix it, currently I'm having to just restart after every mission.

Found the issue thanks to "Path of Exile 2" - enable "Steam overlay" and use it with this game. Does not get laggy. Can someone else test this? @LazyWings @sithex

Real strange that steam overlay disablement does this...

Found the issue thanks to "Path of Exile 2" - enable "Steam overlay" and use it with this game. Does not get laggy. Can someone else test this? @LazyWings @sithex

Real strange that steam overlay disablement does this...

I can confirm. I had disabled the Steam overlay as part of troubleshooting to figure out why Darktide no longer launched (turned out a recent Bazzite update removed Feral Gamemode) and I forgot to re-enable after solving the problem.

With the overlay off, after ~15 minutes and/or a large horde, the game would start skipping frames or something. It didn't feel like input lag and my ping stayed level throughout. Alt+F4 and rejoining the same game would fix it until halfway through the next game.

I had thought that the removal of Gamemode was the culprit, but it continued after reinstalling and only stopped I found this thread and re-enabling the Steam overlay.

Game crashes to the desktop often at all map endings/finishing steps.

Using LD_PRELOAD="" %command% --lua-heap-mb-size 2048 somewhat mitigates this, but crashes are with most games (usually close to end, before escaping)

Latest crashed game log: steam-1361210.log

The performance issues might be related to this: https://github.com/doitsujin/dxvk/issues/4436.

LD_PRELOAD="" is a workaround.

Warhammer Darktide raytracing crash
...
The game runs fine if raytracing isn't enabled. If it is enabled the game will run for a few seconds after joining the main hub then freeze and eventually exit.

FWIW I had exactly this issue for literally 18 months or so until recently; proton-experimental-bleeding-edge fixed it for me as of around a month ago. I also use the NVIDIA 580.x driver series (and I have a RTX 4080 card).

I note you've already tried Proton Experimental, but have you tried Bleeding Edge?

Thanks for the suggestion @adamdmoss . I didn't even know there was a bleeding edge build! However, it still gives me the same issue unfortunately. I'll look into it a bit more tomorrow and report back if anything changes.

steam-1361210.log

Here's the log from bleeding edge. I see a lot of the following but its the same result. I tried proton ge too but same again;

13738.138:041c:0420:info:nvapi64:Unknown NV_LATENCY_MARKER_TYPE: 13
13738.155:041c:0420:info:nvapi64:Unknown NV_LATENCY_MARKER_TYPE: 14

Ok think I may have fixed it. My settings;

• Proton hotfix
• Vsync off
• frame cap 60
• DLSS enabled set to performance
• Nvidia reflex disabled
• x server settings - force composite pipeline disabled.

The problem was caused by setting DLSS to Automatic. As soon as I re-enable it the game crashes within a few seconds. Hope this helps any future Ogryns bashing their gpu to make shiny pixels.

Actually still doesn't work, if raytracing is disabled I can re-enable it in game and sometimes it will run fine for a bit, sometimes it will freeze and eventually crash. If raytracing is enabled from startup it ill crash within a few seconds reliably. Very odd, I'll just play without raytracing.

Game randomly crashes during gameplay.

GPU: RTX 5070
NVIDIA Driver Version: 580.105.08
CPU: Intel Core Ultra 9 285H
Kernel: 6.17.12-200.nobara.fc43.x86_64 (64-bit)
Proton: GE 10-26/bleeding edge

steam-1361210.log

I don't know if this is a regression or not, but for the last 6 months (I think) I've experienced extreme loading times (into the lobby), like 5 mins or more (I'm running a it from PCI-E 5th gen m.2 drive), sometimes it after a while it just dumps be back into the character select.
After the game has loaded into the lobby it's fine but after character select it takes ages (this is with all mods disabled).

This is all exacerbated by the fact I get frequenter DC to character select which means I then need to wait again to log back in.

So I've confirmed something, after a major patch the game loads normally, but then at some point, I get a CTD and then after that, from that point on the game takes ages to load into the lobby.

I found new issue with Darktide under Proton. The game starts and work fine (without crashing), but constantly throws "Failed binding to network address" error while player account authorization when IPv6 is disabled in the system with ipv6.disable=1 as a kernel parameter. So you can't actually play the game.

When you re-enable IPv6 in your Linux system the game starting completely fine. For notice on Windows Darktide is working even with IPv6 disabled. The other games I've tested under Proton are working without IPv6 as well.

Sadly I need to keep my IPv6 off to have better and smoother web browsing experience. For more details you can look at this thread.

Here's log files from the game itself and Proton log.

The issue appears with various Proton versions.

steam-1361210.log

console-2026-03-16-16.09.48-f97969b6-7b42-4c4e-bf12-ddf9f1c366c3.log

Hello @SP220HawkFire, can you take lsfg-vk out of the mix and check how it behaves?

i removed lsfg-vk as far as i know
(it had me add files to ~/.local/share/applications ~/.local/share/icons/... ~/.local/share/vulkan/implicit_layer.d ~/.local/bin and ~/.local/lib so i just deleted those)
and it seems to work fine! kinda sucks that lsfg-vk was the issue since i know lossless scaling works amazing on other games.
any possible way i can keep lsfg-vk but have it exclude this game?
edit: i just had to make sure i didnt add the game to lsfg-vk :)

Ray tracing causes game freeze and return to desktop after few seconds/couple of minutes with message err:winevulkan:signaller_worker wait timed out with non-empty poll list - no other visible messages or errors.

Hello! Here again with this misterious crash, happening only when I enable RT in the game (either illumination, reflections or both) this time only with Nvidia cards (my rigs have RTX 5080 desktop and RTX 4070 laptop). Interestingly enough, I own a Radeon RX 9070XT as well (changed for the RTX 5080 some days ago) which doesn't show the problem at all, except producing weird super exposed reflections on some scenarios. I diligently tried all the workarounds issued by users on ProtonDB without success. Crash is reproducible on Fedora 43/44 and Gentoo, with different kernels and drivers (6.18 train and 580+ Nvidia drivers, currently using the 595 series) and by using either the official Proton as shipped by Steam or the GE-baked ones (9.0+). Disabling RT solves. Another interesting thing is that pushing on RT with other games, like CP2077, works flawlessy. It might be something strictly related with how the game implements RT and how it interacts with Proton layer and the Nvidia drivers.

System information and journalctl at: https://gist.github.com/rubendelmonte/441f59751320b1ea5c4bc934c4e2bc68
Steam logs at: https://gist.github.com/rubendelmonte/0227ec5856031eb1fe1e054e16e5ba49

Compatibility issue report

Summary

Darktide consistently crashes shortly after pressing Space at the title screen and loading past the "verifying inquisitorial identification" screen.

On an older kernel, the crash caused an amdgpu reset and restarted/killed the X session.

After switching to kernel 7.0.0-14-generic, the desktop survives, but Darktide still crashes. The failure now appears as VK_ERROR_DEVICE_LOST in the Proton/VKD3D log.

What happens

1. Launch Darktide through Steam.
2. Startup logos and cinematic play normally.
3. Reach title screen.
4. Press Space to continue.
5. Game loads through the black "verifying inquisitorial identification" screen.
6. Splash art appears again briefly and game audio can be heard.
7. Game crashes.

System

Game: Warhammer 40,000: Darktide
Steam App ID: 1361210
GPU: AMD Radeon RX 5700 XT / Navi10
Kernel: 7.0.0-14-generic
Mesa/RADV: 26.1.3
(AMD open-source Vulkan driver also tested: 2.0.349)
Proton tested: GE-Proton10-31, GE-Proton10-32
Desktop: Linux Mint / X11

Relevant log lines

From steam-1361210.log:

vkd3d-proton:d3d12_command_queue_flush_waiters: Failed to submit semaphore waits, vr -4.
vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
vkd3d-proton:d3d12_device_mark_as_removed: Device is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
winevulkan:signaller_worker wait timed out with non-empty poll list.

Earlier logs on the older kernel showed:

amdgpu_job_timedout: ring gfx_0.0.0 timeout
GPU reset begin
VRAM is lost due to GPU reset

On kernel 7.0.0-14-generic, the GPU/session recovery is better, but the game still crashes with device lost.

Tests already performed

• GE-Proton10-31: crashes
• GE-Proton10-32: crashes
• Proton Experimental: game does not launch
• RADV 26.1.3: crashes
• AMD open-source Vulkan driver 2.0.349: crashes the same way
• Conservative GPU profile in LACT:
  • reduced power limit (-15%)
  • core clock capped at 1750 MHz
• Safe/low Darktide config:
  • lower graphics settings
  • no ray tracing
  • 60 FPS cap attempted
• Tested launch options:
  • PROTON_LOG=1 %command%
  • PROTON_LOG=1 RADV_DEBUG=nodcc %command%
  • PROTON_LOG=1 VKD3D_CONFIG=single_queue,no_upload_hvv,nodxr VKD3D_FRAME_RATE=60 %command%
  • forced RADV Vulkan ICD
  • forced AMD open-source Vulkan ICD

Attached logs

darktide-kernel-gpu.log
steam-1361210.log
console-2026-06-29-02.44.54-37d76643-d4d4-4c92-a9b0-c1b6dfb5d373.log

Compatibility Report

• Name of the game with compatibility issues: Warhammer 40,000: Darktide
• Steam AppID of the game: 1361210

System Information

• GPU: AMD Radeon RX 6700M
• Video driver version: Mesa 26.1.3
• Kernel version: 7.1.2-1-default
• Link to full system information report as Gist: https://gist.github.com/Ortinik/79db2eb582924778dc32a6460aa9833d
• Proton version: Proton Experimental, Proton 11.0, GE-Proton10-34, GE-Proton11-1

I confirm:

• [x] that I haven't found an existing compatibility report for this game.
• [x] that I have checked whether there are updates for my system available.

steam-1361210.log

Symptoms

Reproduction

1. Launch Darktide.
2. Log into account and select any character.
3. Log into the hub.
4. Open Loadout or Cosmetics menus (Esc -> Operative -> Loadout or Cosmetics tab).
5. Notice that item preview tiles are broken.

The issue was also reported on reddit by some other Proton users - https://www.reddit.com/r/DarkTide/comments/1udmub4/icons_not_fully_rendering_arch_linux/

On 4080 (lastest cachyOS, 7.1.2-2-cachyos, 610.43.02 drivers) using DLSS and "transformer model" game crashes, can be in seconds or minutes (in-missions). Using CNN fixes it (just get graphical glitches like bended or wrong object frame (as older tech, might be normal).

Will get logs - but seems to be on experimental (inc. bleeding-edge), proton 11, even GE latest one. Posted this so other can verify, might be ME issue. Will get logs later.

Switching from Transformer to CNN still crashes the game in the same instance. But afterwards its fine.