From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Chris Friesen <cfriesen@nortel.com>
Cc: Brian Gordon <legerde@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Aerospace and linux
Date: Fri, 11 Jun 2010 11:37:17 -0300 [thread overview]
Message-ID: <20100611143717.GF28084@khazad-dum.debian.net> (raw)
In-Reply-To: <4C112E7B.1040101@nortel.com>
On Thu, 10 Jun 2010, Chris Friesen wrote:
> On 06/10/2010 11:29 AM, Brian Gordon wrote:
> > When these SEU can be detected some action may be taken to improve
> > the behaviour of the system (log a fault and reset in order to
> > refresh things from scratch?). So the first question becomes how to
> > detect an SEU.
>
> I do work in telco stuff. We use ECC RAM, turn on ECC/parity on the
> various buses, enable error-checking in the hardware, etc.
Let's not forget that the hardware better have unassisted scrubbing
(rewrite cells where an CE is detected), because we don't scrub when
we are notified of a CE.
Background scrubbing might also be something to look for (run over all
RAM over a large period of time, to catch dormant CEs and fix them
before they become UEs).
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2010-06-11 14:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 17:29 Brian Gordon
2010-06-10 18:23 ` Andi Kleen
2010-06-10 18:38 ` Brian Gordon
2010-06-10 18:46 ` Chris Friesen
2010-06-10 19:14 ` Brian Gordon
2010-06-10 18:48 ` Andi Kleen
2010-06-13 8:51 ` Borislav Petkov
2010-06-10 18:27 ` Chris Friesen
2010-06-10 18:42 ` Brian Gordon
2010-06-10 19:23 ` Massimiliano Galanti
2010-06-10 19:37 ` Brian Gordon
2010-06-10 19:42 ` Brian Gordon
2010-06-10 19:52 ` Massimiliano Galanti
2010-06-10 20:12 ` Brian Gordon
2010-06-10 19:59 ` Massimiliano Galanti
2010-06-11 14:37 ` Henrique de Moraes Holschuh [this message]
2010-06-13 15:26 Denys Fedorysychenko
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=20100611143717.GF28084@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=cfriesen@nortel.com \
--cc=legerde@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome