Date: Tue, 23 Feb 1999 13:11:51 -0700 From: "Justin T. Gibbs" <gibbs@plutotech.com> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: scsi@FreeBSD.org Subject: Re: dual-channel U2W scsi performance Message-ID: <199902232020.NAA13242@pluto.plutotech.com> In-Reply-To: Your message of "Tue, 23 Feb 1999 14:50:26 EST." <14034.65025.537279.428755@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
>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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199902232020.NAA13242>