Issue with suspend

Hi, I have just installed lubuntu on an older asus pc and everything worked smoothly. Thanks for the great job the team is doing here.

There is just one issue: power management

When I try to suspend to ram, the system shuts down … as far as I can see from logs without any issues.

The screen shuts of, but fans / system power stays on.

The only way to recover from this state is to press power button for 4 seconds

I know that this is not a HW issue, as suspend to ram worked on an older libreelec distri I was running on the system recently.

It would be great if someone could help me to debug this issue.

Best Regards
Heinzi

find system info and logs attached:

lsb_release -a

Distributor ID: Ubuntu
Description: Ubuntu 20.04.2 LTS
Release: 20.04
Codename: focal

lshw

homeoffice
description: Desktop Computer
product: S1-AT5NM10E (To Be Filled By O.E.M.)
vendor: ASUSTeK Computer INC
version: System Version
serial: System Serial Number
width: 64 bits
capabilities: smbios-2.6 dmi-2.6 smp vsyscall32
configuration: boot=normal chassis=desktop family=To Be Filled By O.E.M. sku=To Be Filled By O.E.M. uuid=0086001E-8C00-003F-B3E5-BCAEC5764D7A
*-core
description: Motherboard
product: S1-AT5NM10E
vendor: ASUSTeK Computer INC.
physical id: 0
version: Rev x.0x
serial: MT7012K23100448
slot: To Be Filled By O.E.M.
*-firmware
description: BIOS
vendor: American Megatrends Inc.
physical id: 0
version: 0401
date: 09/17/2010
size: 64KiB
capacity: 1MiB
capabilities: isa pci pnp apm upgrade shadowing escd cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer int10video acpi usb ls120boot zipboot biosbootspecification
*-cpu
description: CPU
product: Intel(R) Atom™ CPU D525 @ 1.80GHz
vendor: Intel Corp.
physical id: 4
bus info: cpu@0
version: Intel(R) Atom™ CPU D525 @ 1.80GHz
serial: To Be Filled By O.E.M.
slot: BGA 473
size: 1800MHz
capacity: 1800MHz
width: 64 bits
clock: 200MHz
capabilities: lm fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl tm2 ssse3 cx16 xtpr pdcm movbe lahf_lm dtherm
configuration: cores=2 enabledcores=2 threads=4
*-cache:0
description: L1 cache
physical id: 5
slot: L1-Cache
size: 48KiB
capacity: 48KiB
capabilities: internal write-back data
configuration: level=1
*-cache:1
description: L2 cache
physical id: 6
slot: L2-Cache
size: 1MiB
capacity: 1MiB
capabilities: internal write-back unified
configuration: level=2
*-memory
description: System Memory
physical id: 20
slot: System board or motherboard
size: 4GiB
*-bank:0
description: SODIMM DDR Synchronous 800 MHz (1,2 ns)
product: ModulePartNumber00
vendor: Manufacturer00
physical id: 0
serial: SerNum00
slot: DIMM0
size: 4GiB
width: 64 bits
clock: 800MHz (1.2ns)
*-bank:1
description: DIMM [empty]
product: ModulePartNumber01
vendor: Manufacturer01
physical id: 1
serial: SerNum01
slot: DIMM1
*-pci
description: Host bridge
product: Atom Processor D4xx/D5xx/N4xx/N5xx DMI Bridge
vendor: Intel Corporation
physical id: 100
bus info: pci@0000:00:00.0
version: 02
width: 32 bits
clock: 33MHz
*-multimedia
description: Audio device
product: NM10/ICH7 Family High Definition Audio Controller
vendor: Intel Corporation
physical id: 1b
bus info: pci@0000:00:1b.0
version: 02
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=snd_hda_intel latency=0
resources: irq:35 memory:f9ef8000-f9efbfff
*-pci:0
description: PCI bridge
product: NM10/ICH7 Family PCI Express Port 1
vendor: Intel Corporation
physical id: 1c
bus info: pci@0000:00:1c.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:24 ioport:e000(size=4096) memory:c0000000-c01fffff ioport:f8f00000(size=1048576)
*-network
description: Ethernet interface
product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:05:00.0
logical name: enp5s0
version: 06
serial: 00:e0:4c:68:00:ab
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=5.8.0-44-generic firmware=rtl_nic/rtl8168e-2.fw latency=0 link=no multicast=yes port=MII
resources: irq:16 ioport:e800(size=256) memory:f8fff000-f8ffffff memory:f8ff8000-f8ffbfff
*-pci:1
description: PCI bridge
product: NM10/ICH7 Family PCI Express Port 2
vendor: Intel Corporation
physical id: 1c.1
bus info: pci@0000:00:1c.1
version: 02
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:25 ioport:1000(size=4096) memory:fbf00000-fbffffff ioport:c0200000(size=2097152)
*-usb
description: USB controller
product: uPD720200 USB 3.0 Host Controller
vendor: NEC Corporation
physical id: 0
bus info: pci@0000:04:00.0
version: 03
width: 64 bits
clock: 33MHz
capabilities: pm msi msix pciexpress xhci bus_master cap_list
configuration: driver=xhci_hcd latency=0
resources: irq:17 memory:fbffa000-fbffbfff
*-usbhost:0
product: xHCI Host Controller
vendor: Linux 5.8.0-44-generic xhci-hcd
physical id: 0
bus info: usb@6
logical name: usb6
version: 5.08
capabilities: usb-2.00
configuration: driver=hub slots=2 speed=480Mbit/s
*-usbhost:1
product: xHCI Host Controller
vendor: Linux 5.8.0-44-generic xhci-hcd
physical id: 1
bus info: usb@7
logical name: usb7
version: 5.08
capabilities: usb-3.00
configuration: driver=hub slots=2 speed=5000Mbit/s
*-pci:2
description: PCI bridge
product: NM10/ICH7 Family PCI Express Port 3
vendor: Intel Corporation
physical id: 1c.2
bus info: pci@0000:00:1c.2
version: 02
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:26 ioport:d000(size=4096) memory:fa000000-fbefffff ioport:ce000000(size=301989888)
*-display
description: VGA compatible controller
product: GT218 [ION]
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@0000:03:00.0
version: a2
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
configuration: driver=nouveau latency=0
resources: irq:34 memory:fa000000-faffffff memory:d0000000-dfffffff memory:ce000000-cfffffff ioport:dc00(size=128) memory:c0000-dffff
*-multimedia
description: Audio device
product: High Definition Audio Controller
vendor: NVIDIA Corporation
physical id: 0.1
bus info: pci@0000:03:00.1
version: a1
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=snd_hda_intel latency=0
resources: irq:19 memory:fbefc000-fbefffff
*-pci:3
description: PCI bridge
product: NM10/ICH7 Family PCI Express Port 4
vendor: Intel Corporation
physical id: 1c.3
bus info: pci@0000:00:1c.3
version: 02
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:27 ioport:2000(size=4096) memory:f9f00000-f9ffffff ioport:c0400000(size=2097152)
*-network
description: Wireless interface
product: AR9285 Wireless Network Adapter (PCI-Express)
vendor: Qualcomm Atheros
physical id: 0
bus info: pci@0000:02:00.0
logical name: wls35
version: 01
serial: 48:5d:60:21:a0:8c
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ath9k driverversion=5.8.0-44-generic firmware=N/A ip=192.168.2.3 latency=0 link=yes multicast=yes wireless=IEEE 802.11
resources: irq:19 memory:f9ff0000-f9ffffff
*-usb:0
description: USB controller
product: NM10/ICH7 Family USB UHCI Controller #1
vendor: Intel Corporation
physical id: 1d
bus info: pci@0000:00:1d.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: uhci bus_master
configuration: driver=uhci_hcd latency=0
resources: irq:23 ioport:c480(size=32)
*-usbhost
product: UHCI Host Controller
vendor: Linux 5.8.0-44-generic uhci_hcd
physical id: 1
bus info: usb@2
logical name: usb2
version: 5.08
capabilities: usb-1.10
configuration: driver=hub slots=2 speed=12Mbit/s
*-usb:1
description: USB controller
product: NM10/ICH7 Family USB UHCI Controller #2
vendor: Intel Corporation
physical id: 1d.1
bus info: pci@0000:00:1d.1
version: 02
width: 32 bits
clock: 33MHz
capabilities: uhci bus_master
configuration: driver=uhci_hcd latency=0
resources: irq:19 ioport:c800(size=32)
*-usbhost
product: UHCI Host Controller
vendor: Linux 5.8.0-44-generic uhci_hcd
physical id: 1
bus info: usb@3
logical name: usb3
version: 5.08
capabilities: usb-1.10
configuration: driver=hub slots=2 speed=12Mbit/s
*-usb:2
description: USB controller
product: NM10/ICH7 Family USB UHCI Controller #3
vendor: Intel Corporation
physical id: 1d.2
bus info: pci@0000:00:1d.2
version: 02
width: 32 bits
clock: 33MHz
capabilities: uhci bus_master
configuration: driver=uhci_hcd latency=0
resources: irq:18 ioport:c880(size=32)
*-usbhost
product: UHCI Host Controller
vendor: Linux 5.8.0-44-generic uhci_hcd
physical id: 1
bus info: usb@4
logical name: usb4
version: 5.08
capabilities: usb-1.10
configuration: driver=hub slots=2 speed=12Mbit/s
*-usb:3
description: USB controller
product: NM10/ICH7 Family USB UHCI Controller #4
vendor: Intel Corporation
physical id: 1d.3
bus info: pci@0000:00:1d.3
version: 02
width: 32 bits
clock: 33MHz
capabilities: uhci bus_master
configuration: driver=uhci_hcd latency=0
resources: irq:16 ioport:cc00(size=32)
*-usbhost
product: UHCI Host Controller
vendor: Linux 5.8.0-44-generic uhci_hcd
physical id: 1
bus info: usb@5
logical name: usb5
version: 5.08
capabilities: usb-1.10
configuration: driver=hub slots=2 speed=12Mbit/s
*-usb
description: Bluetooth wireless interface
product: AR3011 Bluetooth
vendor: Qualcomm Atheros Communications
physical id: 2
bus info: usb@5:2
version: 0.01
capabilities: bluetooth usb-1.10
configuration: driver=btusb maxpower=100mA speed=12Mbit/s
*-usb:4
description: USB controller
product: NM10/ICH7 Family USB2 EHCI Controller
vendor: Intel Corporation
physical id: 1d.7
bus info: pci@0000:00:1d.7
version: 02
width: 32 bits
clock: 33MHz
capabilities: pm debug ehci bus_master cap_list
configuration: driver=ehci-pci latency=0
resources: irq:23 memory:f9effc00-f9efffff
*-usbhost
product: EHCI Host Controller
vendor: Linux 5.8.0-44-generic ehci_hcd
physical id: 1
bus info: usb@1
logical name: usb1
version: 5.08
capabilities: usb-2.00
configuration: driver=hub slots=8 speed=480Mbit/s
*-usb
description: USB hub
product: USB2.0 Hub
vendor: GenesysLogic
physical id: 1
bus info: usb@1:1
version: 92.26
capabilities: usb-2.10
configuration: driver=hub maxpower=100mA slots=4 speed=480Mbit/s
*-usb:0
description: Video
product: Aukey-PC-LM1E Camera
vendor: Aukey-PC-LM1E Camera
physical id: 2
bus info: usb@1:1.2
version: 10.0a
capabilities: usb-2.00
configuration: driver=snd-usb-audio maxpower=500mA speed=480Mbit/s
*-usb:1
description: USB hub
product: USB2.0 Hub
vendor: GenesysLogic
physical id: 4
bus info: usb@1:1.4
version: 92.26
capabilities: usb-2.10
configuration: driver=hub maxpower=100mA slots=4 speed=480Mbit/s
*-usb:0
description: Keyboard
product: USB keyboard
vendor: Cherry
physical id: 1
bus info: usb@1:1.4.1
version: 1.03
capabilities: usb-2.00
configuration: driver=usbhid maxpower=100mA speed=1Mbit/s
*-usb:1
description: Audio device
product: Jabra EVOLVE 30 II
vendor: GN Audio A/S
physical id: 2
bus info: usb@1:1.4.2
version: 2.07
serial: 0003102B0A5207
capabilities: usb-2.00 audio-control
configuration: driver=usbhid maxpower=100mA speed=12Mbit/s
*-usb:2
description: Mouse
product: USB Optical Mouse
vendor: PixArt
physical id: 3
bus info: usb@1:1.4.3
version: 1.00
capabilities: usb-2.00
configuration: driver=usbhid maxpower=100mA speed=1Mbit/s
*-pci:4
description: PCI bridge
product: 82801 Mobile PCI Bridge
vendor: Intel Corporation
physical id: 1e
bus info: pci@0000:00:1e.0
version: e2
width: 32 bits
clock: 33MHz
capabilities: pci subtractive_decode bus_master cap_list
*-isa
description: ISA bridge
product: NM10 Family LPC Controller
vendor: Intel Corporation
physical id: 1f
bus info: pci@0000:00:1f.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: isa bus_master cap_list
configuration: driver=lpc_ich latency=0
resources: irq:0
*-ide
description: IDE interface
product: NM10/ICH7 Family SATA Controller [IDE mode]
vendor: Intel Corporation
physical id: 1f.2
bus info: pci@0000:00:1f.2
version: 02
width: 32 bits
clock: 66MHz
capabilities: ide pm isa_compat_mode pci_native_mode bus_master cap_list
configuration: driver=ata_piix latency=0
resources: irq:19 ioport:1f0(size=8) ioport:3f6 ioport:170(size=8) ioport:376 ioport:ff90(size=16) memory:c0600000-c06003ff
*-serial
description: SMBus
product: NM10/ICH7 Family SMBus Controller
vendor: Intel Corporation
physical id: 1f.3
bus info: pci@0000:00:1f.3
version: 02
width: 32 bits
clock: 33MHz
configuration: driver=i801_smbus latency=0
resources: irq:19 ioport:400(size=32)
*-pnp00:00
product: PnP device PNP0c01
physical id: 1
capabilities: pnp
configuration: driver=system
*-pnp00:01
product: PnP device PNP0b00
physical id: 2
capabilities: pnp
configuration: driver=rtc_cmos
*-pnp00:02
product: PnP device PNP0c02
physical id: 3
capabilities: pnp
configuration: driver=system
*-pnp00:03
product: PnP device PNP0c02
physical id: 5
capabilities: pnp
configuration: driver=system
*-pnp00:04
product: PnP device PNP0c02
physical id: 6
capabilities: pnp
configuration: driver=system
*-pnp00:05
product: PnP device NTN0530
physical id: 7
capabilities: pnp
configuration: driver=nuvoton-cir
*-pnp00:06
product: PnP device PNP0c02
physical id: 8
capabilities: pnp
configuration: driver=system
*-pnp00:07
product: PnP device PNP0c01
physical id: 9
capabilities: pnp
configuration: driver=system
*-scsi:0
physical id: a
logical name: scsi0
capabilities: emulated
*-cdrom
description: DVD reader
product: DVD-ROM DTA0N
vendor: HL-DT-ST
physical id: 0.0.0
bus info: scsi@0:0.0.0
logical name: /dev/cdrom
logical name: /dev/dvd
logical name: /dev/sr0
version: D1B0
capabilities: removable audio dvd
configuration: ansiversion=5 status=nodisc
*-scsi:1
physical id: b
logical name: scsi1
capabilities: emulated
*-disk
description: ATA Disk
product: WDC WD5000AVDS-7
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@1:0.0.0
logical name: /dev/sda
version: 0A01
serial: WD-WCAV9S613636
size: 465GiB (500GB)
capabilities: gpt-1.00 partitioned partitioned:gpt
configuration: ansiversion=5 guid=84513235-95be-0a41-a3e0-010d428484be logicalsectorsize=512 sectorsize=512
*-volume:0
description: EXT4 volume
vendor: Linux
physical id: 1
bus info: scsi@1:0.0.0,1
logical name: /dev/sda1
logical name: /
version: 1.0
serial: 4d73e78c-2935-4f16-91d0-33972c580550
size: 97GiB
capabilities: journaled extended_attributes large_files huge_files dir_nlink 64bit extents ext4 ext2 initialized
configuration: created=2021-03-02 09:32:59 filesystem=ext4 lastmountpoint=/ modified=2021-03-02 18:22:17 mount.fstype=ext4 mount.options=rw,relatime mounted=2021-03-02 18:19:17 state=mounted
*-volume:1
description: Linux swap volume
vendor: Linux
physical id: 2
bus info: scsi@1:0.0.0,2
logical name: /dev/sda2
version: 1
serial: 6526383d-b94f-4b2b-8e56-3f6cf431ebbe
size: 15GiB
capacity: 15GiB
capabilities: nofs swap initialized
configuration: filesystem=swap pagesize=4095
*-volume:2
description: EXT4 volume
vendor: Linux
physical id: 3
bus info: scsi@1:0.0.0,3
logical name: /dev/sda3
version: 1.0
serial: 0e5fcbdc-f2f9-453b-8e55-1fea67e31ce2
size: 352GiB
capabilities: journaled extended_attributes large_files huge_files dir_nlink 64bit extents ext4 ext2 initialized
configuration: created=2021-03-02 09:33:17 filesystem=ext4 modified=2021-03-02 09:33:37 state=clean

