From: Pavel Machek <pavel@suse.cz>
To: Arjan van de Ven <arjan@infradead.org>
Cc: davej@codemonkey.org.uk, auke-jan.h.kok@intel.com,
len.brown@intel.com, cpufreq@lists.linux.org.uk,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: bug? acpi p-state + ondemand keeps dropping max freq
Date: Mon, 16 Jun 2008 12:42:00 +0200 [thread overview]
Message-ID: <20080616104159.GA28659@elf.ucw.cz> (raw)
In-Reply-To: <20080607145435.4afc9812@infradead.org>
On Sat 2008-06-07 14:54:35, 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
> 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...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-06-16 10:42 UTC|newest]
Thread overview: 20+ 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
2008-06-16 10:42 ` Pavel Machek [this message]
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-10 22:40 Beglin, Brad R
2008-06-13 14:21 ` Thomas Renninger
2008-07-08 10:57 ` Arkadiusz Miskiewicz
-- strict thread matches above, loose matches on Subject: below --
2008-06-10 21:45 Beglin, Brad R
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=20080616104159.GA28659@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=arjan@infradead.org \
--cc=auke-jan.h.kok@intel.com \
--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 \
/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