From: "Luck, Tony" <tony.luck@intel.com>
To: Borislav Petkov <bp@alien8.de>, rui wang <ruiv.wang@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"gong.chen@linux.intel.com" <gong.chen@linux.intel.com>,
"Wang, Rui Y" <rui.y.wang@intel.com>
Subject: RE: [PATCH v3] x86/mce: Try printing all machine check banks known before panic
Date: Fri, 21 Nov 2014 17:20:53 +0000 [thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F3294F888@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <20141121164140.GA4274@pd.tnic>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 838 bytes --]
> leave them in. Then you can read them out again on panic time. The mce
> log buffer will have to become a circular buffer or something like that.
This is a mixed bag. If there are a bunch of errors so that we overflow the buffer,
then general wisdom says that people want to see the first errors, as the later
ones may just be secondary effects from the earlier ones.
But - lots of systems don't run mcelog(8) daemon. So the buffer just fills
up with the first 32 errors (perhaps all relatively harmless corrected errors)
and then when some serious stuff happens we have no place to log :-)
Perhaps we need separate buffers for UC=0 and UC=1? Or something else??
-Tony
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2014-11-21 17:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 9:22 [PATCH v3] x86/mce: Try printing all machine check banks known before panic ruiv.wang
2014-11-19 10:29 ` Borislav Petkov
2014-11-19 23:34 ` Luck, Tony
2014-11-20 10:15 ` Borislav Petkov
2014-11-21 1:20 ` rui wang
2014-11-21 16:41 ` Borislav Petkov
2014-11-21 17:20 ` Luck, Tony [this message]
2014-11-21 18:13 ` Borislav Petkov
2014-11-21 21:31 ` Luck, Tony
2014-11-21 21:35 ` Borislav Petkov
2014-11-21 21:59 ` Luck, Tony
2014-11-23 20:55 ` Borislav Petkov
2014-11-22 2:16 ` rui wang
2014-11-22 9:44 ` Borislav Petkov
2014-11-22 15:32 ` rui wang
2014-11-22 16:31 ` Borislav Petkov
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=3908561D78D1C84285E8C5FCA982C28F3294F888@ORSMSX114.amr.corp.intel.com \
--to=tony.luck@intel.com \
--cc=bp@alien8.de \
--cc=gong.chen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.y.wang@intel.com \
--cc=ruiv.wang@gmail.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).