From owner-freebsd-current  Wed Nov 13 07:10:08 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA21698
          for current-outgoing; Wed, 13 Nov 1996 07:10:08 -0800 (PST)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA21691
          for <freebsd-current@freebsd.org>; Wed, 13 Nov 1996 07:10:03 -0800 (PST)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id IAA00027; Wed, 13 Nov 1996 08:09:53 -0700 (MST)
Date: Wed, 13 Nov 1996 08:09:53 -0700 (MST)
Message-Id: <199611131509.IAA00027@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Cc: Gary Roberts <wangel@wgrobez1.remote.louisville.edu>,
        freebsd-current@freebsd.org
In-Reply-To: <16289.847880091@time.cdrom.com>
References: <Pine.NEB.3.95.961112223306.2199A-100000@wgrobez1.remote.louisville.edu>
	<16289.847880091@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.

The fix also broke PS/2 mouse support. :( :(



Nate