lscpu

Architektur: x86_64
CPU Operationsmodus: 32-bit, 64-bit
Byte-Reihenfolge: Little Endian
Adressgrößen: 36 bits physical, 48 bits virtual
CPU(s): 4
Liste der Online-CPU(s): 0-3
Thread(s) pro Kern: 2
Kern(e) pro Socket: 2
Sockel: 1
NUMA-Knoten: 1
Anbieterkennung: GenuineIntel
Prozessorfamilie: 6
Modell: 28
Modellname: Intel(R) Atom™ CPU D525 @ 1.80GHz
Stepping: 10
CPU MHz: 1800.146
BogoMIPS: 3600.29
L1d Cache: 48 KiB
L1i Cache: 64 KiB
L2 Cache: 1 MiB
NUMA-Knoten0 CPU(s): 0-3
Vulnerability Itlb multihit: Not affected
Vulnerability L1tf: Not affected
Vulnerability Mds: Not affected
Vulnerability Meltdown: Not affected
Vulnerability Spec store bypass: Not affected
Vulnerability Spectre v1: Not affected
Vulnerability Spectre v2: Not affected
Vulnerability Srbds: Not affected
Vulnerability Tsx async abort: Not affected
Markierungen: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl tm2 ssse3 cx16 xtpr pdcm movbe lahf_lm dtherm

