+++ 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. :)
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.
3mo. w/o any feedback contrary to my assertion that cpuspeed is operating as intended, closing NOTABUG.