Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #65026 > unrolled thread

Bug#939170: linux: does not suspend completely, locks up

Started by"Daniel M." <danielHL.83@googlemail.com>
First post2019-09-02 01:20 +0200
Last post2020-09-17 10:10 +0200
Articles 9 — 7 participants

Back to article view | Back to linux.debian.kernel


Contents

  Bug#939170: linux: does not suspend completely, locks up "Daniel M." <danielHL.83@googlemail.com> - 2019-09-02 01:20 +0200
    Bug#939170: linux-image-5.2.0-2-amd64: does not suspend completely, locks up Moritz Schlarb <schlarbm@uni-mainz.de> - 2019-09-05 22:00 +0200
    Bug#939170: Also with systemctl suspend "Daniel M." <danielhl.83@googlemail.com> - 2019-09-22 18:10 +0200
    Bug#939170: linux: does not suspend completely, locks up Marc Bonnor <mabo@myask.xyz> - 2019-09-23 12:00 +0200
    Bug#939170: Maybe wrong package? "Daniel M." <danielhl.83@googlemail.com> - 2019-10-20 16:10 +0200
    Bug#939170: linux: does not suspend completely, locks up Felix Rublack <frubi@frubi.net> - 2020-01-26 18:20 +0100
    Bug#939170: linux: does not suspend completely, locks up "Daniel M." <danielhl.83@googlemail.com> - 2020-03-14 14:30 +0100
      Bug#939170: linux: does not suspend completely, locks up Frank Loeffler <frank.loeffler@uni-jena.de> - 2020-04-27 21:50 +0200
    Bug#939170: linux: does not suspend completely, locks up Borys Jurgiel <lists@borysjurgiel.pl> - 2020-09-17 10:10 +0200

#65026 — Bug#939170: linux: does not suspend completely, locks up

From"Daniel M." <danielHL.83@googlemail.com>
Date2019-09-02 01:20 +0200
SubjectBug#939170: linux: does not suspend completely, locks up
Message-ID<yBHiy-63X-7@gated-at.bofh.it>
Source: linux
Version: 5.2.9-2
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Since the update from 4.19 to 5.2.9 my Lenovo Thinkpad E460 no longer suspends properly. If I 
close the lid or chose Suspend from the KDE launcher, the system will start to suspend but never 
reaches standby. Power light will blink as usual, display backlight turns off but keyboard LEDs 
don't turn off, fan is still active.

The system doesn't respond to Ctrl-Alt-Del or change to a Terminal. No input changes anything. 
Waiting (30min) doesn't help either. Rebooting to Kernel 4.19 fixes the problem immediatly.

