All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Pittman <daniel@rimspace.net>
To: linux-kernel@vger.kernel.org
Subject: Adaptec AHA-2940U2W "Data Parity Error Dectected" messages
Date: Tue, 09 Aug 2005 17:19:47 +1000	[thread overview]
Message-ID: <878xzbr2zw.fsf@rimspace.net> (raw)

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

[...]

Aug  9 17:03:34 anu kernel: scsi0: Data Parity Error Detected during address or write data phase

[...]

Aug  9 17:04:36 anu kernel: scsi0: PCI parity error checking has been disabled.
Aug  9 17:04:36 anu kernel: scsi0: Some device on this bus is generating bad parity.
Aug  9 17:04:36 anu kernel: scsi0: This is an error *observed by*, not *generated by*, this controller.
Aug  9 17:04:36 anu kernel: scsi0: Too many PCI parity errors observed as a target.
Aug  9 17:04:36 anu kernel: scsi0: WARNING WARNING WARNING WARNING


Now, the log message claims that the SCSI controller is not responsible
for these parity errors, so my questions are:

* should I panic about this?
* should I have seen this before the SCSI controller was installed?
* can I do anything about it, or identifying the cause?

Thanks,
      Daniel

             reply	other threads:[~2005-08-09  7:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-09  7:19 Daniel Pittman [this message]
2005-08-09  7:27 ` Adaptec AHA-2940U2W "Data Parity Error Dectected" messages Lee Revell
2005-08-09  8:16   ` Daniel Pittman

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=878xzbr2zw.fsf@rimspace.net \
    --to=daniel@rimspace.net \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.