Re: p4-clockmod doesn't seem to allow the highest possible speed

[Wouter Verhelst <wouter@grep.be>]

[-- Attachment #1.1: Type: text/plain, Size: 2442 bytes --]

On Sat, Jan 10, 2004 at 04:38:34PM +0100, Dominik Brodowski wrote:
> > Note that I had to reboot my box to unload the module. This is probably
> > related to the above, but just in case it isn't: I cannot rmmod the
> > p4-clockmod module, trying anyway results in rmmod segfaulting -- at
> > least once the frequency has been altered. I didn't reboot again just to
> > test that, but if you want, it's no problem.
> 
> That's unrelated, and I was able to reproduce it on my notebook as well. The
> attached patch [which should apply with some offset] should fix that.

OK, thanks.

[...]
> On Sat, Jan 10, 2004 at 04:02:52PM +0100, Wouter Verhelst wrote:
> > > What does /proc/cpuinfo say before modprobing p4-clockmod, and
> > > after modprobing p4-clockmod?
> > 
> > The only difference with the one you already have is the Mhz number
> > (which seems logical). Before it's loaded, it's at 2194.424;
> > Immediately after loading p4-clockmod, that number was still the
> > same, but in the mean time it went back to 1919.054
>
> 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

> BTW, could it be that this is still the 2.6.0 module, instead of the
> 2.6.1 variant? 2.6.1 should report more "clean" values in
> /sys/devices/system/cpu/cpufreq/... it should report 2200000 instead
> of 2193205.

Yes, the first mail I sent (with the command line stuff in /sys) was
before I installed 2.6.1, still running 2.6.0 at that point. Sorry for
the confusion :-)

-- 
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.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
Cpufreq mailing list
Cpufreq@www.linux.org.uk
http://www.linux.org.uk/mailman/listinfo/cpufreq