From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 221318] mice behind ASMedia ASM1042A via Thunderbolt 2 never produce input, most likely due to interrupt pipe idle window during enumeration
Date: Thu, 09 Apr 2026 22:29:23 +0000 [thread overview]
Message-ID: <bug-221318-208809-vl9WNwIifK@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221318-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221318
--- Comment #21 from manauer.uel@gmail.com ---
I just tested at a second location. Same MacBook Pro 13" Early 2015 and same
ASMedia ASM1042A, but a different monitor (LG 34UC88-B instead of LG 34CB98-B)
and a different mouse (Logitech G403 Prodigy, 046d:c083, two interfaces both at
1ms). Same issue, same workaround fixes it.
Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M
|__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M
ID 043e:9a10 LG Electronics USA, Inc. 34UC88-B
|__ Port 003: Dev 003, If 0, Class=Hub, Driver=hub/4p, 480M
ID 2109:2813 VIA Labs, Inc. VL813 Hub
|__ Port 001: Dev 005, If 0, Class=Human Interface Device,
Driver=usbhid, 12M
ID 046d:c083 Logitech, Inc. G403 Prodigy Gaming Mouse
|__ Port 001: Dev 005, If 1, Class=Human Interface Device,
Driver=usbhid, 12M
ID 046d:c083 Logitech, Inc. G403 Prodigy Gaming Mouse
Interface 0: bInterfaceProtocol Mouse, EP 0x81 IN, bInterval 1
Interface 1: bInterfaceProtocol 0, EP 0x82 IN, bInterval 1
I also plugged in a no-name mouse (China Resource Semico, 1a2c:0043, one
interface at 10ms) and it works fine without any workaround. Same controller,
same hub chain. The 10ms vs 1ms pattern holds here too.
Interface 0: bInterfaceProtocol Mouse, EP 0x81 IN, bInterval 10
I also noticed that all mice work in the OpenCore bootloader, same as on macOS
and Windows. OpenCore uses the EFI USB stack, which presumably keeps the
interrupt pipe active without idle logic. This fits the theory that the problem
is not necessarily in the ASM1042A hardware alone or in usbhid alone, but in
the combination of those two.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2026-04-09 22:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 20:22 [Bug 221318] New: mice behind ASMedia ASM1042A via Thunderbolt 2 never produce input, most likely due to interrupt pipe idle window during enumeration bugzilla-daemon
2026-04-04 9:54 ` [Bug 221318] " bugzilla-daemon
2026-04-04 17:32 ` bugzilla-daemon
2026-04-04 17:33 ` bugzilla-daemon
2026-04-04 17:34 ` bugzilla-daemon
2026-04-04 17:35 ` bugzilla-daemon
2026-04-04 17:39 ` bugzilla-daemon
2026-04-04 21:02 ` bugzilla-daemon
2026-04-05 22:09 ` bugzilla-daemon
2026-04-05 22:37 ` bugzilla-daemon
2026-04-05 22:44 ` bugzilla-daemon
2026-04-06 8:30 ` bugzilla-daemon
2026-04-06 11:35 ` bugzilla-daemon
2026-04-06 11:36 ` bugzilla-daemon
2026-04-06 11:54 ` bugzilla-daemon
2026-04-06 15:35 ` bugzilla-daemon
2026-04-06 19:56 ` bugzilla-daemon
2026-04-06 20:06 ` bugzilla-daemon
2026-04-06 20:11 ` bugzilla-daemon
2026-04-07 7:13 ` bugzilla-daemon
2026-04-07 13:18 ` bugzilla-daemon
2026-04-09 22:29 ` bugzilla-daemon [this message]
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-221318-208809-vl9WNwIifK@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