From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: Ishikawa <ishikawa@yk.rim.or.jp>, Andrew Morton <akpm@digeo.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: aic7xxx woes in 2.5
Date: Sun, 15 Dec 2002 13:17:44 -0700 [thread overview]
Message-ID: <28320000.1039983464@aslan.btc.adaptec.com> (raw)
In-Reply-To: <3DFC1BD2.F2F347C9@yk.rim.or.jp>
> Hi,
>
>> The parity error is intermittent. But when it happens, the lockup
>> always happens.
>>
>> This never happens in 2.4 kernels.
>>
>> It seems to happen a little more frequently on uniprocessor builds.
>>
>> So relevant questions would be:
>>
>> 1) Why does only 2.5 get the parity error?
>
>
> Since you say "uniprocessor builds", maybe you are using
> high-quality dual processor board. But just in case, does your
> motherboard support proper PCI parity bus check?
These are SCSI parity errors, not PCI parity errors.
--
Justin
next prev parent reply other threads:[~2002-12-15 20:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-15 4:31 aic7xxx woes in 2.5 Andrew Morton
2002-12-15 6:06 ` Ishikawa
2002-12-15 6:48 ` Andrew Morton
2002-12-15 13:48 ` Ishikawa
2002-12-15 20:17 ` Justin T. Gibbs [this message]
2002-12-15 20:09 ` Justin T. Gibbs
2002-12-16 9:40 ` Andrew Morton
2002-12-16 18:52 ` Justin T. Gibbs
2002-12-16 19:03 ` Christoph Hellwig
2002-12-16 19:08 ` Andrew Morton
2002-12-16 19:26 ` Justin T. Gibbs
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=28320000.1039983464@aslan.btc.adaptec.com \
--to=gibbs@scsiguy.com \
--cc=akpm@digeo.com \
--cc=ishikawa@yk.rim.or.jp \
--cc=linux-scsi@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