Bug#1010949: Wake up from Suspend makes computer unusable

[Joshua Brickel]

Package: systemd

Version: 247.3-7

Severity: critical

Justification: breaks the whole system

This is happening on Debian 11 Stable version, most up to date software. This

only started a week or two ago.

How to repeat the bug.

Boot computer.

Send computer into suspend mode.

Wait for the computer to be in suspend mode

Touch a letter on the keyboard.

What happens:

When waking up from suspend mode only one monitor goes active (of two in my

case), and the keyboard and mouse no longer respond. The system is thus

unusable, any information not saved before suspend is lost as the only way to

bring down the computer at that point is to shut it off from the physical power

button.

I have tried this from both gnome and KDE, same issue. So I'm pretty sure it

is within the Systemd subsystem.

-- Package-specific info:

-- System Information:

Debian Release: 11.3

APT prefers stable-security

APT policy: (500, 'stable-security'), (500, 'stable')

Architecture: amd64 (x86_64)

Foreign Architectures: i386

Kernel: Linux 5.10.0-14-amd64 (SMP w/48 CPU threads)

Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set

Shell: /bin/sh linked to /usr/bin/dash

Init: systemd (via /run/systemd/system)

LSM: AppArmor: enabled

Versions of packages systemd depends on:

ii adduser 3.118

ii libacl1 2.2.53-10

ii libapparmor1 2.13.6-10

ii libaudit1 1:3.0-2

ii libblkid1 2.36.1-8+deb11u1

ii libc6 2.31-13+deb11u3

ii libcap2 1:2.44-1

ii libcrypt1 1:4.4.18-4

ii libcryptsetup12 2:2.3.7-1+deb11u1

ii libgcrypt20 1.8.7-6

ii libgnutls30 3.7.1-5

ii libgpg-error0 1.38-2

ii libip4tc2 1.8.7-1

ii libkmod2 28-1

ii liblz4-1 1.9.3-2

ii liblzma5 5.2.5-2.1~deb11u1

ii libmount1 2.36.1-8+deb11u1

ii libpam0g 1.4.0-9+deb11u1

ii libseccomp2 2.5.1-1+deb11u1

ii libselinux1 3.1-3

ii libsystemd0 247.3-7

ii libzstd1 1.4.8+dfsg-2.1

ii mount 2.36.1-8+deb11u1

ii util-linux 2.36.1-8+deb11u1

Versions of packages systemd recommends:

ii dbus 1.12.20-2

ii systemd-timesyncd [time-daemon] 247.3-7

Versions of packages systemd suggests:

ii policykit-1 0.105-31+deb11u1

pn systemd-container <none>

Versions of packages systemd is related to:

pn dracut <none>

ii initramfs-tools 0.140

ii libnss-systemd 247.3-7

ii libpam-systemd 247.3-7

ii udev 247.3-7

-- Configuration Files:

/etc/systemd/logind.conf changed:

[Login]

IdleAction=suspend

IdleActionSec=10min

-- no debconf information

[Michael Biebl]

control: tags -1 + moreinfo

Am 13.05.22 um 22:37 schrieb Joshua Brickel:

> I have tried this from both gnome and KDE, same issue. So I'm pretty sure it
>
> is within the Systemd subsystem.

How so? If anything, this sounds like a kernel problem.
Why do you say it's a systemd issue?

[Joshua Brickel]

I only figured it was systemd because systemd, from what I know is responsible for initiating suspend, and I figured waking up from it afterwards.  But I'm not discounting the possibility it is a kernel issue.  If there is any testing you want me to do (logs and that sort of thing) to determine what is causing this, I will be happy to try and oblige.  And if you truly think this is a kernel issue, and have the authority to reassign the bug to the kernel team, then by all means please do so.  My only interest is trying to get this issue solved.

Also I'm not sure why I didn't get your reply to my posting.  So sorry for the late follow-up.

[Michael Biebl]

Am 17.05.22 um 11:02 schrieb Michael Biebl:
> Am 17.05.22 um 00:22 schrieb Joshua Brickel:

>>
>> I only figured it was systemd because systemd, from what I know is
>> responsible for initiating suspend, and I figured waking up from it
>> afterwards.
>

> While systemd triggers the suspend (which is basically) writing the
> string "mem" to /sys/power/state, the actual suspend and subsequent
> hibernate is handled by the kernel.

s/hibernate/resume/

[Michael Biebl]

Am 17.05.22 um 00:22 schrieb Joshua Brickel:
>

> I only figured it was systemd because systemd, from what I know is
> responsible for initiating suspend, and I figured waking up from it
> afterwards.

[Joshua Brickel]

Okay, you got me convinced. So I guess I should try the one kernel below.

Is there a howto page on how to do this and make sure grub knows about it too?

On Tue, 17 May 2022 11:03:28 +0200 Michael Biebl <bi...@debian.org> wrote:

> Am 17.05.22 um 11:02 schrieb Michael Biebl:

> s/hibernate/resume/

>

[Michael Biebl]

Am 19.05.22 um 03:49 schrieb Joshua Brickel:

> Okay, you got me convinced. So I guess I should try the one kernel below.
>
> Is there a howto page on how to do this and make sure grub knows about
> it too?
>

grub is not involved in resume from suspend.