Laptop immediately resumes after suspending

divyanshu1234 · July 6, 2020, 5:46pm

I have an ASUS ROG Strix Scar 3:
1 TB SSD
NVIDIA GTX 1660

I installed Fedora 32 today, and I am having problems trying to suspend it. Whenever I try to do so, it immediately resumes and shows the lock screen. I tried changing my GRUB configs. But nothing worked.

Any kind of help will be appreciated.

My GRUB config file:

GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet"
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG=true

tachi · July 7, 2020, 5:01pm

Try to turn fastboot off in your BIOS.
If you have dual boot system with Windows 10 you can also turn it off in Additional power settings > Choose what the power buttons do. Untick the box at Turn on fast startup.

divyanshu1234 · July 7, 2020, 8:33pm

I had already done that as fast boot would prevent me from mounting other partition in Fedora. It is still resuming after suspending.

Could it be that I have 16 GB RAM and only 8 GB of swap memory?

stippi · July 9, 2020, 8:24am

@divyanshu1234:
Yes of course it’s possible to have less swap than RAM like on my system:

~$ free -h
total used free shared buff/cache available
Mem: 15Gi 2,8Gi 9Gi 820Mi 2,7Gi 11Gi
Swap: 7,8Gi 0B 7,8Gi

But this shouldn’t affect suspend from my p.o.v.

Greetings
stippi

divyanshu1234 · July 9, 2020, 10:17am

Here are my logs:

