From owner-aic7xxx@FreeBSD.ORG Tue Jul 8 15:52:29 2003 Return-Path: Delivered-To: aic7xxx@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E4A437B401 for ; Tue, 8 Jul 2003 15:52:29 -0700 (PDT) Received: from magic.adaptec.com (magic-mail.adaptec.com [208.236.45.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FB7C43F3F for ; Tue, 8 Jul 2003 15:52:28 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6/8.11.6) with ESMTP id h68MqRs08527; Tue, 8 Jul 2003 15:52:27 -0700 Received: from [10.100.253.70] (aslan.btc.adaptec.com [10.100.253.70]) by redfish.adaptec.com (8.8.8p2+Sun/8.8.8) with ESMTP id PAA27909; Tue, 8 Jul 2003 15:52:27 -0700 (PDT) Date: Tue, 08 Jul 2003 16:54:05 -0600 From: "Justin T. Gibbs" To: David Cross , aic7xxx@freebsd.org Message-ID: <460170000.1057704844@aslan.btc.adaptec.com> In-Reply-To: <3F0B3C0A.BC3BD8C0@msfc.nasa.gov> References: <3F0354C7.C3ADD9B@msfc.nasa.gov> <3F036341.97CCE4BC@msfc.nasa.gov><3F03A90D.A8C142A2@msfc.nasa.gov> <3F0B3C0A.BC3BD8C0@msfc.nasa.gov> X-Mailer: Mulberry/3.1.0b3 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: aic79xx abort during boot X-BeenThere: aic7xxx@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Justin T. Gibbs" List-Id: Adaptec Device Drivers in FreeBSD and Linux List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2003 22:52:29 -0000 > However, your comment about a possible revision issue on the IBM drives > may still be something I am facing. There are intermittent messages during > boot which would lead me to believe that it might be in our better interest > to pursue a revision update. > There is a series of messages that come up stating that: > > DV failed to configure device... I still don't know the type of device you are using, so I can't say if upgrading the firmware is the correct solution to this problem. It would be helpfull to see all of the messages from a boot with the driver configured for debugging and the debugging options set to 0x800. This will show all of the domain validation process, making it trivial to understand the DV failure. -- Justin