From owner-freebsd-current  Tue Aug  6 10:21:16 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id KAA01308
          for current-outgoing; Tue, 6 Aug 1996 10:21:16 -0700 (PDT)
Received: from miller.cs.uwm.edu (miller.cs.uwm.edu [129.89.9.13])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA01303
          for <freebsd-current@freebsd.org>; Tue, 6 Aug 1996 10:21:14 -0700 (PDT)
Received: (from james@localhost) by miller.cs.uwm.edu (8.7.3/8.7.3) id MAA23320; Tue, 6 Aug 1996 12:21:12 -0500
Date: Tue, 6 Aug 1996 12:21:12 -0500
From: Jim Lowe <james@miller.cs.uwm.edu>
Message-Id: <199608061721.MAA23320@miller.cs.uwm.edu>
To: freebsd-current@freebsd.org, wangel@wgrobez1.remote.louisville.edu
Subject: Re:  locking up
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> From: Gary Roberts <wangel@wgrobez1.remote.louisville.edu>
> To: freebsd-current@freebsd.org
> Subject: locking up
> 
> Sometimes, at no predetermined time, without warning, when switching VC's,
> I'll lock up. FreeBSD doesn't lockup just the keyboard, and I can only fix
> it by rebooting.
> 

A while ago Bruce Evans had posted this, if you run it, it
unlocks the keyboard.  I don't know why this happens or why
it hasn't been fixed.  The way I run it is to remote login
from some other machine.

	-Jim

> Date: Tue, 20 Feb 1996 23:52:48 +1100
> From: Bruce Evans <bde@zeta.org.au>
> Message-Id: <199602201252.XAA23329@godzilla.zeta.org.au>
> To: freebsd-current@FreeBSD.org, j@uriah.heep.sax.de
> Subject: Re: Keyboard lockout on 2.x.x
> 
> To fix it if you can log in as root from another host, try
> 
> 	echo "set ipending=2" | gdb -k -w /kernel /dev/mem
> 
> This fakes a keyboard interrupt.
> 
> Bruce
>