[GeneralJo]

Hi all - just installed the latest version of Linux Lite onto my older Acer Aspire Z5761 All-In-One PC. I'm not new to Linux (my daily driver laptop runs Linux Mint, my 'tinkering' laptop runs MX Linux and my HTPC runs Linux Mint as well) but this is my first time installing Linux Lite. I'm a tech. guy and do computer help and repairs as a side business, but I wouldn't call myself a 'Linux Guru'...fairly advanced user, maybe, but I'm not one of you folks that can do everything through Terminal!

Basically....the install went fine and everything works perfectly EXCEPT Sleep/Suspend. System specs:

Code:

System:   Kernel: 5.15.0-60-generic x86_64 bits: 64 compiler: N/A   parameters: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic   root=UUID=82a44c8d-3646-49b2-b8e0-eb7844a44320 ro quiet splash   vt.handoff=7   Desktop: Xfce 4.16.0 tk: Gtk 3.24.23 info: xfce4-panel wm: xfwm4   dm: LightDM 1.30.0 Distro: Linux Lite 6.2 LTS   base: Ubuntu 22.04.2 LTS (Jammy Jellyfish) Machine:   Type: Desktop Mobo: Acer model: Aspire Z5761 serial: <filter>   UEFI: American Megatrends v: P01-A1 date: 12/06/2010 CPU:   Topology: Quad Core model: Intel Core i5-2400S bits: 64 type: MCP   arch: Sandy Bridge family: 6 model-id: 2A (42) stepping: 7 microcode: 2F   L2 cache: 6144 KiB   flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 19954   Speed: 2832 MHz min/max: 1600/3300 MHz Core speeds (MHz): 1: 1596 2: 1596   3: 1596 4: 1596   Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported   Type: l1tf mitigation: PTE Inversion   Type: mds mitigation: Clear CPU buffers; SMT disabled   Type: meltdown mitigation: PTI   Type: mmio_stale_data status: Unknown: No mitigations   Type: retbleed status: Not affected   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: Retpolines, IBPB: conditional, IBRS_FW,   STIBP: disabled, RSB filling, PBRSB-eIBRS: Not affected   Type: srbds status: Not affected   Type: tsx_async_abort status: Not affected Graphics:   Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics   vendor: Acer Incorporated ALI driver: i915 v: kernel bus ID: 00:02.0   chip ID: 8086:0102   Display: x11 server: X.Org 1.21.1.3 driver: modesetting   unloaded: fbdev,vesa resolution: 1920x1080~60Hz   OpenGL: renderer: Mesa Intel HD Graphics 2000 (SNB GT1) v: 3.3 Mesa 22.2.5   direct render: Yes Audio:   Device-1: Intel 6 Series/C200 Series Family High Definition Audio   vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel   bus ID: 00:1b.0 chip ID: 8086:1c20   Device-2: Chicony CNFA213 type: USB driver: snd-usb-audio,uvcvideo   bus ID: 1-1.5:4 chip ID: 04f2:b1f3 serial: <filter>   Sound Server: ALSA v: k5.15.0-60-generic Network:   Device-1: Intel 82579LM Gigabit Network vendor: Acer Incorporated ALI   driver: N/A port: f080 bus ID: 00:19.0 chip ID: 8086:1502   Device-2: Realtek RTL8191SU 802.11n WLAN Adapter type: USB driver: r8712u   bus ID: 2-1.8:4 chip ID: 0bda:8172 serial: <filter>   IF: wlx68a3c408d9c4 state: up mac: <filter> Drives:   Local Storage: total: 465.76 GiB used: 16.32 GiB (3.5%)   SMART Message: Required tool smartctl not installed. Check --recommends   ID-1: /dev/sda vendor: Seagate model: ST3500413AS size: 465.76 GiB   block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s   rotation: 7200 rpm serial: <filter> rev: JC66 scheme: GPT Partition:   ID-1: / raw size: 465.26 GiB size: 457.77 GiB (98.39%)   used: 16.31 GiB (3.6%) fs: ext4 dev: /dev/sda2 Sensors:   System Temperatures: cpu: 32.0 C mobo: N/A   Fan Speeds (RPM): N/A Repos:   Active apt repos in: /etc/apt/sources.list   1: deb http://ca.archive.ubuntu.com/ubuntu/ jammy main restricted   2: deb http://ca.archive.ubuntu.com/ubuntu/ jammy-updates main restricted   3: deb http://ca.archive.ubuntu.com/ubuntu/ jammy universe   4: deb http://ca.archive.ubuntu.com/ubuntu/ jammy-updates universe   5: deb http://ca.archive.ubuntu.com/ubuntu/ jammy multiverse   6: deb http://ca.archive.ubuntu.com/ubuntu/ jammy-updates multiverse   7: deb http://ca.archive.ubuntu.com/ubuntu/ jammy-backports main restricted universe multiverse   8: deb http://archive.canonical.com/ubuntu jammy partner   9: deb http://ca.archive.ubuntu.com/ubuntu/ jammy-security main restricted   10: deb http://ca.archive.ubuntu.com/ubuntu/ jammy-security universe   11: deb http://ca.archive.ubuntu.com/ubuntu/ jammy-security multiverse   Active apt repos in: /etc/apt/sources.list.d/google-chrome.list   1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main   Active apt repos in: /etc/apt/sources.list.d/linuxlite.list   1: deb http://repo.linuxliteos.com/linuxlite/ fluorite main   Active apt repos in: /etc/apt/sources.list.d/skype-stable.list   1: deb [arch=amd64] https://repo.skype.com/deb stable main   Active apt repos in: /etc/apt/sources.list.d/spotify.list   1: deb http://repository.spotify.com stable non-free   Active apt repos in: /etc/apt/sources.list.d/teejee2008-ubuntu-foss-jammy.list   1: deb https://ppa.launchpadcontent.net/teejee2008/foss/ubuntu/ jammy main   Active apt repos in: /etc/apt/sources.list.d/teejee2008-ubuntu-ppa-jammy.list   1: deb https://ppa.launchpadcontent.net/teejee2008/ppa/ubuntu/ jammy main Info:   Processes: 235 Uptime: 30m Memory: 5.65 GiB used: 1.38 GiB (24.4%)   Init: systemd v: 249 runlevel: 5 Compilers: gcc: 11.3.0 alt: 11/12/9   Shell: bash v: 5.1.16 running in: xfce4-terminal inxi: 3.0.38

