powernow regression in 8-STABLE

[Jung-uk Kim]

On Wednesday 20 July 2011 10:28 pm, Callum Gibson wrote:
> On 20Jul11 19:28, Jung-uk Kim wrote:
> }From your dmesg output, I see that the processor speed was not
> }calibrated properly.  ML-40's max. core freq. is 2,200 MHz
> according }to its specification but it was probed at 2,282 MHz,
> which is too }high.  I think that's the problem.  Can you please
> try the attached }patch?
>
> Yes, I have seen core freq wobble around for most of the time I've
> owned it, but usually close to 2200. This morning (with my reverted
> powernow.c) I had: dev.cpu.0.freq_levels: 3080/35000 2800/29000
> 2520/24000 2240/20000 1120/9000 which I don't believe I've seen
> before. Anyway...
>
> With your new patch applied (and powernow.c changed back to
> r222148) I get exact freq levels:
>
> dev.cpu.0.freq_levels: 2200/35000 2000/29000 1800/24000 1600/20000
> 800/9000

That's better. :-)

> However, dev.cpu.0.freq OID is still missing from sysctl output.
>
> As another data point, with your new patch applied, but the old
> powernow.c, (which I booted into mistakenly first time), I did have
> dev.cpu.0.freq, but the freq levels weren't exact.
>
> Here is a new verbose boot output with a cleaned and built kernel,
> 8-STABLE as at time=1311028656 and your patch applied:
>
> http://members.optusnet.com.au/callumgibson/verboseboot2.out

Can you please do "set debug.cpufreq.verbose=1" from loader prompt and 
show me the dmesg output?  I want to see intial settings.  You can 
reset it from command line with "sysctl debug.cpufreq.verbose=0" 
later.

Thanks,

Jung-uk Kim