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

[bert hubert]

>   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!

-- 
http://www.PowerDNS.com      Open source, database driven DNS Software 
http://netherlabs.nl              Open and Closed source services
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/