From owner-freebsd-current Thu Nov 7 22:12:28 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C6AF37B401 for ; Thu, 7 Nov 2002 22:12:27 -0800 (PST) Received: from HAL9000.homeunix.com (12-232-220-15.client.attbi.com [12.232.220.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id A739843E88 for ; Thu, 7 Nov 2002 22:12:26 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.6/8.12.5) with ESMTP id gA86BBjV000409; Thu, 7 Nov 2002 22:11:11 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.6/8.12.5/Submit) id gA86BAg1000408; Thu, 7 Nov 2002 22:11:10 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Date: Thu, 7 Nov 2002 22:11:10 -0800 From: David Schultz To: "Michael G. Petry" Cc: Julian Elischer , Sidcarter , current@FreeBSD.ORG Subject: Re: Kernel not booting....Immediate crash Message-ID: <20021108061110.GB309@HAL9000.homeunix.com> Mail-Followup-To: "Michael G. Petry" , Julian Elischer , Sidcarter , current@FreeBSD.ORG References: <200211071859.gA7IxbEV075350@netwolf.NetMasters.Com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200211071859.gA7IxbEV075350@netwolf.NetMasters.Com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Michael G. Petry : > I'm noticing the same behavior on a PPro system I have and am following > the thread "SMP broken on PPro". It looks like the problem is not SMP > specific, but it does seem PPro centric. I observed the problem on a PPro as well, but it is not specific to PPros. It will occur on any BIOSes (mostly older ones) that use a small amount of memory right before the 640K mark. The problem is that the person who committed the broken change didn't understand that you have to map this region into virtual memory if you're going to call the BIOS in protected mode. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message