From owner-freebsd-scsi@FreeBSD.ORG Mon Jul 5 22:10:24 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC87216A4CE for ; Mon, 5 Jul 2004 22:10:24 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5438E43D3F for ; Mon, 5 Jul 2004 22:10:24 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from samsco.org (cpe.125.wat.v126.packetworks.net [64.235.97.125] (may be forged)) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i65MEpXH094147; Mon, 5 Jul 2004 16:14:57 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <40E9D1B1.1020907@samsco.org> Date: Mon, 05 Jul 2004 16:09:53 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040304 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrew Fried References: <40E960CC.4000002@cis.fed.gov> In-Reply-To: <40E960CC.4000002@cis.fed.gov> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-scsi@freebsd.org Subject: Re: Adaptec 2410SA starts doing this:aac0:COMMAND0xc551a7e8TIMEOUTAFTER 147 SECONDS (Modified by Chad Leigh -- Shire.NetLLC) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jul 2004 22:10:24 -0000 Andrew Fried wrote: > Scott, > > I have an urgent need to upgrade the storage on one of my FreeBSD 5.2.1 > boxes and was thinking of using Adaptec's 2410SA serial ATA raid card. > Since this is a critical application (evidence), I was hoping you'd > provide me with your assessment of the current state of your aac > driver. Do you believe it is stable at its current state of developement? > Thanks! > > Andrew > Andrew, I fixed the last known stability problem in the aac driver in early June. I don't want to guarantee that it is bullet-proof now, but it certainly is better than it was a few months ago and better than it was in 5.2.1. I'd advise sticking with 5.2.1 and backporting the latest aac driver sources to it. Doing this should be fairly trivial, and I'm happy to help if you get stuck. scott