Haswell Fujitsu Laptop has Trouble Waking Up from Suspend


I have replaced my KDE Neon installation with openSUSE Tumbleweed KDE a few days ago. However, my laptop is having trouble waking up from suspend, the system wakes up to a black screen, completely unresponsive, so to avoid data corruption, I have to REISUB.

I am unable to debug this is issue, as the previous boot’s kernel log (journalct -b -1) abruptly ends without any indication regarding waking from suspend.
In fact, after attempting to wake up the system, even keyboard status LEDs are unresponsive.

System specs:

  **Host:** localhost.localdomain **Kernel:** 5.19.2-1-default **arch:** x86_64 **bits:** 64 
    **Desktop:** KDE Plasma **v:** 5.25.4 **Distro:** openSUSE Tumbleweed 20220824 
  **Type:** Laptop **System:** FUJITSU **product:** LIFEBOOK E754 **v:** 10601115935 
    **serial:** <superuser required> 
  **Mobo:** FUJITSU **model:** FJNB26F **v:** N3 **serial:** <superuser required> 
    **UEFI:** FUJITSU // Phoenix **v:** Version 1.32 **date:** 09/06/2017 
  **ID-1:** CMB1 **charge:** 20.8 Wh (49.1%) **condition:** 42.4/62.2 Wh (68.2%) 
    **volts:** 11.3 **min:** 11.1 
  **Info:** quad core **model:** Intel Core i7-4702MQ **bits:** 64 **type:** MT MCP **cache:** 
    **L2:** 1024 KiB 
  **Speed (MHz):** **avg:** 800 **min/max:** 800/3200 **cores:** **1:** 798 **2:** 798 **3:** 798 
    **4:** 798 **5:** 798 **6:** 798 **7:** 798 **8:** 819 
  **Device-1:** Intel 4th Gen Core Processor Integrated Graphics **driver:** i915 
    **v:** kernel 
  **Display:** wayland **server:** X.org **v:** **with:** Xwayland **v:** 22.1.3 
    **compositor:** kwin_wayland **driver:** **X:** **loaded:** modesetting 
    **unloaded:** fbdev,vesa **gpu:** i915 **resolution:** 1366x768 
  **OpenGL:** **renderer:** Mesa Intel HD Graphics 4600 (HSW GT2) **v:** 4.6 Mesa 
  **Device-1:** Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
    **driver:** snd_hda_intel 
  **Device-2:** Intel 8 Series/C220 Series High Definition Audio 
    **driver:** snd_hda_intel 
  **Sound Server-1:** ALSA **v:** k5.19.2-1-default **running:** yes 
  **Sound Server-2:** PipeWire **v:** 0.3.56 **running:** yes 
  **Device-1:** Intel Ethernet I217-LM **driver:** e1000e 
  **IF:** enp0s25 **state:** down **mac:** ----------------
  **Device-2:** Intel Wireless 7260 **driver:** iwlwifi 
  **IF:** wlp2s0 **state:** up **mac:** -------------------
  **IF-ID-1:** virbr0 **state:** down **mac:** ------------
  **Device-1:** Intel Bluetooth wireless interface **type:** USB **driver:** btusb 
  **Report:** rfkill **ID:** hci0 **rfk-id:** 1 **state:** down **bt-service:** enabled,running 
    **rfk-block:** **hardware:** no **software:** yes **address:** see --recommends 
  **Local Storage:** **total:** 465.77 GiB **used:** 214.14 GiB (46.0%) 
  **ID-1:** /dev/sda **vendor:** Western Digital **model:** WDS250G2B0A 
    **size:** 232.89 GiB 
  **ID-2:** /dev/sdb **vendor:** HP **model:** SSD S700 250GB **size:** 232.89 GiB 
  **ID-1:** / **size:** 230.38 GiB **used:** 102.71 GiB (44.6%) **fs:** btrfs **dev:** /dev/dm-0 
  **ID-2:** /home **size:** 230.38 GiB **used:** 102.71 GiB (44.6%) **fs:** btrfs 
    **dev:** /dev/dm-0 
  **ID-3:** /opt **size:** 230.38 GiB **used:** 102.71 GiB (44.6%) **fs:** btrfs 
    **dev:** /dev/dm-0 
  **ID-4:** /var **size:** 230.38 GiB **used:** 102.71 GiB (44.6%) **fs:** btrfs 
    **dev:** /dev/dm-0 
  **ID-1:** swap-1 **type:** zram **size:** 7.75 GiB **used:** 0 KiB (0.0%) **dev:** /dev/zram0 
  **ID-2:** swap-2 **type:** zram **size:** 7.75 GiB **used:** 0 KiB (0.0%) **dev:** /dev/zram1 
  **System Temperatures:** **cpu:** 49.0 C **mobo:** N/A 
  **Fan Speeds (RPM):** N/A 
  **Processes:** 323 **Uptime:** 0h 21m **Memory:** 15.51 GiB **used:** 4.14 GiB (26.7%) 
  **Shell:** Zsh **inxi:** 3.3.20

Thank you,
Kind regards.

It does not appear that I am able to edit the initial post and I have forgotten to mention that this does not happen everytime, from what I have noticed, putting laptop to sleep by closing the lid may be the main culprit.

Do you have something with which to try to remote login when it happens, and maybe catch dmesg and/or journal?

Yes, after your suggestion, I enabled ssh and attempted to connect from my phone. Unfortunately, the system really appears to be completely frozen after waking up. SSH’ing to my laptop works well otherwise.

Also, please disregard my previous message, these freezes occur regardless of suspend method (closing the lid or KDE menu button).

It seems to be a kernel related issue, as a workaround it works fine after downgrading my kernel to 5.14.21 from https://repos.opensuse.org/distribution/leap/15.4/repo/oss/x86_64/ and adding a lock.

In this case you need to open bug report on https://bugzilla.opensuse.org, same user/password as here.

Thank you, created a new ticket regarding this issue: 1202825 – Haswell Laptop Completely Freezes After Waking up from Suspend