From: "Chris Friesen" <cfriesen@nortel.com>
To: Brian Gordon <legerde@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Aerospace and linux
Date: Thu, 10 Jun 2010 12:27:07 -0600 [thread overview]
Message-ID: <4C112E7B.1040101@nortel.com> (raw)
In-Reply-To: <AANLkTimrZvKyh6zYnUg2xzDVBVr5NxqtJhxZ42AVhkVI@mail.gmail.com>
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.
At higher abstraction levels you can checksum the data being stored and
validate it when you access it.
Some of the errors are "soft" and can be corrected, others are "hard"
and uncorrectable. If you get enough "soft" errors in a short enough
time it may be desirable to treat it as a "hard" error and reset.
> Thank you to anyone for any pointers on where I can look to learn
> more about detecting SEU in linux.
You might start by taking a look at the "edac" code in the kernel.
Linux in general doesn't normally enable all the fault detection code,
so you may need to start looking at datasheets.
Chris
--
The author works for GENBAND Corporation (GENBAND) who is solely
responsible for this email and its contents. All enquiries regarding
this email should be addressed to GENBAND. Nortel has provided the use
of the nortel.com domain to GENBAND in connection with this email solely
for the purpose of connectivity and Nortel Networks Inc. has no
liability for the email or its contents. GENBAND's web site is
http://www.genband.com
next prev parent reply other threads:[~2010-06-10 18:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 17:29 Aerospace and linux 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=4C112E7B.1040101@nortel.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.