From owner-freebsd-smp  Thu Nov 21 14:07:34 1996
Return-Path: owner-smp
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id OAA20545
          for smp-outgoing; Thu, 21 Nov 1996 14:07:34 -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 OAA20538;
          Thu, 21 Nov 1996 14:07:27 -0800 (PST)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA12263; Thu, 21 Nov 1996 15:07:18 -0700 (MST)
Date: Thu, 21 Nov 1996 15:07:18 -0700 (MST)
Message-Id: <199611212207.PAA12263@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
To: Steve Passe <smp@csn.net>
Cc: Peter Wemm <peter@freefall.freebsd.org>, freebsd-smp@freefall.freebsd.org
Subject: Re: Console lockup
In-Reply-To: <199611212136.OAA04559@clem.systemsix.com>
References: <199611210416.UAA03553@freefall.freebsd.org>
	<199611212136.OAA04559@clem.systemsix.com>
Sender: owner-smp@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> so I have "make world' done, a non-SMP kernel built and working.

Does it work fine all the time?

> I can build both APIC_IO and non-APIC_IO kernels.
> They start, show no problems, both get to point of wanting keyboard input,
>  (i started them '-s')
> At this point they both lock, looks like keyboard input is hosed.  If I hit
> numlock i get "^@^@", but no change, ie the numlock light stays lit.  So the
> kernel appears to be catching INT1, but the sc driver seems unhappy.
> 
> Any theories???

Syscons has changed quite a bit in the last week or so to accomodate the
PS/2 mouse.  There are known bugs/bogosities in the code (according to
Bruce), but the author's fixes cause it to not work at all on one of my
test boxes, so I haven't applied the fixes to the tree.

We've got to get on this pretty quick, so hopefully we'll have this
resolved soon.

In the meantime, if you can back out to the 1.186 version of syscons
from the CVS tree I suspect all of your problems will go away.


Nate