Date: Mon, 22 Mar 1999 15:16:05 -0700 (MST) From: "Kenneth D. Merry" <ken@plutotech.com> To: obrien@leonardo.net (Mike O'Brien) Cc: freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Odd messages Message-ID: <199903222216.PAA68834@panzer.plutotech.com> In-Reply-To: <199903220723.XAA00414@caern.limax.com> from "Mike O'Brien" at "Mar 21, 1999 11:23:40 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Mike O'Brien wrote... > Ever since I upgraded to 3.1-RELEASE, I've occasionally been > seeing bursts like this: > > Mar 21 20:01:22 caern /kernel: (da0:ahc0:0:0:0): SCB 0x18 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x9 > Mar 21 20:01:22 caern /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB > Mar 21 20:01:22 caern /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent > Mar 21 20:01:22 caern /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 > Mar 21 20:01:22 caern /kernel: Unexpected busfree. LASTPHASE == 0xa0 > Mar 21 20:01:22 caern /kernel: SEQADDR == 0x151 [ ... ] > > Mar 21 23:15:30 caern /kernel: da0 at ahc0 bus 0 target 0 lun 0 > Mar 21 23:15:30 caern /kernel: da0: <QUANTUM VP32210 81H8> Fixed Direct Access SCSI-2 device > Mar 21 23:15:30 caern /kernel: da0: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled > Mar 21 23:15:30 caern /kernel: da0: 2103MB (4308352 512 byte sectors: 64H 32S/T 2103C) [ ... ] > It's an Adaptec 2940 with two drives as shown. > > Mostly, it happens while the system is idle and when I get > back, everything is OK. This last time, the disk system was frozen > and I had to Hit The Big Black Button. Things rebooted normally. > > Ordinarily I'd say the drive is wonky, but my suspicions are > aroused: things ran fine under 2.2.6, and this bad stuff started > happening as soon as I installed 3.1. Any takers? This is most likely a drive firmware problem, although it could be cabling or termination. And the system wasn't completely idle when it happened. The 'timed out while idle' message means that a command from the da(4) driver timed out and there was nothing else going on at the time. The timeout for reads and writes from the da driver is 60 seconds. So if the drive doesn't respond in that period of time, something is definitely wrong. What is a VP32210? I don't see that anywhere on Quantum's web site listing of various model numbers. Probably the reason it happens on 3.1 and not on 2.2.6 is that CAM loads the disks a whole lot more than the old SCSI layer did. I suspect that this is a firmware problem, since I've seen other Quantum disks with the same symptoms. The most famous example is the Quantum Atlas II with LXY4 or older firmware. (They fixed that problem in the LYK8 firmware.) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199903222216.PAA68834>