Bug 216977 - /sys/power/disk went missing
/sys/power/disk went missing
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nigel Cunningham
Brian Brock
: 214206 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2006-11-22 18:06 EST by Matthias Clasen
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-02-20 04:46:00 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Matthias Clasen 2006-11-22 18:06:55 EST
For a while, my Dell M65 laptop had nicely working suspend and hibernate, which
was very cool. Now, with the beta2 kernel, /sys/power/disk went missing, which
for some reason breaks both suspend and hibernate. That is very sad.

[mclasen@localhost RHEL-5]$ rpm -q kernel-PAE
Comment 1 Linda Wang 2006-11-29 12:46:01 EST
can you try the regular kernel, kernel-2.6.18-1.2747.el5?
Comment 3 RHEL Product and Program Management 2006-11-29 13:00:40 EST
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
Comment 4 Matthias Clasen 2006-11-29 13:08:08 EST
> can you try the regular kernel, kernel-2.6.18-1.2747.el5?

Not right now, I had to cede my laptop to the X team temporarily. 
But e.g. Dave Jones has one too...

Comment 5 Linda Wang 2006-12-01 10:37:26 EST
*** Bug 214206 has been marked as a duplicate of this bug. ***
Comment 6 Nigel Cunningham 2007-02-20 04:46:00 EST
swsusp doesn't support PAE. If you go back to a 4GB Highmem kernel, the entry 
will reappear.

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