LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Horst von Brand <vonbrand@inf.utfsm.cl> To: "Timothy Miller" <theosib@hotmail.com> Cc: linux-kernel@vger.kernel.org, miller@techsource.com, vonbrand@inf.utfsm.cl Subject: Re: [OT] Linux stability despite unstable hardware Date: Sat, 22 May 2004 00:43:42 -0400 [thread overview] Message-ID: <200405220443.i4M4hh631517@pincoya.inf.utfsm.cl> (raw) In-Reply-To: Your message of "Fri, 21 May 2004 17:57:09 -0400." <BAY1-F135u0T4Dk5Je6000264da@hotmail.com> "Timothy Miller" <theosib@hotmail.com> said: > 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. Really? memtest86 <http://www,memtest86.com> did finish its run without errors? I'm sure they'd want to get their hands on the broken RAM... > 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. Sure enough, if the kernel lives (mostly) in unaffected memory, and furthermore doesn't bang on it quite as hard as a compiler run does (the kernel only runs for a tiny fraction of the time). -- Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
next prev parent reply other threads:[~2004-05-22 4:43 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 [this message] 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=200405220443.i4M4hh631517@pincoya.inf.utfsm.cl \ --to=vonbrand@inf.utfsm.cl \ --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: linkBe 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; as well as URLs for NNTP newsgroup(s).