Weird freezing on Wolfenstein: The New Order. Only on desktop, not Steam Deck. Is Valve interested in a bug report?
Weird freezing on Wolfenstein: The New Order. Only on desktop, not Steam Deck. Is Valve interested in a bug report?
I'm on Kubuntu 24.04, rocking a build that was pretty darn high end in 2021 with an AMD 6800 XT, and of course, Wolfenstein: The New Order was already old news by then. Proton does miracles, but this game freezes my entire machine. The last time I saw something like this happen was with Monster Hunter World in 2018, on a much older version of Proton. I can reliably get the game to freeze my machine in the opening level of The New Order, even across multiple versions of Proton, even with the renderapi launch parameter that should switch it back to OpenGL. Of course, even if I report this to Steam support, they'll tell me that they only support Steam Deck and not bespoke Linux desktops, and the game works fine on my Steam Deck, but would they be interested in some logs and a bug reported against the GitHub project? This is assuming no one here has an easy fix, of course. But if not, how would I get the logs? I wouldn't know what I'm looking at in those logs, personally. I'm also not sure if they'll write out correctly. Because it freezes the entire machine, I end up having to hard shut down the computer by the power button, and once or twice during my experiments, it failed to mount my game SSD (a separate drive from where my OS is installed) at boot, and I had to set up the automatic mount in the partition manager again. So assuming that doesn't impact the ability to write out the logs, I can collect them with some instructions, if you kind strangers in the know wouldn't mind providing them, please. And if Valve is interested in looking at them.
You're viewing a single thread.
https://github.com/ValveSoftware/Proton/wiki/Proton-FAQ
Add this as a Steam launch option for the game:`PROTON_LOG=1 %command%` How? 1. Right-click on the game title under the Library in Steam and select Properties. 2. Under the General tab click the Set launch options... button. 3. Enter the above code in. Logs will be saved to $HOME/steam-$STEAM\_APP\_ID.log, overwriting any previous log with that name.
If it’s happening on your desktop but not the steamdeck, my first assumption would be an issue with your desktop software/hardware.
Might want to check OS logs at the same time of the crash as well.
https://linuxhandbook.com/journalctl-command/
I don’t see anyone else mention crashing: https://www.protondb.com/app/201810?device=pc
Alright, from journalctl, I can for sure identify exactly where my computer hung. That last line that repeats itself? It repeats itself thousands of times until I shut the machine down. Does that mean anything to you?
Aug 03 12:58:26 Compy-5600X steam[4057]: 08/03 12:58:26 minidumps folder is set to /tmp/dumps Aug 03 12:58:26 Compy-5600X steam[4057]: 08/03 12:58:26 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(20240716232148)/tid(1798223) Aug 03 12:58:26 Compy-5600X steam[4057]: 08/03 12:58:26 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(1.0)/tid(1798223) Aug 03 12:58:36 Compy-5600X kernel: input: Microsoft X-Box 360 pad 0 as /devices/virtual/input/input105 Aug 03 13:00:04 Compy-5600X systemd[1]: Starting sysstat-collect.service - system activity accounting tool... Aug 03 13:00:04 Compy-5600X systemd[1]: sysstat-collect.service: Deactivated successfully. Aug 03 13:00:04 Compy-5600X systemd[1]: Finished sysstat-collect.service - system activity accounting tool. Aug 03 13:00:33 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:4 pasid:32798, for process WolfNewOrder_x6 pid 1798131 thread WolfNewOrd:cs0 pid 1798172) Aug 03 13:00:33 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu: in page starting at address 0x0000e8674353a000 from client 0x1b (UTCL2) Aug 03 13:00:33 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00401430 Aug 03 13:00:33 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu: Faulty UTCL2 client ID: SQC (data) (0xa) Aug 03 13:00:33 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu: MORE_FAULTS: 0x0 Aug 03 13:00:33 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu: WALKER_ERROR: 0x0 Aug 03 13:00:33 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Aug 03 13:00:33 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu: MAPPING_ERROR: 0x0 Aug 03 13:00:33 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu: RW: 0x0 Aug 03 13:00:43 Compy-5600X kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=815617255, emitted seq=815617257 Aug 03 13:00:43 Compy-5600X kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process WolfNewOrder_x6 pid 1798131 thread WolfNewOrd:cs0 pid 1798172 Aug 03 13:00:43 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu: GPU reset begin! Aug 03 13:00:44 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu: MODE1 reset Aug 03 13:00:44 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu: GPU mode1 reset Aug 03 13:00:44 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu: GPU smu mode1 reset Aug 03 13:00:44 Compy-5600X kernel: amdgpu 0000:0a:00.0: amdgpu: GPU reset succeeded, trying to resume Aug 03 13:00:44 Compy-5600X kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000F00000). Aug 03 13:00:44 Compy-5600X kernel: [drm] VRAM is lost due to GPU reset! Aug 03 13:00:44 Compy-5600X kernel: [drm] PSP is resuming... Aug 03 13:00:44 Compy-5600X kernel: [drm] reserve 0xa00000 from 0x83fd000000 for PSP TMR Aug 03 13:00:45 Compy-5600X plasmashell[1970]: amdgpu: amdgpu_cs_query_fence_status failed. Aug 03 13:00:45 Compy-5600X steam[4057]: amdgpu: amdgpu_cs_query_fence_status failed. Aug 03 13:00:45 Compy-5600X steam[4057]: amdgpu: amdgpu_cs_query_fence_status failed. Aug 03 13:00:45 Compy-5600X steam[4057]: amdgpu: amdgpu_cs_query_fence_status failed. Aug 03 13:00:45 Compy-5600X steam[4057]: amdgpu: amdgpu_cs_query_fence_status failed. Aug 03 13:00:45 Compy-5600X steam[4057]: amdgpu: amdgpu_cs_query_fence_status failed.I can also get the Proton logs if you still need them, but that will have to come later, since it's an ordeal to plan for a scenario where my desktop will crash.
This is just a guess, but I imagine kubuntu probably has a slightly dated kernel / mesa versions. My understanding is that As much as we wouldn’t like it to be the case, there’s still issues with AMD. It’s not totally perfect and Improvements and fixes are being added to the kernel and mesa packages all the time.
Maybe someone on AMD can confirm?
I own the game and did not experience a crash when playing through it on my nvidia system last year.
To be fair, I can't find evidence of anyone on the internet experiencing this same freeze, so it's probably more specific to me than AMD in general. When I saw freezes like this in Monster Hunter, years ago, I was on Nvidia.
If it's an amdgpu bug try reporting it to the amd linux gitlab
Have you ever tested your RAM? Like a proper memtest overnight?
If I ever suspect hardware, I also stress test the cpu with prime95.
I could give it a shot. Will it test VRAM too? Last I ran memtest was years ago. It needs a boot device like a USB, right?
Thanks. I'll give it a go. I don't think I'm convinced it's a hardware issue, since that error says something about permissions and faulty IDs, but what do I know? Couldn't hurt to check.
I’m not so sure it is either, but since you’re on kubuntu you don’t easily have access to newer mesa/kernel to test software.
Troubleshooting is not about finding the issue right away, it’s about eliminating by going through all of it and trying it to narrow it down.
Have you tried a distro with a bit more recent packages? If it also crashes then we know it’s more likely something with your hardware.
I'm not in a position to test on more than just these two machines/distros. Once upon a time, I tried switching to Fedora, but some of the behaviors were not to my liking, so I went back to Kubuntu.
I’ll end it here.
If you are curious I’d check out the following link and see what version of mesa you are running vs the latest. Maybe you can find more info or other experiences from users on that specific version.
https://linuxcapable.com/how-to-upgrade-mesa-drivers-on-ubuntu-linux/
If you want to explore a newer kernel: https://ubuntuhandbook.org/index.php/2023/08/install-latest-kernel-new-repository/amp/
Finally, I’m curious if you boot using USB into a live distro like Nobara, if you can manage to test the game. Or even actually install Nobara to a spare USB drive drive and test the game.
Maybe someone else can chime in, but that’s about all I can think of. If you want to find a root cause, you have to run through and find what’s not the issue.