Bug 1010583 - Computer won't resume from sleep
Summary: Computer won't resume from sleep
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 19
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-21 18:52 UTC by bugzilla.justin
Modified: 2013-10-02 02:31 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-02 02:31:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description bugzilla.justin 2013-09-21 18:52:28 UTC
Description of problem:
In Fedora 19 GNOME I click "Lock" to put the machine to sleep. The monitor turns off but my keyboard and mouse are still lit up (as expected). However it's impossible to get out of sleep - pressing keys on the keyboard, moving the mouse, pressing the power button - nothing wakes it up.

Pressing caps lock or num lock doesn't toggle the light on that specific key, so it's obvious key strokes aren't being registered.

The only way to use the computer again is to hit the reset button.


Version-Release number of selected component (if applicable):
Fedora 19, fully updated
Linux 3.11


How reproducible:
Always


Steps to Reproduce:
1. Click Lock in GNOME Shell
2. Press keys/move mouse


Actual results:
Nothing happens. Only way to make computer usable is to hardware reset.


Expected results:
Screen turns on. Can use computer.


Additional info:
The reason I'm filing this as a Kernel bug is because the system was working perfectly until Fedora 19 got the 3.11 kernel. That is when the issue started happening. When I boot back into an old 3.10 kernel (3.10.11-200.fc19.x86_64 to be exact) I'm unable to reproduce this issue.

Comment 1 bugzilla.justin 2013-09-21 18:58:08 UTC
System information:
http://paste.fedoraproject.org/41262/97898091/

Comment 2 bugzilla.justin 2013-10-02 02:31:29 UTC
3.11.2-201.fc19.x86_64 seems to have fixed the problem. All is good!


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