From: Prarit Bhargava <prarit@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: len.brown@kernel.org
Subject: Re: [RESEND 2] [PATCH 0/2] Rewrite power limit notification interrupt handling
Date: Wed, 29 May 2013 14:14:09 -0400 [thread overview]
Message-ID: <51A64571.5050804@redhat.com> (raw)
Len,
>The "Power Limit Notification" (X86_FEATURE_PLN) was added in Sandy Bridge
>to give the OS the option of knowing when the package has reached
>a configured power threshold.
>printk(KERN_CRIT "CPU%d: %s power limit notification (total events = %lu)
>printk(KERN_INFO "CPU%d: %s power limit normal\n"
I'm seeing this on a widening number of systems, mostly newer Intel systems.
>However, these events are quite routine on some systems under some conditions,
>alarming customers and provoking un-necessary customer support calls.
The idea that these are "routine" just doesn't make sense to me. Either this
warning is firing for a valid reason or it isn't. If it isn't then the question
remains -- why is it firing? Is it because of buggy FW or is something
actually wrong with the hardware?
P.
reply other threads:[~2013-05-29 18:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=51A64571.5050804@redhat.com \
--to=prarit@redhat.com \
--cc=len.brown@kernel.org \
--cc=linux-kernel@vger.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