[Lenovo Thinkpad X260] System freezes after closing lid

Bug #1552906 reported by Simon P.
80
This bug affects 15 people
Affects Status Importance Assigned to Milestone
Linux
Unknown
Unknown
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

My current Ubuntu version is 14.04.4 but I also tried 15.10.
Regardless of the Ubuntu version there is a serious problem with my new Thinkpad X260 when it is in battery mode and I close and reopen the lid. The problem is not affecting the suspend mode as it still occurs when this mode is disabled.

what I expect to happen: After closing the lid the screen goes off. When I open the lid again, screen goes on and I can use the laptop.

what happens every time: When I close the lid the screen turns black. When I open the lid again the screen displays the system but it is frozen and does not react on input.

Interestingly I can not reproduce this problem when the laptop is connected to an AC power source.
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: simon 1437 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=76bcd0ad-fc42-4d1a-8089-0f10d23df682
InstallationDate: Installed on 2016-03-03 (0 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc.
 Bus 001 Device 003: ID 04ca:7058 Lite-On Technology Corp.
 Bus 001 Device 005: ID 8087:0a2b Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20F5S0EU00
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic.efi.signed root=UUID=fa7f6b64-3d57-43ce-a52b-5323c46dd0ca ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-27-generic N/A
 linux-backports-modules-4.2.0-27-generic N/A
 linux-firmware 1.127.20
Tags: trusty
Uname: Linux 4.2.0-27-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/25/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: R02ET44W (1.17 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20F5S0EU00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrR02ET44W(1.17):bd01/25/2016:svnLENOVO:pn20F5S0EU00:pvrThinkPadX260:rvnLENOVO:rn20F5S0EU00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20F5S0EU00
dmi.product.version: ThinkPad X260
dmi.sys.vendor: LENOVO

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1552906

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Simon P. (simpre) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected trusty
description: updated
Revision history for this message
Simon P. (simpre) wrote : BootDmesg.txt

apport information

Revision history for this message
Simon P. (simpre) wrote : CRDA.txt

apport information

Revision history for this message
Simon P. (simpre) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Simon P. (simpre) wrote : IwConfig.txt

apport information

Revision history for this message
Simon P. (simpre) wrote : Lspci.txt

apport information

Revision history for this message
Simon P. (simpre) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Simon P. (simpre) wrote : ProcEnviron.txt

apport information

Revision history for this message
Simon P. (simpre) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Simon P. (simpre) wrote : ProcModules.txt

apport information

Revision history for this message
Simon P. (simpre) wrote : PulseList.txt

apport information

Revision history for this message
Simon P. (simpre) wrote : RfKill.txt

apport information

Revision history for this message
Simon P. (simpre) wrote : UdevDb.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Simon P. (simpre) wrote : UdevLog.txt

apport information

Revision history for this message
Simon P. (simpre) wrote : WifiSyslog.txt

apport information

Revision history for this message
Alexander Müller (donothingloop) wrote : Re: System freezes after closing lid on Thinkpad X260

Hi.

I have exactly the same problem but with a Lenovo Thinkpad T460s.

This is most likely acpi related as I can boot with acpi=off and the freeze does not occur when I close the lid.
I also noticed that acpi=pm does not resolve the problem.

The bug also occurs during the cryptsetups ask-password screen on boot right after grub when you close the lid.

Suspend mode works without any problems when I enter it by clicking on the button.

When connected to an AC adapter, the bug is not reproducible.

Revision history for this message
Alexander Müller (donothingloop) wrote :

The acpi=pm in my last comment was a typo and should be acpi=ht.

Revision history for this message
Simon P. (simpre) wrote :

There also is a kernel bug report about this problem: https://bugzilla.kernel.org/show_bug.cgi?id=113551

When setting intel_pstate=no_hwp as a kernel option like described there, the problem does not occur any more on my X260.

Revision history for this message
penalvch (penalvch) wrote :

Simon P., thank you for reporting this and helping make Ubuntu better.

In order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

Once testing of the latest upstream kernel is complete, please mark this report Status Confirmed. Please let us know your results.

Thank you for your understanding.

tags: added: latest-bios-1.17
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: wily
Simon P. (simpre)
description: updated
tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.5.0-rc7
Revision history for this message
Simon P. (simpre) wrote :

Thanks for your further instructions. I just tested the latest upstream kernel 4.5.0rc7, the problem still exists.

tags: added: kernel-bug-exists-upstream-4.5-rc7
removed: kernel-bug-exists-upstream-4.5.0-rc7
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Simon P., to clarify, after the system freeze, is there a crash file in /var/crash?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Simon P. (simpre) wrote :

No. There are crash files stored in that directory.

Revision history for this message
penalvch (penalvch) wrote :

Simon P.:
Me: "...after the system freeze, is there a crash file in /var/crash?"
You: "No. There are crash files stored in that directory."

Unfortunately, I'm not sure which answer you are providing. Could you please advise?

Revision history for this message
Simon P. (simpre) wrote :

Sorry. I meant to say:

No. There are no crash files stored in that directory.

Revision history for this message
penalvch (penalvch) wrote :

Simon P., could you please capture the crash via https://help.ubuntu.com/community/DebuggingSystemCrash ?

Revision history for this message
Simon P. (simpre) wrote :

I was not able to get information via the linux-crashdump tool, but I added the kern.log file to this comment with information starting from the system start until closing the lid. After closing the lid there was no more new information in the kern.log file and I had to perform a hard reboot.

penalvch (penalvch)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Trent Lloyd (lathiat) wrote :

Upstream bug had a patch posted today:
https://bugzilla.kernel.org/show_bug.cgi?id=110941#c90

Revision history for this message
penalvch (penalvch) wrote :

Simon P., it would be helpful if you confirmed if the upstream patch addresses your issue. Could you please do so following https://wiki.ubuntu.com/Kernel/KernelBisection#Testing_a_newly_released_patch_from_upstream ?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Simon P. (simpre) wrote :

After some difficulties I was able to test the kernel patch today and I can confirm it solves the issue.

A sidenote: It often takes noticeably longer for my PC to enter the suspend mode with the new patched kernel than before.

penalvch (penalvch)
tags: added: cherry-pick kernel-fixed-upstream
Changed in linux (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Russell Jones (russell-jones-oxphys) wrote :

Hello,

The patch committed to 4.4.6-rc1, https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a21211672c9a1d730a39aa65d4a5b3414700adfb (identical to https://git.kernel.org/cgit/linux/kernel/git/rafael/linux-pm.git/commit/?h=bleeding-edge&id=42341f87ba1bee4c5be95038c24abb69cbcf361a ) is newer than https://bugzilla.kernel.org/attachment.cgi?id=209371&action=diff (the one in comment #90 mentioned in c#28 here)

I've applied the newer patch successfully (with some chunk messages) to 4.4.0-14-lts-xenial and 4.4.0-15-lts-xenial on Trusty (T460 and T460s) and 4.4.0-16 on Xenial (T460s). Reportedly the same problem affects X1 Carbon G4s https://www.reddit.com/r/thinkpad/comments/48wp3o/x1_carbon_gen_4_ubuntu_minireview/ (and the Yoga 260 as mentioned in https://bugzilla.kernel.org/show_bug.cgi?id=110941 ) The author says in 110941 "It should work for any 4.4 kernel"

The bug about the T460s is https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1561974 though I'm not sure whether this would count as a duplicate or not given they're different models.

Revision history for this message
Russell Jones (russell-jones-oxphys) wrote :

Specifically I get the output

$ patch -p1 < ../../t460s-smm-pstates.patch
patching file arch/x86/kernel/cpu/mcheck/therm_throt.c
patching file drivers/acpi/acpi_processor.c
patching file drivers/acpi/bus.c
Hunk #1 succeeded at 1004 (offset -1 lines).
patching file drivers/acpi/internal.h
Hunk #1 succeeded at 130 (offset -8 lines).
$

Revision history for this message
Vadim Zaliva (lord-5) wrote :

I am having the same problem and one workaround I have found is to put computer to sleep using menu item on toolbar before closing the lid.

Revision history for this message
Kgorbi (kgorbi) wrote :

The same problem exists on Thinkpad W530, Ubutnu 16.04, Kernel 4.8.0-46-generic, NVidia proprietary drivers 381.09.

Revision history for this message
Thomas Steinbach (thomas-steinbach) wrote :

May there be a regression since Ubuntu 17.04? I have the described problems with my Lenovo ThinkPad T460s: Closing the lid will suspend Ubuntu. After opening the lid the screen is either black (no backlight) or (since Ubuntu 17.10) the lock screen is shown but the system is freezed.

I have appended my syslog from the suspend to the freeze. What other information could I provide?

penalvch (penalvch)
tags: added: bios-outdated-1.33
removed: latest-bios-1.17
Revision history for this message
penalvch (penalvch) wrote :

Thomas Steinbach, given you have different hardware than the original reporter, and a potential regression of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1561974 (not a continuation of the scope of this report), it is best to file a new report via a terminal:
ubuntu-bug linux

Feel free to subscribe me to it.

summary: - System freezes after closing lid on Thinkpad X260
+ [Lenovo Thinkpad X260] System freezes after closing lid
Revision history for this message
penalvch (penalvch) wrote :

Simon P., to advise, the patch that you tested as fixing your issue was released for later versions of the Ubuntu kernel as per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1561974 .

Could you please confirm if one of the following works for you:
1) With 14.04 using the kernel enablement stack in: https://wiki.ubuntu.com/Kernel/LTSEnablementStack
2) Using Xenial (16.04) or later?

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Simon P. (simpre) wrote :

Yes I can confirm that the problem was fixed for my hardware. 16.04 and 17.10 both work well.

Revision history for this message
Thomas Steinbach (thomas-steinbach) wrote :

Christopher M., thank you for your support. I will do so.

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.