[1676] in linux-scsi channel archive
Re: ATN Initiator Detected Error
daemon@ATHENA.MIT.EDU (Marc SCHAEFER)
Thu Apr 3 02:16:29 1997
From: schaefer@alphanet.ch (Marc SCHAEFER)
Date: 3 Apr 1997 06:45:44 GMT
Apparently-To: linux-scsi@vger.rutgers.edu
To: ;@unlisted-recipients (no To-header on input)
In article <5husv9$oh0$1@vulcan.alphanet.ch>,
Gerard Roudier <groudier@club-internet.fr> writes:
> It is this one. The message MESSAGE PARITY ERROR means that a scsi parity
> error has been detected while receiving a message. It can be send by any
Yes, that's right.
> AFAIK, SCSI standards recommendation is the initiator send a INITIATOR
> DETECTED ERROR message in order to notify a target of scsi parity error in
> DATA IN phase. So, in my opinion, the behaviour of the 154X controller is
> quite correct (Could it be different?).
On the SCSI specification I have, this message means that an internal
initiator failure has happened, linked or not to previous SCSI
operations or internal to the initiator, which should not prevent the
target from retrying the operation. Also, this is not only happening
with the 1542, and not only on Linux (I did some testing to find out).
They don't speak clearly about a parity error, and that looked confusing
to me. However, after re-reading the spec for MESSAGE PARITY ERROR, it
seems clearer to me.
Thank you for your help
PS: now I have to figure out *why* I get so much parity errors, then.