lspci

00:00.0 Host bridge: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx DMI Bridge (rev 02)
00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 4 (rev 02)
00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 (rev 02)
00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 (rev 02)
00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation NM10 Family LPC Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation NM10/ICH7 Family SATA Controller [IDE mode] (rev 02)
00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 02)
02:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
03:00.0 VGA compatible controller: NVIDIA Corporation GT218 [ION] (rev a2)
03:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1)
04:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)

lsusb

Bus 001 Device 008: ID 04f2:0939 Chicony Electronics Co., Ltd
Bus 001 Device 007: ID 0b0e:0312 GN Netcom
Bus 001 Device 006: ID 046a:b090 Cherry GmbH Keyboard
Bus 001 Device 005: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 004: ID 1bcf:0215 Sunplus Innovation Technology Inc.
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 003: ID 0cf3:3005 Qualcomm Atheros Communications AR3011 Bluetooth
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

1 Like

syslog:

1 Like

Adding information:

Issue also is visible when booting from live medium.

1 Like

Some more trial:

ubuntu 20.04 → after suspend it takes a long while but finally suspends … but after wakeup … system is crashed … corrupted display … unresponsive …
lubuntu 18:04 → same behavior as lubuntu 20.04
latest kodi live image → same issue

I’ve got a weird & old Nokia box that has issues with suspend, in my case it performs the same on multiple OSes so I concluded it’s a box issue; impacting all tested Linux & BSD kernels. The fans on this nokia remain on switching to low; but they’re supposed to as its intended to be used in a rack

