Date: Mon, 11 Feb 2002 00:43:30 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= <groudier@free.fr> To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de> Cc: <freebsd-scsi@FreeBSD.ORG>, Frank Altpeter <frank@altpeter.de> Subject: Re: SCSI parity error detected Message-ID: <20020211002602.I2420-100000@gerard> In-Reply-To: <200202112125.g1BLPQN61061@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 11 Feb 2002, Joerg Wunsch wrote: > G=E9rard Roudier <groudier@free.fr> wrote: > > > OTOH, the offending devices exhibit some *SUN* proprietary > > firmware. Given that SUN guys are known to be great reinventors of > > the wheel, we may suspect these devices to have some questionnable > > behaviour. > > Ah no. AFAICT, all that Sun's doing here is addings their "SUNxxG" to > the vendor string so their tools can quickly identify and categorize > their disks. Very probably. But it just makes their firmware suspicious. What a questionnable value-added. > I'm using a > > <FUJITSU MAJ3182M SUN18G 0804> at scbus0 target 0 lun 0 (pass0,da0) > > (also SCA, but sitting behind a Tekram 53c895 40 MHz LVD bus) here, > and it works just great. May-be the driver understands the NVRAM setup here. I donnot know all hard disks in existence. Is this one wide capable? > > If we suppose that SUN guys didn't break SCSI too much here (??), > > the problem may be due to your SCA-to-SCSI2 tinking machines not > > connecting and/or terminating all signals as needed for WIDE SCSI. > > Since i was the guy advising him to ask here, i'm now already familiar > with Frank's setup. ;-) He originally used a plain 8-bit > configuration, his "SCA-to-SCSI2" should rather read as "SCA to 8-bit > 50-pin" adapter. So there's no wide negotiation involved at all. > Certainly those adapters don't terminate anything, but the disks > should never enter wide mode anyway. > > Following my advise he changed the old configuration from using the > CD-ROM's internal (passive) termination to an active plug-in > terminator, which didn't help. > > This Dawicontrol is 8-bit only btw., despite of using an 53c875. But the driver cannot guess it. And it doesn't understand the Dawicontrol settings from NVRAM (if some exists). Note that when the driver negotiates Wide, it negotiates also Sync immediately without any DATA phase occurring and reports the new parameters to CAM. As a result, the new transfer settings should be printed to the syslog prior to any further DATA phase. If there is no such message in the log, then the Wide+Sync negotiation should not have taken place. This point should be checked. OTOH, if there is no such message in the log, it could well be the initial INQUIRY response that got a SCSI PARITY error. The problem might then be the/a SCSI PARITY signal not being properly driven/connected. G=E9rard. 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?20020211002602.I2420-100000>