Page MenuHomeSolus

Laptop Frozen after Suspend
Open, Needs More InfoPublic

Description

Yesterday I installed Solus 4.1, and its up to date. Today I clicked on suspend and after a few minutes when I hit the power button the screen background comes on but no functionality on
the keyboard or mouse. The system is completely frozen, I can't even open terminals with Ctrl + Alt + F... . I have tried this twice and same results. I have to do a hard-reset to start system again. I'm using a Hp Elitebook 6930p with 4Gb Ram.

Event Timeline

ZVNexus added a subscriber: ZVNexus.Feb 8 2020, 3:19 PM

This is actually happening on my desktop as well. Weird, sleep used to work fine. When triggering suspend from systemctl resuming works fine, so IDK what's going on.

DataDrake triaged this task as Needs More Info priority.Feb 8 2020, 4:37 PM
DataDrake edited projects, added Hardware; removed Lacks Project.
DataDrake added a subscriber: DataDrake.

Can you see what's in the systemd journal right after you start the shutdown? That should be getting flushed to disk before your lock-up.

palto42 added a comment.EditedMay 1 2020, 6:39 PM

Since 26.04.2020 I have a similar issue that the laptop freezes after wakeup from suspend. After wake-up I get a black screen with a blinking cursor in the top left corner. I can only hard-power-off the pc and restart.

I'm using Solus Linux without issues since more than a year on this laptop and had no problems with sleep/suspend before.

Before 26. April the journalctls for suspend / wake-up looked like this:

