It turns out this is not as consistently reproducible as I thought. The issue happened for at least three consecutive reboots (including one complete power-off) before I sent this bug, but when I later went to test if unplugging/reconnecting the USB device after boot made any difference, I discovered it had actually initialized correctly on that boot, and it has worked properly ever since then, including after the latest syspatch.
So... no idea what's going on, but without being reproducible, it's hard to debug this any further, and at least it's working now! On Thu, May 2, 2019 at 4:12 PM <andrew.daugher...@gmail.com> wrote: > > >Synopsis: KVM switch USB mouse not working after 6.5 upgrade - > >"uhidev1: no report descriptor" > >Category: kernel > >Environment: > System : OpenBSD 6.5 > Details : OpenBSD 6.5 (GENERIC.MP) #3: Sat Apr 13 14:48:43 MDT > 2019 > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > Architecture: OpenBSD.amd64 > Machine : amd64 > >Description: > The server is connected to a KVM switch, which has a single USB > connection for both keyboard and mouse. Both devices previously worked (in > 6.4 and earlier), but now only the keyboard works. > > Not sure if relevant, but this machine has *only* USB 3.0 ports, no > USB > 2.0 at all, so the keyboard and mouse are connected to an xhci port. > > In 6.4, the keyboard and mouse were detected like this: > uhidev0 at uhub0 port 2 configuration 1 interface 0 "Avocent APC AP5631" rev > 1.10/1.00 addr 2 > uhidev0: iclass 3/1 > ukbd0 at uhidev0: 8 variable keys, 6 key codes, country code 33 > wskbd0 at ukbd0 mux 1 > wskbd0: connecting to wsdisplay0 > uhidev1 at uhub0 port 2 configuration 1 interface 1 "Avocent APC AP5631" rev > 1.10/1.00 addr 2 > uhidev1: iclass 3/1, 3 report ids > ums0 at uhidev1 reportid 1: 5 buttons, Z dir > wsmouse0 at ums0 mux 0 > uhid0 at uhidev1 reportid 2: input=2, output=0, feature=0 > uhid1 at uhidev1 reportid 3: input=1, output=0, feature=0 > > >How-To-Repeat: > Connect a (composite?) device like this to a system running 6.5: > addr 02: 0624:0706 Avocent, APC AP5631 > low speed, power 100 mA, config 1, rev 1.00 > driver: uhidev0 > driver: uhidev1 > >Fix: > Unknown. A "normal" USB mouse connected directly to the machine does > work. > > > dmesg: [snip] > uhidev0 at uhub0 port 2 configuration 1 interface 0 "Avocent APC AP5631" rev > 1.10/1.00 addr 2 > uhidev0: iclass 3/1 > ukbd0 at uhidev0: 8 variable keys, 6 key codes, country code 33 > wskbd0 at ukbd0 mux 1 > wskbd0: connecting to wsdisplay0 > uhidev1 at uhub0 port 2 configuration 1 interface 1 "Avocent APC AP5631" rev > 1.10/1.00 addr 2 > uhidev1: no report descriptor > usbdevs: > Controller /dev/usb0: > addr 01: 8086:0000 Intel, xHCI root hub > super speed, self powered, config 1, rev 1.00 > driver: uhub0 > addr 02: 0624:0706 Avocent, APC AP5631 > low speed, power 100 mA, config 1, rev 1.00 > driver: uhidev0 > driver: uhidev1 > addr 03: 413c:a001 no manufacturer, Gadget USB HUB > high speed, self powered, config 1, rev 0.00, iSerial 0123456789 > driver: uhub1
