[Bug 1162045] New: Power Mgmt Guide needs to Address Howto Suppress Sleep State
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1162045
Bug ID: 1162045
Summary: Power Mgmt Guide needs to Address Howto Suppress Sleep
State
Product: Fedora Documentation
Version: devel
Component: power-management-guide
Severity: low
Assignee: yruseva(a)redhat.com
Reporter: redzilla.coralnut(a)xoxy.net
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: ddomingo(a)redhat.com, yruseva(a)redhat.com,
zach(a)oglesby.co
Description of problem:
F20 Power Management Guide does not address the hooks into the sleep system
provided by systemd. Ever since p,m-utils was deprecated there have been no
Fedora/RHAT resources available that discuss how to utilize the hooks into the
sleep system to prevent entry into the sleep state.
Example: in the era of pm-utils (going back to what, F15?) one could write
scripts to suppress the transition to S3 if a desirable network connection were
established that should not be interrupted. All that was required was to place
the script in /etc/pm/sleep.d/ and have it issue a non-zero exit code if sleep
should be suppressed. When the goto sleep process prepared for sleep by
executing the script, the script could deliver a non-zero exit code and prevent
entry into the sleep state.
Now that pm-utils has been deprecated and replaced with systemd, Fedora now
ignores any/all scripts in /etc/pm/*. That isn't a problem. What *IS* a
problem, though, is that for the past 5 releases of Fedora, the Power
Management Guide has completely ignored the topic of how to use custom scripts
to prevent entry into the sleep state. As a result, our only options are to
look for help and examples in other distributions.
Version-Release number of selected component (if applicable):
F20, F21
How reproducible:
N/A. The documentation doesn't address the problem.
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
6 years, 3 months
[Bug 1080006] New: Incorrect command for multi-core power saving
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1080006
Bug ID: 1080006
Summary: Incorrect command for multi-core power saving
Product: Fedora Documentation
Version: devel
Component: power-management-guide
Assignee: yruseva(a)redhat.com
Reporter: fedorabugs(a)aylett.co.uk
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: ddomingo(a)redhat.com, yruseva(a)redhat.com,
zach(a)oglesby.co
Description of problem:
In section 4.2
[https://docs.fedoraproject.org/en-US/Fedora/20/html/Power_Management_Guid...],
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.
--
You are receiving this mail because:
You are the QA Contact for the bug.
6 years, 3 months
[Bug 994167] New: typo in servicectl enable command
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=994167
Bug ID: 994167
Summary: typo in servicectl enable command
Product: Fedora Documentation
Version: devel
Component: power-management-guide
Assignee: yruseva(a)redhat.com
Reporter: joseignacio.quintana(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: ddomingo(a)redhat.com, oglesbyzm(a)gmail.com,
yruseva(a)redhat.com
Description of problem:
>>> F19, power-management-guide, Section: 2.5.3. Installation and Usage
>>> command "systemctl tuned enable" should be "systemctl enable tuned"
Version-Release number of selected component (if applicable):
>>> F19 doc of power management guide
How reproducible:
# systemctl tuned enable
# ERR: Unknown operation 'tuned'.
# systemctl enable tuned
# OK: ln -s '/usr/lib/systemd/system/tuned.service'
'/etc/systemd/system/multi-user.target.wants/tuned.service'
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
6 years, 3 months
[Bug 973950] New: Type in Chapter 1.2
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=973950
Bug ID: 973950
Summary: Type in Chapter 1.2
Product: Fedora Documentation
Version: devel
Component: power-management-guide
Severity: low
Priority: unspecified
Assignee: r.landmann(a)redhat.com
Reporter: swierckx(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: ddomingo(a)redhat.com, oglesbyzm(a)gmail.com,
r.landmann(a)redhat.com
Description of problem:
In chapter 1.2 of the power management guide there is a type in the fedora
version mentioned
"The kernel used in releases of Fedora prior to Fedora 8 used a periodic timer
for each CPU. This timer prevents the CPU from truly going idle ..."
should probably be
""The kernel used in releases of Fedora prior to Fedora 18 used a periodic
timer for each CPU. This timer prevents the CPU from truly going idle ...""
I deducted this from the sentence a little further where it is mentioned that
only from Fedora 18 the idle CPU state is tickles
--
You are receiving this mail because:
You are the QA Contact for the bug.
6 years, 3 months
[Bug 842190] New: Cpufreq governor
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=842190
Bug ID: 842190
QA Contact: docs-qa(a)lists.fedoraproject.org
Severity: unspecified
Version: devel
Priority: unspecified
CC: ddomingo(a)redhat.com, oglesbyzm(a)gmail.com
Assignee: r.landmann(a)redhat.com
Summary: Cpufreq governor
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: h479627(a)rtrtr.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: power-management-guide
Product: Fedora Documentation
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
6 years, 3 months
[Bug 832179] New: Power management guide is wrong for frequency scaling in Fedora 17
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=832179
Bug ID: 832179
QA Contact: docs-qa(a)lists.fedoraproject.org
Severity: medium
Version: devel
Priority: unspecified
CC: ddomingo(a)redhat.com, oglesbyzm(a)gmail.com
Assignee: r.landmann(a)redhat.com
Summary: Power management guide is wrong for frequency scaling
in Fedora 17
Regression: ---
Story Points: ---
Classification: Fedora
OS: Linux
Reporter: jnm11(a)cam.ac.uk
Type: Bug
Documentation: ---
Hardware: All
Mount Type: ---
Status: NEW
Component: power-management-guide
Product: Fedora Documentation
Description of problem:
Power management guide is wrong
https://docs.fedoraproject.org/en-US/Fedora/17/html/Power_Management_Guid...
Version-Release number of selected component (if applicable):
Fedora 17
the location of the cpufreq directory is misspecified
it is
/lib/modules/3.4.0-1.fc17.x86_64/kernel/drivers/cpufreq
There are no modules
acpi-cpufreq or p4-clockmod available
is acpi-cpufreq directly compiled in.
the cpuspeed package is mentioned for the userspace governor but no package
exists in fedora 17.
I have been completely unable to figure out the following use case.
My laptop overheats and powers off if the cpu load is high for too long.
There should be a cpu governor or userspace daemon that reduces frequency when
the temperature gets too high.
--
You are receiving this mail because:
You are the QA Contact for the bug.
6 years, 3 months