All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [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
Date: Wed, 22 Jul 2026 16:31:23 +0000	[thread overview]
Message-ID: <bug-221778-208809@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=221778

            Bug ID: 221778
           Summary: [REGRESSION 6.12→6.18] ASUS N-KEY keyboard (0b05:19b6)
                    USB resets ~1/sec under dGPU rendering load on Raphael
                    xHCI
           Product: Drivers
           Version: 2.5
          Hardware: AMD
                OS: Linux
            Status: NEW
          Severity: high
          Priority: P3
         Component: USB
          Assignee: drivers_usb@kernel-bugs.kernel.org
          Reporter: m.langas55@gmail.com
        Regression: No

Hardware: ASUS ROG Strix G16 G614PM (AMD variant: Raphael iGPU + RTX 5060
Laptop dGPU), BIOS G614PM.316 (latest from ASUS).
Internal keyboard: ASUS "N-KEY Device", USB 0b05:19b6, hid-asus driver,
attached to usb 3-1 on the AMD Raphael xHCI controller (1022:15b6/15b7).

Summary: since 6.18, rendering load on the Nvidia dGPU causes the
internal keyboard's USB device to reset ~once per second
("usb 3-1: reset full-speed USB device" in dmesg — 4,557 resets in one
8h boot). The resets corrupt input below userspace: evtest on
/dev/input/event3 shows missed key presses, releases arriving seconds
late, and missing autorepeat. In games this manifests as stuck/dropped
WASD keys.

Trigger isolation:
- iGPU rendering with dGPU powered but idle: CLEAN (tested via
  supergfxctl Integrated mode).
- dGPU rendering by application: resets begin
  immediately (70 resets in the first ~2 min after game launch).

Kernels tested:
- 6.12.75 (Arch linux-lts): CLEAN — 0 resets in a full game session.
- 6.18.38 (cachyos-lts): BROKEN.
- 7.1.4 (cachyos): BROKEN (retested 2026-07-22).

Ruled out: EC reset (no effect), BIOS (already latest), hardware
(machine is clean on 6.12).

Distro: CachyOS (Arch-based, rolling). Nvidia driver 610.43.03 via
nvidia-open-dkms.

Multiple users with G614/G615 models report identical symptoms on the
same 0b05:19b6 device:
-
https://discuss.cachyos.org/t/keyboard-input-issues-on-asus-rog-strix-16-2025-with-cachyos-during-gaming/30823
- https://github.com/ublue-os/bazzite/issues/4590

I will be away from this machine until ~2026-07-24; I can respond to
questions and run tests after that. Other affected users are active in
the CachyOS thread linked above and may be able to test sooner.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2026-07-22 16:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22 16:31 bugzilla-daemon [this message]
2026-07-22 16:47 ` [Bug 221778] [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 21:39 ` bugzilla-daemon
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@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.