From: Fenghua Yu <fenghua.yu@intel.com>
To: Udo Steinberg <udo@hypervisor.org>
Cc: "Yu, Fenghua" <fenghua.yu@intel.com>,
"Luck, Tony" <tony.luck@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: MCE/Package power limit notification
Date: Tue, 29 Nov 2011 13:43:43 -0800 [thread overview]
Message-ID: <20111129214342.GB5412@linux-os.sc.intel.com> (raw)
In-Reply-To: <20111129222424.498469fe@x220.fritz.box>
On Tue, Nov 29, 2011 at 01:24:24PM -0800, Udo Steinberg wrote:
> On Mon, 28 Nov 2011 14:50:47 -0800 Yu, Fenghua (YF) wrote:
>
> YF> I sent out a patch to remove the mcelog info. Could you try it and see if it works for you?
> YF> https://lkml.org/lkml/2011/11/14/239
> YF>
> YF> Thanks.
> YF>
> YF> -Fenghua
>
> Hi Fenghua,
>
> Thanks for the patch. It works and eliminates the MCE warnings. What exactly
> are the BIOS issues mentioned in the patch description? Is BIOS programming
> some MSRs the wrong way?
Hi, Udo,
Could you please check counters in /sys/devices/system/cpu/cpu#/thermal_throttle
and see which counters report the thermal events?
The thought of the patch is to remove the errors in mcelog and report the errors
in respective counters. Therefore, the events are not reported as scary hardware
issues but are still captured in counters.
I think BIOS/firmware sets up power limit or thermal throttle incorrectly and
triggers events incorrectly. You may try updated BIOS to see if the events go
away.
Thanks.
-Fenghua
next prev parent reply other threads:[~2011-11-29 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 15:09 MCE/Package power limit notification Udo Steinberg
2011-11-28 22:46 ` Luck, Tony
2011-11-28 22:50 ` Yu, Fenghua
2011-11-29 21:24 ` Udo Steinberg
2011-11-29 21:43 ` Fenghua Yu [this message]
2011-11-29 22:19 ` Udo Steinberg
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=20111129214342.GB5412@linux-os.sc.intel.com \
--to=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=udo@hypervisor.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