From owner-freebsd-smp Fri May 28 8:37:49 1999 Delivered-To: freebsd-smp@freebsd.org Received: from idea.co.uk (ultra2.idea.co.uk [194.36.20.11]) by hub.freebsd.org (Postfix) with ESMTP id EF40C14E65; Fri, 28 May 1999 08:36:24 -0700 (PDT) (envelope-from kiril@idea.co.uk) Received: (from kiril@localhost) by idea.co.uk (8.9.2/8.9.2) id QAA23951; Fri, 28 May 1999 16:27:07 +0100 (BST) From: Kiril Mitev Message-Id: <199905281527.QAA23951@idea.co.uk> Subject: Re: SMP and SCSI problems in 3.2 To: marcus@miami.edu (Joe "Marcus" Clarke) Date: Fri, 28 May 1999 16:27:07 +0100 (BST) Cc: ken@plutotech.com, freebsd-stable@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG In-Reply-To: from "Joe \"Marcus\" Clarke" at May 28, 99 11:17:41 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > Recently, we installed 3.2-RELEASE on our primary Computer Science server, > > > and began to see some severe errors when trying to do intensive (i.e. > > > dump/restore) disk operations to any of our SCSI-attached disks. The > > > errors we are getting are as follows: > > > > > > (da0:ahc0:0:0:0): SCB 0x29 - timed out while idle, LASTPHASE == 0x1, > > > SEQADDR == > > > 0x8 > > > (da0:ahc0:0:0:0): Queuing a BDR SCB > > > (da0:ahc0:0:0:0): Bus Device Reset Message Sent > > > (da0:ahc0:0:0:0): no longer in timeout, status = 34c > > > ahc0: Bus Devices Reset on A:0. 3 SCBs aborted > > > > > > Disabling SMP seems to clear up some of this, but we were hoping to get > > > SMP and SCSI working together. Our SCSI card is an Adaptec 2940UW2. > > > Attached is the kernel config file in use. If this seems like a > > > termination problem, we're doubting it since we had this working with an > > > early version of 3.0-SNAP with CAM. Me Too! In my case however, this happens on a MB-based Adaptec UW2 and ONLY when a vinum drive is active on the same channel as the tape drive. That is, ChA has 3 disks + 1 tape, 2 of the disks are in a vinum volume, the third (and terminating) disk is "normal". IF the vinum volume is active (eg fsck) with the tape drive plugged in, the tape drive blinks, and the above messages come out... boot -s , and mounting the standalone disk only does NOT display any erros. kernel is SMP, os version is 3.1, i DONT have SCSI ID clashes :-), further info available on request after my 5gb at-a-time backup of the massive volume finishes :-)) Kiril To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message