From owner-freebsd-amd64@FreeBSD.ORG  Mon Dec  6 21:55:52 2004
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
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 2A6B516A4CE
	for <freebsd-amd64@freebsd.org>; Mon,  6 Dec 2004 21:55:52 +0000 (GMT)
Received: from eagle4.cc.GeorgiaSouthern.edu (eagle4.cc.GeorgiaSouthern.edu
	[141.165.4.53])	by mx1.FreeBSD.org (Postfix) with ESMTP id 3D1DD43D1F
	for <freebsd-amd64@freebsd.org>;
	Mon,  6 Dec 2004 21:55:51 +0000 (GMT)
	(envelope-from sdodson@sdodson.com)
Received: from [141.165.208.115] (vl208-115.vl208.GeorgiaSouthern.edu
	[141.165.208.115])iB6LtmjS007423
	for <freebsd-amd64@freebsd.org>; Mon, 6 Dec 2004 16:55:49 -0500 (EST)
Message-ID: <41B4D564.2090006@sdodson.com>
Date: Mon, 06 Dec 2004 16:55:48 -0500
From: Scott Dodson <sdodson@sdodson.com>
User-Agent: Mozilla Thunderbird 1.0RC1 (X11/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: freebsd-amd64@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: nForce woes?
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Dec 2004 21:55:52 -0000

Do we expect the nForce 4 chipset to alleviate many of the problems 
found in nForce 3 or should I steer clear of products using this chipset 
as well?

--
Scott Dodson