From owner-freebsd-hackers  Wed Oct 16 22:49:47 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id WAA07452
          for hackers-outgoing; Wed, 16 Oct 1996 22:49:47 -0700 (PDT)
Received: from mailhub.aros.net (mailhub.aros.net [205.164.111.17])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA07446
          for <freebsd-hackers@freebsd.org>; Wed, 16 Oct 1996 22:49:45 -0700 (PDT)
Received: from fluffy.aros.net (fluffy.aros.net [205.164.111.2]) by mailhub.aros.net (8.7.6/Unknown) with ESMTP id XAA06674; Wed, 16 Oct 1996 23:49:44 -0600 (MDT)
Received: from fluffy.aros.net (localhost [127.0.0.1]) by fluffy.aros.net (8.7.6/8.6.12) with ESMTP id XAA00642; Wed, 16 Oct 1996 23:49:42 -0600 (MDT)
Message-Id: <199610170549.XAA00642@fluffy.aros.net>
To: Josh MacDonald <jmacd@CS.Berkeley.EDU>
Subject: Re: 2.2-961006-SNAP keyboard lockup
cc: freebsd-hackers@freebsd.org
In-reply-to: Your message of "Wed, 16 Oct 1996 12:07:09 PDT."
             <199610161907.MAA08995@paris.CS.Berkeley.EDU> 
Date: Wed, 16 Oct 1996 23:49:41 -0600
From: Dave Andersen <angio@aros.net>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Under -current, supped just after 100696-SNAP, I experience
these quite frequently when using syscons.  The problem
is actually fairly easy to replicate by rapidly switching
between vty's on the console - if I keep it up enough, the
keyboard will lock solid.  I haven't determined if it only
happens if I hit certain combinations of keys or not, but
that's the best way to duplicate it.

It's never happened under X, most likely because I'm never
  a) switching vty's
or
  b) hitting the certain keys that cause it to lock.

It's not possible to get the system to reset the keyboard short of
a reboot; swapping in a different keyboard with all the associated
risks to the motherboard doesn't cause it to magically cure itself.

(Tyan tomcat II, dual P133 (not using SMP on it right now, I
 actually use the system for work. :), 64MB, mostly PCI, with
 a soundblaster awe-32), chicony KB-2923 keyboard).

> Though keyboard lockups have been much less frequent than they were in
> August, I just experienced another, similar, lockup.  If a fix is in
> place, perhaps this means it hasn't completely fixed the problem.