[Lenovo E450] S3 executed failure unsuccessully and there is a Critical Failure in suspend_single log.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Medium
|
Adam Lee | ||
linux (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
linux-lts-utopic (Ubuntu) |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
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-
ProcVersionSign
Uname: Linux 3.16.0-30-generic x86_64
NonfreeKernelMo
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)
description: | updated |
tags: | added: blocks-hwcert |
Changed in hwe-next: | |
assignee: | nobody → Adam Lee (adam8157) |
Changed in hwe-next: | |
importance: | Undecided → Medium |
Changed in linux-lts-utopic (Ubuntu): | |
importance: | Undecided → Medium |
Changed in linux-lts-utopic (Ubuntu): | |
status: | New → Confirmed |
FAILED [MEDIUM] ShortSuspend: Test 1, Unexpected: S3 slept for 5 seconds, less ToSuspend: Test 1, CRITICAL Kernel message: [
than the expected 30 seconds.
FAILED [CRITICAL] PmDevicesFailed
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).