From: Olaf Freyer <aaron667@gmx.net>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Florian Mickler <florian@mickler.org>,
linux-kernel@vger.kernel.org,
Chris Wilson <chris@chris-wilson.co.uk>,
Keith Packard <keithp@keithp.com>,
dri-devel@lists.freedesktop.org
Subject: Re: Erroneous package power limit notification since kernel 2.6.39
Date: Wed, 29 Jun 2011 00:01:58 +0200 [thread overview]
Message-ID: <4E0A4F56.90806@gmx.net> (raw)
In-Reply-To: <20110628141831.55502d76@jbarnes-desktop>
Am 28.06.2011 23:18, schrieb Jesse Barnes:
> On Tue, 28 Jun 2011 23:09:45 +0200
> Olaf Freyer <aaron667@gmx.net> wrote:
>>>>> I'd guess ccab5c82759e2ace74b2e84f82d1e0eedd932571 could be the
>>>>> cause. Can you check if the appended revert of that commit makes
>>>>> things disappear?
>>>> It seems like you guessed perfectly correct - reverting the commit makes
>>>> those notifications go away at once.
>>>>
>>> Without this reverted you see messages? I missed the earlier stuff,
>>> what message are you seeing?
>>>
>> Since 2.6.39 I saw those as soon as I start up the xserver:
>>
>> May 22 14:41:34 localhost kernel: [ 57.525848] CPU0: Package power
>> limit notification (total events = 1)
>> May 22 14:41:34 localhost kernel: [ 57.536904] CPU0: Package power
>> limit normal
> Ok interesting, didn't realize X startup was so GPU intensive. :)
>
> The patch you reverted will definitely cause the GPU to ramp up its
> frequency much faster than before, but it sounds like on your system
> you might also see it with the revert if you run something GPU
> intensive like nexuiz.
>
> The CPU (and by extension the GPU) will take care of itself though; if
> things get too hot or over power, it will clock throttle to keep itself
> in a safe range.
I also see the message alot during my daily average usage of my computer
(just using Firefox, Thunderbird and IntelliJ) - seeing things like
CPU3: Package power limit notification (total events = 90809)
after a normal day in the office became normal since 2.6.39.
I just gave nexuiz a try for about 30 minutes with the reversal patch
applied -
and not a single message appeared in my logs.
next prev parent reply other threads:[~2011-06-28 22:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-22 13:01 Erroneous package power limit notification since kernel 2.6.39 Olaf Freyer
2011-05-25 15:40 ` Olaf Freyer
2011-06-02 16:50 ` Olaf Freyer
2011-06-26 16:27 ` Florian Mickler
2011-06-28 20:46 ` Olaf Freyer
2011-06-28 20:59 ` Jesse Barnes
2011-06-28 21:09 ` Olaf Freyer
2011-06-28 21:18 ` Jesse Barnes
2011-06-28 22:01 ` Olaf Freyer [this message]
2011-06-28 22:06 ` Jesse Barnes
2011-06-30 6:37 ` Olaf Freyer
2011-07-22 16:10 ` Jesse Barnes
2011-05-29 19:53 ` Maciej Rutecki
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=4E0A4F56.90806@gmx.net \
--to=aaron667@gmx.net \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=florian@mickler.org \
--cc=jbarnes@virtuousgeek.org \
--cc=keithp@keithp.com \
--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