Buster goes to sleep immediately when switching to console

[grl]

Hi!

I have Debian with Cinnamon and lightdm on a Thinkpad W530. Not sure which release i installed initially, now - after several upgrades I'm running Buster.

Since the update to Buster I have a strange problem:
If I change to a console via Ctrl-F1 the system goes to sleep immediately. Sometimes I can't even see the login prompt of the console. After wake up I'm on the desired console - but only for a minute or so before the system goes to sleep again.
The same happens if I stop lightdm. Tried using gdm3 as well - same behaviour. I tried playing with sleep-inactive-ac-timeout and sleep-inactive-battery-timeout - but no change at all.
Also if I send the system to sleep via GUI and wake it up again It goes to sleep once again if I don't enter my username and password within some minutes - very annoying...

Unfortunately all I could find on google, newsgroups and forums handles either the known problem of going to sleep after 20 minutes (mine goes to sleep immediately, not after 20min) or the other way round - not going to sleep at all!

Any ideas how to get a system that does not fall asleep this fast? Falling asleep is MY job - not my laptops

regards
Lukas

[L_V]

First very very basic investigation.....
* Is your battery in good condition ?
* Any difference if plugged/unplugged to the mains ?

[grl]

First very very basic investigation.....
* Is your battery in good condition ?
* Any difference if plugged/unplugged to the mains ?

Battery is more or less new.
No difference between AC or Battery, on Dock or off Dock.

And it worked with stretch - the problem appeared with the update to buster, so I'd assume that it is not hardware related.

regards
Lukas

[L_V]

Is upower package installed ?
Does this return something wrong ?

Code: Select all

apt install -fs

+ which desktop environment ?

[grl]

Is upower package installed ?
Does this return something wrong ?

Code: Select all

apt install -fs

+ which desktop environment ?

upower is installed.
no problems with apt
and as written in the first post its cinnamon and lightdm.

regards and thanks
Lukas

[L_V]

If you create a new user profile for test, and switch to it, same problem ?

Code: Select all

# adduser test

[grl]

Same behaviour.
But while testing with a different user I noticed something strange:
The problem changes depending if the lid of the Thinkpad was opened or not during start. As I normally work on a docking station the lid is closed while booting or resuming.
I might have done the off-dock tests after booting on-dock - not totally sure about that, but I'll retest.

Now I disabled the lidswitch in /etc/systemd/logind.conf (set HandleLidSwitch, HandleLidSwitchExternalPower and HandleLidSwitchDocked to ignore).

That definitely changed something - just retesting the combinations I can think off.

What I don't get is that its only dependant of the lid DURING BOOT - no difference if the lid is opened or closed after boot....

Lukas

[L_V]

Is acpi installed ?
(I don't say to install it / just a question for the moment).

[grl]

Code: Select all

dpkg -l |grep acpi
ii  acpi                                          1.7-1.1                               amd64        displays information on ACPI devices
ii  acpi-call-dkms                                1.1.0-5                               all          Kernel module that enables you to call ACPI methods
ii  acpi-support-base                             0.142-8                               all          scripts for handling base ACPI events such as the power button
ii  acpid                                         1:2.0.31-1                            amd64        Advanced Configuration and Power Interface event daemon

And thanks for helping!

Lukas

[grl]

OK, after disabling the lidswitch-handling in /etc/systemd/logind.conf the problem seems to be gone away.
I can live with no reaction to the lidswitch - so the immediate problem is solved.

But I would still be interested in learning about the original issue - what changed between stretch and buster. And I can't think of a way the state of the lidswitch AT BOOT affects the whole system...

regards
Lukas

[L_V]

For investigation..

Code: Select all

acpi -V

and and ... I don't know..
Hope you did not tweak too many system files before upgrade.
Probably easier to clarify with a fresh installation.

[grl]

Code: Select all

acpi -V
Battery 0: Unknown, 95%
Battery 0: design capacity 7641 mAh, last full capacity 6481 mAh = 84%
Adapter 0: on-line
Thermal 0: ok, 68.0 degrees C
Thermal 0: trip point 0 switches to mode critical at temperature 103.0 degrees C
Cooling 0: Processor 0 of 10
Cooling 1: Processor 0 of 10
Cooling 2: Processor 0 of 10
Cooling 3: intel_powerclamp no state information available
Cooling 4: Processor 0 of 10
Cooling 5: x86_pkg_temp no state information available
Cooling 6: Processor 0 of 10
Cooling 7: Processor 0 of 10
Cooling 8: Processor 0 of 10
Cooling 9: Processor 0 of 10

I don't exactly know which configuration I tweaked - its an installation I'm using for years. A reinstall I want to avoid as long as possible - way to much programs installed and settings done...

Lukas

[L_V]

Yes, but... some cleaning sometimes helps....

Code: Select all

lscpu |grep name

Is intel-microcode installed ?

[grl]

Yes, but... some cleaning sometimes helps....

I agree - but its an awful lot of work. And tbh - I learnt the most about linux while searching for solutions to problems like that.

Code: Select all

lscpu |grep name
Model name:          Intel(R) Core(TM) i7-3820QM CPU @ 2.70GHz

An no, intel-microcode is not installed

Lukas

[L_V]

Don't know if intel-microcode can help. I don't really believe but who knows.
Cannot try it for you : you may.
And that's the most I can do !

[Head_on_a_Stick]

no, intel-microcode is not installed

Try installing it, I don't think 3rd generation processors had any specific problems but it's worth a go.

Check the systemd journal for any clues, ask the interweb for a guide.

Perhaps also try adding i915 to /etc/initramfs-tools/modules and then

Code: Select all

# update-initramfs -u -k all

Reboot to test.