From owner-freebsd-scsi Tue Mar 26 3:20:42 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id E56D337B416 for ; Tue, 26 Mar 2002 03:20:32 -0800 (PST) Received: (from uucp@localhost) by srv1.cosmo-project.de (8.11.6/8.11.6) with UUCP id g2QBKEr02995; Tue, 26 Mar 2002 12:20:14 +0100 (CET) (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.1.10]) by cicely5.cicely.de (8.12.1/8.12.1) with ESMTP id g2QBGo6e095612; Tue, 26 Mar 2002 12:16:50 +0100 (CET)?g (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (localhost [127.0.0.1]) by cicely8.cicely.de (8.12.2/8.12.2) with ESMTP id g2QBGonU017317; Tue, 26 Mar 2002 12:16:50 +0100 (CET) (envelope-from ticso@cicely8.cicely.de) Received: (from ticso@localhost) by cicely8.cicely.de (8.12.2/8.12.2/Submit) id g2QBGlXd017316; Tue, 26 Mar 2002 12:16:47 +0100 (CET) Date: Tue, 26 Mar 2002 12:16:46 +0100 From: Bernd Walter To: Julian Elischer Cc: Scott Long , scsi@FreeBSD.ORG Subject: Re: SCSI error messages. Message-ID: <20020326111645.GG14060@cicely8.cicely.de> References: <3C9A8A03.A36B57B6@vicor-nb.com> <1016761959.8445.19.camel@hollin.btc.adaptec.com> <3C9A90FE.30983DC@vicor-nb.com> <1016763240.8445.24.camel@hollin.btc.adaptec.com> <3C9A947D.CC00A837@vicor-nb.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C9A947D.CC00A837@vicor-nb.com> User-Agent: Mutt/1.3.26i X-Operating-System: FreeBSD cicely8.cicely.de 5.0-CURRENT i386 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, Mar 21, 2002 at 06:18:37PM -0800, Julian Elischer wrote: > Scott Long wrote: > > > > > > > > Oops, you might be right, I mistook the pcib0 line. Still, check the > > BIOS to see if anything screwy is enabled. > > > > Scott > > Also I should add that the machine has been seen working for a while. > I just would like to know what the messages mean. Well the timeouts are because the drive went to sleep and did not return from a comand in a reasonable time. The result is a BDR (bus device reset) which tries to reset the drive. Finaly the drive responds not beeing ready. Sounds like a bad firmware on the drive. The timeout alone could be a bad cabeling too, but this should not result in dropping the device. You might work around the firmware bug by disabling tagged queueing and/or write cache. It could also be triggered by a problem with a physical drive. Nevertheless the error behavour is broken. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message