Bug 1090128

Summary:	Resume from suspend on 3.13.10-200.fc20.x86_64 results in a black screen
Product:	[Fedora] Fedora	Reporter:	Jay Kamat <jaygkamat>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	20	CC:	gansalmon, itamar, jaygkamat, jonathan, kernel-maint, madhu.chinakonda, mchehab, n0000b.n000b
Target Milestone:	---	Flags:	jforbes: needinfo?
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-12-10 15:03:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jay Kamat 2014-04-22 16:19:20 UTC

Description of problem:
If I put the laptop to sleep/suspend and try to turn it back on, the result is a black screen, exactally the same as when the laptop is off. However, I can still "use" the laptop, just without a display. 

There is no reponse if I press <ctl><alt><f#>.

Version-Release number of selected component (if applicable):
Kernel 3.13.10-200.fc20.x86_64 (with yum update)

Graphics Card:
AMD Radeon 7600 HD with default Fedora Drivers

Laptop Model:
HP Pavilion m6-1035dx

How reproducible:
always

Steps to Reproduce:
1. Boot into fedora
2. Close the lid or press the sleep button
3. Open the lid or press the power button

Actual results:
The screen stays blank

Expected results:
A usable laptop comes up


Additional info:
Here is my dmesg output before and after sleeping
Before Sleep: bit.ly/QCIOQk
After Sleep: bit.ly/1kXq8Gv

Let me know if anyone needs any additional information =)

Comment 1 n0000b.n000b 2014-04-29 00:53:23 UTC

have you tried?

sudo pm-suspend --quirk-test --quirk-s3-bios

see also:

https://bugzilla.redhat.com/show_bug.cgi?id=1069027

https://bugs.freedesktop.org/show_bug.cgi?id=42960

Comment 2 Jay Kamat 2014-04-29 01:21:20 UTC

That command results in the same problem as I stated above (no improvement), so this must be a different bug. 

Is there any other information that could help pin down this issue?

Comment 3 Justin M. Forbes 2014-05-21 19:41:30 UTC

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.14.4-200.fc20.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 4 Jay Kamat 2014-05-22 00:59:38 UTC

The new kernel update has not changed the symptoms for me, everything is exactly the same as described above.  (Kernel 3.14.4-200)

Comment 5 Justin M. Forbes 2014-11-13 16:05:02 UTC

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.17.2-200.fc20.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21.

If you experience different issues, please open a new bug report for those.

Comment 6 Justin M. Forbes 2014-12-10 15:03:21 UTC

This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.