From: "Luck, Tony" <tony.luck@intel.com>
To: "paulmck@kernel.org" <paulmck@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"bp@alien8.de" <bp@alien8.de>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"kernel-team@fb.com" <kernel-team@fb.com>
Subject: RE: [PATCH RFC x86/mce] Make mce_timed_out() identify holdout CPUs
Date: Thu, 7 Jan 2021 00:26:19 +0000 [thread overview]
Message-ID: <366fc78e7b8c4474958b289eec31ed25@intel.com> (raw)
In-Reply-To: <20210106232347.GG2743@paulmck-ThinkPad-P72>
> Please see below for an updated patch.
Yes. That worked:
[ 78.946069] mce: mce_timed_out: MCE holdout CPUs (may include false positives): 24-47,120-143
[ 78.946151] mce: mce_timed_out: MCE holdout CPUs (may include false positives): 24-47,120-143
[ 78.946153] Kernel panic - not syncing: Timeout: Not all CPUs entered broadcast exception handler
I guess that more than one CPU hit the timeout and so your new message was printed twice
before the panic code took over?
Once again, the whole of socket 1 is MIA rather than just the pair of threads on one of the cores there.
But that's a useful improvement (eliminating the other three sockets on this system).
Tested-by: Tony Luck <tony.luck@intel.com>
-Tony
next prev parent reply other threads:[~2021-01-07 0:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 17:41 [PATCH RFC x86/mce] Make mce_timed_out() identify holdout CPUs Paul E. McKenney
2021-01-06 18:32 ` Borislav Petkov
2021-01-06 19:13 ` Paul E. McKenney
2021-01-07 7:07 ` Borislav Petkov
2021-01-07 17:08 ` Paul E. McKenney
2021-01-08 12:31 ` Borislav Petkov
2021-01-08 14:55 ` Paul E. McKenney
2021-01-08 16:57 ` Borislav Petkov
2021-01-06 18:39 ` Luck, Tony
2021-01-06 19:17 ` Paul E. McKenney
2021-01-06 22:49 ` Luck, Tony
2021-01-06 23:23 ` Paul E. McKenney
2021-01-07 0:26 ` Luck, Tony [this message]
2021-01-07 0:41 ` Paul E. McKenney
2021-01-08 17:09 ` [tip: ras/core] x86/mce: " tip-bot2 for Paul E. McKenney
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=366fc78e7b8c4474958b289eec31ed25@intel.com \
--to=tony.luck@intel.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=kernel-team@fb.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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