GSP RPC channel stops responding (status 0x11) during GPU teardown on shutdown/suspend/hibernate — RTX 5060 Max-Q, hybrid Optimus laptop

Open
  • Is something wrong?
#1,439 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
8/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
c, linux
Domain
operating-systems

Research direction

The payload names _issueRpcAndWait, rpcRmApiFree_GSP, GspRmFree and an assertion at gmmu_walk.c:842, but it does not say which change would fix the failure or what a passing result looks like. Reproducing needs a suspend, hibernate or shutdown cycle on RTX 5060 hardware with GSP logs, which a newcomer may not have. Treat this as a diagnosis thread for maintainers rather than a first contribution.

Written by the indexing model from the issue text.

Description

Hardware: ASUS ROG Zephyrus G14 (GA403UM), hybrid GPU — NVIDIA GeForce RTX 5060 Max-Q (GB206M, PCI 10de:2d59) + AMD Radeon 8060S (HawkPoint iGPU, amdgpu)
Driver: nvidia-open-dkms 610.57.04
Kernel: 7.2.5-3-omarchy (Arch-based, Omarchy 4.0.4)

Summary: The GSP RPC channel (_issueRpcAndWait) intermittently stops responding with status=0x00000011 during GPU resource teardown. This has been observed in three different transitions, always with the same signature, always requiring a hard power-off:

  1. Resume from suspend → amdgpu-side deadlock on resume (separate signature, included for context).
  2. Entering suspend → NVIDIA PM suspend/hibernate notifier flatly refuses sleep: NVRM: PM hibernate/suspend notifier failed: 0x11.
  3. Plain shutdown/logout (no sleep involved at all) → GSP RPC channel dies mid-teardown:
NVRM: GPU0 _issueRpcAndWait: rpcSendMessage failed with status 0x00000011 for fn 10 sequence ...
NVRM: GPU0 rpcRmApiFree_GSP: GspRmFree failed: hClient=...; status=0x00000011
NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: pEntries != NULL @ gmmu_walk.c:842
NVRM: GPU0 mmuWalkUnmap: Failed to unmap VA Range ... Status = 0x00000040
  1. Hibernate via HibernateMode=shutdown: image write to disk succeeds, but the subsequent shutdown-teardown phase hits the same GSP wedge as (3), freezing the machine. The hard power-off that follows then corrupts the hibernation image: next boot fails to resume (PM: hibernation: Failed to load image, recovering, resume failed (-5)), silently dropping the session instead of restoring it.

Impact: No supported sleep/hibernate/clean-shutdown path currently completes reliably on this machine; every attempt risks a hard power-off, and hibernate additionally risks data/session loss on a bad resume.

Happy to pull full journalctl excerpts, nvidia-bug-report.sh output, or test driver/kernel params on request. Cross-referenced at omacom/omarchy#9696 for the OS-level symptoms and workaround history.

Dominant language
C
Stars
17.5k
Forks
1.9k
No merged PRs in 30d

Getting set up

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.

More from NVIDIA/open-gpu-kernel-modules

All issues in NVIDIA/open-gpu-kernel-modules

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.