Bug 699695

Summary:	Suspend stopped working with 2.6.35.12-88.fc14 on ASUS F3e
Product:	[Fedora] Fedora	Reporter:	Jan "Yenya" Kasprzak <kas>
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:	14	CC:	gansalmon, itamar, 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:	2011-04-27 01:17:34 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 Jan "Yenya" Kasprzak 2011-04-26 12:02:41 UTC

Description of problem:
On my laptop (ASUS F3e) suspend-to-RAM stopped working after upgrade to 2.6.35.12-88 kernel. Under the previous kernel (2.6.35.11-83.fc14) suspend/resume works as expected.

Version-Release number of selected component (if applicable):
kernel-2.6.35.12-88.fc14.x86_64

How reproducible:
100 %

Steps to Reproduce:
1. Install F14 on ASUS F3E
2. Upgrade to the latest kernel
3. log in, configure the power button as suspend-to-RAM, press the power button
  
Actual results:
The system tries to suspend itself but immediately comes back with locked screen (as it usually does after the resume). After typing in my password, I can continue working.


Expected results:
The system should suspend itself.

Additional info:
dmesg output from the time of attempted suspend:
[  149.728920] PM: Syncing filesystems ... done.
[  149.730637] PM: Preparing system for mem sleep
[  149.830313] Freezing user space processes ... (elapsed 0.01 seconds) done.
[  149.841085] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
[  149.852046] PM: Entering mem sleep
[  149.852091] Suspending console(s) (use no_console_suspend to debug)
[  149.854422] btusb_intr_complete: hci0 urb ffff880078e8b300 failed to resubmit (1)
[  149.855436] btusb_bulk_complete: hci0 urb ffff880078e8b900 failed to resubmit (1)
[  149.856418] btusb_bulk_complete: hci0 urb ffff880078e8b0c0 failed to resubmit (1)
[  149.867159] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[  149.867360] sd 0:0:0:0: [sda] Stopping disk
[  150.268093] tpm_tis 00:0b: Operation Timed out
[  150.268104] legacy_suspend(): pnp_bus_suspend+0x0/0x85 returns -62
[  150.268109] PM: Device 00:0b failed to suspend: error -62
[  150.268113] PM: Some devices failed to suspend
[  150.515461] sd 0:0:0:0: [sda] Starting disk
[  151.850150] PM: resume of devices complete after 1582.032 msecs
[  151.850330] PM: Finishing wakeup.
[  151.850331] Restarting tasks ... done.
[  151.850707] video LNXVIDEO:00: Restoring backlight state
[  152.151990] atl1 0000:03:00.0: irq 50 for MSI/MSI-X

Comment 1 Chuck Ebbert 2011-04-27 01:17:34 UTC


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