cpufreq buggy on thinkpad t42

Found a workaround from a similar older bug. This helps a bit, but where to place?

eric@calliope:~$ sudo cpufreq-set -c 0 -d 600Mhz -u 1.80Ghz

Now the cpu scales faster like in jaunty before, but the default behaviour is a bug.

Eric

This bug seems to affect more hardware, must be kernel or software related.

eee901go, UNR 9.10, here the workaround does not help.

Powercord:
root@scylla:/home/eric# cpufreq-set -c0 -g powersave
root@scylla:/home/eric# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Bitte melden Sie Fehler an <email address hidden>.
analysiere CPU 0:
  Treiber: acpi-cpufreq
  Folgende CPUs können nur gleichzeitig ihre Frequenz variieren: 0
  Hardwarebedingte Grenzen der Taktfrequenz: 800 MHz - 1.60 GHz
  mögliche Taktfrequenzen: 1.60 GHz, 1.33 GHz, 1.07 GHz, 800 MHz
  mögliche Regler: conservative, ondemand, userspace, powersave, performance
  momentane Taktik: die Frequenz soll innerhalb 1.60 GHz und 1.60 GHz.
                    liegen. Der Regler "powersave" kann frei entscheiden,
                    welche Taktfrequenz innerhalb dieser Grenze verwendet wird.
  momentane Taktfrequenz ist 1.60 GHz (verifiziert durch Nachfrage bei der Hardware).

Means that powersave can switch between 1.60 and 1.60, full fan noise and much heat from the computer. So lets change the governor.

root@scylla:/home/eric# cpufreq-set -c0 -g ondemand
root@scylla:/home/eric# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Bitte melden Sie Fehler an <email address hidden>.
analysiere CPU 0:
  Treiber: acpi-cpufreq
  Folgende CPUs können nur gleichzeitig ihre Frequenz variieren: 0
  Hardwarebedingte Grenzen der Taktfrequenz: 800 MHz - 1.60 GHz
  mögliche Taktfrequenzen: 1.60 GHz, 1.33 GHz, 1.07 GHz, 800 MHz
  mögliche Regler: conservative, ondemand, userspace, powersave, performance
  momentane Taktik: die Frequenz soll innerhalb 1.60 GHz und 1.60 GHz.
                    liegen. Der Regler "ondemand" kann frei entscheiden,

Full power at all, no way to bring the computer down to save energy.

Battery with full reboot! Default behaviour
----
root@scylla:/home/eric# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Bitte melden Sie Fehler an <email address hidden>.
analysiere CPU 0:
  Treiber: acpi-cpufreq
  Folgende CPUs können nur gleichzeitig ihre Frequenz variieren: 0
  Hardwarebedingte Grenzen der Taktfrequenz: 800 MHz - 1.60 GHz
  mögliche Taktfrequenzen: 1.60 GHz, 1.33 GHz, 1.07 GHz, 800 MHz
  mögliche Regler: conservative, ondemand, userspace, powersave, performance
  momentane Taktik: die Frequenz soll innerhalb 1.33 GHz und 1.33 GHz.
                    liegen. Der Regler "performance" kann frei entscheiden,

Why the hell perfomance as default? How can we save energy when blowing with 1.33 or 1.33 scaling range? Lets change the governor.....
root@scylla:/home/eric# cpufreq-set -c0 -g ondemand
root@scylla:/home/eric# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Bitte melden Sie Fehler an <email address hidden>.
analysiere CPU 0:
  Treiber: acpi-cpufreq
  Folgende CPUs können nur gleichzeitig ihre Frequenz variieren: 0
  Hardwarebedingte Grenzen der Taktfrequenz: 800 MHz - 1.60 GHz
  mögliche Taktfrequenzen: 1.60 GHz, 1.33 GHz, 1.07 GHz, 800 MHz
  mögliche Regler: conservative, ondemand, userspace, powersave, performance
  momentane Taktik: die Frequenz soll ...

Confirmed for amd64
Description: Ubuntu 9.10
Release: 9.10

ii linux-image-2. 2.6.31-15.50

eric@charon:~$ cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to <email address hidden>, please.
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which need to switch frequency at the same time: 0
  hardware limits: 1.20 GHz - 1.80 GHz
  available frequency steps: 1.80 GHz, 1.20 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance
  current policy: frequency should be within 1.80 GHz and 1.80 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.

No powersaving at all, the cpu stay fixed at 1800 and wont come down. This machine was updated from jaunty to karmic so the working cpufreq was destroyed by kernel or cpufreq packages.

Please change the bug to "cpufreq" general cause not only the t42 was affected.

Eric

Reason for this bug is a missing default setting in karmic.

1. In user gconf the apps/gnome-power-manager/cpufreq tree is missing completely
2. sysfsutils are not installed by default
3. The gnome-cpu applet cannot save changes permanently

We have a undefined state after boot, the kernel dont know what to do and goes crazy.

If a userspace daemon like powernowd is installed or sysfsutils with following conf the situation can be cleared.

#
# /etc/sysfs.conf - Configuration file for setting sysfs attributes.
#
# The sysfs mount directory is automatically prepended to the attribute paths.
#
# Syntax:
# attribute = value
# mode attribute = 0600 # (any valid argument for chmod)
# owner attribute = root:wheel # (any valid argument for chown)
#
# Examples:
#
# Always use the powersave CPU frequency governor
# devices/system/cpu/cpu0/cpufreq/scaling_governor = powersave
devices/system/cpu/cpu0/cpufreq/scaling_governor = ondemand

This bug duplicates to: 460064, 475706, 434255

This seems to be fixed at 10.04lts and later, my t42 did not show the described problem anymore.