[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F2DA88106@ORSMSX106.amr.corp.intel.com>
Date: Wed, 19 Jun 2013 18:19:25 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Borislav Petkov <bp@...en8.de>,
"Naveen N. Rao" <naveen.n.rao@...ux.vnet.ibm.com>
CC: "ananth@...ibm.com" <ananth@...ibm.com>,
"masbock@...ux.vnet.ibm.com" <masbock@...ux.vnet.ibm.com>,
"lcm@...ux.vnet.ibm.com" <lcm@...ux.vnet.ibm.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"Huang, Ying" <ying.huang@...el.com>
Subject: RE: [PATCH v2 2/2] mce: acpi/apei: Add a boot option to disable ff
mode for corrected errors
> Interesting, why? Why would we even need such an option? My impression
> is, if ACPI tells us FF, MCE code doesn't poll those banks anymore. So
> where do the duplicated reports come from?
The option is only disabling the Linux side of firmware first ... the BIOS
will still be doing it and generating records to feed to the OS using APEI.
So Linux may see the error in a bank and report it, and BIOS may report
the same error. Though I'd expect that to be rare as whoever saw it first
would most likely clear the bank before the other could see it.
I asked for the option because I'm nervous about just skipping some banks
on the say-so of the BIOS ... what if the BIOS did something wrong. This
option gives us a way to return to the way things were before this patch.
These parts are now looking good ... but we still need to tackle what Linux
does when it does get the CPER record. I suspect we need to preserve
the existing "fake an mcelog entry with just the address" on old platforms,
but need to do something smarter on new ones.
-Tony
Powered by blists - more mailing lists