NVIDIA / NVIDIA/open-gpu-kernel-modules

Strinova crashes: Attempt to wait on invalid sync FD

Open
#1,297 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C
Stars
17.4k
Forks
1.9k
PR merge metrics
No merged PRs in 30d

Description

NVIDIA Open GPU Kernel Modules Version

595.71.05, 610.57.04

Please confirm this issue does not happen with the proprietary driver (of the same version). This issue tracker is only for bugs specific to the open kernel driver.
  • I confirm that this does not happen with the proprietary driver package.
Operating System and Version

NixOS 26.05 (Yarara)

Kernel Release

Linux 7.1.7 #1-NixOS SMP PREEMPT_DYNAMIC

Please confirm you are running a stable release kernel (e.g. not a -rc). We do not accept bug reports for unreleased kernels.
  • I am running on a stable kernel release.
Hardware: GPU

NVIDIA GeForce RTX 2060

Describe the bug

Approximately 1 out of 5 attempts, launching Strinova via Steam, then entering the Kanami dorm "Area A" results in a hang of the rendering thread, followed by either a Render Thread timeout after two minutes, a freeze of the game (with audio still running), or a crash with "invalid Pak signature" Unreal Engine error. In the journal, at some attempts appeared:

16:20:12 kernel: [drm:nv_drm_semsurf_fence_wait_ioctl [nvidia_drm]] *ERROR* [GPU ID 0x00000100] Attempt to wait on invalid sync FD: 1511
Full NVIDIA log from this crash Retrieved using `journalctl --since "-10min" | \grep -iE "nvidia|drm|fence|hung|semsurf"`:
[Fri Aug 14 15:32:32 2026] nvidia: loading out-of-tree module taints kernel.
[Fri Aug 14 15:32:32 2026] nvidia-nvlink: Nvlink Core is being initialized, major device number 242
[Fri Aug 14 15:32:32 2026] nvidia 0000:01:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=none
[Fri Aug 14 15:32:33 2026] NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64  595.71.05  Release Build  (nixbld@)  
[Fri Aug 14 15:32:36 2026] nvidia-gpu 0000:01:00.3: enabling device (0000 -> 0002)
[Fri Aug 14 15:32:36 2026] nvidia_modeset: unknown parameter 'vblank_sem_control' ignored
[Fri Aug 14 15:32:36 2026] nvidia-modeset: Loading NVIDIA UNIX Open Kernel Mode Setting Driver for x86_64  595.71.05  Release Build  (nixbld@)  
[Fri Aug 14 15:32:36 2026] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input5
[Fri Aug 14 15:32:36 2026] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input6
[Fri Aug 14 15:32:36 2026] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input7
[Fri Aug 14 15:32:36 2026] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input8
[Fri Aug 14 15:32:36 2026] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[Fri Aug 14 15:32:37 2026] nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
[Fri Aug 14 15:32:38 2026] [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 1
[Fri Aug 14 15:32:38 2026] nvidia 0000:01:00.0: vgaarb: deactivate vga console
[Fri Aug 14 15:32:38 2026] fbcon: nvidia-drmdrmfb (fb0) is primary device
[Fri Aug 14 15:32:39 2026] nvidia 0000:01:00.0: [drm] fb0: nvidia-drmdrmfb frame buffer device
[Fri Aug 14 16:20:12 2026] [drm:nv_drm_semsurf_fence_wait_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Attempt to wait on invalid sync FD: 1511

(the crash occurred at the moment of the last line)

The crash sometimes also occurs while rapidly switching the main menu tabs, or during matches, but I wasn't able to reproduce the latter condition. Attempting to mitigate the issue, I have performed the following actions (In no particular order, some of those more than once), to no avail:

  1. Cleared the DXVK cache at steamapps/shadercache
  2. Reinstalled the game
  3. Verified the game files
  4. Tried out different Proton versions: dwproton-11.0-1-x86_64, dwproton-10.0-26-x86_64, Proton-CachyOs Latest, Proton Hotfix, Proton Experimental, Proton 9.0-4, GE-Proton11-3, and DW-Proton Latest.
  5. Switched to the proprietary modules
  6. Upgraded the drivers to 610.57.04
  7. Updated the nixpkgs and nixpkgs-unstable.

The bug occurred on all Proton versions, with both proprietary and open source modules, on both tested driver versions (595.71.05 and 610.57.04), although notably the bug didn't crash the game instantly on open modules 610.57.04, instead opening the error dialog with "LowLevelFatalError The game resource file is corrupted (...) Pak chunk signature check failed". It might be a fluke though, because other attempts on the same driver version behaved predictably just like on the older ones.

I found some similar issues, which might be related:
NVIDIA Forum thread
COSMIC GitHub issue
osu! GitHub issue

If any other information would be of any help, please let me know.

To Reproduce
  1. Install Strinova through Steam (haven't tested other launch methods)
  2. Enter the Kanami dorm, Area A.
  3. If no bug occurs, try restarting the launched and trying again, or switch rapidly between the tabs at the top, and the Area A in the dorm
Bug Incidence

Sometimes

nvidia-bug-report.log.gz

nvidia-bug-report.log.gz

More Info

EDIT: occurred multiple times on switching to the agent tab

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the nvidia_drm nv_drm_semsurf_fence_wait_ioctl path named in the journal, then reproduce the failure by entering Kanami dorm Area A or rapidly switching menu tabs. Compare the journal and nvidia-bug-report.log.gz from failing and successful attempts; done means the invalid sync FD error and resulting hang or crash no longer occur.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
computer-graphics, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.