| Summary: | acpitool -s failed with error could not open file : /proc/acpi/sleep | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kamae Norihiro <norihiro> |
| Component: | acpitool | Assignee: | Steven M. Parrish <smparrish> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | dad, dwreski, jskarvad, pertusus, rohlfing, smparrish |
| 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: | 2013-02-13 22:25:40 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Kamae Norihiro
2012-01-24 12:39:54 UTC
Kamae Norihiro beat me to this report by 6 months. I get exactly the same failure, both with acpitool -s and acpitool -S.
The required file, /proc/acpi/sleep, is absent.
And my errors occur with these package IDs:
acpitool-0.5.1-4.fc17.i686
kernel-PAE-3.4.4-5.fc17.i686
For what it's worth, both pm-suspend and pm-hibernate also fail, but for reasons that boggle the mind. See BZ 838648.
In BZ 819559 Jaroslav Škarvada told me to try these commands instead:
Try suspend via:
# echo mem > /sys/power/state
and hibernate:
# echo disk > /sys/power/state
Although this provides a workaround, it would be nice to see acpitool fixed.
Same problem just appeared with my last reboot to the following: kernel-3.5.2-3.fc17.x86_64 acpitool-0.5.1-4.fc17.x86_64 (In reply to comment #2) > Same problem just appeared with my last reboot to the following: > > kernel-3.5.2-3.fc17.x86_64 > acpitool-0.5.1-4.fc17.x86_64 Sorry for the double posting - So going back through my yum log file, it seems the current acpitool package has been on my system since March, and things definitely worked long after that. From my log files, the most likely change relating to the problem is the update of the kernel package. Is it possible the current kernel doesn't provide the /proc/acpi/sleep file? Also, the workaround that David quoted works nicely, but it doesn't fix suspending via, for example, KDE (both via menu and "sleep" keyboard key). I suspect these higher-level interfaces rely on acpitool internally? Hi, just wondered if there was any further progress on this? I have a similar problem with fc17. I previously had fc15 on this desktop and suspend worked as expected. I have all the updates applied. This is on an MSI MS-7506. I don't have /proc/acpi/sleep and the echo commands fail as root: # echo mem > /sys/power/state -bash: echo: write error: No such device The file exists, and selinux is disabled. When I try and actually suspend, it's like the commands are being executed, including the disk spinning down and display going dim, but it just doesn't complete the process. I've tried resetting the BIOS defaults, including making sure ACPI is enabled. Running acpitool manually also doesn't work as expected. Here is the output from "acpitool -e" [root@sage ~]# acpitool -e Kernel version : 3.6.8-2.fc17.x8 - ACPI version : 20120711 ----------------------------------------------------------- Battery status : <not available> AC adapter : <info not available or off-line> Fan : <not available> CPU type : AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ CPU speed : 2100.002 MHz Cache size : 512 KB Bogomips : 4200.00 Bogomips : 4199.39 Function Show_CPU_Info : could not read directory /proc/acpi/processor/ Make sure your kernel has ACPI processor support enabled. Thermal info : <not available> Device S-state Status Sysfs node --------------------------------------- 1. NSMB S4 *disabled pci:0000:00:01.1 2. USB0 S4 *enabled pci:0000:00:02.0 3. USB2 S1 *enabled pci:0000:00:02.1 4. US15 S4 *enabled pci:0000:00:04.0 5. US12 S1 *enabled pci:0000:00:04.1 6. NMAC S5 *disabled pci:0000:00:0a.0 7. P0P1 S4 *disabled pci:0000:00:08.0 8. HDAC S4 *disabled pci:0000:00:07.0 9. BR10 S4 *disabled pci:0000:00:0b.0 10. BR11 S4 *disabled pci:0000:00:0c.0 11. BR12 S4 *disabled pci:0000:00:0d.0 12. PWRB S4 *enabled Any ideas greatly appreciated. Thanks, Dave This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |