linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joel Schopp <jschopp@austin.ibm.com>
To: Russ Anderson <rja@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RCF] Linux memory error handling
Date: Wed, 15 Jun 2005 15:42:00 -0500	[thread overview]
Message-ID: <42B09298.4000600@austin.ibm.com> (raw)
In-Reply-To: <200506151430.j5FEUD7J1393603@clink.americas.sgi.com>

> 	A common question is whether single bit (corrected) errors will 
> 	turn into double bit (uncorrected) errors.  The answer is it
> 	depends on the underlying cause of the memory error.  There are
> 	some errors that show up as single bits, especially transient 
> 	and soft errors, that do not degrade over time.  There are other
> 	failures that do degrade over time.

This sounds like one of our primary motivations for working on memory 
hotplug remove.  Detection of recoverable errors that degrade to 
unrecoverable errors, but don't because we remove the memory before it 
gets that far.

Much PPC64 hardware/firmware already supports this detection.


  parent reply	other threads:[~2005-06-15 20:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-15 14:30 [RCF] Linux memory error handling Russ Anderson
2005-06-15 15:08 ` Andi Kleen
2005-06-15 16:36   ` Russ Anderson
2005-06-15 15:26 ` Maciej W. Rozycki
2005-06-15 19:46   ` Russell King
2005-06-15 20:28     ` [RFC] " Russ Anderson
2005-06-15 20:45       ` Dave Hansen
2005-06-15 21:27         ` Russ Anderson
2005-06-15 21:33           ` Dave Hansen
2005-06-20 20:42             ` Russ Anderson
2005-06-20 21:07               ` Dave Hansen
2005-06-15 22:09   ` Russ Anderson
2005-06-16 19:42     ` Maciej W. Rozycki
2005-06-16  1:03   ` [RCF] " Ross Biro
2005-06-15 20:42 ` Joel Schopp [this message]
2005-06-16  2:54 ` Wang, Zhenyu

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=42B09298.4000600@austin.ibm.com \
    --to=jschopp@austin.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rja@sgi.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;
as well as URLs for NNTP newsgroup(s).