Bug 671054 - laptop does not wake from sleep
Summary: laptop does not wake from sleep
Keywords:
Status: CLOSED DUPLICATE of bug 671055
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:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-20 04:43 UTC by Chris Murphy
Modified: 2011-01-21 21:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-21 21:54:55 UTC
Type: ---


Attachments (Terms of Use)

Description Chris Murphy 2011-01-20 04:43:47 UTC
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 Brendan Jones 2011-01-21 21:54:55 UTC

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

*** This bug has been marked as a duplicate of bug 671055 ***


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