Hi Riley et al...
WRT 2.2.5-22....I apologize for the silly question, but I'm confused. I've
installed 2.2.5-15 on two separate systems both with the aic7xxx driver
installed. One's an SMP system(Dell PowerEdge 2300 2x450MHz with aic7890 &
a couple of AHA-2944UW's, 256MB, 2x 4.3GB)and the other is a UP system (NEC
ExpressServer 5800 120Ra2 500MHz with 128MB, 8.7GB SCSI drive, ncr53x896 &
3 AHA-2944UW). I need to at least attempt to use 2.2.5 of some flavor for
a test I'm doing.
What pieces of the 2.2.5-22 do I need? Do I need the smp (for the SMP
system obviously), source, and kernel-2.2.5-22.i686.rpm or just one of
those pieces?
Please let me know if you need more information and TIA.
Heather
-------------
Original Text
From: "Riley Williams" <rhw@MemAlpha.CX>, on 7/16/99 2:13 PM:
To: smtp@Eng@EMCHOP1["Jeff" <schaller@southwind.net>]
Cc: smtp@Eng@EMCHOP1[<linux-kernel@vger.rutgers.edu>]
Hi Jeff.
> Recently found time to upgrade to Redhat's 2.2.5-15 kernel; it
> works fine. Got the corresponding source RPM and tried to
> compile my own -- compile went fine. Problem is, booting with
> the new kernel puts me in a SCSI loop.
You are aware that RedHat issued a 2.2.5-22 kernel over a month ago?
According to RedHat's errata page, this was to fix as vulnerability in
the kernel, but I can state that the -22 kernel is far more stable on
my systems than the -15 kernel was...
> Whereas the stock kernel gives something like this on boot:
> scsi0: blah blah
> scsi0: blah blah
> scsi0: blah blah
> scsi1: more stuff
> scsi1: more stuff
> scsi1: more stuff
> which is correct (aha3940 dual-channel controller), the kernel I
> compiled does this:
> scsi0: blah blah
> scsi0: blah blah
> scsi0: blah blah
> scsi bus timeout
> [repeat]
> In other words, it never sees scsi1. I didn't change the SCSI
> setup between the two kernels. The only thing I can think of is
> that I added a sound card (ISA). I'm not sure which SCSI
> options Redhat picked for the aic7xxx driver, but I compiled it
> into the kernel (Y), left TCQ at 8, upped the reset timeout to
> 15 seconds (so I could read the above messages), and said (N) to
> the extra debugging info.
> My first thought was that the aic7xxx driver was buggy in 2.2.5;
> the other possibility that I can come with is that the sound
> card is stealing the controller's 2nd IRQ. The thing with that
> is that the stock kernel boots just fine.
> Should I just get a later 2.2 kernel?
That's probably a good idea anyway - there's quite a few bugs fixed
between 2.2.5 and 2.2.10 so you're probably better off jumping
straight to the latter...
> If the precise error messages would be helpful, let me know, and
> I'll write them down when I get home.
They usually are...
> Thanks for any ideas :)
Best wishes from Riley.
+----------------------------------------------------------------------+
| There is something frustrating about the quality and speed of Linux |
| development, ie., the quality is too high and the speed is too high, |
| in other words, I can implement this XXXX feature, but I bet someone |
| else has already done so and is just about to release their patch. |
+----------------------------------------------------------------------+
* ftp://ftp.MemAlpha.cx/pub/rhw/Linux
* http://www.MemAlpha.cx/kernel.versions.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/