Suspend Issues

Issues & Assistance
1

Hello everyone.

I’ve been banging my head on this since my initial install of garuda. I am a Windows user primarily who has tried a few times over the years to migrate to linux.

I’m incredibly pleased with my system performance, gaming performance etc. since I installed garuda. Other than the KDE janky animations that I attribute to X11 (I use an NVIDIA RTX3080, Wayland is an issue) my games run smoothly, fast, and without issue.

However, no matter what I try, I cannot suspend or hibernate my system. When I choose to suspend, my keyboard/mouse lighting will switch off, the screens will go dark, and after about 30-45 seconds the speakers will “pop”. However, the system power will remain on. If I hit a key on my keyboard, the system will return to the lock screen as if it was turning back on for the first time.

```text
System:
  Kernel: 6.5.7-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1 clocksource: tsc
    available: acpi_pm parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=16e6b88c-2d5c-4fda-8cab-7cb7346a56c2 rw rootflags=subvol=@ quiet quiet
    rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3 ibt=off module_blacklist=r8169
    mem_sleep_default=s2idle
  Desktop: KDE Plasma v: 5.27.8 tk: Qt v: 5.15.11 wm: kwin_x11 dm: SDDM Distro: Garuda Linux
    base: Arch Linux
Machine:
  Type: Desktop System: Alienware product: Alienware Aurora R11 v: 1.0.21 serial: <filter> Chassis:
    type: 3 serial: <filter>
  Mobo: Alienware model: 0N43JM v: A00 serial: <filter> UEFI: Alienware v: 1.0.21
    date: 07/04/2023
CPU:
  Info: model: Intel Core i7-10700 socket: U3E1 bits: 64 type: MT MCP arch: Comet Lake gen: core 10
    level: v3 note: check built: 2020 process: Intel 14nm family: 6 model-id: 0xA5 (165) stepping: 5
    microcode: 0xF8
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 512 KiB
    desc: d-8x32 KiB; i-8x32 KiB L2: 2 MiB desc: 8x256 KiB L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 2718 high: 4699 min/max: 800/4800 base/boost: 2871/8300 scaling:
    driver: intel_pstate governor: powersave volts: 0.8 V ext-clock: 100 MHz cores: 1: 4699 2: 4602
    3: 4602 4: 800 5: 800 6: 4605 7: 800 8: 800 9: 4616 10: 800 11: 4602 12: 800 13: 4666 14: 4696
    15: 800 16: 800 bogomips: 92796
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: NVIDIA GA102 [GeForce RTX 3080] vendor: Dell driver: nvidia v: 535.113.01
    alternate: nouveau,nvidia_drm non-free: 535.xx+ status: current (as of 2023-09) arch: Ampere
    code: GAxxx process: TSMC n7 (7nm) built: 2020-23 pcie: gen: 3 speed: 8 GT/s lanes: 8 link-max:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:2206 class-ID: 0300
  Display: server: X.Org v: 21.1.8 with: Xwayland v: 23.2.1 compositor: kwin_x11 driver: X:
    loaded: modesetting,nvidia alternate: fbdev,nouveau,nv,vesa gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3840x1080 s-dpi: 90 s-size: 1084x301mm (42.68x11.85")
    s-diag: 1125mm (44.29")
  Monitor-1: DP-4 pos: primary,left res: 1920x1080 hz: 60 dpi: 90 size: 544x303mm (21.42x11.93")
    diag: 623mm (24.52") modes: N/A
  Monitor-2: HDMI-0 pos: right res: 1920x1080 hz: 60 dpi: 92 size: 531x299mm (20.91x11.77")
    diag: 609mm (23.99") modes: N/A
  Monitor-3: None-1-1 size-res: N/A modes: N/A
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2 drv: swrast gbm:
    drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 535.113.01 glx-v: 1.4
    direct-render: yes renderer: NVIDIA GeForce RTX 3080/PCIe/SSE2 memory: 9.77 GiB
  API: Vulkan v: 1.3.264 layers: 1 device: 0 type: discrete-gpu name: NVIDIA GeForce RTX 3080
    driver: nvidia v: 535.113.01 device-ID: 10de:2206 surfaces: xcb,xlib
Audio:
  Device-1: Intel Comet Lake PCH cAVS vendor: Dell driver: snd_hda_intel v: kernel
    alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:06c8 class-ID: 0403
  Device-2: NVIDIA GA102 High Definition Audio vendor: Dell driver: snd_hda_intel v: kernel pcie:
    gen: 3 speed: 8 GT/s lanes: 8 link-max: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.1
    chip-ID: 10de:1aef class-ID: 0403
  API: ALSA v: k6.5.7-zen2-1-zen status: kernel-api with: aoss type: oss-emulator tools: N/A
  Server-1: PipeWire v: 0.3.82 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: Intel Comet Lake PCH CNVi WiFi driver: iwlwifi v: kernel bus-ID: 00:14.3
    chip-ID: 8086:06f0 class-ID: 0280
  IF: wlo1 state: down mac: <filter>
  Device-2: Realtek Killer E3000 2.5GbE vendor: Dell driver: N/A modules: r8169 pcie: gen: 2
    speed: 5 GT/s lanes: 1 port: 3000 bus-ID: 04:00.0 chip-ID
: 10ec:3000 class-ID: 0200
  Device-3: ASIX AX88179 Gigabit Ethernet driver: ax88179_178a type: USB rev: 3.0 speed: 5 Gb/s
    lanes: 1 mode: 3.2 gen-1x1 bus-ID: 2-1:2 chip-ID: 0b95:1790 class-ID: ff00 serial: <filter>
  IF: enp0s20f0u1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1
    mode: 1.1 bus-ID: 1-14:5 chip-ID: 8087:0026 class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2 lmp-v: 11 status:
    discoverable: no pairing: no class-ID: 7c0104
Drives:
  Local Storage: total: 2.73 TiB used: 1.2 TiB (43.9%)
  ID-1: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 2B4QFXO7 temp: 31.9 C scheme: GPT
  SMART: yes health: PASSED on: 9d 4h cycles: 695 read-units: 20,602,315 [10.5 TB]
    written-units: 16,084,543 [8.23 TB]
  ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST2000DM008-2FR102
    family: BarraCuda 3.5 (SMR) size: 1.82 TiB block-size: physical: 4096 B logical: 512 B sata: 3.1
    speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter> fw-rev: 1003 temp: 39 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 10554h+06m+59.913s cycles: 2206 read: 12.71 TiB
    written: 12.99 TiB Pre-Fail: attribute: Spin_Retry_Count value: 100 worst: 100 threshold: 97
Partition:
  ID-1: / raw-size: 734.95 GiB size: 734.95 GiB (100.00%) used: 150.44 GiB (20.5%) fs: btrfs
    block-size: 4096 B dev: /dev/nvme1n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: N/A size: 96 MiB used: 42.3 MiB (44.1%) fs: vfat block-size: 512 B
    dev: /dev/nvme0n1p1
  ID-3: /home raw-size: 734.95 GiB size: 734.95 GiB (100.00%) used: 150.44 GiB (20.5%) fs: btrfs
    block-size: 4096 B dev: /dev/nvme1n1p2 maj-min: 259:2
  ID-4: /var/log raw-size: 734.95 GiB size: 734.95 GiB (100.00%) used: 150.44 GiB (20.5%)
    fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 734.95 GiB size: 734.95 GiB (100.00%) used: 150.44 GiB (20.5%)
    fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p2 maj-min: 259:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 15.42 GiB used: 0 KiB (0.0%) priority: 100 comp: zstd
    avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 47.0 C pch: 35.0 C mobo: N/A gpu: nvidia temp: 37 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 32%
Info:
  Processes: 394 Uptime: 1h 1m wakeups: 1 Memory: total: 16 GiB available: 15.42 GiB
  used: 4.52 GiB (29.3%) Init: systemd v: 254 default: graphical tool: systemctl Compilers:
  gcc: 13.2.1 Packages: 1452 pm: pacman pkgs: 1442 libs: 454 tools: octopi,paru pm: flatpak
  pkgs: 10 Client: shell wrapper v: 5.1.16-release inxi: 3.3.30
Garuda (2.6.17-1):
  System install date:     2023-10-16
  Last full system update: 2023-10-17 ↻
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut nvidia-dkms
  Windows dual boot:       No/Undetected  **my note: I am dual boot**
  Failed units:

I have tried many different solutions from two days of googling and scouring the internet, from the LTS kernel, to modifications to various services, none of which are of any help. I have also ensured that windows fast boot options are disabled.

I suspect one of my hardware are at fault, based on my logs I’ve parsed:

Oct 17 15:00:00 JMLinux systemd-logind[803]: The system will suspend now!
Oct 17 15:00:00 JMLinux ModemManager[874]: <msg> [sleep-monitor-systemd] system is about to suspend
Oct 17 15:00:00 JMLinux NetworkManager[849]: <info>  [1697565600.3608] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Oct 17 15:00:00 JMLinux NetworkManager[849]: <info>  [1697565600.3609] device (wlo1): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Oct 17 15:00:00 JMLinux NetworkManager[849]: <info>  [1697565600.3757] device (wlo1): set-hw-addr: reset MAC address to DC:41:A9:17:61:87 (unmanage)
Oct 17 15:00:00 JMLinux NetworkManager[849]: <info>  [1697565600.3854] device (p2p-dev-wlo1): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Oct 17 15:00:00 JMLinux NetworkManager[849]: <info>  [1697565600.3855] manager: NetworkManager state is now ASLEEP
Oct 17 15:00:00 JMLinux NetworkManager[849]: <info>  [1697565600.3855] device (enp0s20f0u1): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Oct 17 15:00:00 JMLinux wpa_supplicant[888]: p2p-dev-wlo1: CTRL-EVENT-DSCP-POLICY clear_all
Oct 17 15:00:00 JMLinux wpa_supplicant[888]: p2p-dev-wlo1: CTRL-EVENT-DSCP-POLICY clear_all
Oct 17 15:00:00 JMLinux wpa_supplicant[888]: nl80211: deinit ifname=p2p-dev-wlo1 disabled_11b_rates=0
Oct 17 15:00:00 JMLinux kded5[1305]: org.kde.plasma.nm.kded: Unhandled active connection state change:  3
Oct 17 15:00:00 JMLinux dbus-daemon[794]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.7' (uid=0 pid=849 comm="/usr/bin/NetworkManager --no-daemon")
Oct 17 15:00:00 JMLinux surfsharkd.js[1790]: {"event":"update","state":{"network_manager_state":10,"openvpn_vpn_state":0,"openvpn_vpn_reason":0,"openvpn_active_connection_state":4,"openvpn_active_connection_reason":0,"wg_active_connection_state":4,"wg_active_connection_reason":0,"user_locked":false,"current_physical_connection":{"id":"Wired Connection","type":"802-3-ethernet","uuid":"8b13c543-d8dd-4803-81f2-ecf175dac5fa","wireless_security":null,"internal_networks":[{"gateway":"192.168.2.1","protocol":"ipv4","address":"192.168.2.37","family":24,"_noncompliant":false}],"interface_name":"enp0s20f0u1","_noncompliant":false}}}
Oct 17 15:00:00 JMLinux systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 17 15:00:00 JMLinux wpa_supplicant[888]: wlo1: CTRL-EVENT-DSCP-POLICY clear_all
Oct 17 15:00:00 JMLinux dbus-daemon[794]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 17 15:00:00 JMLinux systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 17 15:00:00 JMLinux NetworkManager[849]: <info>  [1697565600.4184] device (enp0s20f0u1): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Oct 17 15:00:00 JMLinux avahi-daemon[792]: Withdrawing address record for fe80::2593:aa6d:b89c:a174 on enp0s20f0u1.
Oct 17 15:00:00 JMLinux avahi-daemon[792]: Leaving mDNS multicast group on interface enp0s20f0u1.IPv6 with address fe80::2593:aa6d:b89c:a174.
Oct 17 15:00:00 JMLinux NetworkManager[849]: <info>  [1697565600.4185] dhcp4 (enp0s20f0u1): canceled DHCP transaction
Oct 17 15:00:00 JMLinux avahi-daemon[792]: Interface enp0s20f0u1.IPv6 no longer relevant for mDNS.
Oct 17 15:00:00 JMLinux NetworkManager[849]: <info>  [1697565600.4185] dhcp4 (enp0s20f0u1): activation: beginning transaction (timeout in 45 seconds)
Oct 17 15:00:00 JMLinux NetworkManager[849]: <info>  [1697565600.4185] dhcp4 (enp0s20f0u1): state changed no lease
Oct 17 15:00:00 JMLinux DiscoverNotifier[1532]: packagekitqt.offline: Cannot process "org.freedesktop.PackageKit" as "org.freedesktop.PackageKit.Offline"
Oct 17 15:00:00 JMLinux avahi-daemon[792]: Withdrawing address record for 192.168.2.37 on enp0s20f0u1.
Oct 17 15:00:00 JMLinux avahi-daemon[792]: Leaving mDNS multicast group on interface enp0s20f0u1.IPv4 with address 192.168.2.37.
Oct 17 15:00:00 JMLinux avahi-daemon[792]: Interface enp0s20f0u1.IPv4 no longer relevant for mDNS.
Oct 17 15:00:00 JMLinux wpa_supplicant[888]: wlo1: CTRL-EVENT-DSCP-POLICY clear_all
Oct 17 15:00:00 JMLinux wpa_supplicant[888]: nl80211: deinit ifname=wlo1 disabled_11b_rates=0
Oct 17 15:00:00 JMLinux NetworkManager[849]: <info>  [1697565600.4432] device (enp0s20f0u1): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Oct 17 15:00:00 JMLinux plasmashell[1367]: qt.svg: <input>:510:9: Could not resolve property: #paint4_linear_678_483
Oct 17 15:00:00 JMLinux PackageKit[1601]: get-updates transaction /4_dcbedcba from uid 1000 finished with success after 0ms
Oct 17 15:00:00 JMLinux kwin_x11[1306]: kwin_core: XCB error: 152 (BadDamage), sequence: 34891, resource id: 14683049, major code: 143 (DAMAGE), minor code: 3 (Subtract)
Oct 17 15:00:00 JMLinux kscreenlocker_greet[2945]: Qt: Session management error: networkIdsList argument is NULL
Oct 17 15:00:00 JMLinux kscreenlocker_greet[2945]: kscreenlocker_greet: Lockscreen QML outdated, falling back to default
Oct 17 15:00:01 JMLinux kscreenlocker_greet[2945]: kf.kirigami: Failed to find a Kirigami platform plugin
Oct 17 15:00:01 JMLinux kscreenlocker_greet[2945]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:8:1: module "QtQuick.VirtualKeyboard" is not installed
Oct 17 15:00:01 JMLinux kscreenlocker_greet[2945]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:8:1: module "QtQuick.VirtualKeyboard" is not installed
Oct 17 15:00:01 JMLinux kscreenlocker_greet[2945]: qt.svg: <input>:304:9: Could not resolve property: #paint1_linear_909_67
Oct 17 15:00:01 JMLinux kscreenlocker_greet[2945]: qt.svg: <input>:304:9: Could not resolve property: #paint3_linear_909_67
Oct 17 15:00:01 JMLinux kscreenlocker_greet[2945]: qt.svg: <input>:304:9: Could not resolve property: #paint1_linear_909_67
Oct 17 15:00:01 JMLinux kscreenlocker_greet[2945]: qt.svg: <input>:304:9: Could not resolve property: #paint3_linear_909_67
Oct 17 15:00:01 JMLinux kscreenlocker_greet[2945]: qt.svg: <input>:304:9: Could not resolve property: #paint1_linear_650_128
Oct 17 15:00:01 JMLinux kscreenlocker_greet[2945]: qt.svg: <input>:304:9: Could not resolve property: #paint1_linear_650_128
Oct 17 15:00:01 JMLinux kscreenlocker_greet[2945]: qt.svg: <input>:304:9: Could not resolve property: #paint1_linear_905_67
Oct 17 15:00:01 JMLinux kscreenlocker_greet[2945]: qt.svg: <input>:304:9: Could not resolve property: #paint1_linear_905_67
Oct 17 15:00:01 JMLinux kscreenlocker_greet[2945]: qt.svg: <input>:304:9: Could not resolve property: #paint1_linear_637_218
Oct 17 15:00:01 JMLinux kscreenlocker_greet[2945]: qt.svg: <input>:304:9: Could not resolve property: #paint1_linear_637_218
Oct 17 15:00:01 JMLinux systemd[1]: Reached target Sleep.
Oct 17 15:00:01 JMLinux systemd[1]: Starting NVIDIA system suspend actions...
Oct 17 15:00:01 JMLinux suspend[2990]: nvidia-suspend.service
Oct 17 15:00:01 JMLinux logger[2990]: <13>Oct 17 15:00:01 suspend: nvidia-suspend.service
Oct 17 15:00:01 JMLinux kernel: snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD data byte 12
Oct 17 15:00:01 JMLinux bluetoothd[793]: Endpoint unregistered: sender=:1.48 path=/MediaEndpoint/A2DPSource/ldac
Oct 17 15:00:01 JMLinux bluetoothd[793]: Endpoint unregistered: sender=:1.48 path=/MediaEndpoint/A2DPSink/aptx_hd
Oct 17 15:00:01 JMLinux bluetoothd[793]: Endpoint unregistered: sender=:1.48 path=/MediaEndpoint/A2DPSource/aptx_hd
Oct 17 15:00:01 JMLinux bluetoothd[793]: Endpoint unregistered: sender=:1.48 path=/MediaEndpoint/A2DPSink/aptx
Oct 17 15:00:01 JMLinux bluetoothd[793]: Endpoint unregistered: sender=:1.48 path=/MediaEndpoint/A2DPSource/aptx
Oct 17 15:00:01 JMLinux bluetoothd[793]: Endpoint unregistered: sender=:1.48 path=/MediaEndpoint/A2DPSink/aac
Oct 17 15:00:01 JMLinux bluetoothd[793]: Endpoint unregistered: sender=:1.48 path=/MediaEndpoint/A2DPSource/aac
Oct 17 15:00:01 JMLinux bluetoothd[793]: Endpoint unregistered: sender=:1.48 path=/MediaEndpoint/A2DPSink/sbc
Oct 17 15:00:01 JMLinux bluetoothd[793]: Endpoint unregistered: sender=:1.48 path=/MediaEndpoint/A2DPSource/sbc
Oct 17 15:00:01 JMLinux bluetoothd[793]: Endpoint unregistered: sender=:1.48 path=/MediaEndpoint/A2DPSink/sbc_xq
Oct 17 15:00:01 JMLinux bluetoothd[793]: Endpoint unregistered: sender=:1.48 path=/MediaEndpoint/A2DPSource/sbc_xq
Oct 17 15:00:01 JMLinux bluetoothd[793]: Endpoint unregistered: sender=:1.48 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Oct 17 15:00:01 JMLinux bluetoothd[793]: Endpoint unregistered: sender=:1.48 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Oct 17 15:00:01 JMLinux bluetoothd[793]: Endpoint unregistered: sender=:1.48 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Oct 17 15:00:01 JMLinux bluetoothd[793]: Endpoint unregistered: sender=:1.48 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Oct 17 15:00:01 JMLinux bluetoothd[793]: Endpoint unregistered: sender=:1.48 path=/MediaEndpoint/A2DPSource/faststream
Oct 17 15:00:01 JMLinux bluetoothd[793]: Endpoint unregistered: sender=:1.48 path=/MediaEndpoint/A2DPSource/faststream_duplex
Oct 17 15:00:01 JMLinux bluetoothd[793]: Endpoint unregistered: sender=:1.48 path=/MediaEndpoint/A2DPSink/opus_05
Oct 17 15:00:01 JMLinux bluetoothd[793]: Endpoint unregistered: sender=:1.48 path=/MediaEndpoint/A2DPSource/opus_05
Oct 17 15:00:01 JMLinux bluetoothd[793]: Endpoint unregistered: sender=:1.48 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Oct 17 15:00:01 JMLinux bluetoothd[793]: Endpoint unregistered: sender=:1.48 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Oct 17 15:00:02 JMLinux systemd[1]: nvidia-suspend.service: Deactivated successfully.
Oct 17 15:00:02 JMLinux systemd[1]: Finished NVIDIA system suspend actions.
Oct 17 15:00:02 JMLinux systemd[1]: Starting System Suspend...
Oct 17 15:00:02 JMLinux systemd-sleep[3004]: Entering sleep state 'suspend'...
Oct 17 15:00:02 JMLinux kernel: PM: suspend entry (s2idle)
Oct 17 15:00:02 JMLinux kernel: Filesystems sync: 0.187 seconds
Oct 17 15:01:15 JMLinux kernel: Freezing user space processes
Oct 17 15:01:15 JMLinux kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Oct 17 15:01:15 JMLinux kernel: OOM killer disabled.
Oct 17 15:01:15 JMLinux kernel: Freezing remaining freezable tasks
Oct 17 15:01:15 JMLinux kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Oct 17 15:01:15 JMLinux kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Oct 17 15:01:15 JMLinux kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Oct 17 15:01:15 JMLinux kernel: sd 0:0:0:0: [sda] Stopping disk
Oct 17 15:01:15 JMLinux kernel: intel_pch_thermal 0000:00:12.0: CPU-PCH is cool [36C]
Oct 17 15:01:15 JMLinux kernel: pci 0000:04:00.0: Unable to change power state from unknown to D0, device inaccessible
Oct 17 15:01:15 JMLinux kernel: pcieport 0000:00:1b.0: broken device, retraining non-functional downstream link at 2.5GT/s
Oct 17 15:01:15 JMLinux kernel: pcieport 0000:00:1b.0: retraining failed
Oct 17 15:01:15 JMLinux kernel: pcieport 0000:00:1b.0: broken device, retraining non-functional downstream link at 2.5GT/s
Oct 17 15:01:15 JMLinux kernel: pcieport 0000:00:1b.0: retraining failed
Oct 17 15:01:15 JMLinux kernel: nvme 0000:03:00.0: not ready 1023ms after resume; waiting
Oct 17 15:01:15 JMLinux kernel: nvme 0000:03:00.0: not ready 2047ms after resume; waiting
Oct 17 15:01:15 JMLinux kernel: nvme 0000:03:00.0: not ready 4095ms after resume; waiting
Oct 17 15:01:15 JMLinux kernel: nvme 0000:03:00.0: not ready 8191ms after resume; waiting
Oct 17 15:01:15 JMLinux kernel: nvme 0000:03:00.0: not ready 16383ms after resume; waiting
Oct 17 15:01:15 JMLinux kernel: nvme 0000:03:00.0: not ready 32767ms after resume; waiting
Oct 17 15:01:15 JMLinux kernel: nvme 0000:03:00.0: not ready 65535ms after resume; giving up
Oct 17 15:01:15 JMLinux kernel: nvme 0000:03:00.0: Unable to change power state from D3cold to D0, device inaccessible
Oct 17 15:01:15 JMLinux kernel: nvme 0000:03:00.0: Unable to change power state from D3cold to D0, device inaccessible
Oct 17 15:01:15 JMLinux kernel: nvme nvme0: Disabling device after reset failure: -19
Oct 17 15:01:15 JMLinux kernel: nvme nvme1: Shutdown timeout set to 8 seconds
Oct 17 15:01:15 JMLinux kernel: nvme nvme1: 12/0/0 default/read/poll queues
Oct 17 15:01:15 JMLinux kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 17 15:01:15 JMLinux kernel: ata3: SATA link down (SStatus 4 SControl 300)
Oct 17 15:01:15 JMLinux kernel: ata2: SATA link down (SStatus 4 SControl 300)
Oct 17 15:01:15 JMLinux kernel: ata4: SATA link down (SStatus 4 SControl 300)
Oct 17 15:01:15 JMLinux kernel: OOM killer enabled.
Oct 17 15:01:15 JMLinux rtkit-daemon[1267]: The canary thread is apparently starving. Taking action.
Oct 17 15:01:15 JMLinux rtkit-daemon[1267]: Demoting known real-time threads.
Oct 17 15:01:15 JMLinux rtkit-daemon[1267]: Demoted 0 threads.
Oct 17 15:01:15 JMLinux kernel: Restarting tasks ... done.
Oct 17 15:01:15 JMLinux kernel: random: crng reseeded on system resumption
Oct 17 15:01:15 JMLinux systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Oct 17 15:01:15 JMLinux systemd-sleep[3004]: System returned from sleep state.
Oct 17 15:01:15 JMLinux bluetoothd[793]: Controller resume with wake event 0x0
Oct 17 15:01:15 JMLinux kernel: PM: suspend exit
Oct 17 15:01:15 JMLinux surfsharkd.js[1790]: JS LOG: Error: Parsing Error: Invalid arguments: 
Oct 17 15:01:15 JMLinux surfsharkd.js[1790]: {"event":"update","state":{"network_manager_state":10,"openvpn_vpn_state":0,"openvpn_vpn_reason":0,"openvpn_active_connection_state":4,"openvpn_active_connection_reason":0,"wg_active_connection_state":4,"wg_active_connection_reason":0,"user_locked":false,"current_physical_connection":null}}
Oct 17 15:01:16 JMLinux systemd[1]: systemd-suspend.service: Deactivated successfully.
Oct 17 15:01:16 JMLinux systemd[1]: Finished System Suspend.
Oct 17 15:01:16 JMLinux systemd[1]: Stopped target Sleep.
Oct 17 15:01:16 JMLinux systemd[1]: Reached target Suspend.
Oct 17 15:01:16 JMLinux systemd-logind[803]: Operation 'sleep' finished.
Oct 17 15:01:16 JMLinux NetworkManager[849]: <info>  [1697565676.1666] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Oct 17 15:01:16 JMLinux NetworkManager[849]: <info>  [1697565676.1667] device (enp0s20f0u1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Oct 17 15:01:16 JMLinux ModemManager[874]: <msg> [sleep-monitor-systemd] system is resuming
Oct 17 15:01:16 JMLinux kdeconnectd[1513]: Error sending UDP packet: QAbstractSocket::NetworkError
Oct 17 15:01:16 JMLinux systemd[1]: Starting NVIDIA system resume actions...
Oct 17 15:01:16 JMLinux systemd[1]: Stopped target Suspend.
Oct 17 15:01:16 JMLinux suspend[3167]: nvidia-resume.service
Oct 17 15:01:16 JMLinux logger[3167]: <13>Oct 17 15:01:16 suspend: nvidia-resume.service
Oct 17 15:01:16 JMLinux systemd[1]: nvidia-resume.service: Deactivated successfully.
Oct 17 15:01:16 JMLinux systemd[1]: Finished NVIDIA system resume actions.
Oct 17 15:01:16 JMLinux bluetoothd[793]: Endpoint registered: sender=:1.89 path=/MediaEndpoint/A2DPSource/ldac
Oct 17 15:01:16 JMLinux bluetoothd[793]: Endpoint registered: sender=:1.89 path=/MediaEndpoint/A2DPSink/aptx_hd
Oct 17 15:01:16 JMLinux bluetoothd[793]: Endpoint registered: sender=:1.89 path=/MediaEndpoint/A2DPSource/aptx_hd
Oct 17 15:01:16 JMLinux bluetoothd[793]: Endpoint registered: sender=:1.89 path=/MediaEndpoint/A2DPSink/aptx
Oct 17 15:01:16 JMLinux bluetoothd[793]: Endpoint registered: sender=:1.89 path=/MediaEndpoint/A2DPSource/aptx
Oct 17 15:01:16 JMLinux bluetoothd[793]: Endpoint registered: sender=:1.89 path=/MediaEndpoint/A2DPSink/aac
Oct 17 15:01:16 JMLinux bluetoothd[793]: Endpoint registered: sender=:1.89 path=/MediaEndpoint/A2DPSource/aac
Oct 17 15:01:16 JMLinux bluetoothd[793]: Endpoint registered: sender=:1.89 path=/MediaEndpoint/A2DPSink/sbc
Oct 17 15:01:16 JMLinux bluetoothd[793]: Endpoint registered: sender=:1.89 path=/MediaEndpoint/A2DPSource/sbc
Oct 17 15:01:16 JMLinux bluetoothd[793]: Endpoint registered: sender=:1.89 path=/MediaEndpoint/A2DPSink/sbc_xq
Oct 17 15:01:16 JMLinux bluetoothd[793]: Endpoint registered: sender=:1.89 path=/MediaEndpoint/A2DPSource/sbc_xq
Oct 17 15:01:16 JMLinux bluetoothd[793]: Endpoint registered: sender=:1.89 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Oct 17 15:01:16 JMLinux bluetoothd[793]: Endpoint registered: sender=:1.89 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Oct 17 15:01:16 JMLinux bluetoothd[793]: Endpoint registered: sender=:1.89 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Oct 17 15:01:16 JMLinux bluetoothd[793]: Endpoint registered: sender=:1.89 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Oct 17 15:01:16 JMLinux bluetoothd[793]: Endpoint registered: sender=:1.89 path=/MediaEndpoint/A2DPSource/faststream
Oct 17 15:01:16 JMLinux bluetoothd[793]: Endpoint registered: sender=:1.89 path=/MediaEndpoint/A2DPSource/faststream_duplex
Oct 17 15:01:16 JMLinux bluetoothd[793]: Endpoint registered: sender=:1.89 path=/MediaEndpoint/A2DPSink/opus_05
Oct 17 15:01:16 JMLinux bluetoothd[793]: Endpoint registered: sender=:1.89 path=/MediaEndpoint/A2DPSource/opus_05
Oct 17 15:01:16 JMLinux bluetoothd[793]: Endpoint registered: sender=:1.89 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Oct 17 15:01:16 JMLinux bluetoothd[793]: Endpoint registered: sender=:1.89 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Oct 17 15:01:16 JMLinux NetworkManager[849]: <info>  [1697565676.4910] device (wlo1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Oct 17 15:01:16 JMLinux NetworkManager[849]: <info>  [1697565676.4914] device (p2p-dev-wlo1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Oct 17 15:01:16 JMLinux NetworkManager[849]: <info>  [1697565676.4916] manager: NetworkManager state is now DISCONNECTED

I would appreciate any help you all can provide. If I can get this fixed, I think I will finally be able to ditch windows for good.

2

Hi there, welcome to the forum.
Please check if this helps:

Create a swap partition (not zram) and configure dracut as suggested.

2 Likes
3

Thanks for the reply.

I was successful in creating a 16GB swap file using the BTRFS method, and configured the kernel parameters to see it, rebooted, confirmed it was there. Unfortunately, no change. Note as part of my troubleshooting, I had turned off deep sleep via kernel parameter as well.

As a random thought, I created a USB stick with a completely different distro (nobara) and loaded into its live mode, then tried to suspend - with the same exact behaviors. (screens go blank, keyboard and mouse RGB lighting go out, then nothing - power still runs. Hit key on keyboard and system eventually resumes as if "waking up) This also makes me think it could be something else.

4

This is an accurate description of the suspend state. If you are expecting the power to shut off, you may be thinking of hibernation which requires additional configuration.

That sounds right. It’s a resume=[UUID] kernel parameter, right?

Don’t forget to set up the dracut module. First create a config file in /etc/dracut.conf.d/:

sudo micro /etc/dracut.conf.d/resume.conf

Paste in this line to add the module:

add_dracutmodules+=" resume "

Be sure to include the spaces between the quotation marks, before and after “resume”.

Ctrl+Q to exit (be sure to save), then rebuild the initramfs:

sudo dracut-rebuild
3 Likes
5

Thanks for the reply.

When I refer to power “stays on”, I mean my system power state remains fully on, eg. fans run, front panel lights show powered on etc., not in the orange blinking “sleep” state.

I used your instructions to the letter all the same to try, with the same results. Tried both suspend and hibernate options. The difference is that with Hibernate, the system just seizes up and I have to do a hardware force shutdown.

6

Some uEFI/BIOS have Sleep State selections available–mine do. I presume you have checked that? :slight_smile:

2 Likes
7

Also make sure that “Wake on LAN” is disabled in your BIOS.

2 Likes
8

Thanks again for the replies - much appreciated.

I’ve tried using both the deep sleep states setting in UEFI and switched off entirely, and Wake on LAN is disabled.

I am no expert by any means friends - I am learning as I go and enjoying it - based on the log I pasted, I am noticing a lot of issues, for example:

Could these be causing the problem by chance?

9

Just some other ideas / possible reading-testing…
https://wiki.archlinux.org/title/Power_management/Suspend_and_hibernate#Instantaneous_wakeups_from_suspend
(talks about AMD CPUs but the temporary solution seems generic)
https://wiki.archlinux.org/title/Power_management/Wakeup_triggers#Instantaneous_wakeups_from_suspend
(linked to the above)

1 Like
11

I’m a little out of practice as I haven’t been doing a lot of support lately. However, IMO from what I suspect from your logs your suspend is being prevented by your Ethernet not being able go into suspend correctly.

It is possible Windows is causing this if you are dual booting Windows.

Are you dual booting with Windows?

If you are using Windows be sure to check that in the Device Manager’s advanced properties that any power saving options are disabled for each network adapter in use on your machine.

Be double sure WOL is disabled as @filo suggested previously.

1 Like
12

I am dual booting with Windows, yes. However, the onboard ethernet card has a fault on it that has caused it to never really work properly, and unfortunately it is an Alienware UEFI bios (I know… I am building a newer system when I can) and the option to disable the onboard ethernet is not available that I can see. I use a USB to Ethernet connection in lieu of the onboard module.

HOWEVER: I have managed to convince the system to suspend by disabling RP05 in the /proc/acpi/wakeup file – the first time only. If I try to suspend a second time without rebooting, the system will successfully power down, but will not recover from wake completely; the screens will stay black. I am thinking this may now be an NVIDIA problem?

13

To me, your logs seem to point to your Ethernet, not your Nvidia card.

14

That was my first guess as well - I did more digging and RP05 (what’s allowed me to suspend on my first attempt only) is linked to my PCI bridge, more specifically 8086:06bc (rev f0)

I’m wondering if disabling that is what’s allowing the system to suspend, but is now causing another issue entirely which makes it so my system won’t initialize video on the second wake.

15

That device is your wifi. Wifi is more commonly responsible for suspend issues, rather than Ethernet.

1 Like
16

I will check into that as well, thanks.

This is the entry I disabled in /proc/acpi/wakeup that allowed the initial suspend:

RP05      S0    *disabled  pci:0000:00:1c.0

And this is what I get from lspci -n linked to 00:1c.0:

00:1c.0 0604: 8086:06bc (rev f0)
18

The 8086 prefix is often used for Intel wifi. In this case I think 8086:06bc is more specifically the pci bridge to your wifi.

Is your bios up to date?

I posted this earlier on a late edit.

Perhaps you did not notice this. You must disable each network device in Windows from using advanced power saving options.

A test that sometimes can diagnose suspend problems is to unload your wifi/Ethernet driver and lower your network interface prior to suspending. This often allows the device to suspend correctly. It is only temporary unfortunately. To correct the issue completely a suspend/resume service can be written.

This is mostly just a workaround. Usually this is permanently fixed by a bios update or new kernel updates. You will definitely want to test alternate kernels starting with the linux-mainline kernel. You should test other kernels, as well as making sure your bios is completely up to date.

2 Likes
19

Just wanted to pop up and say that you can toggle wakeup on lan and other such stuff using powertop.

sudo powertop

in terminal.

>> Disabled      Wake-on-lan status for device wlp0s20f3
Disabled      Wake status for USB device usb3
Disabled      Wake status for USB device 3-6
Disabled      Wake status for USB device usb1
Disabled      Wake status for USB device usb4
Disabled      Wake status for USB device 3-10
Disabled      Wake status for USB device usb2

Although these changes aren’t permanent you can see the command it’s using for doing the same and make it permanent if it helps.

2 Likes
20

Thanks, I’m going to start testing with other kernels next.

I also triple checked and power management is indeed off in Device Manager. (note the only reason I’m keeping dual boot for now is so i have a failsafe incase my linux experiment crashes and burns haha)
As an update, I temporarily unloaded both the wifi and ethernet as a test on boot using a blacklist in modprobe.d but continue to have the same sleep issues. The KDE session seems to completely start fresh when the system resumes from its failed “sleep”.

I ran journalctl -b again and found this:

Oct 18 12:41:40 JMLinux kernel: intel_pch_thermal 0000:00:12.0: CPU-PCH is cool [35C]
Oct 18 12:41:40 JMLinux kernel: pci 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible
Oct 18 12:41:40 JMLinux kernel: nvme nvme1: Shutdown timeout set to 8 seconds
Oct 18 12:41:40 JMLinux kernel: nvme nvme1: 12/0/0 default/read/poll queues
Oct 18 12:41:40 JMLinux kernel: ata4: SATA link down (SStatus 4 SControl 300)
Oct 18 12:41:40 JMLinux kernel: ata2: SATA link down (SStatus 4 SControl 300)
Oct 18 12:41:40 JMLinux kernel: ata3: SATA link down (SStatus 4 SControl 300)
Oct 18 12:41:40 JMLinux kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 18 12:41:40 JMLinux kernel: OOM killer enabled.
Oct 18 12:41:40 JMLinux kernel: Restarting tasks ... done.

pci 4 is that blasted faulty Ethernet controller, as listed in lspci:

04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Killer E3000 2.5GbE Controller (rev 03)
Subsystem: Dell Killer E3000 2.5GbE Controller
!!! Unknown header type 7f
I/O ports at 3000 [size=256]
Memory at a1100000 (64-bit, non-prefetchable) [size=64K]
Memory at a1110000 (64-bit, non-prefetchable) [size=16K]
Kernel modules: r8169

which tells me using blacklist for that purpose did nothing at all. I’m fairly convinced that stupid onboard ethernet is at fault, but the bios on this thing won’t let me disable it.

21

Thanks for the powertop suggestion, I tried disabling USB wake but as I suspected all that did was make me have to hit the power button to resume from “sleep” (which i’ve established is the system just sitting there burning power with fans, lights etc while it “sleeps”)

Appreciate everyone’s help here btw. I think I’ve narrowed it down to this faulty ethernet controller - I just need some way to make it so linux can’t see it period.

EDIT: I wonder if it could potentially be an issue with this bridge as well - recall that when I disabled the wakeup on this device as I will list below from lspci, sleep would successfully complete on first activation, then fail to reinit video on the second successful sleep.

00:1c.0 PCI bridge: Intel Corporation Device 06bc (rev f0) (prog-if 00 [Normal decode])
Subsystem: Dell Device 09a3
Flags: bus master, fast devsel, latency 0, IRQ 124
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
I/O behind bridge: 3000-3fff [size=4K] [16-bit]
Memory behind bridge: a1100000-a11fffff [size=1M] [32-bit]
Prefetchable memory behind bridge: [disabled] [64-bit]
Capabilities: <access denied>
Kernel driver in use: pcieport
22

I didn’t see the answer to @tbg’s uEFI/BIOS being up-to-date question. Yours is dated July, and Dell is pretty good at promptly issuing updates on machines, and it has been my experience with Dell that the latest machines receive them the most. It wouldn’t surprise me if there might be one pending? BIOS updates, as you’re probably already aware, are made in regard to a machine’s hardware. Best of luck! :slight_smile:

1 Like