From: David Mosberger <davidm@napali.hpl.hp.com>
To: Matthias Fouquet-Lapar <mfl@kernel.paris.sgi.com>
Cc: davidm@hpl.hp.com, Andi Kleen <ak@suse.de>,
davidm@napali.hpl.hp.com, iod00d@hp.com,
ishii.hironobu@jp.fujitsu.com, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org
Subject: Re: [RFC/PATCH, 1/4] readX_check() performance evaluation
Date: Thu, 29 Jan 2004 21:09:13 +0000 [thread overview]
Message-ID: <16409.30329.336793.50051@napali.hpl.hp.com> (raw)
In-Reply-To: <200401292016.i0TKGraI034387@mtv-vpn-hw-mfl-2.corp.sgi.com>
>>>>> On Thu, 29 Jan 2004 21:16:52 +0100 ("CET), Matthias Fouquet-Lapar <mfl@kernel.paris.sgi.com> said:
Matthias> We have done a rather large study with DIMMs that had SBEs
Matthias> I should have been more precice. We used field returned
Matthias> parts which had reported SBEs and had been exchanged in
Matthias> the field. Our goal was to see if any of these parts
Matthias> "de-generate" over time. Most of these parts had hard
Matthias> single bit failures in one or more locations.
Ah, that's more interesting, agreed.
Matthias> As I said, we didn't find evidence that even hard SBEs
Matthias> turn into a multiple bit error.
But you were changing the operating environment of the chip, so I
wouldn't draw too strong of a conclusion. Or was the reason for the
hard SBEs known and it was determined that the operating environment
was not a factor in triggering them?
--david
next prev parent reply other threads:[~2004-01-29 21:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 1:54 [RFC/PATCH, 1/4] readX_check() performance evaluation Hironobu Ishii
2004-01-28 17:20 ` Grant Grundler
2004-01-28 17:41 ` Andi Kleen
2004-01-28 18:31 ` David Mosberger
2004-01-28 18:52 ` Andi Kleen
2004-01-28 19:24 ` David Mosberger
2004-01-28 19:39 ` Andi Kleen
2004-01-28 19:48 ` David Mosberger
2004-01-28 20:01 ` Andi Kleen
2004-01-28 23:35 ` David Mosberger
2004-02-16 10:19 ` Pavel Machek
2004-01-28 19:09 ` Grant Grundler
2004-01-28 19:17 ` Andi Kleen
2004-01-28 21:14 ` Grant Grundler
2004-01-28 21:39 ` Andi Kleen
2004-01-29 8:23 ` Matthias Fouquet-Lapar
2004-01-29 19:28 ` David Mosberger
2004-01-29 20:16 ` Matthias Fouquet-Lapar
2004-01-29 21:09 ` David Mosberger [this message]
2004-01-29 22:20 ` Matthias Fouquet-Lapar
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=16409.30329.336793.50051@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=ak@suse.de \
--cc=davidm@hpl.hp.com \
--cc=iod00d@hp.com \
--cc=ishii.hironobu@jp.fujitsu.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfl@kernel.paris.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