Bug 679431 - Waking from suspend causes a full reboot
Summary: Waking from suspend causes a full reboot
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-22 15:04 UTC by Stephen Gallagher
Modified: 2012-06-04 18:46 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-04 18:46:45 UTC
Type: ---


Attachments (Terms of Use)

Description Stephen Gallagher 2011-02-22 15:04:36 UTC
Description of problem:
Discovered during https://fedoraproject.org/wiki/Test_Day:2011-02-22_Nouveau

Version-Release number of selected component (if applicable):
xorg-x11-drv-nouveau-0.0.16-19.20110216git42c16ff.fc15

How reproducible:
Every time

Steps to Reproduce:
1. Boot the live image into a graphical login
2. Log in
3. Close laptop lid
4. Open laptop lid (press space bar to wake, on this particular laptop)

  
Actual results:
System boots from BIOS

Expected results:
System resumes from where it was suspended

Additional info:
Laptop is a Sony VAIO VPCCW17fx with nVidia GeForce 210M graphics

Comment 1 Stephen Gallagher 2011-02-22 15:14:00 UTC
Reassigning to kernel per hughsie's recommendation in IRC.


Also, the smolt profile for this hardware is available here: http://www.smolts.org/client/show/pub_44c80725-3125-4081-ae2b-9a0be0797f03

Comment 2 gymper 2012-02-21 05:55:21 UTC
A workaround is to add this to kernel boot params:  acpi_sleep=nonvs

Comment 3 Josh Boyer 2012-06-04 15:45:03 UTC
Is this still seen with the 2.6.43/3.3 kernel updates in F15/F16?

Comment 4 Stephen Gallagher 2012-06-04 18:40:00 UTC
Sorry, I'm not using an nVidia-based laptop any more, so I don't have any way to test this.

Comment 5 Josh Boyer 2012-06-04 18:46:45 UTC
OK


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