From: Wouter Verhelst <wouter@grep.be>
To: Ducrot Bruno <ducrot@poupinou.org>, cpufreq@www.linux.org.uk
Subject: Re: p4-clockmod doesn't seem to allow the highest possible speed
Date: Sun, 11 Jan 2004 20:56:19 +0100 [thread overview]
Message-ID: <20040111195619.GA25048@grep.be> (raw)
In-Reply-To: <20040111173547.GB5485@dominikbrodowski.de>
On Sun, Jan 11, 2004 at 06:35:47PM +0100, Dominik Brodowski wrote:
> On Sat, Jan 10, 2004 at 08:35:26PM +0100, Wouter Verhelst wrote:
> > That happens both when it's in P0 or P1.
>
> So ACPI works to set the processor in P0 and P1?
Yes.
> If so, you really really should use the ACPI cpufreq driver instead of
> the p4-clockmod driver. The former will offer you true "SpeedStep"
> support, the latter only some clock modulation which won't save you
> much energy as ACPI supports the C2 idle state anyway.
Ah, so what p4-clockmod does is not SpeedStep?
Hm. That sucks.
> > Not that it matters -- p4-clockmod seems to do it right :)
>
> It's not as noisy, indeed. But it's not right -- as long as acpi.ko works.
It mostly does, although I've had lockups when using the /proc interface
to switch CPU frequencies -- yes, should've reported that, but I only
now remember :)
> > > I think ACPI is messing with us. It detects a high temperature
> > > situation, tries to scale down the CPU, and forces down the CPU speed.
> >
> > Hm. This one got me thinking; I think I just found it. I forgot that I
> > installed cpufreqd a while ago, which seems to be the culprit: when I
> > start cpufreqd, the system falls back to 1925Mhz. I've removed it now,
> > however, as killing cpufreqd does not release the maximum speed back to
> > it's normal value of 2.2Ghz, I'm not entirely sure; so...
> >
> > > Could you send me the output of /proc/acpi/processor/*/* and
> > > /proc/acpi/thermal_zone/*/* when you notice this situation again?
> >
> > ... I've still put those at
> > http://users.pandora.be/wouter.verhelst/proc-acpi.tgz
>
> Hm, can't recognize anything strange there. When the situation appears
> again, what does /sys/devices/sytem/cpu/cpu0/cpufreq/scaling_max_freq say?
That does not change.
--
Wouter Verhelst
Debian GNU/Linux -- http://www.debian.org
Nederlandstalige Linux-documentatie -- http://nl.linux.org
"Stop breathing down my neck." "My breathing is merely a simulation."
"So is my neck, stop it anyway!"
-- Voyager's EMH versus the Prometheus' EMH, stardate 51462.
next prev parent reply other threads:[~2004-01-11 19:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 18:18 p4-clockmod doesn't seem to allow the highest possible speed Wouter Verhelst
2004-01-10 10:15 ` Dominik Brodowski
2004-01-10 11:08 ` Wouter Verhelst
2004-01-10 13:18 ` Dominik Brodowski
2004-01-10 15:02 ` Wouter Verhelst
2004-01-10 15:38 ` Dominik Brodowski
2004-01-10 16:30 ` Wouter Verhelst
2004-01-10 15:21 ` Wouter Verhelst
2004-01-10 15:41 ` Dominik Brodowski
2004-01-10 16:32 ` Wouter Verhelst
2004-01-10 18:53 ` Ducrot Bruno
2004-01-10 19:35 ` Wouter Verhelst
2004-01-11 15:48 ` Ducrot Bruno
2004-01-11 17:30 ` Dominik Brodowski
2004-01-11 18:05 ` Ducrot Bruno
2004-01-11 17:35 ` Dominik Brodowski
2004-01-11 19:56 ` Wouter Verhelst [this message]
2004-01-11 20:06 ` Dominik Brodowski
2004-01-11 20:24 ` Wouter Verhelst
2004-01-12 12:26 ` Ducrot Bruno
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=20040111195619.GA25048@grep.be \
--to=wouter@grep.be \
--cc=cpufreq@www.linux.org.uk \
--cc=ducrot@poupinou.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.