From: Wakko Warner <wakko@animx.eu.org>
To: Metod Kozelj <metod.kozelj@rzs-hm.si>
Cc: "Justin T. Gibbs" <gibbs@scsiguy.com>,
linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org
Subject: Re: 2.4.3-pre2 aic7xxx crash on alpha
Date: Thu, 8 Mar 2001 06:30:16 -0500 [thread overview]
Message-ID: <20010308063016.B1803@animx.eu.org> (raw)
In-Reply-To: <200103080445.f284jsO36939@aslan.scsiguy.com> <Pine.HPP.3.96.1010308095215.15847B-100000@hmljhp.rzs-hm.si>
In-Reply-To: <Pine.HPP.3.96.1010308095215.15847B-100000@hmljhp.rzs-hm.si>; from Metod Kozelj on Thu, Mar 08, 2001 at 10:08:32AM +0100
> > >(scsi1:A:0:0): data overrun detected in Data-out phase. Tag == 0x36.
> > >(scsi1:A:0:0): Have seen Data Phase. Length = 0. NumSGs = 0.
> >
> > As I mentioned to you the last time you brought up this problem, I
> > don't believe that this is caused by the aic7xxx driver, but the
> > aic7xxx driver may be the first to notice the corruption.
>
> I can second this somehow. I was testing 2.4.2 on SX164 alpha, same
> AHA-2940UW controller. In my case, system freezes solid if I do extensive
> reading from CD-ROM (NEC CD-ROM DRIVE:465). It happens using stock AIC7xxx
> driver (5.3.something) as well as the new (6.1.2 or something).
> I'm back to 2.2.18 using AIC7xxx v5.1.31 and everything is happy.
> This makes me believe that it must be mid-layer SCSI drivers causing
> problems.
I tried the aic driver from 2.2.17 and 18 which also lockup this system.
Noone on the list that I've seen has used an adaptec card in an alphaserver
1000a 4/266 and said anything about it.
--
Lab tests show that use of micro$oft causes cancer in lab animals
prev parent reply other threads:[~2001-03-08 11:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-08 2:09 2.4.3-pre2 aic7xxx crash on alpha Wakko Warner
2001-03-08 4:45 ` Justin T. Gibbs
2001-03-08 9:08 ` Metod Kozelj
2001-03-08 11:30 ` Wakko Warner [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=20010308063016.B1803@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=gibbs@scsiguy.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=metod.kozelj@rzs-hm.si \
/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