From owner-freebsd-scsi Mon Apr 21 08:20:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA21879 for freebsd-scsi-outgoing; Mon, 21 Apr 1997 08:20:50 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA21868 for ; Mon, 21 Apr 1997 08:20:46 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.3) with ESMTP id JAA09950; Mon, 21 Apr 1997 09:20:41 -0600 (MDT) Message-Id: <199704211520.JAA09950@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: Alan Judge cc: freebsd-scsi@freebsd.org Subject: Re: Vendor specific ASCQ SCSI errors in 2.2-STABLE In-reply-to: Your message of "Mon, 21 Apr 1997 13:17:52 BST." <199704211217.NAA20868@indigo.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Apr 1997 09:19:08 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I sometimes get errors of the form: > sd0(ahc0:0:0): ABORTED COMMAND asc:41,86 Vendor Specific ASCQ, retries >:4 >only under high load and on multiple different disks (as far as I can reproduc >e >the problem). >From a quick look at the Atlas II tech ref I have here, this is: DDMA overrun or REQ/ACK overrun/underrun error. BUT, the manual says that it will return HARDWARE ERROR not ABORTED COMMAND in this case. I'll have to go look at how we print out the information to make sure this is correct. If this is indeed the case, I would suspect a cabling or termination problem that rears it's ugly head only under heavy load. >I have a bunch of identical disks in a 2.2-GAMMA machine and have never seen >a similar error. The 2.2-GAMMA driver can't generate the same kinds of load as the current driver. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations ===========================================