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

Aperta
  • Qualcosa non va?
#1,439 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
8/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
c, linux
Ambito
operating-systems

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
C
Stelle
17.5k
Fork
1.9k
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di NVIDIA/open-gpu-kernel-modules

Tutte le issue di NVIDIA/open-gpu-kernel-modules

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.