[Bug 469636] Re: Wrong CPU frequencies reported, cannot run max freq

[C. Brayton]

This is precisely my problem, too (Ubuntu 9.10 Intel Duo 2 T2500 kernel
2.9.31-17-generic.

dmsg says:

[    0.000000] Detected 1997.533 MHz processor.

but /proc/cpuinfo assigns 1.0GHz to both cores, and as a result
scaling_max_freq is limited to 1.0GHz, and cannot be manually reset.

At boot, cpufreq-info shows that all is well: governor=ondemand,
maximum=2GHz minimum=1GHz. Within a few minutes, however, some process
(which!?) changes those values. Now my min=my max: "between 1GHz and
1GHz."

Sorry, a bit sloppy, this report. Majored in poetry.

cpuinfo after the governor and freq settings are changed :

processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 14
model name	: Genuine Intel(R) CPU           T2500  @ 2.00GHz
stepping	: 8
cpu MHz		: 1000.000
cache size	: 2048 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 2
apicid		: 0
initial apicid	: 0
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe constant_tsc arch_perfmon bts pni monitor vmx est tm2 xtpr pdcm
bogomips	: 3995.06
clflush size	: 64
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 14
model name	: Genuine Intel(R) CPU           T2500  @ 2.00GHz
stepping	: 8
cpu MHz		: 1000.000
cache size	: 2048 KB
physical id	: 0
siblings	: 2
core id		: 1
cpu cores	: 2
apicid		: 1
initial apicid	: 1
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe constant_tsc arch_perfmon bts pni monitor vmx est tm2 xtpr pdcm
bogomips	: 3994.66
clflush size	: 64
power management:

-- 
Wrong CPU frequencies reported, cannot run max freq
https://bugs.launchpad.net/bugs/469636
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs