From owner-freebsd-scsi@FreeBSD.ORG  Wed Aug  6 07:53:40 2003
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Delivered-To: freebsd-scsi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id A3B9E37B432; Wed,  6 Aug 2003 07:53:37 -0700 (PDT)
Received: from mail.sandvine.com (sandvine.com [199.243.201.138])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 4242243FBF; Wed,  6 Aug 2003 07:53:36 -0700 (PDT)
	(envelope-from don@sandvine.com)
Received: by mail.sandvine.com with Internet Mail Service (5.5.2653.19)
	id <305LHM6S>; Wed, 6 Aug 2003 10:53:35 -0400
Message-ID: <FE045D4D9F7AED4CBFF1B3B813C8533702742163@mail.sandvine.com>
From: Don Bowman <don@sandvine.com>
To: "'Justin T. Gibbs'" <gibbs@scsiguy.com>,
	Don Bowman <don@sandvine.com>,
	"'freebsd-scsi@freebsd.org'" <freebsd-scsi@freebsd.org>,
	"'aic7xxx@freebsd.org'" <aic7xxx@freebsd.org>
Date: Wed, 6 Aug 2003 10:53:28 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Ongoing U320 AIC7902 Seagate ST318453LW issues, SCB timed out
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Aug 2003 14:53:40 -0000

From: Justin T. Gibbs [mailto:gibbs@scsiguy.com]

> > On some systems I am sometimes getting this error pop out.
> > It seems to track the system for some reason. This is
> > not a bad cable, signals look good on oscope.
> > 
> > Drive is: SEAGATE ST318453LW, FW 0005
> 
> You seem to have found another way to trip up the Seagate drives.
> According to the controller, there are 13 commands that are 
> outstanding
> on the drive that have not been completed within the timeout period.
> The bus is idle and so is the controller.
> 
> The SCB count in this dump is 64.  Are you not throttling the number
> of commands to 32 for these devices?  If so, the SCB count should not
> be higher than 32 for a single drive configuration.  I have 
> seen behavior
> similar to what you are experiencing with tag depths greater than 32.

I'm continuing to test without the throttle. I'm @ a loss for why
it tracks some systems and not others.

There doesn't seem to be a reliable way to drop the number of
tags since the system may not always come up. I don't think
there's an option in the kernel to do so.

--don