From owner-freebsd-smp Thu Nov 21 14:23:08 1996 Return-Path: owner-smp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA21445 for smp-outgoing; Thu, 21 Nov 1996 14:23: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 OAA21439 for ; Thu, 21 Nov 1996 14:22:59 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA12347; Thu, 21 Nov 1996 15:22:48 -0700 (MST) Date: Thu, 21 Nov 1996 15:22:48 -0700 (MST) Message-Id: <199611212222.PAA12347@rocky.mt.sri.com> From: Nate Williams To: Steve Passe Cc: Nate Williams , freebsd-smp@freefall.freebsd.org Subject: Re: Console lockup In-Reply-To: <199611212218.PAA04779@clem.systemsix.com> References: <199611212207.PAA12263@rocky.mt.sri.com> <199611212218.PAA04779@clem.systemsix.com> Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [ Keyboard lockup with SMP kernels ] > > > 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. > > > > 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. > > the syscons.h/syscons.c files are identical between LOCAL and SMP kernels. > I see something about lkm drivers being needed now, is that a possibility? Nope, but the existing bugs in syscons are causing similar problems to what you are seeing with normal kernels, so seeing it in the SMP kernel may be due to some timing issues. As I said above, try reverting to V1.186 of syscons.c and see if the problem goes away. Nate