Date: Sat, 13 Feb 1999 12:22:55 -0600 (CST) From: Jonathan Lemon <jlemon@americantv.com> To: freebsd-scsi@FreeBSD.ORG Subject: Re: bad drive? Message-ID: <199902131822.MAA25275@free.pcs> In-Reply-To: <local.mail.freebsd-scsi/199902130338.UAA38390@panzer.plutotech.com> References: <local.mail.freebsd-scsi/61128.918808646@gjp.erols.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <local.mail.freebsd-scsi/199902130338.UAA38390@panzer.plutotech.com> you write: >Gary Palmer wrote... >> Feb 11 12:46:39 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x1c - timed out while >> id >> le, LASTPHASE == 0x1, SEQADDR == 0xc >> Feb 11 12:46:40 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB >> Feb 11 12:46:40 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message >> Sent >> Feb 11 12:46:40 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, >> status >> = 353 >> Feb 11 12:46:40 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 >> Feb 11 12:46:40 virtual /kernel: SEQADDR == 0x157 >> Feb 11 12:47:39 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x2f - timed out while >> id > >I suppose it is possible that this could be caused by bad termination or >something similar. I recently had a pile of errors similar to this on a 3.0-BETA machine, where I couldn't do a `make world' or tape backup without getting lots of `Timed out while idle' messages. Taking the SCSI cable out, and hammering on all the connectors to insure a solid fit between the connectors and the cable appears to have solved the problem for me. -- Jonathan 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?199902131822.MAA25275>