[OpenIndiana-discuss] Keyboard issues with OpenIndiana oi_151a9 (and OmniOS)

[Bob Friesenhahn]

Since starting with OpenIndiana, I have encountered a problem that 
sometimes the keyboard is claimed (in /var/adm/messages) to be removed 
and then immediately restored with exactly the same messages as if the 
keyboard was physically unplugged and then plugged back in.  This 
happens up to three times per day.  I encountered this with a Sun Type 
7 keyboard (two units tested) and a Logitech keyboard.

When a KVM is involved, then all connected hosts see the same event as 
if it originates from the keyboard (or is specific to the keyboard KVM 
input). When using the KVM, Solaris 10 and Windows 7 hosts recover 
properly but with OpenIndiana the keyboard input is dead, even though 
similar messages are produced as for Solaris 10, or for physical 
replug.

The messages are similar to this:

Sep 27 04:01:10 weerd genunix: [ID 408114 kern.info] /pci at 0,0/pci15d9,62c at 1d/hub at 1/hub at 1/keyboard at 2 (hid9) removed
Sep 27 04:01:11 weerd usba: [ID 912658 kern.info] USB 2.0 device (usb430,a2) operating at low speed (USB 1.x) on USB 2.0 external hub: keyboard at 2, hid9 at bus address 7
Sep 27 04:01:11 weerd usba: [ID 349649 kern.info]       Sun USB Keyboard
Sep 27 04:01:11 weerd genunix: [ID 936769 kern.info] hid9 is /pci at 0,0/pci15d9,62c at 1d/hub at 1/hub at 1/keyboard at 2
Sep 27 04:01:11 weerd genunix: [ID 408114 kern.info] /pci at 0,0/pci15d9,62c at 1d/hub at 1/hub at 1/keyboard at 2 (hid9) online

If I unplug and replug the keyboard into the KVM, or into the host, 
the keyboard recovers.

If I plug the mouse into the USB hub in the Type 7 keyboard, then the 
mouse is removed as well when the keyboard goes away, except that the 
mouse always recovers.

The hardware involved (for OpenIndiana) is SuperMicro hardware and is 
a Sun Ultra-40 M-2 for Solaris 10.

I am told that recent OmniOS exhibits the same problems when using 
SuperMicro hardware and that a cold boot of the system is necessary to 
unhang the keyboard since otherwise the USB bridge on the motherboard 
does not re-initialize properly.

Do others experience this problem (hung keyboard)?  Is there a 
work-around to avoid the hang?

Bob
-- 
Bob Friesenhahn
bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/