Bug 917563

Summary:	No graphic after suspend
Product:	[Fedora] Fedora	Reporter:	Andre Naehring <naehring>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	gansalmon, itamar, jforbes, jonathan, kernel-maint, madhu.chinakonda
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-06 16:24:16 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 Andre Naehring 2013-03-04 11:05:09 UTC

Description of problem: Using the latest kernel version kernel-3.8.1-201.fc18.x86_64 my Thinkpad will wakeup after suspend but the screen stays blank. Using the previous kernel 3.7.9 everything works fine. 


Version-Release number of selected component (if applicable): affected kernel-3.8.1-201.fc18.x86_64, previous (3.7.9-205.fc18.x86_64) is _not_ affected.


How reproducible: Simply close laptop lid for suspend and open it again.


 
Actual results: screen stays blank, looks like laptop wakes up (using ctrl-alt-del) after switching to another terminal (which is also blank) initiates the expected reboot


Expected results: show graphics


Additional info:

used graphics: Intel® Ivybridge Mobil, here:

00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
	Subsystem: Lenovo Device 21fa
	Kernel driver in use: i915

Comment 1 Andre Naehring 2013-03-04 14:38:32 UTC

Okay, this occurs only if you are using the kernel cmdline parameter "acpi_backlight=vendor". 

This one is neccessary for brightness control. Not using this parameter, suspend and wake up works.

Comment 2 Justin M. Forbes 2013-03-06 16:24:16 UTC


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