Fedora was working fine on my laptop during the initial month but as of now, if my system goes to suspend it can’t resume. When I shut down it shows the following log and in both cases, I have to force shutdown by pressing the power button.
Have you tried getting a terminal (<ctrl-alt F3>, etc.) or connection with SSH from another system to see if it is the kernel that crashed or just a subsystem? What changed (kernel update, etc.)?
From the information so far, this could be a power management issue with the USB controller. The journal should provide some insight – search for ACPI messages and also the low numbered priority messages.
As the laptop is frozen and the screen is black,<ctrl-alt F3> doesn’t work. Using SSH, the connection is lost as soon as I try to resume from suspended state.
Here is the following log for when I go to suspend and try to resume from it, got it from journalctl -b -1
It looks like the problem is with enterng sleep. Here (old iMac)
Oct 09 19:20:06 <hostname> systemd-sleep[7176]: Entering sleep state 'suspend'...
Oct 09 19:20:06 <hostname> kernel: PM: suspend entry (deep)
Oct 10 15:25:04 <hostname> kernel: Filesystems sync: 0.106 seconds
Oct 10 15:25:04 <hostname> kernel: Freezing user space processes
Oct 10 15:25:04 <hostname> kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Oct 10 15:25:04 <hostname> kernel: OOM killer disabled.
Oct 10 15:25:04 <hostname> kernel: Freezing remaining freezable tasks
Oct 10 15:25:04 <hostname> kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Oct 10 15:25:04 <hostname> kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Oct 10 15:25:04 <hostname> kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Oct 10 15:25:04 <hostname> kernel: sd 4:0:0:0: [sdb] Synchronizing SCSI cache
Oct 10 15:25:04 <hostname> kernel: sd 5:0:0:0: [sdc] Synchronizing SCSI cache
Oct 10 15:25:04 <hostname> kernel: sd 0:0:0:0: [sda] Stopping disk
Oct 10 15:25:04 <hostname> kernel: sd 4:0:0:0: [sdb] Stopping disk
Oct 10 15:25:04 <hostname> kernel: ERROR @wl_notify_scan_status :
Oct 10 15:25:04 <hostname> kernel: wlp3s0 Scan_results error (-22)
Oct 10 15:25:04 <hostname> kernel: PM: suspend devices took 1.017 seconds
Oct 10 15:25:04 <hostname> kernel: ACPI: EC: interrupt blocked
Oct 10 15:25:04 <hostname> kernel: ACPI: PM: Preparing to enter system sleep state S3
Oct 10 15:25:04 <hostname> kernel: ACPI: EC: event blocked
Oct 10 15:25:04 <hostname> kernel: ACPI: EC: EC stopped
Oct 10 15:25:04 <hostname> kernel: ACPI: PM: Saving platform NVS memory
Oct 10 15:25:04 <hostname> kernel: Disabling non-boot CPUs ...
Oct 10 15:25:04 <hostname> kernel: smpboot: CPU 1 is now offline
Oct 10 15:25:04 <hostname> kernel: smpboot: CPU 2 is now offline
Oct 10 15:25:04 <hostname> kernel: smpboot: CPU 3 is now offline
[I assume the clock is not yet reset when resume begins]
Oct 10 15:25:04 <hostname> kernel: ACPI: PM: Low-level resume complete
Oct 10 15:25:04 <hostname> kernel: ACPI: EC: EC started
Oct 10 15:25:04 <hostname> kernel: ACPI: PM: Restoring platform NVS memory
Oct 10 15:25:04 <hostname> kernel: Enabling non-boot CPUs ...
Oct 10 15:25:04 <hostname> kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Oct 10 15:25:04 <hostname> kernel: CPU1 is up
Oct 10 15:25:04 <hostname> kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
[more resuming, clock get reset to proper time]
There are some errors preceeding the systemd-sleep entry. Sleep is complicated due to the wide variety of use cases and hardware. There are lots of configuration options in linux, and support for sleep is evolving. You may find useful options for similar hardware in forums for other distros. You should make sure Fedora is fully updated (including vendor firmware for all devices) so others with the same hardware can try to reproduce the problem.
