Date: Fri, 28 Jan 2000 17:24:47 +0900 From: "Daniel C. Sobral" <dcs@newsguy.com> To: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> Cc: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, Bill Fenner <fenner@research.att.com>, current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT Message-ID: <3891524F.1BD2820D@newsguy.com> References: <200001271856.KAA09456@windsor.research.att.com> <45272.949008490@zippy.cdrom.com> <200001272143.QAA20638@khavrinen.lcs.mit.edu> <200001280038.JAA12998@zodiac.mech.utsunomiya-u.ac.jp>
index | next in thread | previous in thread | raw e-mail
Kazutaka YOKOTA wrote: > > I have had reports on similar lockup in both 4.0-CURRENT and 3.X. > I personally have not been able to reproduce it, but now my new sand box > machine exhibits this problem occasionally. > > The I/O access to the AT keyboard by the atkbd driver have not changed > much for the last couple of years, despite massive source tree > reorganization. And yes, problem reports started to pop-up since > sometime around the last summer. > > I have not been able to track down the cause of the problem, but > am suspecting possibility of the clock/timer problem. It happens with me from time to time. It is NOT related to kernel, since it happens between boot0 and boot2. It will happen when I'm typing something during boot, so it's probably some sort of race. Symptons include keys having weird mappings, and some keys not mapping to anything at all, after boot. At boot2/loader, no keypress is recognized at all. Very rare. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "2 b or not to b" meaning varies depending on whether one uses the 79 or the 83 standard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the messagehelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3891524F.1BD2820D>