Game: Steam Machine crashes with GPU device lost during title/intro #1622

Open
opened 2026-11-18 17:11:34 +00:00 by BeanBot · 1 comment
Member

Reported on Discord

Longshot version and channel

nightly-475-79d4a143 (source c38536ba), nightly. The report was made from this build; the reporter says nightly 484.

What happened and how to reproduce

Starting Longshot on SteamOS, it closes unexpectedly within seconds with VK_ERROR_DEVICE_LOST. The reporter says it happens every time on launch. Expected the game to launch.

Where in the game and frequency

Title and intro; every launch, according to the report.

GPU and driver

AMD Steam Machine (RADV NAVI33), RADV Mesa 26.2.0-devel (git-b73996432f) according to the attached in-game report. The reporter's system details say Mesa 26.1.2 (git-18b3910ac0); please clarify which driver build was active for the latest reproduction.

CPU, RAM and OS

AMD Custom CPU 1772 (12 threads), 16 GiB RAM; SteamOS 3.11 build 20261117.1000, kernel 7.3.1-valve3-1-neptune-73-g6fbfd992c8fe, Wayland. The report lists 15 GB.

Settings and overlays

Reporter says no settings changed and no overlays/injectors. Attached report lists 0 settings changed from defaults (though settings include output resolution 2560x1440 and upscaling 1).

Crash/log excerpt

The crash report says it ran for 6 seconds, reason device lost. Relevant ending of longshot_log.txt:

[hos sead::MainThread] vk: batched submit 638 failed (-4)
[hos host] vk: device lost: reading the fault info (RX_VK_CHECKPOINTS=1 for markers)
[hos host] vk: device fault: 
[hos host] vk: FATAL: the GPU device was lost (VK_ERROR_DEVICE_LOST): the driver stopped or reset the GPU, and nothing sent to it runs any more (on Linux, dmesg or journalctl -k around this time names the reset)

The reporter supplied this dmesg excerpt:

[ 4098.990872]  ? __x64_sys_futex+0x136/0x220
[ 4098.990875]  ? do_syscall_64+0xc9/0x570
[ 4098.990878]  ? srso_alias_return_thunk+0x5/0xfbef5
[ 4098.990881]  ? srso_alias_return_thunk+0x5/0xfbef5
[ 4098.990883]  ? srso_alias_return_thunk+0x5/0xfbef5
[ 4098.990885]  ? do_syscall_64+0x35/0x570
[ 4098.990888]  entry_SYSCALL_64_after_hwframe+0x76/0x7e
[ 4098.990891] RIP: 0033:0x7f4d16b1e46d
[ 4098.990896] Code: Unable to access opcode bytes at 0x7f4d16b1e443.
[ 4098.990897] RSP: 002b:00007f4cf3bf0908 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
[ 4098.990900] RAX: fffffffffffffe00 RBX: 00007f4d04052170 RCX: 00007f4d16b1e46d
[ 4098.990901] RDX: 00000000000010e5 RSI: 0000000000000080 RDI: 00007f4d040521a8
[ 4098.990903] RBP: 0000000000000000 R08: 0000000000000000 R09: 00007f4d00000000
[ 4098.990904] R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
[ 4098.990906] R13: 0000000000000000 R14: 00007f4d040521a8 R15: 00000000000010e5
[ 4098.990911]  </TASK>
[ 4098.990912] ---[ end trace 0000000000000000 ]---

Attachments

The attached bug-reports.zip contains the in-game report and crash records. Its report is bug-reports/pending/report-20261118T055841Z.txt; retain the archive/member as the source attachment. It includes a long log tail and crash records.

Still unknown

  • Whether nightly 484 reproduces the same device-lost crash and the full report/log for that exact run.
  • Whether launch was from Steam Gaming Mode or Desktop Mode.
  • The exact Mesa/driver version used on the 484 reproduction, given the mismatch in reported versions.
  • Whether the kernel trace excerpt is from the same crash/time; more surrounding kernel/journal lines would help.
  • Confirmation of the Steam Machine model/hardware identity (the report names AMD Steam Machine, RADV NAVI33).
