LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Mark Rustad <mrustad@gmail.com>
To: Chris Rankin <rankincj@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-stable release plans?
Date: Wed, 24 Jan 2007 10:28:43 -0600	[thread overview]
Message-ID: <4238B011-A417-41DE-8998-01BAAA484486@gmail.com> (raw)
In-Reply-To: <964414.64865.qm@web52908.mail.yahoo.com>

On Jan 24, 2007, at 9:53 AM, Chris Rankin wrote:

>>> But MY kernel is clearly untainted.
>>> So what other explanation is there apart from a kernel bug?
>
>> If it's me you're asking: I don't know (overheating, cosmic  
>> rays, ...)
>
> I suppose what I'm *really* asking is what the basis is for  
> assuming that this *isn't* a kernel
> bug and can therefore be safely ignored, seeing as the oops is  
> real, the hardware is fine and the
> kernel is untainted? That seems to cover the bases from where I'm  
> sitting.
>
> Cheers,
> Chris
>
> P.S. No micro-heatwaves have occurred here, either. Do we all need  
> to install muon detectors in
> our homes before reporting bugs now, so that we can exclude cosmic  
> ray events too?

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. There were three X-class solar flares in the month of  
December. Even if you have ECC memory, it is still possible to suffer  
data corruption because many BIOSes do not turn on bus parity error  
detection. And are the memories in your disk drive controllers ECC or  
parity protected? I wouldn't bet on it...

All too often, modern PCs are data corruption accidents waiting to  
happen.

-- 
Mark Rustad, MRustad@mac.com



  parent reply	other threads:[~2007-01-24 16:28 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-24 15:53 Chris Rankin
2007-01-24 16:12 ` Hugh Dickins
2007-01-24 17:33   ` Chris Rankin
2007-01-24 16:28 ` Mark Rustad [this message]
2007-01-24 22:37   ` Chris Rankin
2007-01-24 23:11     ` Alan
2007-01-24 23:05       ` Chris Rankin
2007-01-24 23:32       ` Mark Rustad
2007-01-24 23:45         ` Chris Rankin
2007-01-25  1:00           ` Ken Moffat
2007-01-25  9:16             ` Chris Rankin
2007-01-25 19:36               ` Ken Moffat
2007-01-26 13:02                 ` Chris Rankin
2007-01-25 23:26               ` Alistair John Strachan
2007-01-25  3:05           ` Mark Rustad
2007-01-25 21:04       ` Matt Mackall
2007-02-02  4:02     ` Valdis.Kletnieks
2007-02-02  6:47       ` Jon Masters
2007-02-02  8:17         ` Valdis.Kletnieks
     [not found] <BC3E207A-1A56-4032-9619-910E80281E9C@gmail.com>
2007-01-25  8:51 ` Chris Rankin
  -- strict thread matches above, loose matches on Subject: below --
2007-01-24 15:06 Chris Rankin
2007-01-24 15:40 ` Hugh Dickins
2007-01-24 13:30 Chris Rankin
2007-01-24 14:37 ` Hugh Dickins
2007-01-22 22:13 Chuck Ebbert
2007-01-23  0:23 ` Jesper Juhl
2007-01-23 20:33   ` Chuck Ebbert
2007-01-23 20:56     ` Adrian Bunk
2007-01-24  4:50   ` Daniel Barkalow

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=4238B011-A417-41DE-8998-01BAAA484486@gmail.com \
    --to=mrustad@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rankincj@yahoo.com \
    --subject='Re: 2.6.18-stable release plans?' \
    /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).