From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 221778] [REGRESSION 6.12→6.18] ASUS N-KEY keyboard (0b05:19b6) USB resets ~1/sec under dGPU rendering load on Raphael xHCI
Date: Wed, 22 Jul 2026 21:39:50 +0000 [thread overview]
Message-ID: <bug-221778-208809-uwzbmkwQd4@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221778-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221778
Michał Pecio (michal.pecio@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |michal.pecio@gmail.com
--- Comment #2 from Michał Pecio (michal.pecio@gmail.com) ---
6.12 to 6.18 is a fairly large spread, and it isn't even clear if the bug is a
regression or perhaps some CachyOS vs Arch difference. And the GPU uses an out
of tree driver, hmm.
IDK about CachyOS, but Arch package archive has 'linux' (non -lts) packages for
all major versions from 6.12 to 6.18. Could you start with testing these to
find which release broke things? And try to use the same NVIDIA driver each
time, or (preferably) see if the problem occurs with Nouveau.
I would wager that resets are deliberate (HID driver seems to do that in
response to USB errors), but that still doesn't explain why USB errors occur
due to GPU activity and why some kernels work but others don't.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2026-07-22 21:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 16:31 [Bug 221778] New: [REGRESSION 6.12→6.18] ASUS N-KEY keyboard (0b05:19b6) USB resets ~1/sec under dGPU rendering load on Raphael xHCI bugzilla-daemon
2026-07-22 16:47 ` [Bug 221778] " bugzilla-daemon
2026-07-22 21:39 ` bugzilla-daemon [this message]
2026-07-23 3:18 ` bugzilla-daemon
2026-07-23 3:23 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-221778-208809-uwzbmkwQd4@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.