Lenovo Helix does not wake up from suspend

[Oliver Kirchkamp]

System goes to sleep, indicator does flash slowly as expected, but there is no way to wake up (Power Button, Lid open, Enter, ...). The only way to recover is to press power button for more than 4 seconds, and then power on again. pm-hibernate does work.

I tried disabling thinkpad_acpi but this didn't change anything.

Problem appears with 4.2.0-18-generic kernel, also with 4.4-rc2 (also under Debian testing kernel 4.2.6-1)

Problem appears with terminal pm-suspend (with and without X running), lid close suspend, gui suspend.

The “resume-trace” yields the following magic:
[ 2.228057] Magic number: 1:0:0
[ 2.228158] rtc_cmos 00:02: setting system clock to 2001-01-01 00:00:18 UTC (978307218)

(while without resume trace it says
[ 2.226884] Magic number: 7:269:577
[ 2.226985] rtc_cmos 00:02: setting system clock to 2015-11-30 09:33:06 UTC (1448875986)
)

The content of /proc/acpi/wakeup (with 4.4-rc2) is the following:

Device S-state Status Sysfs node
LID S4 *enabled platform:PNP0C0D:00
SLPB S3 *enabled platform:PNP0C0E:00
IGBE S4 *disabled
PXSX S4 *disabled
EXP2 S4 *disabled pci:0000:00:1c.1
PXSX S4 *disabled pci:0000:06:00.0
PXSX S4 *disabled
XHCI S3 *enabled pci:0000:00:14.0
EHC1 S3 *disabled
PWRB S0 *enabled platform:PNP0C0C:00

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-18-generic 4.2.0-18.22
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: i3
Date: Sun Nov 29 18:43:47 2015
HibernationDevice: RESUME=UUID=f98d2c71-4853-418e-a6e7-8ab0b045b03b
InstallationDate: Installed on 2015-11-27 (2 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: LENOVO 20CGCTO1WW
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed root=UUID=7c946f64-259a-4f17-9583-1a6797af1250 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-18-generic N/A
 linux-backports-modules-4.2.0-18-generic N/A
 linux-firmware 1.149.2
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/21/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: N17ET80W (1.80 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20CGCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50512 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 11
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrN17ET80W(1.80):bd08/21/2015:svnLENOVO:pn20CGCTO1WW:pvrThinkPadHelix2nd:rvnLENOVO:rn20CGCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct11:cvrNone:
dmi.product.name: 20CGCTO1WW
dmi.product.version: ThinkPad Helix 2nd
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Oliver Kirchkamp, 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 from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

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.

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

Thank you for your understanding.

[penalvch (penalvch)]

Oliver Kirchkamp, could you please provide the missing information from https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[Oliver Kirchkamp (21-oliver)]

Here is the full dmesg requested in https://wiki.ubuntu.com/DebuggingKernelSuspend

[Oliver Kirchkamp (21-oliver)]

Regarding your question about different releases: The Lenovo helix requires kernel 4.2 and above (otherwise it does not detect its keyboard). So I can not say anothing about pre 15.10 releases.

As I said above, the problem also occurs with Debian testing.

[jonnieo (jonnie-o)]

Hi, is there any update on this? I have had the same bug for ages, and reported it to the linux-acpi mailing list but got no response. http://www.spinics.net/lists/linux-acpi/msg57233.html

Is this an ubuntu bug or a kernel bug? Presumably the latter, in which case, maybe this should be reported to the thinkpad-acpi-devel list? I am happy to help test any patches.

Jonathan

[Oliver Kirchkamp (21-oliver)]

At Tue, 05 Jan 2016 20:50:25 -0000, jonnieo wrote:
> Hi, is there any update on this?

Hi Jonathan

not that I know. If you want to report this to the thinkpad-acpi-devel
list, go ahead :-)

Best

Oliver

[Henrique de Moraes Holschuh (hmh)]

We don't deal with GPUs or generic ACPI in thinkpad-acpi-devel, just with the thinkpad-acpi driver.

Please do this: remove the thinkpad-acpi driver (make it so it won't autoload, maybe renaming it). Reboot. Test.

If the problem persists, we cannot help you in the thinkpad-acpi-devel. If the problem disappears, contact me directly and we will find the bug and squash it.

[Henrique de Moraes Holschuh (hmh)]

Please make sure you are running the latest UEFI firmware from Lenovo. I didn't check this, but there might be a newer one:

Your CPU microcode is outdated. Intel microcode updates fix a lot more than just CPU microcode, they can also workaround or fix some issues with other circuits inside the processor package, such as the power management controllers, interconnects, etc.

Please install the "intel-microcode" package, version 3.20151106.1 or later, and reboot to activate it. It contains microcode 0x22 for your CPU, which should be reported in /proc/cpuinfo.

[Oliver Kirchkamp (21-oliver)]

(1) I did update the bios. Output from dmidecode reads now...

N17ET83W (1.83 )
12/02/2015

(2) I installied microcode 0x22 from "intel-microcode" package, version 3.20151106.1

(3) I disabled thinkpad_acpi

None of this or any combination thereof yields any improvement.

Hibernation does work, suspend does not work. Suspend can only be initiated (and seems to lead to a substantial battery drain), but the only way to return from suspend is a hard power-off.

[Christian (list-christian)]

Hi there,
I have the same behaviour on a Lenovo Thinkpad Yoga, running
- Linux Mint 18.2 (hence Ubuntu 16.04)
- 4.10.0-38-generic
- Lenovo BIOS Version: GQET52WW (1.32), Release Date: 05/04/2017
- intel-microcode 3.20170707.1~ubuntu16.04.0

Only difference is, that standby randomly works (maybe 4 out of 10 times)

What is the status of this? It seems abandoned for a year now without a solution. Can I help somehow with debug information?

Regards
  Chris

[Oliver Kirchkamp (21-oliver)]

At Mon, 06 Nov 2017 10:45:41 -0000, Christian List wrote:
> What is the status of this?

Chris

I checked recently with a current 4.9 Kernel - no change, the Helix still does not want to wake up from suspend.

Best

Oliver

[penalvch (penalvch)]

Oliver Kirchkamp, the latest mainline kernel is now 4.14-rc8. Could you please update your BIOS, and if still reproducible, test 4.14-rc8 and advise to the results?

Once tested, please post the results of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

[Oliver Kirchkamp (21-oliver)]

At Mon, 06 Nov 2017 12:55:36 -0000, Christopher M. Penalver wrote:
> Oliver Kirchkamp, the latest mainline kernel is now 4.14-rc8. Could you
> please update your BIOS, and if still reproducible, test 4.14-rc8 and
> advise to the results?

Dear Christopher M. Penalver

thank you for your email. Sorry, I fear I will not be able to do this - too many commitments.

Best

Oliver

[penalvch (penalvch)]

Oliver Kirchkamp, fair enough. To advise, without providing requested information, it would be most difficult for developers to pursue a root cause to your issue.

Hence, would you like this report to remain open for when your schedule opens up, or would you like to close this report as Status Invalid?

[Christian (list-christian)]

I disagree to move this to invalid (Not only still I have that bug as well), as it was already on triaged, hence a problem to be looked in.

Would it make sense, that I check with the latest kernel?

Regards
  Chris

[penalvch (penalvch)]

Christian List, it will be most helpful if you use the computer the problem is reproducible with, and file a new report with Ubuntu by using the default repository kernel (not mainline/upstream/3rd party) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

[Christian (list-christian)]

Hi Christopher,

not sure if I understand. Do you have a definition page of the different kinds of kernels you mentioned?
With repository kernel I would understand an available kernel via repository sources. However would Linux Mint be considered as a 3rd party?
Next question would be which version is preferred? The latest available one? (In my case 4.13.0-16.19, running right now 4.10.0-38.42)

Regards
  Chris

[penalvch (penalvch)]

Christian List, please use Ubuntu via http://cdimage.ubuntu.com/daily-live/current/ and report using it.

[Oliver Kirchkamp (21-oliver)]

At Sun, 19 Nov 2017 20:13:35 -0000, Christopher M. Penalver wrote:
> ...would you like this report to remain open for when your schedule
> opens up, or would you like to close this report as Status Invalid?...

Dear Christopher M. Penalver

as far as I am concerned, I fear I will not be able to contribute during the foreseeable future. If this means the issue must be closed, then so be it.

Best

Oliver
--
https://www.kirchkamp.de/

[Kai-Heng Feng (kaihengfeng)]

My guess is that it doesn't support S3 at all.

Does suspend work on v4.14?

[Launchpad Janitor (janitor)]

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