You mention “Ubuntu 20.04” but didn’t give specifics as to which you were using… was it the GA (5.4) kernel?, HWE (5.8) kernel or other?

You also mention Lubuntu 18.04 & same behavior; if you’re comparing a 18.04 using HWE (5.4) kernel & Ubuntu 20.04 (GA 5.4) kernel the same behavior would be expected as it’s the same kernel stack, but you gave no specifics as to what stack you tried?

For example, 18.04 can use

  • 18.04 or 18.04.1 (4.15 kernel or GA kernel)
  • 18.04.2 (live; 4.18 kernel)
  • 18.04.3 (live, 5.0 kernel)
  • 18.04.4 (live, 5.3 kernel)
  • 18.04.5 (5.4 kernel; same as used in 20.04 GA)

Which is used by default is selected at install time (by the ISO you use to install, though that choice can be changed)

Given I think it’ll be close to kernel that matters for your issue, being specific as to kernel being compared matters in my opinion; and you didn’t provide that detail.

I’d also try suspending via command, for example

systemctl suspend

but I’d try variations & other methods too.

I’d compare different stacks (my list of 18.04 stacks show 5 choices available from live media alone), but if it was me, I’d probably go wider than those; the GA & HWE stacks for 18.04 for starters, me I like Debian so I’d likely test that too, but also another non-Debian/Ubuntu base too (eg. Fedora can be used in live mode, or without install as I recall) to look for clues.

