Freezing after suspend with weird text, no mouse, no keyboard

RayenHadd · 2026-05-29 20:33:56

Hardware:

HP ZBook Fury 17 G8
CPU: Intel i7‑11850H
GPU1: Intel UHD Graphics (integrated)
GPU2: NVIDIA RTX A5000 Mobile (Ampere)
Driver: nvidia-open-dkms (open kernel modules)
Kernel: linux‑lts 6.12.66‑1‑lts (also reproduces on mainline)

Problem description:
When suspending the laptop (to s2idle) and then resuming, the system freezes and a lot of logs and text appears, completely within 1‑2 seconds after resume. Caps Lock LED blinks, no TTY, no mouse. Only forced power off works.
The freeze occurs reliably with driver version 590.48.01 (and likely any 590.x).

What does NOT fix the issue (on 590.48.01):

Adding kernel parameters `nvidia.NVreg_EnableGpuFirmware=0` and `nvidia.NVreg_DynamicPowerManagement=0x03`
Switching from open modules to proprietary modules
Using only the integrated GPU (NVIDIA offloading still causes the same panic on resume)

What DOES fix the issue:
Downgrading to nvidia-open-dkms 580.95.05 (with matching nvidia‑utils and lib32‑nvidia‑utils). After downgrade, suspend/resume works perfectly.

The crash is triggered during resume, right after `PM: suspend exit`. The kernel log shows a GSP task panic followed by multiple assertion failures and a page fault in `nvidia_modeset`.

Jan 27 17:30:33 artbook kernel: PM: suspend exit
Jan 27 17:30:33 artbook kernel: NVRM: kgspHealthCheck_TU102: ****************************** GSP-CrashCat Report *******************************
Jan 27 17:30:33 artbook kernel: NVRM: kgspPrintGspBinBuildId_IMPL: GSP bin buildId: cf812cb3f2f1e8c8209dc2e446fdf536ba9ec88f
Jan 27 17:30:33 artbook kernel: NVRM: GPU at PCI:0000:01:00: GPU-d6d45493-ad27-63b7-7786-8e7c414c8bce
Jan 27 17:30:33 artbook kernel: NVRM: Xid (PCI:0000:01:00): 120, GSP task panic: unknown error (0) @ pc:0x19da988, aux:0x0, partition:2#0, task:3
[...]
Jan 27 17:30:33 artbook kernel: NVRM: GPU0 nvCheckOkFailedNoLog: Check failed: Reset required [NV_ERR_RESET_REQUIRED] (0x00000062) returned from kgspWaitForRmInitDone(...)
[...]
Jan 27 17:30:33 artbook kernel: BUG: unable to handle page fault for address: 0000000000002610
Jan 27 17:30:33 artbook kernel: #PF: supervisor read access in kernel mode
Jan 27 17:30:33 artbook kernel: RIP: 0010:DisableVblankSemControl+0x1f/0xa0 [nvidia_modeset]
[...]
Jan 27 17:30:33 artbook kernel: Call Trace:
Jan 27 17:30:33 artbook kernel:  nvEvoDisableVblankSemControl+0x37/0x60 [nvidia_modeset]
Jan 27 17:30:33 artbook kernel:  FreeDeviceReference+0x7d/0x180 [nvidia_modeset]
Jan 27 17:30:33 artbook kernel:  nvRevokeDevice+0x8c/0x90 [nvidia_modeset]
Jan 27 17:30:33 artbook kernel:  nvResumeDevEvo+0x1ef/0x200 [nvidia_modeset]
Jan 27 17:30:33 artbook kernel:  nvKmsResume+0x5c/0xc0 [nvidia_modeset]
Jan 27 17:30:33 artbook kernel:  nvkms_resume+0x1f/0x50 [nvidia_modeset]
Jan 27 17:30:33 artbook kernel:  nv_set_system_power_state+0x108/0x540 [nvidia]

Full logs available:

Kernel log of crash (from original forum post)
Suspend-related error log

## Additional observations

The issue is specific to driver version 590.x (including 590.48.01).
Driver 580.95.05 does not exhibit the problem.
The crash occurs regardless of whether the NVIDIA GPU is actively used before suspend (hybrid mode).
GSP firmware build ID involved: `cf812cb3f2f1e8c8209dc2e446fdf536ba9ec88f`

For now, I am using the downgraded 580.95.05 driver and have locked the packages with `IgnorePkg`. I want to upgrade and solve this error

Note: I used AI to write this because I don't understand a lot about GPUs and I don't have the abilities to understand logs and read them and write about them, I am open to provide more logs or anything if that helps, I upgraded to 595 and same error happened, and I am sending this to see if the error is solved in version 610 and if not, how to solve it, since i want to upgrade to recent kernel versions, I asked in Nvidia Linux forums, but no response .

seth · 2026-05-29 21:10:36

You cannot disable the GSP w/ nvidia-open but could try w/ https://aur.archlinux.org/packages?O=0&K=580xx

Jan 27 13:37:23 artbook kernel: CPU: 6 UID: 0 PID: 1818 Comm: nvidia-sleep.sh Tainted: G     U     OE      6.12.66-1-lts #1 6279dfbe826eab485c29634739f11488210df180

How does this relate to https://bbs.archlinux.org/viewtopic.php?id=311871 ?
Do you have a current journal?

Also what about the 595.71.05 drivers (which will trigger the VRAM preservation script differently from the 590xx ones)

RayenHadd · 2026-05-29 21:24:57

seth wrote:

You cannot disable the GSP w/ nvidia-open but could try w/ https://aur.archlinux.org/packages?O=0&K=580xx
Jan 27 13:37:23 artbook kernel: CPU: 6 UID: 0 PID: 1818 Comm: nvidia-sleep.sh Tainted: G     U     OE      6.12.66-1-lts #1 6279dfbe826eab485c29634739f11488210df180
How does this relate to https://bbs.archlinux.org/viewtopic.php?id=311871 ?
Do you have a current journal?
Also what about the 595.71.05 drivers (which will trigger the VRAM preservation script differently from the 590xx ones)

Based on the last time I spoke about this error, downgrading was the only solution, I downgraded, but it is not healthy to not upgrade the kernel and the drivers for a long time, I tried the 595 driver but still same suspend error for a reason, for now I am still using kernel 6.12 and still with the NVIDIA open drivers v580
I proposed again the problem is because I wanted to ask if there is any new solution
I will try upgrading to v610 (new version of the drivers) but I will wait before doing that since it released today, and then update the post with anything that happens.

seth · 2026-05-30 06:27:04

The 580xx drivers from the AUR are NOT a "downgrade", you're using the 580 legacy tree of the binary only drivers like some people have to use the 470xx or 390xx drivers - just that your GPU is theoretically also supported by the 590xx drivers and nvidia-open - or nouveau.

I proposed again the problem is because I wanted to ask if there is any new solution

Please report this thread to be merged w/ your old one and at least provide some actually updated journal to illustrate the new status quo.

Arch Linux

#1 2026-05-29 20:33:56

Freezing after suspend with weird text, no mouse, no keyboard

#2 2026-05-29 21:10:36

Re: Freezing after suspend with weird text, no mouse, no keyboard

#3 2026-05-29 21:24:57

Re: Freezing after suspend with weird text, no mouse, no keyboard

#4 2026-05-30 06:27:04

Re: Freezing after suspend with weird text, no mouse, no keyboard

Board footer