Skip to main content ↑ ↓
Topic: Suspend/hibernate doesn't resume (Read 204 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Suspend/hibernate doesn't resume

Hi. After suspending/hibernating from the DE (KDE plasma), when I try to resume using the physical power button, the machine just some log messages without proceeding to the lockscreen. I guess the messages are from /var/log/kernel.log, contents of which for the last hour I post:

Code: [Select]
Aug  8 18:09:29 artixlinux kernel: iwlwifi 0000:70:00.0: Registered PHC clock: iwlwifi-PTP, with index: 0
Aug  8 18:09:29 artixlinux kernel: alx 0000:6d:00.0 eth0: NIC Up: 1 Gbps Full
Aug  8 18:09:47 artixlinux kernel: ksplashqml[682]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
Aug  8 18:09:48 artixlinux kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Aug  8 18:12:23 artixlinux kernel: usb 1-5: 1:1: cannot get freq at ep 0x2
Aug  8 18:12:23 artixlinux kernel: usb 1-5: 1:1: cannot get freq at ep 0x2
Aug  8 18:12:23 artixlinux kernel: Bluetooth: RFCOMM TTY layer initialized
Aug  8 18:12:23 artixlinux kernel: Bluetooth: RFCOMM socket layer initialized
Aug  8 18:12:23 artixlinux kernel: Bluetooth: RFCOMM ver 1.11
Aug  8 18:12:58 artixlinux kernel: iwlwifi 0000:70:00.0: Registered PHC clock: iwlwifi-PTP, with index: 0
Aug  8 18:13:13 artixlinux kernel: usb 1-5: 1:1: cannot get freq at ep 0x2
Aug  8 18:13:13 artixlinux kernel: usb 1-5: 1:1: cannot get freq at ep 0x2
Aug  8 18:13:13 artixlinux kernel: Bluetooth: RFCOMM TTY layer initialized
Aug  8 18:13:13 artixlinux kernel: Bluetooth: RFCOMM socket layer initialized
Aug  8 18:13:13 artixlinux kernel: Bluetooth: RFCOMM ver 1.11
Aug  8 18:13:17 artixlinux kernel: ksplashqml[735]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
Aug  8 18:13:19 artixlinux kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Aug  8 18:13:47 artixlinux kernel: alx 0000:6d:00.0 eth0: Link Down
Aug  8 18:13:50 artixlinux kernel: alx 0000:6d:00.0 eth0: NIC Up: 1 Gbps Full
Aug  8 18:21:00 artixlinux kernel: alx 0000:6d:00.0 eth0: Link Down
Aug  8 18:21:03 artixlinux kernel: alx 0000:6d:00.0 eth0: NIC Up: 1 Gbps Full
Aug  8 18:21:53 artixlinux kernel: alx 0000:6d:00.0 eth0: Link Down
Aug  8 18:21:56 artixlinux kernel: alx 0000:6d:00.0 eth0: NIC Up: 1 Gbps Full
Aug  8 18:24:16 artixlinux kernel: alx 0000:6d:00.0 eth0: NIC Up: 1 Gbps Full
Aug  8 18:24:16 artixlinux kernel: iwlwifi 0000:70:00.0: Registered PHC clock: iwlwifi-PTP, with index: 0
Aug  8 18:25:16 artixlinux kernel: usb 1-5: 1:1: cannot get freq at ep 0x2
Aug  8 18:25:16 artixlinux kernel: usb 1-5: 1:1: cannot get freq at ep 0x2
Aug  8 18:25:17 artixlinux kernel: Bluetooth: RFCOMM TTY layer initialized
Aug  8 18:25:17 artixlinux kernel: Bluetooth: RFCOMM socket layer initialized
Aug  8 18:25:17 artixlinux kernel: Bluetooth: RFCOMM ver 1.11
Aug  8 18:28:52 artixlinux kernel: ksplashqml[747]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
Aug  8 18:28:54 artixlinux kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Aug  8 18:30:27 artixlinux kernel: usb 1-5: 1:1: cannot get freq at ep 0x2
Aug  8 18:30:27 artixlinux kernel: usb 1-5: 1:1: cannot get freq at ep 0x2
Aug  8 18:30:27 artixlinux kernel: Bluetooth: RFCOMM TTY layer initialized
Aug  8 18:30:27 artixlinux kernel: Bluetooth: RFCOMM socket layer initialized
Aug  8 18:30:27 artixlinux kernel: Bluetooth: RFCOMM ver 1.11
Aug  8 18:32:01 artixlinux kernel: ksplashqml[737]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
Aug  8 18:32:03 artixlinux kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Aug  8 18:44:46 artixlinux kernel: alx 0000:6d:00.0 eth0: Link Down
Aug  8 18:44:52 artixlinux kernel: alx 0000:6d:00.0 eth0: NIC Up: 1 Gbps Full
Aug  8 18:44:53 artixlinux kernel: alx 0000:6d:00.0 eth0: Link Down
Aug  8 18:44:55 artixlinux kernel: alx 0000:6d:00.0 eth0: NIC Up: 1 Gbps Full
Aug  8 18:44:56 artixlinux kernel: alx 0000:6d:00.0 eth0: Link Down
Aug  8 18:44:58 artixlinux kernel: alx 0000:6d:00.0 eth0: NIC Up: 1 Gbps Full
Please bare me as I am a newbie still learning artix. Thanks in advance.

Re: Suspend/hibernate doesn't resume

Reply #1 –
There's an error from the nvidia driver, KDE has a bad record with it. If you can't find your problem (and a fix) in the NVIDIA/Troubleshooting wiki article, you can try using different kernels (e.g. zen or lts) with nvidia-dkms or nvidia-open-dkms. If you find a combination that works, use IgnorePkg in /etc/pacman.conf to prevent related updates. Last resort is using the nouveau driver.