Testing via live media means no changes are needed to your system, and it’s where I’d start (you gave no specifics on what you tried; GA or HWE stack on both focal or bionic?)

Maybe useful How can I suspend/hibernate from command line? - Ask Ubuntu but there are bound to be better; it’s just the first that appeared on a search.

@guiver Thanks for your elaborated answer. While trying different live images I just used just the latest live image form a specific release … so I probably used 5.4 kernel over and over again.

I tried systemctl suspend and pm-suspend method, both result in the same behavior.

I will check out more kernel versions according to your recommendation and post the results here.

1 Like

stupid question:

where would I find old releases ?

under this link

https://cdimage.ubuntu.com/lubuntu/releases/18.04.1/release

I only find the 18.04.5 image

https://cdimage.ubuntu.com/lubuntu/releases/18.04.1/release/lubuntu-18.04.5-desktop-amd64.iso

help apreciated.

Best Regards
Stephan

Yeah sorry, Index of /lubuntu/releases which will let you walk down to each 18.04 point release, but always ends up pointing at the latest (18.04.5 though the alternate ISO would provide the GA kernel as it’s not be re-created since 18.04; the alternate ISO isn’t live though so requires install).

To test the kernels, you could always opt to try the main Ubuntu releases (all those are available; Index of /releases/bionic). Main ubuntu will have the same base (and kernel stack), just the GNOME desktop (and apps) instead of Lubuntu’s LXDE (for bionic).

