LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Timothy Miller" <theosib@hotmail.com>
To: linux-kernel@vger.kernel.org
Cc: miller@techsource.com
Subject: [OT] Linux stability despite unstable hardware
Date: Fri, 21 May 2004 17:57:09 -0400 [thread overview]
Message-ID: <BAY1-F135u0T4Dk5Je6000264da@hotmail.com> (raw)
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?
_________________________________________________________________
Watch LIVE baseball games on your computer with MLB.TV, included with MSN
Premium! http://join.msn.click-url.com/go/onm00200439ave/direct/01/
next reply other threads:[~2004-05-21 21:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-21 21:57 Timothy Miller [this message]
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
-- 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=BAY1-F135u0T4Dk5Je6000264da@hotmail.com \
--to=theosib@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.com \
--subject='Re: [OT] Linux stability despite unstable hardware' \
/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
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).