linux-kernel - Re: Erroneous package power limit notification since kernel 2.6.39

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110628141831.55502d76@jbarnes-desktop>
Date:	Tue, 28 Jun 2011 14:18:31 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Olaf Freyer <aaron667@....net>
Cc:	Florian Mickler <florian@...kler.org>,
	linux-kernel@...r.kernel.org,
	Chris Wilson <chris@...is-wilson.co.uk>,
	Keith Packard <keithp@...thp.com>,
	dri-devel@...ts.freedesktop.org
Subject: Re: Erroneous package power limit notification since kernel 2.6.39

On Tue, 28 Jun 2011 23:09:45 +0200
Olaf Freyer <aaron667@....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.525844] CPU4: Package power
> limit notification (total events = 1)
> 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.525851] CPU1: Package power
> limit notification (total events = 1)
> May 22 14:41:34 localhost kernel: [   57.525854] CPU2: Package power
> limit notification (total events = 1)
> May 22 14:41:34 localhost kernel: [   57.525856] CPU5: Package power
> limit notification (total events = 1)
> May 22 14:41:34 localhost kernel: [   57.525859] CPU3: Package power
> limit notification (total events = 1)
> May 22 14:41:34 localhost kernel: [   57.525861] Disabling lock
> debugging due to kernel taint
> May 22 14:41:34 localhost kernel: [   57.525869] CPU6: Package power
> limit notification (total events = 1)
> May 22 14:41:34 localhost kernel: [   57.525872] CPU7: Package power
> limit notification (total events = 1)
> May 22 14:41:34 localhost kernel: [   57.536890] CPU1: Package power
> limit normal
> May 22 14:41:34 localhost kernel: [   57.536893] CPU4: Package power
> limit normal
> May 22 14:41:34 localhost kernel: [   57.536896] CPU2: Package power
> limit normal
> May 22 14:41:34 localhost kernel: [   57.536899] CPU3: Package power
> limit normal
> May 22 14:41:34 localhost kernel: [   57.536901] CPU5: Package power
> limit normal
> May 22 14:41:34 localhost kernel: [   57.536904] CPU0: Package power
> limit normal
> May 22 14:41:34 localhost kernel: [   57.536915] CPU6: Package power
> limit normal
> May 22 14:41:34 localhost kernel: [   57.536918] CPU7: 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.

-- 
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/