Bug 708551 - Suspend and Hibernate no longer working after upgrade to Fedora 15
Summary: Suspend and Hibernate no longer working after upgrade to Fedora 15
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-27 23:35 UTC by Gerard Fernandes
Modified: 2011-12-06 13:53 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 13:53:57 UTC
Type: ---


Attachments (Terms of Use)

Description Gerard Fernandes 2011-05-27 23:35:40 UTC
Description of problem: Suspend and Hibernate no longer working after upgrade to Fedora 15


Version-Release number of selected component (if applicable):
kernel-2.6.38.6-27.fc15.x86_64


How reproducible: Always


Steps to Reproduce:
1. From the user menu in Gnome-3 select Suspend or Hibernate
2. Notice the laptop goes into the suspend or hibernate state
3. Click on the power button to resume
  
Actual results: Resumes but fails to bring up graphical mode so the screen is blank.


Expected results: Should be able to resume from either suspend or hibernate states to a full graphical environment.


Additional info: This used to work on Fedora-14. The laptop is a Dell Studio 1740.
Smolt profile link: http://www.smolts.org/client/show/pub_91d07f36-0a8b-4094-a4ce-d81ce02ff1e3

Comment 1 Jahanzeb Arshad 2011-06-01 07:33:54 UTC
(In reply to comment #0)
> Description of problem: Suspend and Hibernate no longer working after upgrade
> to Fedora 15
> 
> 
> Version-Release number of selected component (if applicable):
> kernel-2.6.38.6-27.fc15.x86_64
> 
> 
> How reproducible: Always
> 
> 
> Steps to Reproduce:
> 1. From the user menu in Gnome-3 select Suspend or Hibernate
> 2. Notice the laptop goes into the suspend or hibernate state
> 3. Click on the power button to resume
> 
> Actual results: Resumes but fails to bring up graphical mode so the screen is
> blank.
> 
> 
> Expected results: Should be able to resume from either suspend or hibernate
> states to a full graphical environment.
> 
> 
> Additional info: This used to work on Fedora-14. The laptop is a Dell Studio
> 1740.
> Smolt profile link:
> http://www.smolts.org/client/show/pub_91d07f36-0a8b-4094-a4ce-d81ce02ff1e3

I am having same problem on a Sony Vaio VGN-SZ79GN.

Comment 2 serverherder 2011-08-10 16:34:01 UTC
Nearly identical configuration as the original poster, except a Studio 1749 and an Intel graphics card, not a Radeon. I am at Bios version A08.  

System suspends properly under 2.6.38 but freezes during resume -- No keyboard or network functionality.  Using kernel 2.6.40+ the system now fails to suspend.  Enabling pm_trace does not cause a "hash matches" message to be displayed.  

Worked properly under 2.6.35 in F14, although multi-monitor support is broken for my video card in this version.  Seems to have broken between 2.6.36-rc1 and 2.6.36-rc6 -- I am unable to boot any kernels in between these two releases. 

My smolt profile is 
http://www.smolts.org/client/show/pub_50a3f8b7-ac72-481c-a345-fba196a3c9a6

Comment 3 serverherder 2011-08-11 01:33:42 UTC
Actually, after trying pm_trace again I was able to identify the cause of the problem was the firewire modules.  Renoving firewire_core and firewire_ohci and adding them to the blacklist resolved the issue.

(Caveat Emptor: When I resumed from suspend the clock jumped forward about ten years. Since I rebooted before adjusting, the system had to be rescued from a live cd as  fsck would not auto-repair the timestamp on the partition)

Comment 4 Gerard Fernandes 2011-12-06 06:30:53 UTC
This is working now! Issue may be closed.

I've updated a few times so don't know exactly which update fixed it.

Comment 5 Josh Boyer 2011-12-06 13:53:57 UTC
Thank you for letting us know.


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