Late last year I needed 18.04.4 for a test (and I’d deleted or couldn’t find my old copy), so had to find it online, I used one of the European sites (like Downloads › Wiki › ubuntuusers.de but if it wasn’t deutsche/german, it was maybe français/french, but I forget sorry)

Hi tried,

  • 18.04.1 (4.15 kernel or GA kernel) → suspend/resume works good
  • 18.04.2 (live; 4.18 kernel) → suspend/resume works good
  • 18.04.3 (live, 5.0 kernel) → suspend/resume works good
  • 18.04.4 (live, 5.3 kernel) → suspend doesn’t work

So seems like the issue was introduced somewhere between 5.0 and 5.3

What is the best next step ?

  • Downgrade the whole os to 18.04.3 and freeze it there. That would mean, that support for the system would end in April 2023 … which is probably a reasonable timeframe for an old Atom box …

  • Downgrade the kernel in my 20.04 system … not sure whether this is such a great Idea, or feasable at all.

  • Figure out the rootcause in the kernel and fix it → probably beyond my capabilities and time :slight_smile:

  • report a bug somewhere and hope for someone to fix it → I’m not sure how and where to file this … and whether someon would care at all …

Best Regards
heinzi

1 Like

Hi,
quick update on that: I bravely downloaded a 5.0 kernel from here:

