NVIDIA / NVIDIA/open-gpu-kernel-modules

Title: RTX 5060 second suspend fails on S3 with xhci context errors on resume (Z370 platform)

Open
#1,264 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C
Stars
17.4k
Forks
1.9k
PR merge metrics
No merged PRs in 30d

Description

NVIDIA Open GPU Kernel Modules Version

610.43.03

Please confirm this issue does not happen with the proprietary driver (of the same version). This issue tracker is only for bugs specific to the open kernel driver.
  • I confirm that this does not happen with the proprietary driver package.
Operating System and Version

CachyOS

Kernel Release

Linux cachyos-x8664 7.1.5-1-cachyos #1 SMP PREEMPT_DYNAMIC Mon, 27 Jul 2026 14:05:40 +0000 x86_64 GNU/Linux

Please confirm you are running a stable release kernel (e.g. not a -rc). We do not accept bug reports for unreleased kernels.
  • I am running on a stable kernel release.
Hardware: GPU

GPU 0: NVIDIA GeForce RTX 5060 (UUID: GPU-c67c8ffd-72be-ea79-26e9-c9de37ab0d0f)

Describe the bug

System info:

GPU: NVIDIA RTX 5060
Driver: 610.43.03 (open)
Kernel: 7.1.x-cachyos
Motherboard: ASUS Z370-P
Desktop: KDE Plasma Wayland
OS: CachyOS (Arch-based)

Symptoms:

First S3 suspend/resume works
On resume: xhci root hubs lose power, USB devices reset
Second suspend never resumes, requires hard reboot
"Applying output configuration failed" in KWin on every suspend
"usb root hub lost power or was reset" on every resume

To Reproduce

Steps to reproduce:

Boot system
Suspend once — resumes successfully but with xhci errors
Suspend again — never resumes

Bug Incidence

Always

nvidia-bug-report.log.gz

nvidia-bug-report.log.gz
nvidia-bug-report.txt

More Info

Perhaps some of this is my own doing, I tried adding services like VT Switch, but that was in my own attempt to fix the suspend failures that were already happening.

Contributor guide

Open the contributing guide

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.

Research direction

Start by reproducing the two-suspend sequence on the listed RTX 5060, Z370, CachyOS, and kernel setup, then inspect the attached nvidia-bug-report.log.gz and nvidia-bug-report.txt for the xHCI and resume failures. Done means the system resumes successfully after repeated S3 cycles without xHCI context errors, USB root-hub resets, or the reported KWin output-configuration failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.