[Hardware] Can't wake up from sleep in KDE

New to Debian (Or Linux in general)? Ask your questions here!
Post Reply
Message
Author
User avatar
supersu
Posts: 17
Joined: 2017-09-10 10:54
Has thanked: 5 times

[Hardware] Can't wake up from sleep in KDE

#1 Post by supersu »

Hi folks.

I installed Debian 12 with KDE to laptop and it works fine except one thing. Sometimes, (sometimes, but not always) when I try to put my laptop to sleeping mode, it goes to strange buggy mode. All peripheral devices are off, screen is off, but laptop's cooler is working. And it's impossible to wake up that laptop by pressing keys on a keyboard or mouse/touchpad keys. And I don't have another chance to wake it up and I have to hold power button during 5 seconds to turn it off completely.

HP Laptop 15-bs0xx

Any ideas how can I debug that issue?

Code: Select all

lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 12 (bookworm)
Release:        12
Codename:       bookworm



uname -a
Linux PC451 6.1.0-26-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.112-1 (2024-09-30) x86_64 GNU/Linux



lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 02)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 02)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point LPC Controller/eSPI Controller (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
02:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] (rev 10)


User avatar
FreewheelinFrank
Global Moderator
Global Moderator
Posts: 2409
Joined: 2010-06-07 16:59
Has thanked: 45 times
Been thanked: 265 times

Re: [Hardware] Can't wake up from sleep in KDE

#2 Post by FreewheelinFrank »

Can we have some hardware information? Please post the output of this command:

Code: Select all

$ inxi -Faz
(You may need to install package inxi first.)

User avatar
supersu
Posts: 17
Joined: 2017-09-10 10:54
Has thanked: 5 times

Re: [Hardware] Can't wake up from sleep in KDE

#3 Post by supersu »

FreewheelinFrank wrote: 2024-10-13 22:11 Can we have some hardware information?
Sure, here we go

Code: Select all

inxi -Faz
System:
  Kernel: 6.1.0-26-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/vmlinuz-6.1.0-26-amd64
    root=UUID=9879395f-0bb6-4b93-a7cb-940785ef70a4 ro
    initrd=/install/gtk/initrd.gz quiet
  Desktop: KDE Plasma v: 5.27.5 wm: kwin_wayland dm: SDDM Distro: Debian
    GNU/Linux 12 (bookworm)
Machine:
  Type: Laptop System: HP product: HP Laptop 15-bs0xx v: Type1ProductConfigId
    serial: <filter> Chassis: type: 10 serial: <filter>
  Mobo: HP model: 832A v: 23.77 serial: <filter> UEFI-[Legacy]: Insyde
    v: F.70 date: 08/10/2022
Battery:
  ID-1: BAT1 charge: 22.5 Wh (100.0%) condition: 22.5/31.1 Wh (72.4%)
    volts: 11.8 min: 10.9 model: Hewlett-Packard PABAS0241231 type: Li-ion
    serial: <filter> status: full
