* CPU-Frequency limited to lowest available frequency while under load
@ 2007-10-30 10:23 Ferdinand Hübner
2007-10-31 13:28 ` Thomas Renninger
0 siblings, 1 reply; 6+ messages in thread
From: Ferdinand Hübner @ 2007-10-30 10:23 UTC (permalink / raw)
To: cpufreq
[-- Attachment #1: Type: text/plain, Size: 1553 bytes --]
Hello,
since I've upgraded to 2.6.23, the current frequency scaling policy is
being changed whenever the CPU is under load.
My CPU is a Core2Duo T7200, frequency steps: 2.00 GHz, 1.67 GHz, 1.33
GHz, 1000 MHz
I'm using the acpi-cpufreq driver and am setting the governor to
'ondemand' via cpufrequtils.
When the system is booted, the scaling works as expected, the partial
output from cpufreq-info:
current policy: frequency should be within 1000 MHz and 2.00 GHz.
However, when I start compiling something the policy is being changed to
the following:
current policy: frequency should be within 1000 MHz and 1000 MHz.
This problem didn't exist with kernels prior to 2.6.23 (I was using
gentoo-sources most of the time), same behaviour as with 2.6.23 can be
observed with 2.6.24-rc1.
I'm not entirely sure if this is a problem with cpufreq, so I apologize
if this is not the right place to ask for help.
Anyway, everytime the maximum CPU frequency is being changed, I receive
the following ACPI events a few seconds afterwards (these events are not
being handled)
processor CPU0 00000080 00000003
processor CPU1 00000080 00000003
Setting the maximum frequency back to 2GHz (cpufreq-set -u 2000MHz) has
either no effect at all, or is being reverted to 1GHz 30 seconds after that.
The 'performance' governor is showing the same behaviour.
I've attached my kernel config for ACPI/CPUFREQ and the output from
acpitool -e.
What can I do to get the "old" behaviour back? I just want the maximum
frequency to stay at 2GHz...
Thank you,
Ferdinand
[-- Attachment #2: kernel-config.txt --]
[-- Type: text/plain, Size: 2014 bytes --]
#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_PM_LEGACY is not set
# CONFIG_PM_DEBUG is not set
CONFIG_PM_SLEEP_SMP=y
CONFIG_PM_SLEEP=y
CONFIG_SUSPEND_SMP_POSSIBLE=y
CONFIG_SUSPEND=y
CONFIG_HIBERNATION_SMP_POSSIBLE=y
# CONFIG_HIBERNATION is not set
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
# CONFIG_ACPI_PROCFS is not set
CONFIG_ACPI_PROC_EVENT=y
CONFIG_ACPI_BUTTON=y
# CONFIG_ACPI_VIDEO is not set
CONFIG_ACPI_FAN=y
CONFIG_ACPI_DOCK=y
# CONFIG_ACPI_BAY is not set
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_HOTPLUG_CPU=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=2001
CONFIG_ACPI_DEBUG=y
# CONFIG_ACPI_DEBUG_FUNC_TRACE is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=y
# CONFIG_APM is not set
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
CONFIG_CPU_FREQ_DEBUG=y
# CONFIG_CPU_FREQ_STAT is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
# CONFIG_CPU_FREQ_GOV_USERSPACE is not set
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
#
# CPUFreq processor drivers
#
CONFIG_X86_ACPI_CPUFREQ=y
# CONFIG_X86_POWERNOW_K6 is not set
# CONFIG_X86_POWERNOW_K7 is not set
# CONFIG_X86_POWERNOW_K8 is not set
# CONFIG_X86_GX_SUSPMOD is not set
# CONFIG_X86_SPEEDSTEP_CENTRINO is not set
# CONFIG_X86_SPEEDSTEP_ICH is not set
# CONFIG_X86_SPEEDSTEP_SMI is not set
# CONFIG_X86_P4_CLOCKMOD is not set
# CONFIG_X86_CPUFREQ_NFORCE2 is not set
# CONFIG_X86_LONGRUN is not set
# CONFIG_X86_LONGHAUL is not set
# CONFIG_X86_E_POWERSAVER is not set
#
# shared options
#
# CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set
# CONFIG_X86_SPEEDSTEP_LIB is not set
CONFIG_CPU_IDLE=y
CONFIG_CPU_IDLE_GOV_LADDER=y
CONFIG_CPU_IDLE_GOV_MENU=y
[-- Attachment #3: acpitool.txt --]
[-- Type: text/plain, Size: 2288 bytes --]
Kernel version : 2.6.24-rc1 - ACPI version : ���\x18���������2.6
-----------------------------------------------------------
Battery status : <not available>
AC adapter : <not available>
Fan : enabled
Fan Speed : 3507 RPM
CPU type : Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz
Min/Max frequency : 1000/1000 MHz
Current frequency : 1000 MHz
Frequency governor : ondemand
Freq. scaling driver : acpi-cpufreq
Cache size : 4096 KB
Bogomips : 4023.70
Bogomips : 3990.04
# of CPU's found : 2
Processor ID : 0
Bus mastering control : yes
Power management : yes
Throttling control : yes
Limit interface : yes
Active C-state : C0
C-states (incl. C0) : 4
Usage of state C1 : 4148 (0.0 %)
Usage of state C2 : 13181091 (74.0 %)
Usage of state C3 : 4636873 (26.0 %)
T-state count : 8
Active T-state : T8
Processor ID : 1
Bus mastering control : yes
Power management : yes
Throttling control : yes
Limit interface : yes
Active C-state : C0
C-states (incl. C0) : 4
Usage of state C1 : 6062 (0.0 %)
Usage of state C2 : 15254283 (67.6 %)
Usage of state C3 : 2673667 (11.8 %)
T-state count : 8
Active T-state : T8
Thermal zone 1 : ok, 52 C
Trip points :
-------------
critical (S5): 127 C
Thermal zone 2 : ok, 53 C
Trip points :
-------------
critical (S5): 99 C
passive: 95 C: tc1=5 tc2=4 tsp=600 devices=CPU0 CPU1
Device S-state Status Sysfs node
---------------------------------------
1. LID S3 *enabled
2. SLPB S3 *enabled
3. EXP0 S4 disabled pci:0000:00:1c.0
4. EXP1 S4 disabled pci:0000:00:1c.1
5. EXP2 S4 disabled pci:0000:00:1c.2
6. EXP3 S4 disabled pci:0000:00:1c.3
7. PCI1 S4 disabled pci:0000:00:1e.0
8. USB0 S3 disabled pci:0000:00:1d.0
9. USB1 S3 disabled pci:0000:00:1d.1
10. USB2 S3 disabled pci:0000:00:1d.2
11. USB7 S3 disabled pci:0000:00:1d.7
12. HDEF S4 disabled pci:0000:00:1b.0
[-- Attachment #4: Type: text/plain, Size: 147 bytes --]
_______________________________________________
Cpufreq mailing list
Cpufreq@lists.linux.org.uk
http://lists.linux.org.uk/mailman/listinfo/cpufreq
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: CPU-Frequency limited to lowest available frequency while under load
2007-10-30 10:23 CPU-Frequency limited to lowest available frequency while under load Ferdinand Hübner
@ 2007-10-31 13:28 ` Thomas Renninger
2007-11-01 18:07 ` Ferdinand Hübner
0 siblings, 1 reply; 6+ messages in thread
From: Thomas Renninger @ 2007-10-31 13:28 UTC (permalink / raw)
To: Ferdinand Hübner; +Cc: cpufreq
On Tue, 2007-10-30 at 11:23 +0100, Ferdinand Hübner wrote:
> Hello,
>
> since I've upgraded to 2.6.23, the current frequency scaling policy is
> being changed whenever the CPU is under load.
> My CPU is a Core2Duo T7200, frequency steps: 2.00 GHz, 1.67 GHz, 1.33
> GHz, 1000 MHz
> I'm using the acpi-cpufreq driver and am setting the governor to
> 'ondemand' via cpufrequtils.
> When the system is booted, the scaling works as expected, the partial
> output from cpufreq-info:
>
> current policy: frequency should be within 1000 MHz and 2.00 GHz.
>
> However, when I start compiling something the policy is being changed to
> the following:
>
> current policy: frequency should be within 1000 MHz and 1000 MHz.
>
> This problem didn't exist with kernels prior to 2.6.23 (I was using
> gentoo-sources most of the time), same behaviour as with 2.6.23 can be
> observed with 2.6.24-rc1.
>
> I'm not entirely sure if this is a problem with cpufreq, so I apologize
> if this is not the right place to ask for help.
>
> Anyway, everytime the maximum CPU frequency is being changed, I receive
> the following ACPI events a few seconds afterwards (these events are not
> being handled)
>
> processor CPU0 00000080 00000003
> processor CPU1 00000080 00000003
>
> Setting the maximum frequency back to 2GHz (cpufreq-set -u 2000MHz) has
> either no effect at all, or is being reverted to 1GHz 30 seconds after that.
> The 'performance' governor is showing the same behaviour.
>
> I've attached my kernel config for ACPI/CPUFREQ and the output from
> acpitool -e.
>
> What can I do to get the "old" behaviour back? I just want the maximum
> frequency to stay at 2GHz...
It can be:
1) frequency limited by BIOS through _PPC
2) frequency reduced by thermal passive limit
3) some really odd cpufreq core bug
>From the last bugs occurring in this area I expect it's 1.
You should add a printk in drivers/acpi/processor_perflib.c
acpi_processor_get_platform_limit():
status = acpi_evaluate_integer(pr->handle, "_PPC", NULL, &ppc);
and print out the ppc value here, best after the checks whether this
call succeeded.
This should be picked up in cpufreq debug output as _PPC often caused
cpufreq problems. A quick look tells me that it is a bit ugly to use
cpufreq debug syntax in acpi layer, but it should be possible and
appropriate.
If _PPC is 0 all freqs are allowed, if it is 1 the highest freq is not
allowed anymore..., so this should always be 0 when working on AC power.
If it is this it could be that:
- ACPI is confused
- It is intended by BIOS (are you working on battery -> look up
your BIOS options, maybe you can modify anything related)
- _PPC is wrong at init (or later) and the value is not reevaluated
at later point
- ...
Maybe you should open a bugreport on http://bugzilla.kernel.org, pls add
me to CC then.
Thomas
> Thank you,
>
> Ferdinand
>
> plain text document attachment (kernel-config.txt)
> #
> # Power management options (ACPI, APM)
> #
> CONFIG_PM=y
> # CONFIG_PM_LEGACY is not set
> # CONFIG_PM_DEBUG is not set
> CONFIG_PM_SLEEP_SMP=y
> CONFIG_PM_SLEEP=y
> CONFIG_SUSPEND_SMP_POSSIBLE=y
> CONFIG_SUSPEND=y
> CONFIG_HIBERNATION_SMP_POSSIBLE=y
> # CONFIG_HIBERNATION is not set
> CONFIG_ACPI=y
> CONFIG_ACPI_SLEEP=y
> # CONFIG_ACPI_PROCFS is not set
> CONFIG_ACPI_PROC_EVENT=y
> CONFIG_ACPI_BUTTON=y
> # CONFIG_ACPI_VIDEO is not set
> CONFIG_ACPI_FAN=y
> CONFIG_ACPI_DOCK=y
> # CONFIG_ACPI_BAY is not set
> CONFIG_ACPI_PROCESSOR=y
> CONFIG_ACPI_HOTPLUG_CPU=y
> CONFIG_ACPI_THERMAL=y
> # CONFIG_ACPI_ASUS is not set
> # CONFIG_ACPI_TOSHIBA is not set
> CONFIG_ACPI_BLACKLIST_YEAR=2001
> CONFIG_ACPI_DEBUG=y
> # CONFIG_ACPI_DEBUG_FUNC_TRACE is not set
> CONFIG_ACPI_EC=y
> CONFIG_ACPI_POWER=y
> CONFIG_ACPI_SYSTEM=y
> CONFIG_X86_PM_TIMER=y
> CONFIG_ACPI_CONTAINER=y
> # CONFIG_APM is not set
>
> #
> # CPU Frequency scaling
> #
> CONFIG_CPU_FREQ=y
> CONFIG_CPU_FREQ_TABLE=y
> CONFIG_CPU_FREQ_DEBUG=y
> # CONFIG_CPU_FREQ_STAT is not set
> # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
> # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
> CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
> # CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
> CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
> CONFIG_CPU_FREQ_GOV_POWERSAVE=y
> # CONFIG_CPU_FREQ_GOV_USERSPACE is not set
> CONFIG_CPU_FREQ_GOV_ONDEMAND=y
> CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
>
> #
> # CPUFreq processor drivers
> #
> CONFIG_X86_ACPI_CPUFREQ=y
> # CONFIG_X86_POWERNOW_K6 is not set
> # CONFIG_X86_POWERNOW_K7 is not set
> # CONFIG_X86_POWERNOW_K8 is not set
> # CONFIG_X86_GX_SUSPMOD is not set
> # CONFIG_X86_SPEEDSTEP_CENTRINO is not set
> # CONFIG_X86_SPEEDSTEP_ICH is not set
> # CONFIG_X86_SPEEDSTEP_SMI is not set
> # CONFIG_X86_P4_CLOCKMOD is not set
> # CONFIG_X86_CPUFREQ_NFORCE2 is not set
> # CONFIG_X86_LONGRUN is not set
> # CONFIG_X86_LONGHAUL is not set
> # CONFIG_X86_E_POWERSAVER is not set
>
> #
> # shared options
> #
> # CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set
> # CONFIG_X86_SPEEDSTEP_LIB is not set
> CONFIG_CPU_IDLE=y
> CONFIG_CPU_IDLE_GOV_LADDER=y
> CONFIG_CPU_IDLE_GOV_MENU=y
> plain text document attachment (acpitool.txt)
> Kernel version : 2.6.24-rc1 - ACPI version : \x182.6
> -----------------------------------------------------------
> Battery status : <not available>
>
> AC adapter : <not available>
> Fan : enabled
> Fan Speed : 3507 RPM
>
> CPU type : Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz
> Min/Max frequency : 1000/1000 MHz
> Current frequency : 1000 MHz
> Frequency governor : ondemand
> Freq. scaling driver : acpi-cpufreq
> Cache size : 4096 KB
> Bogomips : 4023.70
> Bogomips : 3990.04
>
> # of CPU's found : 2
>
> Processor ID : 0
> Bus mastering control : yes
> Power management : yes
> Throttling control : yes
> Limit interface : yes
> Active C-state : C0
> C-states (incl. C0) : 4
> Usage of state C1 : 4148 (0.0 %)
> Usage of state C2 : 13181091 (74.0 %)
> Usage of state C3 : 4636873 (26.0 %)
> T-state count : 8
> Active T-state : T8
>
>
> Processor ID : 1
> Bus mastering control : yes
> Power management : yes
> Throttling control : yes
> Limit interface : yes
> Active C-state : C0
> C-states (incl. C0) : 4
> Usage of state C1 : 6062 (0.0 %)
> Usage of state C2 : 15254283 (67.6 %)
> Usage of state C3 : 2673667 (11.8 %)
> T-state count : 8
> Active T-state : T8
>
>
>
> Thermal zone 1 : ok, 52 C
> Trip points :
> -------------
> critical (S5): 127 C
>
> Thermal zone 2 : ok, 53 C
> Trip points :
> -------------
> critical (S5): 99 C
> passive: 95 C: tc1=5 tc2=4 tsp=600 devices=CPU0 CPU1
>
>
> Device S-state Status Sysfs node
> ---------------------------------------
> 1. LID S3 *enabled
> 2. SLPB S3 *enabled
> 3. EXP0 S4 disabled pci:0000:00:1c.0
> 4. EXP1 S4 disabled pci:0000:00:1c.1
> 5. EXP2 S4 disabled pci:0000:00:1c.2
> 6. EXP3 S4 disabled pci:0000:00:1c.3
> 7. PCI1 S4 disabled pci:0000:00:1e.0
> 8. USB0 S3 disabled pci:0000:00:1d.0
> 9. USB1 S3 disabled pci:0000:00:1d.1
> 10. USB2 S3 disabled pci:0000:00:1d.2
> 11. USB7 S3 disabled pci:0000:00:1d.7
> 12. HDEF S4 disabled pci:0000:00:1b.0
> _______________________________________________
> Cpufreq mailing list
> Cpufreq@lists.linux.org.uk
> http://lists.linux.org.uk/mailman/listinfo/cpufreq
_______________________________________________
Cpufreq mailing list
Cpufreq@lists.linux.org.uk
http://lists.linux.org.uk/mailman/listinfo/cpufreq
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: CPU-Frequency limited to lowest available frequency while under load
2007-10-31 13:28 ` Thomas Renninger
@ 2007-11-01 18:07 ` Ferdinand Hübner
2007-11-01 18:31 ` Thomas Renninger
0 siblings, 1 reply; 6+ messages in thread
From: Ferdinand Hübner @ 2007-11-01 18:07 UTC (permalink / raw)
To: trenn; +Cc: cpufreq
[-- Attachment #1: Type: text/plain, Size: 2661 bytes --]
Thomas Renninger wrote:
> It can be:
> 1) frequency limited by BIOS through _PPC
> 2) frequency reduced by thermal passive limit
> 3) some really odd cpufreq core bug
>
>>From the last bugs occurring in this area I expect it's 1.
>
> You should add a printk in drivers/acpi/processor_perflib.c
> acpi_processor_get_platform_limit():
> status = acpi_evaluate_integer(pr->handle, "_PPC", NULL, &ppc);
> and print out the ppc value here, best after the checks whether this
> call succeeded.
>
> This should be picked up in cpufreq debug output as _PPC often caused
> cpufreq problems. A quick look tells me that it is a bit ugly to use
> cpufreq debug syntax in acpi layer, but it should be possible and
> appropriate.
>
> If _PPC is 0 all freqs are allowed, if it is 1 the highest freq is not
> allowed anymore..., so this should always be 0 when working on AC power.
I have applied the patch and ran some tests with cpufreq core debugging
enabled. What I receive is the following output:
cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
cpufreq-core: setting new policy for CPU 0: 1000000 - 2000000 kHz
freq-table: request for verification of policy (1000000 - 2000000 kHz)
for cpu 0
freq-table: verification lead to (1000000 - 2000000 kHz) for cpu 0
freq-table: request for verification of policy (1000000 - 1000000 kHz)
for cpu 0
freq-table: verification lead to (1000000 - 1000000 kHz) for cpu 0
cpufreq-core: new min and max freqs are 1000000 - 1000000 kHz
I repeated the test a couple of times and the _PPC values have always
been 0 except for the last test I did. The value was 3 in the last test.
Does that mean that the BIOS is partially responsible?
> If it is this it could be that:
> - ACPI is confused
> - It is intended by BIOS (are you working on battery -> look up
> your BIOS options, maybe you can modify anything related)
> - _PPC is wrong at init (or later) and the value is not reevaluated
I was not working on battery, the _PPC values were 0 at init. I re-ran
the tests whithout X or acpid enabled and the problem did not happen
without acpid/X. So I guess the problem has something to do with ACPI?
I tried to investigate further with acpi debugging, but I am completely
overwhelmed with acpi's debugging output. I have no clue how to read
something useful from it.
I have attached parts of /var/log/messages with the debugging output
from cpufreq (I did not include the acpi part).
> Maybe you should open a bugreport on http://bugzilla.kernel.org, pls add
> me to CC then.
I would start with posting at the acpi mailing list, maybe someone can
help me debugging...
Thank you for your help,
Ferdinand
[-- Attachment #2: messages.txt --]
[-- Type: text/plain, Size: 13525 bytes --]
Nov 1 09:59:38 panther cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
Nov 1 09:59:42 panther printk: 89 messages suppressed.
Nov 1 09:59:42 panther cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
Nov 1 09:59:47 panther printk: 223 messages suppressed.
Nov 1 09:59:47 panther cpufreq-core: target for CPU 0: 1838571 kHz, relation 0
Nov 1 09:59:52 panther printk: 182 messages suppressed.
Nov 1 09:59:52 panther cpufreq-core: target for CPU 0: 1381714 kHz, relation 0
Nov 1 09:59:57 panther printk: 168 messages suppressed.
Nov 1 09:59:57 panther cpufreq-core: target for CPU 0: 1400000 kHz, relation 0
Nov 1 10:00:02 panther printk: 170 messages suppressed.
Nov 1 10:00:02 panther cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
Nov 1 10:00:02 panther cpufreq-core: setting new policy for CPU 0: 1000000 - 2000000 kHz
Nov 1 10:00:02 panther freq-table: request for verification of policy (1000000 - 2000000 kHz) for cpu 0
Nov 1 10:00:02 panther freq-table: verification lead to (1000000 - 2000000 kHz) for cpu 0
Nov 1 10:00:02 panther freq-table: request for verification of policy (1000000 - 1000000 kHz) for cpu 0
Nov 1 10:00:02 panther freq-table: verification lead to (1000000 - 1000000 kHz) for cpu 0
Nov 1 10:00:02 panther cpufreq-core: new min and max freqs are 1000000 - 1000000 kHz
Nov 1 10:00:02 panther cpufreq-core: governor: change or update limits
Nov 1 10:00:02 panther cpufreq-core: __cpufreq_governor for CPU 0, event 3
Nov 1 10:00:02 panther cpufreq-core: target for CPU 0: 1000000 kHz, relation 1
Nov 1 10:00:02 panther freq-table: request for target 1000000 kHz (relation: 1) for cpu 0
Nov 1 10:00:02 panther freq-table: target is 3 (1000000 kHz, 3)
Nov 1 10:00:02 panther cpufreq-core: notification 0 of frequency transition to 1000000 kHz
Nov 1 10:00:02 panther cpufreq-core: notification 0 of frequency transition to 1000000 kHz
Nov 1 10:00:02 panther cpufreq-core: notification 1 of frequency transition to 1000000 kHz
Nov 1 10:00:02 panther cpufreq-core: notification 1 of frequency transition to 1000000 kHz
Nov 1 10:00:02 panther acpid: received event "processor CPU0 00000080 00000003"
Nov 1 10:00:02 panther acpid: notifying client 5849[0:0]
Nov 1 10:00:02 panther acpid: executing action "/etc/acpi/default.sh processor CPU0 00000080 00000003"
Nov 1 10:00:02 panther cpufreq-core: setting new policy for CPU 0: 1000000 - 2000000 kHz
Nov 1 10:00:02 panther freq-table: request for verification of policy (1000000 - 2000000 kHz) for cpu 0
Nov 1 10:00:02 panther freq-table: verification lead to (1000000 - 2000000 kHz) for cpu 0
Nov 1 10:00:02 panther freq-table: request for verification of policy (1000000 - 1000000 kHz) for cpu 0
Nov 1 10:00:02 panther freq-table: verification lead to (1000000 - 1000000 kHz) for cpu 0
Nov 1 10:00:02 panther cpufreq-core: new min and max freqs are 1000000 - 1000000 kHz
Nov 1 10:00:02 panther cpufreq-core: governor: change or update limits
Nov 1 10:00:02 panther cpufreq-core: __cpufreq_governor for CPU 0, event 3
Nov 1 10:00:02 panther logger: ACPI event unhandled: processor CPU0 00000080 00000003
Nov 1 10:00:02 panther acpid: action exited with status 0
Nov 1 10:00:02 panther acpid: completed event "processor CPU0 00000080 00000003"
Nov 1 10:00:02 panther acpid: received event "processor CPU1 00000080 00000003"
Nov 1 10:00:02 panther acpid: notifying client 5849[0:0]
Nov 1 10:00:02 panther acpid: executing action "/etc/acpi/default.sh processor CPU1 00000080 00000003"
Nov 1 10:00:02 panther logger: ACPI event unhandled: processor CPU1 00000080 00000003
Nov 1 10:00:02 panther acpid: action exited with status 0
Nov 1 10:00:02 panther acpid: completed event "processor CPU1 00000080 00000003"
Nov 1 10:00:27 panther printk: 16 messages suppressed.
Nov 1 10:00:27 panther cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
Nov 1 10:00:27 panther cpufreq-core: updating policy for CPU 0
Nov 1 10:00:27 panther cpufreq-core: setting new policy for CPU 0: 1000000 - 2000000 kHz
Nov 1 10:00:27 panther freq-table: request for verification of policy (1000000 - 2000000 kHz) for cpu 0
Nov 1 10:00:27 panther freq-table: verification lead to (1000000 - 2000000 kHz) for cpu 0
Nov 1 10:00:27 panther freq-table: request for verification of policy (1000000 - 2000000 kHz) for cpu 0
Nov 1 10:00:27 panther freq-table: verification lead to (1000000 - 2000000 kHz) for cpu 0
Nov 1 10:00:27 panther cpufreq-core: new min and max freqs are 1000000 - 2000000 kHz
Nov 1 10:00:27 panther cpufreq-core: governor: change or update limits
Nov 1 10:00:27 panther cpufreq-core: __cpufreq_governor for CPU 0, event 3
Nov 1 10:00:27 panther acpid: received event "processor CPU0 00000080 00000000"
Nov 1 10:00:27 panther acpid: notifying client 5849[0:0]
Nov 1 10:00:27 panther acpid: executing action "/etc/acpi/default.sh processor CPU0 00000080 00000000"
Nov 1 10:00:27 panther cpufreq-core: CPU 1: _PPC is 0 - frequency not limited
Nov 1 10:00:27 panther cpufreq-core: updating policy for CPU 1
Nov 1 10:00:27 panther cpufreq-core: Warning: CPU frequency out of sync: cpufreq and timing core thinks of 1000000, is 0 kHz.
Nov 1 10:00:27 panther cpufreq-core: setting new policy for CPU 0: 1000000 - 2000000 kHz
Nov 1 10:00:27 panther freq-table: request for verification of policy (1000000 - 2000000 kHz) for cpu 0
Nov 1 10:00:27 panther freq-table: verification lead to (1000000 - 2000000 kHz) for cpu 0
Nov 1 10:00:27 panther freq-table: request for verification of policy (1000000 - 2000000 kHz) for cpu 0
Nov 1 10:00:27 panther freq-table: verification lead to (1000000 - 2000000 kHz) for cpu 0
Nov 1 10:00:27 panther cpufreq-core: new min and max freqs are 1000000 - 2000000 kHz
Nov 1 10:00:27 panther cpufreq-core: governor: change or update limits
Nov 1 10:00:27 panther cpufreq-core: __cpufreq_governor for CPU 0, event 3
Nov 1 10:00:27 panther logger: ACPI event unhandled: processor CPU0 00000080 00000000
Nov 1 10:00:27 panther acpid: action exited with status 0
Nov 1 10:00:27 panther acpid: completed event "processor CPU0 00000080 00000000"
Nov 1 10:00:27 panther acpid: received event "processor CPU1 00000080 00000000"
Nov 1 10:00:27 panther acpid: notifying client 5849[0:0]
Nov 1 10:00:27 panther acpid: executing action "/etc/acpi/default.sh processor CPU1 00000080 00000000"
Nov 1 10:00:27 panther logger: ACPI event unhandled: processor CPU1 00000080 00000000
Nov 1 10:00:27 panther acpid: action exited with status 0
Nov 1 10:00:27 panther acpid: completed event "processor CPU1 00000080 00000000"
Nov 1 10:00:42 panther printk: 2 messages suppressed.
Nov 1 10:00:42 panther cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
Nov 1 10:00:42 panther freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
Nov 1 10:00:42 panther freq-table: target is 0 (2000000 kHz, 0)
-----------------
Nov 1 10:38:05 panther cpufreq-core: CPU 0: _PPC is 3 - frequency limited
Nov 1 10:38:05 panther cpufreq-core: setting new policy for CPU 0: 1000000 - 2000000 kHz
Nov 1 10:38:05 panther freq-table: request for verification of policy (1000000 - 2000000 kHz) for cpu 0
Nov 1 10:38:05 panther freq-table: verification lead to (1000000 - 2000000 kHz) for cpu 0
Nov 1 10:38:05 panther freq-table: request for verification of policy (1000000 - 1000000 kHz) for cpu 0
Nov 1 10:38:05 panther freq-table: verification lead to (1000000 - 1000000 kHz) for cpu 0
Nov 1 10:38:05 panther cpufreq-core: new min and max freqs are 1000000 - 1000000 kHz
Nov 1 10:38:05 panther cpufreq-core: governor: change or update limits
Nov 1 10:38:05 panther cpufreq-core: __cpufreq_governor for CPU 0, event 3
Nov 1 10:38:05 panther cpufreq-core: target for CPU 0: 1000000 kHz, relation 1
Nov 1 10:38:05 panther freq-table: request for target 1000000 kHz (relation: 1) for cpu 0
Nov 1 10:38:05 panther acpid: received event "processor CPU0 00000080 00000003"
Nov 1 10:38:05 panther acpid: notifying client 1676[0:0]
Nov 1 10:38:05 panther acpid: executing action "/etc/acpi/default.sh processor CPU0 00000080 00000003"
Nov 1 10:38:05 panther freq-table: target is 3 (1000000 kHz, 3)
Nov 1 10:38:05 panther cpufreq-core: notification 0 of frequency transition to 1000000 kHz
Nov 1 10:38:05 panther cpufreq-core: notification 0 of frequency transition to 1000000 kHz
Nov 1 10:38:05 panther cpufreq-core: notification 1 of frequency transition to 1000000 kHz
Nov 1 10:38:05 panther cpufreq-core: notification 1 of frequency transition to 1000000 kHz
Nov 1 10:38:05 panther cpufreq-core: setting new policy for CPU 0: 1000000 - 2000000 kHz
Nov 1 10:38:05 panther freq-table: request for verification of policy (1000000 - 2000000 kHz) for cpu 0
Nov 1 10:38:05 panther freq-table: verification lead to (1000000 - 2000000 kHz) for cpu 0
Nov 1 10:38:05 panther freq-table: request for verification of policy (1000000 - 1000000 kHz) for cpu 0
Nov 1 10:38:05 panther freq-table: verification lead to (1000000 - 1000000 kHz) for cpu 0
Nov 1 10:38:05 panther cpufreq-core: new min and max freqs are 1000000 - 1000000 kHz
Nov 1 10:38:05 panther cpufreq-core: governor: change or update limits
Nov 1 10:38:05 panther cpufreq-core: __cpufreq_governor for CPU 0, event 3
Nov 1 10:38:05 panther logger: ACPI event unhandled: processor CPU0 00000080 00000003
Nov 1 10:38:05 panther acpid: action exited with status 0
Nov 1 10:38:05 panther acpid: completed event "processor CPU0 00000080 00000003"
Nov 1 10:38:05 panther acpid: received event "processor CPU1 00000080 00000003"
Nov 1 10:38:05 panther acpid: notifying client 1676[0:0]
Nov 1 10:38:05 panther acpid: executing action "/etc/acpi/default.sh processor CPU1 00000080 00000003"
Nov 1 10:38:05 panther logger: ACPI event unhandled: processor CPU1 00000080 00000003
Nov 1 10:38:05 panther acpid: action exited with status 0
Nov 1 10:38:05 panther acpid: completed event "processor CPU1 00000080 00000003"
Nov 1 10:39:28 panther [fglrx:firegl_lock] *ERROR* Process 2822 is using illegal context 0x00000003
Nov 1 10:39:54 panther su[1821]: pam_unix(su:session): session closed for user root
Nov 1 10:41:17 panther printk: 6 messages suppressed.
Nov 1 10:41:17 panther cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
Nov 1 10:41:17 panther cpufreq-core: updating policy for CPU 0
Nov 1 10:41:17 panther cpufreq-core: setting new policy for CPU 0: 1000000 - 2000000 kHz
Nov 1 10:41:17 panther freq-table: request for verification of policy (1000000 - 2000000 kHz) for cpu 0
Nov 1 10:41:17 panther freq-table: verification lead to (1000000 - 2000000 kHz) for cpu 0
Nov 1 10:41:17 panther freq-table: request for verification of policy (1000000 - 2000000 kHz) for cpu 0
Nov 1 10:41:17 panther freq-table: verification lead to (1000000 - 2000000 kHz) for cpu 0
Nov 1 10:41:17 panther cpufreq-core: new min and max freqs are 1000000 - 2000000 kHz
Nov 1 10:41:17 panther cpufreq-core: governor: change or update limits
Nov 1 10:41:17 panther cpufreq-core: __cpufreq_governor for CPU 0, event 3
Nov 1 10:41:17 panther acpid: received event "processor CPU0 00000080 00000000"
Nov 1 10:41:17 panther acpid: notifying client 1676[0:0]
Nov 1 10:41:17 panther acpid: executing action "/etc/acpi/default.sh processor CPU0 00000080 00000000"
Nov 1 10:41:17 panther cpufreq-core: CPU 1: _PPC is 0 - frequency not limited
Nov 1 10:41:17 panther cpufreq-core: updating policy for CPU 1
Nov 1 10:41:17 panther cpufreq-core: Warning: CPU frequency out of sync: cpufreq and timing core thinks of 1000000, is 0 kHz.
Nov 1 10:41:17 panther cpufreq-core: notification 0 of frequency transition to 0 kHz
Nov 1 10:41:17 panther cpufreq-core: notification 1 of frequency transition to 0 kHz
Nov 1 10:41:17 panther cpufreq-core: setting new policy for CPU 0: 1000000 - 2000000 kHz
Nov 1 10:41:17 panther freq-table: request for verification of policy (1000000 - 2000000 kHz) for cpu 0
Nov 1 10:41:17 panther freq-table: verification lead to (1000000 - 2000000 kHz) for cpu 0
Nov 1 10:41:17 panther freq-table: request for verification of policy (1000000 - 2000000 kHz) for cpu 0
Nov 1 10:41:17 panther freq-table: verification lead to (1000000 - 2000000 kHz) for cpu 0
Nov 1 10:41:17 panther cpufreq-core: new min and max freqs are 1000000 - 2000000 kHz
Nov 1 10:41:17 panther cpufreq-core: governor: change or update limits
Nov 1 10:41:17 panther cpufreq-core: __cpufreq_governor for CPU 0, event 3
Nov 1 10:41:17 panther logger: ACPI event unhandled: processor CPU0 00000080 00000000
Nov 1 10:41:17 panther acpid: action exited with status 0
Nov 1 10:41:17 panther acpid: completed event "processor CPU0 00000080 00000000"
Nov 1 10:41:17 panther acpid: received event "processor CPU1 00000080 00000000"
Nov 1 10:41:17 panther acpid: notifying client 1676[0:0]
Nov 1 10:41:17 panther acpid: executing action "/etc/acpi/default.sh processor CPU1 00000080 00000000"
Nov 1 10:41:17 panther logger: ACPI event unhandled: processor CPU1 00000080 00000000
Nov 1 10:41:17 panther acpid: action exited with status 0
Nov 1 10:41:17 panther acpid: completed event "processor CPU1 00000080 00000000"
Nov 1 10:41:17 panther cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
Nov 1 10:41:17 panther freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
Nov 1 10:41:17 panther freq-table: target is 0 (2000000 kHz, 0)
Nov 1 10:41:22 panther printk: 550 messages suppressed.
Nov 1 10:41:22 panther cpufreq-core: target for CPU 0: 1188571 kHz, relation 0
[-- Attachment #3: Type: text/plain, Size: 147 bytes --]
_______________________________________________
Cpufreq mailing list
Cpufreq@lists.linux.org.uk
http://lists.linux.org.uk/mailman/listinfo/cpufreq
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: CPU-Frequency limited to lowest available frequency while under load
2007-11-01 18:07 ` Ferdinand Hübner
@ 2007-11-01 18:31 ` Thomas Renninger
2007-11-01 18:36 ` Jarod Wilson
0 siblings, 1 reply; 6+ messages in thread
From: Thomas Renninger @ 2007-11-01 18:31 UTC (permalink / raw)
To: Ferdinand Hübner; +Cc: cpufreq
Hi Ferdinand,
I cut down the mail a bit...
On Thu, 2007-11-01 at 19:07 +0100, Ferdinand Hübner wrote:
> Thomas Renninger wrote:
>
> > It can be:
> > 1) frequency limited by BIOS through _PPC
> > 2) frequency reduced by thermal passive limit
> > 3) some really odd cpufreq core bug
> >
> >>From the last bugs occurring in this area I expect it's 1.
> I repeated the test a couple of times and the _PPC values have always
> been 0 except for the last test I did. The value was 3 in the last test.
> Does that mean that the BIOS is partially responsible?
If the value is 3, the highest three freqs are not allowed by BIOS.
This may be intended, probably not.
IMO best is you open a bug at http://bugzilla.kernel.org to collect info
at one place..., for now I'd assign it to the ACPI component.
acpidump output should be most important atm, pls attach it there and
take me into CC list.
Is it possible for you to reproduce this easily?
Maybe something you noticed like: it always happens after x mins or
after loading module y...
You could also try to not load other ACPI modules: battery, thermal,
button, fan, ac.
Maybe it does not happen then anymore?
Do you use hwmon, thermal sensor modules?
Thomas
_______________________________________________
Cpufreq mailing list
Cpufreq@lists.linux.org.uk
http://lists.linux.org.uk/mailman/listinfo/cpufreq
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: CPU-Frequency limited to lowest available frequency while under load
2007-11-01 18:31 ` Thomas Renninger
@ 2007-11-01 18:36 ` Jarod Wilson
2007-11-06 16:01 ` Ferdinand Hübner
0 siblings, 1 reply; 6+ messages in thread
From: Jarod Wilson @ 2007-11-01 18:36 UTC (permalink / raw)
To: Ferdinand Hübner; +Cc: cpufreq
[-- Attachment #1.1: Type: text/plain, Size: 1873 bytes --]
Thomas Renninger wrote:
> Hi Ferdinand,
>
> I cut down the mail a bit...
> On Thu, 2007-11-01 at 19:07 +0100, Ferdinand Hübner wrote:
>> Thomas Renninger wrote:
>>
>>> It can be:
>>> 1) frequency limited by BIOS through _PPC
>>> 2) frequency reduced by thermal passive limit
>>> 3) some really odd cpufreq core bug
>>>
>>> >From the last bugs occurring in this area I expect it's 1.
>
>> I repeated the test a couple of times and the _PPC values have always
>> been 0 except for the last test I did. The value was 3 in the last test.
>> Does that mean that the BIOS is partially responsible?
> If the value is 3, the highest three freqs are not allowed by BIOS.
> This may be intended, probably not.
>
> IMO best is you open a bug at http://bugzilla.kernel.org to collect info
> at one place..., for now I'd assign it to the ACPI component.
>
> acpidump output should be most important atm, pls attach it there and
> take me into CC list.
>
> Is it possible for you to reproduce this easily?
> Maybe something you noticed like: it always happens after x mins or
> after loading module y...
> You could also try to not load other ACPI modules: battery, thermal,
> button, fan, ac.
> Maybe it does not happen then anymore?
I didn't pay much attention to earlier posts in this thread, so pardon
if this has already been covered, but...
I had a similar sounding case reported in the Red Hat bugzilla, where a
Dell laptop wouldn't scale above its minimum frequency if the system was
running on a travel charger. This turned out to be a limitation imposed
intentionally by the system BIOS (and documented somewhere on Dell's web
site). On battery and on the normal charger, the same system had no
problems whatsoever.
Just throwing it out there, ignore me if its irrelevant. :)
--
Jarod Wilson
jwilson@redhat.com
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
[-- Attachment #2: Type: text/plain, Size: 147 bytes --]
_______________________________________________
Cpufreq mailing list
Cpufreq@lists.linux.org.uk
http://lists.linux.org.uk/mailman/listinfo/cpufreq
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: CPU-Frequency limited to lowest available frequency while under load
2007-11-01 18:36 ` Jarod Wilson
@ 2007-11-06 16:01 ` Ferdinand Hübner
0 siblings, 0 replies; 6+ messages in thread
From: Ferdinand Hübner @ 2007-11-06 16:01 UTC (permalink / raw)
To: cpufreq
Jarod Wilson wrote:
> I didn't pay much attention to earlier posts in this thread, so pardon
> if this has already been covered, but...
>
> I had a similar sounding case reported in the Red Hat bugzilla, where a
> Dell laptop wouldn't scale above its minimum frequency if the system was
> running on a travel charger. This turned out to be a limitation imposed
> intentionally by the system BIOS (and documented somewhere on Dell's web
> site). On battery and on the normal charger, the same system had no
> problems whatsoever.
>
> Just throwing it out there, ignore me if its irrelevant. :)
>
I gave it a shot and did a BIOS update and played around with the
options in the BIOS.
Now it does scale correctly... I should have tried that earlier, I did
not expect that, because I "only" did a kernel upgrade and did not touch
the BIOS in any way...
Thanks!
Ferdinand
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2007-11-06 16:01 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-10-30 10:23 CPU-Frequency limited to lowest available frequency while under load Ferdinand Hübner
2007-10-31 13:28 ` Thomas Renninger
2007-11-01 18:07 ` Ferdinand Hübner
2007-11-01 18:31 ` Thomas Renninger
2007-11-01 18:36 ` Jarod Wilson
2007-11-06 16:01 ` Ferdinand Hübner
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.