From owner-freebsd-current  Tue Feb 20 04:58:50 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id EAA11638
          for current-outgoing; Tue, 20 Feb 1996 04:58:50 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA11633
          for <freebsd-current@FreeBSD.ORG>; Tue, 20 Feb 1996 04:58:21 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id XAA23329; Tue, 20 Feb 1996 23:52:48 +1100
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
Cc: KentH@HNS.St-Louis.Mo.US
Sender: owner-current@FreeBSD.ORG
Precedence: bulk

>It doesn't matter whether LEDs would really be toggled.  The command
>is always sent to the keyboard on a VT switch, even if the update will
>yield the same LED state as previously.  Hence the line conflict will
>always happen.

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