From owner-freebsd-stable Mon May 11 08:31:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24412 for freebsd-stable-outgoing; Mon, 11 May 1998 08:31:30 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from obiwan.TerraNova.net (root@obiwan.TerraNova.net [209.4.59.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24203 for ; Mon, 11 May 1998 08:28:08 -0700 (PDT) (envelope-from bofh@terranova.net) Received: from guenhwyvar (tog@guenhwyvar.TerraNova.net [209.4.59.4]) by obiwan.TerraNova.net (8.8.8/TNN/3.1) with SMTP id LAA17187; Mon, 11 May 1998 11:27:59 -0400 (EDT) Message-ID: <35571882.43A9@terranova.net> Date: Mon, 11 May 1998 11:25:54 -0400 From: Travis Mikalson Organization: TerraNovaNet X-Mailer: Mozilla 3.04 (Win95; I) MIME-Version: 1.0 To: Greg Rowe CC: am@f1.ru, freebsd-stable@FreeBSD.ORG Subject: Re: SCSI problems? References: <199805101413.SAA01551@px.f1.ru> <9805111442.ZM18802@psv.oss.uswest.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Greg Rowe wrote: > > The 2940UW is revision E (rev 1) which won't handle any kind of load with the > current Adaptec code. We're going to test the CAM code with the Revision E's > this week to see if the problem still exists. (Verify this by running a number > of bonnie tests to be certain) You can either put a Revision D controller in > (rev 0) or drop the transfer rate in the SCSI setup to 10 MBS to fix the > problem. > > Greg I've been getting this same spew since upgrading from 2.1.7 to 2.2.1 back when 2.2.1 was released. The AHA-2940UW in question is 2 years old at least and it doesn't seem to have anything to do with load on the hard disks. sd1(ahc0:2:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x5 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa Ordered Tag queued Ordered Tag sent sd1(ahc0:2:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x5 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa sd1(ahc0:2:0): Queueing an Abort SCB sd1(ahc0:2:0): Abort Message Sent sd1(ahc0:2:0): SCB 6 - Abort Tag Completed. sd1(ahc0:2:0): no longer in timeout --Few days pass-- sd1(ahc0:2:0): SCB 0x2 - timed out in command phase, SCSISIGI == 0x84 SEQADDR = 0x4e SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2 Ordered Tag queued sd1(ahc0:2:0): SCB 0x1 timedout while recovery in progress sd1(ahc0:2:0): SCB 0x3 timedout while recovery in progress sd1(ahc0:2:0): SCB 0x7 timedout while recovery in progress sd0(ahc0:0:0): SCB 0x4 timedout while recovery in progress sd1(ahc0:2:0): SCB 0x2 - timed out in command phase, SCSISIGI == 0x84 SEQADDR = 0x4e SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2 sd1(ahc0:2:0): abort message in message buffer sd1(ahc0:2:0): SCB 7 - Abort Tag Completed. sd1(ahc0:2:0): no longer in timeout Ordered Tag sent sd1(ahc0:2:0): SCB 0x2 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x4 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa sd1(ahc0:2:0): Queueing an Abort SCB sd1(ahc0:2:0): Abort Message Sent sd1(ahc0:2:0): SCB 2 - Abort Tag Completed. sd1(ahc0:2:0): no longer in timeout This machine has been up for 54 days and this has happened three times since it was rebooted. I thought it might just be due to a crappy choice of hard disks, too. I still need to get around to replacing them and seeing if it helps. > On May 10, 6:13pm, Andrew Maltsev wrote: > > Subject: SCSI problems? > > I'd just done `make world' and upgraded the kernel to -stable (as of > > 9-May). > > > > Here is what I got near the and of booting: > > sd0(ahc0:4:0): SCB 0x2 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == > 0x0 > > SEQADDR = 0x8 SCSISEQ = 0x12 SSTAT0 = 0x0 SSTAT1 = 0xa > > Ordered Tag queued > > sd0(ahc0:4:0): SCB 0x1 timedout while recovery in progress > > sd0(ahc0:4:0): SCB 0x0 timedout while recovery in progress > > sd0(ahc0:4:0): SCB 0x2 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == > 0x0 > > SEQADDR = 0x8 SCSISEQ = 0x12 SSTAT0 = 0x0 SSTAT1 = 0xa > > sd0(ahc0:4:0): Queueing an Abort SCB > > sd0(ahc0:4:0): Abort Message Sent > > sd0(ahc0:4:0): SCB 2 - Abort Tag Completed. > > sd0(ahc0:4:0): no longer in timeout > > Ordered Tag sent > > > > I see no more such messages. Is it a problem? > > > > I'm using > > options AHC_TAGENABLE > > options AHC_SCBPAGING_ENABLE > > options AHC_ALLOW_MEMIO > > in my kernel. > > > > There are no IDE drives, only 2940UW adapter and two scsi devices > > ahc0 rev 1 int a irq 9 on pci0:9:0 > > ahc0: aic7880 Wide Channel, SCSI Id=7, 16/255 SCBs > > (ahc0:2:0): "HP HP35480A T603" type 1 removable SCSI 2 > > st0(ahc0:2:0): Sequential-Access density code 0x13, drive empty > > ahc0: target 4 Tagged Queuing Device > > (ahc0:4:0): "SEAGATE ST34572W 0876" type 0 fixed SCSI 2 > > sd0(ahc0:4:0): Direct-Access 4340MB (8888924 512 byte sectors) > > > > Btw, should I include BOUNCE_BUFFERS option if I have no ISA cards? > > > > Andrew. -- TerraNovaNet Internet Services - Key Largo, FL Voice: (305)453-4011 Fax: (305)451-5991 http://www.terranova.net/ ---------------------------------------------- Duct tape is like the force. It has a light side, and a dark side, and it holds the universe together ... -- Carl Zwanzig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message