Bug 722750 - [REGRESSION] System suspend does not work anymore
Summary: [REGRESSION] System suspend does not work anymore
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-17 10:23 UTC by Sergey
Modified: 2012-06-06 16:35 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-06 16:35:43 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Novell 680674 0 None None None Never

Description Sergey 2011-07-17 10:23:14 UTC 
I migrated from Mandriva Linux 2010.2 to OpenSuSe 11.4 and found that Suspend to
RAM functionality broken. System suspends successful but brashes at wakeup:
laptop boots from POST screen without any messages. Now I using Fedora 15 but facing the same issue. I also tried Fedora 14 with no success.

Suspend functionality was worked fine with kernel 2.6.33 provided with old distributions.

Reproducible: Always

Steps to Reproduce:
1. Login
2. Click suspend (Suspend to RAM in old versions)
3. Wait while suspend complete
4. Press any key to wakeup device
Actual Results:  
Laptop boots from POST screen without any error messages and it looks like the
laptop was just turned on.

Expected Results:  
System should wakeup and continue 

Laptop: Sony VAIO VPC F11Z1R 

I tried this functionality both with NVIDIA's driver and nouveau with no success.

I also tried to use kernel suspend debug but didn't found cause. You can also read attached bug at novell to get additional information.
Comment 1 Sergey 2011-07-17 10:29:17 UTC 
Also I found system suspend still work with i386 kernel
Note You need to log in before you can comment on or make changes to this bug.