Bug 654107 - Unable to resume after a pm-suspend
Summary: Unable to resume after a pm-suspend
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 14
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-16 21:39 UTC by christophe.lindheimer
Modified: 2013-01-10 06:20 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 18:44:15 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
run pm_suspend from X (4.29 KB, application/octet-stream)
2010-11-16 21:39 UTC, christophe.lindheimer
no flags Details
run pm_suspend --no-quirck from X (2.99 KB, application/octet-stream)
2010-11-16 21:40 UTC, christophe.lindheimer
no flags Details
run pm_suspend from console (4.00 KB, application/octet-stream)
2010-11-16 21:41 UTC, christophe.lindheimer
no flags Details

Description christophe.lindheimer 2010-11-16 21:39:48 UTC
Created attachment 460937 [details]
run pm_suspend from X

Description of problem:

After a pm-suspend the laptop goes off
After pressing the power button, the laptop starts but the scren remain blank
Laptop is a ecafe 900 with via proc C7-M

Version-Release number of selected component (if applicable):

Fedora 14

How reproducible:


Steps to Reproduce:
1.run pm-suspend
2.press power button to resume
3.
  
Actual results:
Resume fails -> black screen

Expected results:


Additional info:

Comment 1 christophe.lindheimer 2010-11-16 21:40:52 UTC
Created attachment 460938 [details]
run pm_suspend --no-quirck  from X

Comment 2 christophe.lindheimer 2010-11-16 21:41:43 UTC
Created attachment 460939 [details]
run pm_suspend from console

Comment 3 John Schmitt 2012-07-17 04:06:10 UTC
I have this problem with an Asus Maximus with a Core i7.  This used to work well (along with pm-hibernate) before 3.2.  If I wake this computer up from pm-suspend, it does an fsck as if the disks had been unmounted abruptly.

Comment 4 John Schmitt 2012-07-17 04:12:13 UTC
I was (naively) hoping that fixing https://bugzilla.redhat.com/show_bug.cgi?id=785384 would also fix my issues.

Comment 5 Szőke Károly 2012-07-17 17:22:35 UTC
I have the same problem after 3.1.9 kernel (from 3.2). I suspend my MSI laptop, and when I try to wake up, the screen remain blank. Then I reset the machine, it stand up. After, when I logged in, automatically come in the screensaver and I must logged in again.

Comment 6 aaronsloman 2012-07-18 01:37:02 UTC
As far as failing to resume properly from pm-hibernate is concerned, this has been discussed in a number of bug-reports including bug #806315, and seems to be related to use of the i915 module (required for intel integrated graphics).


I have a dell lattitude E6410 with core i5 processor and intel graphics and a desktop PC with core i5 processor and intel graphics, both running fedora 16.
Both show (intermittent inability to complete resuming after pm-hibernate the default settings in /boot/grub2/grub.cfg 

However, I have found that resume after pm-hibernate always works provided that when resuming I have acpi=off in the kernel parameters (only when resuming, not when booting), as described in this comment https://bugzilla.redhat.com/show_bug.cgi?id=806315#c37 

The scripts described there are now available here:
http://www.cs.bham.ac.uk/~axs/laptop/hibernate-on-linux.html

Suggestions for improvement welcome. 

I have no idea whether this method will work for resume from suspend. I never use suspend, only hibernate.

There is no guarantee that my method will work for anyone else. I don't know why it works! It is not a satisfactory long term solution, but I have been using it without problems for a few months (multiple hibernates and resumes: e.g. uptime (since last reboot) on my PC is 39 days -- using hibernate at least once a day, and often two or three times in a day.

Comment 7 Fedora End Of Life 2012-08-16 18:44:18 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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" (top right of this page) 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


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