linux-kernel - Re: cpufreq: last commit for 2.6.29 break cpufreq performance module

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] [day] [month] [year] [list]

Message-ID: <cc0fa41f0902091741u40220b1cif47c7964010281c9@mail.gmail.com>
Date:	Mon, 9 Feb 2009 23:41:08 -0200
From:	Guilherme Malschitzky Schroeder <guilherme.m.schroeder@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: cpufreq: last commit for 2.6.29 break cpufreq performance module

Sorry about the wrong info, i used the last cpufreq_ondemand.c file
before this commit and get the same problem. So it' s not the last
commit that changes the behaviour.
I'll bisect it and give more info.

On Mon, Feb 9, 2009 at 11:21 PM, Guilherme Malschitzky Schroeder
<guilherme.m.schroeder@...il.com> wrote:
> Hello,
>
> After this commit 6707fbb56c8fd3121e334291d170934bcaca2e7f, if i
> change the governor of cpufreq to performance, my processor still
> shows 800MHz instead of 2268.
>
> dub:/sys/devices/system/cpu/cpu0/cpufreq# cat scaling_governor
> ondemand
>
> dub:/sys/devices/system/cpu/cpu0/cpufreq# cat cpuinfo_cur_freq
> 800000
>
> dub:/sys/devices/system/cpu/cpu0/cpufreq# echo performance > scaling_governor
> dub:/sys/devices/system/cpu/cpu0/cpufreq# cat scaling_governor
> performance
> dub:/sys/devices/system/cpu/cpu0/cpufreq# cat cpuinfo_cur_freq
> 2267000
>
> But, /proc/cpuinfo shows 800MHz:
>
> model name      : Intel(R) Core(TM)2 Duo CPU     P8400  @ 2.26GHz
> stepping        : 6
> cpu MHz         : 800.000
>
> And i cannot remove the ondemand module:
>
> dub:/sys/devices/system/cpu/cpu0/cpufreq# rmmod cpufreq_ondemand
> ERROR: Module cpufreq_ondemand is in use
>
> I can confirm that it's not on 2268MHz because glxgears runs below the expected.
>
> No errors on dmesg too.
>
--
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/