Jul 09 15:42:03 LAPTOP-RUL9M0JJ systemd-logind[1011]: Operation 'sleep' finished.
Jul 09 15:42:03 LAPTOP-RUL9M0JJ systemd[1]: Stopped target Sleep.
Jul 09 15:42:03 LAPTOP-RUL9M0JJ audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/>
Jul 09 15:42:03 LAPTOP-RUL9M0JJ systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
Jul 09 15:42:03 LAPTOP-RUL9M0JJ systemd[1]: Dependency failed for Suspend.
Jul 09 15:42:03 LAPTOP-RUL9M0JJ systemd[1]: Failed to start Suspend.
Jul 09 15:42:03 LAPTOP-RUL9M0JJ systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
Jul 09 15:42:03 LAPTOP-RUL9M0JJ systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
Jul 09 15:42:03 LAPTOP-RUL9M0JJ systemd-sleep[5293]: Failed to suspend system. System resumed again: Connection timed out
Jul 09 15:42:03 LAPTOP-RUL9M0JJ kernel: PM: suspend exit
Jul 09 15:42:03 LAPTOP-RUL9M0JJ NetworkManager[1030]: <info>  [1594289523.3081] device (wlo1): supplicant interface state: disconnected -> scanning
Jul 09 15:42:03 LAPTOP-RUL9M0JJ kernel: Restarting tasks ... done.
Jul 09 15:42:03 LAPTOP-RUL9M0JJ wpa_supplicant[1156]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=WORLD
Jul 09 15:42:03 LAPTOP-RUL9M0JJ kernel: OOM killer enabled.
Jul 09 15:42:03 LAPTOP-RUL9M0JJ kernel: PM: resume devices took 0.223 seconds
Jul 09 15:42:03 LAPTOP-RUL9M0JJ kernel: PM: Some devices failed to suspend, or early wake event detected
Jul 09 15:42:03 LAPTOP-RUL9M0JJ kernel: ata1: SATA link down (SStatus 4 SControl 300)
Jul 09 15:42:03 LAPTOP-RUL9M0JJ kernel: PM: Device 0000:01:00.2 failed to suspend async: error -110
Jul 09 15:42:03 LAPTOP-RUL9M0JJ kernel: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -110
Jul 09 15:42:03 LAPTOP-RUL9M0JJ kernel: PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -110
Jul 09 15:42:03 LAPTOP-RUL9M0JJ kernel: PM: suspend_common(): xhci_pci_suspend+0x0/0x100 returns -110
Jul 09 15:42:03 LAPTOP-RUL9M0JJ kernel: xhci_hcd 0000:01:00.2: WARN: xHC CMD_RUN timeout
Jul 09 15:42:03 LAPTOP-RUL9M0JJ kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jul 09 15:42:03 LAPTOP-RUL9M0JJ kernel: Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done.
Jul 09 15:42:03 LAPTOP-RUL9M0JJ kernel: OOM killer disabled.
Jul 09 15:42:03 LAPTOP-RUL9M0JJ kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.
Jul 09 15:42:02 LAPTOP-RUL9M0JJ kernel: Filesystems sync: 0.006 seconds
Jul 09 15:42:02 LAPTOP-RUL9M0JJ kernel: PM: suspend entry (s2idle)
Jul 09 15:42:02 LAPTOP-RUL9M0JJ kernel: PM: suspend exit
Jul 09 15:42:02 LAPTOP-RUL9M0JJ gnome-shell[1906]: An active wireless connection, in infrastructure mode, involves no access point?
Jul 09 15:42:02 LAPTOP-RUL9M0JJ NetworkManager[1030]: <info>  [1594289522.7463] device (wlo1): supplicant interface state: completed -> disconnected
Jul 09 15:42:02 LAPTOP-RUL9M0JJ wpa_supplicant[1156]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=WORLD
Jul 09 15:42:02 LAPTOP-RUL9M0JJ wpa_supplicant[1156]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/1
Jul 09 15:42:02 LAPTOP-RUL9M0JJ NetworkManager[1030]: <warn>  [1594289522.7429] sup-iface[0x56419caa39f0,wlo1]: connection disconnected (reason -3)
Jul 09 15:42:02 LAPTOP-RUL9M0JJ wpa_supplicant[1156]: wlo1: CTRL-EVENT-DISCONNECTED bssid=94:65:2d:07:2b:71 reason=3 locally_generated=1
Jul 09 15:42:02 LAPTOP-RUL9M0JJ kernel: Restarting tasks ... done.
Jul 09 15:42:02 LAPTOP-RUL9M0JJ kernel: OOM killer enabled.
Jul 09 15:42:02 LAPTOP-RUL9M0JJ kernel: acpi LNXPOWER:01: Turning OFF
Jul 09 15:42:02 LAPTOP-RUL9M0JJ kernel: acpi LNXPOWER:05: Turning OFF
Jul 09 15:42:02 LAPTOP-RUL9M0JJ kernel: PM: resume devices took 0.227 seconds
Jul 09 15:42:02 LAPTOP-RUL9M0JJ kernel: nvme nvme0: 8/0/0 default/read/poll queues
Jul 09 15:42:02 LAPTOP-RUL9M0JJ kernel: PM: Some devices failed to suspend, or early wake event detected
Jul 09 15:42:02 LAPTOP-RUL9M0JJ kernel: PM: Device 0000:01:00.2 failed to suspend async: error -110
Jul 09 15:42:02 LAPTOP-RUL9M0JJ kernel: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -110
Jul 09 15:42:02 LAPTOP-RUL9M0JJ kernel: PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -110
Jul 09 15:42:02 LAPTOP-RUL9M0JJ kernel: PM: suspend_common(): xhci_pci_suspend+0x0/0x100 returns -110
Jul 09 15:42:02 LAPTOP-RUL9M0JJ kernel: xhci_hcd 0000:01:00.2: WARN: xHC CMD_RUN timeout
Jul 09 15:42:02 LAPTOP-RUL9M0JJ kernel: wlo1: deauthenticating from 94:65:2d:07:2b:71 by local choice (Reason: 3=DEAUTH_LEAVING)
Jul 09 15:42:02 LAPTOP-RUL9M0JJ kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jul 09 15:42:02 LAPTOP-RUL9M0JJ kernel: Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done.
Jul 09 15:42:02 LAPTOP-RUL9M0JJ kernel: OOM killer disabled.
Jul 09 15:42:02 LAPTOP-RUL9M0JJ kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Jul 09 15:42:02 LAPTOP-RUL9M0JJ kernel: Filesystems sync: 0.007 seconds
Jul 09 15:42:02 LAPTOP-RUL9M0JJ kernel: PM: suspend entry (deep)
Jul 09 15:42:02 LAPTOP-RUL9M0JJ systemd-sleep[5293]: Suspending system...
Jul 09 15:42:02 LAPTOP-RUL9M0JJ systemd[1]: Starting Suspend...
Jul 09 15:42:02 LAPTOP-RUL9M0JJ systemd[1]: Reached target Sleep.
Jul 09 15:42:01 LAPTOP-RUL9M0JJ NetworkManager[1030]: <info>  [1594289521.1328] manager: NetworkManager state is now ASLEEP
Jul 09 15:42:01 LAPTOP-RUL9M0JJ NetworkManager[1030]: <info>  [1594289521.1324] device (p2p-dev-wlo1): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jul 09 15:42:01 LAPTOP-RUL9M0JJ NetworkManager[1030]: <info>  [1594289521.1121] device (eno2): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jul 09 15:42:01 LAPTOP-RUL9M0JJ NetworkManager[1030]: <info>  [1594289521.1119] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jul 09 15:42:01 LAPTOP-RUL9M0JJ kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Jul 09 15:42:01 LAPTOP-RUL9M0JJ kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Jul 09 15:42:01 LAPTOP-RUL9M0JJ kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Jul 09 15:42:01 LAPTOP-RUL9M0JJ systemd-logind[1011]: Power key pressed.

divyanshu1234 · July 9, 2020, 11:15am

So, my friend figured out that there was a problem with a USB device, an we used the following command to unbind it:

echo 0000:01:00.2 > /sys/bus/pci/devices/0000:01:00.2/driver/unbind

After this, the system is able to suspend.

The lspci -v show the following data for this device:

01:00.2 USB controller: NVIDIA Corporation TU116 USB 3.1 Host Controller (rev a1) (prog-if 30 [XHCI])
	Subsystem: ASUSTeK Computer Inc. Device 10ff
	Flags: fast devsel, IRQ 18
	Memory at a2000000 (64-bit, prefetchable) [virtual] [size=256K]
	Memory at a2040000 (64-bit, prefetchable) [virtual] [size=64K]
	Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [78] Express Endpoint, MSI 00
	Capabilities: [b4] Power Management version 3
	Capabilities: [100] Advanced Error Reporting

Does anyone have any idea what device this is?

tachi · July 9, 2020, 4:22pm

What it literally says: USB 3.1 Host Controller

Are you still able to use USB devices at SuperSpeed at 10Gbps after unbind? Not sure if it affects all USB ports or only the USB 3.0/3.1 ports.

divyanshu1234 · July 9, 2020, 7:47pm

I haven’t tried that yet. Is there a way to bind them back?