CPU:
  Info: model: Intel Core i7-7500U socket: BGA1356 (U3E1) note: check bits: 64
    type: MT MCP arch: Amber/Kaby Lake note: check gen: core 7 level: v3
    note: check built: 2017 process: Intel 14nm family: 6 model-id: 0x8E (142)
    stepping: 9 microcode: 0xF6
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
    L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
    L3: 4 MiB desc: 1x4 MiB
  Speed (MHz): avg: 700 min/max: 400/3500 base/boost: 2600/8300 scaling:
    driver: intel_pstate governor: powersave volts: 0.9 V ext-clock: 100 MHz
    cores: 1: 700 2: 700 3: 700 4: 700 bogomips: 23199
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  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: IBRS; IBPB: conditional; STIBP: conditional;
    RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel HD Graphics 620 vendor: Hewlett-Packard driver: i915
    v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports:
    active: eDP-1 empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:5916
    class-ID: 0300
  Device-2: Sunplus Innovation HP TrueVision HD Camera type: USB
    driver: uvcvideo bus-ID: 1-5:5 chip-ID: 1bcf:2c9b class-ID: 0e02
  Display: server: X.Org v: 1.22.1.9 with: Xwayland v: 22.1.9
    compositor: kwin_wayland driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: iris gpu: i915 display-ID: :1 screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99")
    s-diag: 414mm (16.31")
  Monitor-1: eDP-1 mapped: XWAYLAND0 model: ChiMei InnoLux 0x15cc
    built: 2015 res: 1366x768 hz: 60 dpi: 102 gamma: 1.2
    size: 340x190mm (13.39x7.48") diag: 394mm (15.5") ratio: 16:9
    modes: 1366x768
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 620 (KBL
    GT2) direct-render: Yes
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_skl
    bus-ID: 00:1f.3 chip-ID: 8086:9d71 class-ID: 0403
  API: ALSA v: k6.1.0-26-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 status: n/a (root, process) 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: Hewlett-Packard RTL8111/8168/8211/8411 driver: r8169 v: kernel pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 01:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0
    chip-ID: 8086:24fb class-ID: 0280
  IF: wlo1 state: down mac: <filter>
  IF-ID-1: br-9f924fa38665 state: up speed: 10000 Mbps duplex: unknown
    mac: <filter>
  IF-ID-2: br-fae848932e29 state: up speed: 10000 Mbps duplex: unknown
    mac: <filter>
  IF-ID-3: docker0 state: down mac: <filter>
  IF-ID-4: veth85afd87 state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  IF-ID-5: vetha57b0c0 state: up speed: 10000 Mbps duplex: full
    mac: <filter>
Bluetooth:
  Device-1: Intel Wireless-AC 3168 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 1-4:3 chip-ID: 8087:0aa7 class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 0 state: down
    bt-service: enabled,running rfk-block: hardware: no software: yes
    address: <filter>
  Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff
    link-mode: peripheral accept
Drives:
  Local Storage: total: 4.78 TiB used: 2.52 TiB (52.8%)
  ID-1: /dev/sda maj-min: 8:0 vendor: SanDisk model: SD8SNAT-256G-1006
    size: 238.47 GiB block-size: physical: 4096 B logical: 512 B sata: 3.2
    speed: 6.0 Gb/s type: SSD serial: <filter> rev: 1006 temp: 17 C
    scheme: MBR
  SMART: yes state: enabled health: PASSED on: 50d 2h cycles: 2843
  ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: Western Digital
    model: WD50NDZW-11BCSS1 family: Elements / My Passport (USB, AF)
    size: 4.55 TiB block-size: physical: 4096 B logical: 512 B sata: 3.1
    speed: 6.0 Gb/s type: HDD rpm: 4800 serial: <filter> rev: 4010
    drive rev: 01.01A01 temp: 42 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 48d 11h cycles: 77
Partition:
  ID-1: / raw-size: 144.68 GiB size: 141.35 GiB (97.70%)
    used: 45.63 GiB (32.3%) fs: ext4 block-size: 4096 B dev: /dev/dm-0
    maj-min: 253:0 mapped: sda5_crypt
  ID-2: /boot raw-size: 3.72 GiB size: 3.59 GiB (96.36%)
    used: 295.6 MiB (8.0%) fs: ext4 block-size: 4096 B dev: /dev/sda3
    maj-min: 8:3
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 40.0 C pch: 36.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 283 Uptime: 1h 52m wakeups: 1 Memory: 15.4 GiB
  used: 6.49 GiB (42.1%) Init: systemd v: 252 target: graphical (5)
  default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12 Packages:
  pm: dpkg pkgs: 4064 libs: 2199 tools: apt,apt-get pm: rpm pkgs: 0
  Shell: Bash (su) v: 5.2.15 running-in: konsole inxi: 3.3.26
I mentioned "Swap: Alert: No swap data was found." in a output. Could it be the reason of such behaviour?

User avatar
FreewheelinFrank
Global Moderator
Global Moderator
Posts: 2409
Joined: 2010-06-07 16:59
Has thanked: 45 times
Been thanked: 265 times

Re: [Hardware] Can't wake up from sleep in KDE

#4 Post by FreewheelinFrank »

Maybe check BIOS options for sleep? There is a suggestion in link below that HP doesn't support sleep for anything except windows.

There is a link in the thread for the Arch Linux sleep troubleshooting page, which might be useful.

Try searching for your laptop model and see if there is any more information. It looks like there are two types of sleep: S0 and S3, and this laptop may not support the type that Linux uses.

I will have a deeper look too when I have time.

https://forum.manjaro.org/t/sleep-not-w ... /145103/14

User avatar
supersu
Posts: 17
Joined: 2017-09-10 10:54
Has thanked: 5 times

Re: [Hardware] Can't wake up from sleep in KDE

#5 Post by supersu »

FreewheelinFrank wrote: 2024-10-14 10:20 Maybe check BIOS options for sleep? There is a suggestion in link below that HP doesn't support sleep for anything except windows.

There is a link in the thread for the Arch Linux sleep troubleshooting page, which might be useful.

Try searching for your laptop model and see if there is any more information. It looks like there are two types of sleep: S0 and S3, and this laptop may not support the type that Linux uses.

I will have a deeper look too when I have time.

https://forum.manjaro.org/t/sleep-not-w ... /145103/14
The first thing I'd like to tell you thank you for your help!
https://forum.manjaro.org/t/sleep-not-w ... /145103/14
Looks like that it's almost the same problem as I have. I checked my BIOS but there is no any kind of configs relates to power saving modes.

In my case usage of systemctl suspend makes my laptop to sleep. And systemctl hibernate works as log out from my user but not as hibernate. At the same time if I use just "suspend" in console do nothing.

Could you please explain what does that output mean?

Code: Select all

cat /sys/power/mem_sleep
s2idle [deep]
Which mode of these 2 is active?[/s]
So in my case it's "deep" mode.

User avatar
FreewheelinFrank
Global Moderator
Global Moderator
Posts: 2409
Joined: 2010-06-07 16:59
Has thanked: 45 times
Been thanked: 265 times

Re: [Hardware] Can't wake up from sleep in KDE

#6 Post by FreewheelinFrank »

To summarise the Arch information:

S0ix = Modern Standby, S2idle

S3 = suspend, deep
[Warning about switching from S0ix to S3] Manufacturers have stopped fixing bugs with the ACPI S3 state since systems shipping with Windows are encouraged to use "Modern standby" by default; if they have voluntarily not advertised it, it is probably broken in some way.
In some opposite situations [switching from S3 to S0ix], faulty firmware advertises support for deep sleep, while only s2idle is supported
Your experience:

S3 is the default (deep) and seems to be broken.

S3 is advertised, but doesn't seem to be supported.

My guess would be that HP doesn't support S3 in this laptop, but that it as advertised due to faulty firmware as the second quote suggests.

My recommendation would be try S0ix.

Code: Select all

# echo s2idel > /sys/power/mem_sleep
(Temporary fix.)

Create directory and file (if not present)

Code: Select all

/etc/systemd/sleep.conf.d/mem-deep.conf
and add

Code: Select all

[Sleep]
MemorySleepMode=s2idle
(Permanent change.)

Alternative method:

Create directory and file (if not present)

Code: Select all

/etc/systemd/sleep.conf.d/freeze.conf
and add

Code: Select all

[Sleep]
SuspendState=freeze
Hopefully s2idel will work for you. Let us know the result. Fingers crossed.

User avatar
supersu
Posts: 17
Joined: 2017-09-10 10:54
Has thanked: 5 times

Re: [Hardware] Can't wake up from sleep in KDE

#7 Post by supersu »

When I tried to use

Code: Select all

echo s2idle > /sys/power/mem_sleep
my laptop turn off all peripheral devices and screen if I used systemctl suspend command. CPU fan resume to work.
Same behaviour when I use a "Sleep" button from menu.
But at the same time it's possible to wake up that laptop using keyboard.

At the same time, if I use "Hibernate" menu button, my laptop turns off everything, after that my screen becomes gray, I can see a cursor and after that, laptop turns off completely. Next to it I have to turn it on by pressing a power button.


Update:
So for now I tried another configuration:

Code: Select all

cat /sys/power/mem_sleep 
s2idle [deep]
Added to file /etc/systemd/sleep.conf 2 strings

Code: Select all

SuspendMode=suspend
HybridSleep=false
Restarted my laptop

But there is no "suspend" mode in a output of

Code: Select all

cat /sys/power/state
freeze mem disk

Update 2:

Code: Select all

journalctl -b | grep -i sleep
oct 15 11:40:39 PC451 kernel: ata3.00: Features: Dev-Sleep
oct 15 11:40:39 PC451 kernel: ahci 0000:00:17.0: port does not support device sleep
oct 15 11:40:46 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:40:46 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:40:46 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:40:47 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:40:47 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:40:47 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:41:14 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:41:14 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:41:14 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:41:14 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:41:14 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:41:14 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:41:14 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:44:54 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:44:54 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:44:54 PC451 NetworkManager[1173]: <info>  [1728985494.4219] manager: sleep: sleep requested (sleeping: no  enabled: yes)
oct 15 11:44:54 PC451 NetworkManager[1173]: <info>  [1728985494.4221] device (wlo1): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
oct 15 11:44:54 PC451 NetworkManager[1173]: <info>  [1728985494.4237] manager: NetworkManager state is now ASLEEP
oct 15 11:44:54 PC451 NetworkManager[1173]: <info>  [1728985494.4240] device (eno1): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
oct 15 11:44:54 PC451 ModemManager[962]: <info>  [sleep-monitor-systemd] system is about to suspend
oct 15 11:44:54 PC451 NetworkManager[1173]: <info>  [1728985494.4743] device (eno1): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
oct 15 11:44:54 PC451 NetworkManager[1173]: <info>  [1728985494.5676] device (eno1): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
oct 15 11:44:54 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:44:54 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:44:54 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:44:54 PC451 systemd[1]: Reached target sleep.target - Sleep.
oct 15 11:44:55 PC451 systemd-sleep[4699]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:44:55 PC451 systemd-sleep[4699]: Entering sleep state 'suspend'...
oct 15 11:45:07 PC451 kernel: ACPI: PM: Preparing to enter system sleep state S3
oct 15 11:45:07 PC451 kernel: ACPI: PM: Waking up from system sleep state S3
oct 15 11:45:07 PC451 kernel: ahci 0000:00:17.0: port does not support device sleep
oct 15 11:45:07 PC451 systemd-sleep[4699]: System returned from sleep state.
oct 15 11:45:07 PC451 systemd-sleep[4806]: /dev/sda:
oct 15 11:45:07 PC451 systemd-sleep[4806]:  setting Advanced Power Management level to 0xfe (254)
oct 15 11:45:07 PC451 systemd-sleep[4806]:  APM_level        = 254
oct 15 11:45:07 PC451 systemd[1]: Stopped target sleep.target - Sleep.
oct 15 11:45:07 PC451 systemd-logind[897]: Operation 'sleep' finished.
oct 15 11:45:07 PC451 ModemManager[962]: <info>  [sleep-monitor-systemd] system is resuming
oct 15 11:45:07 PC451 NetworkManager[1173]: <info>  [1728985507.4158] manager: sleep: wake requested (sleeping: yes  enabled: yes)
oct 15 11:48:02 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:48:02 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:48:02 PC451 NetworkManager[1173]: <info>  [1728985682.8924] manager: sleep: sleep requested (sleeping: no  enabled: yes)
oct 15 11:48:02 PC451 ModemManager[962]: <info>  [sleep-monitor-systemd] system is about to suspend
oct 15 11:48:02 PC451 NetworkManager[1173]: <info>  [1728985682.8927] device (wlo1): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
oct 15 11:48:02 PC451 NetworkManager[1173]: <info>  [1728985682.8940] manager: NetworkManager state is now ASLEEP
oct 15 11:48:02 PC451 NetworkManager[1173]: <info>  [1728985682.8943] device (eno1): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
oct 15 11:48:02 PC451 NetworkManager[1173]: <info>  [1728985682.9464] device (eno1): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
oct 15 11:48:03 PC451 NetworkManager[1173]: <info>  [1728985683.0236] device (eno1): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
oct 15 11:48:03 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:48:03 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:48:03 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:48:03 PC451 systemd[1]: Reached target sleep.target - Sleep.
oct 15 11:48:03 PC451 systemd-sleep[5301]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:48:03 PC451 systemd-sleep[5301]: Entering sleep state 'suspend'...
oct 15 11:48:15 PC451 kernel: ACPI: PM: Preparing to enter system sleep state S3
oct 15 11:48:15 PC451 kernel: ACPI: PM: Waking up from system sleep state S3
oct 15 11:48:15 PC451 kernel: ahci 0000:00:17.0: port does not support device sleep
oct 15 11:48:15 PC451 systemd-sleep[5301]: System returned from sleep state.
oct 15 11:48:15 PC451 systemd-sleep[5349]: /dev/sda:
oct 15 11:48:15 PC451 systemd-sleep[5349]:  setting Advanced Power Management level to 0xfe (254)
oct 15 11:48:15 PC451 systemd-sleep[5349]:  APM_level        = 254
oct 15 11:48:15 PC451 systemd[1]: Stopped target sleep.target - Sleep.
oct 15 11:48:15 PC451 systemd-logind[897]: Operation 'sleep' finished.
oct 15 11:48:15 PC451 NetworkManager[1173]: <info>  [1728985695.6817] manager: sleep: wake requested (sleeping: yes  enabled: yes)
oct 15 11:48:15 PC451 ModemManager[962]: <info>  [sleep-monitor-systemd] system is resuming
oct 15 11:48:45 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:48:45 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:48:45 PC451 NetworkManager[1173]: <info>  [1728985725.9163] manager: sleep: sleep requested (sleeping: no  enabled: yes)
oct 15 11:48:45 PC451 ModemManager[962]: <info>  [sleep-monitor-systemd] system is about to suspend
oct 15 11:48:45 PC451 NetworkManager[1173]: <info>  [1728985725.9167] device (wlo1): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
oct 15 11:48:45 PC451 NetworkManager[1173]: <info>  [1728985725.9214] manager: NetworkManager state is now ASLEEP
oct 15 11:48:45 PC451 NetworkManager[1173]: <info>  [1728985725.9237] device (eno1): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
oct 15 11:48:45 PC451 NetworkManager[1173]: <info>  [1728985725.9484] device (eno1): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
oct 15 11:48:46 PC451 NetworkManager[1173]: <info>  [1728985726.0228] device (eno1): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
oct 15 11:48:46 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:48:46 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:48:46 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:48:46 PC451 systemd[1]: Reached target sleep.target - Sleep.
oct 15 11:48:46 PC451 systemd-sleep[5582]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:48:46 PC451 systemd-sleep[5582]: Entering sleep state 'suspend'...
oct 15 11:48:57 PC451 kernel: ACPI: PM: Preparing to enter system sleep state S3
oct 15 11:48:57 PC451 kernel: ACPI: PM: Waking up from system sleep state S3
oct 15 11:48:57 PC451 kernel: ahci 0000:00:17.0: port does not support device sleep
oct 15 11:48:57 PC451 systemd-sleep[5582]: System returned from sleep state.
oct 15 11:48:57 PC451 systemd-sleep[5637]: /dev/sda:
oct 15 11:48:57 PC451 systemd-sleep[5637]:  setting Advanced Power Management level to 0xfe (254)
oct 15 11:48:57 PC451 systemd-sleep[5637]:  APM_level        = 254
oct 15 11:48:57 PC451 systemd[1]: Stopped target sleep.target - Sleep.
oct 15 11:48:57 PC451 systemd-logind[897]: Operation 'sleep' finished.
oct 15 11:48:57 PC451 NetworkManager[1173]: <info>  [1728985737.4940] manager: sleep: wake requested (sleeping: yes  enabled: yes)
oct 15 11:48:57 PC451 ModemManager[962]: <info>  [sleep-monitor-systemd] system is resuming
oct 15 11:49:10 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:49:10 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:49:10 PC451 NetworkManager[1173]: <info>  [1728985750.6290] manager: sleep: sleep requested (sleeping: no  enabled: yes)
oct 15 11:49:10 PC451 NetworkManager[1173]: <info>  [1728985750.6294] device (wlo1): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
oct 15 11:49:10 PC451 NetworkManager[1173]: <info>  [1728985750.6317] manager: NetworkManager state is now ASLEEP
oct 15 11:49:10 PC451 NetworkManager[1173]: <info>  [1728985750.6321] device (eno1): state change: ip-config -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
oct 15 11:49:10 PC451 ModemManager[962]: <info>  [sleep-monitor-systemd] system is about to suspend
oct 15 11:49:10 PC451 NetworkManager[1173]: <info>  [1728985750.7062] device (eno1): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
oct 15 11:49:10 PC451 NetworkManager[1173]: <info>  [1728985750.7277] device (eno1): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
oct 15 11:49:11 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:49:11 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:49:11 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:49:11 PC451 systemd[1]: Reached target sleep.target - Sleep.
oct 15 11:49:11 PC451 systemd-sleep[5812]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:49:11 PC451 systemd-sleep[5812]: Entering sleep state 'suspend'...
oct 15 11:50:10 PC451 kernel: ACPI: PM: Preparing to enter system sleep state S3
oct 15 11:50:10 PC451 kernel: ACPI: PM: Waking up from system sleep state S3
oct 15 11:50:10 PC451 kernel: ahci 0000:00:17.0: port does not support device sleep
oct 15 11:50:10 PC451 systemd-sleep[5812]: System returned from sleep state.
oct 15 11:50:10 PC451 systemd-sleep[5869]: /dev/sda:
oct 15 11:50:10 PC451 systemd-sleep[5869]:  setting Advanced Power Management level to 0xfe (254)
oct 15 11:50:10 PC451 systemd-sleep[5869]:  APM_level        = 254
oct 15 11:50:10 PC451 systemd[1]: Stopped target sleep.target - Sleep.
oct 15 11:50:10 PC451 systemd-logind[897]: Operation 'sleep' finished.
oct 15 11:50:10 PC451 ModemManager[962]: <info>  [sleep-monitor-systemd] system is resuming
oct 15 11:50:10 PC451 NetworkManager[1173]: <info>  [1728985810.5111] manager: sleep: wake requested (sleeping: yes  enabled: yes)
oct 15 11:50:16 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:50:16 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:50:16 PC451 NetworkManager[1173]: <info>  [1728985816.6026] manager: sleep: sleep requested (sleeping: no  enabled: yes)
oct 15 11:50:16 PC451 NetworkManager[1173]: <info>  [1728985816.6028] device (wlo1): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
oct 15 11:50:16 PC451 NetworkManager[1173]: <info>  [1728985816.6037] manager: NetworkManager state is now ASLEEP
oct 15 11:50:16 PC451 NetworkManager[1173]: <info>  [1728985816.6038] device (eno1): state change: ip-config -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
oct 15 11:50:16 PC451 ModemManager[962]: <info>  [sleep-monitor-systemd] system is about to suspend
oct 15 11:50:16 PC451 NetworkManager[1173]: <info>  [1728985816.6141] device (eno1): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
oct 15 11:50:16 PC451 NetworkManager[1173]: <info>  [1728985816.6366] device (eno1): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
oct 15 11:50:16 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:50:16 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:50:16 PC451 systemd-logind[897]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:50:17 PC451 systemd[1]: Reached target sleep.target - Sleep.
oct 15 11:50:17 PC451 systemd-sleep[6001]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 15 11:50:17 PC451 systemd-sleep[6001]: Entering sleep state 'suspend'...
oct 15 11:50:28 PC451 kernel: ACPI: PM: Preparing to enter system sleep state S3
oct 15 11:50:28 PC451 kernel: ACPI: PM: Waking up from system sleep state S3
oct 15 11:50:28 PC451 kernel: ahci 0000:00:17.0: port does not support device sleep
oct 15 11:50:28 PC451 systemd-sleep[6001]: System returned from sleep state.
oct 15 11:50:28 PC451 systemd-sleep[6047]: /dev/sda:
oct 15 11:50:28 PC451 systemd-sleep[6047]:  setting Advanced Power Management level to 0xfe (254)
oct 15 11:50:28 PC451 systemd-sleep[6047]:  APM_level        = 254
oct 15 11:50:28 PC451 systemd[1]: Stopped target sleep.target - Sleep.
oct 15 11:50:28 PC451 systemd-logind[897]: Operation 'sleep' finished.
oct 15 11:50:28 PC451 ModemManager[962]: <info>  [sleep-monitor-systemd] system is resuming
oct 15 11:50:28 PC451 NetworkManager[1173]: <info>  [1728985828.5307] manager: sleep: wake requested (sleeping: yes  enabled: yes)

User avatar
FreewheelinFrank
Global Moderator
Global Moderator
Posts: 2409
Joined: 2010-06-07 16:59
Has thanked: 45 times
Been thanked: 265 times

Re: [Hardware] Can't wake up from sleep in KDE

#8 Post by FreewheelinFrank »

supersu wrote: 2024-10-15 08:45 When I tried to use

Code: Select all

echo s2idle > /sys/power/mem_sleep
my laptop turn off all peripheral devices and screen if I used systemctl suspend command. CPU fan resume to work.
Same behaviour when I use a "Sleep" button from menu.
But at the same time it's possible to wake up that laptop using keyboard.
Does the fan stop after a period? What is the ambient temperature where you use the computer? What is CPU temp when you attempt suspend?

Is it possible the CPU is hot and the system recognises that it is not safe to shut off the fan before the CPU has cooled to a safe temperature?

User avatar
supersu
Posts: 17
Joined: 2017-09-10 10:54
Has thanked: 5 times

Re: [Hardware] Can't wake up from sleep in KDE

#9 Post by supersu »

FreewheelinFrank wrote: 2024-10-16 09:14 Does the fan stop after a period? What is the ambient temperature where you use the computer? What is CPU temp when you attempt suspend?

Is it possible the CPU is hot and the system recognises that it is not safe to shut off the fan before the CPU has cooled to a safe temperature?
No, I tried to wait but it doesn't stop. Theoretically it's possible, but it looks like the CPU temperature is fine.

User avatar
FreewheelinFrank
Global Moderator
Global Moderator
Posts: 2409
Joined: 2010-06-07 16:59
Has thanked: 45 times
Been thanked: 265 times

Re: [Hardware] Can't wake up from sleep in KDE

#10 Post by FreewheelinFrank »

supersu wrote: 2024-10-17 16:51
No, I tried to wait but it doesn't stop. Theoretically it's possible, but it looks like the CPU temperature is fine.
It looks like this issue is not limited to Linux users. See the following for example:

https://h30434.www3.hp.com/t5/Notebook- ... -p/7731231

https://h30434.www3.hp.com/t5/Gaming-No ... -p/7716878

It seems the CPU is active in s2idle, so maybe having the fan running is intentional? Probably better than having the CPU overheat.

https://discussion.fedoraproject.org/t/ ... heat/80004

Things you could try are:

*Check for firmware updates with fwupmgr

https://github.com/fwupd/fwupd

*Try a more recent kernel from Debian Backports to see if any fixes have been added for power handling.

*Note the time then enter suspend for a few minutes, note the time again then come out of suspend and run:

Code: Select all

# journalctl --since 09:00 --until 09:05
Substituting the times you noted. Post the output here and we can look for any relevant messages.

To be honest, s2idle seems to be intended for suspending the laptop for brief periods. You wouldn't want to be using it for transporting the laptop in a bag, for example. Hibernate is probably a better option for any long period of non-use.

Also see discussion here:

https://forums.debian.net/viewtopic.php ... 8&start=20

Suggestion that a newer kernel might work better.

User avatar
supersu
Posts: 17
Joined: 2017-09-10 10:54
Has thanked: 5 times

Re: [Hardware] Can't wake up from sleep in KDE

#11 Post by supersu »

FreewheelinFrank wrote: 2024-10-16 09:14 What is CPU temp when you attempt suspend?
Hello, sorry for a delay. Looks like my problem was not resolved. And it makes me sad.
The average temperature is 40-45 degrees.

FreewheelinFrank wrote: 2024-10-16 09:14 It looks like this issue is not limited to Linux users. See the following for example:
I'd tell that it's not related to my issue. But general responses from HP support makes me scary.

I tried to launch fwupdmgr but it told me that
WARNING: UEFI firmware can not be updated in legacy BIOS mode
so it looks like I'm using UEFI in fallback mode.

Besides that I updated my kernel from backports but no luck, problems are here. So let me try to explain again. I have the issues with sleep and hibernate modes.
1) Sometimes my laptop goes to sleep mode but cooler resume to work and the biggest problem - it's impossible to wake it up! I have to shut down that laptop forcefully. When I try to turn it on it starts to check partitions after incorrect shutdown.
Fan works but I can't wake it up.
2) Sometimes sleep mode works perfectly fine. Like 2, 5, 20 time (as I wrote previously) it goes to sleep mode and I can wake it up. No issues.
Everything turned off and I can wake it up from sleep mode.
3) From what I understood after couple of tests, when I try to put my laptop to hibernate state it turn off everything. After that screen backlight is turning on and screen becomes gray. After that my laptop turns off immediately. When I try to turn it on it starts to check partitions after incorrect shutdown. But to be honest, I don't care about hibernate mode at all.

