public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: Konstantin Kletschke <konsti@ludenkalle.de>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.4.20-pre7-ac3 aic7xxx broken?
Date: Mon, 23 Sep 2002 13:15:44 -0600	[thread overview]
Message-ID: <2539730816.1032808544@aslan.btc.adaptec.com> (raw)
In-Reply-To: <20020923180017.GA16270@sexmachine.doom>

> Hi!
> 
> I wonder if my 
> 
> Bus  0, device   9, function  0:
>       SCSI storage controller: Adaptec AHA-7850 (rev 3).

...

> is broken or the aic7xxx driver in linux-2.4.20-pre7-ac3?
> 
> The modul loads fine, the cdrom seems to work properly, though,
> but this messages appears in my
> message.log:
> 
> ==> /var/log/syslog <==
> Sep 23 19:32:23 sexmachine kernel: scsi1: PCI error Interrupt at seqaddr
> = 0x9
> Sep 23 19:32:23 sexmachine kernel: scsi1: Data Parity Error Detected
> during address or write data phase
> 
> several times a minute. The aic7xxx_old produces no errorr messages...

On some motherboards with some chipsets, you can get these messages if
another busmaster (say an IDE drive or a sound card) is hogging the bus.
Usually this is with a VIA chipset.  Its not clear why the aic7xxx_old
driver would behave differently other than it disables memory write
and invalidate PCI transactions on this chip.  The new driver doesn't
need that work around.

As to wether it is safe or not, well our investigation into these issues
has shown that the parity errors are real, but it is the parity that
is at fault.  It is hard to say if that is the case for your MB or not.
Can you provide, in private email, a full lspci dump?

Thanks,
Justin

  reply	other threads:[~2002-09-23 19:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-23 18:00 2.4.20-pre7-ac3 aic7xxx broken? Konstantin Kletschke
2002-09-23 19:15 ` Justin T. Gibbs [this message]
2002-09-23 21:27   ` Quick aic7xxx bug hunt Jeff Garzik
2002-09-23 21:54     ` Justin T. Gibbs
2002-09-23 22:18       ` Jeff Garzik
2002-09-23 22:44         ` Justin T. Gibbs
2002-09-23 22:50           ` Jeff Garzik
2002-09-23 22:55             ` Justin T. Gibbs
2002-09-23 23:22               ` Jeff Garzik
2002-09-23 23:28                 ` Jeff Garzik
2002-09-23  7:44                   ` Benjamin Herrenschmidt

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=2539730816.1032808544@aslan.btc.adaptec.com \
    --to=gibbs@scsiguy.com \
    --cc=konsti@ludenkalle.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox