From owner-freebsd-current  Wed Nov 13 02:16:08 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id CAA06480
          for current-outgoing; Wed, 13 Nov 1996 02:16:08 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA06467
          for <freebsd-current@FreeBSD.org>; Wed, 13 Nov 1996 02:16:02 -0800 (PST)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.2/8.6.9) with ESMTP id CAA16291; Wed, 13 Nov 1996 02:14:51 -0800 (PST)
To: Gary Roberts <wangel@wgrobez1.remote.louisville.edu>
cc: freebsd-current@FreeBSD.org
In-reply-to: Your message of "Tue, 12 Nov 1996 22:33:24 EST."
             <Pine.NEB.3.95.961112223306.2199A-100000@wgrobez1.remote.louisville.edu> 
Date: Wed, 13 Nov 1996 02:14:51 -0800
Message-ID: <16289.847880091@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> Has anyone been looking into why the Keyboard spastically locks up?  We
> know there is the 'band-aid'(echo "set ipending=2"|gdb -k -w /kernel
> /dev/mem)by telnetting into the 'locked' machine by another machine.  Not
> a problem, and it works, but what if people don't have another machine?

That's been fixed in -current with Soren's latest syscons changes.

						Jordan