I updated BIOS and kernel to latest versions but it didn't help. And there were no issues during last 3 years of Windows usage at all.

Next to it I added all of the configuration mentioned at this topic and my laptop goes to sleep mode and the most important thing - it's possible to wake it up. But the fan works all the time. So here is the output of commands:

Code: Select all

journalctl --since 14:27 --until 14:31
oct 24 14:27:14 PC451 dbus-daemon[937]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.41' (uid=1000 pid=17>
oct 24 14:27:14 PC451 dbus-daemon[937]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
oct 24 14:27:14 PC451 systemd-udevd[546]: /etc/udev/rules.d/99-megasync-udev.rules:1 The line takes no effect, ignoring.
oct 24 14:27:54 PC451 plasmashell[1756]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
oct 24 14:27:55 PC451 wireplumber[1554]: <WpSiNode:0x558cb3d39c40> Object activation aborted: proxy destroyed
oct 24 14:27:55 PC451 wireplumber[1554]: <WpSiNode:0x558cb3d39c40> failed to activate item: Object activation aborted: proxy destroyed
oct 24 14:27:56 PC451 systemd-logind[945]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 24 14:27:56 PC451 systemd-logind[945]: /etc/systemd/sleep.conf.d/mem-deep.conf:2: Unknown key 'MemorySleepMode' in section [Sleep], ignoring.
oct 24 14:27:56 PC451 systemd-logind[945]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 24 14:27:56 PC451 systemd-logind[945]: /etc/systemd/sleep.conf.d/mem-deep.conf:2: Unknown key 'MemorySleepMode' in section [Sleep], ignoring.
oct 24 14:27:56 PC451 systemd-logind[945]: The system will suspend now!
oct 24 14:27:56 PC451 NetworkManager[1238]: <info>  [1729772876.2003] manager: sleep: sleep requested (sleeping: no  enabled: yes)
oct 24 14:27:56 PC451 ModemManager[1016]: <info>  [sleep-monitor-systemd] system is about to suspend
oct 24 14:27:56 PC451 NetworkManager[1238]: <info>  [1729772876.2007] device (wlo1): state change: unavailable -> unmanaged (reason 'sleeping', sys>
oct 24 14:27:56 PC451 NetworkManager[1238]: <info>  [1729772876.2020] device (wlo1): set-hw-addr: reset MAC address to 28:C6:3F:D4:D4:56 (unmanage)
oct 24 14:27:56 PC451 NetworkManager[1238]: <info>  [1729772876.2073] manager: NetworkManager state is now ASLEEP
oct 24 14:27:56 PC451 NetworkManager[1238]: <info>  [1729772876.2078] device (eno1): state change: activated -> deactivating (reason 'sleeping', sy>
oct 24 14:27:56 PC451 kded5[1726]: org.kde.plasma.nm.kded: Unhandled active connection state change:  3
oct 24 14:27:56 PC451 dbus-daemon[937]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm>
oct 24 14:27:56 PC451 systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
oct 24 14:27:56 PC451 dbus-daemon[937]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
oct 24 14:27:56 PC451 systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
oct 24 14:27:56 PC451 NetworkManager[1238]: <info>  [1729772876.2623] device (eno1): state change: deactivating -> disconnected (reason 'sleeping',>
oct 24 14:27:56 PC451 kwin_wayland_wrapper[200405]: QSocketNotifier: Can only be used with threads started with QThread
oct 24 14:27:56 PC451 NetworkManager[1238]: <info>  [1729772876.2890] dhcp4 (eno1): canceled DHCP transaction
oct 24 14:27:56 PC451 NetworkManager[1238]: <info>  [1729772876.2890] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
oct 24 14:27:56 PC451 NetworkManager[1238]: <info>  [1729772876.2890] dhcp4 (eno1): state changed no lease
oct 24 14:27:56 PC451 charon[3020]: 13[KNL] 192.168.0.24 disappeared from eno1
oct 24 14:27:56 PC451 avahi-daemon[932]: Withdrawing address record for 192.168.0.24 on eno1.
oct 24 14:27:56 PC451 avahi-daemon[932]: Leaving mDNS multicast group on interface eno1.IPv4 with address 192.168.0.24.
oct 24 14:27:56 PC451 avahi-daemon[932]: Interface eno1.IPv4 no longer relevant for mDNS.
oct 24 14:27:56 PC451 NetworkManager[1238]: <info>  [1729772876.3341] device (eno1): state change: disconnected -> unmanaged (reason 'sleeping', sy>
oct 24 14:27:56 PC451 kernel: r8169 0000:01:00.0 eno1: Link is Down
oct 24 14:27:56 PC451 charon[3020]: 10[KNL] interface eno1 deactivated
oct 24 14:27:56 PC451 systemd-logind[945]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 24 14:27:56 PC451 systemd-logind[945]: /etc/systemd/sleep.conf.d/mem-deep.conf:2: Unknown key 'MemorySleepMode' in section [Sleep], ignoring.
oct 24 14:27:56 PC451 systemd-logind[945]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 24 14:27:56 PC451 systemd-logind[945]: /etc/systemd/sleep.conf.d/mem-deep.conf:2: Unknown key 'MemorySleepMode' in section [Sleep], ignoring.
oct 24 14:27:56 PC451 systemd-logind[945]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 24 14:27:56 PC451 systemd-logind[945]: /etc/systemd/sleep.conf.d/mem-deep.conf:2: Unknown key 'MemorySleepMode' in section [Sleep], ignoring.
oct 24 14:27:56 PC451 kwin_wayland_wrapper[200405]: kf.kirigami: Failed to find a Kirigami platform plugin
oct 24 14:27:56 PC451 kwin_wayland_wrapper[200405]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
oct 24 14:27:56 PC451 systemd[1]: Reached target sleep.target - Sleep.
oct 24 14:27:56 PC451 systemd[1]: Starting systemd-suspend.service - System Suspend...
oct 24 14:27:56 PC451 systemd-sleep[200458]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 24 14:27:56 PC451 systemd-sleep[200458]: /etc/systemd/sleep.conf.d/mem-deep.conf:2: Unknown key 'MemorySleepMode' in section [Sleep], ignoring.
oct 24 14:27:56 PC451 systemd-sleep[200458]: Entering sleep state 'suspend'...
oct 24 14:27:56 PC451 kernel: PM: suspend entry (s2idle)
oct 24 14:30:20 PC451 kernel: Filesystems sync: 0.015 seconds
oct 24 14:30:20 PC451 kernel: (NULL device *): firmware: direct-loading firmware i915/kbl_dmc_ver1_04.bin
oct 24 14:30:20 PC451 kernel: (NULL device *): firmware: direct-loading firmware iwlwifi-3168-29.ucode
oct 24 14:30:20 PC451 kernel: (NULL device *): firmware: direct-loading firmware regulatory.db
oct 24 14:30:20 PC451 kernel: (NULL device *): firmware: direct-loading firmware regulatory.db.p7s
oct 24 14:30:20 PC451 kernel: (NULL device *): firmware: direct-loading firmware intel/ibt-hw-37.8.10-fw-22.50.19.14.f.bseq
oct 24 14:30:20 PC451 kernel: Freezing user space processes
oct 24 14:30:20 PC451 kernel: Freezing user space processes completed (elapsed 0.002 seconds)
oct 24 14:30:20 PC451 kernel: OOM killer disabled.
oct 24 14:30:20 PC451 kernel: Freezing remaining freezable tasks
oct 24 14:30:20 PC451 kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
oct 24 14:30:20 PC451 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
oct 24 14:30:20 PC451 kernel: sd 2:0:0:0: [sda] Synchronizing SCSI cache
oct 24 14:30:20 PC451 kernel: ata3.00: Entering standby power mode
oct 24 14:30:20 PC451 kernel: ACPI: EC: interrupt blocked
oct 24 14:30:20 PC451 kernel: intel_pch_thermal 0000:00:14.2: CPU-PCH is cool [29C]
oct 24 14:30:20 PC451 kernel: ACPI: EC: interrupt unblocked
oct 24 14:30:20 PC451 kernel: pcieport 0000:00:1c.5: Intel SPT PCH root port ACS workaround enabled
oct 24 14:30:20 PC451 kernel: pcieport 0000:00:1c.0: Intel SPT PCH root port ACS workaround enabled
oct 24 14:30:20 PC451 kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
oct 24 14:30:20 PC451 kernel: ata3.00: Entering active power mode
oct 24 14:30:20 PC451 kernel: ata1: SATA link down (SStatus 4 SControl 300)
oct 24 14:30:20 PC451 kernel: ata2: SATA link down (SStatus 0 SControl 300)
oct 24 14:30:20 PC451 kernel: ata3.00: configured for UDMA/100
oct 24 14:30:20 PC451 kernel: ahci 0000:00:17.0: port does not support device sleep
oct 24 14:30:20 PC451 kernel: OOM killer enabled.
oct 24 14:30:20 PC451 kernel: Restarting tasks ... 
oct 24 14:30:20 PC451 kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
oct 24 14:30:20 PC451 kernel: done.
oct 24 14:30:20 PC451 kernel: random: crng reseeded on system resumption
oct 24 14:30:20 PC451 kernel: thermal thermal_zone6: failed to read out thermal zone (-61)
oct 24 14:30:20 PC451 systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
oct 24 14:30:20 PC451 systemd[1]: sysstat-collect.service: Deactivated successfully.
oct 24 14:30:20 PC451 systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
oct 24 14:30:20 PC451 systemd-udevd[546]: /etc/udev/rules.d/99-megasync-udev.rules:1 The line takes no effect, ignoring.
oct 24 14:30:20 PC451 systemd-sleep[200458]: System returned from sleep state.
oct 24 14:30:20 PC451 kernel: PM: suspend exit
oct 24 14:30:20 PC451 kwin_wayland_wrapper[200405]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
oct 24 14:30:20 PC451 systemd-sleep[200563]: /dev/sda:
oct 24 14:30:20 PC451 systemd-sleep[200563]:  setting Advanced Power Management level to 0xfe (254)
oct 24 14:30:20 PC451 systemd-sleep[200563]:  APM_level        = 254
oct 24 14:30:20 PC451 fwupd[139027]: 12:30:20.506 FuPluginIntelMe      failed to get public key using /fpf/OemCred: generic failure [0xb]
oct 24 14:30:20 PC451 systemd[1]: systemd-suspend.service: Deactivated successfully.
oct 24 14:30:20 PC451 systemd[1]: Finished systemd-suspend.service - System Suspend.
oct 24 14:30:20 PC451 systemd[1]: Stopped target sleep.target - Sleep.
oct 24 14:30:20 PC451 systemd[1]: Reached target suspend.target - Suspend.
oct 24 14:30:20 PC451 systemd[1]: Stopped target suspend.target - Suspend.
oct 24 14:30:20 PC451 systemd-logind[945]: Operation 'sleep' finished.
oct 24 14:30:20 PC451 ModemManager[1016]: <info>  [sleep-monitor-systemd] system is resuming
oct 24 14:30:20 PC451 kded5[1726]: kf.bluezqt: PendingCall Error: "Failed"
oct 24 14:30:20 PC451 NetworkManager[1238]: <info>  [1729773020.5281] manager: sleep: wake requested (sleeping: yes  enabled: yes)
oct 24 14:30:20 PC451 bluetoothd[933]: Failed to set mode: Failed (0x03)
oct 24 14:30:20 PC451 NetworkManager[1238]: <info>  [1729773020.5282] device (eno1): state change: unmanaged -> unavailable (reason 'managed', sys->
oct 24 14:30:20 PC451 kernel: psmouse serio1: synaptics: queried max coordinates: x [..5648], y [..4826]
oct 24 14:30:20 PC451 kernel: Generic FE-GE Realtek PHY r8169-0-100:00: attached PHY driver (mii_bus:phy_addr=r8169-0-100:00, irq=MAC)
oct 24 14:30:20 PC451 kernel: psmouse serio1: synaptics: queried min coordinates: x [1292..], y [1026..]
oct 24 14:30:20 PC451 charon[3020]: 06[KNL] interface eno1 activated
oct 24 14:30:20 PC451 NetworkManager[1238]: <info>  [1729773020.7505] device (wlo1): state change: unmanaged -> unavailable (reason 'managed', sys->
oct 24 14:30:20 PC451 kernel: r8169 0000:01:00.0 eno1: Link is Down
oct 24 14:30:20 PC451 NetworkManager[1238]: <info>  [1729773020.7529] device (wlo1): set-hw-addr: set MAC address to 25:8E:22:A4:84:A1 (scanning)
oct 24 14:30:20 PC451 NetworkManager[1238]: <info>  [1729773020.7542] manager: NetworkManager state is now CONNECTED_LOCAL
oct 24 14:30:23 PC451 ModemManager[1016]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.0/0000:01:00>
oct 24 14:30:23 PC451 ModemManager[1016]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.5/0000:02:00>
oct 24 14:30:23 PC451 NetworkManager[1238]: <info>  [1729773023.6780] device (eno1): carrier: link connected
oct 24 14:30:23 PC451 kernel: r8169 0000:01:00.0 eno1: Link is Up - 1Gbps/Full - flow control rx/tx
oct 24 14:30:23 PC451 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
oct 24 14:30:23 PC451 NetworkManager[1238]: <info>  [1729773023.6792] device (eno1): state change: unavailable -> disconnected (reason 'carrier-cha>
oct 24 14:30:23 PC451 NetworkManager[1238]: <info>  [1729773023.6819] policy: auto-activating connection 'Проводное соединение 1' (cfe619f6-6e10-38>
oct 24 14:30:23 PC451 NetworkManager[1238]: <info>  [1729773023.6838] device (eno1): Activation: starting connection 'Проводное соединение 1' (cfe6>
oct 24 14:30:23 PC451 NetworkManager[1238]: <info>  [1729773023.6842] device (eno1): state change: disconnected -> prepare (reason 'none', sys-ifac>
oct 24 14:30:23 PC451 NetworkManager[1238]: <info>  [1729773023.6856] manager: NetworkManager state is now CONNECTING
oct 24 14:30:23 PC451 NetworkManager[1238]: <info>  [1729773023.6864] device (eno1): state change: prepare -> config (reason 'none', sys-iface-stat>
oct 24 14:30:23 PC451 NetworkManager[1238]: <info>  [1729773023.7285] device (eno1): state change: config -> ip-config (reason 'none', sys-iface-st>
oct 24 14:30:23 PC451 NetworkManager[1238]: <info>  [1729773023.7288] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
oct 24 14:30:23 PC451 CRON[200634]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
oct 24 14:30:23 PC451 CRON[200635]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron s>
oct 24 14:30:23 PC451 CRON[200634]: pam_unix(cron:session): session closed for user root
oct 24 14:30:25 PC451 plasmashell[1756]: kpipewire_logging: Window not available PipeWireSourceItem_QML_993(0x56200a0cd3c0, parent=0x562008d5b060, >
oct 24 14:30:28 PC451 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
oct 24 14:30:28 PC451 plasmashell[1756]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x56200b5d8380) QQmlContext(0x56200872ab50) QUrl("fil>
oct 24 14:30:28 PC451 plasmashell[1756]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x56200b5d8380) QQmlContext(0x56200872ab50) QUrl("fil





dmesg | grep ahci
[    1.464734] ahci 0000:00:17.0: version 3.0
[    1.464946] ahci 0000:00:17.0: AHCI 0001.0301 32 slots 3 ports 6 Gbps 0x7 impl SATA mode
[    1.464950] ahci 0000:00:17.0: flags: 64bit ncq ilck pm led clo only pio slum part deso sadm sds apst 
[    1.465680] scsi host0: ahci
[    1.466038] scsi host1: ahci
[    1.466461] scsi host2: ahci
[    1.798535] ahci 0000:00:17.0: port does not support device sleep
[18418.539646] ahci 0000:00:17.0: port does not support device sleep
[20750.582800] ahci 0000:00:17.0: port does not support device sleep

At the end I fixed these errors
oct 24 14:27:56 PC451 systemd-logind[945]: /etc/systemd/sleep.conf:29: Unknown key 'HybridSleep' in section [Sleep], ignoring.
oct 24 14:27:56 PC451 systemd-logind[945]: /etc/systemd/sleep.conf.d/mem-deep.conf:2: Unknown key 'MemorySleepMode' in section [Sleep], ignoring.
and edited /etc/systemd/sleep.conf file. I added 3 lines there
SuspendMode=suspend
AllowHybridSleep=false
SuspendState=freeze

for now sleep mode works but CPU fan don't want to stop.

User avatar
FreewheelinFrank
Global Moderator
Global Moderator
Posts: 2409
Joined: 2010-06-07 16:59
Has thanked: 45 times
Been thanked: 265 times

Re: [Hardware] Can't wake up from sleep in KDE

#12 Post by FreewheelinFrank »

Windows users are complaining about fans *not* coming on while the laptop is in sleep, so maybe Linux is doing the right thing in cooling the CPUs?

https://h30434.www3.hp.com/t5/Notebook- ... -p/8716778

"Modern Suspend" aka S0ix aka S2idle is a Microsoft thing, and if you search it, you will find many Microsoft users complaining bitterly about battery drain or overheating CPUs.

It could be that HP has messed up the implementation in this hardware, and Windows is simply leaving the CPUs to cook.

I will have a look at the output when I'm on my PC, as it's difficult to read on a phone.

User avatar
supersu
Posts: 17
Joined: 2017-09-10 10:54
Has thanked: 5 times

Re: [Hardware] Can't wake up from sleep in KDE

#13 Post by supersu »

FreewheelinFrank wrote: 2024-10-24 15:55 I will have a look at the output when I'm on my PC, as it's difficult to read on a phone.
Thank you for the explanation and help. Waiting for your response.
FreewheelinFrank wrote: 2024-10-24 15:55 you will find many Microsoft users complaining bitterly about battery drain or overheating CPUs.
Theoretically it could be related, yes.

User avatar
FreewheelinFrank
Global Moderator
Global Moderator
Posts: 2409
Joined: 2010-06-07 16:59
Has thanked: 45 times
Been thanked: 265 times

Re: [Hardware] Can't wake up from sleep in KDE

#14 Post by FreewheelinFrank »

From the output it looks like the system is entering and leaving s2idle without any issues. Not that I'm an expert.

If BIOS is up to date and latest kernel doesn't work, you may need to file a bug report so that people who are experts in this can have a look. It may need a fix in the kernel to work. This would obviously help other users, if you have the time to do it.

My guess would be that Windows knows about and has access to some firmware settings that are not advertised in the BIOS. Not untypical of manufacturers: fix it in Windows and not give a rat's ass about Linux. Again, I'm not an expert.

User avatar
supersu
Posts: 17
Joined: 2017-09-10 10:54
Has thanked: 5 times

Re: [Hardware] Can't wake up from sleep in KDE

#15 Post by supersu »

FreewheelinFrank wrote: 2024-10-25 09:01 If BIOS is up to date and latest kernel doesn't work, you may need to file a bug report so that people who are experts in this can have a look. It may need a fix in the kernel to work. This would obviously help other users, if you have the time to do it.
Thanks again for your help. Could you please explain how can I create a bug report? And where?

User avatar
FreewheelinFrank
Global Moderator
Global Moderator
Posts: 2409
Joined: 2010-06-07 16:59
Has thanked: 45 times
Been thanked: 265 times

Re: [Hardware] Can't wake up from sleep in KDE

#16 Post by FreewheelinFrank »

supersu wrote: 2024-10-27 10:27
FreewheelinFrank wrote: 2024-10-25 09:01 If BIOS is up to date and latest kernel doesn't work, you may need to file a bug report so that people who are experts in this can have a look. It may need a fix in the kernel to work. This would obviously help other users, if you have the time to do it.
Thanks again for your help. Could you please explain how can I create a bug report? And where?
https://www.debian.org/Bugs/Reporting

The reportbug program will give you an opportunity to review existing bugs. If there is an existing bug for fans working in suspend, you can probably add your information to that. I'd imagine the bug is in the kernel, as AFAIK, power handling fixes are done there. As mentioned in the link, you can send an email and ask for advice if you are not sure. Thanks for taking the time to do it. This is how things get fixed.

Post Reply