From: Phil Brutsche <phil@tux.obix.com>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: "Justin T. Gibbs" <gibbs@scsiguy.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.19, 2.4.20pre7, problem with aic7xxx driver
Date: Fri, 20 Sep 2002 14:48:56 -0500 [thread overview]
Message-ID: <3D8B7BA8.8010403@tux.obix.com> (raw)
In-Reply-To: 20020920201919.3009507f.skraw@ithnet.com
Stephan von Krawczynski wrote:
> Hello Justin, hello all,
>
> I just came across an interesting phenomenon regarding 2.4.19 / 2.4.20-pre7 and
> adaptec scsi. Scene is this:
>
> board: Asus SP97-V with Pentium 200 (non-MMX) (I know it is old)
> controllers tried: adaptec 29160, 29160N, 2940 U2W
> kernel: 2.4.18-SuSE (distribution 8.0), 2.4.19, 2.4.20-pre7
>
> From all possible configurations of the above the following work:
>
> kernel 2.4.18-SuSE: with all controllers
> kernel 2.4.19 : only with 2940 U2W
> kernel 2.4.20-pre7: only with 2040 U2W
The aic7xxx driver works like a champ here in 2.4.17 (vanilla and with
rmap-11c), vanilla 2.4.19, and early vanilla 2.5.x (last I used was 2.5.9).
This is a 29160 (the 64-bit dual-channel card, not the 19160 or 29160N)
controller on a MSI 694D-Pro motherboard - dual 1GHz PIIIs.
Phil
next prev parent reply other threads:[~2002-09-20 19:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-20 5:28 2.4.20pre7, aic7xxx-6.2.8: Panic: HOST_MSG_LOOP with invalid SCB 0 Ville Herva
2002-09-20 15:37 ` Justin T. Gibbs
2002-09-20 18:19 ` 2.4.19, 2.4.20pre7, problem with aic7xxx driver Stephan von Krawczynski
2002-09-20 19:48 ` Phil Brutsche [this message]
2002-09-20 19:56 ` Stephan von Krawczynski
2002-09-23 15:28 ` 2.4.20pre7, aic7xxx-6.2.8: Panic: HOST_MSG_LOOP with invalid SCB 0 Marcelo Tosatti
2002-09-23 17:35 ` Justin T. Gibbs
2002-09-23 16:54 ` Marcelo Tosatti
2002-09-23 6:35 ` Benjamin Herrenschmidt
2002-09-23 21:43 ` Justin T. Gibbs
2002-09-23 7:15 ` 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=3D8B7BA8.8010403@tux.obix.com \
--to=phil@tux.obix.com \
--cc=gibbs@scsiguy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=skraw@ithnet.com \
/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).