From owner-freebsd-bugs  Tue Dec 17 15:15:35 1996
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id PAA26986
          for bugs-outgoing; Tue, 17 Dec 1996 15:15:35 -0800 (PST)
Received: from meter.eng.uci.edu (root@meter.eng.uci.edu [128.200.85.3])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA26981
          for <bugs@freebsd.org>; Tue, 17 Dec 1996 15:15:32 -0800 (PST)
Received: from newport.ece.uci.edu by meter.eng.uci.edu (8.8.3) id PAA25730; Tue, 17 Dec 1996 15:11:54 -0800 (PST)
Received: from localhost by newport.ece.uci.edu (8.8.3) id PAA08307; Tue, 17 Dec 1996 15:14:17 -0800 (PST)
Message-Id: <199612172314.PAA08307@newport.ece.uci.edu>
To: Bruce Evans <bde@zeta.org.au>
cc: bugs@freebsd.org, dawes@xfree86.org
Subject: Re: unexpected signal 2? 
In-reply-to: Your message of "Tue, 17 Dec 1996 21:36:27 +1100."
             <199612171036.VAA18150@godzilla.zeta.org.au> 
Date: Tue, 17 Dec 1996 15:14:12 -0800
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.
> 

Hmmm, I'd say "better" is correct.  It doesn't seem to happen as frequently,
but it still happens in -2.2.  Perhaps there is a scancode that
is getting confused?

Steven