On Thursday 30 December 2010 03:16:05 Bill Longman wrote:
> 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:

I do not have cpufreutils installed, but use the ondemand governor as a 
default.

http://thread.gmane.org/gmane.linux.gentoo.user/227247


> 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  <-- interesting!-->
>         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

This is what my i7 Q is showing:

Handle 0x0005, DMI type 4, 42 bytes
Processor Information
	Socket Designation: U2E1
	Type: Central Processor
	Family: <OUT OF SPEC>
	Manufacturer: Intel
	ID: E5 06 01 00 FF FB EB BF
	Version: CPU Version
	Voltage: 3.3 V
	External Clock: 133 MHz
	Max Speed: 4096 MHz  <--my max speed with turbo should be 2.8GHz?-->
	Current Speed: 1600 MHz  <--my max speed without turbo-->
	Status: Populated, Enabled
	Upgrade: ZIF Socket
	L1 Cache Handle: 0x0006
	L2 Cache Handle: 0x0007
	L3 Cache Handle: 0x0008
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified
	Core Count: 4
	Core Enabled: 4
	Thread Count: 8
	Characteristics:
		64-bit capable

My turbo reading leads me to think that the dmidecode is not necessarily 
reporting what the CPU can do.
-- 
Regards,
Mick