You are not logged in.

Pages: 1

#1 2012-08-16 03:21:53

runny6play
Member
Registered: 2012-02-18
Posts: 85

cpu caps @ 1.2 Ghz on battery [solved-ish (worked around)]

I'm having issues with my i7.quad core. Both cpu-freq and i7z report my i7 quad core @ 2.5 Ghz maxing at 1.2 on battery. it runs fine and even turbos when on AC

Last edited by runny6play (2012-08-19 06:33:57)

Offline

#2 2012-08-16 05:46:24

runny6play
Member
Registered: 2012-02-18
Posts: 85

Re: cpu caps @ 1.2 Ghz on battery [solved-ish (worked around)]

(cpu0 is on proformance gov. the rest are on ondemand.)
on battery idle

cat /proc/cpuinfo | grep MHz
cpu MHz		: 2501.000
cpu MHz		: 800.000
cpu MHz		: 800.000
cpu MHz		: 800.000
cpu MHz		: 800.000
cpu MHz		: 800.000
cpu MHz		: 800.000
cpu MHz		: 800.000
i7z

Cpu speed from cpuinfo 2494.00Mhz
cpuinfo might be wrong if cpufreq is enabled. To guess correctly try estimating
Linux's inbuilt cpu_khz code emulated now
True Frequency (without accounting Turbo) 2493 MHz
  CPU Multiplier 25x || Bus clock frequency (BCLK) 99.72 MHz

Socket [0] - [physical cores=4, logical cores=8, max online cores ever=4]
  TURBO ENABLED on 4 Cores, Hyper Threading ON
  True Frequency 2592.72 MHz (99.72 x [26])
  Max TURBO Multiplier (if Enabled) with 1/2/3/4 Cores is  36x/35x/33x/33x
  Current Frequency 1650.54 MHz [99.72 x 16.55] (Max of below)
        Core [core-id]  :Actual Freq (Mult.)      C0%   Halt(C1)%  C3 %   C6 %
        Core 1 [0]:       1650.54 (16.55x)      5.81    3.31    1.16       1
        Core 2 [1]:       898.17 (9.01x)        1.43    1.19       0       0
        Core 3 [2]:       937.31 (9.40x)           1    0.102      0       0
        Core 4 [3]:       858.80 (8.61x)           1    0.485      0       0



C0 = Processor running without halting
C1 = Processor running with halts (States >C0 are power saver)
C3 = Cores running with PLL turned off and core cache turned off
C6 = Everything in C3 + core state saved to last level cache
  Above values in table are in percentage over the last 1 sec

battery under load

cat /dev/urandom >/dev/null
cat /proc/cpuinfo | grep MHz
cpu MHz		: 1200.000
cpu MHz		: 1200.000
cpu MHz		: 800.000
cpu MHz		: 800.000
cpu MHz		: 800.000
cpu MHz		: 800.000
cpu MHz		: 800.000
cpu MHz		: 800.000
i7z


Cpu speed from cpuinfo 2494.00Mhz
cpuinfo might be wrong if cpufreq is enabled. To guess correctly try estimating
Linux's inbuilt cpu_khz code emulated now
True Frequency (without accounting Turbo) 2494 MHz
  CPU Multiplier 25x || Bus clock frequency (BCLK) 99.76 MHz

Socket [0] - [physical cores=4, logical cores=8, max online cores ever=4]
  TURBO ENABLED on 4 Cores, Hyper Threading ON
  True Frequency 2593.76 MHz (99.76 x [26])
  Max TURBO Multiplier (if Enabled) with 1/2/3/4 Cores is  36x/35x/33x/33x
  Current Frequency 1197.12 MHz [99.76 x 12.00] (Max of below)
        Core [core-id]  :Actual Freq (Mult.)      C0%   Halt(C1)%  C3 %   C6 %
        Core 1 [0]:       1197.12 (12.00x)       100      52       0       0
        Core 2 [1]:       1197.10 (12.00x)      6.57    4.62       0       0
        Core 3 [2]:       1197.12 (12.00x)      9.44    4.49       1       0
        Core 4 [3]:       1197.01 (12.00x)         1     6.4       0       0



C0 = Processor running without halting
C1 = Processor running with halts (States >C0 are power saver)
C3 = Cores running with PLL turned off and core cache turned off
C6 = Everything in C3 + core state saved to last level cache
  Above values in table are in percentage over the last 1 sec

AC idle

cat /proc/cpuinfo | grep MHz
cpu MHz		: 2500.000
cpu MHz		: 2500.000
cpu MHz		: 800.000
cpu MHz		: 800.000
cpu MHz		: 800.000
cpu MHz		: 800.000
cpu MHz		: 800.000
cpu MHz		: 800.000
i7z



Cpu speed from cpuinfo 2494.00Mhz
cpuinfo might be wrong if cpufreq is enabled. To guess correctly try estimating
Linux's inbuilt cpu_khz code emulated now
True Frequency (without accounting Turbo) 2494 MHz
  CPU Multiplier 25x || Bus clock frequency (BCLK) 99.76 MHz

