From owner-freebsd-scsi@FreeBSD.ORG Sun Jul 27 20:36:48 2003 Return-Path: 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 1A65537B401; Sun, 27 Jul 2003 20:36:48 -0700 (PDT) Received: from aslan.scsiguy.com (mail.scsiguy.com [63.229.232.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0495743FA3; Sun, 27 Jul 2003 20:36:47 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by aslan.scsiguy.com (8.12.9/8.12.8) with ESMTP id h6S3akEU022311; Sun, 27 Jul 2003 21:36:46 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Date: Sun, 27 Jul 2003 21:36:46 -0600 From: "Justin T. Gibbs" To: Don Bowman , "'freebsd-scsi@freebsd.org'" , aic7xxx@freebsd.org Message-ID: <2849575408.1059363406@aslan.scsiguy.com> In-Reply-To: References: X-Mailer: Mulberry/3.0.3 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: RE: AIC7902 w/ seagate U320 drive issue on releng-4 (and current) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jul 2003 03:36:48 -0000 > FYI, i've solved this problem for me by moving to > firmware version 5 on the ST318453LW (U320 15KRPM 18GB) > seagate drive. This is exactly what I was going to suggest. 0004 is known bad in packetized operation. Your test to drop the speed to 160MB/s was a good thought, but for the 790X controllers, we will still attempt to run with packetized protocol, assuming the device supports it, even when you reduce the negotiated rate. You can disable packetized protocol in SCSI-Select which would probably have allowed you to limp along until you got updated firmware. Sadly, 0005 is not perfect. I have seen situations where under hight tag load 0005 still drops trasactions. I believe that Seagate has a fix for this, but it has yet to be put into release level firmware. You might want to touch base with them in another month to see if they have released a follow on to 0005. -- Justin