gpu_vaspace.c assertions and dmaAllocMapping_GM107 failures under high VRAM usage

Open
  • Is something wrong?
#1,453 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

Start with gpu_vaspace.c and the dmaAllocMapping_GM107 call path implicated by the reported assertion. Reproduce the failure with Substance Painter at high VRAM usage using a 4K textureset while comparing 1K and 2K workloads, and inspect the attached NVIDIA bug report. Done means identifying and fixing the mapping failure, with a regression test or repeatable verification showing the 4K workload no longer produces the assertion.

Written by the indexing model from the issue text.

Description

bug
NVIDIA Open GPU Kernel Modules Version

615.78.08

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

CachyOS

Kernel Release

Linux ZOS 7.2.9-2-cachyos #1 SMP PREEMPT_DYNAMIC Fri, 09 Oct 2026 15:36:46 +0000 x86_64 GNU/Linux

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 3060 Ti (UUID: GPU-9370f5e5-6960-c726-81de-17a10ead47b4)

Describe the bug

Under high GPU memory usage, I repeatedly encounter NVIDIA kernel errors involving GPU virtual-address-space mapping failures. GPU memory usage reached approximately 7871 MiB out of 8192 MiB when observed.

The errors include:

intermapRegisterDmaMapping: Failed to insert new mapping node

nvAssertFailedNoLog: Assertion failed: NV_OK == status @ gpu_vaspace.c

NV_ERR_INVALID_ARGUMENT

_gvaspaceMappingInsert

dmaAllocMapping_GM107: can't update VA space for mapping

The issue occurs during a workload involving 4K textures; the same workload does not trigger the problem with 1K or 2K textures.

I found other reports mentioning similar errors and suspect that high VRAM usage may expose a GPU virtual-address-space or DMA mapping problem.

To Reproduce

I have this on Substance Painter (both 2025 and 2026), I set my resolution to 4k for only one textureset, while using the path tool for stitching.

Bug Incidence

Always

nvidia-bug-report.log.gz

nvidia-bug-report.log.gz

More Info

No response

Dominant language
C
Stars
17.5k
Forks
1.9k
No merged PRs in 30d

Getting set up

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.

More from NVIDIA/open-gpu-kernel-modules

All issues in NVIDIA/open-gpu-kernel-modules

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.