Bug 455124 - cpuspeed not working
cpuspeed not working
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: cpuspeed (Show other bugs)
9
x86_64 Linux
low Severity low
: ---
: ---
Assigned To: Jarod Wilson
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-12 07:48 EDT by Sander
Modified: 2008-07-12 21:55 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-07-12 21:55:04 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Sander 2008-07-12 07:48:59 EDT
Description of problem:
The CPU is always running on the full clock speed. Cpuspeed is unable to start.

Version-Release number of selected component (if applicable):
cpuspeed v1.2.1

How reproducible:

Steps to Reproduce:
1. Boot system
2. Try to start cpuspeed (service cpuspeed start)
  
Actual results:
[root] service cpuspeed status
cpuspeed is stopped

Expected results:
[root] service cpuspeed status
cpuspeed started

Additional info:
Because cpuspeed is unable to start I tried to insert the module manually.

[root] modprobe acpi-cpufreq
FATAL: Error inserting acpi_cpufreq
(/lib/modules/2.6.25.9-76.fc9.x86_64/kernel/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.ko):
No such device

[root] ls /lib/modules/2.6.25.9-76.fc9.x86_64/kernel/arch/x86/kernel/cpu/cpufreq
acpi-cpufreq.ko  powernow-k8.ko

System is unable to find acpi_cpufreq.ko, but it does exist.

* cpuinfo
Intel(R) Core(TM)2 Duo CPU     E6750  @ 2.66GHz
Comment 1 Jarod Wilson 2008-07-12 21:55:04 EDT
That cpu should be using acpi-cpufreq. The "No such device" upon modprobing it
indicates either your bios is broken, or frequency scaling is disabled in the
bios. Please double-check your bios settings, and if they claim frequency
scaling is enabled, check for a bios update, apply it and see what you can see.
Chances are rather slim this is actually a software bug.

Note You need to log in before you can comment on or make changes to this bug.