Laptop reboots on wakeup on battery

Most likely after a recent update my Dell Latitude E5470 running Gnome started rebooting when trying to wake up from sleep, unless it is connected to power both on suspend and wakeup. If system is either suspended and/or resumed on battery it reboots as soon as the lid is opened or power button is pressed.

inxi
System:    Kernel: 4.19.113-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.19-x86_64 root=UUID=b8c4ef4a-0113-4c34-856c-ff60b967cbd8 rw quiet 
           udev.log_priority=3 
           Desktop: Gnome 3.36.0 wm: gnome-shell dm: GDM 3.34.1 Distro: Manjaro Linux 
Machine:   Type: Laptop System: Dell product: Latitude E5470 v: N/A serial: <filter> Chassis: type: 9 serial: <filter> 
           Mobo: Dell model: 0MT53G v: A00 serial: <filter> UEFI: Dell v: 1.21.6 date: 10/02/2019 
Battery:   ID-1: BAT0 charge: 45.6 Wh condition: 50.6/57.1 Wh (89%) volts: 8.3/7.6 model: Panasonic DELL 79VRK6B type: Li-poly 
           serial: <filter> status: Charging 
CPU:       Topology: Quad Core model: Intel Core i5-6300HQ bits: 64 type: MCP arch: Skylake-S family: 6 model-id: 5E (94) 
           stepping: 3 microcode: D6 L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 18432 
           Speed: 1143 MHz min/max: 800/3200 MHz Core speeds (MHz): 1: 1795 2: 1760 3: 1815 4: 1848 
           Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled 
           Type: mds mitigation: Clear CPU buffers; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: disabled, RSB filling 
           Type: tsx_async_abort mitigation: Clear CPU buffers; SMT disabled 
Graphics:  Device-1: Intel HD Graphics 530 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:191b 
           Display: x11 server: X.Org 1.20.8 driver: i915 compositor: gnome-shell resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 530 (Skylake GT2) v: 4.6 Mesa 19.3.5 compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Dell driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           chip ID: 8086:a170 
           Sound Server: ALSA v: k4.19.113-1-MANJARO 
Network:   Device-1: Intel Ethernet I219-LM vendor: Dell driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 
           chip ID: 8086:15b7 
           IF: enp0s31f6 state: down mac: <filter> 
           Device-2: Intel Wireless 8260 driver: iwlwifi v: kernel port: f040 bus ID: 01:00.0 chip ID: 8086:24f3 
           IF: wlp1s0 state: up mac: <filter> 
           IF-ID-1: docker0 state: down mac: <filter> 
Drives:    Local Storage: total: 238.47 GiB used: 112.47 GiB (47.2%) 
           ID-1: /dev/sda vendor: Intel model: SSDSCKGF256A5 SATA 256GB size: 238.47 GiB block size: physical: 512 B 
           logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: LB1i scheme: GPT 
Partition: ID-1: / raw size: 50.00 GiB size: 48.97 GiB (97.93%) used: 23.04 GiB (47.0%) fs: ext4 dev: /dev/sda2 
           ID-2: /home raw size: 187.99 GiB size: 184.03 GiB (97.90%) used: 89.44 GiB (48.6%) fs: ext4 dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 52.0 C mobo: N/A 
           Fan Speeds (RPM): cpu: 2410 
Info:      Processes: 196 Uptime: 9m Memory: 19.50 GiB used: 2.11 GiB (10.8%) Init: systemd v: 244 Compilers: gcc: 9.3.0 
           Shell: bash v: 5.0.16 running in: gnome-terminal inxi: 3.0.37 
