RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 1029918 [details]
boot.log

Description of problem:
After the installation of RHEL-6.7-Snapshot-1, during booting into any rc mode list of error messages "/etc/rc5.d/S13cpuspeed: line91: echo: write error: Invalid argument" are seen.

Version-Release number of selected component (if applicable):
cpuspeed-1.5-20.el6_4

How reproducible:
Always while booting into rc modes like rc5, rc4, rc3, rc2 and rc1.

Steps to Reproduce:
1.Install RHEL-6.7-Snapshot-1
2.Boot into the installed OS. (Generally in run level 5)
3.Check the boot.log messages for error messages for current run level.

Actual results:
Error messages by cpuspeed are seen.
"/etc/rc5.d/S13cpuspeed: line91: echo: write error: Invalid argument"
Starting cpuspeed [failed]

Expected results:
No Error messages. cpuspeed should work properly.

Additional info:
#cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_governors
performance powersave

#cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
powersave


Seems like /etc/rc5.d/S13cpuspeed is trying to insert values like "userspace" or "ondemand" or "conservative" and is failing because its not supported by the system.

Similar issue was listed in https://access.redhat.com/solutions/328853

Created attachment 1029919 [details]
cpuinfo

Thank you for the report.  This is a known issue affecting Intel platforms caused by changes in the kernel.

This is of a purely cosmetic nature and you can safely disable the cpuspeed service as scaling and performance management is now done by the kernel driver directly.

In that case, can you please disable this service from init.d, just to prevent any confusion from user-end?

(In reply to Sujith from comment #3)
> In that case, can you please disable this service from init.d, just to
> prevent any confusion from user-end?

Yes, something along those lines is the planned fix for this problem.

Fixed in cpuspeed-1.5-21.el6.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-1440.html