On Wed, Dec 29, 2010 at 4:43 PM, Mick <michaelkintzios@gmail.com> wrote:

> Just a wild guess:  are you running some desktop applet that manages the
> cpu
> frequency and is stuck on manual with a low setting?
>
> I have the i7 Q 720 @ 1.60GHz, which is supposedly go up to 2.8G with turbo
> boost, but can't say that I have ever seen it going that high ... not sure
> if
> there's a setting somewhere I should tweak.  This is from cpuinfo:
>
> =========================
> $ cat /proc/cpuinfo
> processor       : 0
> vendor_id       : GenuineIntel
> cpu family      : 6
> model           : 30
> model name      : Intel(R) Core(TM) i7 CPU       Q 720  @ 1.60GHz
> stepping        : 5
> cpu MHz         : 931.000
> cache size      : 6144 KB
> physical id     : 0
> siblings        : 8
> core id         : 0
> cpu cores       : 4
> apicid          : 0
> initial apicid  : 0
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 11
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> cmov
> pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp
> lm
> constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc
> aperfmperf
> pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1
> sse4_2
> popcnt lahf_lm ida dts tpr_shadow vnmi flexpriority ept vpid
> bogomips        : 3192.42
> clflush size    : 64
> cache_alignment : 64
> address sizes   : 36 bits physical, 48 bits virtual
> power management:
> =========================
> As you can see power management is also blank.
>
> These are my frequencies:
>
> $ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_*
> 1597000 1596000 1463000 1330000 1197000 1064000 931000
> conservative userspace powersave ondemand performance
> 931000
> acpi-cpufreq
> ondemand
> 1597000
> 931000
> <unsupported>
>
> PS.  Any ideas what makes that turbo thingy kick in?
>

The only thing that runs at boot is cpufrequtils and here is the config for
it:

# Options when starting cpufreq (given to the `cpufreq-set` program)
START_OPTS="--governor performance"

# Options when stopping cpufreq (given to the `cpufreq-set` program)
STOP_OPTS="--governor performance"

# Extra settings to write to sysfs cpufreq values.
#SYSFS_EXTRA="ondemand/ignore_nice_load=1 ondemand/up_threshold=70"
SYSFS_EXTRA="ondemand/ignore_nice_load=1"

And since I have power mgmt debug turned on, all my logs are belong to pm:
e1000e 0000:00:19.0: __pm_runtime_resume()!
e1000e 0000:00:19.0: __pm_runtime_resume() returns 1!
scsi host1: __pm_runtime_resume()!
scsi host1: __pm_runtime_resume() returns 1!
scsi host1: __pm_runtime_resume()!
scsi host1: __pm_runtime_resume() returns 1!
scsi host1: __pm_runtime_resume()!
scsi host1: __pm_runtime_resume() returns 1!
scsi host1: __pm_runtime_resume()!
etc, etc, etc, ad nauseum....

And even when I try this kind of thing:
/sys/devices/system/cpu
19:08:23# for a in cpu?/cpufreq/scaling_max_freq; do   echo -n 2667000 > $a;
done
/sys/devices/system/cpu
19:09:05# cat cpu?/cpufreq/scaling_max_freq
1199000
1199000
1199000
1199000
/sys/devices/system/cpu
19:09:20# for a in cpu?/cpufreq/scaling_governor; do   echo -n performance >
$a; done

I can see gkrellm get its governor changed but I cannot override the max
freq. How can I tell what the BIOS is reporting?  Here is what dmidecode
tells me about the CPU:

Handle 0x0004, DMI type 4, 42 bytes
Processor Information
        Socket Designation: CPU 1
        Type: Central Processor
        Family: <OUT OF SPEC>
        Manufacturer: Intel
        ID: 52 06 02 00 FF FB EB BF
        Version: Intel(R) Core(TM) i7 CPU       M 620  @ 2.67GH
        Voltage: 0.0 V
        External Clock: 533 MHz
        Max Speed: 4000 MHz
        Current Speed: 2666 MHz
        Status: Populated, Enabled
        Upgrade: Other
        L1 Cache Handle: 0x0005
        L2 Cache Handle: 0x0006
        L3 Cache Handle: 0x0007
        Serial Number: To Be Filled By O.E.M.
        Asset Tag: To Be Filled By O.E.M.
        Part Number: To Be Filled By O.E.M.
        Core Count: 2
        Core Enabled: 1
        Thread Count: 2
        Characteristics:
                64-bit capable


-- 
Bill Longman