From owner-freebsd-current Sat Aug 14 1: 9:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id DA57915143 for ; Sat, 14 Aug 1999 01:09:34 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id RAA03114; Sat, 14 Aug 1999 17:08:14 +0900 (JST) Message-ID: <37B52262.A5A6EDB7@newsguy.com> Date: Sat, 14 Aug 1999 17:01:38 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Mike Smith Cc: Warner Losh , Ron Klinkien , freebsd-current@FreeBSD.ORG Subject: Re: Problems with 4.0 keyboard input! References: <199908140505.WAA00566@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > In message <199908140443.VAA00388@dingo.cdrom.com> Mike Smith writes: > > : It's not the boot blocks doing anything explicit; they just use the BIOS. > > > > I have noticed that boot[12] doesn't seem to have this problem. > > However, after /boot/loader has been loaded, I see this problem from > > time to time. I don't know what is going on, I'm just reporting what > > I've seen.... > > *mumble* We're seeing a few cases where BIOS code in the boot path > isn't working too well (or at all) when run in vm86 mode. 8( I think it's interrupt-related. A race somewhere. From time to time, if I'm pressing keys during the early stages of boot, the keyboard will freeze. It's rare, and it only happens when I'm pressing keys during the early stages of boot. Alas, I have seen this happen before, with OS/2 Boot Manager, so I take it for granted. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "You intend to eat me, then?" he asked the dragon. "Well, I must admit, more for the amusement than the taste." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message