All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bryan Andersen <bryan@nerdvest.com>
To: Timothy Miller <theosib@hotmail.com>
Cc: linux-kernel@vger.kernel.org, miller@techsource.com
Subject: Re: [OT] Linux stability despite unstable hardware
Date: Sat, 22 May 2004 12:27:55 -0500	[thread overview]
Message-ID: <40AF8D9B.2080904@nerdvest.com> (raw)
In-Reply-To: <BAY1-F135u0T4Dk5Je6000264da@hotmail.com>

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 [OT] Linux stability despite unstable hardware 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:
  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=40AF8D9B.2080904@nerdvest.com \
    --to=bryan@nerdvest.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miller@techsource.com \
    --cc=theosib@hotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.