From: Daniel Pittman <daniel@rimspace.net>
To: Lee Revell <rlrevell@joe-job.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Adaptec AHA-2940U2W "Data Parity Error Dectected" messages
Date: Tue, 09 Aug 2005 18:16:46 +1000 [thread overview]
Message-ID: <871x53r0cx.fsf@rimspace.net> (raw)
In-Reply-To: <1123572475.27813.2.camel@mindpipe> (Lee Revell's message of "Tue, 09 Aug 2005 03:27:54 -0400")
Lee Revell <rlrevell@joe-job.com> writes:
> On Tue, 2005-08-09 at 17:19 +1000, Daniel Pittman wrote:
>> I recently installed a SCSI tape drive and Adaptec AHA-2940U2W SCSI
>> controller into my server to run backups.
>>
>> Since then, the driver issues these warnings on a semi-regular basis
>> while the drive is busy:
>>
>> Aug 9 17:00:26 anu kernel: scsi0: Data Parity Error Detected during address or write data phase
>> Aug 9 17:00:26 anu kernel: scsi0: PCI error Interrupt at seqaddr = 0x8
>
> Make sure the hardware is all installed correctly. Check that the card
> is fully seated, or try it in another PCI slot.
Thanks. I will take the server down shortly and give that a shot.
> Also check your cabling and termination.
Could SCSI cabling and/or termination cause the card to report *PCI*
errors, or am I misunderstanding these messages?
I guess that the fact that the "PCI" bit kept showing up in them is
what confuses me. I didn't except a SCSI card to report PCI bus issues
through the Linux driver, and since it claimed to be a victim, not a
cause, I didn't know quite how to trace the problem down...
Thanks,
Daniel
prev parent reply other threads:[~2005-08-09 8:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 7:19 Adaptec AHA-2940U2W "Data Parity Error Dectected" messages Daniel Pittman
2005-08-09 7:27 ` Lee Revell
2005-08-09 8:16 ` Daniel Pittman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871x53r0cx.fsf@rimspace.net \
--to=daniel@rimspace.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox