public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Pavel Machek <pavel@suse.cz>,
	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
Date: Mon, 09 Jun 2008 09:39:39 -0700	[thread overview]
Message-ID: <484D5CCB.10302@intel.com> (raw)
In-Reply-To: <20080607145435.4afc9812@infradead.org>

Arjan van de Ven wrote:
> On Sat, 7 Jun 2008 23:39:18 +0200
> Pavel Machek <pavel@suse.cz> 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
>>
>> 								Pavel
>>
> 
> 
> 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...

I neither run gnome nor kde. there's nothing running on this box that is managing
power settings.

Auke



  parent reply	other threads:[~2008-06-09 16:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080606140846.GA9580@ucw.cz>
2008-06-07 21:39 ` bug? acpi p-state + ondemand keeps dropping max freq Pavel Machek
2008-06-07 21:54   ` Arjan van de Ven
2008-06-07 23:36     ` Holger Macht
2008-06-09 16:39     ` Kok, Auke [this message]
2008-06-16 10:42     ` Pavel Machek
2008-06-16 14:43       ` Arjan van de Ven
2008-06-17  8:44         ` Pavel Machek
2008-07-05 19:49         ` Björn Steinbrink
2008-07-05 20:04           ` Björn Steinbrink
2008-06-17 18:15       ` Len Brown
2008-06-05 22:30 Kok, Auke
2008-06-06  4:13 ` Henrique de Moraes Holschuh
2008-06-06 16:34   ` Kok, Auke
2008-06-06 19:47     ` Henrique de Moraes Holschuh
2008-06-07  2:46 ` Len Brown
2008-06-07 23:22 ` Björn Steinbrink

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=484D5CCB.10302@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=arjan@infradead.org \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=davej@codemonkey.org.uk \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    /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