Game: v3.1.0 GPU hang (VK_ERROR_DEVICE_LOST, NVIDIA Xid 109) when pulling the Master Sword (Temple of Time), Linux/gamescope, RTX 5060 Ti #2195

Closed
opened 2026-11-22 03:05:57 +00:00 by xenovorx · 2 comments

Longshot version

v3.1.0

Channel

Release

What kind of problem

Crash, freeze or black screen

What happened

After updating from v3.0.0 to v3.1.0, the game freezes and closes with "the GPU device was lost (VK_ERROR_DEVICE_LOST)" three runs in a row. Each time the kernel logs an NVIDIA Xid 109 (CTX SWITCH TIMEOUT) for the longshot process, so the GPU hangs and the driver resets the channel.

  • Run 1 (run_id 491ca9519cbd09bf86df774951a6166f, longshot_log.2.txt): about 8 minutes of normal play at 60 fps (Bottom of the Well -> Kakariko -> Market -> Hyrule Field). Froze right after entering Hyrule Field (child) from the Market: fps fell to 7, then 0.2, then device lost. Checkpoints: stage 0x1 at marker 28675075 (write-back of pool 000000102dc00000, frame 29391); before it an INDIRECT dispatch of program 685adb41edc19de7 and a dispatch of 6637ac1d052d22d4.
  • Run 2 (run_id 4baad5bf8da5f52026740f58c4c08571, longshot_log.1.txt) and run 3 (run_id 5f0cc60d951d754e88b09e4726f625a4, longshot_log.txt): loaded the save in Castle Town Market (child, right after finishing Bottom of the Well / Lens of Truth), walked to the Temple of Time and pulled the Master Sword from the Pedestal of Time. Both froze during the sword pull, about 45-55 s after starting, at THE SAME DRAW: checkpoint stage 0x1 = draw of program d905f52b7517c681 (after a436621aac894ccf, 37c7c71dd10303b7 and fa80653c8974bfbb x4). Each one logged "upload chunk wait failed (-4)" and "wait for fence ...: -4" just before.

Crash records (bug-reports/pending): reason "device lost", thread host, module_offset longshot+0x2272e470, backtrace longshot+0x2272e470 <- longshot+0x22715004.

Kernel:
NVRM: Xid (PCI:0000:01:00): 109, pid=30571, name=longshot, channel 0x00000021, errorString CTX SWITCH TIMEOUT, Info 0x7c01a
NVRM: Xid (PCI:0000:01:00): 109, pid=32106, name=longshot, channel 0x00000019, errorString CTX SWITCH TIMEOUT, Info 0x5c019
NVRM: Xid (PCI:0000:01:00): 109, pid=32474, name=longshot, channel 0x00000019, errorString CTX SWITCH TIMEOUT, Info 0x5c019

This PC had no Xid at all in November before this (rc.3 to v3.0.0 played fine, same saves, same driver). Nothing else changed between v3.0.0 and v3.1.0: same driver, kernel, gamescope and options file. The v3.1.0 build had 0 failures, and the title screen ran at 60 fps in a test start.

Where in the game

Temple of Time (child), pulling the Master Sword from the Pedestal of Time after Bottom of the Well (twice, same draw, ~45-55 s after loading the save in the Market); once when entering Hyrule Field (child) from the Market

How often

Every time

Graphics card and driver version

NVIDIA GeForce RTX 5060 Ti 16 GB, NVIDIA 620.70.06 (open kernel modules, linux-cachyos-deckify-nvidia-open)

CPU, RAM and operating system

Intel Core i7-14700K, 32 GB, CachyOS (Handheld Edition, kernel 7.3.4-1-cachyos-deckify), Steam game mode (gamescope 3.17.0), 2560x1440 60 Hz TV

Changes from the defaults

