LKML Archive on
help / color / mirror / Atom feed
From: Jesse Pollard <>
To: "Timothy Miller" <>,
Subject: Re: [OT] Linux stability despite unstable hardware
Date: Mon, 24 May 2004 10:10:19 -0500	[thread overview]
Message-ID: <04052410101900.02297@tabby> (raw)
In-Reply-To: <>

On Friday 21 May 2004 16:57, Timothy Miller wrote:
> I have had some issues recently with memory errors when using aggressive
> memory timings.  Although memory tests pass fine, gcc would tend to crash
> and would generate incorrect code when compiling other things. Gcc couldn't
> even build itself properly under those conditions.
> The really interesting thing is that the Linux kernel was totally
> unaffected.  Compiling the Linux kernel is often thought of as a stressful
> thing for a system, yet compiling a kernel with a broken gcc on a system
> with intermittent memory errors goes through error free, and the kernel is
> 100% stable when running.
> But until the memory errors were fixed, things like KDE wouldn't build
> without gcc crashing.
> So, what is it about Linux that makes it build properly with a broken GCC
> and run perfectly despite memory errors?

Been there, seen that too.

I think it has to do with smaller files. This reduces the memory pressure and
the power requirements of the overall system. Once the compiler gets loaded in
memory, it stayes there, small files (without too many includes) keep the
buffer requirements down, and reuses memory that may be better.

I fixed mine by just treating everything as the next lower grade memory 
(switched the BIOS from 60ns to 70ns). I didn't even see a significant
performance reduction either.

  parent reply	other threads:[~2004-05-24 15:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-21 21:57 Timothy Miller
2004-05-22  0:55 ` Rob Couto
2004-05-22  4:43 ` Horst von Brand
2004-05-22  6:12   ` Steve Dover
2004-05-22 17:27 ` Bryan Andersen
2004-05-24 15:10 ` Jesse Pollard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-05-21 18:04 Timothy Miller
2004-05-22 22:46 ` Andrew Walrond

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=04052410101900.02297@tabby \ \ \ \ \
    --subject='Re: [OT] Linux stability despite unstable hardware' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).