RTX 50-series (Blackwell): s2idle resume hangs on Linux 7.0 kernel; same driver works on 6.17

[a-pushkin]

NVIDIA Open GPU Kernel Modules Version

580.142

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 Beta

Kernel Release

7.0.0-14-generic #14-Ubuntu 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 5070 Laptop GPU

Describe the bug

Tested on two upstream tags; both reproduce.

Primary (currently installed, actively reproducing): 580.142

• Upstream tag: https://github.com/NVIDIA/open-gpu-kernel-modules/releases/tag/580.142
• Distro package: nvidia-dkms-580-open 580.142-0ubuntu3 (Ubuntu 26.04)
• modinfo srcversion: C4BC8E95CA62E8363647ABA

Also reproduced on: 595.58.03

• Upstream tag: https://github.com/NVIDIA/open-gpu-kernel-modules/releases/tag/595.58.03
• Distro package: nvidia-dkms-595-open 595.58.03-0ubuntu2 (Ubuntu 26.04)

Not built from source / SHA — DKMS-built from the Ubuntu-packaged upstream-tag
source tree.

## Field: Stable kernel confirmation

Confirmed. `uname -a` reports:
`Linux 7.0.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Mon Apr 13 11:09:53 UTC 2026 x86_64`
— Ubuntu's ABI-14 build of upstream stable Linux 7.0, not a `-rc`.

---

## Field: Describe the bug

The nvidia-open driver hangs during s2idle lid-close suspend on Linux
kernel 7.0. The identical driver on the identical hardware suspends and
resumes cleanly on kernel 6.17. Blacklisting all nvidia kernel modules on
kernel 7.0 also produces a clean s2idle cycle, so this is a driver-side
regression triggered by kernel changes between 6.17 and 7.0 — not a
platform or kernel-core bug. Both 580.142 and 595.58.03 reproduce.

Kernel	nvidia loaded	Result
6.17.0-22	yes	works
6.17.0-22	no	works
7.0.0-14	yes	hangs
7.0.0-14	no (module_blacklist=nvidia_drm,nvidia_modeset,nvidia_uvm,nvidia)	works

Failure signature

journalctl -b -1 -k of a failed boot ends with:

kernel: nvidia 0000:01:00.0: Enabling HDA controller
    (then the journal ends — the next line is the next boot after hard reset)

PM: suspend entry (s2idle) does not print. The kernel emits that
message only after dpm_suspend_start() — the device suspend cascade —
returns, so the fact that it never prints means one of the .suspend
callbacks in the cascade never returns. The last device the kernel
touched per the log is the nvidia-bound GPU function at 0000:01:00.0.

The Enabling HDA controller line itself is kernel-side, from
quirk_nvidia_hda in drivers/pci/quirks.c, and the same line also
appears on 6.17 where it's followed by a normal cycle. It's not the
problem — it's just the last log emitted before control enters the
nvidia driver's suspend path, where it never returns on 7.0.

Post-hang artifact on the next boot

dmesg on the post-reset boot shows the GSP left in an inconsistent state
from the aborted resume:

NVRM: _kgspProcessRpcEvent: Attempted to process RPC event from GPU0: 0x101a
      (PFM_REQ_HNDLR_STATE_SYNC_CALLBACK) during bootup without API lock
NVRM: nvAssertFailedNoLog: Assertion failed: 0 @ kernel_gsp.c:1446

This is a consequence of the failed resume, not the primary bug, but the
GSP PM RPC path is a plausible place to look.

Corroboration on different hardware

Another user reports the identical symptoms on a Lenovo ThinkPad T1g Gen
8 (Intel Core Ultra 9 + RTX 5070 Max-Q) with the same kernel + driver
combination on Ubuntu 26.04, ruling out platform (AMD Phoenix /
Framework) as a necessary condition:
https://forums.developer.nvidia.com/t/ubuntu-26-04-suspend-resumes-to-black-screen/365785

Tracking

Full diagnostics attached to Ubuntu Launchpad bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149963

To Reproduce

Framework Laptop 16 with an RTX 5070 Max-Q Mobile (GB206M) and AMD
Phoenix iGPU, on Ubuntu 26.04 "resolute" (development release).

1. Install nvidia-open:
   sudo apt install nvidia-driver-595-open
   (or nvidia-driver-580-open — both reproduce)

2. Boot linux-image-7.0.0-14-generic with default modprobe config.
   Confirm all four nvidia kernel modules are loaded:
   lsmod | grep -E '^nvidia(_drm|_modeset|_uvm)?\b'

3. Log in to GNOME on Wayland (AMD iGPU drives the internal display via
   amdgpu; nvidia modules are loaded for compute / offload).

4. Close the laptop lid. Wait ~10 seconds. Open the lid.

Expected: normal s2idle resume — display re-lights, session continues,
dmesg shows PM: resume from suspend-to-idle → PM: suspend exit.

