From: Cesar Eduardo Barros <cesarb@cesarb.net>
To: Joe Perches <joe@perches.com>
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 20:12:16 -0300 [thread overview]
Message-ID: <4C784650.2030200@cesarb.net> (raw)
In-Reply-To: <1282894751.1836.41.camel@Joe-Laptop>
Em 27-08-2010 04:39, Joe Perches escreveu:
> On Thu, 2010-08-26 at 22:38 -0300, Cesar Eduardo Barros wrote:
>> intel ips 0000:00:1f.6: CPU power limit 3863 exceeded: 0
>>
>> I think you put the parameters in the wrong order on the dev_info() call
>> for the CPU power limit; it is the limit that is 0.
>
> Yes. Fixed.
>
>> Two bogus things I can see:
>>
>> - The first "MCP power limit exceeded" seems very bogus.
>> - What do you mean, core_power_limit is zero?
>
> I added a logging message whenever the turbo limits change
> and logging messages for power/temp on MCH for completeness.
>
> Maybe this will show something useful like when/how
> CPU power limit gets set to 0.
Running with it right now, did not help much:
$ dmesg | fgrep 'intel ips'
intel ips 0000:00:1f.6: Warning: CPU TDP doesn't match expected value
(found 25, expected 35)
intel ips 0000:00:1f.6: PCI INT C -> GSI 18 (level, low) -> IRQ 18
intel ips 0000:00:1f.6: IPS driver initialized, MCP temp limit 65535
intel ips 0000:00:1f.6: MCP power limit 65535 exceeded: cpu:8058 +
mch:23392829
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 5675
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 6369
intel ips 0000:00:1f.6: MCP power limit 65535 exceeded: cpu:5095 + mch:65379
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 7387
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 8326
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 5943
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 6428
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 5775
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 7061
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 5153
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 5098
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 5208
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 7500
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 9144
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 6722
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 7156
intel ips 0000:00:1f.6: MCP power limit 65535 exceeded: cpu:5693 + mch:64598
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 5856
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 4209
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 4726
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 5259
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 5212
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 4862
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 5281
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 4235
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 4897
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 5257
intel ips 0000:00:1f.6: MCP power limit 65535 exceeded: cpu:5111 + mch:64134
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 4843
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 4909
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 5904
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 6059
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 5579
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 5970
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 5213
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 6388
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 4444
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 6545
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 4439
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 4682
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 4337
intel ips 0000:00:1f.6: CPU power limit 0 exceeded: 4499
Just for fun, here is what debugfs has to say:
$ ls /sys/kernel/debug/ips/
cpu_clamp cpu_power cpu_temp mch_power mch_temp
$ cat /sys/kernel/debug/ips/*
23.0W 21.0A
4415mW
46.99
59670mW
0.00
All numbers except the last vary a lot. A few more examples:
21.0W 21.0A
4379mW
51.09
6493mW
0.00
23.0W 21.0A
4681mW
45.13
34062mW
0.00
--
Cesar Eduardo Barros
cesarb@cesarb.net
cesar.barros@gmail.com
next prev parent reply other threads:[~2010-08-27 23:12 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 [this message]
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
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=4C784650.2030200@cesarb.net \
--to=cesarb@cesarb.net \
--cc=jbarnes@virtuousgeek.org \
--cc=joe@perches.com \
--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
Powered by JetHome