linux-kernel - Re: cpufreq limits avilable frequencies to 800MHz on git kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 25 May 2008 11:36:24 +0200
From:	Arkadiusz Miskiewicz <arekm@...en.pl>
To:	linux-kernel@...r.kernel.org
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	cpufreq@...ts.linux.org.uk
Subject: Re: cpufreq limits avilable frequencies to 800MHz on git kernel

On Saturday 24 May 2008, Andrew Morton wrote:
> On Fri, 23 May 2008 19:44:57 +0200 Arkadiusz Miskiewicz <arekm@...en.pl> 
wrote:
> > thinkpad z60m, Intel(R) Pentium(R) M processor 2.00GHz. kernel from git
> > from 1-2 days ago.
> >
> > Unfortunately it seems that suspend to ram/resume causes frequency
> > to be limited to 800MHz only. I can't set it to 2GHz again :-/
> >
> > scaling_max_freq is then 800000 and cannot be changed.
> >
> > reboot and the problem disappears until new suspend/resume cycle.
> >
> > cpufreq stuff is driven by acpi-cpufreq
> >
> > $ cpufreq-info
> > cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
> > Report errors and bugs to linux@...do.de, please.
> > analyzing CPU 0:
> >   driver: acpi-cpufreq
> >   CPUs which need to switch frequency at the same time: 0
> >   hardware limits: 800 MHz - 2.00 GHz
> >   available frequency steps: 2.00 GHz, 1.60 GHz, 1.33 GHz, 1.07 GHz, 800
> > MHz available cpufreq governors: powersave, userspace, ondemand,
> > performance current policy: frequency should be within 800 MHz and 800
> > MHz. The governor "performance" may decide which speed to use within this
> > range.
> >   current CPU frequency is 800 MHz.
> >
> > /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:0
> > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq:800000
> > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq:2000000
> > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq:800000
> > /sys/devices/system/cpu/cpu0/cpufreq/related_cpus:0
> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies:200000
> >0 1600000 1333000 1066000 800000
> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:powersav
> >e userspace ondemand performance
> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:800000
> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:acpi-cpufreq
> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:performance
> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:800000
> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:800000
> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed:<unsupported>
>
> Thanks.  Is this a newly-occurring bug or did earlier kernels do this also?
>
> If it was newly added, do you know in which kernel version we might
> have added it?

I wasn't able to reproduce the problem on final 2.6.24 but was able to 
reproduce on final 2.6.25. Problem introduced somewhere between it seems.

Note that 2-3 suspend to ram/resume cycles is needed to get into the problem.

-- 
Arkadiusz Miśkiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/