Subject: kern/19333: Some USB->PS/2 adapters unusably slow?
To: None <gnats-bugs@gnats.netbsd.org>
From: seebs <seebs@vash.cel.plethora.net>
List: netbsd-bugs
Date: 12/09/2002 09:05:53
>Number:         19333
>Category:       kern
>Synopsis:       On some adapters, keypresses take about 1/4 second
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Dec 09 09:07:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     seebs
>Release:        NetBSD 1.6K
>Organization:
	
>Environment:
System: NetBSD vash.cel.plethora.net 1.6K NetBSD 1.6K (VASH) #1: Mon Dec 9 08:50:42 CST 2002 seebs@vash.cel.plethora.net:/usr/src/sys/arch/i386/compile/VASH i386
Architecture: i386
Machine: i386
>Description:
	I have a couple of USB keyboard adapters, which look like

ukbd0 at uhidev0 reportid 1
ukbd: imod=0 usage=0x700e0 flags=0x2 pos=0 size=1 cnt=1
wskbd1 at ukbd0 mux 1

ukbd1 at uhidev1
ukbd: imod=0 usage=0x700e0 flags=0x2 pos=0 size=1 cnt=1
wskbd2 at ukbd1 mux 1

	The first one is built into a multifunction hub; the second is a
	standalone adapter.

	The first one consistently takes about 1/4 second to process a key
	press; the second has normal responsiveness.

	Experimenting, I have found that the press and release interrupts
	seem to be coming in a slow but regular stream from the first
	device, but working fine on the second.

	More interestingly, I have two hubs which exhibit exactly the same
	behavior:
	1.  Keyboard interrupts are unusably slow.
	2.  Mouse interrupts are fine.
	3.  The USB ports on the hub are totally silent; plugging devices
	into them has no effect.

	One is a D-Link hub, the other is a "QVS" hub.  Both have serial
	ports (uftdi), keyboard, mouse, and other USB ports.  One also has
	an ethernet and parallel port controller.

>How-To-Repeat:
	Plug one of these hubs in.

>Fix:
	None figured out.  I know that both of these devices were known
	to work a couple of months ago, and I think this is probably a hub
	driver problem, not a keyboard driver problem.  I'm still poking
	around at it.
>Release-Note:
>Audit-Trail:
>Unformatted: