Suspend - takes 30 seconds to fully suspend

Bug #1898421 reported by Sebastian Cherek
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Using `systemctl suspend` or suspending through the power menu takes 30 seconds for the system to fully suspend.

Expected:
The system suspends in under 2 seconds (e.g. check Arch Linux)
Actual:
The system takes 30 seconds to suspend (31.44 seconds using a stopwatch)

Description: Ubuntu 20.04.1 LTS
Release: 20.04
Codename: focal

DMESG:
[ 8521.093270] PM: suspend entry (deep)
[ 8521.104938] Filesystems sync: 0.011 seconds
[ 8521.182123] Freezing user space processes ... (elapsed 0.004 seconds) done.
[ 8521.187004] OOM killer disabled.
[ 8521.187005] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 8521.188754] printk: Suspending console(s) (use no_console_suspend to debug)
[ 8521.219072] sd 1:0:0:0: [sda] Synchronizing SCSI cache
[ 8521.219621] sd 1:0:0:0: [sda] Stopping disk
[ 8521.958776] ACPI: Preparing to enter system sleep state S3
[ 8521.960793] PM: Saving platform NVS memory
[ 8521.961025] Disabling non-boot CPUs ...
[ 8521.961558] IRQ 26: no longer affine to CPU1
[ 8521.962593] smpboot: CPU 1 is now offline
[ 8521.964649] IRQ 18: no longer affine to CPU2
[ 8521.965669] smpboot: CPU 2 is now offline
[ 8521.967970] IRQ 27: no longer affine to CPU3
[ 8521.968991] smpboot: CPU 3 is now offline
[ 8521.970958] ACPI: Low-level resume complete
[ 8521.970958] PM: Restoring platform NVS memory
[ 8521.976827] Enabling non-boot CPUs ...
[ 8521.976893] x86: Booting SMP configuration:
[ 8521.976894] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 8521.983510] CPU1 is up
[ 8521.983545] smpboot: Booting Node 0 Processor 2 APIC 0x3
[ 8521.990199] CPU2 is up
[ 8521.990234] smpboot: Booting Node 0 Processor 3 APIC 0x1
[ 8521.996937] CPU3 is up
[ 8521.999566] ACPI: Waking up from system sleep state S3
[ 8522.039068] usb usb3: root hub lost power or was reset
[ 8522.039085] usb usb4: root hub lost power or was reset
[ 8522.039093] usb usb5: root hub lost power or was reset
[ 8522.039149] usb usb6: root hub lost power or was reset
[ 8522.039172] usb usb7: root hub lost power or was reset
[ 8522.039207] usb usb8: root hub lost power or was reset
[ 8522.046933] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0
[ 8522.053105] [drm] PCIE GART of 1024M enabled (table at 0x0000000000162000).
[ 8522.053201] radeon 0000:01:00.0: WB enabled
[ 8522.053204] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0x000000002d5e699f
[ 8522.053207] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0x000000006b3686a1
[ 8522.053999] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0x00000000556b4497
[ 8522.054407] sd 1:0:0:0: [sda] Starting disk
[ 8522.070310] [drm] ring test on 0 succeeded in 2 usecs
[ 8522.070320] [drm] ring test on 3 succeeded in 6 usecs
[ 8522.139382] mt7601u 1-5:1.0: Error: MCU response pre-completed!
[ 8522.167009] mt7601u 1-5:1.0: EEPROM ver:0c fae:00
[ 8522.246061] [drm] ring test on 5 succeeded in 2 usecs
[ 8522.246069] [drm] UVD initialized successfully.
[ 8522.246206] [drm] ib test on ring 0 succeeded in 0 usecs
[ 8522.246333] [drm] ib test on ring 3 succeeded in 0 usecs
[ 8522.372750] ata1: SATA link down (SStatus 0 SControl 300)
[ 8522.420793] ata4: SATA link down (SStatus 0 SControl 300)
[ 8522.420965] ata5: SATA link down (SStatus 0 SControl 300)
[ 8522.420984] ata6: SATA link down (SStatus 0 SControl 300)
[ 8522.421015] ata3: SATA link down (SStatus 0 SControl 300)
[ 8522.534422] usb 4-2: reset low-speed USB device number 3 using uhci_hcd
[ 8522.586417] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 8522.589674] ata2.00: configured for UDMA/133
[ 8522.589762] ata2.00: Enabling discard_zeroes_data
[ 8522.910492] [drm] ib test on ring 5 succeeded
[ 8523.114411] usb 4-1: reset low-speed USB device number 2 using uhci_hcd
[ 8523.467722] OOM killer enabled.
[ 8523.467723] Restarting tasks ...
[ 8523.469565] pci 0000:00:1e.0: PCI bridge to [bus 03]
[ 8523.469623] pci 0000:00:1e.0: PCI bridge to [bus 03]
[ 8523.469671] pci 0000:00:1e.0: PCI bridge to [bus 03]
[ 8523.469723] pci 0000:00:1e.0: PCI bridge to [bus 03]
[ 8523.469769] pci 0000:00:1e.0: PCI bridge to [bus 03]
[ 8523.469816] pci 0000:00:1e.0: PCI bridge to [bus 03]
[ 8523.486043] rfkill: input handler enabled
[ 8523.494520] done.
[ 8523.496289] PM: suspend exit
[ 8523.511552] rfkill: input handler disabled
[ 8541.280829] check: Corrupted low memory at 00000000de236a5f (c6e8 phys) = 400000000000

