Bug 238690 - pm-hibernate fails in shutting down a Dell OPTIPLEX GX280
Summary: pm-hibernate fails in shutting down a Dell OPTIPLEX GX280
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: pm-utils
Version: rawhide
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Phil Knirsch
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-05-02 11:43 UTC by Steven Op de beeck
Modified: 2015-03-05 01:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-04-08 08:13:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
extract of kernel messages, seems to be of restore, nothing on actual hibernate itself (8.60 KB, text/plain)
2007-05-02 11:43 UTC, Steven Op de beeck
no flags Details

Description Steven Op de beeck 2007-05-02 11:43:12 UTC
Description of problem:

pm-hibernate fails in shutting down the machine. A lot of status msgs appear
concerning shrinking memory, etc. After the messages that says 'syncing [...]
sda [...]' the system stays at message indefinately and starts using cpu cycles,
as I can hear from the cpu-fans that start blowing faster.

After manually resetting the machine it returns from hibernate, and restores the
system to the state before hibernating.

pm-hibernate worked in fc6.

Version-Release number of selected component (if applicable):
pm-utils-0.99.3-2.fc7

How reproducible:
run pm-hibernate in terminal, or click the hibernate button in gnome.

Steps to Reproduce:
1. hibernate the machine using pm-hibernate
2. wait for machine to shutdown
  
Actual results:
- machine starts eating cpu
- required to manually reset machine
- recovers from hibernate as expected after being switched on

Expected results:
- machine shuts down automatically
- recovers from hibernate as expected after being switched on

Additional info:
machine:
Dell OPTIPLEX GX280
3.2Ghz, 1GiB RAM
80GB harddisk on /dev/sda
selinux enabled in permissive mode
kernel-2.6.21-1.3116.fc7 (same behavior with earlier fc7 kernels, I started from
test3)
bios set to S3

Comment 1 Steven Op de beeck 2007-05-02 11:43:13 UTC
Created attachment 153932 [details]
extract of kernel messages, seems to be of restore, nothing on actual hibernate itself

Comment 2 Steven Op de beeck 2007-05-02 11:45:28 UTC
Comment on attachment 153932 [details]
extract of kernel messages, seems to be of restore, nothing on actual hibernate itself

fixed mime-type

Comment 3 Richard Hughes 2007-05-24 12:07:34 UTC
Can you try some of the quirks in
http://people.freedesktop.org/~hughsient/quirk/ please - thanks!

Comment 4 Steven Op de beeck 2007-05-24 14:05:20 UTC
I tried pm-hibernate just now, and it seems to work fine. Clean hibernate,
shutdown and thaw.

However, while reading the quirks-website, I noticed pm-suspend doesn't succeed
in returning from suspend. I tried some combinations of parameters, but nothing
seemed to work, until I got tired of force-shutdowning my pc.

I noticed both S3-related params result in a complete shutdown. 

On a rare occasion I am able to login through ssh and reboot, other times the
monitor stays off and the pc doesn't respond to anything (including ping).

I will do some testing later. The quirks-site seems down for the moment.

Comment 5 Till Maas 2007-09-13 05:31:00 UTC
(In reply to comment #4)

> I will do some testing later. The quirks-site seems down for the moment.

Did you do more testing? Does it work now?

Comment 6 Till Maas 2008-01-08 16:36:57 UTC
Steven, can you please test, whether it does still not work for you? I cannot
check this, because I do not have access to a notebook like yours.

Comment 7 Steven Op de beeck 2008-01-28 23:08:58 UTC
The machine is a desktop computer at my work. Hibernate still works fine.
Suspend has the same problem. I did not re-try the quirks. When I find the time,
in the next two weeks, I will look into this.

Comment 8 Steven Op de beeck 2008-04-08 08:13:46 UTC
On a completely update F7 using the ATI radeon driver, both suspend and hibernate appear to be working 
correctly.


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