From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arjan van de Ven Subject: Re: bug? acpi p-state + ondemand keeps dropping max freq Date: Mon, 16 Jun 2008 07:43:37 -0700 Message-ID: <20080616074337.46d6f411@infradead.org> References: <20080606140846.GA9580@ucw.cz> <20080607213918.GC1746@elf.ucw.cz> <20080607145435.4afc9812@infradead.org> <20080616104159.GA28659@elf.ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from casper.infradead.org ([85.118.1.10]:48971 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753898AbYFPOns (ORCPT ); Mon, 16 Jun 2008 10:43:48 -0400 In-Reply-To: <20080616104159.GA28659@elf.ucw.cz> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Pavel Machek Cc: 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 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.