Bug 671055 - laptop does not wake from sleep
Summary: laptop does not wake from sleep
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: upower
Version: 14
Hardware: i386
OS: Linux
low
high
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 671054 (view as bug list)
Depends On:
Blocks: 848951
TreeView+ depends on / blocked
 
Reported: 2011-01-20 04:44 UTC by Chris Murphy
Modified: 2013-01-07 21:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 848951 (view as bug list)
Environment:
Last Closed: 2012-08-16 19:56:48 UTC
Type: ---


Attachments (Terms of Use)
varlogmessage (78.06 KB, text/plain)
2011-01-20 04:44 UTC, Chris Murphy
no flags Details
pmsuspendlog (3.11 KB, text/plain)
2011-01-20 04:54 UTC, Chris Murphy
no flags Details

Description Chris Murphy 2011-01-20 04:44:31 UTC
Created attachment 474385 [details]
varlogmessage

Description of problem:

Power Management Preferences set to "put computer to sleep when inactive for 2 hours". Computer sleeps within approximately 2 hours but will not wake up. When any button is pressed, hard drive spins up, power light stops flashing, black screen, cannot ssh into the system to get any information.



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

Fedora 14



How reproducible:

Always

Steps to Reproduce:
1. Either allow computer to idle  until sleep time arrives; or close lid.
2. Once computer is asleep, try to rewake pushing any button.

  
Actual results:

Drive spin up.
Power light solid.
Black screen.
No network services including ssh.
No response from ping.

Expected results:

Expect it to wake up.

Additional info:

Full system details:
http://www.smolts.org/client/show_all/pub_2ca5f783-63ad-4b0d-a268-1e662099d42e

/var/log/messages is unrevealing but I will post the relevant log in full.
17:49:13 is when sleep arrives
20:25:41 is the next reboot as a result of having to force shutdown of the machine and then turn it back on again since there was no response from ssh or ping.

Comment 1 Chris Murphy 2011-01-20 04:54:11 UTC
Created attachment 474388 [details]
pmsuspendlog

Comment 2 Chris Murphy 2011-01-20 04:57:54 UTC
Currently using btrfs with this setup, however I had the same issue with the same hardware running Fedora 12 and Fedora 13 using ext4 so I don't think the filesystem is related.

Comment 3 Brendan Jones 2011-01-21 21:54:55 UTC
*** Bug 671054 has been marked as a duplicate of this bug. ***

Comment 4 Fedora End Of Life 2012-08-16 19:56:51 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

Comment 5 Chris Murphy 2013-01-07 21:31:22 UTC
Just in case this is found by someone else in a search, problem is solved by updating the BIOS to A16 from Dell's website. Very basic.


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