From owner-freebsd-bugs  Thu Jul  3 02:39:36 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id CAA01063
          for bugs-outgoing; Thu, 3 Jul 1997 02:39:36 -0700 (PDT)
Received: from meter.eng.uci.edu (root@meter.eng.uci.edu [128.200.85.3])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA01057;
          Thu, 3 Jul 1997 02:39:22 -0700 (PDT)
Received: from newport.ece.uci.edu by meter.eng.uci.edu (8.8.5) id CAA23197; Thu, 3 Jul 1997 02:39:15 -0700 (PDT)
Received: from localhost by newport.ece.uci.edu (8.8.5) id CAA05754; Thu, 3 Jul 1997 02:39:14 -0700 (PDT)
Message-Id: <199707030939.CAA05754@newport.ece.uci.edu>
To: bugs@freebsd.org
cc: bde@freebsd.org
Subject: PS/2 and Keycode bug
Date: Thu, 03 Jul 1997 02:39:13 -0700
From: Steven Wallace <swallace@ece.uci.edu>
Sender: owner-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


>>Also, I've always had this annonying problem using a PS/2 mouse,
>>which is why I end up using a serial one.  When I use device
>>/dev/psm0 and protocol PS/2, sometimes the keyboard state gets messed
>>up so that the X server thinks a modifier key (control, alt) will 
>>remain in the depressed state when the key is not pressed.  I
> 
> This should work better in FreeBSD-current and -2.2.  The psm and
> syscons drivers can now separate psm and keyboard scancodes.
> 

There is still a big problem with the PS/2 and keyboard.

Note that while using the mouse and typing at the same time this problem
occurs.  

I just tried upgrading to XF86 3.3 and the problem continues.
Now that my built-in serial ports aren't being recognized for some 
strange reason, I'm using the PS2 port for my mouse!

Who's fault is this? (in terms of the kernel)

Steven