Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753068Ab1F1WHK (ORCPT ); Tue, 28 Jun 2011 18:07:10 -0400 Received: from oproxy1-pub.bluehost.com ([66.147.249.253]:50784 "HELO oproxy1-pub.bluehost.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1752524Ab1F1WGz (ORCPT ); Tue, 28 Jun 2011 18:06:55 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=virtuousgeek.org; h=Received:Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References:X-Mailer:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=tfDu8Fbs+xbCfGsYjLBivkKQCBMNcsGDmcr0/yUv1VBaC+qXrP1uoob1NcXLqmbpBOG3xO5kLyzOge+Xhh29QYJ6Xo1FN1NOoxGRtQv5TLuPCnd+wVtasjutMCAqPTro; Date: Tue, 28 Jun 2011 15:06:44 -0700 From: Jesse Barnes To: Olaf Freyer Cc: Florian Mickler , linux-kernel@vger.kernel.org, Chris Wilson , Keith Packard , dri-devel@lists.freedesktop.org Subject: Re: Erroneous package power limit notification since kernel 2.6.39 Message-ID: <20110628150644.14805e83@jbarnes-desktop> In-Reply-To: <4E0A4F56.90806@gmx.net> References: <4DD9092A.4080507@gmx.net> <20110626182725.3f2eac8d@schatten.dmk.lab> <4E0A3DB1.8000202@gmx.net> <20110628135936.297293b4@jbarnes-desktop> <4E0A4319.6040309@gmx.net> <20110628141831.55502d76@jbarnes-desktop> <4E0A4F56.90806@gmx.net> X-Mailer: Claws Mail 3.7.6 (GTK+ 2.22.0; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Identified-User: {10642:box514.bluehost.com:virtuous:virtuousgeek.org} {sentby:smtp auth 67.161.37.189 authed with jbarnes@virtuousgeek.org} Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2259 Lines: 51 On Wed, 29 Jun 2011 00:01:58 +0200 Olaf Freyer wrote: > Am 28.06.2011 23:18, schrieb Jesse Barnes: > > On Tue, 28 Jun 2011 23:09:45 +0200 > > Olaf Freyer 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. Sounds like with the patch reverted we can't drive your GPU and CPU hard enough to generate the messages. Not sure if that's a good thing or a bad thing though... -- 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/