Bug 216027 - ACPI TAD driver prevents suspend deep failure at first try - AMD Ryzen 4600H Renoir 16 Go
Summary: ACPI TAD driver prevents suspend deep failure at first try - AMD Ryzen 4600H ...
Status: NEW
Alias: None
Product: ACPI
Classification: Unclassified
Component: Power-Sleep-Wake (show other bugs)
Hardware: AMD Linux
: P1 normal
Assignee: acpi_power-sleep-wake
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-25 11:24 UTC by Christian Casteyde
Modified: 2022-06-27 04:12 UTC (History)
1 user (show)

See Also:
Kernel Version: 5.18.0
Subsystem:
Regression: No
Bisected commit-id:

Attachments
dmesg for 5.18 first deep suspend failure after boot (4.21 KB, text/plain)
2022-05-25 11:24 UTC, Christian Casteyde 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Christian Casteyde 2022-05-25 11:24:31 UTC 
Created attachment 301042 [details]
dmesg for 5.18 first deep suspend failure after boot

HP Pavilion Gaming 15-en1096nf, Slackware64 15
Kernel 5.18.0 (but problem present before)
AMD Ryzen 4600H Renoir 16 Go + AMD APU + NVidia GTX1650Ti (unused, no driver)

After boot, the first suspend request (echo "mem" > /sys/power/state) fails if the ACPI TAD driver is loader. This request succeeds if TAD is not loaded.

For reference, seen while analyzing https://gitlab.freedesktop.org/drm/amd/-/issues/2023

With PM debug option activated, every call returns 0:
[   77.597010] PM: suspend of devices complete after 281.660 msecs
[   77.597019] PM: start suspend of devices complete after 281.924 msecs
[   77.597464] snd_hda_intel 0000:01:00.1: PM: calling pci_pm_suspend_late+0x0/0x30 @ 2447, parent: 0000:00:01.1
[   77.597478] snd_hda_intel 0000:01:00.1: PM: pci_pm_suspend_late+0x0/0x30 returned 0 after 1 usecs
[   77.597487] i2c_hid_acpi i2c-ELAN0718:00: PM: calling acpi_subsys_suspend_late+0x0/0x50 @ 2447, parent: i2c-0
[   77.597488] acpi-tad ACPI000E:00: PM: calling acpi_subsys_suspend_late+0x0/0x50 @ 886, parent: platform
[   77.597495] i2c_hid_acpi i2c-ELAN0718:00: PM: acpi_subsys_suspend_late+0x0/0x50 returned 0 after 1 usecs
[   77.597562] acpi-tad ACPI000E:00: PM: acpi_subsys_suspend_late+0x0/0x50 returned 0 after 62 usecs
[   77.597570] acpi-wmi PNP0C14:00: PM: calling acpi_subsys_suspend_late+0x0/0x50 @ 886, parent: platform
[   77.597574] acpi-wmi PNP0C14:00: PM: acpi_subsys_suspend_late+0x0/0x50 returned 0 after 0 usecs
[   77.597684] acpi-wmi PNP0C14:00: PM: calling acpi_subsys_resume_early+0x0/0x50 @ 886, parent: platform
[   77.597685] i2c_hid_acpi i2c-ELAN0718:00: PM: calling acpi_subsys_resume_early+0x0/0x50 @ 2447, parent: i2c-0
[   77.597690] acpi-wmi PNP0C14:00: PM: acpi_subsys_resume_early+0x0/0x50 returned 0 after 0 usecs
[   77.597686] snd_hda_intel 0000:01:00.1: PM: calling pci_pm_resume_early+0x0/0x20 @ 2459, parent: 0000:00:01.1
[   77.597695] acpi-tad ACPI000E:00: PM: calling acpi_subsys_resume_early+0x0/0x50 @ 886, parent: platform
[   77.597695] i2c_hid_acpi i2c-ELAN0718:00: PM: acpi_subsys_resume_early+0x0/0x50 returned 0 after 0 usecs
[   77.597700] acpi-tad ACPI000E:00: PM: acpi_subsys_resume_early+0x0/0x50 returned 0 after 0 usecs
[   77.597699] snd_hda_intel 0000:01:00.1: PM: pci_pm_resume_early+0x0/0x20 returned 0 after 0 usecs
[   77.597809] PM: early resume of devices complete after 0.177 msecs
[   77.597814] PM: late suspend of devices aborted after 0.790 msecs
[   77.597817] PM: late suspend of devices failed
Note You need to log in before you can comment on or make changes to this bug.