From owner-freebsd-current@FreeBSD.ORG  Tue Nov  2 03:02:32 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 E28A016A4CE; Tue,  2 Nov 2004 03:02:32 +0000 (GMT)
Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id C3B3743D39; Tue,  2 Nov 2004 03:02:32 +0000 (GMT)
	(envelope-from dwhite@gumbysoft.com)
Received: by carver.gumbysoft.com (Postfix, from userid 1000)
	id B414172DD4; Mon,  1 Nov 2004 19:02:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by carver.gumbysoft.com (Postfix) with ESMTP id AD15B72DCB;
	Mon,  1 Nov 2004 19:02:32 -0800 (PST)
Date: Mon, 1 Nov 2004 19:02:32 -0800 (PST)
From: Doug White <dwhite@gumbysoft.com>
To: John Baldwin <jhb@FreeBSD.org>
In-Reply-To: <200411011752.34180.jhb@FreeBSD.org>
Message-ID: <20041101190046.J56441@carver.gumbysoft.com>
References: <20041031194121.FE2D.DSNOFE@yahoo.com.cn>
	<20041031222154.50A5.DSNOFE@yahoo.com.cn>
	<200411011752.34180.jhb@FreeBSD.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-current@FreeBSD.org
cc: Deng XueFeng <dsnofe@yahoo.com.cn>
Subject: Re: CPUTYPE?=athlon-xp breaks loader (was Re: instant reboot when
 trying to load recent RELENG_5 kernel)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Nov 2004 03:02:33 -0000

On Mon, 1 Nov 2004, John Baldwin wrote:

> Your BIOS writer needs to be beaten with a blunt instrument.  They are trying
> to enter protected mode themselves and not handling the fact that they can be
> called from vm86 mode.  There's not much FreeBSD can do about narrow-minded,
> kludgey BIOS code.

ISTR that some BIOSen try to play this game because they are trying to see
if UDMA works.  Try demoting the disk to PIO in the BIOS; FreBSD ignores
this setting when configuring disks, so its safe to leave that way.

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite@gumbysoft.com          |  www.FreeBSD.org