From: Disconnect <lkml@sigkill.net>
To: lkml <linux-kernel@vger.kernel.org>
Subject: RE: Aix7xxx unstable in 2.4.21-rc2? (RE: Linux 2.4.21-rc2)
Date: 23 May 2003 11:20:02 -0400 [thread overview]
Message-ID: <1053703202.16126.25.camel@slappy> (raw)
In-Reply-To: <002c01c32108$1e4bb980$020b10ac@pitzeier.priv.at>
On Fri, 2003-05-23 at 04:48, Oliver Pitzeier wrote:
> [ ... ]
>
> OK. So now I have to say: _Don't_ use 2.4.20-rc* if you have a aic7xxx. You can
> use 2.4.19 and maybe 2.4.20(?).
2.4.20 is fine for me here... (Its 2.4.20 with the AA highmem-as-lowmem
patch and 1G of ram):
$ head -n 2 /proc/scsi/aic7xxx/[01];uname -a;uptime
==> /proc/scsi/aic7xxx/0 <==
Adaptec AIC7xxx driver version: 6.2.8
aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs
==> /proc/scsi/aic7xxx/1 <==
Adaptec AIC7xxx driver version: 6.2.8
aic7880: Ultra Wide Channel B, SCSI Id=7, 16/253 SCBs
Linux oscar 2.4.20 #1 Sun Mar 2 13:09:09 EST 2003 i686 unknown unknown
GNU/Linux
11:20:24 up 53 days, 19:33, 30 users, load average: 0.14, 0.19, 0.20
--
Disconnect <lkml@sigkill.net>
next prev parent reply other threads:[~2003-05-23 15:06 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.m0c9ksl.1ijqph1@ifi.uio.no>
2003-05-09 6:55 ` Linux 2.4.21-rc2 Gregoire Favre
2003-05-09 7:06 ` Anders Karlsson
2003-05-09 7:07 ` Marc-Christian Petersen
2003-05-09 7:31 ` Gregoire Favre
2003-05-09 7:35 ` Marc-Christian Petersen
2003-05-09 7:39 ` Gregoire Favre
2003-05-11 19:08 ` Sven Krohlas
2003-05-22 15:19 ` Aix7xxx unstable in 2.4.21-rc2? (RE: Linux 2.4.21-rc2) Oliver Pitzeier
2003-05-22 15:31 ` Marc-Christian Petersen
2003-05-22 21:33 ` Scott McDermott
2003-05-23 8:45 ` Oliver Pitzeier
2003-05-23 17:52 ` Marcelo Tosatti
2003-05-23 20:19 ` Willy Tarreau
2003-05-23 22:58 ` Scott McDermott
2003-05-26 18:51 ` Marcelo Tosatti
2003-05-23 7:17 ` Sven Krohlas
2003-05-26 12:54 ` Matthias Andree
2003-05-23 7:14 ` Sven Krohlas
2003-05-23 8:48 ` Oliver Pitzeier
2003-05-23 9:26 ` Sven Krohlas
2003-05-23 9:32 ` Oliver Pitzeier
2003-05-23 11:33 ` Stephan von Krawczynski
2003-05-24 0:18 ` J.A. Magallon
2003-05-23 15:20 ` Disconnect [this message]
2003-05-23 23:29 James Bottomley
2003-05-24 6:43 ` Willy Tarreau
2003-05-24 14:36 ` James Bottomley
2003-05-24 14:51 ` Justin T. Gibbs
2003-05-24 15:55 ` James Bottomley
2003-05-28 23:08 ` Bill Davidsen
2003-05-26 4:21 ` David S. Miller
2003-05-26 4:25 ` David S. Miller
2003-05-26 8:47 ` Marc-Christian Petersen
2003-05-26 17:58 ` Marcelo Tosatti
2003-05-26 18:42 ` Marcelo Tosatti
2003-05-26 21:29 ` Willy Tarreau
2003-05-26 21:35 ` Marcelo Tosatti
2003-05-27 4:21 ` Willy Tarreau
2003-05-26 22:16 ` Carl-Daniel Hailfinger
2003-05-26 22:18 ` Marc-Christian Petersen
2003-05-26 22:33 ` Carl-Daniel Hailfinger
2003-05-27 0:35 ` Alan Cox
2003-05-27 4:39 ` Willy Tarreau
2003-05-27 4:47 ` Marcelo Tosatti
2003-05-27 5:00 ` Willy Tarreau
2003-05-27 8:38 ` Oliver Pitzeier
2003-05-27 8:44 ` Marc-Christian Petersen
2003-05-27 9:44 ` Oliver Pitzeier
2003-05-27 20:01 ` Marcelo Tosatti
2003-06-23 7:57 ` Oliver Pitzeier
[not found] <20030523085010$1ac2@gated-at.bofh.it>
[not found] ` <20030523180021$109a@gated-at.bofh.it>
[not found] ` <20030523203017$0e66@gated-at.bofh.it>
2003-05-24 11:46 ` Pascal Schmidt
2003-05-24 20:06 ` Nicholas Wourms
2003-05-28 23:11 ` Bill Davidsen
2003-05-26 21:53 john
2003-05-27 9:12 Eric Valette
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=1053703202.16126.25.camel@slappy \
--to=lkml@sigkill.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;
as well as URLs for NNTP newsgroup(s).