Socket [0] - [physical cores=4, logical cores=8, max online cores ever=4]
  TURBO ENABLED on 4 Cores, Hyper Threading ON
  True Frequency 2593.76 MHz (99.76 x [26])
  Max TURBO Multiplier (if Enabled) with 1/2/3/4 Cores is  36x/35x/33x/33x
  Current Frequency 2037.92 MHz [99.76 x 20.43] (Max of below)
        Core [core-id]  :Actual Freq (Mult.)      C0%   Halt(C1)%  C3 %   C6 %
        Core 1 [0]:       2037.92 (20.43x)      11.5    4.66       1    1.39
        Core 2 [1]:       1242.11 (12.45x)       5.7    4.19       0       0
        Core 3 [2]:       1646.17 (16.50x)      5.29    2.55       0       0
        Core 4 [3]:       890.73 (8.93x)         2.5    1.82       0       0



C0 = Processor running without halting
C1 = Processor running with halts (States >C0 are power saver)
C3 = Cores running with PLL turned off and core cache turned off
C6 = Everything in C3 + core state saved to last level cache
  Above values in table are in percentage over the last 1 sec

AC under load

cat /proc/cpuinfo | grep MHz
cpu MHz		: 2500.000
cpu MHz		: 800.000
cpu MHz		: 800.000
cpu MHz		: 800.000
cpu MHz		: 800.000
cpu MHz		: 2500.000
cpu MHz		: 800.000
cpu MHz		: 800.000
i7z

Cpu speed from cpuinfo 2494.00Mhz
cpuinfo might be wrong if cpufreq is enabled. To guess correctly try estimating
Linux's inbuilt cpu_khz code emulated now
True Frequency (without accounting Turbo) 2494 MHz
  CPU Multiplier 25x || Bus clock frequency (BCLK) 99.76 MHz

Socket [0] - [physical cores=4, logical cores=8, max online cores ever=4]
  TURBO ENABLED on 4 Cores, Hyper Threading ON
  True Frequency 2593.76 MHz (99.76 x [26])
  Max TURBO Multiplier (if Enabled) with 1/2/3/4 Cores is  36x/35x/33x/33x
  Current Frequency 2494.13 MHz [99.76 x 25.00] (Max of below)
        Core [core-id]  :Actual Freq (Mult.)      C0%   Halt(C1)%  C3 %   C6 %
        Core 1 [0]:       2494.13 (25.00x)      12.5    2.16    1.51       1
        Core 2 [1]:       2494.00 (25.00x)       100       0       0       0
        Core 3 [2]:       2493.97 (25.00x)         1    0.426      0       0
        Core 4 [3]:       2493.96 (25.00x)      1.21    2.38       0       0



C0 = Processor running without halting
C1 = Processor running with halts (States >C0 are power saver)
C3 = Cores running with PLL turned off and core cache turned off
C6 = Everything in C3 + core state saved to last level cache
  Above values in table are in percentage over the last 1 sec

the readings between them are radically different and i don't know which are right and which are wrong, but both tools report a cap of 1.2 Ghz on battery and i don't know why. I don't have any power saving features in the bios or the OS enabled

Offline

#3 2012-08-16 10:34:14

mutterschiff
Member
From: somewhere around Dresden, Ger
Registered: 2012-08-02
Posts: 31

Re: cpu caps @ 1.2 Ghz on battery [solved-ish (worked around)]

is something like cpupower or laptop-tools running?

Last.Fm
thou shalt not kill -9

Offline

#4 2012-08-16 19:28:47

runny6play
Member
Registered: 2012-02-18
Posts: 85

Re: cpu caps @ 1.2 Ghz on battery [solved-ish (worked around)]

I had laptop-mode-tools installed but i never set it up. I uninstalled That and pm-utils just to be sure. I also tried the  acpi=off on the kernel line but it results in a system hang at boot. It might also be worth noting that when i rebooted resetting the governor on cpu0 the CPU now clocks up to 3.4 on AC (turbo boost)

Last edited by runny6play (2012-08-16 19:30:11)

Offline

#5 2012-08-17 07:26:24

runny6play
Member
Registered: 2012-02-18
Posts: 85

Re: cpu caps @ 1.2 Ghz on battery [solved-ish (worked around)]

Update

turbo boost will not boost after the plug has been removed even after being plugged back in.
rmmod processor will keep the turbo / clock up if the plug is removed but as soon as the cpu idles it will drop to 800 Mhz and gets stuck there untill the processor module is reloaded. (does the same on AC)
rmmod processor then modprobe processor will fix turbo if the plug has been removed in the same session

Last edited by runny6play (2012-08-17 07:27:38)

Offline

#6 2012-08-17 08:36:03

runny6play
Member
Registered: 2012-02-18
Posts: 85

Re: cpu caps @ 1.2 Ghz on battery [solved-ish (worked around)]

Blacklisting the ac module is a workaround. but i can imagine that it will have undesired side effects and a very round about way of fixing the problem. I am also worryed that this will cause my computer to overcharge my battery

Edit: this also only works if the laptop is plugged in while being turned on

Edit: I was wrong I just blacklisted it wrong.

Last edited by runny6play (2012-08-19 06:33:19)

Offline

Pages: 1

Board footer

Powered by FluxBB