Bug 203656

Summary: CPU frequency scaling does not work
Product: [Fedora] Fedora Reporter: Peter Eriksen <s022018>
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED NOTABUG QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-09-01 13:16:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg none

Description Peter Eriksen 2006-08-22 20:49:49 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.6) Gecko/20060808 Fedora/1.5.0.6-3 Firefox/1.5.0.6 pango-text

Description of problem:
After upgrading from FC5 the CPU scaling does not work any more.  At least that is what CPU Frequency Scaling Monitor 2.15.3 tells me, see below.

Version-Release number of selected component (if applicable):
2.6.17-1.2583.fc6 #1 SMP Tue Aug 22 00:29:50 EDT 2006 i686 i686 i386 GNU/Linux

How reproducible:
Always


Steps to Reproduce:
1. Add the CPU Monitor applet to the panel.

Actual Results:
CPU frequency scaling unsupported

You will not be able to modify the frequency of your machine.  Your machine may be misconfigured or not have hardware support for CPU frequency scaling.

Expected Results:


Additional info:
Comment 1 Peter Eriksen 2006-08-22 20:51:29 UTC 
Created attachment 134674 [details]
dmesg
Comment 2 Peter Eriksen 2006-09-01 13:16:15 UTC 
(In reply to comment #0)
> Description of problem:
> After upgrading from FC5 the CPU scaling does not work any more.  At least
that is what CPU Frequency Scaling Monitor 2.15.3 tells me, see below.

It seems to work now after the kernel upgrade of today.  I don't know if it was
that, or the command I ran before rebooting:
/sbin/modprobe cpufreq_ondemand

Anyway, it seems to work now, so please close this bug, or something.