Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1080006

Summary:	Incorrect command for multi-core power saving
Product:	[Retired] Fedora Documentation	Reporter:	Andrew Aylett <andrew>
Component:	power-management-guide	Assignee:	Petr Bokoc <pbokoc>
Status:	CLOSED EOL	QA Contact:	Fedora Docs QA <docs-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	devel	CC:	zach
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-07 15:30:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Andrew Aylett 2014-03-24 13:57:28 UTC

Description of problem:
In section 4.2 [https://docs.fedoraproject.org/en-US/Fedora/20/html/Power_Management_Guide/Example_Laptop.html], there's a list of commands that can be executed to save some power.  The command listed for "enable multi-core power-saving (part of the laptop-battery-powersave profile)" is a duplicate of the previous command and is therefore incorrect.

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

The command is given as:

echo Y > /sys/module/snd_ac97_codec/parameters/power_save

Which is the command for enabling audio codec power saving, not for enabling multi-core power saving.

Comment 1 Andrew Aylett 2014-03-24 13:59:39 UTC

The RH docs[0] suggest that the command should be this:

echo 1 > /sys/devices/system/cpu/sched_mc_power_savings

[0]: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Power_Management_Guide/Example_Laptop.html

Comment 4 Petr Bokoc 2019-11-07 15:30:10 UTC

I'm closing this bug as part of a Bugzilla cleanup effort. The most likely reason is that the bug has been opened either against a component we no longer publish, or against Release Notes for an EOL release.