From owner-freebsd-current Thu Jan 27 16: 5:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id E4FC714C03; Thu, 27 Jan 2000 16:05:41 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA03163; Thu, 27 Jan 2000 16:14:48 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001280014.QAA03163@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: Mike Smith , Brian Beattie , Bill Fenner , rcarter@pinyon.org, current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-reply-to: Your message of "Thu, 27 Jan 2000 16:59:10 MST." <200001272359.QAA49853@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Jan 2000 16:14:48 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <200001272329.PAA02514@mass.cdrom.com> Mike Smith writes: > : It doesn't do anything to the keyboard, it just calls the BIOS to find > : out whether keys have been pressed. > > I've been seeing the hit twice fast problem for months. It's always been a problem; we don't understand the mechanics of it however. Susceptibility varies widely between systems, and the best hypothesis I've been able to come up with is that there are issues with taking interrupts in vm86 mode; possibly the BIOS is being re-entered in a fashion it doesn't like. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message