Public bug reported:
Suspend is regressed on the NVIDIA 595 branch on this system. The crash
reproduces with both nvidia-driver-595 and nvidia-driver-595-open, in
both deep and s2idle, and both before login at the GDM greeter and after
login in GNOME Wayland. The crash happens after PM: suspend entry, kdump
captures the vmcore, and the machine then performs a normal boot. From
the user side this looks like a shutdown or reboot instead of a failed
suspend/resume.
Rolling back to nvidia-driver-580-open 580.126.09-0ubuntu9 restores
working suspend and resume on the same kernel, hardware, and Wayland
session.
Environment:
- Completely up-to-date Ubuntu 26.04 beta as of 2026-04-06
- Kernel 7.0.0-10-generic
- GNOME on Wayland
- NVIDIA GeForce RTX 3080 Ti
- Failing drivers: nvidia-driver-595 595.58.03-0ubuntu1 and
nvidia-driver-595-open 595.58.03-0ubuntu1
- Working control: nvidia-driver-580-open 580.126.09-0ubuntu9
- Available sleep modes: s2idle [deep]
Reproduction:
1. Boot the system with the NVIDIA 595 branch active.
2. Leave the machine at the GDM greeter or log into GNOME on Wayland.
3. Trigger suspend.
4. Observe the machine power down displays and devices.
5. Instead of resuming in the same boot, the machine shows the Ubuntu shutdown
spinner, POSTs, and boots again.
Expected result:
The machine should enter suspend and later resume in the same boot.
Actual result:
The kernel crashes during suspend inside nvidia_modeset. A representative
vmcore excerpt shows:
PM: suspend entry (s2idle)
jump_label: Fatal kernel bug, unexpected op at
nvkms_kthread_q_callback+0x8e/0x1a0 [nvidia_modeset]
kernel BUG at arch/x86/kernel/jump_label.c:73!
freeze_processes
enter_state
pm_suspend
What was ruled out:
- Closed versus open 595 packaging: both fail.
- deep versus s2idle: both fail.
- Logged-in session state: suspend also fails from the GDM greeter.
- GSP firmware disable: reproduces even with NVreg_EnableGpuFirmware=0
confirmed active on 595-open.
Working control case:
After rolling back to nvidia-driver-580-open 580.126.09-0ubuntu9 and rebooting,
suspend works from both the GDM greeter and the logged-in GNOME Wayland
desktop, with successful deep suspend and resume and no short kdump boot
afterward.
Why this looks like a reboot:
The original suspend attempt crashes, then kdump starts a short crash-kernel
boot to save the vmcore, and then the machine boots normally. On screen that
sequence resembles shutdown and reboot instead of failed resume.
Attachments:
- LAUNCHPAD-ATTACHMENT-BUNDLE.txt
Contents of the single attachment bundle:
- failing 595 suspend journal excerpt
- vmcore dmesg excerpt showing the nvidia_modeset crash
- comparison covering closed 595, open 595, and working 580-open
- working 580-open suspend journal excerpt
- driver and environment snapshot for the working control case
** Affects: nvidia-graphics-drivers-595 (Ubuntu)
Importance: Undecided
Status: New
** Tags: nvidia resolute suspend-resume
** Attachment added: "Various log evidence"
https://bugs.launchpad.net/bugs/2147391/+attachment/5959142/+files/LAUNCHPAD-ATTACHMENT-BUNDLE.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2147391
Title:
Suspend crashes in nvidia_modeset on RTX 3080 Ti with NVIDIA 595 on
Ubuntu 26.04 beta kernel 7.0.0-10-generic; 580-open works on the same
system
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-595/+bug/2147391/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
