Date: Fri, 26 Feb 1999 16:17:21 -0700 (MST) From: "Kenneth D. Merry" <ken@plutotech.com> To: volf@oasis.IAEhv.nl (Frank Volf) Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: ahc error message Message-ID: <199902262317.QAA53929@panzer.plutotech.com> In-Reply-To: <199902262120.VAA02181@avalon.oasis.IAEhv.nl> from Frank Volf at "Feb 26, 1999 10:20:10 pm"
index | next in thread | previous in thread | raw e-mail
Frank Volf wrote... > > Hi, > > Can somebody please explain the following error message: > > SEQADDR == 0x155 > (da0:ahc0:0:0:0): SCB 0x9 - timed out while idle, LASTPHASE == 0x1, SEQADDR > == > (da0:ahc0:0:0:0): Queuing a BDR SCB > (da0:ahc0:0:0:0): Bus Device Reset Message Sent > (da0:ahc0:0:0:0): no longer in timeout, status = 353 > Unexpected busfree. LASTPHASE == 0xa0 > SEQADDR == 0x155 > (da0:ahc0:0:0:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SEQADDR > == > (da0:ahc0:0:0:0): Queuing a BDR SCB > (da0:ahc0:0:0:0): Bus Device Reset Message Sent > (da0:ahc0:0:0:0): no longer in timeout, status = 353 > Unexpected busfree. LASTPHASE == 0xa0 > SEQADDR == 0x155 > (da0:ahc0:0:0:0): SCB 0x15 - timed out while idle, LASTPHASE == 0x1, SEQADDR > == > (da0:ahc0:0:0:0): Queuing a BDR SCB > (da0:ahc0:0:0:0): Bus Device Reset Message Sent > (da0:ahc0:0:0:0): no longer in timeout, status = 353 > Unexpected busfree. LASTPHASE == 0xa0 > SEQADDR == 0x155 > > I'v got dozens of them with different numbers after SCB. Is this a serious > problem? How can it be fixed? The system is a 3.1-STABLE system upgraded > last week. Before that it was a 2.6-RELEASE, in which I never noticed this > or similar SCSI messages. The 'timed out while idle' messages mean that the drive did not return a command before the timeout period expired, and there was nothing going on on the bus at the time. The timeout period for the da driver is 60 seconds, so if a drive doesn't return a transaction in that period of time, something is certainly wrong. This indicates that the drive is "going out to lunch" for some reason, and not responding to commands. There are several possible explanations: - it could be a cabling or termination problem - it could be your drive has buggy firmware. What kind of drive is it, and how heavily loaded is it? What was going on when the errors popped up? - it could be your drive is dying Some firmware revisions of the Quantum Atlas II showed symptoms like that under heavy load. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the messagehelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199902262317.QAA53929>