Comment 12 for bug 36014

I've been working on trying to fix this, and have had some success in tracking down the problem. The problem occurs in the verification steps of __cpufreq_set_policy in cpufreq.c. If one comments out that (from after the memcpy to before the data->min = policy->min), cpufreq works fine.

Something seems to be going wrong with the verification step, but the debugging information doesn't appear to offer any specifics as to what step is going wrong. When the problem is there, I get the following output:

cpufreq-core: setting new policy for CPU 0: 600000 - 1600000 kHz
freq-table: request for verification of policy (600000 - 1600000 kHz) for cpu 0
freq-table: verification lead to (600000 - 1600000 kHz) for cpu 0
freq-table: request for verification of policy (600000 - 600000 kHz) for cpu 0
freq-table: verification lead to (600000 - 600000 kHz) for cpu 0
cpufreq-core: new min and max freqs are 600000 - 600000 kHz

I'll get more on this later.