Built with the AppImage on the command line: --cli --update game --work work --jobs 8 --fetch-ngx-sdk --accept-nvidia-license (LONGSHOT_NGX_SDK set), so DLSS is built in.
Options: dlss=2 (DLAA, "NVIDIA DLAA after the game's bloom and tone map"), nvidia_reflex=1, frame_generation=0, hdr=0, vsync=0, frame_rate_cap=0, ultrawide=1, field_of_view=100, anisotropic_filtering=4, shadow_resolution=0, output_res=2048x1152.
No longshot_env.txt. Started from a Steam non-Steam shortcut with LD_PRELOAD="" %command% (so no Steam overlay). No ReShade, MangoHud or vkBasalt in the log.

longshot_log.txt

attached bellow

Screenshots or video

No response

Before you send it

  • The problem is still there on the newest release or nightly.
  • I searched the open issues for it.
  • I'm not attaching game files, keys, the game's executable, its .bin caches or saves.
### Longshot version v3.1.0 ### Channel Release ### What kind of problem Crash, freeze or black screen ### What happened After updating from v3.0.0 to v3.1.0, the game freezes and closes with "the GPU device was lost (VK_ERROR_DEVICE_LOST)" three runs in a row. Each time the kernel logs an NVIDIA Xid 109 (CTX SWITCH TIMEOUT) for the longshot process, so the GPU hangs and the driver resets the channel. - Run 1 (run_id 491ca9519cbd09bf86df774951a6166f, longshot_log.2.txt): about 8 minutes of normal play at 60 fps (Bottom of the Well -> Kakariko -> Market -> Hyrule Field). Froze right after entering Hyrule Field (child) from the Market: fps fell to 7, then 0.2, then device lost. Checkpoints: stage 0x1 at marker 28675075 (write-back of pool 000000102dc00000, frame 29391); before it an INDIRECT dispatch of program 685adb41edc19de7 and a dispatch of 6637ac1d052d22d4. - Run 2 (run_id 4baad5bf8da5f52026740f58c4c08571, longshot_log.1.txt) and run 3 (run_id 5f0cc60d951d754e88b09e4726f625a4, longshot_log.txt): loaded the save in Castle Town Market (child, right after finishing Bottom of the Well / Lens of Truth), walked to the Temple of Time and pulled the Master Sword from the Pedestal of Time. Both froze during the sword pull, about 45-55 s after starting, at THE SAME DRAW: checkpoint stage 0x1 = draw of program d905f52b7517c681 (after a436621aac894ccf, 37c7c71dd10303b7 and fa80653c8974bfbb x4). Each one logged "upload chunk wait failed (-4)" and "wait for fence ...: -4" just before. Crash records (bug-reports/pending): reason "device lost", thread host, module_offset longshot+0x2272e470, backtrace longshot+0x2272e470 <- longshot+0x22715004. Kernel: NVRM: Xid (PCI:0000:01:00): 109, pid=30571, name=longshot, channel 0x00000021, errorString CTX SWITCH TIMEOUT, Info 0x7c01a NVRM: Xid (PCI:0000:01:00): 109, pid=32106, name=longshot, channel 0x00000019, errorString CTX SWITCH TIMEOUT, Info 0x5c019 NVRM: Xid (PCI:0000:01:00): 109, pid=32474, name=longshot, channel 0x00000019, errorString CTX SWITCH TIMEOUT, Info 0x5c019 This PC had no Xid at all in November before this (rc.3 to v3.0.0 played fine, same saves, same driver). Nothing else changed between v3.0.0 and v3.1.0: same driver, kernel, gamescope and options file. The v3.1.0 build had 0 failures, and the title screen ran at 60 fps in a test start. ### Where in the game Temple of Time (child), pulling the Master Sword from the Pedestal of Time after Bottom of the Well (twice, same draw, ~45-55 s after loading the save in the Market); once when entering Hyrule Field (child) from the Market ### How often Every time ### Graphics card and driver version NVIDIA GeForce RTX 5060 Ti 16 GB, NVIDIA 620.70.06 (open kernel modules, linux-cachyos-deckify-nvidia-open) ### CPU, RAM and operating system Intel Core i7-14700K, 32 GB, CachyOS (Handheld Edition, kernel 7.3.4-1-cachyos-deckify), Steam game mode (gamescope 3.17.0), 2560x1440 60 Hz TV ### Changes from the defaults Built with the AppImage on the command line: --cli --update game --work work --jobs 8 --fetch-ngx-sdk --accept-nvidia-license (LONGSHOT_NGX_SDK set), so DLSS is built in. Options: dlss=2 (DLAA, "NVIDIA DLAA after the game's bloom and tone map"), nvidia_reflex=1, frame_generation=0, hdr=0, vsync=0, frame_rate_cap=0, ultrawide=1, field_of_view=100, anisotropic_filtering=4, shadow_resolution=0, output_res=2048x1152. No longshot_env.txt. Started from a Steam non-Steam shortcut with LD_PRELOAD="" %command% (so no Steam overlay). No ReShade, MangoHud or vkBasalt in the log. ### longshot_log.txt attached bellow ### Screenshots or video _No response_ ### Before you send it - [x] The problem is still there on the newest release or nightly. - [x] I searched the open issues for it. - [x] I'm not attaching game files, keys, the game's executable, its .bin caches or saves.
Member

