From: Mark Rustad <mrustad@gmail.com>
To: Chris Rankin <rankincj@yahoo.com>
Cc: Alan <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-stable release plans?
Date: Wed, 24 Jan 2007 21:05:04 -0600 [thread overview]
Message-ID: <973C1FB2-7B4D-4A46-B5DA-4B04AB3444F6@gmail.com> (raw)
In-Reply-To: <559149.89346.qm@web52906.mail.yahoo.com>
On Jan 24, 2007, at 5:45 PM, Chris Rankin wrote:
>> --- Mark Rustad <mrustad@gmail.com> wrote:
>> Exactly. Halting use of a version of the kernel based on a single
>> incident provides no insight to the source of the problem. It could
>> be anything...
>
> There is a world of difference between a polite request for more
> information (although I gave you
> everything I had), and fobbing someone off with a story about
> cosmic rays.
I'm sorry. I didn't mean to imply anything like that. I just happened
to notice that the date of the bug report appeared to correlate
pretty well with one of the solar flare events last month. I was
really trying to share some information that just conceivably might
have been related, based on the earlier messages in this thread
regarding memory errors.
I don't normally follow solar activity. I have been looking into some
system failures that happened last month. The systems had been
running with all bus error detection enabled – the hardware set to
spontaneously reboot on any uncorrectable error. Since our systems
are redundant, performing a reset simply means that the redundant
partner will take over, so the reset is the best way to be certain
that there is no data corruption. I eventually recalled a radio
report last month about a coronal mass ejection on the sun and how
things might be disrupted here. I checked out www.spaceweather.com
and found that December was a very active month, with three separate
X-class flares. I have no way to conclude that the failures that I
have seen were influenced by events on the sun, but it seems
possible. Compared to our systems, most PCs and even much server-
class hardware systems are likely to corrupt a bit just keep on going.
We'll never know if any of these things were correlated with the
solar flares because they all seem to be one-off failures. I do find
it interesting though. Our systems seem to be doing statistically
better this month. What do you think?
--
Mark Rustad, MRustad@mac.com
next prev parent reply other threads:[~2007-01-25 3:05 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
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 [this message]
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=973C1FB2-7B4D-4A46-B5DA-4B04AB3444F6@gmail.com \
--to=mrustad@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rankincj@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®