[Bug 289340] keychron v8 max cannot continue receiving input if usb port gets reset

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289340

            Bug ID: 289340
           Summary: keychron v8 max cannot continue receiving input if usb
                    port gets reset
           Product: Base System
           Version: Unspecified
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: jon@xyinn.org

Created attachment 263554
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=263554&action=edit
dmesg

Hey all,

I recently purchased a Keychron V8 Max keyboard and it's been a good and fun
experience to use it. However one thing I've noticed is that if there is any
USB port disconnect / reset of any kind, the 2.4 GHz keyboard receiver is still
properly detected, but the keyboard can no longer send/receive input to FreeBSD
(14.3-RELEASE-p2). Even if I were to physically unplug the receiver and
reconnect it either to the same spot on my USB dongle, or even connecting it to
a physical port (on my Framework Laptop 13 AMD), it will no longer work. The
only way to fix this is to reboot the entire machine, which is extremely
disruptive. I've also tried to do a "force pairing" mode by pressing and
holding Fn + 4 but that didn't work either. I've tested this on macOS as well
and macOS is able to properly recover and continue input. I've attached a dmesg
log showing the initial boot, and you'll start to see some "self powered" /
"(disconnected)" messages. Once this happens, the keyboard is dead. I also have
a few other peripherals connected such as a wireless mouse which continues to
function properly. I would notice a "stop the world" pause of the mouse while
the hub <> FreeBSD attempt to reconnect, and then the mouse properly resumes.
I'm going to purchase a new USB dongle since I feel there may be a hardware
issue, but given that this scenario works/recovers fine on other OSes, FreeBSD
should be able to gracefully recover as well.

Even without the USB dongle though, I can easily replicate this by turning on
the machine with the Keychron 2.4 GHz receiver plugged into a physical USB port
on the Framework Laptop directly, waiting to reach my FreeBSD desktop,
unplugging the receiver, and plugging it back in and the keyboard will be dead
until I reboot it. In this case the "hardware failure" situation is eliminated
and it reveals the issue. The USB dongle rebooting (for w/e reason) is just
simulating the above case in a more extreme scenario.

Please let me know if there is any testing I can do for this or any patches
people want me to apply. I'm opening a separate ticket compared to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268129 since this issue
doesn't seem to be quirk related.

Thank you,
Jonathan

-- 
You are receiving this mail because:
You are the assignee for the bug.