From owner-freebsd-stable Tue Jul 25 20:24:25 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id DA39437B7C4 for ; Tue, 25 Jul 2000 20:24:21 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id UAA18452; Tue, 25 Jul 2000 20:24:14 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id UAA19123; Tue, 25 Jul 2000 20:24:13 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Tue, 25 Jul 2000 20:24:13 -0700 (PDT) Message-Id: <200007260324.UAA19123@vashon.polstra.com> To: stable@freebsd.org Cc: richp@richp.com Subject: Re: SCSI errors: Invalidating pack In-Reply-To: <200007260257.TAA31155@squishy.slurping.com> References: <200007260257.TAA31155@squishy.slurping.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200007260257.TAA31155@squishy.slurping.com>, Rich Prillinger wrote: > > I've been messing around trying to get SCSI to work on a > FreeBSD box for a few weeks now. No matter what combination > of the following hardware/software I use, I get this error at > some (seemingly random) time during disk-intensive activities > (cvsup, makes, etc): > > (da0:ahc0:0:0:0): Invalidating pack > (da0:ahc0:0:0:0): SCB 0x1f - timed out while idle, SEQADDR == 0xa > (da0:ahc0:0:0:0): Queueing a BDR SCB > (da0:ahc0:0:0:0): no longer in timeout, status = 34a > (da0:ahc0:0:0:0): Invalidating pack > (da0:ahc0:0:0:0): SCB 0x1f - timed out while idle, SEQADDR == 0xa > (da0:ahc0:0:0:0): Queueing a BDR SCB > (da0:ahc0:0:0:0): no longer in timeout, status = 34a > (da0:ahc0:0:0:0): Invalidating pack > (da0:ahc0:0:0:0): Invalidating pack > (da0:ahc0:0:0:0): Invalidating pack > (da0:ahc0:0:0:0): Invalidating pack > (da0:ahc0:0:0:0): Invalidating pack > [etc] > > After which the machine hangs and requires a hard reboot. > > I've tried 3.4-RELEASE, 4.0-RELEASE, and 4.0-STABLE snapshot > (20000718 and 0723) with all the following hardware combinations: > > Seagate ST39216W with Adaptec 2940UW Pro > Seagate ST39216W with Advansys 3940UW > > Seagate ST39216N with Adaptec 2940U > Seagate ST39216N with Adaptec 2940UW Pro > Seagate ST39216N with Advansys 3940UW Anoncvs.freebsd.org had this problem about 2 weeks ago. I mailed the messages to Justin Gibbs and he told me that the problem is caused by a firmware bug in the Seagate drives. Anoncvs has slightly different drives, but I bet its the same bug: da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 8761MB (17942584 512 byte sectors: 255H 63S/T 1116C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 8761MB (17942584 512 byte sectors: 255H 63S/T 1116C) You will have to contact Seagate technical support to get the firmware upgrades. But in the meantime, according to Justin, disabling the write caches (WCE in mode page 8) will work around the problem. You can do that with the camcontrol command. Justin posted more details about this in the FreeBSD-scsi mailing list. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message