Bug 235754

Summary: CPU scaling not working on Asus Z62Fm
Product: Red Hat Enterprise Linux 5 Reporter: rizo83
Component: kernelAssignee: Peter Martuccelli <peterm>
Status: CLOSED WONTFIX QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: low Docs Contact:
Priority: medium    
Version: 5.0CC: jfeeney, razvan.vilt
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-13 02:31:21 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 output w/ cpufreq.debug=7 added kernel parameters
none
RHEL using FC6 kernel -- cpu scaling working none

Description rizo83 2007-04-09 22:45:46 UTC
Description of problem: speedstep CPU scaling on Asus Z62Fm is not working. 
speedstep-smi states "No supported Intel CPU detected."  Although it works fine
with FC6 2.6.20 kernel.  Similar to FC6 bug
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=221070


Version-Release number of selected component (if applicable): RHEL Client 5 x86
kernel 2.6.18-8.el5 and 2.6.18-8.1.1.el5


How reproducible: Fresh install.

Comment 1 rizo83 2007-04-09 22:45:46 UTC
Created attachment 152072 [details]
dmesg output w/ cpufreq.debug=7 added kernel parameters

Comment 2 rizo83 2007-04-10 19:24:11 UTC
Created attachment 152175 [details]
RHEL using FC6 kernel -- cpu scaling working

Comment 3 Razvan Corneliu C.R. VILT 2007-05-30 12:28:37 UTC
It's the same on my HP nc8430 laptop. The CPU is an Intel Core 2 Duo T7200.

Comment 6 Brian Maly 2009-03-11 17:51:20 UTC
The CPU detection appears to be misdetecting the exact processor type/model.

This is with the i386 (32bit) or the x86_64 (64bit) kernel?

Comment 11 John Feeney 2013-11-13 02:31:21 UTC
This Bugzilla has been reviewed by Red Hat and is not planned on being
addressed in Red Hat Enterprise Linux 5, and therefore is being closed.
If this bug is critical to production systems, please contact your Red
Hat support representative and provide a sufficient business justification
in order to re-open it.