From owner-freebsd-scsi Thu Jun 1 20: 7:36 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from ns1.networkiowa.com (ns1.networkiowa.com [209.234.64.192]) by hub.freebsd.org (Postfix) with ESMTP id 8DFD737B67B for ; Thu, 1 Jun 2000 20:07:34 -0700 (PDT) (envelope-from johnl@raccoon.com) Received: from raccoon.com (dsl.72.145.networkiowa.com [209.234.72.145]) by ns1.networkiowa.com (8.9.3/8.9.3) with ESMTP id WAA04917; Thu, 1 Jun 2000 22:12:02 -0500 Message-ID: <393724F1.B90D3283@raccoon.com> Date: Thu, 01 Jun 2000 22:07:30 -0500 From: John Lengeling X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: John , freebsd-scsi@FreeBSD.ORG Subject: Re: Dying connection? References: <4.3.1.2.20000531193727.00ac2af0@mail.udel.edu> <3935DAA5.7859492B@raccoon.com> <20000531233754.A88537@panzer.kdm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kenneth D. Merry" wrote: > > On Wed, May 31, 2000 at 22:38:13 -0500, John Lengeling wrote: > > > > Wow! I was going to post this same thing tonight... I got the same type > > of error message today on one of my machines. I run 4.0-RELEASE, > > Adaptec 2940 v1.11 firmware, and a Seagate ST34371N. I haven't had any > > problems with the drive over the past 10 days since I installed it. > > > > I recieved the error, while I was hitting the drive hard doing a 1GM ftp > > and processing a 400M http log file using urchin. I was wondering it if > > might be a firmware problem on the 2940 or the drive revolving around > > tag queueing. > > I kinda doubt it's a tagged queueing problem with your drives, I think both > of those Seagates are known good. > > As for the controller, we don't use Adaptec's firmware, and no one else has > reported Adaptec driver problems. > > You'll have to post the error messages you got. While they may look > similar, there are many different types of timeout messages, and we'll only > be able to speculate on what the problem is if you post the errors. I wrote down the following error message: SCB 0x25 - timed out while idle, SEQADDR - 0xc Queueing a BDR SCB Bus Device Reset Message Sent no longer in timout, status = 34b Bus Device Reset on A:0 18 SCBs aborted Invalidating Pack johnl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message