From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 23 02:00:09 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 4472D16A4CE; Wed, 23 Jun 2004 02:00:09 +0000 (GMT) Received: from mail.jrv.org (rrcs-sw-24-73-246-106.biz.rr.com [24.73.246.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id B8D8243D5E; Wed, 23 Jun 2004 02:00:04 +0000 (GMT) (envelope-from james@jrv.org) Received: from [192.168.3.156] (zippy.jrv.org [192.168.3.156]) (authenticated bits=0) by mail.jrv.org (8.12.11/8.12.10) with ESMTP id i5N1xfQN012317 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Jun 2004 20:59:42 -0500 (CDT) (envelope-from james@jrv.org) Message-ID: <40D8E40D.5090805@jrv.org> Date: Tue, 22 Jun 2004 20:59:41 -0500 From: "James R. Van Artsalen" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Losher References: <200406221811.47868.Peter_Losher@isc.org> In-Reply-To: <200406221811.47868.Peter_Losher@isc.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Vinod Kashyap cc: freebsd-amd64@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: [freebsd-amd64] Possible 3ware 8506-12 SATA Controller issues... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2004 02:00:09 -0000 Peter Losher wrote: >>You might want to upgrade to twe in -CURRENT, and see if that >>makes a difference. >> >> > >Tried compiling a 5.2.1 kernel w/ the twe driver plopped from -CURRENT >cvsup'ed 30 minutes ago, and it didn't go to well: > > 5.2.1-release w/8506-8 seems to work for me on AMD64 with 8 GB of RAM in a Tyan S2885 with two Opteron 248 CPUs in a slot jumpered to 64/66 PCI rather than PCI-X. I'm not trying to use any twe-specific monitoring tools and haven't tested to see if the twe driver notices disk errors. I believe that the driver does not handle more than 4 GB of RAM and requires bounce-buffers. Testing consisted of running "make buildworld" in a loop with a kernel building in a loop at the same; see if it's still running after a week and fsck is clean.