LKML Archive on
help / color / mirror / Atom feed
From: Bryan Andersen <>
To: Timothy Miller <>
Subject: Re: [OT] Linux stability despite unstable hardware
Date: Sat, 22 May 2004 12:27:55 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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?

It could just be heat buildup in an critical area when under sustained 
heavy load.  It may take a while for enough heat to build up to cause 
problems.  I just recently found one of these.  It would take 4-6 hours 
of heavy intensive processing before an error would happen.  I placed a 
fan pointing at the motherboard chipset and memory to keep them cooler 
and the problem seams to have gone away.

For testing I wrote a script that kept compiling the kernel again and 
agian in a while(true) loop.  Effectively a repeat until crash loop. 
For each compile it saved the stdout/stderr output and diffed it against 
the first run.  Any differnces were flagged for checking latter.

- Bryan

  parent reply	other threads:[~2004-05-22 17:28 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 [this message]
2004-05-24 15:10 ` Jesse Pollard
  -- 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 \ \ \ \ \ \
    --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).