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 16:47:43 +0000 [thread overview]
Message-ID: <bug-221778-208809-JFfRuVMup1@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221778-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221778
--- Comment #1 from Miguel Cervantes (m.langas55@gmail.com) ---
A note from me, I did write this with AI I'm not sure about the flow of things
yet in the linux space, I have to admit some of these processes are confusing
for me, I just want the information at the very least out there in an useful
place, I apologize in advance if there are obvious errors/things I'm omitting.
--
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 16:47 UTC|newest]
Thread overview: 3+ 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 ` bugzilla-daemon [this message]
2026-07-22 21:39 ` [Bug 221778] " 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-JFfRuVMup1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox