NVIDIA / NVIDIA/open-gpu-kernel-modules

System fails to resume from suspend with NVIDIA GSP heartbeat timeout

Open
#1,125 4 comments 1 reaction 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.58.03-2 (from package nvidia-open-dkms)

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

Arch Linux

Kernel Release

6.19.13-arch1-1 SMP PREEMPT_DYNAMIC Tue, 21 Apr 2026 23:38:22 +0000 x86_64 GNU/Linux (stable release)

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 3080 (UUID: GPU-8c983cec-3f59-dd0b-50c0-b0d42da360bb)

Describe the bug

After suspending the system, resume fails with NVIDIA GSP (Graphics System Processor) heartbeat timeout errors, followed by DRM atomic modeset failures. The system becomes unresponsive and requires a hard reset to recover.

To Reproduce

To Reproduce:

  1. Use system normally
  2. Suspend the system
  3. Wait for any duration
  4. Attempt to resume the system
  5. Observe failure to resume properly, requiring hard reset
Bug Incidence

Sometimes

nvidia-bug-report.log.gz

nvidia-bug-report.log.gz

More Info

The problem appears to be that after the GSP heartbeat times out, the driver fails to properly reset the GPU and restore display configuration, leading to DRM atomic modeset failures.

Key error messages from journalctl:

  • apr 27 18:37:30 kernel: NVRM: _kgspIsHeartbeatTimedOut: Heartbeat timed out, currentTimeMs 3486357473 heartbeat 0 heartbeatWithOffsetMs 0 diff 3486357473 timeout 5200
  • apr 27 18:37:30 kernel: NVRM: _kgspRpcRecvPoll: GSP RM heartbeat timed out
  • apr 27 18:37:31 kernel: [drm:nv_drm_atomic_apply_modeset_config [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000a00] Failed to initialize semaphore for plane fence
  • apr 27 18:37:31 kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000a00] Failed to apply atomic modeset. Error code: -11

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 reviewing nvidia-bug-report.log.gz and the journalctl errors for the GSP heartbeat timeout and subsequent DRM atomic modeset failures. Trace the suspend/resume path for the NVIDIA open kernel driver and reproduce the failure on the listed Arch Linux kernel and RTX 3080 hardware. Done means resume completes reliably without heartbeat timeout, semaphore, or atomic modeset errors.

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
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.