Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 914623 - cpupower set -m doesn't work
cpupower set -m doesn't work
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: cpupowerutils (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Neil Horman
Jeff Bastian
Depends On:
  Show dependency treegraph
Reported: 2013-02-22 05:38 EST by Jaroslav Škarvada
Modified: 2013-11-20 23:39 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-11-20 23:39:48 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1533 normal SHIPPED_LIVE cpupowerutils bug fix and enhancement update 2013-11-20 16:40:59 EST

  None (edit)
Description Jaroslav Škarvada 2013-02-22 05:38:02 EST
Description of problem:
cpupower set -m doesn't work. From the source code it seems this feature is not implemented, but the error message is misleading and can be wrongly interpreted as the feature is not supported by your platform.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. echo 0 > /sys/devices/system/cpu/sched_mc_power_savings; cat /sys/devices/system/cpu/sched_mc_power_savings
2. cpupower set -m 0
Actual results:
Error setting sched-mc not supported

Expected results:
sched-mc set

Additional info:
I think it would be enough to change the message to something like:
Error setting sched-mc not implemented

or remove the feature entirely (upstream kernel drops the sched_mc_power_savings).
Comment 12 errata-xmlrpc 2013-11-20 23:39:48 EST
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.


Note You need to log in before you can comment on or make changes to this bug.