From: "Prasanna S. Panchamukhi" <prasanna.panchamukhi@riverbed.com>
To: Borislav Petkov <bp@amd64.org>
Cc: Rob Becker <Rob.Becker@riverbed.com>,
"bluesmoke-devel@lists.sourceforge.net"
<bluesmoke-devel@lists.sourceforge.net>,
Arthur Jones <Arthur.Jones@riverbed.com>,
"dougthompson@xmission.com" <dougthompson@xmission.com>
Subject: Re: EDAC linux-2.6.34-rc5 non correctable errors not reported on AMD64 opteron
Date: Thu, 6 May 2010 16:56:29 -0700 [thread overview]
Message-ID: <20100506235628.GA12811@ppanchamukhi> (raw)
In-Reply-To: <20100430110023.GA6554@aftab>
Hi Boris,
On Fri, Apr 30, 2010 at 04:00:23AM -0700, Borislav Petkov wrote:
> Hi Prasanna, Keith,
>
> from what I could see, you're doing the injection correctly and
> the injection code accesses the right bits so that should work ok.
> What happens is rather what Keith explained in detail with the only
> correction that it is not the BIOS but the hardware itself that takes
> action to prevent the system from damaging the data.
>
> See, double-bit errors are deemed uncorrectable and your machine
> syncfloods¹, i.e. it terminates further stale data propagation.
> Therefore, no software gets to run, not even the machine check handler
> (not to mention the clumsy EDAC error polling mechanism). And that's
> why you don't get the errors reported; OTOH, if you want to test the
> amd64_edac driver, injecting single-bit errors should work and you can
> report to me any issues you encounter.
Is there a way to disable Sync Flood on uncorrectable errors and
instead generate MCE.
Thanks
Prasanna
>
> Hope that helps.
>
> Thanks.
>
>
>
> ¹ See the section on Sync Flooding in the Hyper Transport spec if you
> want to know more details on that.
>
> --
> Regards/Gruss,
> Boris.
>
> --
> Advanced Micro Devices, Inc.
> Operating Systems Research Center
------------------------------------------------------------------------------
next prev parent reply other threads:[~2010-05-06 23:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 18:30 EDAC linux-2.6.34-rc5 non correctable errors not reported on AMD64 opteron Prasanna S. Panchamukhi
2010-04-29 22:13 ` Keith Mannthey
2010-04-29 22:31 ` Prasanna S. Panchamukhi
2010-04-29 23:18 ` Keith Mannthey
2010-04-30 0:12 ` Prasanna S. Panchamukhi
2010-04-30 0:38 ` Keith Mannthey
2010-04-30 11:00 ` Borislav Petkov
2010-05-05 1:40 ` Prasanna S. Panchamukhi
2010-05-06 23:56 ` Prasanna S. Panchamukhi [this message]
2010-04-30 14:08 ` Ben Woodard
-- strict thread matches above, loose matches on Subject: below --
2010-04-28 17:14 EDAC: Linux-2.6.34-rc5 non correctable errors not reported on AMD64 Opteron Prasanna Panchamukhi
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=20100506235628.GA12811@ppanchamukhi \
--to=prasanna.panchamukhi@riverbed.com \
--cc=Arthur.Jones@riverbed.com \
--cc=Rob.Becker@riverbed.com \
--cc=bluesmoke-devel@lists.sourceforge.net \
--cc=bp@amd64.org \
--cc=dougthompson@xmission.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