[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#577260: linux-image-2.6.32-4-686: 2 GHz core 2 duo (E4400) reported as (or used at?) 1000 MHz



On Sat, 2010-04-10 at 23:50 +0200, Bernhard Kuemel wrote:
> Package: linux-2.6
> Version: 2.6.32-11
> Severity: normal
> 
> 
> I use a intel core 2 duo E4400 CPU at stock 2 GHz. /proc/cpuinfo 
> claims its frequency is 1000 MHz. cpufreq-info says its hardware 
> limit is 1000 MHz. During boot the kernel says:
> [    0.000000] Detected 1999.951 MHz processor.
> [    0.076234] CPU0: Intel(R) Core(TM)2 Duo CPU     E4400  @ 2.00GHz stepping 0d
> [    0.164090] CPU1: Intel(R) Core(TM)2 Duo CPU     E4400  @ 2.00GHz stepping 0d
> 
> I'm not sure wether my CPU is running at 1 or 2 GHz.
> 
> This all happens while I run seti@home on both cores so the ondemand 
> governor, speedstep or whatever should switch to maximum frequency. 
> Indeed, ondemand switches to what it thinks is the maximum frequency.
> Using the performance governor didn't help.
[...]
> --------------------- cpufreq-info ---------------------------
> bernhard@be:/data/home/bernhard$ cpufreq-info
> cpufrequtils 006: cpufreq-info (C) Dominik Brodowski 2004-2009
> Report errors and bugs to cpufreq@vger.kernel.org, please.
> analyzing CPU 0:
>   driver: acpi-cpufreq
>   CPUs which run at the same hardware frequency: 0
>   CPUs which need to have their frequency coordinated by software: 0
>   maximum transition latency: 160 us.
>   hardware limits: 600 MHz - 1000 MHz
>   available frequency steps: 1000 MHz, 800 MHz, 600 MHz
[...]

Note that the driver is acpi-cpufreq - this means it is dependent on the
BIOS.  Please check whether there is a BIOS update available for this
system.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: