Hi, I’m seeing a regression specifically in 580.105.08. Hibernate (ACPI S4) worked on 580.95.05 and stopped working immediately after updating to 580.105.08. Nothing else in my setup changed.
What happens now is:
The system writes the hibernate image, the display shuts off, USB briefly power-cycles, but the system never actually powers down. Fans keep running, power LED stays on forever, and I have to do a manual power button shutdown. After that, the system does resume from the hibernate image just fine, so the snapshot is being created properly - the machine just never transitions into S4.
System details:
-
GPU: RTX 3060 Ti
-
Driver package:
nvidia-dkms -
Working version: 580.95.05
-
Broken version: 580.105.08
-
Kernels tested:
-
6.17.8-zen
-
6.12.58-lts
(same issue across all)
-
-
Distro: Arch Linux
-
Display server: Wayland
-
Motherboard: MSI PRO Z690-A DDR4
-
Hibernate config:
-
HibernateState=disk -
HibernateMode=shutdown
-
-
Swap on disk (not encrypted)
This is the upgrade timeline from pacman:
[2025-11-07] upgraded nvidia-dkms (575.64.03 → 580.95.05)
[2025-11-14] upgraded nvidia-dkms (580.95.05 → 580.105.08)
Hibernate still worked on 580.95.05 and broke only after the 580.105.08 update. Here’s the journal output from a failing hibernate attempt on 580.105.08:
systemd-sleep[1723]: Performing sleep operation 'hibernate'...
PM: hibernation: Creating image:
PM: hibernation: Need to copy 1222466 pages
PM: hibernation: Normal pages needed: 1222466 + 1024, available pages: 2922493
PM: hibernation: hibernation exit
systemd-sleep[1723]: System returned from sleep operation 'hibernate'.
systemd-logind[504]: Operation 'hibernate' finished.
NVIDIA’s hibernate/resume services report success but the system never shuts off:
Starting NVIDIA system hibernate actions...
nvidia-hibernate.service: Deactivated successfully.
Starting NVIDIA system resume actions...
nvidia-resume.service: Deactivated successfully.
Physical behavior:
– screen off
– keyboard LEDs off → immediately on
– fans keep spinning
– system stays powered indefinitely
– manual shutdown required
– next boot resumes correctly
Rolling back from 580.105.08 → 580.95.05 restores correct S4 behavior immediately.
I can attach a full nvidia-bug-report.sh log, PM trace, or ACPI trace if needed. Just let me know what’s useful.