[Lenovo ThinkPad E440] Ubuntu 14.04 doesn't recover from suspend

Bug #1388618 reported by Tsvetomir Dimitrov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

After the system is suspended it doesn't recover. The screen remains black, the led still blinks (indicating that the laptop is suspended). The power button also doesn't start the system.

WORKAROUND: Disable USB3 support from bios.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-39-generic 3.13.0-39.66
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ceco 2126 F.... pulseaudio
 /dev/snd/controlC1: ceco 2126 F.... pulseaudio
CurrentDesktop: Unity
Date: Sun Nov 2 20:55:42 2014
HibernationDevice: RESUME=UUID=05fb3337-4136-46a2-8288-a9142306c863
MachineType: LENOVO 20C500F8BM
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=3e73d4c0-26cc-40b2-be4d-62c36f2707ec ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-39-generic N/A
 linux-backports-modules-3.13.0-39-generic N/A
 linux-firmware 1.127.7
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/14/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: J9ET96WW (2.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20C500F8BM
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 PRO
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrJ9ET96WW(2.16):bd10/14/2014:svnLENOVO:pn20C500F8BM:pvrThinkPadEdgeE440:rvnLENOVO:rn20C500F8BM:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20C500F8BM
dmi.product.version: ThinkPad Edge E440
dmi.sys.vendor: LENOVO

Revision history for this message
Tsvetomir Dimitrov (tdimitrov) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote : Re: Ubuntu 14.04 doesn't recover from suspend on ThinkPad E440

Tsvetomir Dimitrov, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested exactly shown as:
kernel-fixed-upstream-3.18-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

tags: added: latest-bios-2.16
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
summary: - Ubuntu 14.04 doesn't recover from suspend on ThinkPad E440
+ [Lenovo ThinkPad E440] Ubuntu 14.04 doesn't recover from suspend
description: updated
penalvch (penalvch)
description: updated
description: updated
tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-3.18.0-031800rc3-generic
Revision history for this message
penalvch (penalvch) wrote :

Tsvetomir Dimitrov, did this problem not occur in a release prior to Trusty?

As well, could you please provide the missing information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

tags: added: kernel-bug-exists-upstream-3.18-rc3
removed: kernel-bug-exists-upstream-3.18.0-031800rc3-generic
Revision history for this message
Mike (triple-eh) wrote :

I have not disabled USB3 yet to see if the problem goes away (that leaves the problem of not having USB3 capability), but I can confirm this bug affected my Lenovo Z580 only after updating to kernel 3.13.0-39-generic.

Hitting the power button, after waiting 30 seconds for the system to wake from suspend, woke up the system but networking was disabled and nothing would bring it back except for a full system restart.

Revision history for this message
penalvch (penalvch) wrote :

Mike, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Revision history for this message
Tsvetomir Dimitrov (tdimitrov) wrote :

Christopher M. Penalver, thank you for your assistance.
I own this laptop for a month and I haven't installed any other Ubuntu releases. I can download 13.10 and 13.04, boot them from USB and try to suspend. Is this helpful?
I'll attach the info about the kernel suspend as soon as I get back home.

Revision history for this message
penalvch (penalvch) wrote :

Tsvetomir Dimitrov, it would be more helpful if to rule out a regression is to test 12.04.0 (kernel 3.2.x) via http://old-releases.ubuntu.com/releases/12.04.0/ (live environment is fine).

Revision history for this message
Tsvetomir Dimitrov (tdimitrov) wrote :

Attached dmesg with resume-trace.

My clock wasn't messed up after the resume-trace so I am afraid I've done something wrong.
For reference, here is the magic number from the file:

[ 2.951140] Magic number: 6:273:495

I see no hash matches line.

Revision history for this message
Tsvetomir Dimitrov (tdimitrov) wrote :

And also /proc/acpi/wakeup output

Revision history for this message
Tsvetomir Dimitrov (tdimitrov) wrote :

Absolutely the same behavior with 12.04.3

uname -a
Linux ubuntu 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 16:19:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
penalvch (penalvch) wrote :

Tsvetomir Dimitrov, just to clarify, 12.04.0 (kernel 3.2.x) is not 12.04.3.

Revision history for this message
Tsvetomir Dimitrov (tdimitrov) wrote :

Christopher M. Penalver, sorry about that. Just tested with 12.04 - same result.
Here's the output from uname -a:

Linux ubuntu 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Is the resume-trace good? If you want me to test something else - I'm available.

Revision history for this message
penalvch (penalvch) wrote :

Tsvetomir Dimitrov, the issue you are reporting is an upstream one. Could you please report this problem to the appropriate mailing list (linux-acpi) by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked.

Thank you for your understanding.

Changed in linux (Ubuntu):
status: Incomplete → Triaged
penalvch (penalvch)
tags: added: precise
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.