[Lenovo E450] S3 executed failure unsuccessully and there is a Critical Failure in suspend_single log.

[Gabriel Zhi Chen]

CID : 201407-15368 Lenovo E450 (A+A) with 14.04.2 (utopic)

Steps:
1. Install 14.04.2 on E450
2. Click 'suspend' from the gear icon on the top right corner.

Expected result:
S3 executed successfully.

Actual result:
1, After click 'Suspend', screen became black in 2 second. Then it will light and come to log in interface.
2. There is a critical failure in suspend_single log.
 s3: CRITICAL Kernel message: [ 6726.173917] PM: Some devices failed to suspend, or early wake event detected
3. There is a Medium failures in the log.
 s3: Unexpected: S3 slept for 5 seconds, less than the expected 30 seconds.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 [modified: boot/vmlinuz-3.16.0-30-generic]
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Mar 19 06:04:27 2015
InstallationDate: Installed on 2015-03-18 (1 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
SourcePackage: linux-lts-utopic
UpgradeStatus: No upgrade log present (probably fresh install)

[Keng-Yu Lin (lexical)]

FAILED [MEDIUM] ShortSuspend: Test 1, Unexpected: S3 slept for 5 seconds, less
than the expected 30 seconds.
FAILED [CRITICAL] PmDevicesFailedToSuspend: Test 1, CRITICAL Kernel message: [
6726.173917] PM: Some devices failed to suspend, or early wake event detected

ADVICE: This is a bug picked up by the kernel, but as yet, the firmware test
suite has no diagnostic advice for this particular problem.

@Gabriel will need /var/log/kern.log to debug (of course it should contain the failure).

[Gabriel Zhi Chen (gabrielzchen)]

@Keng-Yu, please refer to kern.log in attachment. Thanks.

[Keng-Yu Lin (lexical)]

@Gabirel, I checked the kern.log, there were a few successful times of s3. does this bug have a failure rate to reproduce? or if the s3 hangs always?

If it has a failure rate, can you roughly estimate the value?

[Adam Lee (adam8157)]

@Keng-Yu, that was not "successful", it suspended and resumed immediately.

[Adam Lee (adam8157)]

In Ubuntu 15.04(vivid), it works well.