linux-kernel - Re: 2.6.17 -> 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4

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, 30 Jul 2006 22:07:18 +0400
From:	Alexey Starikovskiy <alexey_y_starikovskiy@...ux.intel.com>
To:	bert hubert <bert.hubert@...herlabs.nl>,
	linux-kernel@...r.kernel.org, zwane@....linux.org.uk,
	davej@...hat.com, venkatesh.pallipadi@...el.com, tony@...mide.com,
	akpm@...l.org, cpufreq@...ts.linux.org.uk
Subject: Re: 2.6.17 -> 2.6.18 regression: cpufreq broken since 2.6.18-rc1
 on	pentium4

Do I understand your logs right and acpi-cpufreq is already loaded and works on your processor?
Do you have any info in /sys/devices/system/cpu/cpu0/cpufreq ?
Why do you want to load p4-clockmod over it? It does not save you any power, just limits performance.

Regards,
	Alex.

bert hubert wrote:
>>   I have similar problem with cpufreq-nforce2 -- http://lkml.org/lkml/2006/7/7/234
>>   I haven't do a git-bisect yet.
> 
> To recap, cpufreq died for at least two people (Tomasz Torcz and me) between
> 2.6.17 and 2.6.18-rc1. I've cc'd everybody who touched cpufreq according to
> the shortlog.
> 
> Abundant details are in:
> 
> http://lkml.org/lkml/2006/7/30/87
> 
> New information is that I've narrowed it down from between 2.6.16.9 and
> 2.6.18-rc1 to between 2.6.17.7 (which works) and 2.6.18-rc1 (which doesn't).
> 
> The problem exists both with cpufreq as modules and staticly, and both with
> P4 and nforce2.
> 
> Please let me know how I can help you solve this problem. I'll try a git
> bisect but a lot of the cpufreq changes appear to be interrelated, so I'm
> unsure if it will work.
> 
> Thanks!
> 
-
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/