Possibly related, for context:

  • issue #606 Game: Arc B390 (Panther Lake iGPU, Windows): the GPU is lost a few minutes into play, twice at a dispatch of compute program 499dbfd0721d2858 — Similar intermittent GPU device-loss/hang during gameplay, but different GPU/OS and failing work.
  • PR #1220 fix(vk): the write-back diff pass has a checkpoint of its own in device-lost reports — Merged diagnostic checkpoint change; informs interpretation of the write-back checkpoint, not a fix for this hang.
Possibly related, for context: - issue #606 Game: Arc B390 (Panther Lake iGPU, Windows): the GPU is lost a few minutes into play, twice at a dispatch of compute program 499dbfd0721d2858 — Similar intermittent GPU device-loss/hang during gameplay, but different GPU/OS and failing work. - PR #1220 fix(vk): the write-back diff pass has a checkpoint of its own in device-lost reports — Merged diagnostic checkpoint change; informs interpretation of the write-back checkpoint, not a fix for this hang.
Author

Fixed in v3.1.1, thanks!

Same PC, driver, kernel, gamescope and options as in the report. After rebuilding with v3.1.1 (DLSS built in), I loaded the same save in the Market, walked to the Temple of Time and pulled the Master Sword (child, after Bottom of the Well) with no hang. Before, v3.1.0 hung there 2 of 2 times.

The v3.1.1 log has none of the signs from the v3.1.0 logs: no "simulated turf: ... -> 0 records" lines, no "a capture's wait for write-back ... timed out", no device lost, and no NVIDIA Xid in the kernel log.

It looks like #2174 (simulated-turf lists keep the game's size) was the fix: all three v3.1.0 logs showed the turf lists shrinking to 0 records and growing back from 0 right before each hang.

Fixed in v3.1.1, thanks! Same PC, driver, kernel, gamescope and options as in the report. After rebuilding with v3.1.1 (DLSS built in), I loaded the same save in the Market, walked to the Temple of Time and pulled the Master Sword (child, after Bottom of the Well) with no hang. Before, v3.1.0 hung there 2 of 2 times. The v3.1.1 log has none of the signs from the v3.1.0 logs: no "simulated turf: ... -> 0 records" lines, no "a capture's wait for write-back ... timed out", no device lost, and no NVIDIA Xid in the kernel log. It looks like #2174 (simulated-turf lists keep the game's size) was the fix: all three v3.1.0 logs showed the turf lists shrinking to 0 records and growing back from 0 right before each hang.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
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#2195
No description provided.