Tags: focal
Revision history for this message
Sebastian Cherek (scherek) wrote :
Download full text (3.1 KiB)

Initial report used an old desktop, below is the output from a Renoir laptop.

[ 1134.925114] PM: suspend entry (s2idle)
[ 1134.936220] Filesystems sync: 0.011 seconds
[ 1134.936483] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 1134.938761] OOM killer disabled.
[ 1134.938762] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 1134.940031] printk: Suspending console(s) (use no_console_suspend to debug)
[ 1134.962659] sd 1:0:0:0: [sda] Synchronizing SCSI cache
[ 1134.963415] sd 1:0:0:0: [sda] Stopping disk
[ 1135.266599] [drm] free PSP TMR buffer
[ 1135.313789] ACPI: EC: interrupt blocked
[ 1135.331004] amdgpu 0000:02:00.0: refused to change power state from D0 to D3hot
[ 1135.331007] xhci_hcd 0000:02:00.4: refused to change power state from D0 to D3hot
[ 1150.496373] ACPI: EC: interrupt unblocked
[ 1150.537397] sd 1:0:0:0: [sda] Starting disk
[ 1150.556055] [drm] PCIE GART of 1024M enabled (table at 0x000000F400900000).
[ 1150.556092] [drm] PSP is resuming...
[ 1150.575984] [drm] reserve 0x400000 from 0xf41fc00000 for PSP TMR
[ 1150.848719] ata1: SATA link down (SStatus 0 SControl 300)
[ 1150.899613] amdgpu: SMU is resuming...
[ 1150.899660] amdgpu: dpm has been disabled
[ 1150.899676] amdgpu: SMU is resumed successfully!
[ 1151.011434] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1151.016213] ata2.00: configured for UDMA/133
[ 1151.144093] [drm] kiq ring mec 2 pipe 1 q 0
[ 1151.152943] [drm] DMUB hardware initialized: version=0x00000001
[ 1151.282435] [drm] Failed to add display topology, DTM TA is not initialized.
[ 1151.309163] [drm] VCN decode and encode initialized successfully(under DPG Mode).
[ 1151.309272] [drm] JPEG decode initialized successfully.
[ 1151.309578] amdgpu 0000:02:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
[ 1151.309581] amdgpu 0000:02:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[ 1151.309582] amdgpu 0000:02:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[ 1151.309584] amdgpu 0000:02:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[ 1151.309586] amdgpu 0000:02:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[ 1151.309588] amdgpu 0000:02:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[ 1151.309589] amdgpu 0000:02:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[ 1151.309591] amdgpu 0000:02:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[ 1151.309593] amdgpu 0000:02:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[ 1151.309595] amdgpu 0000:02:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
[ 1151.309596] amdgpu 0000:02:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
[ 1151.309598] amdgpu 0000:02:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
[ 1151.309600] amdgpu 0000:02:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
[ 1151.309601] amdgpu 0000:02:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
[ 1151.309603] amdgpu 0000:02:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
[ 1151.318752] OOM killer enabled.
[ 1151.318754] Restarting tasks ... done.
[ 1151.343199] PM: suspend exit
[ 1158.309787] [drm] Failed to add display topology, DTM TA is not i...

Read more...

Revision history for this message
Dan Streetman (ddstreet) wrote :

This isn't a problem with systemd, it looks like this is a problem either with your kernel drivers and/or actual hardware, e.g.:

[ 1135.331004] amdgpu 0000:02:00.0: refused to change power state from D0 to D3hot
[ 1135.331007] xhci_hcd 0000:02:00.4: refused to change power state from D0 to D3hot

affects: systemd (Ubuntu) → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1898421

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: focal
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.