From: Borislav Petkov <bp@alien8.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "Raj, Ashok" <ashok.raj@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>
Subject: Re: [Patch V2] x86, mce: Ensure offline CPU's don't participate in mce rendezvous process.
Date: Mon, 7 Dec 2015 21:19:51 +0100 [thread overview]
Message-ID: <20151207201951.GI22248@pd.tnic> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F39F7C24B@ORSMSX114.amr.corp.intel.com>
On Mon, Dec 07, 2015 at 08:04:30PM +0000, Luck, Tony wrote:
> > Kernel panic - not syncing: Timeout: Not all CPUs entered broadcast exception handler
>
> Is that what we printed in this case? ... boy is that a misleading message ... we got *extra*
> cpus (the offline ones), not "Not all".
>
> Good job we have a fix :-)
Well, we still have that printk string in there.
And that is incorrect too, because the MCE (at least the one I'm
injecting) gets broadcasted to the CPUs on the *node* and not to the
whole system.
If we had to be precise, text should say "Not all CPUs which the MCE was
broadcasted to entered the exception handler..."
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2015-12-07 20:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-05 0:29 [Patch V2] x86, mce: Ensure offline CPU's don't participate in mce rendezvous process Ashok Raj
2015-12-07 20:00 ` Borislav Petkov
2015-12-07 20:04 ` Luck, Tony
2015-12-07 20:19 ` Borislav Petkov [this message]
2015-12-07 22:07 ` Luck, Tony
2015-12-07 22:34 ` Borislav Petkov
2015-12-07 23:26 ` Luck, Tony
2015-12-07 23:46 ` Raj, Ashok
2015-12-07 23:25 ` Borislav Petkov
2015-12-08 1:41 ` Raj, Ashok
2015-12-08 9:18 ` Borislav Petkov
2015-12-08 15:59 ` Luck, Tony
2015-12-08 18:56 ` 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=20151207201951.GI22248@pd.tnic \
--to=bp@alien8.de \
--cc=ashok.raj@intel.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).