AMD desktop fails to suspend

Bug #1941808 reported by Jacob Abrams
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Since upgrading to 5.11.0-31-generic from 5.11.0-25-generic my system is no longer able to enter deep sleep when I choose "Suspend" from the Gnome power menu. The display goes blank for about 3 seconds and then comes back to the login screen.

Machine setup:

Desktop PC
Ubuntu 21.04
Linux version 5.11.0-17-generic
AMD Ryzen 3900X
Asus X590 PRIME PRO motherboard
NVIDIA P400 GPU

The following appears in dmesg:

[ 193.035190] PM: suspend entry (deep)
[ 193.043644] Filesystems sync: 0.008 seconds
[ 193.221385] rfkill: input handler enabled
[ 193.223342] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 193.225169] OOM killer disabled.
[ 193.225170] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 193.226377] printk: Suspending console(s) (use no_console_suspend to debug)
[ 193.227086] serial 00:04: disabled
[ 193.236938] PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16
[ 193.236948] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -16
[ 193.236955] PM: Device 0000:0b:00.3 failed to suspend async: error -16
[ 193.433850] PM: Some devices failed to suspend, or early wake event detected
[ 193.434781] serial 00:04: activated
[ 193.439638] nvme nvme1: Shutdown timeout set to 8 seconds
[ 193.441267] nvme nvme0: 32/0/0 default/read/poll queues
[ 193.467431] nvme nvme1: 32/0/0 default/read/poll queues
[ 193.729944] usb 5-2.3: reset high-speed USB device number 3 using xhci_hcd
[ 193.746614] ata1: SATA link down (SStatus 0 SControl 300)
[ 193.746619] ata2: SATA link down (SStatus 0 SControl 300)
[ 193.864008] OOM killer enabled.
[ 193.864009] Restarting tasks ... done.
[ 193.865012] PM: suspend exit
[ 193.865069] PM: suspend entry (s2idle)
[ 193.869519] Filesystems sync: 0.004 seconds
[ 193.907792] Freezing user space processes ... (elapsed 0.007 seconds) done.
[ 193.915352] OOM killer disabled.
[ 193.915353] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 193.916464] printk: Suspending console(s) (use no_console_suspend to debug)
[ 193.917046] serial 00:04: disabled
[ 193.925345] PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16
[ 193.925355] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -16
[ 193.925362] PM: Device 0000:0b:00.3 failed to suspend async: error -16
[ 194.118212] PM: Some devices failed to suspend, or early wake event detected
[ 194.119120] serial 00:04: activated
[ 194.123827] nvme nvme1: Shutdown timeout set to 8 seconds
[ 194.126322] nvme nvme0: 32/0/0 default/read/poll queues
[ 194.150499] nvme nvme1: 32/0/0 default/read/poll queues
[ 194.413459] usb 5-2.3: reset high-speed USB device number 3 using xhci_hcd
[ 194.434238] ata2: SATA link down (SStatus 0 SControl 300)
[ 194.434256] ata1: SATA link down (SStatus 0 SControl 300)
[ 194.547373] OOM killer enabled.
[ 194.547374] Restarting tasks ... done.
[ 194.548195] PM: suspend exit
[ 194.694550] rfkill: input handler disabled

I see pci device mentioned is:

0b:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-image-5.11.0-31-generic 5.11.0-31.33
ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
Uname: Linux 5.11.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: jacob 2034 F.... pulseaudio
 /dev/snd/controlC0: jacob 2034 F.... pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 26 16:57:09 2021
InstallationDate: Installed on 2020-10-28 (302 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
 lo no wireless extensions.

 enp5s0 no wireless extensions.

 docker0 no wireless extensions.
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic root=UUID=f721d5df-ceec-434a-919a-0680ee380996 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-31-generic N/A
 linux-backports-modules-5.11.0-31-generic N/A
 linux-firmware 1.197.3
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to hirsute on 2021-05-14 (104 days ago)
dmi.bios.date: 08/09/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4021
dmi.board.asset.tag: Default string
dmi.board.name: PRIME X570-PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Jacob Abrams (satur9nine) wrote :
Revision history for this message
Jacob Abrams (satur9nine) wrote :

Actually it appears that one usb device was the source of the problem. It's not a common USB device so it's not likely worth fixing.

Bus 005 Device 003: ID 28f3:4000 Clover Network, Inc. Flex

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Alex Hung (alexhung) wrote :

In this case, you can disable USB wakeup if you don't need USB wakeup.

A quick search finds an tutorial: http://www.das-werkstatt.com/forum/werkstatt/viewtopic.php?f=7&t=1985

Revision history for this message
Mario Limonciello (superm1) wrote :

S2idle was not really functional on older kernels anyway. It doesn't start working properly until about 5.14.

So can you please retry with one and if it persists update the issue?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
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.