Can no longer suspend
Open, Needs More InfoPublic
Actions

Assigned To

None

Authored By

	samteezy
	Jan 5 2021, 3:09 AM

Description

After the last set of updates that were synced to the repo last Friday, I can no longer suspend my PC.

I think it's related to wpa_supplicant or NetworkManager? Running

sudo gnome-logs

I see the following lines:

Failed to start Suspend.
/usr/lib64/systemd/system-sleep/wpa_supplicant.sh failed with exit status 255.
Freezing of tasks failed after 20.005 seconds (0 tasks refusing to freeze, wq_busy=1):
Failed to suspend system. System resumed again: Device or resource busy

For what it's worth, while I do have a hardware wifi antenna installed, I have wifi disabled in the NetworkManager applet since I primarily connect this desktop via Ethernet.

Event Timeline

samteezy created this task.Jan 5 2021, 3:09 AM

Herald added a project: Lacks Project. · View Herald TranscriptJan 5 2021, 3:09 AM

liontiger23 added a subscriber: liontiger23.Jan 5 2021, 5:03 PM

Is this still an issue?

just, 2 weeks ago?, started happening for me 100%, never had any issues before...

sudo journalctl -b -1
...
Aug 07 14:45:22 solus-ssd systemd[1]: Starting Suspend...
Aug 07 14:45:22 solus-ssd systemd-sleep[16288]: Failed to connect to non-global ctrl_ifname: (nil) error: No such file or directory
Aug 07 14:45:22 solus-ssd [16286]: /usr/lib64/systemd/system-sleep/wpa_supplicant.sh failed with exit status 255.
Aug 07 14:45:22 solus-ssd systemd-sleep[16285]: Suspending system...
Aug 07 14:45:22 solus-ssd kernel: PM: suspend entry (deep)
Aug 07 16:28:17 solus-ssd kernel: Freezing user space processes ... (elapsed 0.395 seconds) done.
Aug 07 16:28:25 solus-ssd kernel: OOM killer disabled.
Aug 07 16:28:25 solus-ssd kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Aug 07 16:28:25 solus-ssd kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Aug 07 16:28:25 solus-ssd kernel: e1000e: EEE TX LPI TIMER: 00000000
Aug 07 16:28:25 solus-ssd kernel: sd 3:0:0:0: [sdb] Synchronizing SCSI cache
Aug 07 16:28:25 solus-ssd kernel: sd 3:0:0:0: [sdb] Stopping disk
Aug 07 16:28:25 solus-ssd kernel: sd 2:0:0:0: [sdc] Synchronizing SCSI cache
Aug 07 16:28:25 solus-ssd kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Aug 07 16:28:25 solus-ssd kernel: sd 2:0:0:0: [sdc] Stopping disk
Aug 07 16:28:25 solus-ssd kernel: sd 0:0:0:0: [sda] Stopping disk
Aug 07 16:28:25 solus-ssd kernel: kworker/u8:25: page allocation failure: order:0, mode:0x100c02(GFP_NOIO|GFP_HIGHMEM|GFP_HARDWALL), nodemask=(null),cpuset=/,mems_allowed=0
Aug 07 16:28:25 solus-ssd kernel: CPU: 1 PID: 16323 Comm: kworker/u8:25 Not tainted 5.13.8-191.current #1
Aug 07 16:28:25 solus-ssd kernel: Hardware name: Dell Inc. Inspiron 530s/0RY007, BIOS 1.0.15 06/20/2008
Aug 07 16:28:25 solus-ssd kernel: Workqueue: events_unbound async_run_entry_fn
Aug 07 16:28:25 solus-ssd kernel: Call Trace:
Aug 07 16:28:25 solus-ssd kernel: dump_stack+0x69/0x8e
Aug 07 16:28:25 solus-ssd kernel: warn_alloc.cold+0x78/0xdc
Aug 07 16:28:25 solus-ssd kernel: alloc_pages_slowpath.constprop.0+0x945/0x980
Aug 07 16:28:25 solus-ssd kernel: alloc_pages+0x325/0x340
Aug 07 16:28:25 solus-ssd kernel: ttm_pool_alloc+0x28d/0x580 [ttm]
Aug 07 16:28:25 solus-ssd kernel: ? __vmalloc_node+0x37/0x40
Aug 07 16:28:25 solus-ssd kernel: ttm_tt_populate+0xa8/0x180 [ttm]
Aug 07 16:28:25 solus-ssd kernel: ttm_bo_handle_move_mem+0x13a/0x170 [ttm]
Aug 07 16:28:25 solus-ssd kernel: ttm_bo_evict+0x131/0x190 [ttm]
Aug 07 16:28:25 solus-ssd kernel: ? atom_execute_table_locked+0x18f/0x200 [radeon]
Aug 07 16:28:25 solus-ssd kernel: ? ttm_bo_mem_compat+0x24/0x50 [ttm]
Aug 07 16:28:25 solus-ssd kernel: ttm_mem_evict_first+0x108/0x3a0 [ttm]
Aug 07 16:28:25 solus-ssd kernel: ? radeon_dpm_change_power_state_locked+0x53/0x290 [radeon]
Aug 07 16:28:25 solus-ssd kernel: ttm_resource_manager_evict_all+0xa2/0x1c0 [ttm]
Aug 07 16:28:25 solus-ssd kernel: ? preempt_count_add+0x49/0xa0
Aug 07 16:28:25 solus-ssd kernel: radeon_suspend_kms+0x202/0x340 [radeon]
Aug 07 16:28:25 solus-ssd kernel: pci_pm_suspend+0x74/0x160
..

TClark77 added a subscriber: TClark77.Jun 12 2022, 4:25 PM

Happen for me after updating

It was mentioned on the forum that this might be related to the TLP upgrade. If you have TLP installed remove it and see if the issue persists.

To be clear, this issue is unrelated to that and you should open a new issue instead.

Yes absolutely, nothing to do with this. My apologies. Looked like a similar log in my searching.

Is this still an issue?

Can no longer suspendOpen, Needs More InfoPublicActions

Description

Event Timeline

Can no longer suspend
Open, Needs More InfoPublic
Actions