Date: Sat, 4 Apr 1998 12:40:50 -0800 (PST) From: Alex <garbanzo@hooked.net> To: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= <ache@nagual.pp.ru> Cc: scsi@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: SCSI errors with latest -current Message-ID: <Pine.BSF.3.96.980404123823.10273C-100000@zippy.dyn.ml.org> In-Reply-To: <19980404193439.51330@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 4 Apr 1998, [koi8-r] Андрей Чернов wrote: > With latest -current I start to get this sort of errors for my several > SCSI drives. Since they started at once for several drives, I suppose it > is not hardware problem. Any ideas? I find that if your disk system is pushed hard enough, that you will get errors like that with SCB paging and/or TAGGED_QUEUING enabled even before PHKs commits. This is one of the things the CAM code (dunno if it's stable enough to use) fixes. In essence it's a combination hardware and software problem... I think. > sd1: SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > SEQADDR = 0x4 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa > Ordered Tag queued > Ordered Tag sent > sd1: SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > SEQADDR = 0x5 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa > sd1: Queueing an Abort SCB > sd1: Abort Message Sent > sd1: SCB 5 - Abort Tag Completed. > sd1: no longer in timeout - alex "We are upping our standards ... so up yours." - Pat Paulsen for US of A Prez, 1988 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980404123823.10273C-100000>