Reported on [Discord](https://discord.com/channels/1569849200047427645/1572656344979210341/1572656344979210341) ### Longshot version and channel nightly-475-79d4a143 (source c38536ba), nightly. The report was made from this build; the reporter says nightly 484. ### What happened and how to reproduce Starting Longshot on SteamOS, it closes unexpectedly within seconds with `VK_ERROR_DEVICE_LOST`. The reporter says it happens every time on launch. Expected the game to launch. ### Where in the game and frequency Title and intro; every launch, according to the report. ### GPU and driver AMD Steam Machine (RADV NAVI33), RADV Mesa 26.2.0-devel (git-b73996432f) according to the attached in-game report. The reporter's system details say Mesa 26.1.2 (git-18b3910ac0); please clarify which driver build was active for the latest reproduction. ### CPU, RAM and OS AMD Custom CPU 1772 (12 threads), 16 GiB RAM; SteamOS 3.11 build 20261117.1000, kernel 7.3.1-valve3-1-neptune-73-g6fbfd992c8fe, Wayland. The report lists 15 GB. ### Settings and overlays Reporter says no settings changed and no overlays/injectors. Attached report lists 0 settings changed from defaults (though settings include output resolution 2560x1440 and upscaling 1). ### Crash/log excerpt The crash report says it ran for 6 seconds, reason `device lost`. Relevant ending of `longshot_log.txt`: ```text [hos sead::MainThread] vk: batched submit 638 failed (-4) [hos host] vk: device lost: reading the fault info (RX_VK_CHECKPOINTS=1 for markers) [hos host] vk: device fault: [hos host] vk: FATAL: the GPU device was lost (VK_ERROR_DEVICE_LOST): the driver stopped or reset the GPU, and nothing sent to it runs any more (on Linux, dmesg or journalctl -k around this time names the reset) ``` The reporter supplied this dmesg excerpt: ```text [ 4098.990872] ? __x64_sys_futex+0x136/0x220 [ 4098.990875] ? do_syscall_64+0xc9/0x570 [ 4098.990878] ? srso_alias_return_thunk+0x5/0xfbef5 [ 4098.990881] ? srso_alias_return_thunk+0x5/0xfbef5 [ 4098.990883] ? srso_alias_return_thunk+0x5/0xfbef5 [ 4098.990885] ? do_syscall_64+0x35/0x570 [ 4098.990888] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 4098.990891] RIP: 0033:0x7f4d16b1e46d [ 4098.990896] Code: Unable to access opcode bytes at 0x7f4d16b1e443. [ 4098.990897] RSP: 002b:00007f4cf3bf0908 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca [ 4098.990900] RAX: fffffffffffffe00 RBX: 00007f4d04052170 RCX: 00007f4d16b1e46d [ 4098.990901] RDX: 00000000000010e5 RSI: 0000000000000080 RDI: 00007f4d040521a8 [ 4098.990903] RBP: 0000000000000000 R08: 0000000000000000 R09: 00007f4d00000000 [ 4098.990904] R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff [ 4098.990906] R13: 0000000000000000 R14: 00007f4d040521a8 R15: 00000000000010e5 [ 4098.990911] </TASK> [ 4098.990912] ---[ end trace 0000000000000000 ]--- ``` ### Attachments The attached `bug-reports.zip` contains the in-game report and crash records. Its report is `bug-reports/pending/report-20261118T055841Z.txt`; retain the archive/member as the source attachment. It includes a long log tail and crash records. ### Still unknown - Whether nightly 484 reproduces the same device-lost crash and the full report/log for that exact run. - Whether launch was from Steam Gaming Mode or Desktop Mode. - The exact Mesa/driver version used on the 484 reproduction, given the mismatch in reported versions. - Whether the kernel trace excerpt is from the same crash/time; more surrounding kernel/journal lines would help. - Confirmation of the Steam Machine model/hardware identity (the report names AMD Steam Machine, RADV NAVI33).
Author
Member

Files from the Discord report:

Files from the Discord report: - [report-20261118T055841Z.txt](https://git.magicbean.dev/attachments/60b0771a-14d9-422a-999f-3b8b8403261c)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Longshot#1622
No description provided.