NVIDIA / NVIDIA/open-gpu-kernel-modules

RTX 5060 Ti: system hangs on suspend (deep/S3), never resumes — 595.71.05 open driver, kernel 7.0.0-27/28

Open
#1,250 3 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.71.05 (nvidia-driver-595-open, Ubuntu package 595.71.05-0ubuntu0.26.04.1)

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

Ubuntu 26.04 LTS

Kernel Release

Linux bruno 7.0.0-28-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Sun Jun 21 01:01:36 UTC 2026 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 5060 Ti

Describe the bug

System completely hangs when entering suspend (deep/S3) and never resumes. Kernel log ends exactly at "PM: suspend entry (deep)" / "Filesystems sync" with no further entries — no "PM: suspend exit", no resume messages at all. Journald itself goes silent, indicating the hang happens very early in the suspend sequence, before/during device suspend callbacks. Only a hard power-off recovers the system.

Reproducible on both linux-image-7.0.0-27-generic and linux-image-7.0.0-28-generic with the identical nvidia-driver-595-open package (595.71.05) — kernel version does not affect the outcome.

Switching /sys/power/mem_sleep to s2idle allows the system to suspend/resume successfully (~16s cycle, clean "PM: suspend exit"), but s2idle does not provide real power savings on this desktop board: /sys/kernel/debug/pmc_core/substate_residencies shows S0i2.0 and S0i2.1 residency of 0 after a full sleep cycle, and fans/ARGB/PSU remain fully active throughout — consistent with this desktop chipset (Intel B760) not supporting genuine Low Power S0 Idle, so s2idle is only a workaround, not a real fix.

This appears related to #1157 (RTX 4070 Ti, same driver 595.71.05, same kernel 7.0.x line, identical hang signature).

To Reproduce
  1. Install nvidia-driver-595-open (595.71.05) on Ubuntu 26.04 with kernel 7.0.0-27 or 7.0.0-28
  2. Ensure mem_sleep_default=deep (desktop default) and NVreg_PreserveVideoMemoryAllocations=1
  3. nvidia-suspend/resume/hibernate systemd services enabled (default)
  4. Trigger suspend via systemctl suspend or KDE Plasma's sleep action
  5. Observe: kernel log ends at "PM: suspend entry (deep)", system becomes fully unresponsive (no display wake, no keyboard/mouse response, fans stay at full/normal, no ACPI wake), requires hard power cycle
Bug Incidence

Always

nvidia-bug-report.log.gz

nvidia-bug-report-sanitized.log

More Info

No response

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 with the sanitized nvidia-bug-report log and the nvidia-suspend, nvidia-resume, and nvidia-hibernate services while reproducing with mem_sleep_default=deep. Compare the suspend path and logs for kernels 7.0.0-27 and 7.0.0-28, using s2idle only as the working comparison. Done means RTX 5060 Ti systems suspend and resume reliably in deep/S3 without requiring a hard power-off.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.