From: Doug Ledford <dledford@redhat.com>
To: Andreas Steinmetz <ast@domdv.de>
Cc: Frank Schneider <\"\"SPATZ1\"@t-online.de>,
linux-kernel@vger.kernel.org, Holger Kiehl <Holger.Kiehl@dwd.de>
Subject: Re: AIC7xxx errors in 2.2.19 but not in 2.2.18
Date: Sat, 15 Sep 2001 11:37:52 -0400 [thread overview]
Message-ID: <3BA375D0.6020903@redhat.com> (raw)
In-Reply-To: <XFMail.20010914153738.ast@domdv.de>
Andreas Steinmetz wrote:
> Hi,
> 2.2.19 only has the 'old' driver. The 'raid/scsi new' problem is a notifier
> chain sequence problem that seems to have been taken care of now.
> What I do see here may be a coincidence of kernel upgrade and a faulty drive.
> Some snippets of 2.2.19 log messages of a faulty drive below.
>
> May 2 03:33:07 pollux kernel: (scsi1:0:1:0) Parity error during Data-In phase.
> May 2 03:33:37 pollux kernel: scsi : aborting command due to timeout : pid
> 1188263, scsi1, channel 0, id 1, lun 0 Read (10) 00 01 04 cd 97 00 00 80 00
I've seen that error a few times now with the new code in 2.2.19. I
don't have a fix for it at this time (and I probably won't since
development on that driver isn't a 'regular' thing at this point). If
the old driver in 2.2.18 worked for you, then I would copy the aic7xxx*
files from 2.2.18 into 2.2.19 and rebuild your kernel.
--
Doug Ledford <dledford@redhat.com> http://people.redhat.com/dledford
Please check my web site for aic7xxx updates/answers before
e-mailing me about problems
next prev parent reply other threads:[~2001-09-15 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-14 9:34 AIC7xxx errors in 2.2.19 but not in 2.2.18 Holger Kiehl
2001-09-14 13:11 ` Frank Schneider
2001-09-14 13:37 ` Andreas Steinmetz
2001-09-15 15:37 ` Doug Ledford [this message]
2001-09-15 15:42 ` Andreas Steinmetz
2001-09-14 13:46 ` Holger Kiehl
2001-09-14 17:12 ` Mike Fedyk
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=3BA375D0.6020903@redhat.com \
--to=dledford@redhat.com \
--cc=ast@domdv.de \
/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;
as well as URLs for NNTP newsgroup(s).