https://kernel.ubuntu.com/~kernel-ppa/mainline/

installed it using dpkg

and voila suspend works … but still, I think I am cut of from e.g. security updates in this way, right ?

So would be much nicer to know the rootcause and get rid of it on a recent kernel version.

Best Regards
heizi

1 Like

If using Lubuntu 18.04.5, I’d suggest using the GA kernel (4.15 or GA/general & 5.4/HWE are supported for the life of that product).

FYI: the 4.18 kernel was from 18.10; it bumped to 5.0 from 19.04, then 5.3 of 19.10 before finally settling on 5.4 of 20.04, being only short-term kernels for updates in Ubuntu releases. The HWE stack is taken from normal releases allowing later hardware to get newer drivers (when using the LTS release).

Of the 18.04 options, I’d stick with the GA kernel, rather than risk using an unsupported disco kernel which would require you to manually back-port patches (unless off-line, where security is a moot point). You can install with 18.04 or 18.04.1, or refer to Kernel/LTSEnablementStack - Ubuntu Wiki which provides both the command to install GA stack, and on completion of testing it, it then provides the command to remove the HWE stack. It’s found in the 20.04/focal section now. ie.

To downgrade from HWE/OEM to GA kernel:

sudo apt install --install-recommends linux-generic

OEM kernels didn’t exist in 18.04 on Ubuntu media… the removal step won’t have 20.04 in the name either; adjust for your release. And FYI: I’ve two old IBM thinkpad laptops that don’t like the 5.4 kernel, but are great on the 4.15/GA kernel.

However, Lubuntu 18.04 LTS is supported by Lubuntu only until April-2021, ie. 3 years only. The five years applies to the main Ubuntu base, which is the problem with 18.04.

The 4.15 kernel isn’t supported on 20.04, and whilst I’m aware of users using it (because of issues), I won’t recommend that. Me I’d likely explore another solution if you need suspend and want something later than bionic/18.04. My guess is you’ll have issues with anything using that kernel (ie. not just a Ubuntu base, but all GNU/Linux using that kernel; which is why I suggested trying non-Ubuntu’s which would confirm that…) In the end it’s your choice as I see it if you need suspend.

thanks für your answer … I’m a bit confused, no so I try to summarize in my words:

  • one option would be to use 18.04.5 using the GA kernel, this would make my system supported until 4.2021 … so this would’nt carry me far

  • the other option you point out is to move to a entirely different non ubuntu based base distri, like debian or fedora … and hope my issue vanishs and doesn’t catch me on the next upgrade.

    If I understand right, this is the solution you propose … which sounds a bit strange to me, because I would think, that the whole purpose of such a forum is rather to keep users with the distro, than send them away …

    On the other hand I can understand, that noone wants to spend big effort to recover support for some cheap little atom box … However I would have hoped to some pointer to what I could try to make my (not really exotic) box work on a recent revsion of lubuntu …

  • would’nt the lubuntu-meta package installed on on a 18.04.5 ubuntu server with GA kernel give me basically a lubuntu system with 5 years of LTS ?

If you load a 18.04 system, you can use ubuntu-support-status to view the support status of the packages on the actual system you are using. eg. on an old ibm thinkpad t43

guiverc@t43-lubu:~$   ubuntu-support-status 
Support status summary of 't43-lubu':

