0000698: cpufrequtils governor ondemand no longer works with kernel 2.6.32 on P4 proz

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0000698

IPFire 2.7

Addon

public

2010-07-29 14:15

2010-07-29 21:30

Reporter

jakumoto

Assigned To

Arne_F

Priority

normal

Severity

minor

Reproducibility

have not tried

Status

closed

Resolution

not fixable

Platform

i386

Linux

OS Version

2.5

Product Version

Core38

Target Version

Fixed in Version

Summary

0000698: cpufrequtils governor ondemand no longer works with kernel 2.6.32 on P4 proz

Description

After upgrading to Core 38, cpufrequtils no longer work with ondemand governor!

Used module: P4-clockmod

The only working governors are performance, userspace and powersave!

I think it is related to this kernel bug , but I found no hint to solve:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536183 [^]

dmesg brings:

ondemand governor failed, too long transition latency of HW, fallback to performance governor

after cpufreq-set -g ondemand

Any ideas ... ?

Steps To Reproduce

Installing Core 38 on 2 different machines with the same CPU leads to the same result!

Additional Information

cat /proc/cpuinfo
--------------------------------------
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Intel(R) Pentium(R) 4 CPU 2.00GHz
stepping : 4
cpu MHz : 2000.000
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
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 up pebs bts
bogomips : 3991.30
clflush size : 64
cache_alignment : 128
address sizes : 36 bits physical, 32 bits virtual
power management:
-----------------------------------------------------------

cpufreq-info

cpufrequtils 007: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  driver: p4-clockmod
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 10.00 ms.
  hardware limits: 250 MHz - 2.00 GHz
  available frequency steps: 250 MHz, 500 MHz, 750 MHz, 1000 MHz, 1.25 GHz, 1.50 GHz, 1.75 GHz, 2.00 GHz
  available cpufreq governors: userspace, powersave, ondemand, conservative, performance
  current policy: frequency should be within 250 MHz and 2.00 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency is 2.00 GHz (asserted by call to hardware).
----------------------------------------------------------------------

Notes
(0002187) Arne_F (administrator) 2010-07-29 21:29	The ondemand governor has a new check to block p4clockmod because it need to much time to switch and it don't really switch down the clock it activate only waitstates. This slowdown the processor significant but don't save much energy. (Only a bit because the north and southbridge habe lower load.

Issue History
Date Modified	Username	Field	Change
2010-07-29 14:15	jakumoto	New Issue
2010-07-29 21:29	Arne_F	Note Added: 0002187
2010-07-29 21:30	Arne_F	Status	new => closed
2010-07-29 21:30	Arne_F	Assigned To	=> Arne_F
2010-07-29 21:30	Arne_F	Resolution	open => not fixable

Relationships