From: Borislav Petkov <bp@suse.de>
To: "Wang, Rui Y" <rui.y.wang@intel.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
"Chen, Gong" <gong.chen@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: MCE Bug?
Date: Wed, 17 Jun 2015 11:41:56 +0200 [thread overview]
Message-ID: <20150617094155.GB26661@pd.tnic> (raw)
In-Reply-To: <FC9702EC51E4CA40A875703BEBD6CEF801AE738D@SHSMSX101.ccr.corp.intel.com>
Hi Rui,
On Wed, Jun 17, 2015 at 02:04:56AM +0000, Wang, Rui Y wrote:
> Is it a known problem? I'm based on Linux 4.1.0-rc3-7.
Yeah, I triggered a similar thing in conjunction with testing Gong's
stuff:
https://lkml.kernel.org/r/20150611082747.GA30391@pd.tnic
And I was waiting in line to get a chance to do some injection on our
EINJ box here too. But it seems you have the required setup already so
if you want to give those changes a run, I've uploaded them here:
git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras.git#tip-ras
It'll be much appreciated.
Thanks!
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next parent reply other threads:[~2015-06-17 9:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <FC9702EC51E4CA40A875703BEBD6CEF801AE738D@SHSMSX101.ccr.corp.intel.com>
2015-06-17 9:41 ` Borislav Petkov [this message]
2015-06-17 17:45 ` MCE Bug? Luck, Tony
2015-06-17 23:53 ` Luck, Tony
2015-06-18 10:25 ` Borislav Petkov
2015-06-18 13:10 ` [PATCH] x86/mce: Kill drain_mcelog_buffer() Borislav Petkov
2015-06-19 9:27 ` [PATCH] x86/mce: Initialize workqueues only once Borislav Petkov
2015-06-19 12:24 ` Borislav Petkov
2015-06-19 17:36 ` [PATCH] x86/mce: Initialize workqueues only once (alternate proposal) Luck, Tony
2015-06-19 19:02 ` Borislav Petkov
2015-06-18 9:18 MCE bug? Rui Wang
2015-06-18 10:02 ` Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2015-06-17 1:57 Rui Wang
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=20150617094155.GB26661@pd.tnic \
--to=bp@suse.de \
--cc=gong.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.y.wang@intel.com \
--cc=tony.luck@intel.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