Date: Tue, 26 Mar 2002 12:16:46 +0100 From: Bernd Walter <ticso@cicely8.cicely.de> To: Julian Elischer <julian@vicor-nb.com> Cc: Scott Long <scott_long@btc.adaptec.com>, scsi@FreeBSD.ORG Subject: Re: SCSI error messages. Message-ID: <20020326111645.GG14060@cicely8.cicely.de> In-Reply-To: <3C9A947D.CC00A837@vicor-nb.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020326111645.GG14060>