Bug 227845

Summary:	cpuspeed daemons cannot start
Product:	Red Hat Enterprise Linux 4	Reporter:	Linda Wang <lwang>
Component:	kernel-utils	Assignee:	Jarod Wilson <jarod>
Status:	CLOSED NOTABUG	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	CC:	jbarton, lizhang, rbiba, travnicj-priv
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-05-09 13:28:31 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:
Bug Depends On:	184469
Bug Blocks:

Comment 1 Jarod Wilson 2007-02-08 15:36:10 UTC

+++ This bug was initially created as a clone of Bug #184469 +++

I'm fairly confident the cpuspeed initscript is operating as intended here. The
heart of the issue is that cpuspeed is installed by default and chkconfig'd on
for all systems. Since we have no way of knowing ahead of time if the system
actually supports frequency scaling or not, we opt to fail to start up silently
to avoid alarming anyone. These appear to be simple cases of cpuspeed silently
exiting because the systems they're being run on in this case don't support cpu
frequency scaling.

Folks are welcome to post their /proc/cpuinfo and dmesg output after booting
with cpufreq.debug=7 added to their kernel boot params to try to convince me
otherwise though. :)

Comment 2 RHEL Program Management 2007-05-09 07:49:32 UTC

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

Comment 3 Jarod Wilson 2007-05-09 13:28:31 UTC

3mo. w/o any feedback contrary to my assertion that cpuspeed is operating as
intended, closing NOTABUG.