Actual: display never wakes, system is unresponsive, hard reset (long
power button) is the only recovery. On the next boot, journalctl -b -1 -k ends with nvidia 0000:01:00.0: Enabling HDA controller and no
PM: suspend entry (s2idle) line.

Switching to linux-image-6.17.0-22-generic with no other changes makes
the same cycle succeed — the only variable that matters is the kernel.

Bug Incidence

Always

nvidia-bug-report.log.gz

nvidia-bug-report.log.gz

More Info

No response

[notdenied]

Affects me too.

Laptop: MSI Vector 16 HX AI A2XW
System: Ubuntu 26.04 (new LTS)
Kernel: 7.0.0-14-generic
CPU: Intel Core Ultra 9 275HX
GPU: GeForce RTX 5080 Max-Q / Mobile
Driver: 595.58.03 (open)

The laptop freezes completely after suspend.

[mmmmmmmmmmmmmmmmmmmdonuts]

I also get a hard freeze on a desktop GPU 5080 on some (but not all) resumes but am on Kernel 6.19.13

System: Arch Linux
Kernel: linux-6.19.13
GPU: Nvidia RTX 5080
Driver: nvidia-open-595.58.03-5
CPU: AMD 9700x

This happens on resume from both KDE before and Gnome. Seems to happen a bit less often on Gnome but may have just been luck

[gcapellib]

Same issue reproduced — Lenovo Legion + RTX 5060 + Kubuntu 26.04
Confirming this regression on a different platform/GPU combination, ruling out laptop-vendor-specificity further.

Hardware

Laptop: Lenovo Legion (LENOVO 83M0 / LNVNB161216), BIOS RGCN34WW (12/11/2025)
CPU: AMD (Hawk Point / HawkPoint1)
iGPU: AMD Radeon (amdgpu)
dGPU: NVIDIA GeForce RTX 5060 Max-Q / Mobile (GB206M, PCI ID 10de:2d19, rev a1)
Display server: Wayland (KDE Plasma / kwin_wayland)

Software

Distro: Kubuntu 26.04 (Resolute Raccoon)
Kernel: 7.0.0-14-generic (#14-Ubuntu SMP PREEMPT(lazy))
Driver: nvidia-dkms-580-open 580.142-0ubuntu3 (distro package, DKMS-built)
Modules loaded: nvidia, nvidia_modeset, nvidia_drm, nvidia_uvm (all 4 active)
nvidia-smi: GPU detected normally, driver functional in regular use
OpenGL renderer: NVIDIA GeForce RTX 5060 Laptop GPU/PCIe/SSE2 (no llvmpipe fallback)

Reproduction

Boot kernel 7.0.0-14-generic with default modprobe config
Log in to KDE Plasma on Wayland
Run systemctl suspend

Actual behavior
Hard kernel panic on suspend entry. Caps Lock LED unresponsive — full system freeze, only long power-button reset recovers.

Fatal kernel bug, unexpected op at nvkms_kthread_q_callback+0x8e/0x1a0 [nvidia_modeset]
kernel BUG at arch/x86/kernel/jump_label.c:731
Oops: invalid opcode: 0000 [#1] SMP NOPTI
CPU: 14 UID: 0 PID: 4178 Comm: systemd-sleep
Tainted: G W OE 7.0.0-14-generic #14-Ubuntu PREEMPT(lazy)

Call Trace:
arch_jump_label_transform_queue+0x37/0x90
__jump_label_update+0x47/0x100
jump_label_update+0x5c/0x110
static_key_slow_inc_cpuslocked+0x53/0xa0
static_key_slow_inc+0x1f/0xa0
freeze_processes+0xd1/0xe0
enter_state+0xe0/0x610
pm_suspend+0x49/0x90
state_store+0x2e/0x60
...

Notes

Crash occurs during suspend entry (freeze_processes in the trace), not on resume
systemd-sleep is the triggering process
Same nvidia_modeset callback site (nvkms_kthread_q_callback) as the Framework + RTX 5070 Max-Q report — strongly suggests common root cause across Blackwell mobile parts
Unable to test kernel 6.17 downgrade on Kubuntu 26.04 (kernel 6.17 not available in Resolute repos; 26.04 ships 7.0 only)

Workaround currently applied
systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target plus disabling all sleep triggers in KDE power management. Suspend is unusable until a fix lands.
Affected combination summary
ComponentVersionGPU archBlackwell (GB206M)Driver580.142-openKernel7.0.0-14-generic (Ubuntu)iGPUAMD (hybrid)CompositorKDE/kwin_wayland

[dylanmtaylor]

This is affecting a Dell Precision 5540 I have with a turing card, using the 595 driver on the linux 7.0 kernel on Ubuntu 26.04. @a-pushkin can you remove "RTX 50-series (Blackwell):" from the title, this clearly affects a lot of cards outside of the blackwell series.