Apr 25 16:03:08 solus_pc systemd-logind[604]: Suspend key pressed.
Apr 25 16:03:08 solus_pc NetworkManager[592]: <info>  [1587823388.7186] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Apr 25 16:03:08 solus_pc NetworkManager[592]: <info>  [1587823388.7188] device (enp4s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Apr 25 16:03:08 solus_pc kernel: sky2 0000:04:00.0 enp4s0: disabling interface
Apr 25 16:03:08 solus_pc NetworkManager[592]: <info>  [1587823388.7262] device (p2p-dev-wlp2s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Apr 25 16:03:08 solus_pc NetworkManager[592]: <info>  [1587823388.7279] manager: NetworkManager state is now ASLEEP
Apr 25 16:03:08 solus_pc systemd[1]: Reached target Sleep.
Apr 25 16:03:08 solus_pc systemd[1]: Starting Suspend...
Apr 25 16:03:08 solus_pc systemd-sleep[16122]: Failed to connect to non-global ctrl_ifname: (nil)  error: No such file or directory
Apr 25 16:03:08 solus_pc [16120]: /usr/lib64/systemd/system-sleep/wpa_supplicant.sh failed with exit status 255.
Apr 25 16:03:08 solus_pc systemd-sleep[16119]: Suspending system...
Apr 25 16:03:08 solus_pc kernel: PM: suspend entry (deep)
Apr 25 16:03:08 solus_pc kernel: Filesystems sync: 0.025 seconds
Apr 25 16:03:09 solus_pc kernel: rfkill: input handler enabled
Apr 25 16:28:38 solus_pc kernel: Freezing user space processes ... (elapsed 0.003 seconds) done.
Apr 25 16:28:38 solus_pc kernel: OOM killer disabled.
Apr 25 16:28:38 solus_pc kernel: Freezing remaining freezable tasks ... (elapsed 4.611 seconds) done.
Apr 25 16:28:38 solus_pc kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Apr 25 16:28:38 solus_pc kernel: wlp2s0: deauthenticating from e0:28:6d:54:bf:bc by local choice (Reason: 3=DEAUTH_LEAVING)
Apr 25 16:28:38 solus_pc kernel: sdhci-pci 0000:03:00.4: Will use DMA mode even though HW doesn't fully claim to support it.
Apr 25 16:28:38 solus_pc kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Apr 25 16:28:38 solus_pc kernel: sd 0:0:0:0: [sda] Stopping disk
Apr 25 16:28:38 solus_pc kernel: ACPI: EC: interrupt blocked
Apr 25 16:28:38 solus_pc kernel: ACPI: Preparing to enter system sleep state S3
Apr 25 16:28:38 solus_pc kernel: ACPI: EC: event blocked
Apr 25 16:28:38 solus_pc kernel: ACPI: EC: EC stopped
Apr 25 16:28:38 solus_pc kernel: PM: Saving platform NVS memory
Apr 25 16:28:38 solus_pc kernel: Disabling non-boot CPUs ...
Apr 25 16:28:38 solus_pc kernel: smpboot: CPU 1 is now offline
Apr 25 16:28:38 solus_pc kernel: smpboot: CPU 2 is now offline
Apr 25 16:28:38 solus_pc kernel: smpboot: CPU 3 is now offline
Apr 25 16:28:38 solus_pc kernel: ACPI: Low-level resume complete
Apr 25 16:28:38 solus_pc kernel: ACPI: EC: EC started
Apr 25 16:28:38 solus_pc kernel: PM: Restoring platform NVS memory
Apr 25 16:28:38 solus_pc kernel: Enabling non-boot CPUs ...
Apr 25 16:28:38 solus_pc kernel: x86: Booting SMP configuration:
Apr 25 16:28:38 solus_pc kernel: smpboot: Booting Node 0 Processor 1 APIC 0x4
Apr 25 16:28:38 solus_pc kernel: CPU1 is up
Apr 25 16:28:38 solus_pc kernel: smpboot: Booting Node 0 Processor 2 APIC 0x1
Apr 25 16:28:38 solus_pc kernel: CPU2 is up
Apr 25 16:28:38 solus_pc kernel: smpboot: Booting Node 0 Processor 3 APIC 0x5

Now the wakeup doesn't work and I have to hard-switch-off the laptop and reboot:

Apr 26 13:55:20 solus_pc systemd-logind[639]: Suspend key pressed.
Apr 26 13:55:20 solus_pc NetworkManager[624]: <info>  [1587902120.5360] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Apr 26 13:55:20 solus_pc kernel: sky2 0000:04:00.0 enp4s0: disabling interface
Apr 26 13:55:20 solus_pc NetworkManager[624]: <info>  [1587902120.5361] device (enp4s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Apr 26 13:55:20 solus_pc NetworkManager[624]: <info>  [1587902120.5405] device (p2p-dev-wlp2s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Apr 26 13:55:20 solus_pc NetworkManager[624]: <info>  [1587902120.5410] manager: NetworkManager state is now ASLEEP
Apr 26 13:55:20 solus_pc systemd[1]: Reached target Sleep.
Apr 26 13:55:20 solus_pc systemd[1]: Starting Suspend...
Apr 26 13:55:20 solus_pc systemd-sleep[2783]: Failed to connect to non-global ctrl_ifname: (nil)  error: No such file or directory
Apr 26 13:55:20 solus_pc [2781]: /usr/lib64/systemd/system-sleep/wpa_supplicant.sh failed with exit status 255.
Apr 26 13:55:20 solus_pc systemd-sleep[2780]: Suspending system...
Apr 26 13:55:20 solus_pc kernel: PM: suspend entry (deep)
Apr 26 13:55:20 solus_pc kernel: Filesystems sync: 0.052 seconds
Apr 26 13:55:21 solus_pc kernel: rfkill: input handler enabled
-- Reboot --
Apr 26 16:32:17 solus kernel: microcode: microcode updated early to revision 0x7, date = 2018-04-23

There is no difference in the log until the laptop suspends (last entry is the "rfkill") . After the unsuccessful wake-up there is nothing logged now, until I hard-reboot.

On 25th I upgrades some Solus packages, from eopkg history I can see that the Linux was upgraded from 5.5.11-151-1-x86_64 to 5.6.4-152-1-x86_64 , maybe this (or another package update) caused the problem.
Note that the laptop was first rebooted on 26.04. at 12:40, that's why the suspend still worked on 25th the whole day I guess.

All upgrades done on 25th:

Vorgang #204: Upgrade ausführen
Datum: 2020-04-25 12:01

    * python-tkinter wurde aktualisiert von 2.7.17-25-1-x86_64 auf 2.7.18-26-1-x86_64.
    * thunderbird wurde aktualisiert von 68.6.0-86-1-x86_64 auf 68.7.0-87-1-x86_64.
    * openvpn wurde aktualisiert von 2.4.7-11-1-x86_64 auf 2.4.9-12-1-x86_64.

Vorgang #203: Upgrade ausführen
Datum: 2020-04-25 11:59

    * libplacebo wurde aktualisiert von 1.29.1-3-1-x86_64 auf 2.43.0-4-1-x86_64.
    * mpv-libs wurde aktualisiert von 0.32.0-73-1-x86_64 auf 0.32.0-74-1-x86_64.
    * python-gphoto2 wurde aktualisiert von 2.1.0-8-1-x86_64 auf 2.2.2-9-1-x86_64.
    * bison wurde aktualisiert von 3.5.4-16-1-x86_64 auf 3.5.4-17-1-x86_64.
    * bison-devel wurde aktualisiert von 3.5.4-16-1-x86_64 auf 3.5.4-17-1-x86_64.
    * imagemagick wurde aktualisiert von 7.0.10.6-141-1-x86_64 auf 7.0.10_7-142-1-x86_64.
    * physfs wurde aktualisiert von 3.0.1-3-1-x86_64 auf 3.0.2-4-1-x86_64.
    * nvidia-390-glx-driver-modaliases wurde aktualisiert von 390.132-63-1-x86_64 auf 390.132-64-1-x86_64.
    * nodejs wurde aktualisiert von 12.15.0-80-1-x86_64 auf 12.16.2-81-1-x86_64.
    * xvidcore wurde aktualisiert von 1.3.5-2-1-x86_64 auf 1.3.7-3-1-x86_64.
    * nvidia-glx-driver-modaliases wurde aktualisiert von 440.82-339-1-x86_64 auf 440.82-340-1-x86_64.
    * btrfs-progs wurde aktualisiert von 5.4.1-25-1-x86_64 auf 5.6-26-1-x86_64.
    * vlc wurde aktualisiert von 3.0.9.2-102-1-x86_64 auf 3.0.9.2-103-1-x86_64.
    * linux-current wurde aktualisiert von 5.5.11-151-1-x86_64 auf 5.6.4-152-1-x86_64.
    * virtualbox-guest-common wurde aktualisiert von 6.1.6-151-1-x86_64 auf 6.1.6-152-1-x86_64.
    * linux-headers wurde aktualisiert von 5.5.11-68-1-x86_64 auf 5.6.4-69-1-x86_64.
    * udisks wurde aktualisiert von 2.8.4-19-1-x86_64 auf 2.8.4-20-1-x86_64.
    * physfs-devel wurde aktualisiert von 3.0.1-3-1-x86_64 auf 3.0.2-4-1-x86_64.
    * linux-current-headers wurde aktualisiert von 5.5.11-151-1-x86_64 auf 5.6.4-152-1-x86_64.
    * python-tenacity wurde aktualisiert von 6.0.0-3-1-x86_64 auf 6.1.0-4-1-x86_64.

Vorgang #202: Upgrade ausführen
Datum: 2020-04-25 11:58

    * virtualbox-guest-current 6.1.6-151-1-x86_64 wurde entfernt.
    * python wurde aktualisiert von 2.7.17-25-1-x86_64 auf 2.7.18-26-1-x86_64.
    * gettext wurde aktualisiert von 0.20.1-12-1-x86_64 auf 0.20.2-13-1-x86_64.
    * python-devel wurde aktualisiert von 2.7.17-25-1-x86_64 auf 2.7.18-26-1-x86_64.
    * gettext-devel wurde aktualisiert von 0.20.1-12-1-x86_64 auf 0.20.2-13-1-x86_64.
palto42 added a comment.EditedMay 2 2020, 8:00 AM

Today I booted with the old kernel 5.5.11-151-1-x86_64 via the grub extra options and tried the sleep mode, and this seems to work without freeze.

Need to try few more times to be 100% sure, but looks reasonable to me based on journalctl and eopkg history.

My laptop is a Sony Vaio with Intel i5-460M and ATI MobilityRadeon HD5650, the board has an Intel HM55 Express chipset.

Found other simlar issues with Linux 5.6.x kernels on Arch Linux https://bbs.archlinux.org/viewtopic.php?id=254475 and https://bbs.archlinux.org/viewtopic.php?id=254838

No solution but some indications that there is a relation to the amd graphics driver.

No change after updating linux-firmware from 20200316-47-1-x86_64 tody 20200421-48-1-x86_64.

Is there an option with eopkg to hold a package (kernel version) so that it is not removed by coming upgrade? I'm a bit afraid that the next kernel update will remove the working 5.5.11-151-1-x86_64 but the new kernel still doesn't fix my suspend freeze issue.

I'm still using the LTS kernel (currently 4.9.227-160.lts), the latest "current" kernel (5.6.18-155.current) still causes issues with wake-up from sleep.

The recent update of linux-current to version 5.6.19-158-1-x86_64 solved the problem (at least for my laptop) .
Suggest to close this ticket since there is was activity anyway.