Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754611AbYGEUEq (ORCPT ); Sat, 5 Jul 2008 16:04:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752473AbYGEUEj (ORCPT ); Sat, 5 Jul 2008 16:04:39 -0400 Received: from mail.gmx.net ([213.165.64.20]:52115 "HELO mail.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1752356AbYGEUEi (ORCPT ); Sat, 5 Jul 2008 16:04:38 -0400 X-Authenticated: #5039886 X-Provags-ID: V01U2FsdGVkX18oPP1Bw5wobNTb55/pgCX1hfDk8r07woHMNyMdme MGq2JBJl69whrB Date: Sat, 5 Jul 2008 22:04:34 +0200 From: =?iso-8859-1?Q?Bj=F6rn?= Steinbrink To: Arjan van de Ven Cc: Pavel Machek , auke-jan.h.kok@intel.com, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, len.brown@intel.com, cpufreq@lists.linux.org.uk, davej@codemonkey.org.uk Subject: Re: bug? acpi p-state + ondemand keeps dropping max freq Message-ID: <20080705200434.GA13278@atjola.homenet> References: <20080606140846.GA9580@ucw.cz> <20080607213918.GC1746@elf.ucw.cz> <20080607145435.4afc9812@infradead.org> <20080616104159.GA28659@elf.ucw.cz> <20080616074337.46d6f411@infradead.org> <20080705194908.GA13149@atjola.homenet> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20080705194908.GA13149@atjola.homenet> User-Agent: Mutt/1.5.18 (2008-05-17) X-Y-GMX-Trusted: 0 X-FuHaFi: 0.5 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2728 Lines: 64 On 2008.07.05 21:49:08 +0200, Bj?rn Steinbrink wrote: > On 2008.06.16 07:43:37 -0700, Arjan van de Ven wrote: > > On Mon, 16 Jun 2008 12:42:00 +0200 > > Pavel Machek wrote: > > > > > On Sat 2008-06-07 14:54:35, Arjan van de Ven wrote: > > > > On Sat, 7 Jun 2008 23:39:18 +0200 > > > > Pavel Machek wrote: > > > > > > > > > > # echo 1866000 > scaling_max_freq ; cat scaling_max_freq > > > > > > 800000 > > > > > > # echo 1866000 > scaling_max_freq ; cat scaling_max_freq > > > > > > 800000 > > > > > > > > > > > > > > > > > > This renders my Dothan to utterly poor speeds. (standard T43) > > > > > > > > > > > > performance cpufreq governor makes no difference - I still can't > > > > > > change the frequency upper/lower values. > > > > > > > > > > Hmm, I have similar problem in Novell bugzilla, on very different > > > > > hw: > > > > > > > > > > https://bugzilla.novell.com/show_bug.cgi?id=396311 > > > > > > > are either of you running gnome-power-manager or kpowersaved ? > > > > sometimes these programs (and more likely, the patches added by a > > > > distro maintainer who doesn't fully realize how power works) tend to > > > > muck with kernel settings around CPU frequency that they have > > > > absolutely no business touching... > > > > > > In novel bugzilla case ignore_ppc=1 helped, so it seems to be BIOS > > > problem, not userland's... > > > > well as long as the user doesn't use this for production use... the > > BIOS often reduces frequencies available to deal with thermal > > situations, so it's not a good idea to ignore that. > > Yep, seems to be a thermal thing. I managed to find some time to play > around with it a bit, and running a cpu hog for a short period of time, > while watching temperature and scaling_max_freq showed this: > [snip] > > > So upon reaching 54?C some throttling kicks in and only when going back > to less then 50?C, that limit is lifted again. Too bad that with Linux, > this T43 already runs at about 47?C when idle, so as soon as there's any > load on the cpu, it will scale up for a few seconds and then get > throttled :-( OK, a stop at thinkwiki[1] later, I know what's happening now. The BIOS has a few settings regarding CPU speed on AC/battery. One is about balancing power and noise. The above throttling does no longer kick in if that option is set to "Maximum Power". Bj?rn [1] http://www.thinkwiki.org/wiki/How_to_make_use_of_Dynamic_Frequency_Scaling#Troubleshooting -- 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/