Bug 768920

Summary:	Dell Studio 17 laptop will not reactivate after suspend
Product:	[Fedora] Fedora	Reporter:	Bill Norman <bluevox.inc>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	16	CC:	gansalmon, itamar, jgotts, jonathan, kernel-maint, madhu.chinakonda
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-01-13 20:21:47 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Bill Norman 2011-12-19 12:35:48 UTC

Description of problem: Dell Studio 17 laptop will not reactivate after placing machine in suspend state. This feature worked fine for all previous kernel versions of FC16 I have run on this machine. 

If I boot using last kernel version 3.1.4-1.fc16.x86_64 suspend works as expected.


Version-Release number of selected component (if applicable):Linux kernel 3.1.5-2.fc16.x86_64


How reproducible:

Select Suspend from Gnome 3.2 user menu. 
 Machine suspends as usual
Press power button to reactivate machine
 System buttons scan/light up. Screen flashes then blanks out. 
 System lights remain on. No screen or keyboard action.

Comment 1 John Gotts 2011-12-26 00:25:09 UTC

Does booting with pci=nocrs fix the problem?

Comment 2 Bill Norman 2012-01-03 22:42:47 UTC

(In reply to comment #1)
> Does booting with pci=nocrs fix the problem?

I added the boot option to /boot/grub2/grub.cfg. Here is the entry for starting the 3.1.6 kernel. 


linux   /vmlinuz-3.1.6-1.fc16.x86_64 root=/dev/mapper/vg_mrroboto-lv_root ro rd.lvm.lv=vg_mrroboto/lv_root rd.md=0 rd.dm=0  KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 rd.lvm.lv=vg_mrroboto/lv_swap LANG=en_US.UTF-8 pci=nocrs

I still could not recover from a suspend.

Comment 3 Bill Norman 2012-01-03 22:51:23 UTC

Just to be clear, the 3.1.4-1 kernel suspend works fine whether or not I boot w/ pci=nocrs.

Comment 4 Josh Boyer 2012-01-03 22:56:07 UTC

Please try kernel-3.1.7-1.fc16 which will be in the next f16-updates-testing push.

Comment 5 Bill Norman 2012-01-13 20:21:47 UTC

This is fixed in kernel-3.1.7-1

Thanks! Works great now.