https://bugzilla.kernel.org/show_bug.cgi?id=16362 Summary: only the lowest frequency is used - scaling_max_frequency is set to lowest frequency and directly reset if changed Product: Power Management Version: 2.5 Kernel Version: 2.6.35-rc4 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: cpufreq AssignedTo: cpufreq@xxxxxxxxxxxxxxx ReportedBy: timshel@xxxxxxxxxxxxxx Regression: Yes I have am using a Core i5 M 540 @ 2.53GHz but only the lowest frequency is used all the time with OpenSuse 11.3 which uses Kernel 2.6.34. cpuinfo_max_freq and scaling_max_freq differ and if I change scaling_max_frequency to the correct cpuinfo one it gets reset? dmesg debug output: [ 1474.178507] cpufreq-core: setting new policy for CPU 0: 1199000 - 2534000 kHz [ 1474.178514] freq-table: request for verification of policy (1199000 - 2534000 kHz) for cpu 0 [ 1474.178519] freq-table: verification lead to (1199000 - 2534000 kHz) for cpu 0 [ 1474.178525] freq-table: request for verification of policy (1199000 - 1199000 kHz) for cpu 0 [ 1474.178529] freq-table: verification lead to (1199000 - 1199000 kHz) for cpu 0 [ 1474.178533] cpufreq-core: new min and max freqs are 1199000 - 1199000 kHz [ 1474.178536] cpufreq-core: governor: change or update limits [ 1474.178540] cpufreq-core: __cpufreq_governor for CPU 0, event 3 [ 1474.178544] cpufreq-core: target for CPU 0: 1199000 kHz, relation 1 [ 1474.178548] freq-table: request for target 1199000 kHz (relation: 1) for cpu 0 [ 1474.178552] freq-table: target is 11 (1199000 kHz, 11) The problem doesn't appear with Kubuntu 10.04 which uses 2.6.32. After installing Vanilla 2.6.34 from the mainline repository I got the same problem there too. It also happens with 2.6.35-rc4 and 2.6.33 but it works fine with latest Vanilla 2.6.32.16 from the same repository so it looks like a Kernel bug. It also worked fine with Opensuse 11.3 while I was using 2.6.31. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