Excerpt from journalctl with reboot (on battery)
Apr 02 23:15:56 ivashin-pc systemd-logind[659]: Suspend key pressed.
Apr 02 23:15:56 ivashin-pc gnome-shell[1403]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Apr 02 23:15:56 ivashin-pc gnome-shell[1403]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Apr 02 23:15:56 ivashin-pc gnome-shell[1403]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Apr 02 23:15:56 ivashin-pc gnome-shell[1403]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Apr 02 23:15:56 ivashin-pc gnome-shell[1403]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Apr 02 23:15:56 ivashin-pc gnome-shell[1403]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Apr 02 23:15:56 ivashin-pc gnome-shell[1403]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Apr 02 23:15:56 ivashin-pc gnome-shell[1403]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Apr 02 23:15:56 ivashin-pc gnome-shell[1403]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Apr 02 23:15:56 ivashin-pc NetworkManager[651]: <info>  [1585858556.2292] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Apr 02 23:15:56 ivashin-pc NetworkManager[651]: <info>  [1585858556.2293] device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-sta>
Apr 02 23:15:56 ivashin-pc NetworkManager[651]: <info>  [1585858556.2296] manager: NetworkManager state is now ASLEEP
Apr 02 23:15:56 ivashin-pc gnome-shell[1403]: Usage of indicator.indicators is deprecated for Indicator
Apr 02 23:15:56 ivashin-pc gnome-shell[1403]: Usage of indicator.indicators is deprecated for Indicator
Apr 02 23:15:56 ivashin-pc gnome-shell[1403]: JS WARNING: [resource:///org/gnome/shell/ui/popupMenu.js 776]: reference to undefined property "_delegate"
Apr 02 23:15:56 ivashin-pc gnome-shell[1403]: Usage of object.actor is deprecated for ButtonBox
Apr 02 23:15:56 ivashin-pc gnome-shell[1403]: Ignoring excess values in shadow definition
Apr 02 23:15:56 ivashin-pc gnome-shell[1403]: Ignoring excess values in shadow definition
Apr 02 23:15:59 ivashin-pc gnome-shell[1403]: ../glib/gobject/gsignal.c:2735: instance '0x560ae897a480' has no handler with id '14038'
Apr 02 23:16:00 ivashin-pc systemd[1]: Reached target Sleep.
Apr 02 23:16:00 ivashin-pc systemd[1]: Starting Suspend...
Apr 02 23:16:00 ivashin-pc systemd-sleep[1941]: Suspending system...
Apr 02 23:16:00 ivashin-pc kernel: PM: suspend entry (deep)
-- Reboot --
Apr 02 23:16:48 ivashin-pc kernel: microcode: microcode updated early to revision 0xd6, date = 2019-10-03
Apr 02 23:16:48 ivashin-pc kernel: Linux version 4.19.113-1-MANJARO (builder@69b2c4653405) (gcc version 9.3.0 (Arch Linux 9.3.0-1)) #1 SMP Wed Mar 25 12:30:45 UTC 2020
Excerpt from journalctl with normal wakeup (plugged in)
Apr 02 23:07:19 ivashin-pc systemd-logind[670]: Suspend key pressed.
Apr 02 23:07:19 ivashin-pc gnome-shell[1409]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Apr 02 23:07:19 ivashin-pc gnome-shell[1409]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Apr 02 23:07:19 ivashin-pc gnome-shell[1409]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Apr 02 23:07:19 ivashin-pc gnome-shell[1409]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Apr 02 23:07:19 ivashin-pc gnome-shell[1409]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Apr 02 23:07:19 ivashin-pc gnome-shell[1409]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Apr 02 23:07:19 ivashin-pc gnome-shell[1409]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Apr 02 23:07:19 ivashin-pc gnome-shell[1409]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Apr 02 23:07:19 ivashin-pc gnome-shell[1409]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Apr 02 23:07:19 ivashin-pc NetworkManager[661]: <info>  [1585858039.1723] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Apr 02 23:07:19 ivashin-pc NetworkManager[661]: <info>  [1585858039.1727] device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-sta>
Apr 02 23:07:19 ivashin-pc NetworkManager[661]: <info>  [1585858039.1731] manager: NetworkManager state is now ASLEEP
Apr 02 23:07:19 ivashin-pc gnome-shell[1409]: Usage of indicator.indicators is deprecated for Indicator
Apr 02 23:07:19 ivashin-pc gnome-shell[1409]: Usage of indicator.indicators is deprecated for Indicator
Apr 02 23:07:19 ivashin-pc gnome-shell[1409]: JS WARNING: [resource:///org/gnome/shell/ui/popupMenu.js 776]: reference to undefined property "_delegate"
Apr 02 23:07:19 ivashin-pc gnome-shell[1409]: Usage of object.actor is deprecated for ButtonBox
Apr 02 23:07:19 ivashin-pc gnome-shell[1409]: Ignoring excess values in shadow definition
Apr 02 23:07:19 ivashin-pc gnome-shell[1409]: Ignoring excess values in shadow definition
Apr 02 23:07:22 ivashin-pc systemd[1]: Reached target Sleep.
Apr 02 23:07:22 ivashin-pc systemd[1]: Starting Suspend...
Apr 02 23:07:23 ivashin-pc systemd-sleep[3964]: Suspending system...
Apr 02 23:07:23 ivashin-pc kernel: PM: suspend entry (deep)
Apr 02 23:07:33 ivashin-pc kernel: PM: Syncing filesystems ... done.
Apr 02 23:07:33 ivashin-pc kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.
Apr 02 23:07:33 ivashin-pc kernel: OOM killer disabled.
Apr 02 23:07:33 ivashin-pc kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Apr 02 23:07:33 ivashin-pc kernel: Suspending console(s) (use no_console_suspend to debug)
Apr 02 23:07:33 ivashin-pc kernel: wlp1s0: deauthenticating from 50:ff:20:19:f1:be by local choice (Reason: 3=DEAUTH_LEAVING)
Apr 02 23:07:33 ivashin-pc kernel: e1000e: EEE TX LPI TIMER: 00000011
Apr 02 23:07:33 ivashin-pc kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Apr 02 23:07:33 ivashin-pc kernel: sd 0:0:0:0: [sda] Stopping disk
Apr 02 23:07:33 ivashin-pc kernel: ACPI: EC: interrupt blocked
Apr 02 23:07:33 ivashin-pc kernel: ACPI: Preparing to enter system sleep state S3
Apr 02 23:07:33 ivashin-pc kernel: ACPI: EC: event blocked
Apr 02 23:07:33 ivashin-pc kernel: ACPI: EC: EC stopped
Apr 02 23:07:33 ivashin-pc kernel: PM: Saving platform NVS memory
Apr 02 23:07:33 ivashin-pc kernel: Disabling non-boot CPUs ...
Apr 02 23:07:33 ivashin-pc kernel: smpboot: CPU 1 is now offline
Apr 02 23:07:33 ivashin-pc kernel: smpboot: CPU 2 is now offline
Apr 02 23:07:33 ivashin-pc kernel: smpboot: CPU 3 is now offline
Apr 02 23:07:33 ivashin-pc kernel: ACPI: Low-level resume complete
Apr 02 23:07:33 ivashin-pc kernel: ACPI: EC: EC started
Apr 02 23:07:33 ivashin-pc kernel: PM: Restoring platform NVS memory
Apr 02 23:07:33 ivashin-pc kernel: Enabling non-boot CPUs ...
Apr 02 23:07:33 ivashin-pc kernel: x86: Booting SMP configuration:
Apr 02 23:07:33 ivashin-pc kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Apr 02 23:07:33 ivashin-pc kernel:  cache: parent cpu1 should not be sleeping
Apr 02 23:07:33 ivashin-pc kernel: CPU1 is up
Apr 02 23:07:33 ivashin-pc kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Apr 02 23:07:33 ivashin-pc kernel:  cache: parent cpu2 should not be sleeping
Apr 02 23:07:33 ivashin-pc kernel: CPU2 is up
Apr 02 23:07:33 ivashin-pc kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Apr 02 23:07:33 ivashin-pc kernel:  cache: parent cpu3 should not be sleeping
Apr 02 23:07:33 ivashin-pc kernel: CPU3 is up
Apr 02 23:07:33 ivashin-pc kernel: ACPI: Waking up from system sleep state S3
Apr 02 23:07:33 ivashin-pc kernel: ACPI: EC: interrupt unblocked
Apr 02 23:07:33 ivashin-pc kernel: ACPI: EC: event unblocked
Apr 02 23:07:33 ivashin-pc kernel: sd 0:0:0:0: [sda] Starting disk
Apr 02 23:07:33 ivashin-pc kernel: iwlwifi 0000:01:00.0: Applying debug destination EXTERNAL_DRAM
Apr 02 23:07:33 ivashin-pc kernel: iwlwifi 0000:01:00.0: Applying debug destination EXTERNAL_DRAM
Apr 02 23:07:33 ivashin-pc kernel: iwlwifi 0000:01:00.0: FW already configured (0) - re-configuring
Apr 02 23:07:33 ivashin-pc kernel: iwlwifi 0000:01:00.0: starting timestamp_marker trigger with delay: 1s
Apr 02 23:07:33 ivashin-pc kernel: usb 1-11: reset high-speed USB device number 4 using xhci_hcd
Apr 02 23:07:33 ivashin-pc kernel: ata3: SATA link down (SStatus 4 SControl 300)
Apr 02 23:07:33 ivashin-pc kernel: ata4: SATA link down (SStatus 0 SControl 300)
Apr 02 23:07:33 ivashin-pc kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Apr 02 23:07:33 ivashin-pc kernel: ata1.00: configured for UDMA/133
Apr 02 23:07:33 ivashin-pc kernel: ahci 0000:00:17.0: port does not support device sleep
Apr 02 23:07:33 ivashin-pc kernel: usb 1-6: reset full-speed USB device number 2 using xhci_hcd
Apr 02 23:07:33 ivashin-pc kernel: usb 1-10: reset full-speed USB device number 3 using xhci_hcd
Apr 02 23:07:33 ivashin-pc kernel: OOM killer enabled.
Apr 02 23:07:33 ivashin-pc kernel: Restarting tasks ... done.
Apr 02 23:07:33 ivashin-pc kernel: acpi PNP0401:00: Already enumerated
Apr 02 23:07:33 ivashin-pc bluetoothd[658]: Endpoint unregistered: sender=:1.200 path=/MediaEndpoint/A2DPSink/sbc
Apr 02 23:07:33 ivashin-pc bluetoothd[658]: Endpoint unregistered: sender=:1.200 path=/MediaEndpoint/A2DPSource/sbc
Apr 02 23:07:33 ivashin-pc wpa_supplicant[721]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=0 noise=9999 txrate=0
Apr 02 23:07:33 ivashin-pc wpa_supplicant[721]: wlp1s0: CTRL-EVENT-DISCONNECTED bssid=50:ff:20:19:f1:be reason=3 locally_generated=1
Apr 02 23:07:33 ivashin-pc wpa_supplicant[721]: wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=WORLD
Apr 02 23:07:33 ivashin-pc systemd[1]: Starting Load/Save RF Kill Switch Status...
Apr 02 23:07:33 ivashin-pc kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
Apr 02 23:07:33 ivashin-pc NetworkManager[661]: <warn>  [1585858053.5575] sup-iface[0x5637acc9f920,wlp1s0]: connection disconnected (reason -3)
Apr 02 23:07:33 ivashin-pc NetworkManager[661]: <info>  [1585858053.5582] device (wlp1s0): supplicant interface state: completed -> disconnected
Apr 02 23:07:33 ivashin-pc gnome-shell[1409]: An active wireless connection, in infrastructure mode, involves no access point?
Apr 02 23:07:33 ivashin-pc kernel: acpi PNP0501:00: Still not present
Apr 02 23:07:33 ivashin-pc kernel: Bluetooth: hci0: Device revision is 5
Apr 02 23:07:33 ivashin-pc kernel: Bluetooth: hci0: Secure boot is enabled
Apr 02 23:07:33 ivashin-pc kernel: Bluetooth: hci0: OTP lock is enabled
Apr 02 23:07:33 ivashin-pc kernel: Bluetooth: hci0: API lock is enabled
Apr 02 23:07:33 ivashin-pc kernel: Bluetooth: hci0: Debug lock is disabled
Apr 02 23:07:33 ivashin-pc kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Apr 02 23:07:33 ivashin-pc kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
Apr 02 23:07:33 ivashin-pc systemd[1]: Stopped target Bluetooth.
Apr 02 23:07:33 ivashin-pc systemd[1324]: Reached target Bluetooth.
Apr 02 23:07:33 ivashin-pc systemd[1]: Started Load/Save RF Kill Switch Status.
Apr 02 23:07:33 ivashin-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostnam>
Apr 02 23:07:33 ivashin-pc systemd[1]: Reached target Bluetooth.
Apr 02 23:07:33 ivashin-pc kernel: audit: type=1130 audit(1585858053.570:136): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/>
Apr 02 23:07:33 ivashin-pc systemd-sleep[3964]: System resumed.
Apr 02 23:07:33 ivashin-pc kernel: PM: suspend exit
Apr 02 23:07:33 ivashin-pc wpa_supplicant[721]: wlp1s0: Reject scan trigger since one is already pending
Apr 02 23:07:33 ivashin-pc wpa_supplicant[721]: wlp1s0: Failed to initiate AP scan
Apr 02 23:07:33 ivashin-pc systemd[1]: systemd-suspend.service: Succeeded.
Apr 02 23:07:33 ivashin-pc systemd[1]: Started Suspend.
Apr 02 23:07:33 ivashin-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostna>
Apr 02 23:07:33 ivashin-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostnam>
Apr 02 23:07:33 ivashin-pc kernel: audit: type=1130 audit(1585858053.980:137): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr>
Apr 02 23:07:33 ivashin-pc kernel: audit: type=1131 audit(1585858053.980:138): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr>
Apr 02 23:07:33 ivashin-pc systemd[1]: Stopped target Sleep.
Apr 02 23:07:33 ivashin-pc systemd[1]: Reached target Suspend.
Apr 02 23:07:33 ivashin-pc systemd[1]: Stopped target Suspend.
Apr 02 23:07:33 ivashin-pc systemd-logind[670]: Operation 'sleep' finished.

Some additional info:

$ cat /sys/power/mem_sleep
s2idle [deep]
journalctl -t systemd-sleep
Mar 19 13:55:46 ivashin-pc systemd-sleep[233334]: Suspending system...
Mar 19 14:43:50 ivashin-pc systemd-sleep[233334]: System resumed.
Mar 19 15:07:13 ivashin-pc systemd-sleep[238371]: Suspending system...
Mar 19 17:05:49 ivashin-pc systemd-sleep[238371]: System resumed.
Mar 19 19:36:00 ivashin-pc systemd-sleep[251802]: Suspending system...
Mar 20 09:51:56 ivashin-pc systemd-sleep[251802]: System resumed.
Mar 20 10:11:43 ivashin-pc systemd-sleep[253997]: Suspending system...
Mar 20 15:54:03 ivashin-pc systemd-sleep[253997]: System resumed.
Mar 20 21:04:43 ivashin-pc systemd-sleep[279796]: Suspending system...
Mar 20 21:47:38 ivashin-pc systemd-sleep[279796]: System resumed.
Mar 20 22:28:16 ivashin-pc systemd-sleep[282628]: Suspending system...
Mar 20 22:29:11 ivashin-pc systemd-sleep[282628]: System resumed.
Mar 20 23:52:37 ivashin-pc systemd-sleep[285748]: Suspending system...
Mar 21 13:10:01 ivashin-pc systemd-sleep[285748]: System resumed.
-- Reboot --
Mar 30 14:54:18 ivashin-pc systemd-sleep[98981]: Suspending system...
Mar 30 17:48:02 ivashin-pc systemd-sleep[98981]: System resumed.
Apr 01 18:21:03 ivashin-pc systemd-sleep[300796]: Suspending system...
Apr 01 20:16:17 ivashin-pc systemd-sleep[300796]: System resumed.
Apr 01 20:26:33 ivashin-pc systemd-sleep[302056]: Suspending system...
Apr 01 20:39:25 ivashin-pc systemd-sleep[302056]: System resumed.
Apr 02 00:07:14 ivashin-pc systemd-sleep[318509]: Suspending system...
Apr 02 00:34:01 ivashin-pc systemd-sleep[318509]: System resumed.
Apr 02 00:34:50 ivashin-pc systemd-sleep[319305]: Suspending system...
Apr 02 10:24:35 ivashin-pc systemd-sleep[319305]: System resumed.
-- Reboot --
Apr 02 19:43:15 ivashin-pc systemd-sleep[18122]: Suspending system...
-- Reboot --
Apr 02 22:34:05 ivashin-pc systemd-sleep[5953]: Suspending system...
-- Reboot --
Apr 02 22:35:51 ivashin-pc systemd-sleep[2155]: Suspending system...
Apr 02 22:36:06 ivashin-pc systemd-sleep[2155]: System resumed.
-- Reboot --
Apr 02 22:38:06 ivashin-pc systemd-sleep[1937]: Suspending system...
-- Reboot --
Apr 02 22:46:15 ivashin-pc systemd-sleep[4022]: Suspending system...
Apr 02 22:46:23 ivashin-pc systemd-sleep[4022]: System resumed.
-- Reboot --
Apr 02 23:07:23 ivashin-pc systemd-sleep[3964]: Suspending system...
Apr 02 23:07:33 ivashin-pc systemd-sleep[3964]: System resumed.
-- Reboot --
Apr 02 23:16:00 ivashin-pc systemd-sleep[1941]: Suspending system...

Stopping tlp does not change anything.

Found the description of the exact same issue description on Arch forum: https://bbs.archlinux.org/viewtopic.php?id=207543

But unfortunately the suggested workaround - simply fully shutting down system - didn't work for me.

Try this
https://bbs.archlinux.org/viewtopic.php?pid=1733042#p1733042
Also go trough this

And maybe a good idea to switch to a newer kernel.

1 Like

Thank you, @bogdancovaciu! I was unable to find this thread myself.

Hibernation trick (enabling hibernation and hibernating system) resolved the problem. Now laptop suspends and resumes both on AC and battery.

Looks like this is a bug somewhere in E5470's firmware. Most likely this was triggered when I tried to run Intel's SSD Firmware Update Tool, which did not work for me and crashed with a kernel panic. Probably in the meantime it messed up ACPI states somehow.

As for the kernel, I tried running 5.4 when it came out, but it broke Electron apps (Electron app and Java2D don't redraw), so I reverted back to 4.19, which works perfectly for me.

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by