From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 20 19:06:53 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8FD0516A4CE; Mon, 20 Sep 2004 19:06:53 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C6FF43D2D; Mon, 20 Sep 2004 19:06:53 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id i8KJ6iaS009444; Mon, 20 Sep 2004 12:06:45 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id i8KJ6iq4009443; Mon, 20 Sep 2004 12:06:44 -0700 (PDT) (envelope-from obrien) Date: Mon, 20 Sep 2004 12:06:43 -0700 From: "David O'Brien" To: Scott Long Message-ID: <20040920190643.GC9191@dragon.nuxi.com> References: <20040919135233.4997ea78@dolphin.local.net> <414DEE9B.3020800@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <414DEE9B.3020800@samsco.org> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: amd64@freebsd.org cc: re@freebsd.org Subject: Re: NO_MIXED_MODE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2004 19:06:53 -0000 On Sun, Sep 19, 2004 at 02:39:55PM -0600, Scott Long wrote: > >I'll second that motion. I have the same chipset, and the same problem > >with NO_MIXED_MODE. I think we should err on the side of caution with > >this one. > > Let's see what Peter, David, and John say about this. My understanding > is that mixed mode has a measurable performance impact, so we don't want > to turn it on universally unless necessary. Correct. > Maybe David knows of a BIOS upgrade that would help your motherboards. I've never been able to get a sufficiently accurate detailed explanation of the problem FreeBSD has on this mobo that I could get the BIOS vendor to fix it; (read, there isn't a fix I know of; but you should be using the latest '1007' for other reasons). I've avoided nForce3-150 mobos like the plague and don't have one for looking into this. If anyone can dive deeper into this issue, I'd appreciate it and will work to have the vendor fix it. -- -- David (obrien@FreeBSD.org)