DOOM: The Dark Ages

Help
1

Crashes after 15 seconds of play. Wonder if it’s Wine, or NixOS or me? Can’t get logs :sob: anyone else in the vast net experience this so far - game is very new

2

well, I guess it’s drivers?

May 17 21:36:23 zits kernel: umip: Titan[77881] ip:155d7011b sp:8119b0: SGDT instruction cannot be used by applications.
May 17 21:36:23 zits kernel: umip: Titan[77881] ip:155d7011b sp:8119b0: For now, expensive software emulation returns the result.
May 17 21:36:32 zits kernel: amdgpu 0000:0d:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32784)
May 17 21:36:32 zits kernel: amdgpu 0000:0d:00.0: amdgpu:  in process Titan pid 77881 thread Foreground Work pid 77941)
May 17 21:36:32 zits kernel: amdgpu 0000:0d:00.0: amdgpu:   in page starting at address 0x0000000474469000 from client 10
May 17 21:36:32 zits kernel: amdgpu 0000:0d:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00601030
May 17 21:36:32 zits kernel: amdgpu 0000:0d:00.0: amdgpu:          Faulty UTCL2 client ID: TCP (0x8)
May 17 21:36:32 zits kernel: amdgpu 0000:0d:00.0: amdgpu:          MORE_FAULTS: 0x0
May 17 21:36:32 zits kernel: amdgpu 0000:0d:00.0: amdgpu:          WALKER_ERROR: 0x0
May 17 21:36:32 zits kernel: amdgpu 0000:0d:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
May 17 21:36:32 zits kernel: amdgpu 0000:0d:00.0: amdgpu:          MAPPING_ERROR: 0x0
May 17 21:36:32 zits kernel: amdgpu 0000:0d:00.0: amdgpu:          RW: 0x0
May 17 21:36:51 zits steam[74520]: src/clientdll/steamengine.cpp (2868) : Assertion Failed: CSteamEngine::BMainLoop appears to have stalled > 15 seconds without event signalled
May 17 21:36:51 zits steam[74520]: src/clientdll/steamengine.cpp (2868) : Assertion Failed: CSteamEngine::BMainLoop appears to have stalled > 15 seconds without event signalled
May 17 21:36:51 zits steam[74520]: assert_20250517213651_37.dmp[85332]: Uploading dump (out-of-process)
May 17 21:36:51 zits steam[74520]: /tmp/dumps/assert_20250517213651_37.dmp
May 17 21:36:51 zits assert_20250517213651_37.dmp[85332]: Uploading dump (out-of-process)
                                                          /tmp/dumps/assert_20250517213651_37.dmp
May 17 21:36:52 zits assert_20250517213651_37.dmp[85332]: Finished uploading minidump (out-of-process): success = yes
May 17 21:36:52 zits assert_20250517213651_37.dmp[85332]: response: CrashID=bp-3acdff9f-76f6-477f-ad5d-fa8412250517
May 17 21:36:52 zits steam[74520]: assert_20250517213651_37.dmp[85332]: Finished uploading minidump (out-of-process): success = yes
May 17 21:36:52 zits steam[74520]: assert_20250517213651_37.dmp[85332]: response: CrashID=bp-3acdff9f-76f6-477f-ad5d-fa8412250517
May 17 21:36:52 zits steam[74520]: assert_20250517213651_37.dmp[85332]: file ''/tmp/dumps/assert_20250517213651_37.dmp'', upload yes: ''CrashID=bp-3acdff9f-76f6-477f-ad5d-fa8412250517''
May 17 21:36:52 zits assert_20250517213651_37.dmp[85332]: file ''/tmp/dumps/assert_20250517213651_37.dmp'', upload yes: ''CrashID=bp-3acdff9f-76f6-477f-ad5d-fa8412250517''
May 17 21:37:34 zits kernel: amdgpu 0000:0d:00.0: amdgpu: Dumping IP State
May 17 21:37:34 zits kernel: amdgpu 0000:0d:00.0: amdgpu: Dumping IP State Completed
May 17 21:37:34 zits kernel: amdgpu 0000:0d:00.0: amdgpu: ring comp_1.2.0 timeout, but soft recovered
May 17 21:37:34 zits kernel: amdgpu 0000:0d:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32784)
May 17 21:37:34 zits kernel: amdgpu 0000:0d:00.0: amdgpu:  in process Titan pid 77881 thread Foreground Work pid 77928)
May 17 21:37:34 zits kernel: amdgpu 0000:0d:00.0: amdgpu:   in page starting at address 0x0000000474400000 from client 10
May 17 21:37:34 zits kernel: amdgpu 0000:0d:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00601031
May 17 21:37:34 zits kernel: amdgpu 0000:0d:00.0: amdgpu:          Faulty UTCL2 client ID: TCP (0x8)
May 17 21:37:34 zits kernel: amdgpu 0000:0d:00.0: amdgpu:          MORE_FAULTS: 0x1
May 17 21:37:34 zits kernel: amdgpu 0000:0d:00.0: amdgpu:          WALKER_ERROR: 0x0
May 17 21:37:34 zits kernel: amdgpu 0000:0d:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
May 17 21:37:34 zits kernel: amdgpu 0000:0d:00.0: amdgpu:          MAPPING_ERROR: 0x0
May 17 21:37:34 zits kernel: amdgpu 0000:0d:00.0: amdgpu:          RW: 0x0
May 17 21:37:34 zits kernel: amdgpu 0000:0d:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32784)
May 17 21:37:34 zits kernel: amdgpu 0000:0d:00.0: amdgpu:  in process Titan pid 77881 thread Foreground Work pid 77928)
May 17 21:37:34 zits kernel: amdgpu 0000:0d:00.0: amdgpu:   in page starting at address 0x000000047d41a000 from client 10
3

Yep, looks like it, try a newer kernel, amdgpu is an in-tree module.

4

I am on latest :sob: Id recommends using amd’s latest drivers & patching is possible but arduous - I think I’ll give it a few weeks and try again then.

5

Also just not really how it works in Linux land. In-tree modules just update with the kernel, if you’re on the latest kernel there is no later amd gpu driver for Linux yet; you’ll just have to wait until amd fix their driver.

I don’t think it’s advisable to use an unreleased kernel version just because of a buggy game.

Edit: FWIW, with NixOS 25.05 and onwards using a different mesa will become much easier:

{ nixpkgs-unstable, ... }: {
  hardware.graphics = {
    package = nixpkgs-unstable.mesa;
    package32 = nixpkgs-unstable.pkgsi686Linux.mesa;
  };
}

for the time being, you can also run nixpkgs-unstable, since that already has the mesa version recommended on protondb. There seem to be workarounds to at least get the game to run on older versions, too.

1 Like
6

Hey, unstable let me get through more of level 1 before a crash that resulted in a bug report window! They really rushed this one out, alas! Anyway, many thanks. It works and will only get better :crossed_fingers: