Lenovo Thinkpad X1 Carbon 7th Gen doesn't suspend and resume

[Anmar Oueja]

Steps:

1. Install Ubuntu 20.04 daily image (tested Jan 29th, 2020 image) using default options.
2. apt update
3. apt upgrade
4. reboot so the machine is in pristine state
5. Close lid
6. Machine doesn't suspend (the light on the laptop power button doesn't pulsate)
7. Open the lid. The system doesn't respond and display is off
8. the only option is to power down the laptop and restart it.
9. upon restarting, Apport doesn't complain (this report was filed manually using ubuntu-bug)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-12-generic 5.4.0-12.15
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Jan 30 18:56:41 2020
InstallationDate: Installed on 2020-01-30 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
SourcePackage: linux-signed-5.4
UpgradeStatus: No upgrade log present (probably fresh install)

[Anmar Oueja (anmar)]

One more thing. Debian testing works fine on the same laptop with the same bios set and the sleep state settign in this bios is also setup to "Linux" as per this guide (https://wiki.archlinux.org/index.php/Lenovo_ThinkPad_X1_Carbon_(Gen_7)#Sleep/Suspend)

[Launchpad Janitor (janitor)]

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

[Dean Henrichsmeyer (dean)]

This also affects x1 carbon 5th gen

[Dean Henrichsmeyer (dean)]

I upgraded today to 5.4.0-14-generic and it affects me. It didn't affect me previously.

[Timo Aaltonen (tjaalton)]

there's 5.4.0-15 in focal-proposed, please give it a try

[Seth Forshee (sforshee)]

Possibly a duplicate of bug 1861837. If so, setting snd_hda_intel.dmic_detect=0 should help as a workaround. To do this, create a file named /etc/modprobe.d/snd-hda-intel.conf with the following contents:

 options snd-hda-intel dmic_detect=0

Reboot, then check that the option was set:

 $ cat /sys/module/snd_hda_intel/parameters/dmic_detect

Which should show 'N' if the option was applied. If suspend works with dmic_detect disabled then this is the same issue as in the other bug.

[Dean Henrichsmeyer (dean)]

Seth - suspend does not work with dmic_detect disabled so it looks like it's something else.

[Dean Henrichsmeyer (dean)]

In my case, this turned out to be the kernel crashing when the e1000e module was removed. I rmmod'd that in rc.local because when I originally purchased the laptop, that module would suck power and battery life.

When I stop removing that module, the kernel doesn't crash and suspend, shutdown, etc, all work as designed. I can file a separate bug about that crash if you prefer or paste the crash here.

[Seth Forshee (sforshee)]

Dean, please file a different bug about that issue. Thanks!

On my gen 7 x1 carbon the hang on suspend is fixed with 5.4.0-15 from focal-propopsed.

[Eugene Crosser (crosser)]

I confirm that suspend does not work with 5.4.0-14-generic and does work with 5.4.0-16-generic on Thinkpad X1 Carbon 7gen.

[Misha Merkushin (bibendi)]

I also confirm that updating from 5.4.0-14 to 5.4.0-17 helps me too! I have a Dell 7490

[Eugene Crosser (crosser)]

To add to #11:
5.4.0-16 and 5.4.0-17 go to suspend when the lid is closed, but *only once* after boot. on subsequent attempts, when the lid it closed, backlight and wifi are turned off, but system does not suspend.

First successful suspend:
[ 147.413295] PM: suspend entry (s2idle)
[ 147.416601] Filesystems sync: 0.003 seconds
[ 147.419371] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 147.421210] OOM killer disabled.
[ 147.421210] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 147.422375] printk: Suspending console(s) (use no_console_suspend to debug)
[ 147.422630] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 147.527810] e1000e: EEE TX LPI TIMER: 00000011
[ 150.246317] ACPI: EC: interrupt blocked
[ 881.134544] ACPI: EC: interrupt unblocked
[ 883.933255] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
[ 884.047802] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
[ 884.112730] iwlwifi 0000:00:14.3: FW already configured (0) - re-configuring
[ 886.815475] e1000e 0000:00:1f.6 enp0s31f6: PHY Wakeup cause - Unicast Packet
[ 887.485832] e1000e 0000:00:1f.6 enp0s31f6: Hardware Error
[ 888.016931] OOM killer enabled.
[ 888.016932] Restarting tasks ... done.
[ 888.060613] PM: suspend exit

Second unsuccessful suspend:
[ 907.584802] PM: suspend entry (s2idle)
[ 907.589779] Filesystems sync: 0.004 seconds
[ 907.591416] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 907.593518] OOM killer disabled.
[ 907.593518] Freezing remaining freezable tasks ... (elapsed 0.328 seconds) done.
[ 907.921560] printk: Suspending console(s) (use no_console_suspend to debug)
[ 907.922127] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 908.024438] e1000e: EEE TX LPI TIMER: 00000011
[ 909.916364] PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0x80 [e1000e] returns -2
[ 909.916367] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2
[ 909.916369] PM: Device 0000:00:1f.6 failed to suspend async: error -2
[ 911.183052] PM: Some devices failed to suspend, or early wake event detected
[ 911.197091] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
[ 911.314903] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
[ 911.382438] iwlwifi 0000:00:14.3: FW already configured (0) - re-configuring
[ 911.413624] OOM killer enabled.
[ 911.413625] Restarting tasks ... done.
[ 911.462021] PM: suspend exit

[Seth Forshee (sforshee)]

On Mon, Mar 02, 2020 at 08:52:56AM -0000, Eugene Crosser wrote:
> To add to #11:
> 5.4.0-16 and 5.4.0-17 go to suspend when the lid is closed, but *only once* after boot. on subsequent attempts, when the lid it closed, backlight and wifi are turned off, but system does not suspend.

Eugene, will you please file a new bug for this issue? Thanks!

[Eugene Crosser (crosser)]

Opened as bug 1865570

[Seth Forshee (sforshee)]

@Anmar, I believe this issue should be fixed now. Can you confirm?

[Anmar Oueja (anmar)]

@Seth, Indeed it is fixed. Thanks guys!

[Trebacz (david-trebacz)]

I'm experiencing the bug. Can I I get some general instructions to install "focal"? When is it likely to be integrated into a 5.4 release. or should I wait for another release.

[izolate (izolate)]

I updated to 20.04 and now I have this bug too. Kernel 5.4.26-050426-generic. Anybody aware of a fix?

[Trebacz (david-trebacz)]

It was gone for awhile, but back in the past couple weeks - 5.4.0-40-generic