mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tim Wright <timw@splhi.com>
To: "Dr. Kelsey Hudson" <kernel@blackhole.compendium-tech.com>
Cc: "Matilainen Panu (NRC/Helsinki)" <panu.matilainen@nokia.com>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.4.x very unstable on 8-way IBM 8500R
Date: Thu, 1 Mar 2001 18:48:43 -0800	[thread overview]
Message-ID: <20010301184843.B5065@kochanski.internal.splhi.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0103011229500.23756-100000@godzilla.research.nokia.com> <Pine.LNX.4.21.0103011701360.8542-100000@sol.compendium-tech.com>
In-Reply-To: <Pine.LNX.4.21.0103011701360.8542-100000@sol.compendium-tech.com>; from kernel@blackhole.compendium-tech.com on Thu, Mar 01, 2001 at 05:04:09PM -0800

On Thu, Mar 01, 2001 at 05:04:09PM -0800, Dr. Kelsey Hudson wrote:
> On Thu, 1 Mar 2001, Matilainen Panu (NRC/Helsinki) wrote:
> 
> > I've been playing around with 8-way IBM8500R (8x700MHz Xeon) with 4.5GB
> > memory & AIC7xxx SCSI-controller. It's perfectly stable with 2.2-kernel
> > (from Red Hat 7) but very erratic on all 2.4-kernels I've tried it with
> > (2.4.[012], compiled both with egcs and RH7's gcc-2.96, both share the
> 
> Under redhat 7 you should use kgcc to compile the kernel, since gcc2.96 is
> inherently broken(*). 
> 

For the umpteenth time, no it isn't. There are serious bugs in the shipped
version of gcc in RedHat 7.0, but they are fixed by applying the update.
The reason for supplying kgcc is to allow building a 2.2 kernel, because of
bugs in the kernel, NOT the compiler.

> > same symptoms). It did have a ServeRAID controller too but IBM suggested
> > we take it out since 4500R also had problems with it on 2.4 but it didn't
> > make any difference at all. Also tried to turn off highmem support but
> > didn't make difference either.
> 
> (*)  redhat chose to ship an experimental compiler with this release of
>      the distribution that has a great many bugs. to ensure proper kernel
>      compillation another proven version of gcc was included, but called
>      kgcc instead. You should always use this to compile your kernels
>      under redhat 7 until the newer version of gcc is released.
> 

No. Provided you grab the update, you can build the 2.4 kernel perfectly
happily using the RedHat gcc snapshot. I'm running it successfully on a number
of machines. The issue with 2.4 on certain Netfinities is a bad interaction
between the NMI watchdog code and the systems management card. Changing
compilers makes no difference.

Tim

-- 
Tim Wright - timw@splhi.com or timw@aracnet.com or twright@us.ibm.com
IBM Linux Technology Center, Beaverton, Oregon
Interested in Linux scalability ? Look at http://lse.sourceforge.net/
"Nobody ever said I was charming, they said "Rimmer, you're a git!"" RD VI

  parent reply	other threads:[~2001-03-02  2:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-01 11:18 Matilainen Panu (NRC/Helsinki)
2001-03-02  1:04 ` Dr. Kelsey Hudson
2001-03-02  1:34   ` Alan Cox
2001-03-02  8:44     ` Matilainen Panu
2001-03-02  2:00   ` J Sloan
2001-03-02  2:48   ` Tim Wright [this message]
2001-03-02  3:59   ` Mike A. Harris
     [not found] <3A9E3F00.E5667AAC@uow.edu.au>
2001-03-01 13:30 ` Matilainen Panu (NRC/Helsinki)
2001-03-02  2:43   ` Tim Wright

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=20010301184843.B5065@kochanski.internal.splhi.com \
    --to=timw@splhi.com \
    --cc=kernel@blackhole.compendium-tech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=panu.matilainen@nokia.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

all inboxes | Powered by JetHome®