GSP RPC Timeout (Xid 119)
The GPU System Processor (GSP) stops responding to RPCs, logged as Xid 119. The GPU becomes unresponsive and usually needs a reset.
The GPU System Processor (GSP) stops responding to RPCs, logged as Xid 119. The GPU becomes unresponsive and usually needs a reset.
What this failure is
GSP RPC Timeout (Xid 119) is a Hardware failure seen during ML training runs. The GPU System Processor (GSP) stops responding to RPCs, logged as Xid 119. The GPU becomes unresponsive and usually needs a reset. Common tags: Xid 119, Gsp, Rpc Timeout, Hardware.
Is this what broke your run? Paste your log.
You're reading about GSP RPC Timeout (Xid 119). Paste your own crash log or traceback below and get the real root cause for YOUR run, not this generic entry. No account, no card. Logs are masked at ingress and never saved to account history.
Want 14 days on the Scale plan?
Request a work-email trial for up to 50 diagnoses a day, alerts, history, and follow-up questions. No credit card or automatic subscription.
Why it happens (the mechanism)
GSP firmware stopped responding to driver RPCs. Firmware/driver interaction bug or load stall. GPU enters an unresponsive state. Taken together, these mechanisms explain why the failure is reproducible, why it tends to surface on specific workloads or scales, and why generic mitigation attempts often fall short without addressing the underlying cause.
What you'll observe
- A GPU becomes unresponsive mid-run
- Xid 119 appears in the kernel log
- CUDA calls to that GPU hang or error
Common symptoms and what they mean
| Symptom | Why it happens |
|---|---|
| Xid 119 in dmesg (GSP RPC timeout) | GSP firmware stopped responding to driver RPCs |
| nvidia-smi hangs or omits the GPU | Firmware/driver interaction bug or load stall |
| CUDA operations on the GPU stall | GPU enters an unresponsive state |
Which systems are affected
- GPUs running GSP firmware (Turing+ with GSP enabled)
- Long-running training
- Driver/GSP firmware combinations with known timeouts
How to confirm this is the problem
Use this checklist to test the hypothesis against a small reproduction. No single line proves the root cause, so preserve the preceding events and compare one variable at a time.
- ✓Reproduce the failure from a clean checkpoint/seed: the symptom must appear without warm-up state from a previous run.
- ✓Verified signal present: Xid 119 in dmesg (GSP RPC timeout)
- ✓Verified signal present: nvidia-smi hangs or omits the GPU
- ✓Verified signal present: CUDA operations on the GPU stall
- ✓A targeted fix from the "How to fix it" section eliminates or substantially reduces the symptom within one validation pass.
The fix and the prevention pattern
The root cause is on this page and stays free. A free account adds the exact remediation steps, keeps your diagnoses instead of discarding them, and unlocks the fix on every entry in the encyclopedia.
Sign up free. Unlock the full analysisNo credit card · 3 free diagnoses · Instant access
Xid 119 in context
Xid 119 is one of a small set of codes the NVIDIA driver uses to report GPU faults, and the number is most of the diagnosis: it tells you whether you are looking at your own code, the driver, or a board that needs replacing.
Compare every Xid code side by sideDiagnose this failure in VS Code
Select the traceback or open the failed terminal, then run Denpex locally to see the initiating rank, collateral failures, exact fix, and verification command without uploading the log.
Install the free VS Code extensionRelated failures to investigate next
Root cause
- GSP firmware stopped responding to driver RPCs
- Firmware/driver interaction bug or load stall
- GPU enters an unresponsive state
The fix and how to prevent it
Unlock the full remediation runbook
14 days on the Scale plan, up to 50 diagnoses a day. Step-by-step remediation, the RMA evidence payload, and multi-node correlation on your own logs. No card, and it does not roll into a subscription.
Don't just read the fix, diagnose your run
The encyclopedia tells you what went wrong. Denpex tells you what went wrong in YOUR training run. With your logs, your config, and your stack.