You have 422 packages (22.5%) supported until April 2021 (Community - 3y)
You have 1350 packages (72.1%) supported until April 2023 (Canonical - 5y)
You have 3 packages (0.2%) supported until April 2021 (Canonical - 3y)

You have 0 packages (0.0%) that can not/no-longer be downloaded
You have 97 packages (5.2%) that are unsupported

You’ll note many (72.1%) packages are supported for 5 years, ie. until April-2023. ubuntu-support-status reports 22.7% of packages are supported only until April-2021 (when Lubuntu, and support for much of the ‘universe’ repository ends; 5 years applies to ‘main’ packages only). Those are just facts. I haven’t decided what I’ll do with my system yet, as mine cannot upgrade to 20.04 :frowning: Most of what I do is off-line, so I’ll likely just deny it access to the internet by default.

My suggestion to try different OSes (specifically Debian & Fedora) was exploratory; to gain more information about the kernel stacks. I mentioned that I believe Fedora could be used in live mode for testing purposes without install for example. Fedora releases only have a supported life of about a year which I consider rather short (they come out every six months; when f34 comes out, 1 month later f32 will be EOL), but you won’t catch me saying anything negative about Debian (I do love my Debian too).

If the problem didn’t occur in Fedora or Debian for example, and you tried the same kernel versions… we know it’s something in the Ubuntu stack that’s an issue… Debian is pretty close to Ubuntu, Fedora a little further away - it was this exploratory purpose that I was talking about.

I talked about 18.04 & the variations only to to show why detail mattered (a test of 18.04 original media is a very different test to a test with 18.04.5 media…), plus to provide different stacks as I felt your issue was kernel related (educated guess at best)

Ubuntu Server, Ubuntu Desktop (ie. with GNOME on 18.04) have 5 years of support; Lubuntu/Xubuntu/Kubuntu/Ubuntu-MATE/Ubuntu-Budgie/etc only came with 3 years (Ubuntu-Studio 18.04 was not a LTS so only had 9 months). Adding anything Lubuntu to Ubuntu Server will mean the server parts have 5 years of support, but the desktop packages (LXDE/Lubuntu) end-support on 2021-April. ubuntu-support-status mentioned earlier will show that.

There maybe other options, I provided all I could think of, at least what I was willing to write about here. (I’d have explored further with other OSes to gain more information & confirm my theories that it’s kernel related, and not just something Ubuntu specific… why I mentioned what I consider off-topic Debian/Fedora… I wasn’t trying to plug either GNU/Linux, using them as example as they’re not Ubuntu based… ie. testing on Pop_OS! would gain you very little in my opinion; they do compile their own kernel but it’s very close; Linux Mint don’t even do that!).

I didn’t answer your earlier question about filing a bug, to get the best response. In my opinion, if you’d like to do that, you should file on the development release (which is hirsute currently, so 5.10 kernel), as the kernels you mentioned are no longer being developed, only getting security fixes (your issue doesn’t relate to security in my opinion). I can provide more detail here if you’re interested, but sorry I missed in my prior answer.

Thanks alot again for that elaborated answer.

While fiddeling around with different live images and distros … I figured out that:

if I switch lubuntu 20.04 to runlevel 3 doing

systemctl isolate multi-user.target

the system enters and leaves suspend without issues

obviosly this can only be a hint and not a reasonable base for a workaround … because the is no point in using suspend to ram if you have to logout from the desktop session before suspend and login after. …

2 Likes

probably the issue is actually more on the desktop environment or the display driver side rather than the kernel … but still kernel 5.0 works with the same desktop and display driver …

Drivers are strictly called kernel modules so are very related to the kernel itself. The difference between each of the 18.04 hardware enablement stacks I used as example includes kernel modules (ie. in user terminology ‘drivers’) but the kernel version is the easy way to list the stack.

This applies in other OSes too, they just don’t have a kernel that changes anywhere near as much as Linux does, and use a non-technical term ‘drivers’.

Thanks for the clarifications … I will probably file a bug against the current ubuntu dev release.

perhaps these guys will find out …

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