Bug 769477 - Lenovo T510 fails to hibernate or suspend.
Summary: Lenovo T510 fails to hibernate or suspend.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: i686
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-20 23:33 UTC by Mike Reid
Modified: 2012-11-14 20:40 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-14 20:40:40 UTC
Type: ---


Attachments (Terms of Use)

Description Mike Reid 2011-12-20 23:33:44 UTC
Description of problem:
Suspend and hibernate don't work, just lock the screen. 

Version-Release number of selected component (if applicable):
gnome-shell.i686          3.2.1-2.fc16 
gnome-shell-extension-alternative-status-menu.noarch    3.2.1-1.fc16 
kernel: 3.1.5-6.fc16.i686.PAE




How reproducible:
Every time. 


Steps to Reproduce:
1. Select hibernae or suspend from menu

  
Actual results:
Locks screen

Expected results:
Hibernate or suspend


Additional info:

Comment 1 Christof Damian 2011-12-27 10:31:12 UTC
I have the same problem, but for me it isn't just related to the suspend button or gnome3. I can't put my T510 into suspend at all, neither to the gnome3 or xfce menu or shutting the lid. This worked flawlessly in Fedora 15.

Comment 2 Mike Reid 2011-12-27 19:52:54 UTC
I've also tried using pm-hibernate and pm-suspend on the command line, also with no success.

Comment 3 Mike Reid 2012-02-18 00:34:47 UTC
I'm now up to: 
kernel 3.2.6-3.fc16.i686.PAE
gnome 3.2.1
and hibernate still doesn't work on this system.

Comment 4 Mike Reid 2012-04-15 05:59:10 UTC
Hibernate still isn't working, now up to kernel 3.3.1-5 (32 bit). 

I wonder if the newer kernels need more swap space to hibernate? 
Here's what I have allocated at present: 

Mem:   3990376k total,  2872288k used,  1118088k free,   259000k buffers
Swap:  5177340k total,        0k used,  5177340k free,  1457180k cached

Comment 5 Mike Reid 2012-05-13 06:52:03 UTC
Now up to 3.3.5-2.fc16.i686.PAE and no hibernation or suspension...

Comment 6 Owen Taylor 2012-05-14 13:40:43 UTC
The fact that pm-hibernate and pm-suspend on the command line don't work either means this has nothing to do with GNOME Shell.

Comment 7 Mike Reid 2012-05-14 19:35:47 UTC
I've been trying the command-line pm-suspend again and I notice that there is an error message in /var/log/pm-suspend.log 
------------------------------
/usr/lib/pm-utils/sleep.d/56dhclient suspend suspend: Returned exit code 2.
Tue May 15 07:29:58 NZST 2012: Inhibit found, will not perform suspend
Tue May 15 07:29:58 NZST 2012: Running hooks for resume
Running hook /usr/lib/pm-utils/sleep.d/55NetworkManager resume suspend:
Having NetworkManager wake interfaces back up...Done.
-----------------------------

Comment 8 Dave Jones 2012-10-23 15:38:25 UTC
# Mass update to all open bugs.

Kernel 3.6.2-1.fc16 has just been pushed to updates.
This update is a significant rebase from the previous version.

Please retest with this kernel, and let us know if your problem has been fixed.

In the event that you have upgraded to a newer release and the bug you reported
is still present, please change the version field to the newest release you have
encountered the issue with.  Before doing so, please ensure you are testing the
latest kernel update in that release and attach any new and relevant information
you may have gathered.

If you are not the original bug reporter and you still experience this bug,
please file a new report, as it is possible that you may be seeing a
different problem. 
(Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).

Comment 9 Mike Reid 2012-10-23 18:42:29 UTC
It's working for me with the latest kernels. 

I also found I had some other issues with the files shutting down my wifi
See #8 on this thread: http://forums.fedoraforum.org/showthread.php?p=1607254#post1607254


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