No resume on ThinkPad Helix -- system keeps sleeping

Bug #1424088 reported by Dean Stanton
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Lenovo ThinkPad Helix is a "Convertable Ultrabook" with an Intel Core-M ("Broadwell") processor. The tablet can come off the dock-with-keyboard and latch to it as a cover.

Attempting a suspend is apparently successful. The LED (on the back of the tablet pulsates).

But neither attaching the tablet in its open position nor pressing the power button will wake the system to resume. The LED continues to pulsate and the system continues to be unreachable by Ethernet.

As a "workaround" I can suspend with pm-suspend-hybrid and then when it does not resume I can force power off and turn it back on. This causes it to thaw.

None of the pm-action "quirk" options helped.

Description: Ubuntu 14.04.2 LTS
Release: 14.04
I have also tried Ubuntu 14.10.1 and it also has this issue.

The kernel message insists that I attach /sys/class/drm/card0/error but that file is empty.

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
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 20 14:08:57 2015
InstallationDate: Installed on 2015-02-20 (0 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)

Revision history for this message
Dean Stanton (dstanton) wrote :

Adding additional logs.

Revision history for this message
Tom Li (biergaizi2009) wrote :

I also hit by this bug. I can confirmed this bug with Linux 4.0.0.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-lts-utopic (Ubuntu):
status: New → Confirmed
penalvch (penalvch)
affects: linux-lts-utopic (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Branimir Ackovic (branimir-ackovic) wrote :

I have the same problem. Any ideas?

Revision history for this message
penalvch (penalvch) wrote :

Branimir Ackovic, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

Revision history for this message
penalvch (penalvch) wrote :

Dean Stanton, thank you for reporting this and helping make Ubuntu better. However, your crash report is manually attached.

Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y dist-upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open a terminal, navigate to your /var/crash directory and file your report with:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

where _my_crash_report.crash is the crash you would like to report. By default, this sends the crash to the Ubuntu Error Tracker infrastructure, which is different than Launchpad. For more on this, please see https://wiki.ubuntu.com/ErrorTracker .

However, if after doing this you would still like to have a crash report posted to Launchpad, for example to ease triage and add others to your report, one would need to open the following file via a terminal:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and file the crash report via:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

If you do open this report, please feel free to subscribe me to it.

However, I'm closing this report since the process outlined above will deal with this issue more efficiently. Also, please do not attach your crash report manually to this report and reopen it. Thank you for your understanding.

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

Changed in linux (Ubuntu):
importance: Low → Undecided
status: Expired → Invalid
Revision history for this message
jMyles (justin-justinholmes) wrote :

I am also affected by this bug. How can I help?

Revision history for this message
penalvch (penalvch) wrote :

jMyles (justin-justinholmes), to clarify, do you have a crash file in /var/crash after the issue?

Revision history for this message
jMyles (justin-justinholmes) wrote :

Hey Christopher. No, I don't have a crash file.

Revision history for this message
penalvch (penalvch) wrote :

jMyles (justin-justinholmes), then it would appear you have a different problem.

Hence, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

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.