Expected outcome would be a complete suspend/standby state and a complete recovery/powerup on
lid open or press of any key.


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (20, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

[toc] | [next] | [standalone]


#65044 — Bug#939170: linux-image-5.2.0-2-amd64: does not suspend completely, locks up

FromMoritz Schlarb <schlarbm@uni-mainz.de>
Date2019-09-05 22:00 +0200
SubjectBug#939170: linux-image-5.2.0-2-amd64: does not suspend completely, locks up
Message-ID<yD65b-5R7-3@gated-at.bofh.it>
In reply to#65026
Source: linux
Version: 5.2.9-2
Followup-For: Bug #939170

Hi everyone,

I'm seeing the same issue with linux-image-5.2.0-2-amd64=5.2.9-2 on Lenovo
Thinkpad X1 Carbon 4th Gen.

Best regards,
Moritz



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (800, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

[toc] | [prev] | [next] | [standalone]


#65153 — Bug#939170: Also with systemctl suspend

From"Daniel M." <danielhl.83@googlemail.com>
Date2019-09-22 18:10 +0200
SubjectBug#939170: Also with systemctl suspend
Message-ID<yJcAV-2q7-5@gated-at.bofh.it>
In reply to#65026
Hi,

this also happens to me when I try systemctl suspend instead of a GUI
action. So it's not a problem of the desktop environment but of kernel
or even systemd.

Maybe something with the thinkpad kernel module?

Cheers,
Daniel

[toc] | [prev] | [next] | [standalone]


#65159

FromMarc Bonnor <mabo@myask.xyz>
Date2019-09-23 12:00 +0200
Message-ID<yJtip-5bp-1@gated-at.bofh.it>
In reply to#65026
Hi,

I think I may have the same problem.

When I shutdown or restart my laptop the process proceeds as normal to
the point where the last message printed on the screen is "Reached
target power-off" and then nothing happens. I then need to push and
hold power button until power switches off.

I setup Systemd persistent logs to allow me to view log messages up
until power off, but again nothing jumps out as being a problem.

I have a Lenovo ThinkPad Laptop; 

DMI: LENOVO 20JAA00FAU/20JAA00FAU, BIOS R0MET48W (1.25) 04/22/2019.


I found this Systemd Debugging tip;

poweroff -f

If this command doesn't work, then Systemd is unlikely to be the
problem and it may be kernel related.

When I tried this command the GUI screen froze and there was a loud
annoying continuous beep.

Pressing and holding the power button turned off the laptop.

[toc] | [prev] | [next] | [standalone]


#65417 — Bug#939170: Maybe wrong package?

From"Daniel M." <danielhl.83@googlemail.com>
Date2019-10-20 16:10 +0200
SubjectBug#939170: Maybe wrong package?
Message-ID<yTk49-5Al-3@gated-at.bofh.it>
In reply to#65026
Hi,

is it possible this one is reported against the wrong package? It
seems like there are a few lenovo laptop / thinkpad owners who
experience this. Is there some (pseudo)package to report this to?
Maybe it gets a bit more traction there...

Cheers,
Daniel

[toc] | [prev] | [next] | [standalone]


#66212

FromFelix Rublack <frubi@frubi.net>
Date2020-01-26 18:20 +0100
Message-ID<zsTJL-2eW-7@gated-at.bofh.it>
In reply to#65026
Hi everyone,

I have the same issue on a ThinkPad T460s (suspend works only half way,
reboot and poweroff stop just short before actual shutdown).

I bisected the problem to the TPM driver. Blacklisting the module in
modprobe.d fixed the problem for me.

Sample configuration: /etc/modprobe.d/blacklist-tpm.conf

# Prevent TPM from loading. It breaks suspend and power cycle.
blacklist tpm
blacklist tpm_crb
blacklist tpm_tis
blacklist tpm_tis_core

Greetings
Felix Rublack

[toc] | [prev] | [next] | [standalone]


#66539

From"Daniel M." <danielhl.83@googlemail.com>
Date2020-03-14 14:30 +0100
Message-ID<zKf1w-32F-1@gated-at.bofh.it>
In reply to#65026
On Sun, 26 Jan 2020 18:03:23 +0100 Felix Rublack <frubi@frubi.net> wrote:
> Hi everyone,
>
> I have the same issue on a ThinkPad T460s (suspend works only half way,
> reboot and poweroff stop just short before actual shutdown).
>
> I bisected the problem to the TPM driver. Blacklisting the module in
> modprobe.d fixed the problem for me.
>
> Sample configuration: /etc/modprobe.d/blacklist-tpm.conf
>
> # Prevent TPM from loading. It breaks suspend and power cycle.
> blacklist tpm
> blacklist tpm_crb
> blacklist tpm_tis
> blacklist tpm_tis_core
>
> Greetings
> Felix Rublack

Hi, thanks a lot! I can confirm that this works also on my Thinkpad
E460. Since you can probably provide more details, could you forward
this to kernel.org?

Cheers,
Daniel

[toc] | [prev] | [next] | [standalone]


#66898

FromFrank Loeffler <frank.loeffler@uni-jena.de>
Date2020-04-27 21:50 +0200
Message-ID<A0hVn-1TG-1@gated-at.bofh.it>
In reply to#66539

[Multipart message — attachments visible in raw view] — view raw

On Sat, Mar 14, 2020 at 02:23:05PM +0100, Daniel M. wrote:
>On Sun, 26 Jan 2020 18:03:23 +0100 Felix Rublack <frubi@frubi.net> wrote:
>> Hi everyone,
>>
>> I have the same issue on a ThinkPad T460s (suspend works only half way,
>> reboot and poweroff stop just short before actual shutdown).
>>
>> I bisected the problem to the TPM driver. Blacklisting the module in
>> modprobe.d fixed the problem for me.
>>
>> Sample configuration: /etc/modprobe.d/blacklist-tpm.conf
>>
>> # Prevent TPM from loading. It breaks suspend and power cycle.
>> blacklist tpm
>> blacklist tpm_crb
>> blacklist tpm_tis
>> blacklist tpm_tis_core
>>
>> Greetings
>> Felix Rublack
>
>Hi, thanks a lot! I can confirm that this works also on my Thinkpad
>E460. Since you can probably provide more details, could you forward
>this to kernel.org?

Hi,

just to add one tiny bit of confirmation: this helped also in my case 
(big thanks!):

I am on Buster with a Lenovo Thinkpad T460, with kernels 4.19.0.8 and 
5.4.0.0.bpo.4 installed. Suspend works fine with 4.19.0.8. The same 
system fails consistently when booted with 5.4, in the same way reported 
earlier: the system starts to suspend, but stops somewhere close to the 
finish line: display is black (don't remember if backlight was off, but 
I think it was), power-led is blinking, but the led-indicators like mute 
stay on. I cannot say something about the fan, as it is usually not 
running for me anyway. Nothing brings the laptop back at this stage 
other than pressing the power-button for like 10 seconds (complete 
restart): no shorter press of the power button, no lid action. Both 
should, and with the 4.19 kernel, do.

With above blacklisting, suspend now also works for kernel version 5.4.

Big thanks again - and it would be interesting to follow this at the 
kernel.org-level (to know when to remove the blacklist again).

Frank Löffler

[toc] | [prev] | [next] | [standalone]


#68147

FromBorys Jurgiel <lists@borysjurgiel.pl>
Date2020-09-17 10:10 +0200
Message-ID<APX9o-76C-9@gated-at.bofh.it>
In reply to#65026
ThinkPad T460s: Instead of blacklisting the module, I just switched from 
"Intel PTT" to "Discrete TPM" in BIOS and everything works perfectly now.

Thanks a lot from me too!
Borys

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web