From owner-freebsd-scsi Tue Feb 23 12:20:40 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (Postfix) with ESMTP id B3E24115F5 for ; Tue, 23 Feb 1999 12:20:36 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.1/8.9.1) with ESMTP id NAA13242; Tue, 23 Feb 1999 13:20:33 -0700 (MST) (envelope-from gibbs@plutotech.com) Message-Id: <199902232020.NAA13242@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrew Gallatin Cc: scsi@FreeBSD.org Subject: Re: dual-channel U2W scsi performance In-reply-to: Your message of "Tue, 23 Feb 1999 14:50:26 EST." <14034.65025.537279.428755@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Feb 1999 13:11:51 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I just tried, and I initially coouldn't get the second scsi channel >working at all. The end result is that the first channel appears to >probe the bus fine, if I move a chain which works just fine on the >first channel to the second channel, I see parity errors whenever a >disk is accessed when the bus is probed: > ><..> >(probe0:ahc1:0:0:2): parity error during Message-In phase. >SEQADDR == 0x15d >SCSIRATE == 0x95 There must be something wrong with your cables. I've had several instances where a loose connector pin caused intermittent parity-errors. If both the driver and the end device are reporting errors, they can't be wrong. I've tested SE operation on the aic7896, so I know that it can work with the current driver. One other thing that may be interesting is a dmesg from a -v boot. It could be that the driver is not setting the termination properly, but this is fairly straight forward for the aic789X series. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message