From: Borislav Petkov <bp@alien8.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, Erik Veijola <erik.veijola@intel.com>,
Tony Luck <tony.luck@intel.com>
Subject: Re: [PATCH] x86/mce: Make timer handling more robust
Date: Tue, 31 Jan 2017 19:36:56 +0100 [thread overview]
Message-ID: <20170131183656.vfishl2fklz76cc4@pd.tnic> (raw)
In-Reply-To: <alpine.DEB.2.20.1701310936080.3457@nanos>
On Tue, Jan 31, 2017 at 09:37:34AM +0100, Thomas Gleixner wrote:
> Erik reported that on a preproduction hardware a CMCI storm triggers the
> BUG_ON in add_timer_on(). The reason is that the per CPU MCE timer is
> started by the CMCI logic before the MCE cpu hotplug callback starts the
nitpick: CPU
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2017-01-31 18:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 8:37 Thomas Gleixner
2017-01-31 13:33 ` Thomas Gleixner
2017-01-31 18:37 ` Borislav Petkov
2017-02-01 9:29 ` Veijola, Erik
2017-01-31 18:36 ` Borislav Petkov [this message]
2017-01-31 20:51 ` [tip:x86/urgent] " tip-bot for Thomas Gleixner
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=20170131183656.vfishl2fklz76cc4@pd.tnic \
--to=bp@alien8.de \
--cc=erik.veijola@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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
all inboxes | Powered by JetHome®