Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Previously, pm-utils did not support the Advanced Configuration and Power Interfaces (ACPI) S1 (Power on Suspend) power state. As a consequence, when BIOS supported the ACPI S3 (Suspend to RAM) power state but not the S1 power state, the "pm-suspend" command failed. This update introduces support for the S1 power state, and if the S3 power state is not supported by BIOS, pm-suspend now triggers the S1 power state.
DescriptionEduardo Minguez
2013-10-30 18:05:31 UTC
Description of problem:
Trying to suspend by running "pm-suspend" to S1 acpi state (standby) doesn't work
Version-Release number of selected component (if applicable):
pm-utils-1.2.5-10
How reproducible:
Configure the BIOS for suspend only to S1 state and run pm-suspend
Steps to Reproduce:
1. Configure BIOS settings to allow acpi suspension only to S1 state
2. Execute pm-suspend
Actual results:
pm-suspend exits (code error 0) but the computer is not suspended
Expected results:
pm-suspend works by changing the acpi state to S1
Additional info:
I've seen in /usr/lib/pm-utils/pm-functions that changing the following works:
# diff pm-functions pm-functions.old
257c257
< if grep -q standby /sys/power/state; then
---
> if grep -q mem /sys/power/state; then
259c259
< do_suspend() { echo -n "standby" >/sys/power/state; }
---
> do_suspend() { echo -n "mem" >/sys/power/state; }
Sorry for the ugly workaround!
Comment 7Jaroslav Škarvada
2014-05-05 11:40:53 UTC
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.
http://rhn.redhat.com/errata/RHBA-2014-1455.html
Description of problem: Trying to suspend by running "pm-suspend" to S1 acpi state (standby) doesn't work Version-Release number of selected component (if applicable): pm-utils-1.2.5-10 How reproducible: Configure the BIOS for suspend only to S1 state and run pm-suspend Steps to Reproduce: 1. Configure BIOS settings to allow acpi suspension only to S1 state 2. Execute pm-suspend Actual results: pm-suspend exits (code error 0) but the computer is not suspended Expected results: pm-suspend works by changing the acpi state to S1 Additional info: I've seen in /usr/lib/pm-utils/pm-functions that changing the following works: # diff pm-functions pm-functions.old 257c257 < if grep -q standby /sys/power/state; then --- > if grep -q mem /sys/power/state; then 259c259 < do_suspend() { echo -n "standby" >/sys/power/state; } --- > do_suspend() { echo -n "mem" >/sys/power/state; } Sorry for the ugly workaround!