From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Cesar Eduardo Barros <cesarb@cesarb.net>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
Matthew Garrett <mjg@redhat.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] intel_ips: quieten "power or thermal limit exceeded" messages
Date: Fri, 27 Aug 2010 01:18:53 +0100 [thread overview]
Message-ID: <20100827011853.3faef5e7@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <1282865341-17607-1-git-send-email-cesarb@cesarb.net>
On Thu, 26 Aug 2010 20:29:01 -0300
Cesar Eduardo Barros <cesarb@cesarb.net> wrote:
> On my Dell Inspiron N4010, one of these messages is printed every five
> seconds. Change both to dev_dbg to quieten them even more.
It's not the kind of thing you want to quieten since in most cases it is
stuff you want to know about.
>
> Signed-off-by: Cesar Eduardo Barros <cesarb@cesarb.net>
> ---
> drivers/platform/x86/intel_ips.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/platform/x86/intel_ips.c b/drivers/platform/x86/intel_ips.c
> index 9024480..7833adc 100644
> --- a/drivers/platform/x86/intel_ips.c
> +++ b/drivers/platform/x86/intel_ips.c
> @@ -607,7 +607,7 @@ static bool mcp_exceeded(struct ips_driver *ips)
> spin_unlock_irqrestore(&ips->turbo_status_lock, flags);
>
> if (ret)
> - dev_info(&ips->dev->dev,
> + dev_dbg(&ips->dev->dev,
> "MCP power or thermal limit exceeded\n");
Probably better to ratelimit it. Being told it occurs is important, being
told every five seconds is indeed excessive.
Alan
next prev parent reply other threads:[~2010-08-27 0:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 0:48 intel ips: CPU TDP doesn't match expected value Cesar Eduardo Barros
2010-08-25 1:37 ` Jesse Barnes
2010-08-26 23:29 ` [PATCH] intel_ips: quieten "power or thermal limit exceeded" messages Cesar Eduardo Barros
2010-08-26 23:33 ` Joe Perches
2010-08-27 0:11 ` Cesar Eduardo Barros
2010-08-27 0:41 ` Joe Perches
2010-08-27 1:38 ` Cesar Eduardo Barros
2010-08-27 7:39 ` Joe Perches
2010-08-27 23:12 ` Cesar Eduardo Barros
2010-08-28 2:21 ` Joe Perches
2010-08-28 10:46 ` Cesar Eduardo Barros
[not found] ` <1282994116.1946.226.camel@Joe-Laptop>
2010-08-28 12:52 ` Cesar Eduardo Barros
2010-08-28 13:01 ` Cesar Eduardo Barros
2010-08-28 13:29 ` Joe Perches
2010-08-28 14:18 ` Cesar Eduardo Barros
2010-08-28 15:23 ` Henrique de Moraes Holschuh
2010-08-28 19:07 ` Cesar Eduardo Barros
2010-08-30 16:29 ` Jesse Barnes
2010-08-30 21:42 ` Cesar Eduardo Barros
2010-09-23 20:31 ` Jesse Barnes
2010-09-23 20:47 ` Joe Perches
2010-09-23 20:50 ` Jesse Barnes
2010-08-27 0:18 ` Alan Cox [this message]
2010-08-27 0:22 ` Cesar Eduardo Barros
2010-08-27 1:42 ` Matthew Garrett
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=20100827011853.3faef5e7@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=cesarb@cesarb.net \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=platform-driver-x86@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
all inboxes | Powered by JetHome®