Kernel 6.12 broke suspend mode

[anokasion]

Hello everyone, at this point I think it is pretty well known that the new kernel 6.12 update broke many distros' suspend mode, however, I think this has happened mostly on different laptop machines, in my case, it stopped working properly (not being able to wake up no matter what) on a desktop computer that runs MX Linux ahs.

This are my specs:

Code: Select all

Snapshot created on: 20240402_1236
System:
  Kernel: 6.12.6-1-liquorix-amd64 [6.12-7~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable amd_pstate=disable BOOT_IMAGE=/boot/vmlinuz-6.12.6-1-liquorix-amd64
    root=UUID=<filter> ro quiet splash init=/lib/systemd/systemd
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.4_ahs_x64 Libretto January 21  2024 base: Debian GNU/Linux
    12 (bookworm)
Machine:
  Type: Desktop System: Gigabyte product: B450M DS3H V2 v: -CF serial: <superuser required>
  Mobo: Gigabyte model: B450M DS3H V2 v: x.x serial: <superuser required> UEFI: American
    Megatrends LLC. v: F63 date: 08/03/2022
CPU:
  Info: model: AMD Ryzen 5 5600G with Radeon Graphics bits: 64 type: MT MCP arch: Zen 3 gen: 4
    level: v3 note: check built: 2021-22 process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80)
    stepping: 0 microcode: 0xA50000D
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache: L1: 384 KiB
    desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 1512 high: 1821 min/max: 1400/4464 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 1697 2: 1414 3: 1696 4: 1414 5: 1697 6: 1414
    7: 1400 8: 1400 9: 1821 10: 1400 11: 1400 12: 1400 bogomips: 93425
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Vulnerable: Safe RET, no microcode
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: always-on; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series] vendor: Gigabyte driver: amdgpu
    v: kernel arch: GCN-5 code: Vega process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s
    lanes: 16 link-max: gen: 4 speed: 16 GT/s ports: active: HDMI-A-1 empty: DVI-D-1
    bus-ID: 06:00.0 chip-ID: 1002:1638 class-ID: 0300 temp: 38.0 C
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: HDMI-A-1 mapped: HDMI-A-0 model: HDMI built: 2021 res: 1920x1080 hz: 60 dpi: 3048
    gamma: 1.2 size: 16x9mm (0.63x0.35") diag: 546mm (21.5") ratio: 16:9 modes: max: 1920x1080
    min: 720x400
  API: OpenGL v: 4.6 Mesa 24.2.2-1~mx23ahs renderer: AMD Radeon Graphics (radeonsi renoir LLVM
    15.0.6 DRM 3.59 6.12.6-1-liquorix-amd64) direct-render: Yes
Audio:
  Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 06:00.1 chip-ID: 1002:1637
    class-ID: 0403
  Device-2: AMD Family 17h/19h HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel pcie:
    gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 06:00.6 chip-ID: 1022:15e3
    class-ID: 0403
  API: ALSA v: k6.12.6-1-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte driver: r8169
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 04:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 238.48 GiB used: 178.17 GiB (74.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37240G size: 223.57 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 0010 scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: SanDisk model: Cruzer Blade size: 14.91 GiB
    block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: 223.32 GiB size: 218.75 GiB (97.96%) used: 178.17 GiB (81.4%) fs: ext4
    dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
    dev: /dev/sda1 maj-min: 8:1
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 43.2 C mobo: 36.0 C gpu: amdgpu temp: 38.0 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2774 pm: dpkg pkgs: 2760 libs: 1489 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 14
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https://brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/grapejuice.list
    1: deb [signed-by=/usr/share/keyrings/grapejuice-archive-keyring.gpg] https://brinkervii.gitlab.io/grapejuice/repositories/debian/ universal main
  Active apt repos in: /etc/apt/sources.list.d/makedeb.list
    1: deb [signed-by=/usr/share/keyrings/makedeb-archive-keyring.gpg arch=all] https://proget.makedeb.org makedeb main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb https://mirrors.ocf.berkeley.edu/mx-packages/mx/repo/ bookworm main non-free
    2: deb https://mirrors.ocf.berkeley.edu/mx-packages/mx/repo/ bookworm ahs
  Active apt repos in: /etc/apt/sources.list.d/vscodium.list
    1: deb [ signed-by=/usr/share/keyrings/vscodium-archive-keyring.gpg ] https://download.vscodium.com/debs vscodium main
  Active apt repos in: /etc/apt/sources.list.d/winehq-bookworm.sources
    1: deb [arch=amd64 i386] https://dl.winehq.org/wine-builds/debian bookworm main
Info:
  Processes: 329 Uptime: 50m wakeups: 0 Memory: 15 GiB used: 2.46 GiB (16.4%) Init: systemd v: 252
  target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

I remember having doubts about running MX Linux ahs when it came out, but the few problems I had during the year (which were only two non critical ones), I posted them to this forum and got solid answers and even the solution after some days, so after the latest big kernel 6.12 update, I thought posting the issue here would be the best bet.

The issue it's pretty straightforward, from XFCE, going to Log Out > Sleep mode (while power manager has sleep mode set as sleep, instead of hibernate, as I have always had) *seems* to put the system on suspend mode, it is strange that the RGB lights on the panel of the PC chassis doesn't turn off, which always the same Sleep mode used to turn off, using the same BIOS settings as usual. But, regardless, the most important problem is that putting the system to sleep is no different than shutting down the machine improperly.

Thanks in advance.

[siamhie]

1. Does this happen with the 6.11.x kernel?


2. fastfetch is alerting you to your disc space usage.

Code: Select all

ID-1: / raw-size: 223.32 GiB size: 218.75 GiB (97.96%) used: 178.17 GiB (81.4%)

[anokasion]

1. Checked again just in case, no problems at all with 6.11, suspend works perfectly

2. Recently one of my SSD died so until I can replace it, I'm living with my small one

[siamhie]

Open a terminal and try this (since you are booting systemd)

Code: Select all

systemctl suspend

[anokasion]

Updated, running 6.12.7-2-liquorix-amd64, it seems this problem has been completely solved, Thanks again.

Update: with the latest kernel, the same mentioned in this post, suspend mode via XFCE (from the Application menu) seems to be faulty in a random way; sometimes it suspends properly, other times I have to hardware reboot the system because it won't wake up pressing any key.
However, using systemctl suspend as you suggested, it seems to works ok, I tried 6 times in a row, and it worked perfectly. Does XFCE's suspend calls some other command? I am familiar with Linux overall, just not with suspend/hibernation mode, I don't even know which log files to check aside dmesg.
As you noticed, my main SSD was almost full, this is because in the night when I upgraded from 6.11.x to 6.12.x, my second "big" SSD died (even the BIOS do not see it), could all these problems be related somehow? how can I know fstrim it's working well? sorry for all the questions, but this woke me up to a matter that can be of concern.