On Wed, 24 Jan 2007 22:37:20 GMT, Chris Rankin said: > --- Mark Rustad <[email protected]> wrote: > > Well, do you have ECC memory? If not, it is at least possible that > > that the solar flares that occurred last month may have affected your > > system. > > I am going to assume that you are being facaetious, because it would be the rarified pinnacle of > supreme arrogance to suggest that a cosmic ray event is a more likely explanation than a bug in > the kernel. Sorry for the late reply, but cosmic ray events (actually, self-induced alpha particle events from decays within the chipset itself) *are* a likely explanation: http://stason.org/TULARC/pc/pc_hardware_faq/2_20_What_does_parity_ECC_memory_protect_the_system_from.html Most important take-away here: "With 100 million computers in use today, we should expect roughly 6 million single bit errors per year. Computer hardware and software companies must receive thousands of "side effect" bug reports and support calls due to memory errors alone. The costs of NOT including parity memory must be huge!"
Attachment:
pgpufahSRRm1l.pgp
Description: PGP signature
- Follow-Ups:
- Re: 2.6.18-stable release plans?
- From: Jon Masters <[email protected]>
- Re: 2.6.18-stable release plans?
- References:
- Re: 2.6.18-stable release plans?
- From: Chris Rankin <[email protected]>
- Re: 2.6.18-stable release plans?
- Prev by Date: Re: [Fastboot] [PATCH] kexec: Fix CONFIG_SMP=n compilation (ia64)
- Next by Date: Re: [RFC 0/8] Cpuset aware writeback
- Previous by thread: Re: 2.6.18-stable release plans?
- Next by thread: Re: 2.6.18-stable release plans?
- Index(es):