• Bug#1106668: The PC freezes on waking up from sleep too often (1/2)

    From =?UTF-8?Q?Peter_M=C3=BCller?=@1:229/2 to All on Tue May 27 17:20:01 2025
    XPost: linux.debian.bugs.dist
    From: [email protected]

    Package: linux-image-6.1.0-37-amd64
    Version: 6.1.140-1
    Control: affects -1 + linux

    For a few weeks now (perhaps after every second or third sleep), awakening from sleep fails too often. More precisely, when I hit the Shift key or click a mouse button when the PC is asleep, it starts waking up (the LED indicating power switches from
    flashing between on and off every second to being continuously on), but the screen remains black. The keyboard remains unresponsive to hitting the LED keys (NumLock, CapsLock, ScrollLock). Hitting the key sequence Alt+(SysRq, R, E, I, S, U, B) has no
    visible effect. Pushing the reboot button has no visible effect. (On another freeze, pinging the PC has no effect; I don't try it out each time.) Observationally, the PC has frozen. Only pressing the power button for 6–10 seconds has a visible effect:
    the computer goes off. After the last such freeze, we find this in the journal:


    Mai 27 06:06:27 AnonymPC dhclient[825]: DHCPDISCOVER on enp7s0 to 255.255.255.255 port 67 interval 10
    Mai 27 06:06:37 AnonymPC dhclient[825]: No DHCPOFFERS received.
    Mai 27 06:06:37 AnonymPC dhclient[825]: No working leases in persistent database - sleeping.
    Mai 27 06:06:37 AnonymPC root[2313259]: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1
    Mai 27 06:09:01 AnonymPC CRON[2315382]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
    Mai 27 06:09:01 AnonymPC CRON[2315383]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
    Mai 27 06:09:01 AnonymPC CRON[2315382]: pam_unix(cron:session): session closed for user root
    Mai 27 06:09:01 AnonymPC systemd[1]: Starting phpsessionclean.service - Clean php session files...
    Mai 27 06:09:01 AnonymPC systemd[1]: phpsessionclean.service: Deactivated successfully.
    Mai 27 06:09:01 AnonymPC systemd[1]: Finished phpsessionclean.service - Clean php session files.
    Mai 27 06:10:14 AnonymPC kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
    Mai 27 06:10:14 AnonymPC kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
    Mai 27 06:10:14 AnonymPC systemd-logind[915]: The system will suspend now!
    Mai 27 06:10:14 AnonymPC NetworkManager[923]: <info> [1748319014.6872] manager: sleep: sleep requested (sleeping: no enabled: yes)
    Mai 27 06:10:14 AnonymPC NetworkManager[923]: <info> [1748319014.6875] device (p2p-dev-wlp179s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
    Mai 27 06:10:14 AnonymPC ModemManager[954]: <info> [sleep-monitor-systemd] system is about to suspend
    Mai 27 06:10:14 AnonymPC NetworkManager[923]: <info> [1748319014.6883] device (wlp179s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
    Mai 27 06:10:14 AnonymPC dbus-daemon[900]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=923 comm="/usr/sbin/NetworkManager --no-daemon")
    Mai 27 06:10:14 AnonymPC systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
    Mai 27 06:10:14 AnonymPC dbus-daemon[900]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
    Mai 27 06:10:14 AnonymPC systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
    Mai 27 06:10:14 AnonymPC kernel: wlp179s0: deauthenticating from d4:21:22:6a:9e:bd by local choice (Reason: 3=DEAUTH_LEAVING)
    Mai 27 06:10:14 AnonymPC wpa_supplicant[925]: wlp179s0: CTRL-EVENT-DISCONNECTED bssid=d4:21:22:6a:9e:bd reason=3 locally_generated=1
    Mai 27 06:10:14 AnonymPC wpa_supplicant[925]: wlp179s0: CTRL-EVENT-DSCP-POLICY clear_all
    Mai 27 06:10:14 AnonymPC NetworkManager[923]: <info> [1748319014.8480] device (wlp179s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
    Mai 27 06:10:14 AnonymPC avahi-daemon[898]: Withdrawing address record for 2003:fd:f08:ae7a:f55d:e51f:862b:bece on wlp179s0.
    Mai 27 06:10:14 AnonymPC avahi-daemon[898]: Leaving mDNS multicast group on interface wlp179s0.IPv6 with address 2003:fd:f08:ae7a:f55d:e51f:862b:bece.
    Mai 27 06:10:14 AnonymPC avahi-daemon[898]: Joining mDNS multicast group on interface wlp179s0.IPv6 with address fe80::34bc:bf13:5e2b:69c0.
    Mai 27 06:10:14 AnonymPC avahi-daemon[898]: Registering new address record for fe80::34bc:bf13:5e2b:69c0 on wlp179s0.*.
    Mai 27 06:10:14 AnonymPC avahi-daemon[898]: Withdrawing address record for fe80::34bc:bf13:5e2b:69c0 on wlp179s0.
    Mai 27 06:10:14 AnonymPC avahi-daemon[898]: Leaving mDNS multicast group on interface wlp179s0.IPv6 with address fe80::34bc:bf13:5e2b:69c0.
    Mai 27 06:10:14 AnonymPC avahi-daemon[898]: Interface wlp179s0.IPv6 no longer relevant for mDNS.
    Mai 27 06:10:14 AnonymPC dbus-daemon[900]: [system] Activating via systemd: service name='org.freedesktop.fwupd' unit='fwupd.service' requested by ':1.128' (uid=1000 pid=2999 comm="/usr/bin/gnome-software --gapplication-service")
    Mai 27 06:10:14 AnonymPC dbus-daemon[900]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.128' (uid=1000 pid=2999 comm="/usr/bin/gnome-software --gapplication-service")
    Mai 27 06:10:14 AnonymPC NetworkManager[923]: <info> [1748319014.8670] dhcp4 (wlp179s0): canceled DHCP transaction
    Mai 27 06:10:14 AnonymPC NetworkManager[923]: <info> [1748319014.8670] dhcp4 (wlp179s0): activation: beginning transaction (timeout in 45 seconds)
    Mai 27 06:10:14 AnonymPC NetworkManager[923]: <info> [1748319014.8671] dhcp4 (wlp179s0): state changed no lease
    Mai 27 06:10:14 AnonymPC NetworkManager[923]: <info> [1748319014.8675] dhcp6 (wlp179s0): canceled DHCP transaction

    [continued in next message]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From =?UTF-8?Q?Peter_M=C3=BCller?=@1:229/2 to All on Wed May 28 18:30:01 2025
    XPost: linux.debian.bugs.dist
    From: [email protected]

    retitle 1106668 Waking up from suspend to RAM reproducibly leads to a hard freeze

    severity 1106668 important

    thanks



    More info:

    - Upon waking up, the hard drive succeeds to spin up; the typical sound of its mechanics is heard.

    - Hitting none of the LED keys (Num Lock, Caps Lock, Scroll Lock) works: all the LED lights remain off.

    - Pinging the PC doesn't work: “Destination unreachable: Address unreachable”.

    - Upon restarting (pressing the power button long until power off, waiting a bit, and then pressing and releasing it):

    * The BIOS/UEFI startup routines print, “The system has POSTed in safe mode. This may be due to the previous POST attempt failing because of system instability, or if the power button was held in to force the system off. If the system failed to POST
    after you made changes to UEFI settings, you may wish to revert to stable settings to prevent POST failure. Press F1 to Run SETUP”. The startup routines show no failure otherwise.

    * The message speaking about filesystem check shows up long sometimes.

    * Manually choosing to sleep from the menu of the GDM login screen and then trying to wake up by hitting a key also leads to freeze. This is reproducible now. So an influence typical user programs (such as Firefox or its plugins) can be ruled out.

    * On the same PC, Windows 11 reproducibly succeeds to manually fall asleep into energy saving (suspend to RAM) and then to wake up when we hit [Esc] or [Shift]. So a software issue somewhere inside Linux (kernel, drivers, modules, …) seems more
    likely than a hardware one.

    I've raised severity because of reproducibility and because I do need the PC to be able to suspend to RAM every night so that I can resume work the next day.


    Here is a log from another sleep, followed by a wakeup with freeze, then pressing and holding a power button for a several seconds, then hitting and releasing the power button:


    May 28 17:28:40 AnonymPC /usr/libexec/gdm-x-session[1505]: (II) systemd-logind: got resume for 13:68
    May 28 17:28:40 AnonymPC /usr/libexec/gdm-x-session[1505]: (II) event4 - Logitech Optical USB Mouse: is tagged by udev as: Mouse
    May 28 17:28:40 AnonymPC /usr/libexec/gdm-x-session[1505]: (II) event4 - Logitech Optical USB Mouse: device set to 400 DPI
    May 28 17:28:40 AnonymPC /usr/libexec/gdm-x-session[1505]: (II) event4 - Logitech Optical USB Mouse: device is a pointer
    May 28 17:28:40 AnonymPC wireplumber[1062]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner
    May 28 17:28:40 AnonymPC pipewire[1060]: spa.v4l2: '/dev/video0' VIDIOC_ENUM_FRAMESIZES: Unpassender IOCTL (I/O-Control) für das Gerät
    May 28 17:28:40 AnonymPC pipewire[1060]: spa.v4l2: '/dev/video0' VIDIOC_ENUM_FRAMESIZES: Unpassender IOCTL (I/O-Control) für das Gerät
    May 28 17:28:40 AnonymPC dbus-daemon[1066]: [session uid=119 pid=1066] Activating via systemd: service name='org.freedesktop.impl.portal.PermissionStore' unit='xdg-permission-store.service' requested by ':1.10' (uid=119 pid=1062 comm="/usr/bin/
    wireplumber")
    May 28 17:28:40 AnonymPC gsd-media-keys[2096]: Unable to get default sink
    May 28 17:28:40 AnonymPC systemd[1038]: Starting xdg-permission-store.service - sandboxed app permission store...
    May 28 17:28:40 AnonymPC dbus-daemon[1066]: [session uid=119 pid=1066] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore'
    May 28 17:28:40 AnonymPC systemd[1038]: Started xdg-permission-store.service - sandboxed app permission store.
    May 28 17:28:40 AnonymPC wireplumber[1062]: <WpPortalPermissionStorePlugin:0x556a839f1630> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
    May 28 17:28:41 AnonymPC kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
    May 28 17:28:44 AnonymPC kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
    May 28 17:28:44 AnonymPC systemd-logind[910]: The system will suspend now!
    May 28 17:28:44 AnonymPC kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
    May 28 17:28:44 AnonymPC NetworkManager[927]: <info> [1748446124.3072] manager: sleep: sleep requested (sleeping: no enabled: yes)
    May 28 17:28:44 AnonymPC NetworkManager[927]: <info> [1748446124.3074] device (p2p-dev-wlp179s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
    May 28 17:28:44 AnonymPC ModemManager[942]: <info> [sleep-monitor-systemd] system is about to suspend
    May 28 17:28:44 AnonymPC NetworkManager[927]: <info> [1748446124.3076] device (wlp179s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
    May 28 17:28:44 AnonymPC gnome-shell[1582]: Screen lock is locked down, not locking
    May 28 17:28:44 AnonymPC dbus-daemon[895]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.11' (uid=0 pid=927 comm="/usr/sbin/NetworkManager --no-daemon")
    May 28 17:28:44 AnonymPC systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
    May 28 17:28:44 AnonymPC dbus-daemon[895]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
    May 28 17:28:44 AnonymPC systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
    May 28 17:28:44 AnonymPC kernel: wlp179s0: deauthenticating from d4:21:22:6a:9e:bd by local choice (Reason: 3=DEAUTH_LEAVING)
    May 28 17:28:44 AnonymPC dhclient[815]: DHCPDISCOVER on enp6s0 to 255.255.255.255 port 67 interval 10
    May 28 17:28:44 AnonymPC sh[815]: DHCPDISCOVER on enp6s0 to 255.255.255.255 port 67 interval 10
    May 28 17:28:44 AnonymPC wpa_supplicant[934]: wlp179s0: CTRL-EVENT-DISCONNECTED bssid=d4:21:22:6a:9e:bd reason=3 locally_generated=1
    May 28 17:28:44 AnonymPC wpa_supplicant[934]: wlp179s0: CTRL-EVENT-DSCP-POLICY clear_all

    [continued in next message]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Uwe =?utf-8?Q?Kleine-K=C3=B6nig?=@1:229/2 to All on Wed Jun 11 18:30:01 2025
    XPost: linux.debian.bugs.dist
    From: [email protected]

    Control: tag -1 + moreinfo

    Hello Peter,

    On Tue, May 27, 2025 at 05:17:32PM +0200, Peter Müller wrote:
    For a few weeks now (perhaps after every second or third sleep),
    awakening from sleep fails too often. More precisely, when I hit the
    Shift key or click a mouse button when the PC is asleep, it starts
    waking up (the LED indicating power switches from flashing between on
    and off every second to being continuously on), but the screen remains
    black. The keyboard remains unresponsive to hitting the LED keys
    (NumLock, CapsLock, ScrollLock). Hitting the key sequence Alt+(SysRq,
    R, E, I, S, U, B) has no visible effect. Pushing the reboot button
    has no visible effect. (On another freeze, pinging the PC has no
    effect; I don't try it out each time.) Observationally, the PC has
    frozen. Only pressing the power button for 6–10 seconds has a visible effect: the computer goes off. After the last such freeze, we find
    this in the journal:
    [...]

    That might be a BIOS issue. I guess there is no BIOS update available
    for your machine?

    If the problems still occur on the newest BIOS, the debugging you need
    to do is described on

    https://docs.kernel.org/power/basic-pm-debugging.html

    Depending on your findings we might get an idea how to fix your issue.
    So please report back your test results.

    Best regards
    Uwe

    -----BEGIN PGP SIGNATURE-----

    iQEzBAABCgAdFiEEP4GsaTp6HlmJrf7Tj4D7WH0S/k4FAmhJrM0ACgkQj4D7WH0S /k7g0Af+N7oOGR1xuOMz3OSxMJVHEPUwLVN7CAGVLNm59GxMNRU3EkjeLIpU9zTn dXRj9xu1zgYmLVjuzZLHKhLbIkHPNAjSeJk/P5QQ22Q4PsfmZHVmql1GyW0ArSTR tlYuHRn29P8no1C4YGGlUhoNovdkQdBYTJZCiTZztdYV+g81k+ffhfBC9vPEgdzc GPkMelybij+gSknatPZm4Fo2CjjgmUyeuDamqq+K0QmjeYG5JDgbOt2MBOBtnIN9 wcwL+7Z0AAkOzUXNxuuVoQH5GHeWL1tSEDI6dGpADZvsUKW/BqQPaX4ZAXBf4KdU I3FPAt2BtCpsnJBpGyvJVJ8MdV4NQg==
    =6rcq
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Peter Mueller@1:229/2 to All on Thu Jun 19 00:10:01 2025
    XPost: linux.debian.bugs.dist
    From: [email protected]

    Dear Uwe, The BIOS is fully up to date (version 4701 from https://www.asus.com/de/motherboards-components/motherboards/workstation/ws-c422-pro-se/helpdesk_bios?model2Name=WS-C422-PRO-SE) https://www.asus.com/de/motherboards-components/motherboards/
    workstation/ws-c422-pro-se/helpdesk_bios?model2Name=WS-C422-PRO-SE). I'll proceed with testing as you suggested and report here when done. Cheers, Peter

    --==bound.0.016746a898ffa0e0ff4a9c2caae9cf2a.mail.rambler.ru=Content-Transfer-Encoding: quoted-printable
    Content-Type: text/html; charset=utf-8

    <div>Dear Uwe,<br><br>The BIOS is fully up to date (version 4701 from <a href="https://www.asus.com/de/motherboards-components/motherboards/workstation/ws-c422-pro-se/helpdesk_bios?model2Name=WS-C422-PRO-SE)">https://www.asus.com/de/motherboards-
    components/motherboards/workstation/ws-c422-pro-se/helpdesk_bios?model2Name=WS-C422-PRO-SE)</a>. I'll proceed with testing as you suggested and report here when done.<br><br>Cheers,<br><br>Peter</div>

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)