[6859] in linux-scsi channel archive
Re: ncr53c875 parity errors
daemon@ATHENA.MIT.EDU (Kurt Garloff)
Wed Jul 21 04:16:34 1999
Date: Wed, 21 Jul 1999 10:05:49 +0200
From: Kurt Garloff <garloff@suse.de>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-scsi@vger.rutgers.edu
Mail-Followup-To: Keith Owens <kaos@ocs.com.au>,
linux-scsi@vger.rutgers.edu
In-Reply-To: <19990721050454.26802.qmail@mail.ocs.com.au>; from Keith Owens on Wed, Jul 21, 1999 at 03:04:52PM +1000
--bajzpZikUji1w+G9
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
On Wed, Jul 21, 1999 at 03:04:52PM +1000, Keith Owens wrote:
> Does this indicate a card problem, a cable problem or is my drive
> giving up? Please copy me on replies, I am not on this list.
> ncr53c875-0: command processing resumed
> Vendor: IBM Model: DORS-32160 Rev: WA6A
> Type: Direct-Access ANSI SCSI revision: 02
> ...
> ncr53c875-0: SCSI parity error detected: SCR1=3D3 DBC=3D19000000 SSTAT1=
=3Df1
Parity errors are very bad. There are some very old scanners which are not
able to generate Parity, so you would have to disable Parity for these
devices.
For your DORS, a parity error is not to be expected. Check cabling and
termination. You're very likely to have hardware problems.
--=20
Kurt Garloff <garloff@suse.de> SuSE GmbH, N=FCrnberg, FRG
Linux kernel development; SCSI drivers: tmscsim(DC390), DC395
--bajzpZikUji1w+G9
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
iQCVAwUBN5V/XRaQN/7O/JIVAQHndAP7BToLf1ZKRxqXdPGJvptT93htRs5MHLlr
IigGCqOCK31XKfMF/MHGUtIjaMWWkRMV9ceVbs8cIDaecVBLFYmrJh4BO3Roetas
tNmRQjiC0KrAecYkd4AD3+MPI+Rp0SQ/MWU3puKrh6PR4Gw5FyM5xMLKaAqeLiK2
QEEU1iBGSw4=
=AnZX
-----END PGP SIGNATURE-----
--bajzpZikUji1w+G9--
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
