From owner-freebsd-current Mon Feb 19 11:59:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA18633 for current-outgoing; Mon, 19 Feb 1996 11:59:42 -0800 (PST) Received: from DeepCore.dk (cph30.pip.dknet.dk [194.192.0.62]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA18626 for ; Mon, 19 Feb 1996 11:59:33 -0800 (PST) Received: (from sos@localhost) by DeepCore.dk (8.7.3/8.7.3) id UAA00474; Mon, 19 Feb 1996 20:57:17 +0100 (MET) From: Søren Schmidt Message-Id: <199602191957.UAA00474@DeepCore.dk> Subject: Re: Keyboard lockout on 2.x.x To: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi) Date: Mon, 19 Feb 1996 20:57:17 +0100 (MET) Cc: KentH@HNS.St-Louis.Mo.US, freebsd-current@FreeBSD.ORG, hosokawa@mt.cs.keio.ac.jp In-Reply-To: <199602190934.SAA18196@frig.mt.cs.keio.ac.jp> from "HOSOKAWA Tatsumi" at Feb 19, 96 06:34:07 pm Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG Precedence: bulk In reply to HOSOKAWA Tatsumi who wrote: > > In article <199602190151.TAA00214@gwydion.hns.st-louis.mo.us> > kenth@HNS.St-Louis.Mo.US writes: > > >> Does anyone have a workaround (or better yet a solution) to the keyboard > >> lockup problem on FreeBSD? > >> > >> I've had this problem running 2.0.5, 2.1.0, and -current. So it doesn't > >> appear to be fixed anywhere. Does anyone have a workaround? > > Since I replaced all DELAY(10) with DELAY(100) in syscons.c, it never > happen. But I'm not sure whether it's a good solution. I think it is actually more a hideaway of the symptoms, rather than a fix for the disease... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end ..