I can't suspend my laptop

Ask Fedora
, ,
1

When I try to systemctl suspend, my laptop goes to suspend mode and resume immediately after.

Here’s the output of dmesg:

[   66.963455] PM: suspend entry (s2idle)
[   67.031124] Filesystems sync: 0.067 seconds
[   67.175783] Freezing user space processes ... (elapsed 0.001 seconds) done.
[   67.177524] OOM killer disabled.
[   67.177524] Freezing remaining freezable tasks ... (elapsed 0.007 seconds) done.
[   67.184922] printk: Suspending console(s) (use no_console_suspend to debug)
[   67.192813] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[   67.193015] sd 0:0:0:0: [sda] Stopping disk
[   67.361155] e1000e: EEE TX LPI TIMER: 00000011
[   68.528287] PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0xd20 [e1000e] returns -2
[   68.528334] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -2
[   68.528355] e1000e 0000:00:19.0: PM: failed to suspend async: error -2
[   68.528429] PM: Some devices failed to suspend, or early wake event detected
[   68.538931] sd 0:0:0:0: [sda] Starting disk
[   68.541710] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
[   68.834897] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
[   68.854566] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   68.854602] ata2: SATA link down (SStatus 0 SControl 300)
[   68.854645] ata5: SATA link down (SStatus 0 SControl 300)
[   68.855530] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[   68.855536] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[   68.855538] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[   68.855617] ata1.00: supports DRM functions and may not be fully accessible
[   68.856368] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[   68.856374] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[   68.856376] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[   68.856450] ata1.00: supports DRM functions and may not be fully accessible
[   68.856966] ata1.00: configured for UDMA/133
[   69.034969] PM: resume devices took 0.507 seconds
[   69.034977] OOM killer enabled.
[   69.034978] Restarting tasks ... done.
[   69.065154] PM: suspend exit
[   69.923455] e1000e 0000:00:19.0 eth0: Hardware Error
[   70.235075] e1000e 0000:00:19.0 eth0: NIC Link is Down
[   71.109910] e1000e 0000:00:19.0 eth0: Hardware Error
[   72.058754] e1000e 0000:00:19.0 eth0: NIC Link is Up 10 Mbps Half Duplex, Flow Control: None
[   72.058762] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
[   72.266120] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   74.848305] e1000e 0000:00:19.0 eth0: NIC Link is Down
[   75.677360] wlan0: authenticate with e4:bf:fa:88:69:16
[   75.679539] wlan0: send auth to e4:bf:fa:88:69:16 (try 1/3)
[   75.758745] wlan0: authenticated
[   75.759635] wlan0: associate with e4:bf:fa:88:69:16 (try 1/3)
[   75.760587] wlan0: RX AssocResp from e4:bf:fa:88:69:16 (capab=0x1011 status=0 aid=24)
[   75.762942] wlan0: associated
[   76.115207] wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by e4:bf:fa:88:69:16
[   76.127319] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   76.892528] e1000e 0000:00:19.0 eth0: PHY Wakeup cause - Unicast Packet
[   77.671525] e1000e 0000:00:19.0 eth0: Hardware Error

Any idea what could prevent it to suspend? Thanks.

1 Like
2

Maybe try it with this so you can get more debug output. It looks as though Suspend is getting interrupted by a early wake event or just some process failing to suspend.

3

Where do I put no_console_suspend?

4

You would use it with the suspend command like systemctl suspend no_console_suspend and this should still provide output while suspending and the log should still have info for you to debug with. AFATG you could also try journalctl -b --priority=3 | grep suspend to see if the journal since boot has any errors related to suspend.