Red Hat Bugzilla – Bug 616524
cpuspeed does not reset MIN/MAX values when config file is emptied
Last modified: 2013-04-15 05:09:37 EDT
+++ This bug was initially created as a clone of Bug #616507 +++ Description of problem: When MIN_SPEED (resp. MAX_SPEED) is set in /etc/sysconfig/cpuspeed, and then removed, /etc/init.d/cpuspeed does not reset the value to the CPU minimum (resp. maximum) frequency. Version-Release number of selected component (if applicable): cpuspeed-1.2.1-9.el5 How reproducible: Always Steps to Reproduce: 0. check CPU frequency using cat /proc/cpuinfo 1. Set MIN_SPEED in /etc/sysconfig/cpuspeed to a suitable value superior to the CPU's minimum frequency 2. restart cpuspeed 3. Unset MIN_SPEED (restore configuration file) 4. restart cpuspeed 5. check CPU frequency using cat /proc/cpuinfo Actual results: CPU frequency in step 5 is equal to the MIN_SPEED set at step 1. Expected results: CPU frequency in steps 0 and 5 are identical. Additional info: This is because the cpuspeed script does not reset the values when the {MIN_SPEED,MAX_SPEED} variables are empty. The original patch attached is for Fedora 13, a RHEL5 patch is coming shortly.
Created attachment 433223 [details] patch for /etc/init.d/cpuspeed patch for F13, applies cleanly on RHEL5.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Initscript fixed in CVS tag cpuspeed-1.2.1-10.el5.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: The /etc/sysconfig/cpuspeed configuration file allows a user to specify custom maximum (the "MAX_SPEED" option) and minimum (the "MIN_SPEED" option) clock speed limits. Prior to this update, when a user removed these custom settings from the configuration and restarted the service, the cpuspeed init script failed to reset these values to the hardware-specific limits. With this update, the init script has been adapted to ensure that when the minimum or maximum clock speed value is not specified, cpuspeed correctly uses the value reported by the CPU.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0502.html