I tested it with a fully updated Hardy Heron 8.04 Alpha: up_threshold is still 31
> uname -a
Linux oliverhp 2.6.24-11-generic #1 SMP Fri Feb 29 22:08:31 UTC 2008 i686 GNU/Linux
The bad thing is, that the default of 31 is not only set at boot time. It is set again upon standby&resume, hibernate&resume, even logout&login and perhaps more occasions.
A nice solution would be, that .../cpufreq/ondemand/up_threshold would not only change the current value but also the default which now seems to be built in the kernel. This way a script at boot time or an entry in /etc/sysfs.conf could set a value that will not change until the next reboot.
I tested it with a fully updated Hardy Heron 8.04 Alpha: up_threshold is still 31
> uname -a
Linux oliverhp 2.6.24-11-generic #1 SMP Fri Feb 29 22:08:31 UTC 2008 i686 GNU/Linux
The bad thing is, that the default of 31 is not only set at boot time. It is set again upon standby&resume, hibernate&resume, even logout&login and perhaps more occasions.
A nice solution would be, that .../cpufreq/ ondemand/ up_threshold would not only change the current value but also the default which now seems to be built in the kernel. This way a script at boot time or an entry in /etc/sysfs.conf could set a value that will not change until the next reboot.