From: "Alok K. Dhir" <alok@dhir.net>
To: <linux-kernel@vger.kernel.org>
Subject: RE: Scsi data parity errors on aix7xxx in kernel 2.4.5
Date: Thu, 31 May 2001 15:02:11 -0400 [thread overview]
Message-ID: <000901c0ea04$32b1b650$1e01a8c0@dhir.net> (raw)
In-Reply-To: <000801c0ea01$51d4eeb0$1e01a8c0@dhir.net>
Forgot to mention (in case it matters) that I'm running ReiserFS on sdd6
which is hanging off of scsi1.
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org
> [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Alok K. Dhir
> Sent: Thursday, May 31, 2001 2:42 PM
> To: linux-kernel@vger.kernel.org
> Subject: Scsi data parity errors on aix7xxx in kernel 2.4.5
>
>
>
> Running kernel 2.4.5 with two scsi controllers - scsi0 is a
> sym53c8xx, scsi1 is aic7xxx.
>
> For the last month or so, I've been getting the following
> error in my syslog 10 or so times a day:
>
> -----
> May 31 14:09:51 dog kernel: scsi1: PCI error Interrupt at
> seqaddr = 0x8e May 31 14:09:51 dog kernel: scsi1: Data Parity
> Error Detected during address or write data phase
> -----
>
> The box is a PIII-750 on an Aopen AX6BC (BX chipset) running
> at 930Mhz (7.5 * 124Mhz bus speed), with 384 megs of RAM
> (1*128MB PC100, 2*128MB PC133). I've tried running at
> 7.5*100 and I still get the errors.
>
> Any advice as to what I should look at to solve this problem?
>
> Thanks
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in the body of a message to
> majordomo@vger.kernel.org More majordomo info at
> http://vger.kernel.org/majordomo-info.html
> Please read the
> FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2001-05-31 18:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-31 18:41 Alok K. Dhir
2001-05-31 19:02 ` Alok K. Dhir [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='000901c0ea04$32b1b650$1e01a8c0@dhir.net' \
--to=alok@dhir.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®