When I put the machine to sleep, all is well - when I try to wake it up, all also SEEMS to go fine EXCEPT that within about 5-10 seconds of waking to the desktop, the entire system freezes and I have to do a hard restart...

I've reinstalled LL twice now to make sure it's not a corruption issue...still does the freezing thing both times. I don't THINK it's the WiFi reconnecting because I've tried forgetting the network so the WiFi wasn't trying to connect on Wake but the freeze still happens...unless it's some sort of WiFi driver issue...?

Anybody have any ideas what would be going, where I could look to figure it out, or how I could go about get it working correctly?

Thanks!

[stevef]

within about 5-10 seconds of waking to the desktop, the entire system freezes

I know there's not a big time window to check, but does the computer appear to work ok during the 5-10 seconds ?

After the 10 seconds, what's the state of the freeze ?
Is it total or do things like the mouse pointer or Caps Lock key still respond  ?
Does the clock in the corner show the right time or is it stuck at a interesting time (e.g. sleep, wake or freeze)?
Does pressing Ctrl Alt F2 together do anything ?

Next time you do a sleep/wake/reboot cycle, make a careful note of the sleep time and the freeze time.

After the reboot open a terminal and run a command like this

Code:

journalctl --since "2023-02-21 11:30" --until "2023-02-21 11:40"

Replacing the date and times with your sleep and freeze values - add a bit of margin but don't include the reboot.

This will page through the system logs.  There will be a lot of stuff but you may pick up something.

[GeneralJo]

within about 5-10 seconds of waking to the desktop, the entire system freezes

I know there's not a big time window to check, but does the computer appear to work ok during the 5-10 seconds ?
During those 5-10 seconds after it wakes from Suspend, yes, it does seem to work fine! Cursor moves, I can open menus, etc...

After the 10 seconds, what's the state of the freeze ?
Is it total or do things like the mouse pointer or Caps Lock key still respond  ?
Does the clock in the corner show the right time or is it stuck at a interesting time (e.g. sleep, wake or freeze)?
Does pressing Ctrl Alt F2 together do anything ?
It seems to be a complete freeze...haven't tried Ctrl Alt F2, but I've tried Ctrl-ALt-Backspace and it didn't do anything...capslock doesn't work, clock seems to freeze, mouse cursor freezes.

Next time you do a sleep/wake/reboot cycle, make a careful note of the sleep time and the freeze time.

After the reboot open a terminal and run a command like this

Code:

journalctl --since "2023-02-21 11:30" --until "2023-02-21 11:40"

Replacing the date and times with your sleep and freeze values - add a bit of margin but don't include the reboot.

This will page through the system logs.  There will be a lot of stuff but you may pick up something.

As for the log - I'll take a look the next time I have time - hopefully this weekend!