High battery drain (s0ix, Ryzen 5900HS)

@superm1

reference: #1652 (comment 1627649)

Brief summary of the problem:

With the recent kernels (I'm on 6.0.6) suspend seems pretty unstable with s0ix.

Sometimes it suspends fine and the battery loses about 1% per hour.

Sometimes it loses about 10% per hour.

My first test: 1PM - 2PM resulted in about 14% -> 13% battery

Second test: 2PM - 5PM resulted in a dead dry machine with 0%

I'm not sure how to debug as the last log entry was PM: suspend entry (s2idle).

I also can't tell since when this regression appeared. It's my spare machine and I rarely use it.

hint: the platform should be the same as in the issue linked above. The screen and dedicated GPU option might be different. But it's also a 2021 G14 (GA401QM in this case).

Hardware description:

• CPU: 5900HS
• GPU: Cezanne
• System Memory: 48GB
• Display(s): Built in 120 Hz QHD

System information:

• Distro name and Version: Fedora 37
• Kernel version: 6.0.6

hint: the platform should be the same as in the issue linked above. The screen and dedicated GPU option might be different. But it's also a 2021 G14 (GA401QM in this case).

Right - but it was a very specific failure when you can't suspend vs can't stay in the deepest state. They need to be debugged differently.

Sometimes it suspends fine and the battery loses about 1% per hour. Sometimes it loses about 10% per hour.

OK so to start out with this particular issue:

0. Make sure you're already on the latest BIOS from the OEM of your system.
1. Please pick up this patch from kernel 6.1: https://github.com/torvalds/linux/commit/cb3e7d624c3ff34a300587929c82af7364cf5c09
2. Please add the following to your kernel command line: pm_debug_messages amd_pmc.dyndbg

Then use the machine as you normally would, but take notes about different suspend cycles, what you did/didn't do differently. H ow you woke it, if you opened the lid, or unplugged the adapter etc. Try to keep track of the power consumption from that cycle as well.

We can correlate that against your logs to explain what's happening. The debug patch I suggested will allow us to understand what IRQ woke the system at any given time and the amd_pmc dynamic debugging will allow us to understand how much time was spent in the deepest sleep state.

added s0ix label

While my machine behaved normally the last 3 cycles a user (@zfarkas) in our community participates in the tests and already posted this log from an 8h suspend cycle (battery 100% -> 40%):

nov 07 21:50:02 g14 kernel: PM: suspend entry (s2idle)
nov 07 21:50:02 g14 kernel: Filesystems sync: 0.007 seconds
nov 07 21:50:02 g14 kernel: PM: Preparing system for sleep (s2idle)
nov 08 06:05:26 g14 kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
nov 08 06:05:26 g14 kernel: OOM killer disabled.
nov 08 06:05:26 g14 kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
nov 08 06:05:26 g14 kernel: PM: Suspending system (s2idle)
nov 08 06:05:26 g14 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
nov 08 06:05:26 g14 kernel: PM: suspend of devices complete after 153.444 msecs
nov 08 06:05:26 g14 kernel: PM: start suspend of devices complete after 153.588 msecs
nov 08 06:05:26 g14 kernel: PM: late suspend of devices complete after 0.598 msecs
nov 08 06:05:26 g14 kernel: ACPI: EC: interrupt blocked
nov 08 06:05:26 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 06:05:26 g14 kernel: PM: noirq suspend of devices complete after 56.463 msecs
nov 08 06:05:26 g14 kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: Constraint not met; min power state:D3hot current power state:D0
nov 08 06:05:26 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 08 06:05:26 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 08 06:05:26 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:7
nov 08 06:05:26 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 08 06:05:26 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 08 06:05:26 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:6
nov 08 06:05:26 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc00e0eb5
nov 08 06:05:26 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 08 06:05:26 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:1
nov 08 06:05:26 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
nov 08 06:05:26 g14 kernel: PM: suspend-to-idle
nov 08 06:05:26 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 08 06:05:26 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 08 06:05:26 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 08 06:05:26 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 08 06:05:26 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 06:05:26 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 08 06:05:26 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 08 06:05:26 g14 kernel: Timekeeping suspended for 50.736 seconds
nov 08 06:05:26 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 06:05:26 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 08 06:05:26 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 08 06:05:26 g14 kernel: asus_wmi: Unknown key code 0x7b
nov 08 06:05:26 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 08 06:05:26 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 08 06:05:26 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 06:05:26 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 08 06:05:26 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 08 06:05:26 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 08 06:05:26 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 08 06:05:26 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 06:05:26 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 08 06:05:26 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 08 06:05:26 g14 kernel: Timekeeping suspended for 29669.869 seconds
nov 08 06:05:26 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 06:05:26 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 08 06:05:26 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 08 06:05:26 g14 kernel: asus_wmi: Unknown key code 0xcf
nov 08 06:05:26 g14 kernel: asus_wmi: Unknown key code 0x7b
nov 08 06:05:26 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 08 06:05:26 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 08 06:05:26 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 06:05:26 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 08 06:05:26 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 08 06:05:26 g14 kernel: Timekeeping suspended for 0.863 seconds
nov 08 06:05:26 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 06:05:26 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 08 06:05:26 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 08 06:05:26 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 08 06:05:26 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 08 06:05:26 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 06:05:26 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 08 06:05:26 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 08 06:05:26 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 06:05:26 g14 kernel: PM: Triggering wakeup from IRQ 7
nov 08 06:05:26 g14 kernel: PM: Triggering wakeup from IRQ 0
nov 08 06:05:26 g14 kernel: ACPI: PM: ACPI non-EC GPE wakeup
nov 08 06:05:26 g14 kernel: PM: resume from suspend-to-idle
nov 08 06:05:26 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 08 06:05:26 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 08 06:05:26 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
nov 08 06:05:26 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 08 06:05:26 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 08 06:05:26 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:8
nov 08 06:05:26 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc00e0eb5
nov 08 06:05:26 g14 kernel: amd_pmc AMDI0005:00: Last suspend in deepest state for 49364654us
nov 08 06:05:26 g14 kernel: ACPI: EC: interrupt unblocked
nov 08 06:05:26 g14 kernel: PM: noirq resume of devices complete after 331.408 msecs
nov 08 06:05:26 g14 kernel: PM: early resume of devices complete after 0.532 msecs
nov 08 06:05:26 g14 kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
nov 08 06:05:26 g14 kernel: pci 0000:00:00.2: PCI INT A: no GSI
nov 08 06:05:26 g14 kernel: Timekeeping suspended for 0.650 seconds
nov 08 06:05:26 g14 kernel: [drm] PCIE GART of 1024M enabled.
nov 08 06:05:26 g14 kernel: [drm] PTB located at 0x000000F41FC00000
nov 08 06:05:26 g14 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
nov 08 06:05:26 g14 kernel: amdgpu 0000:04:00.0: amdgpu: dpm has been disabled
nov 08 06:05:26 g14 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
nov 08 06:05:26 g14 kernel: nvme nvme0: 8/0/0 default/read/poll queues
nov 08 06:05:26 g14 kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
nov 08 06:05:26 g14 kernel: [drm] JPEG decode initialized successfully.
nov 08 06:05:26 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
nov 08 06:05:26 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
nov 08 06:05:26 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
nov 08 06:05:26 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
nov 08 06:05:26 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
nov 08 06:05:26 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
nov 08 06:05:26 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
nov 08 06:05:26 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
nov 08 06:05:26 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
nov 08 06:05:26 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
nov 08 06:05:26 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
nov 08 06:05:26 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
nov 08 06:05:26 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
nov 08 06:05:26 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
nov 08 06:05:26 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
nov 08 06:05:26 g14 kernel: PM: resume of devices complete after 296.700 msecs
nov 08 06:05:26 g14 kernel: PM: Finishing wakeup.
nov 08 06:05:26 g14 kernel: OOM killer enabled.
nov 08 06:05:26 g14 kernel: Restarting tasks ... done.
nov 08 06:05:26 g14 kernel: random: crng reseeded on system resumption
nov 08 06:05:26 g14 kernel: PM: suspend exit

It looks like the patch is applied there.

I'm testing my machine also throughout the day today again.

Btw: are text file uploads prefered or are direct postings of log entries like this okay?

OK so from looking at this log, the SoC only spent 50 seconds of the 29669 second suspend in the deepeest state. That would definitely murder battery life.

There's a patch in 6.1 that might help debug this better. We need to find out if the idlemask changes from each wakeup to the next.

Can you please either backport it or upgrade to 6.1-rc4? https://github.com/torvalds/linux/commit/c928df03bde92d70babeb22d500f528256758aee

I'm also concerned by this:

nov 08 06:05:26 g14 kernel: asus_wmi: Unknown key code 0x7b

Those are happening on resume. Any idea what they actually mean? I wonder if the EC is expecting you to do something in asus-wmi that you're not doing.

Btw: are text file uploads prefered or are direct postings of log entries like this okay?

Either is fine.

I also got a wakeup from IRQ 9 during a shorter suspend cycle.

lid close, 1:30h suspend, 3% lost

Nov 08 08:06:01 fedora systemd-sleep[3750]: Entering sleep state 'suspend'...
Nov 08 08:06:01 fedora kernel: PM: suspend entry (s2idle)
Nov 08 08:06:01 fedora kernel: Filesystems sync: 0.025 seconds
Nov 08 08:06:01 fedora kernel: PM: Preparing system for sleep (s2idle)
Nov 08 09:38:07 fedora kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Nov 08 09:38:07 fedora kernel: OOM killer disabled.
Nov 08 09:38:07 fedora kernel: Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done.
Nov 08 09:38:07 fedora kernel: PM: Suspending system (s2idle)
Nov 08 09:38:07 fedora kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Nov 08 09:38:07 fedora kernel: queueing ieee80211 work while going to suspend
Nov 08 09:38:07 fedora kernel: PM: suspend of devices complete after 238.595 msecs
Nov 08 09:38:07 fedora kernel: PM: start suspend of devices complete after 238.856 msecs
Nov 08 09:38:07 fedora kernel: PM: suspend devices took 0.238 seconds
Nov 08 09:38:07 fedora kernel: PM: late suspend of devices complete after 0.672 msecs
Nov 08 09:38:07 fedora kernel: ACPI: EC: interrupt blocked
Nov 08 09:38:07 fedora kernel: xhci_hcd 0000:04:00.3: Refused to change power state from D0 to D3hot
Nov 08 09:38:07 fedora kernel: PM: noirq suspend of devices complete after 42.793 msecs
Nov 08 09:38:07 fedora kernel: ACPI: \_SB_.PLTF.P000: LPI: Device not power manageable
Nov 08 09:38:07 fedora kernel: ACPI: \_SB_.PLTF.P001: LPI: Device not power manageable
Nov 08 09:38:07 fedora kernel: ACPI: \_SB_.PLTF.P002: LPI: Device not power manageable
Nov 08 09:38:07 fedora kernel: ACPI: \_SB_.PLTF.P003: LPI: Device not power manageable
Nov 08 09:38:07 fedora kernel: ACPI: \_SB_.PLTF.P004: LPI: Device not power manageable
Nov 08 09:38:07 fedora kernel: ACPI: \_SB_.PLTF.P005: LPI: Device not power manageable
Nov 08 09:38:07 fedora kernel: ACPI: \_SB_.PLTF.P006: LPI: Device not power manageable
Nov 08 09:38:07 fedora kernel: ACPI: \_SB_.PLTF.P007: LPI: Device not power manageable
Nov 08 09:38:07 fedora kernel: ACPI: \_SB_.PLTF.P008: LPI: Device not power manageable
Nov 08 09:38:07 fedora kernel: ACPI: \_SB_.PLTF.P009: LPI: Device not power manageable
Nov 08 09:38:07 fedora kernel: ACPI: \_SB_.PLTF.P00A: LPI: Device not power manageable
Nov 08 09:38:07 fedora kernel: ACPI: \_SB_.PLTF.P00B: LPI: Device not power manageable
Nov 08 09:38:07 fedora kernel: ACPI: \_SB_.PLTF.P00C: LPI: Device not power manageable
Nov 08 09:38:07 fedora kernel: ACPI: \_SB_.PLTF.P00D: LPI: Device not power manageable
Nov 08 09:38:07 fedora kernel: ACPI: \_SB_.PLTF.P00E: LPI: Device not power manageable
Nov 08 09:38:07 fedora kernel: ACPI: \_SB_.PLTF.P00F: LPI: Device not power manageable
Nov 08 09:38:07 fedora kernel: ACPI: \_SB_.PCI0.GPP1: LPI: Device not power manageable
Nov 08 09:38:07 fedora kernel: ACPI: \_SB_.PCI0.GPP2: LPI: Device not power manageable
Nov 08 09:38:07 fedora kernel: ACPI: \_SB_.PCI0.GPP4: LPI: Device not power manageable
Nov 08 09:38:07 fedora kernel: ACPI: \_SB_.PCI0.GPP4.WLAN: LPI: Device not power manageable
Nov 08 09:38:07 fedora kernel: ACPI: \_SB_.PCI0.GP17.VGA_: LPI: Device not power manageable
Nov 08 09:38:07 fedora kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: Constraint not met; min power state:D3hot current power state:D0
Nov 08 09:38:07 fedora kernel: ACPI: \_SB_.PCI0.GP17.HDAU: LPI: Device not power manageable
Nov 08 09:38:07 fedora kernel: ACPI: \_SB_.PCI0.GP18.SATA: LPI: Device not power manageable
Nov 08 09:38:07 fedora kernel: ACPI: \_SB_.PCI0.GP18.SAT1: LPI: Device not power manageable
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:73f
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:9
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:ec1c8a80
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:5
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:4
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:7
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:6
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:402c00
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:2
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: SMU program 0 version is 64.44.0
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc00f0eb5
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:1
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
Nov 08 09:38:07 fedora kernel: PM: suspend-to-idle
Nov 08 09:38:07 fedora kernel: Timekeeping suspended for 5524.490 seconds
Nov 08 09:38:07 fedora kernel: PM: Triggering wakeup from IRQ 9
Nov 08 09:38:07 fedora kernel: ACPI: EC: ACPI EC GPE status set
Nov 08 09:38:07 fedora kernel: ACPI: EC: ACPI EC GPE dispatched
Nov 08 09:38:07 fedora kernel: ACPI: EC: ACPI EC work flushed
Nov 08 09:38:07 fedora kernel: ACPI: PM: Wakeup after ACPI Notify sync
Nov 08 09:38:07 fedora kernel: PM: resume from suspend-to-idle
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:8
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc00f0eb5
Nov 08 09:38:07 fedora kernel: amd_pmc AMDI0005:00: Last suspend in deepest state for 5525497467us
Nov 08 09:38:07 fedora kernel: ACPI: EC: interrupt unblocked
Nov 08 09:38:07 fedora kernel: PM: noirq resume of devices complete after 1154.689 msecs
Nov 08 09:38:07 fedora kernel: PM: early resume of devices complete after 0.392 msecs
Nov 08 09:38:07 fedora kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
Nov 08 09:38:07 fedora kernel: pci 0000:00:00.2: PCI INT A: no GSI
Nov 08 09:38:07 fedora kernel: [drm] PCIE GART of 1024M enabled.
Nov 08 09:38:07 fedora kernel: [drm] PTB located at 0x000000F41FC00000
Nov 08 09:38:07 fedora kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
Nov 08 09:38:07 fedora kernel: amdgpu 0000:04:00.0: amdgpu: dpm has been disabled
Nov 08 09:38:07 fedora kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
Nov 08 09:38:07 fedora kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Nov 08 09:38:07 fedora kernel: [drm] JPEG decode initialized successfully.
Nov 08 09:38:07 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
Nov 08 09:38:07 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Nov 08 09:38:07 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Nov 08 09:38:07 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Nov 08 09:38:07 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Nov 08 09:38:07 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Nov 08 09:38:07 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Nov 08 09:38:07 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Nov 08 09:38:07 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
Nov 08 09:38:07 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
Nov 08 09:38:07 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
Nov 08 09:38:07 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
Nov 08 09:38:07 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
Nov 08 09:38:07 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
Nov 08 09:38:07 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
Nov 08 09:38:07 fedora kernel: nvme nvme0: 16/0/0 default/read/poll queues
Nov 08 09:38:07 fedora kernel: nvme nvme0: Ignoring bogus Namespace Identifiers
Nov 08 09:38:07 fedora kernel: PM: resume of devices complete after 276.741 msecs
Nov 08 09:38:07 fedora kernel: PM: resume devices took 0.278 seconds
Nov 08 09:38:07 fedora kernel: PM: Finishing wakeup.
Nov 08 09:38:07 fedora kernel: OOM killer enabled.
Nov 08 09:38:07 fedora kernel: Restarting tasks ... done.
Nov 08 09:38:07 fedora kernel: random: crng reseeded on system resumption
Nov 08 09:38:07 fedora kernel: PM: suspend exit

I think though this log is pretty normal.

I'm not able to reproduce this issue on my end at the moment, @zfarkas's log above with the battery drain should be a bad suspend.

Could it be that IRQ 9 has something to do with the lid open event?

For me it happens once in this short period of time and it might got triggered when I opened the lid.

In @zfarkas's logs though this event gets triggered multiple times and we also see an IRQ 7 wakeup call.

According to them, their lid was open

I think though this log is pretty normal.

This one you can see that nearly the entire suspend cycle was spent in the deepest state.

Could it be that IRQ 9 has something to do with the lid open event?

Yes; IRQ 9 is the ACPI SCI, and with the lid open event you'll see it. What's most concerning is when there are events happening WITHOUT you doing power adapter or lid. That means the EC woke the system for some reason, and if you don't get back to the deepest state then something blocked it.

We can try to approach it from the patch in my other post, but if that's not helpful we will need to turn on some of the ACPI debugging layer to understand what events are coming through and being processed.

In @zfarkas's logs though this event gets triggered multiple times and we also see an IRQ 7 wakeup call.

This is the GPIO controller. It's probably from a power button press I would guess. It's not happening during the "spurious" wakes so I wouldn't be too concerned.

FYI, my lid was not closed.

Just had a 3 hours long suspend session, with minimal battery drain (I don't remember exactly, was around 35-37%, went down to 32%). I closed the lid after the laptop went to sleep.

Here are the logs:

nov 08 16:53:52 g14 kernel: PM: suspend entry (s2idle)
nov 08 16:53:52 g14 kernel: Filesystems sync: 0.006 seconds
nov 08 16:53:52 g14 kernel: PM: Preparing system for sleep (s2idle)
nov 08 19:45:21 g14 kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.
nov 08 19:45:21 g14 kernel: OOM killer disabled.
nov 08 19:45:21 g14 kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
nov 08 19:45:21 g14 kernel: PM: Suspending system (s2idle)
nov 08 19:45:21 g14 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
nov 08 19:45:21 g14 kernel: PM: suspend of devices complete after 142.960 msecs
nov 08 19:45:21 g14 kernel: PM: start suspend of devices complete after 143.163 msecs
nov 08 19:45:21 g14 kernel: PM: late suspend of devices complete after 0.634 msecs
nov 08 19:45:21 g14 kernel: ACPI: EC: interrupt blocked
nov 08 19:45:21 g14 kernel: PM: noirq suspend of devices complete after 72.912 msecs
nov 08 19:45:21 g14 kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: Constraint not met; min power state:D3hot current power state:D0
nov 08 19:45:21 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 08 19:45:21 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 08 19:45:21 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:7
nov 08 19:45:21 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 08 19:45:21 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 08 19:45:21 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:6
nov 08 19:45:21 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc00e0eb5
nov 08 19:45:21 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 08 19:45:21 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:1
nov 08 19:45:21 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
nov 08 19:45:21 g14 kernel: PM: suspend-to-idle
nov 08 19:45:21 g14 kernel: Timekeeping suspended for 3.688 seconds
nov 08 19:45:21 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 19:45:21 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 08 19:45:21 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 08 19:45:21 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 08 19:45:21 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 08 19:45:21 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 19:45:21 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 08 19:45:21 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 08 19:45:21 g14 kernel: Timekeeping suspended for 2.991 seconds
nov 08 19:45:21 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 19:45:21 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 08 19:45:21 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 08 19:45:21 g14 kernel: asus_wmi: Unknown key code 0x7b
nov 08 19:45:21 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 08 19:45:21 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 08 19:45:21 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 19:45:21 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 08 19:45:21 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 08 19:45:21 g14 kernel: Timekeeping suspended for 0.871 seconds
nov 08 19:45:21 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 19:45:21 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 08 19:45:21 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 08 19:45:21 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 08 19:45:21 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 08 19:45:21 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 19:45:21 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 08 19:45:21 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 08 19:45:21 g14 kernel: Timekeeping suspended for 10277.995 seconds
nov 08 19:45:21 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 19:45:21 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 08 19:45:21 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 08 19:45:21 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 08 19:45:21 g14 kernel: ACPI: PM: Wakeup after ACPI Notify sync
nov 08 19:45:21 g14 kernel: PM: resume from suspend-to-idle
nov 08 19:45:21 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 08 19:45:21 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 08 19:45:21 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
nov 08 19:45:21 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 08 19:45:21 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 08 19:45:21 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:8
nov 08 19:45:21 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc00f0eb5
nov 08 19:45:21 g14 kernel: amd_pmc AMDI0005:00: Last suspend in deepest state for 3461883us
nov 08 19:45:21 g14 kernel: ACPI: EC: interrupt unblocked
nov 08 19:45:21 g14 kernel: PM: noirq resume of devices complete after 333.454 msecs
nov 08 19:45:21 g14 kernel: PM: early resume of devices complete after 0.404 msecs
nov 08 19:45:21 g14 kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
nov 08 19:45:21 g14 kernel: pci 0000:00:00.2: PCI INT A: no GSI
nov 08 19:45:21 g14 kernel: [drm] PCIE GART of 1024M enabled.
nov 08 19:45:21 g14 kernel: [drm] PTB located at 0x000000F41FC00000
nov 08 19:45:21 g14 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
nov 08 19:45:21 g14 kernel: amdgpu 0000:04:00.0: amdgpu: dpm has been disabled
nov 08 19:45:21 g14 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
nov 08 19:45:21 g14 kernel: nvme nvme0: 8/0/0 default/read/poll queues
nov 08 19:45:21 g14 kernel: asus_wmi: Unknown key code 0xcf
nov 08 19:45:21 g14 kernel: asus_wmi: Unknown key code 0x7b
nov 08 19:45:21 g14 kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
nov 08 19:45:21 g14 kernel: [drm] JPEG decode initialized successfully.
nov 08 19:45:21 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
nov 08 19:45:21 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
nov 08 19:45:21 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
nov 08 19:45:21 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
nov 08 19:45:21 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
nov 08 19:45:21 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
nov 08 19:45:21 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
nov 08 19:45:21 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
nov 08 19:45:21 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
nov 08 19:45:21 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
nov 08 19:45:21 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
nov 08 19:45:21 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
nov 08 19:45:21 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
nov 08 19:45:21 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
nov 08 19:45:21 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
nov 08 19:45:21 g14 kernel: usb 1-1: reset high-speed USB device number 2 using xhci_hcd
nov 08 19:45:21 g14 kernel: usb 2-1: reset SuperSpeed USB device number 2 using xhci_hcd
nov 08 19:45:21 g14 kernel: usb 1-1.1: reset high-speed USB device number 4 using xhci_hcd
nov 08 19:45:21 g14 kernel: usb 2-1.2: reset SuperSpeed USB device number 3 using xhci_hcd
nov 08 19:45:21 g14 kernel: r8152 2-1.2:1.0: skip request firmware
nov 08 19:45:21 g14 kernel: r8152 2-1.2:1.0: load rtl8153b-2 v1 10/23/19 successfully
nov 08 19:45:21 g14 kernel: PM: resume of devices complete after 2568.814 msecs
nov 08 19:45:21 g14 kernel: PM: Finishing wakeup.
nov 08 19:45:21 g14 kernel: OOM killer enabled.
nov 08 19:45:21 g14 kernel: Restarting tasks ... done.
nov 08 19:45:21 g14 kernel: random: crng reseeded on system resumption
nov 08 19:45:22 g14 kernel: PM: suspend exit

Actually that is a pretty bad suspend. 3.461883/10277.995 is less than 1% in the deepeest state.

I've got a development patch that I'd like you to try. 0001-platform-x86-amd-pmc-Add-a-workaround-for-s0i3-issue.patch

Please apply it on top of 6.1-rc4, and let's see the next debug log with that in place.

It's from an older internal tree, so it might faily to apply; i'm not sure how smart git is about the filename change. So if it fails to apply; please s,drivers/platform/x86/amd-pmc.c,drivers/platform/x86/amd/pmc.c, to fix it.

Now on the patched 6.1-rc4, a few minutes of suspend, deepest state for only 19 seconds?

nov 08 22:37:48 g14 kernel: PM: suspend entry (s2idle)
nov 08 22:37:48 g14 kernel: Filesystems sync: 0.002 seconds
nov 08 22:37:48 g14 kernel: PM: Preparing system for sleep (s2idle)
nov 08 22:45:23 g14 kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
nov 08 22:45:23 g14 kernel: OOM killer disabled.
nov 08 22:45:23 g14 kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
nov 08 22:45:23 g14 kernel: PM: Suspending system (s2idle)
nov 08 22:45:23 g14 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
nov 08 22:45:23 g14 kernel: PM: suspend of devices complete after 136.188 msecs
nov 08 22:45:23 g14 kernel: PM: start suspend of devices complete after 136.393 msecs
nov 08 22:45:23 g14 kernel: PM: late suspend of devices complete after 0.566 msecs
nov 08 22:45:23 g14 kernel: ACPI: EC: interrupt blocked
nov 08 22:45:23 g14 kernel: PM: noirq suspend of devices complete after 56.540 msecs
nov 08 22:45:23 g14 kernel: ACPI: \_SB_.PLTF.P000: LPI: Device not power manageable
nov 08 22:45:23 g14 kernel: ACPI: \_SB_.PLTF.P001: LPI: Device not power manageable
nov 08 22:45:23 g14 kernel: ACPI: \_SB_.PLTF.P002: LPI: Device not power manageable
nov 08 22:45:23 g14 kernel: ACPI: \_SB_.PLTF.P003: LPI: Device not power manageable
nov 08 22:45:23 g14 kernel: ACPI: \_SB_.PLTF.P004: LPI: Device not power manageable
nov 08 22:45:23 g14 kernel: ACPI: \_SB_.PLTF.P005: LPI: Device not power manageable
nov 08 22:45:23 g14 kernel: ACPI: \_SB_.PLTF.P006: LPI: Device not power manageable
nov 08 22:45:23 g14 kernel: ACPI: \_SB_.PLTF.P007: LPI: Device not power manageable
nov 08 22:45:23 g14 kernel: ACPI: \_SB_.PLTF.P008: LPI: Device not power manageable
nov 08 22:45:23 g14 kernel: ACPI: \_SB_.PLTF.P009: LPI: Device not power manageable
nov 08 22:45:23 g14 kernel: ACPI: \_SB_.PLTF.P00A: LPI: Device not power manageable
nov 08 22:45:23 g14 kernel: ACPI: \_SB_.PLTF.P00B: LPI: Device not power manageable
nov 08 22:45:23 g14 kernel: ACPI: \_SB_.PLTF.P00C: LPI: Device not power manageable
nov 08 22:45:23 g14 kernel: ACPI: \_SB_.PLTF.P00D: LPI: Device not power manageable
nov 08 22:45:23 g14 kernel: ACPI: \_SB_.PLTF.P00E: LPI: Device not power manageable
nov 08 22:45:23 g14 kernel: ACPI: \_SB_.PLTF.P00F: LPI: Device not power manageable
nov 08 22:45:23 g14 kernel: ACPI: \_SB_.PCI0.GPP1: LPI: Device not power manageable
nov 08 22:45:23 g14 kernel: ACPI: \_SB_.PCI0.GPP2: LPI: Device not power manageable
nov 08 22:45:23 g14 kernel: ACPI: \_SB_.PCI0.GPP4: LPI: Device not power manageable
nov 08 22:45:23 g14 kernel: ACPI: \_SB_.PCI0.GPP4.WLAN: LPI: Device not power manageable
nov 08 22:45:23 g14 kernel: ACPI: \_SB_.PCI0.GP17.VGA_: LPI: Device not power manageable
nov 08 22:45:23 g14 kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: Constraint not met; min power state:D3hot current power state:D0
nov 08 22:45:23 g14 kernel: ACPI: \_SB_.PCI0.GP17.HDAU: LPI: Device not power manageable
nov 08 22:45:23 g14 kernel: ACPI: \_SB_.PCI0.GP18.SATA: LPI: Device not power manageable
nov 08 22:45:23 g14 kernel: ACPI: \_SB_.PCI0.GP18.SAT1: LPI: Device not power manageable
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:73f
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:9
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:ec1c7a80
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:5
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:4
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:7
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:6
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:402c00
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:2
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: SMU program 0 version is 64.44.0
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:1
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
nov 08 22:45:23 g14 kernel: PM: suspend-to-idle
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02e0eb5
nov 08 22:45:23 g14 kernel: Timekeeping suspended for 19.967 seconds
nov 08 22:45:23 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 22:45:23 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 08 22:45:23 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 08 22:45:23 g14 kernel: asus_wmi: Unknown key code 0x7b
nov 08 22:45:23 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 08 22:45:23 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 08 22:45:23 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 22:45:23 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 08 22:45:23 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 08 22:45:23 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 08 22:45:23 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 08 22:45:23 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 22:45:23 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 08 22:45:23 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 08 22:45:23 g14 kernel: Timekeeping suspended for 0.872 seconds
nov 08 22:45:23 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 22:45:23 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 08 22:45:23 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 08 22:45:23 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 08 22:45:23 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 08 22:45:23 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 08 22:45:23 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 08 22:45:23 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 08 22:45:23 g14 kernel: Timekeeping suspended for 430.997 seconds
nov 08 22:45:23 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 22:45:23 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 08 22:45:23 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 08 22:45:23 g14 kernel: asus_wmi: Unknown key code 0xcf
nov 08 22:45:23 g14 kernel: asus_wmi: Unknown key code 0x7b
nov 08 22:45:23 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 08 22:45:23 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 08 22:45:23 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02e0eb5
nov 08 22:45:23 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 08 22:45:23 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02e0eb5
nov 08 22:45:23 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 22:45:23 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 08 22:45:23 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 08 22:45:23 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 08 22:45:23 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 08 22:45:23 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02e0eb5
nov 08 22:45:23 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 08 22:45:23 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02e0eb5
nov 08 22:45:23 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 08 22:45:23 g14 kernel: PM: Triggering wakeup from IRQ 7
nov 08 22:45:23 g14 kernel: PM: Triggering wakeup from IRQ 0
nov 08 22:45:23 g14 kernel: ACPI: PM: ACPI non-EC GPE wakeup
nov 08 22:45:23 g14 kernel: PM: resume from suspend-to-idle
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:8
nov 08 22:45:23 g14 kernel: amd_pmc AMDI0005:00: Last suspend in deepest state for 19754699us
nov 08 22:45:23 g14 kernel: ACPI: EC: interrupt unblocked
nov 08 22:45:23 g14 kernel: PM: noirq resume of devices complete after 1273.472 msecs
nov 08 22:45:23 g14 kernel: PM: early resume of devices complete after 0.427 msecs
nov 08 22:45:23 g14 kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
nov 08 22:45:23 g14 kernel: pci 0000:00:00.2: PCI INT A: no GSI
nov 08 22:45:23 g14 kernel: [drm] PCIE GART of 1024M enabled.
nov 08 22:45:23 g14 kernel: [drm] PTB located at 0x000000F41FC00000
nov 08 22:45:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
nov 08 22:45:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: dpm has been disabled
nov 08 22:45:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
nov 08 22:45:23 g14 kernel: nvme nvme0: 8/0/0 default/read/poll queues
nov 08 22:45:23 g14 kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
nov 08 22:45:23 g14 kernel: [drm] JPEG decode initialized successfully.
nov 08 22:45:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
nov 08 22:45:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
nov 08 22:45:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
nov 08 22:45:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
nov 08 22:45:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
nov 08 22:45:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
nov 08 22:45:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
nov 08 22:45:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
nov 08 22:45:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
nov 08 22:45:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
nov 08 22:45:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
nov 08 22:45:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
nov 08 22:45:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
nov 08 22:45:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
nov 08 22:45:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
nov 08 22:45:23 g14 kernel: usb 1-1: reset high-speed USB device number 2 using xhci_hcd
nov 08 22:45:23 g14 kernel: usb 2-1: reset SuperSpeed USB device number 2 using xhci_hcd
nov 08 22:45:23 g14 kernel: usb 1-1.1: reset high-speed USB device number 4 using xhci_hcd
nov 08 22:45:23 g14 kernel: usb 2-1.2: reset SuperSpeed USB device number 3 using xhci_hcd
nov 08 22:45:23 g14 kernel: r8152 2-1.2:1.0: skip request firmware
nov 08 22:45:23 g14 kernel: r8152 2-1.2:1.0: load rtl8153b-2 v1 10/23/19 successfully
nov 08 22:45:23 g14 kernel: PM: resume of devices complete after 1446.022 msecs
nov 08 22:45:23 g14 kernel: PM: Finishing wakeup.
nov 08 22:45:23 g14 kernel: OOM killer enabled.
nov 08 22:45:23 g14 kernel: Restarting tasks ... done.
nov 08 22:45:23 g14 kernel: random: crng reseeded on system resumption
nov 08 22:45:23 g14 kernel: PM: suspend exit

Yeah so pretty much the first suspend cycle (19.7 seconds) you were in the deepest state, but from every wakeup onwards after that you were not. The idle mask does change by one bit in the future attempts. I didn't think that bit actually mattered but I'll try to find out if that's bit that changed is actually significant. @lijo any thoughts on this?

BTW that's an awful lot of wakeups though too if that's just a few minutes.

While I'm looking into the bit difference three asks:

1. Can I please see an acpidump? I'll see if something stands out with the EC not being notified properly at suspend time for your system.
2. If you blacklist asus-wmi on a given boot does the same thing happen?
3. If you extend the range in my patch 10-20ms to 30-50ms does that help?

Here are the acpidump outputs:

• acpidump_ga401qm.log
• acpidump_ga401qm_binary.tgz

I've removed the asus-wmi module, and will check the results now...

Seems like blacklisting asus-wmi has no real effect, about 30 minutes of suspend, only about 4 seconds in deep sleep:

nov 09 08:26:55 g14 kernel: PM: suspend entry (s2idle)
nov 09 08:26:55 g14 kernel: Filesystems sync: 0.001 seconds
nov 09 08:26:55 g14 kernel: PM: Preparing system for sleep (s2idle)
nov 09 08:55:23 g14 kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
nov 09 08:55:23 g14 kernel: OOM killer disabled.
nov 09 08:55:23 g14 kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
nov 09 08:55:23 g14 kernel: PM: Suspending system (s2idle)
nov 09 08:55:23 g14 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
nov 09 08:55:23 g14 kernel: PM: suspend of devices complete after 143.600 msecs
nov 09 08:55:23 g14 kernel: PM: start suspend of devices complete after 143.789 msecs
nov 09 08:55:23 g14 kernel: PM: late suspend of devices complete after 0.481 msecs
nov 09 08:55:23 g14 kernel: ACPI: EC: interrupt blocked
nov 09 08:55:23 g14 kernel: PM: noirq suspend of devices complete after 63.051 msecs
nov 09 08:55:23 g14 kernel: ACPI: \_SB_.PLTF.P000: LPI: Device not power manageable
nov 09 08:55:23 g14 kernel: ACPI: \_SB_.PLTF.P001: LPI: Device not power manageable
nov 09 08:55:23 g14 kernel: ACPI: \_SB_.PLTF.P002: LPI: Device not power manageable
nov 09 08:55:23 g14 kernel: ACPI: \_SB_.PLTF.P003: LPI: Device not power manageable
nov 09 08:55:23 g14 kernel: ACPI: \_SB_.PLTF.P004: LPI: Device not power manageable
nov 09 08:55:23 g14 kernel: ACPI: \_SB_.PLTF.P005: LPI: Device not power manageable
nov 09 08:55:23 g14 kernel: ACPI: \_SB_.PLTF.P006: LPI: Device not power manageable
nov 09 08:55:23 g14 kernel: ACPI: \_SB_.PLTF.P007: LPI: Device not power manageable
nov 09 08:55:23 g14 kernel: ACPI: \_SB_.PLTF.P008: LPI: Device not power manageable
nov 09 08:55:23 g14 kernel: ACPI: \_SB_.PLTF.P009: LPI: Device not power manageable
nov 09 08:55:23 g14 kernel: ACPI: \_SB_.PLTF.P00A: LPI: Device not power manageable
nov 09 08:55:23 g14 kernel: ACPI: \_SB_.PLTF.P00B: LPI: Device not power manageable
nov 09 08:55:23 g14 kernel: ACPI: \_SB_.PLTF.P00C: LPI: Device not power manageable
nov 09 08:55:23 g14 kernel: ACPI: \_SB_.PLTF.P00D: LPI: Device not power manageable
nov 09 08:55:23 g14 kernel: ACPI: \_SB_.PLTF.P00E: LPI: Device not power manageable
nov 09 08:55:23 g14 kernel: ACPI: \_SB_.PLTF.P00F: LPI: Device not power manageable
nov 09 08:55:23 g14 kernel: ACPI: \_SB_.PCI0.GPP1: LPI: Device not power manageable
nov 09 08:55:23 g14 kernel: ACPI: \_SB_.PCI0.GPP2: LPI: Device not power manageable
nov 09 08:55:23 g14 kernel: ACPI: \_SB_.PCI0.GPP4: LPI: Device not power manageable
nov 09 08:55:23 g14 kernel: ACPI: \_SB_.PCI0.GPP4.WLAN: LPI: Device not power manageable
nov 09 08:55:23 g14 kernel: ACPI: \_SB_.PCI0.GP17.VGA_: LPI: Device not power manageable
nov 09 08:55:23 g14 kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: Constraint not met; min power state:D3hot current power state:D0
nov 09 08:55:23 g14 kernel: ACPI: \_SB_.PCI0.GP17.HDAU: LPI: Device not power manageable
nov 09 08:55:23 g14 kernel: ACPI: \_SB_.PCI0.GP18.SATA: LPI: Device not power manageable
nov 09 08:55:23 g14 kernel: ACPI: \_SB_.PCI0.GP18.SAT1: LPI: Device not power manageable
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:73f
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:9
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:ec1c7a80
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:5
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:4
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:7
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:6
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:402c00
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:2
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: SMU program 0 version is 64.44.0
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:1
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
nov 09 08:55:23 g14 kernel: PM: suspend-to-idle
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02e0eb5
nov 09 08:55:23 g14 kernel: Timekeeping suspended for 3.938 seconds
nov 09 08:55:23 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 09 08:55:23 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 09 08:55:23 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 09 08:55:23 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 09 08:55:23 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 09 08:55:23 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 09 08:55:23 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 09 08:55:23 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 09 08:55:23 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 09 08:55:23 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 09 08:55:23 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 09 08:55:23 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 09 08:55:23 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 09 08:55:23 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 09 08:55:23 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 09 08:55:23 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 09 08:55:23 g14 kernel: Timekeeping suspended for 1699.872 seconds
nov 09 08:55:23 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 09 08:55:23 g14 kernel: PM: Triggering wakeup from IRQ 34
nov 09 08:55:23 g14 kernel: PM: Triggering wakeup from IRQ 0
nov 09 08:55:23 g14 kernel: ACPI: PM: ACPI non-EC GPE wakeup
nov 09 08:55:23 g14 kernel: PM: resume from suspend-to-idle
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:8
nov 09 08:55:23 g14 kernel: amd_pmc AMDI0005:00: Last suspend in deepest state for 4213012us
nov 09 08:55:23 g14 kernel: ACPI: EC: interrupt unblocked
nov 09 08:55:23 g14 kernel: PM: noirq resume of devices complete after 1339.465 msecs
nov 09 08:55:23 g14 kernel: PM: early resume of devices complete after 0.660 msecs
nov 09 08:55:23 g14 kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
nov 09 08:55:23 g14 kernel: pci 0000:00:00.2: PCI INT A: no GSI
nov 09 08:55:23 g14 kernel: [drm] PCIE GART of 1024M enabled.
nov 09 08:55:23 g14 kernel: [drm] PTB located at 0x000000F41FC00000
nov 09 08:55:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
nov 09 08:55:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: dpm has been disabled
nov 09 08:55:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
nov 09 08:55:23 g14 kernel: nvme nvme0: 8/0/0 default/read/poll queues
nov 09 08:55:23 g14 kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
nov 09 08:55:23 g14 kernel: [drm] JPEG decode initialized successfully.
nov 09 08:55:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
nov 09 08:55:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
nov 09 08:55:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
nov 09 08:55:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
nov 09 08:55:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
nov 09 08:55:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
nov 09 08:55:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
nov 09 08:55:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
nov 09 08:55:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
nov 09 08:55:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
nov 09 08:55:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
nov 09 08:55:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
nov 09 08:55:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
nov 09 08:55:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
nov 09 08:55:23 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
nov 09 08:55:23 g14 kernel: usb 1-1: reset high-speed USB device number 2 using xhci_hcd
nov 09 08:55:23 g14 kernel: usb 2-1: reset SuperSpeed USB device number 2 using xhci_hcd
nov 09 08:55:23 g14 kernel: usb 1-1.1: reset high-speed USB device number 4 using xhci_hcd
nov 09 08:55:23 g14 kernel: usb 2-1.2: reset SuperSpeed USB device number 3 using xhci_hcd
nov 09 08:55:23 g14 kernel: r8152 2-1.2:1.0: skip request firmware
nov 09 08:55:23 g14 kernel: r8152 2-1.2:1.0: load rtl8153b-2 v1 10/23/19 successfully
nov 09 08:55:23 g14 kernel: PM: resume of devices complete after 2020.291 msecs
nov 09 08:55:23 g14 kernel: PM: Finishing wakeup.
nov 09 08:55:23 g14 kernel: OOM killer enabled.
nov 09 08:55:23 g14 kernel: Restarting tasks ... done.
nov 09 08:55:23 g14 kernel: random: crng reseeded on system resumption
nov 09 08:55:23 g14 kernel: PM: suspend exit

Will extend now the range as you've suggested.

Interestingly my acpidump is a tiny bit different

acpidump_qa401qm_marcaux.diff

Nothing that should influence this behavious I would think.

Another session, with extended range in the patch, around 8% drain in one hour:

nov 09 14:28:01 g14 kernel: PM: suspend entry (s2idle)
nov 09 14:28:01 g14 kernel: Filesystems sync: 0.002 seconds
nov 09 14:28:01 g14 kernel: PM: Preparing system for sleep (s2idle)
nov 09 15:28:04 g14 kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
nov 09 15:28:04 g14 kernel: OOM killer disabled.
nov 09 15:28:04 g14 kernel: Freezing remaining freezable tasks ... (elapsed 2.379 seconds) done.
nov 09 15:28:04 g14 kernel: PM: Suspending system (s2idle)
nov 09 15:28:04 g14 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
nov 09 15:28:04 g14 kernel: PM: suspend of devices complete after 167.670 msecs
nov 09 15:28:04 g14 kernel: PM: start suspend of devices complete after 168.101 msecs
nov 09 15:28:04 g14 kernel: PM: late suspend of devices complete after 1.122 msecs
nov 09 15:28:04 g14 kernel: ACPI: EC: interrupt blocked
nov 09 15:28:04 g14 kernel: PM: noirq suspend of devices complete after 62.215 msecs
nov 09 15:28:04 g14 kernel: ACPI: \_SB_.PLTF.P000: LPI: Device not power manageable
nov 09 15:28:04 g14 kernel: ACPI: \_SB_.PLTF.P001: LPI: Device not power manageable
nov 09 15:28:04 g14 kernel: ACPI: \_SB_.PLTF.P002: LPI: Device not power manageable
nov 09 15:28:04 g14 kernel: ACPI: \_SB_.PLTF.P003: LPI: Device not power manageable
nov 09 15:28:04 g14 kernel: ACPI: \_SB_.PLTF.P004: LPI: Device not power manageable
nov 09 15:28:04 g14 kernel: ACPI: \_SB_.PLTF.P005: LPI: Device not power manageable
nov 09 15:28:04 g14 kernel: ACPI: \_SB_.PLTF.P006: LPI: Device not power manageable
nov 09 15:28:04 g14 kernel: ACPI: \_SB_.PLTF.P007: LPI: Device not power manageable
nov 09 15:28:04 g14 kernel: ACPI: \_SB_.PLTF.P008: LPI: Device not power manageable
nov 09 15:28:04 g14 kernel: ACPI: \_SB_.PLTF.P009: LPI: Device not power manageable
nov 09 15:28:04 g14 kernel: ACPI: \_SB_.PLTF.P00A: LPI: Device not power manageable
nov 09 15:28:04 g14 kernel: ACPI: \_SB_.PLTF.P00B: LPI: Device not power manageable
nov 09 15:28:04 g14 kernel: ACPI: \_SB_.PLTF.P00C: LPI: Device not power manageable
nov 09 15:28:04 g14 kernel: ACPI: \_SB_.PLTF.P00D: LPI: Device not power manageable
nov 09 15:28:04 g14 kernel: ACPI: \_SB_.PLTF.P00E: LPI: Device not power manageable
nov 09 15:28:04 g14 kernel: ACPI: \_SB_.PLTF.P00F: LPI: Device not power manageable
nov 09 15:28:04 g14 kernel: ACPI: \_SB_.PCI0.GPP1: LPI: Device not power manageable
nov 09 15:28:04 g14 kernel: ACPI: \_SB_.PCI0.GPP2: LPI: Device not power manageable
nov 09 15:28:04 g14 kernel: ACPI: \_SB_.PCI0.GPP4: LPI: Device not power manageable
nov 09 15:28:04 g14 kernel: ACPI: \_SB_.PCI0.GPP4.WLAN: LPI: Device not power manageable
nov 09 15:28:04 g14 kernel: ACPI: \_SB_.PCI0.GP17.VGA_: LPI: Device not power manageable
nov 09 15:28:04 g14 kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: Constraint not met; min power state:D3hot current power state:D0
nov 09 15:28:04 g14 kernel: ACPI: \_SB_.PCI0.GP17.HDAU: LPI: Device not power manageable
nov 09 15:28:04 g14 kernel: ACPI: \_SB_.PCI0.GP18.SATA: LPI: Device not power manageable
nov 09 15:28:04 g14 kernel: ACPI: \_SB_.PCI0.GP18.SAT1: LPI: Device not power manageable
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:73f
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:9
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:ec1c7a80
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:5
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:4
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:7
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:6
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:402c00
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:2
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: SMU program 0 version is 64.44.0
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:1
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
nov 09 15:28:04 g14 kernel: PM: suspend-to-idle
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02e0eb5
nov 09 15:28:04 g14 kernel: Timekeeping suspended for 12.764 seconds
nov 09 15:28:04 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 09 15:28:04 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 09 15:28:04 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 09 15:28:04 g14 kernel: asus_wmi: Unknown key code 0x7b
nov 09 15:28:04 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 09 15:28:04 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 09 15:28:04 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 09 15:28:04 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 09 15:28:04 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 09 15:28:04 g14 kernel: Timekeeping suspended for 0.872 seconds
nov 09 15:28:04 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 09 15:28:04 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 09 15:28:04 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 09 15:28:04 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 09 15:28:04 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 09 15:28:04 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 09 15:28:04 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 09 15:28:04 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 09 15:28:04 g14 kernel: Timekeeping suspended for 3582.997 seconds
nov 09 15:28:04 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 09 15:28:04 g14 kernel: PM: Triggering wakeup from IRQ 7
nov 09 15:28:04 g14 kernel: PM: Triggering wakeup from IRQ 0
nov 09 15:28:04 g14 kernel: ACPI: PM: ACPI non-EC GPE wakeup
nov 09 15:28:04 g14 kernel: PM: resume from suspend-to-idle
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:8
nov 09 15:28:04 g14 kernel: amd_pmc AMDI0005:00: Last suspend in deepest state for 12547790us
nov 09 15:28:04 g14 kernel: ACPI: EC: interrupt unblocked
nov 09 15:28:04 g14 kernel: PM: noirq resume of devices complete after 1339.646 msecs
nov 09 15:28:04 g14 kernel: asus_wmi: Unknown key code 0xcf
nov 09 15:28:04 g14 kernel: asus_wmi: Unknown key code 0x7b
nov 09 15:28:04 g14 kernel: PM: early resume of devices complete after 0.736 msecs
nov 09 15:28:04 g14 kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
nov 09 15:28:04 g14 kernel: pci 0000:00:00.2: PCI INT A: no GSI
nov 09 15:28:04 g14 kernel: [drm] PCIE GART of 1024M enabled.
nov 09 15:28:04 g14 kernel: [drm] PTB located at 0x000000F41FC00000
nov 09 15:28:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
nov 09 15:28:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: dpm has been disabled
nov 09 15:28:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
nov 09 15:28:04 g14 kernel: nvme nvme0: 8/0/0 default/read/poll queues
nov 09 15:28:04 g14 kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
nov 09 15:28:04 g14 kernel: [drm] JPEG decode initialized successfully.
nov 09 15:28:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
nov 09 15:28:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
nov 09 15:28:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
nov 09 15:28:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
nov 09 15:28:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
nov 09 15:28:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
nov 09 15:28:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
nov 09 15:28:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
nov 09 15:28:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
nov 09 15:28:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
nov 09 15:28:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
nov 09 15:28:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
nov 09 15:28:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
nov 09 15:28:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
nov 09 15:28:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
nov 09 15:28:04 g14 kernel: usb 1-1: reset high-speed USB device number 2 using xhci_hcd
nov 09 15:28:04 g14 kernel: usb 2-1: reset SuperSpeed USB device number 2 using xhci_hcd
nov 09 15:28:04 g14 kernel: usb 1-1.3: reset high-speed USB device number 6 using xhci_hcd
nov 09 15:28:04 g14 kernel: usb 1-1.1: reset high-speed USB device number 4 using xhci_hcd
nov 09 15:28:04 g14 kernel: usb 2-1.2: reset SuperSpeed USB device number 3 using xhci_hcd
nov 09 15:28:04 g14 kernel: r8152 2-1.2:1.0: skip request firmware
nov 09 15:28:04 g14 kernel: r8152 2-1.2:1.0: load rtl8153b-2 v1 10/23/19 successfully
nov 09 15:28:04 g14 kernel: PM: resume of devices complete after 1605.239 msecs
nov 09 15:28:04 g14 kernel: PM: Finishing wakeup.
nov 09 15:28:04 g14 kernel: OOM killer enabled.
nov 09 15:28:04 g14 kernel: Restarting tasks ... done.
nov 09 15:28:04 g14 kernel: random: crng reseeded on system resumption
nov 09 15:28:04 g14 kernel: PM: suspend exit

Another session, with extended range in the patch, around 8% drain in one hour:

From your above reports the signature looks the same.

• asus-wmi blacklist doesn't help it, but there is an ACPI notification that comes in that it doesn't react to either. We need to characterize that still.
• The one bit is different in the idle mask
• The usleep_range patch isn't doing anything notable for your situation.

Looking at the PEP code from the acpidump the Windows GUID isn't populated with anything, but the AMD GUID is. I expect with the latest 6.1 kernel code both get executed. Can you please turn on dynamic debugging for this file? Like this on kernel command line: acpi.dyndbg='drivers/acpi/x86/s2idle.c'. If they both do indeed execute, then we're at least doing everything that ASUS expected.

I appear to have gotten the syntax wrong. Try this: acpi.dyndbg=file drivers/acpi/x86/s2idle.c +p

another try

Nov 09 17:44:03 fedora kernel: PM: suspend entry (s2idle)
Nov 09 17:44:03 fedora kernel: Filesystems sync: 0.026 seconds
Nov 09 17:44:03 fedora kernel: PM: Preparing system for sleep (s2idle)
Nov 09 17:45:41 fedora kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Nov 09 17:45:41 fedora kernel: OOM killer disabled.
Nov 09 17:45:41 fedora kernel: Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done.
Nov 09 17:45:41 fedora kernel: PM: Suspending system (s2idle)
Nov 09 17:45:41 fedora kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Nov 09 17:45:41 fedora kernel: queueing ieee80211 work while going to suspend
Nov 09 17:45:41 fedora kernel: PM: suspend of devices complete after 134.596 msecs
Nov 09 17:45:41 fedora kernel: PM: start suspend of devices complete after 134.878 msecs
Nov 09 17:45:41 fedora kernel: PM: suspend devices took 0.134 seconds
Nov 09 17:45:41 fedora kernel: PM: late suspend of devices complete after 0.742 msecs
Nov 09 17:45:41 fedora kernel: ACPI: EC: interrupt blocked
Nov 09 17:45:41 fedora kernel: PM: noirq suspend of devices complete after 45.736 msecs
Nov 09 17:45:41 fedora kernel: ACPI: \_SB_.PLTF.P000: LPI: Device not power manageable
Nov 09 17:45:41 fedora kernel: ACPI: \_SB_.PLTF.P001: LPI: Device not power manageable
Nov 09 17:45:41 fedora kernel: ACPI: \_SB_.PLTF.P002: LPI: Device not power manageable
Nov 09 17:45:41 fedora kernel: ACPI: \_SB_.PLTF.P003: LPI: Device not power manageable
Nov 09 17:45:41 fedora kernel: ACPI: \_SB_.PLTF.P004: LPI: Device not power manageable
Nov 09 17:45:41 fedora kernel: ACPI: \_SB_.PLTF.P005: LPI: Device not power manageable
Nov 09 17:45:41 fedora kernel: ACPI: \_SB_.PLTF.P006: LPI: Device not power manageable
Nov 09 17:45:41 fedora kernel: ACPI: \_SB_.PLTF.P007: LPI: Device not power manageable
Nov 09 17:45:41 fedora kernel: ACPI: \_SB_.PLTF.P008: LPI: Device not power manageable
Nov 09 17:45:41 fedora kernel: ACPI: \_SB_.PLTF.P009: LPI: Device not power manageable
Nov 09 17:45:41 fedora kernel: ACPI: \_SB_.PLTF.P00A: LPI: Device not power manageable
Nov 09 17:45:41 fedora kernel: ACPI: \_SB_.PLTF.P00B: LPI: Device not power manageable
Nov 09 17:45:41 fedora kernel: ACPI: \_SB_.PLTF.P00C: LPI: Device not power manageable
Nov 09 17:45:41 fedora kernel: ACPI: \_SB_.PLTF.P00D: LPI: Device not power manageable
Nov 09 17:45:41 fedora kernel: ACPI: \_SB_.PLTF.P00E: LPI: Device not power manageable
Nov 09 17:45:41 fedora kernel: ACPI: \_SB_.PLTF.P00F: LPI: Device not power manageable
Nov 09 17:45:41 fedora kernel: ACPI: \_SB_.PCI0.GPP1: LPI: Device not power manageable
Nov 09 17:45:41 fedora kernel: ACPI: \_SB_.PCI0.GPP2: LPI: Device not power manageable
Nov 09 17:45:41 fedora kernel: ACPI: \_SB_.PCI0.GPP4: LPI: Device not power manageable
Nov 09 17:45:41 fedora kernel: ACPI: \_SB_.PCI0.GPP4.WLAN: LPI: Device not power manageable
Nov 09 17:45:41 fedora kernel: ACPI: \_SB_.PCI0.GP17.VGA_: LPI: Device not power manageable
Nov 09 17:45:41 fedora kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: Constraint not met; min power state:D3hot current power state:D0
Nov 09 17:45:41 fedora kernel: ACPI: \_SB_.PCI0.GP17.HDAU: LPI: Device not power manageable
Nov 09 17:45:41 fedora kernel: ACPI: \_SB_.PCI0.GP18.SATA: LPI: Device not power manageable
Nov 09 17:45:41 fedora kernel: ACPI: \_SB_.PCI0.GP18.SAT1: LPI: Device not power manageable
Nov 09 17:45:41 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 17:45:41 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:73f
Nov 09 17:45:41 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:9
Nov 09 17:45:41 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 17:45:41 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:ec1c8a80
Nov 09 17:45:41 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:5
Nov 09 17:45:41 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 17:45:41 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 09 17:45:41 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:4
Nov 09 17:45:41 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 17:45:41 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 09 17:45:41 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:7
Nov 09 17:45:41 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 17:45:41 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 09 17:45:41 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:6
Nov 09 17:45:41 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 17:45:41 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:1
Nov 09 17:45:41 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
Nov 09 17:45:41 fedora kernel: PM: suspend-to-idle
Nov 09 17:45:41 fedora kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
Nov 09 17:45:41 fedora kernel: Timekeeping suspended for 95.785 seconds
Nov 09 17:45:41 fedora kernel: PM: Triggering wakeup from IRQ 9
Nov 09 17:45:41 fedora kernel: ACPI: EC: ACPI EC GPE status set
Nov 09 17:45:41 fedora kernel: ACPI: EC: ACPI EC GPE dispatched
Nov 09 17:45:41 fedora kernel: ACPI: EC: ACPI EC work flushed
Nov 09 17:45:41 fedora kernel: ACPI: PM: Wakeup after ACPI Notify sync
Nov 09 17:45:41 fedora kernel: PM: resume from suspend-to-idle
Nov 09 17:45:41 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 17:45:41 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 09 17:45:41 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
Nov 09 17:45:41 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 17:45:41 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 09 17:45:41 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:8
Nov 09 17:45:41 fedora kernel: amd_pmc AMDI0005:00: Last suspend in deepest state for 96121643us
Nov 09 17:45:41 fedora kernel: ACPI: EC: interrupt unblocked
Nov 09 17:45:41 fedora kernel: PM: noirq resume of devices complete after 1261.693 msecs
Nov 09 17:45:41 fedora kernel: PM: early resume of devices complete after 0.501 msecs
Nov 09 17:45:41 fedora kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
Nov 09 17:45:41 fedora kernel: pci 0000:00:00.2: PCI INT A: no GSI
Nov 09 17:45:41 fedora kernel: [drm] PCIE GART of 1024M enabled.
Nov 09 17:45:41 fedora kernel: [drm] PTB located at 0x000000F41FC00000
Nov 09 17:45:41 fedora kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
Nov 09 17:45:41 fedora kernel: amdgpu 0000:04:00.0: amdgpu: dpm has been disabled
Nov 09 17:45:41 fedora kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
Nov 09 17:45:41 fedora kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Nov 09 17:45:41 fedora kernel: [drm] JPEG decode initialized successfully.
Nov 09 17:45:41 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
Nov 09 17:45:41 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Nov 09 17:45:41 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Nov 09 17:45:41 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Nov 09 17:45:41 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Nov 09 17:45:41 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Nov 09 17:45:41 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Nov 09 17:45:41 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Nov 09 17:45:41 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
Nov 09 17:45:41 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
Nov 09 17:45:41 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
Nov 09 17:45:41 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
Nov 09 17:45:41 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
Nov 09 17:45:41 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
Nov 09 17:45:41 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
Nov 09 17:45:41 fedora kernel: nvme nvme0: 16/0/0 default/read/poll queues
Nov 09 17:45:41 fedora kernel: nvme nvme0: Ignoring bogus Namespace Identifiers
Nov 09 17:45:41 fedora kernel: PM: resume of devices complete after 275.915 msecs
Nov 09 17:45:41 fedora kernel: PM: resume devices took 0.276 seconds
Nov 09 17:45:41 fedora kernel: PM: Finishing wakeup.
Nov 09 17:45:41 fedora kernel: OOM killer enabled.
Nov 09 17:45:41 fedora kernel: Restarting tasks ... done.
Nov 09 17:45:41 fedora kernel: random: crng reseeded on system resumption
Nov 09 17:45:41 fedora kernel: PM: suspend exit

cat /proc/cmdline BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.1.0-0.rc4.20221108git59f2f4b8a757.36.local.fc37.x86_64 root=UUID=... ro rootflags=subvol=root rd.luks.uuid=luks-... rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 pm_debug_messages amd_pmc.dyndbg acpi.dyndbg=file drivers/acpi/x86/s2idle.c +p

do I need to set no_console_suspend according to this: Nov 09 17:45:41 fedora kernel: printk: Suspending console(s) (use no_console_suspend to debug) ?

Man I'm still getting the syntax wrong. 3rd try is a charm? acpi.dyndbg='file drivers/acpi/x86/s2idle.c +p'

this looks promising

Nov 09 17:53:37 fedora kernel: PM: suspend entry (s2idle)
Nov 09 17:53:37 fedora kernel: Filesystems sync: 0.029 seconds
Nov 09 17:53:37 fedora kernel: PM: Preparing system for sleep (s2idle)
Nov 09 17:57:30 fedora kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Nov 09 17:57:30 fedora kernel: OOM killer disabled.
Nov 09 17:57:30 fedora kernel: Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done.
Nov 09 17:57:30 fedora kernel: PM: Suspending system (s2idle)
Nov 09 17:57:30 fedora kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Nov 09 17:57:30 fedora kernel: queueing ieee80211 work while going to suspend
Nov 09 17:57:30 fedora kernel: PM: suspend of devices complete after 142.615 msecs
Nov 09 17:57:30 fedora kernel: PM: start suspend of devices complete after 142.882 msecs
Nov 09 17:57:30 fedora kernel: PM: suspend devices took 0.142 seconds
Nov 09 17:57:30 fedora kernel: PM: late suspend of devices complete after 0.773 msecs
Nov 09 17:57:30 fedora kernel: ACPI: EC: interrupt blocked
Nov 09 17:57:30 fedora kernel: PM: noirq suspend of devices complete after 47.750 msecs
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P000: LPI: required min power state:D3hot current power state:D0
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P000: LPI: Device not power manageable
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P001: LPI: required min power state:D3hot current power state:D0
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P001: LPI: Device not power manageable
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P002: LPI: required min power state:D3hot current power state:D0
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P002: LPI: Device not power manageable
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P003: LPI: required min power state:D3hot current power state:D0
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P003: LPI: Device not power manageable
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P004: LPI: required min power state:D3hot current power state:D0
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P004: LPI: Device not power manageable
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P005: LPI: required min power state:D3hot current power state:D0
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P005: LPI: Device not power manageable
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P006: LPI: required min power state:D3hot current power state:D0
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P006: LPI: Device not power manageable
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P007: LPI: required min power state:D3hot current power state:D0
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P007: LPI: Device not power manageable
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P008: LPI: required min power state:D3hot current power state:D0
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P008: LPI: Device not power manageable
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P009: LPI: required min power state:D3hot current power state:D0
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P009: LPI: Device not power manageable
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P00A: LPI: required min power state:D3hot current power state:D0
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P00A: LPI: Device not power manageable
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P00B: LPI: required min power state:D3hot current power state:D0
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P00B: LPI: Device not power manageable
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P00C: LPI: required min power state:D3hot current power state:D0
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P00C: LPI: Device not power manageable
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P00D: LPI: required min power state:D3hot current power state:D0
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P00D: LPI: Device not power manageable
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P00E: LPI: required min power state:D3hot current power state:D0
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P00E: LPI: Device not power manageable
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P00F: LPI: required min power state:D3hot current power state:D0
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PLTF.P00F: LPI: Device not power manageable
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PCI0.GPP0: LPI: required min power state:D3hot current power state:D3cold
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PCI0.GPP1: LPI: required min power state:D1 current power state:D0
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PCI0.GPP1: LPI: Device not power manageable
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PCI0.GPP2: LPI: required min power state:D1 current power state:D0
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PCI0.GPP2: LPI: Device not power manageable
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PCI0.GPP4: LPI: required min power state:D1 current power state:D0
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PCI0.GPP4: LPI: Device not power manageable
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PCI0.GPP4.WLAN: LPI: required min power state:D3hot current power state:D0
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PCI0.GPP4.WLAN: LPI: Device not power manageable
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PCI0.GPP6.NVME: LPI: required min power state:D3hot current power state:D3cold
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PCI0.GP17.VGA_: LPI: required min power state:D3hot current power state:D0
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PCI0.GP17.VGA_: LPI: Device not power manageable
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PCI0.GP17.AZAL: LPI: required min power state:D3hot current power state:D3hot
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: required min power state:D3hot current power state:D0
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: Constraint not met; min power state:D3hot current power state:D0
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PCI0.GP17.HDAU: LPI: required min power state:D3hot current power state:D0
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PCI0.GP17.HDAU: LPI: Device not power manageable
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PCI0.GP17.XHC0: LPI: required min power state:D3hot current power state:D3hot
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PCI0.GP17.XHC1: LPI: required min power state:D3hot current power state:D3hot
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PCI0.GP18.SATA: LPI: required min power state:D3hot current power state:D0
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PCI0.GP18.SATA: LPI: Device not power manageable
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PCI0.GP18.SAT1: LPI: required min power state:D3hot current power state:D0
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PCI0.GP18.SAT1: LPI: Device not power manageable
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 3 evaluation successful
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 2 evaluation successful
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 5 evaluation successful
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 7 evaluation successful
Nov 09 17:57:30 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 17:57:30 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:73f
Nov 09 17:57:30 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:9
Nov 09 17:57:30 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 17:57:30 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:ec1c8a80
Nov 09 17:57:30 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:5
Nov 09 17:57:30 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 17:57:30 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 09 17:57:30 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:4
Nov 09 17:57:30 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 17:57:30 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 09 17:57:30 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:7
Nov 09 17:57:30 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 17:57:30 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 09 17:57:30 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:6
Nov 09 17:57:30 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 17:57:30 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:1
Nov 09 17:57:30 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
Nov 09 17:57:30 fedora kernel: PM: suspend-to-idle
Nov 09 17:57:30 fedora kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
Nov 09 17:57:30 fedora kernel: Timekeeping suspended for 231.381 seconds
Nov 09 17:57:30 fedora kernel: PM: Triggering wakeup from IRQ 9
Nov 09 17:57:30 fedora kernel: ACPI: EC: ACPI EC GPE status set
Nov 09 17:57:30 fedora kernel: ACPI: EC: ACPI EC GPE dispatched
Nov 09 17:57:30 fedora kernel: ACPI: EC: ACPI EC work flushed
Nov 09 17:57:30 fedora kernel: ACPI: PM: Wakeup after ACPI Notify sync
Nov 09 17:57:30 fedora kernel: PM: resume from suspend-to-idle
Nov 09 17:57:30 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 17:57:30 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 09 17:57:30 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
Nov 09 17:57:30 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 17:57:30 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 09 17:57:30 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:8
Nov 09 17:57:30 fedora kernel: amd_pmc AMDI0005:00: Last suspend in deepest state for 231951965us
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 8 evaluation successful
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 3 evaluation successful
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 6 evaluation successful
Nov 09 17:57:30 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 4 evaluation successful
Nov 09 17:57:30 fedora kernel: ACPI: EC: interrupt unblocked
Nov 09 17:57:30 fedora kernel: PM: noirq resume of devices complete after 1259.541 msecs
Nov 09 17:57:30 fedora kernel: PM: early resume of devices complete after 0.493 msecs
Nov 09 17:57:30 fedora kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
Nov 09 17:57:30 fedora kernel: pci 0000:00:00.2: PCI INT A: no GSI
Nov 09 17:57:30 fedora kernel: [drm] PCIE GART of 1024M enabled.
Nov 09 17:57:30 fedora kernel: [drm] PTB located at 0x000000F41FC00000
Nov 09 17:57:30 fedora kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
Nov 09 17:57:30 fedora kernel: amdgpu 0000:04:00.0: amdgpu: dpm has been disabled
Nov 09 17:57:30 fedora kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
Nov 09 17:57:30 fedora kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Nov 09 17:57:30 fedora kernel: [drm] JPEG decode initialized successfully.
Nov 09 17:57:30 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
Nov 09 17:57:30 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Nov 09 17:57:30 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Nov 09 17:57:30 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Nov 09 17:57:30 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Nov 09 17:57:30 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Nov 09 17:57:30 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Nov 09 17:57:30 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Nov 09 17:57:30 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
Nov 09 17:57:30 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
Nov 09 17:57:30 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
Nov 09 17:57:30 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
Nov 09 17:57:30 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
Nov 09 17:57:30 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
Nov 09 17:57:30 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
Nov 09 17:57:30 fedora kernel: nvme nvme0: 16/0/0 default/read/poll queues
Nov 09 17:57:30 fedora kernel: nvme nvme0: Ignoring bogus Namespace Identifiers
Nov 09 17:57:30 fedora kernel: PM: resume of devices complete after 275.756 msecs
Nov 09 17:57:30 fedora kernel: PM: resume devices took 0.276 seconds
Nov 09 17:57:30 fedora kernel: PM: Finishing wakeup.
Nov 09 17:57:30 fedora kernel: OOM killer enabled.
Nov 09 17:57:30 fedora kernel: Restarting tasks ... done.
Nov 09 17:57:30 fedora kernel: random: crng reseeded on system resumption
Nov 09 17:57:30 fedora kernel: PM: suspend exit

Yes; but can I see the whole log this time?

this is the full journal from the current boot test.log

shall I filter for kernel messages next time?

OK got what I need. There are no problems here with the kernel notification path to the EC relative to what is actually declared in the firmware.

In looking at the reasons for an ACPI event and the idle mask difference I have another suspicion. Does this "high power consumption" issue only happen if the AC is unplugged (or plugged in for that matter) after you have entered suspend?

hmm... I just tried it out and through a super scientific method I observed that the coile whine I usually have, when the machine suspends properly, stops when I pull the power plug while it is suspended (I started suspend while plugged in, pulled it after a while)

A few more wakeup calls appear

Nov 09 18:14:28 fedora kernel: PM: suspend entry (s2idle)
Nov 09 18:14:28 fedora kernel: Filesystems sync: 0.020 seconds
Nov 09 18:14:28 fedora kernel: PM: Preparing system for sleep (s2idle)
Nov 09 18:16:11 fedora kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Nov 09 18:16:11 fedora kernel: OOM killer disabled.
Nov 09 18:16:11 fedora kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Nov 09 18:16:11 fedora kernel: PM: Suspending system (s2idle)
Nov 09 18:16:11 fedora kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Nov 09 18:16:11 fedora kernel: queueing ieee80211 work while going to suspend
Nov 09 18:16:11 fedora kernel: PM: suspend of devices complete after 328.538 msecs
Nov 09 18:16:11 fedora kernel: PM: start suspend of devices complete after 328.704 msecs
Nov 09 18:16:11 fedora kernel: PM: suspend devices took 0.328 seconds
Nov 09 18:16:11 fedora kernel: PM: late suspend of devices complete after 0.688 msecs
Nov 09 18:16:11 fedora kernel: ACPI: EC: interrupt blocked
Nov 09 18:16:11 fedora kernel: PM: noirq suspend of devices complete after 46.756 msecs
Nov 09 18:16:11 fedora kernel: ACPI: \_SB_.PCI0.GPP0: LPI: required min power state:D3hot current power state:D3cold
Nov 09 18:16:11 fedora kernel: ACPI: \_SB_.PCI0.GPP6.NVME: LPI: required min power state:D3hot current power state:D3cold
Nov 09 18:16:11 fedora kernel: ACPI: \_SB_.PCI0.GP17.AZAL: LPI: required min power state:D3hot current power state:D3hot
Nov 09 18:16:11 fedora kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: required min power state:D3hot current power state:D0
Nov 09 18:16:11 fedora kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: Constraint not met; min power state:D3hot current power state:D0
Nov 09 18:16:11 fedora kernel: ACPI: \_SB_.PCI0.GP17.XHC0: LPI: required min power state:D3hot current power state:D3hot
Nov 09 18:16:11 fedora kernel: ACPI: \_SB_.PCI0.GP17.XHC1: LPI: required min power state:D3hot current power state:D3hot
Nov 09 18:16:11 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 3 evaluation successful
Nov 09 18:16:11 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 2 evaluation successful
Nov 09 18:16:11 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 5 evaluation successful
Nov 09 18:16:11 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 7 evaluation successful
Nov 09 18:16:11 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 18:16:11 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 09 18:16:11 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:7
Nov 09 18:16:11 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 18:16:11 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 09 18:16:11 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:6
Nov 09 18:16:11 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 18:16:11 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:1
Nov 09 18:16:11 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
Nov 09 18:16:11 fedora kernel: PM: suspend-to-idle
Nov 09 18:16:11 fedora kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02e0eb5
Nov 09 18:16:11 fedora kernel: Timekeeping suspended for 46.071 seconds
Nov 09 18:16:11 fedora kernel: PM: Triggering wakeup from IRQ 9
Nov 09 18:16:11 fedora kernel: ACPI: EC: ACPI EC GPE status set
Nov 09 18:16:11 fedora kernel: ACPI: EC: ACPI EC GPE dispatched
Nov 09 18:16:11 fedora kernel: asus_wmi: Unknown key code 0x7b
Nov 09 18:16:11 fedora kernel: ACPI: EC: ACPI EC work flushed
Nov 09 18:16:11 fedora kernel: ACPI: PM: Rearming ACPI SCI for wakeup
Nov 09 18:16:11 fedora kernel: PM: Triggering wakeup from IRQ 9
Nov 09 18:16:11 fedora kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
Nov 09 18:16:11 fedora kernel: ACPI: EC: ACPI EC GPE status set
Nov 09 18:16:11 fedora kernel: ACPI: PM: Rearming ACPI SCI for wakeup
Nov 09 18:16:11 fedora kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
Nov 09 18:16:11 fedora kernel: Timekeeping suspended for 55.840 seconds
Nov 09 18:16:11 fedora kernel: PM: Triggering wakeup from IRQ 9
Nov 09 18:16:11 fedora kernel: PM: Triggering wakeup from IRQ 34
Nov 09 18:16:11 fedora kernel: PM: Triggering wakeup from IRQ 0
Nov 09 18:16:11 fedora kernel: ACPI: PM: ACPI non-EC GPE wakeup
Nov 09 18:16:11 fedora kernel: PM: resume from suspend-to-idle
Nov 09 18:16:11 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 18:16:11 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 09 18:16:11 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
Nov 09 18:16:11 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 18:16:11 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 09 18:16:11 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:8
Nov 09 18:16:11 fedora kernel: amd_pmc AMDI0005:00: Last suspend in deepest state for 46782714us
Nov 09 18:16:11 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 8 evaluation successful
Nov 09 18:16:11 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 3 evaluation successful
Nov 09 18:16:11 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 6 evaluation successful
Nov 09 18:16:11 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 4 evaluation successful
Nov 09 18:16:11 fedora kernel: ACPI: EC: interrupt unblocked
Nov 09 18:16:11 fedora kernel: PM: noirq resume of devices complete after 281.491 msecs
Nov 09 18:16:11 fedora kernel: PM: early resume of devices complete after 0.513 msecs
Nov 09 18:16:11 fedora kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
Nov 09 18:16:11 fedora kernel: pci 0000:00:00.2: PCI INT A: no GSI
Nov 09 18:16:11 fedora kernel: [drm] PCIE GART of 1024M enabled.
Nov 09 18:16:11 fedora kernel: [drm] PTB located at 0x000000F41FC00000
Nov 09 18:16:11 fedora kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
Nov 09 18:16:11 fedora kernel: amdgpu 0000:04:00.0: amdgpu: dpm has been disabled
Nov 09 18:16:11 fedora kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
Nov 09 18:16:11 fedora kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Nov 09 18:16:11 fedora kernel: [drm] JPEG decode initialized successfully.
Nov 09 18:16:11 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
Nov 09 18:16:11 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Nov 09 18:16:11 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Nov 09 18:16:11 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Nov 09 18:16:11 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Nov 09 18:16:11 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Nov 09 18:16:11 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Nov 09 18:16:11 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Nov 09 18:16:11 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
Nov 09 18:16:11 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
Nov 09 18:16:11 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
Nov 09 18:16:11 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
Nov 09 18:16:11 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
Nov 09 18:16:11 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
Nov 09 18:16:11 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
Nov 09 18:16:11 fedora kernel: nvme nvme0: 16/0/0 default/read/poll queues
Nov 09 18:16:11 fedora kernel: nvme nvme0: Ignoring bogus Namespace Identifiers
Nov 09 18:16:11 fedora kernel: PM: resume of devices complete after 275.761 msecs
Nov 09 18:16:11 fedora kernel: PM: resume devices took 0.276 seconds
Nov 09 18:16:11 fedora kernel: PM: Finishing wakeup.
Nov 09 18:16:11 fedora kernel: OOM killer enabled.
Nov 09 18:16:11 fedora kernel: Restarting tasks ... done.
Nov 09 18:16:11 fedora kernel: random: crng reseeded on system resumption
Nov 09 18:16:11 fedora kernel: PM: suspend exit

A few more wakeup calls appear

Sounds like we might have a promising root cause of the trigger then for this problem at least.

At runtime if you plug in/unplug the AC adapter do you see those same events:

asus_wmi: Unknown key code 0x7b

and

asus_wmi: Unknown key code 0xcf
asus_wmi: Unknown key code 0x7b

If so; we might have decoded their meaning

from unplugged to plugged

Nov 09 18:22:22 fedora kernel: asus_wmi: Unknown key code 0xcf
Nov 09 18:22:23 fedora kernel: asus_wmi: Unknown key code 0x7b

from plugged to unplugged

Nov 09 18:23:03 fedora kernel: asus_wmi: Unknown key code 0x7b

7b is triggered both times, while cf only when get plugged

Well maybe one of you guys can turn that information into a kernel patch to asus-wmi to ignore those events. Or better yet you can add a dynamic debugging statement about the power adapter plugged in / unplugged to that driver. It can be helpful for debugging these kinds of issues in the future.

At least this all jives together now.

Another idea to root cause what's happening - can you please put the iommu into pass through mode (iommu=pt) and then suspend and toggle the cord? If that helps we might have a page fault that is triggered during the resume process.

Would ignoring those events have other consequences (like not being able to detect a plugged / battery state)? or are those events completely seperate?

So the reason those events go to the asus-wmi driver is a result of the way the ASL works. When the system wakes up from the power source plug in the EC is queried, gets some info. One of the calls has an ACPI Notify() that all registered receivers will get. asus-wmi happens to be registered for this and does nothing with the info, just shows that message.

On Windows I would guess that there is some GUI application that receives events like that and shows a popup with an icon that power is plugged in or unplugged. Unless the ASUS driver actually is supposed to respond and do something different it should be harmless to change the code to ignore such events.

with iommu=pt

Nov 09 18:33:15 fedora systemd-sleep[3912]: Entering sleep state 'suspend'...
Nov 09 18:33:15 fedora kernel: PM: suspend entry (s2idle)
Nov 09 18:33:15 fedora kernel: Filesystems sync: 0.017 seconds
Nov 09 18:33:15 fedora kernel: PM: Preparing system for sleep (s2idle)
Nov 09 18:35:16 fedora kernel: Freezing user space processes ... (elapsed 0.014 seconds) done.
Nov 09 18:35:16 fedora kernel: OOM killer disabled.
Nov 09 18:35:16 fedora kernel: Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done.
Nov 09 18:35:16 fedora kernel: PM: Suspending system (s2idle)
Nov 09 18:35:16 fedora kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Nov 09 18:35:16 fedora kernel: queueing ieee80211 work while going to suspend
Nov 09 18:35:16 fedora kernel: PM: suspend of devices complete after 124.441 msecs
Nov 09 18:35:16 fedora kernel: PM: start suspend of devices complete after 124.608 msecs
Nov 09 18:35:16 fedora kernel: PM: suspend devices took 0.124 seconds
Nov 09 18:35:16 fedora kernel: PM: late suspend of devices complete after 0.511 msecs
Nov 09 18:35:16 fedora kernel: ACPI: EC: interrupt blocked
Nov 09 18:35:16 fedora kernel: PM: noirq suspend of devices complete after 47.166 msecs
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P000: LPI: required min power state:D3hot current power state:D0
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P000: LPI: Device not power manageable
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P001: LPI: required min power state:D3hot current power state:D0
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P001: LPI: Device not power manageable
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P002: LPI: required min power state:D3hot current power state:D0
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P002: LPI: Device not power manageable
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P003: LPI: required min power state:D3hot current power state:D0
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P003: LPI: Device not power manageable
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P004: LPI: required min power state:D3hot current power state:D0
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P004: LPI: Device not power manageable
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P005: LPI: required min power state:D3hot current power state:D0
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P005: LPI: Device not power manageable
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P006: LPI: required min power state:D3hot current power state:D0
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P006: LPI: Device not power manageable
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P007: LPI: required min power state:D3hot current power state:D0
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P007: LPI: Device not power manageable
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P008: LPI: required min power state:D3hot current power state:D0
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P008: LPI: Device not power manageable
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P009: LPI: required min power state:D3hot current power state:D0
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P009: LPI: Device not power manageable
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P00A: LPI: required min power state:D3hot current power state:D0
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P00A: LPI: Device not power manageable
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P00B: LPI: required min power state:D3hot current power state:D0
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P00B: LPI: Device not power manageable
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P00C: LPI: required min power state:D3hot current power state:D0
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P00C: LPI: Device not power manageable
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P00D: LPI: required min power state:D3hot current power state:D0
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P00D: LPI: Device not power manageable
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P00E: LPI: required min power state:D3hot current power state:D0
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P00E: LPI: Device not power manageable
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P00F: LPI: required min power state:D3hot current power state:D0
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PLTF.P00F: LPI: Device not power manageable
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PCI0.GPP0: LPI: required min power state:D3hot current power state:D3cold
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PCI0.GPP1: LPI: required min power state:D1 current power state:D0
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PCI0.GPP1: LPI: Device not power manageable
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PCI0.GPP2: LPI: required min power state:D1 current power state:D0
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PCI0.GPP2: LPI: Device not power manageable
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PCI0.GPP4: LPI: required min power state:D1 current power state:D0
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PCI0.GPP4: LPI: Device not power manageable
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PCI0.GPP4.WLAN: LPI: required min power state:D3hot current power state:D0
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PCI0.GPP4.WLAN: LPI: Device not power manageable
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PCI0.GPP6.NVME: LPI: required min power state:D3hot current power state:D3cold
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PCI0.GP17.VGA_: LPI: required min power state:D3hot current power state:D0
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PCI0.GP17.VGA_: LPI: Device not power manageable
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PCI0.GP17.AZAL: LPI: required min power state:D3hot current power state:D3hot
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: required min power state:D3hot current power state:D0
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: Constraint not met; min power state:D3hot current power state:D0
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PCI0.GP17.HDAU: LPI: required min power state:D3hot current power state:D0
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PCI0.GP17.HDAU: LPI: Device not power manageable
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PCI0.GP17.XHC0: LPI: required min power state:D3hot current power state:D3hot
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PCI0.GP17.XHC1: LPI: required min power state:D3hot current power state:D3hot
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PCI0.GP18.SATA: LPI: required min power state:D3hot current power state:D0
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PCI0.GP18.SATA: LPI: Device not power manageable
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PCI0.GP18.SAT1: LPI: required min power state:D3hot current power state:D0
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PCI0.GP18.SAT1: LPI: Device not power manageable
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 3 evaluation successful
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 2 evaluation successful
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 5 evaluation successful
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 7 evaluation successful
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:73f
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:9
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:ec1c8a80
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:5
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:4
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:7
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:6
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:1
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
Nov 09 18:35:16 fedora kernel: PM: suspend-to-idle
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02e0eb5
Nov 09 18:35:16 fedora kernel: Timekeeping suspended for 34.942 seconds
Nov 09 18:35:16 fedora kernel: PM: Triggering wakeup from IRQ 9
Nov 09 18:35:16 fedora kernel: ACPI: EC: ACPI EC GPE status set
Nov 09 18:35:16 fedora kernel: ACPI: EC: ACPI EC GPE dispatched
Nov 09 18:35:16 fedora kernel: asus_wmi: Unknown key code 0x7b
Nov 09 18:35:16 fedora kernel: ACPI: EC: ACPI EC work flushed
Nov 09 18:35:16 fedora kernel: ACPI: PM: Rearming ACPI SCI for wakeup
Nov 09 18:35:16 fedora kernel: PM: Triggering wakeup from IRQ 9
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
Nov 09 18:35:16 fedora kernel: ACPI: EC: ACPI EC GPE status set
Nov 09 18:35:16 fedora kernel: ACPI: EC: ACPI EC GPE dispatched
Nov 09 18:35:16 fedora kernel: ACPI: EC: ACPI EC work flushed
Nov 09 18:35:16 fedora kernel: ACPI: PM: Rearming ACPI SCI for wakeup
Nov 09 18:35:16 fedora kernel: PM: Triggering wakeup from IRQ 9
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
Nov 09 18:35:16 fedora kernel: ACPI: EC: ACPI EC GPE status set
Nov 09 18:35:16 fedora kernel: ACPI: PM: Rearming ACPI SCI for wakeup
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
Nov 09 18:35:16 fedora kernel: Timekeeping suspended for 84.881 seconds
Nov 09 18:35:16 fedora kernel: PM: Triggering wakeup from IRQ 9
Nov 09 18:35:16 fedora kernel: PM: Triggering wakeup from IRQ 7
Nov 09 18:35:16 fedora kernel: PM: Triggering wakeup from IRQ 0
Nov 09 18:35:16 fedora kernel: ACPI: PM: ACPI non-EC GPE wakeup
Nov 09 18:35:16 fedora kernel: PM: resume from suspend-to-idle
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:8
Nov 09 18:35:16 fedora kernel: amd_pmc AMDI0005:00: Last suspend in deepest state for 35083373us
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 8 evaluation successful
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 3 evaluation successful
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 6 evaluation successful
Nov 09 18:35:16 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 4 evaluation successful
Nov 09 18:35:16 fedora kernel: ACPI: EC: interrupt unblocked
Nov 09 18:35:16 fedora kernel: PM: noirq resume of devices complete after 258.308 msecs
Nov 09 18:35:16 fedora kernel: PM: early resume of devices complete after 0.523 msecs
Nov 09 18:35:16 fedora kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
Nov 09 18:35:16 fedora kernel: pci 0000:00:00.2: PCI INT A: no GSI
Nov 09 18:35:16 fedora kernel: [drm] PCIE GART of 1024M enabled.
Nov 09 18:35:16 fedora kernel: [drm] PTB located at 0x000000F41FC00000
Nov 09 18:35:16 fedora kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
Nov 09 18:35:16 fedora kernel: amdgpu 0000:04:00.0: amdgpu: dpm has been disabled
Nov 09 18:35:16 fedora kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
Nov 09 18:35:16 fedora kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Nov 09 18:35:16 fedora kernel: [drm] JPEG decode initialized successfully.
Nov 09 18:35:16 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
Nov 09 18:35:16 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Nov 09 18:35:16 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Nov 09 18:35:16 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Nov 09 18:35:16 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Nov 09 18:35:16 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Nov 09 18:35:16 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Nov 09 18:35:16 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Nov 09 18:35:16 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
Nov 09 18:35:16 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
Nov 09 18:35:16 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
Nov 09 18:35:16 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
Nov 09 18:35:16 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
Nov 09 18:35:16 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
Nov 09 18:35:16 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
Nov 09 18:35:16 fedora kernel: nvme nvme0: 16/0/0 default/read/poll queues
Nov 09 18:35:16 fedora kernel: nvme nvme0: Ignoring bogus Namespace Identifiers
Nov 09 18:35:16 fedora kernel: PM: resume of devices complete after 274.997 msecs
Nov 09 18:35:16 fedora kernel: PM: resume devices took 0.275 seconds
Nov 09 18:35:16 fedora kernel: PM: Finishing wakeup.
Nov 09 18:35:16 fedora kernel: OOM killer enabled.
Nov 09 18:35:16 fedora kernel: Restarting tasks ... done.
Nov 09 18:35:16 fedora kernel: random: crng reseeded on system resumption
Nov 09 18:35:16 fedora kernel: PM: suspend exit

OK, so that didn't help. I've got another workaround you can try; but it might have some pretty negative consequences like lid wakeup won't work anymore. Try adding acpi.ec_no_wakeup=1 to your kernel command line.

Thank you very much for guiding us

It looks like with this parameter acpi.ec_no_wakeup=1 the 0xcf event is not triggered. Coile whine also stays, indicating that it might continues in this power state - longer periods will give a better conclusion though.

Nov 09 18:47:42 fedora kernel: PM: suspend entry (s2idle)
Nov 09 18:47:42 fedora kernel: Filesystems sync: 0.016 seconds
Nov 09 18:47:42 fedora kernel: PM: Preparing system for sleep (s2idle)
Nov 09 18:49:04 fedora kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Nov 09 18:49:04 fedora kernel: OOM killer disabled.
Nov 09 18:49:04 fedora kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Nov 09 18:49:04 fedora kernel: PM: Suspending system (s2idle)
Nov 09 18:49:04 fedora kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Nov 09 18:49:04 fedora kernel: queueing ieee80211 work while going to suspend
Nov 09 18:49:04 fedora kernel: PM: suspend of devices complete after 137.767 msecs
Nov 09 18:49:04 fedora kernel: PM: start suspend of devices complete after 137.945 msecs
Nov 09 18:49:04 fedora kernel: PM: suspend devices took 0.138 seconds
Nov 09 18:49:04 fedora kernel: PM: late suspend of devices complete after 0.647 msecs
Nov 09 18:49:04 fedora kernel: ACPI: EC: interrupt blocked
Nov 09 18:49:04 fedora kernel: PM: noirq suspend of devices complete after 46.850 msecs
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P000: LPI: required min power state:D3hot current power state:D0
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P000: LPI: Device not power manageable
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P001: LPI: required min power state:D3hot current power state:D0
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P001: LPI: Device not power manageable
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P002: LPI: required min power state:D3hot current power state:D0
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P002: LPI: Device not power manageable
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P003: LPI: required min power state:D3hot current power state:D0
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P003: LPI: Device not power manageable
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P004: LPI: required min power state:D3hot current power state:D0
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P004: LPI: Device not power manageable
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P005: LPI: required min power state:D3hot current power state:D0
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P005: LPI: Device not power manageable
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P006: LPI: required min power state:D3hot current power state:D0
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P006: LPI: Device not power manageable
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P007: LPI: required min power state:D3hot current power state:D0
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P007: LPI: Device not power manageable
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P008: LPI: required min power state:D3hot current power state:D0
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P008: LPI: Device not power manageable
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P009: LPI: required min power state:D3hot current power state:D0
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P009: LPI: Device not power manageable
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P00A: LPI: required min power state:D3hot current power state:D0
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P00A: LPI: Device not power manageable
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P00B: LPI: required min power state:D3hot current power state:D0
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P00B: LPI: Device not power manageable
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P00C: LPI: required min power state:D3hot current power state:D0
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P00C: LPI: Device not power manageable
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P00D: LPI: required min power state:D3hot current power state:D0
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P00D: LPI: Device not power manageable
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P00E: LPI: required min power state:D3hot current power state:D0
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P00E: LPI: Device not power manageable
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P00F: LPI: required min power state:D3hot current power state:D0
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PLTF.P00F: LPI: Device not power manageable
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PCI0.GPP0: LPI: required min power state:D3hot current power state:D3cold
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PCI0.GPP1: LPI: required min power state:D1 current power state:D0
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PCI0.GPP1: LPI: Device not power manageable
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PCI0.GPP2: LPI: required min power state:D1 current power state:D0
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PCI0.GPP2: LPI: Device not power manageable
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PCI0.GPP4: LPI: required min power state:D1 current power state:D0
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PCI0.GPP4: LPI: Device not power manageable
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PCI0.GPP4.WLAN: LPI: required min power state:D3hot current power state:D0
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PCI0.GPP4.WLAN: LPI: Device not power manageable
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PCI0.GPP6.NVME: LPI: required min power state:D3hot current power state:D3cold
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PCI0.GP17.VGA_: LPI: required min power state:D3hot current power state:D0
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PCI0.GP17.VGA_: LPI: Device not power manageable
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PCI0.GP17.AZAL: LPI: required min power state:D3hot current power state:D3hot
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: required min power state:D3hot current power state:D0
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: Constraint not met; min power state:D3hot current power state:D0
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PCI0.GP17.HDAU: LPI: required min power state:D3hot current power state:D0
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PCI0.GP17.HDAU: LPI: Device not power manageable
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PCI0.GP17.XHC0: LPI: required min power state:D3hot current power state:D3hot
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PCI0.GP17.XHC1: LPI: required min power state:D3hot current power state:D3hot
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PCI0.GP18.SATA: LPI: required min power state:D3hot current power state:D0
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PCI0.GP18.SATA: LPI: Device not power manageable
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PCI0.GP18.SAT1: LPI: required min power state:D3hot current power state:D0
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PCI0.GP18.SAT1: LPI: Device not power manageable
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 3 evaluation successful
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 2 evaluation successful
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 5 evaluation successful
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 7 evaluation successful
Nov 09 18:49:04 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 18:49:04 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:73f
Nov 09 18:49:04 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:9
Nov 09 18:49:04 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 18:49:04 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:ec1c8a80
Nov 09 18:49:04 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:5
Nov 09 18:49:04 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 18:49:04 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 09 18:49:04 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:4
Nov 09 18:49:04 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 18:49:04 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 09 18:49:04 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:7
Nov 09 18:49:04 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 18:49:04 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 09 18:49:04 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:6
Nov 09 18:49:04 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 18:49:04 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:1
Nov 09 18:49:04 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
Nov 09 18:49:04 fedora kernel: PM: suspend-to-idle
Nov 09 18:49:04 fedora kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02e0eb5
Nov 09 18:49:04 fedora kernel: Timekeeping suspended for 81.679 seconds
Nov 09 18:49:04 fedora kernel: PM: Triggering wakeup from IRQ 9
Nov 09 18:49:04 fedora kernel: PM: Triggering wakeup from IRQ 7
Nov 09 18:49:04 fedora kernel: ACPI: PM: ACPI non-EC GPE wakeup
Nov 09 18:49:04 fedora kernel: PM: resume from suspend-to-idle
Nov 09 18:49:04 fedora kernel: PM: Triggering wakeup from IRQ 0
Nov 09 18:49:04 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 18:49:04 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 09 18:49:04 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
Nov 09 18:49:04 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 09 18:49:04 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 09 18:49:04 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:8
Nov 09 18:49:04 fedora kernel: amd_pmc AMDI0005:00: Last suspend in deepest state for 82455352us
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 8 evaluation successful
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 3 evaluation successful
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 6 evaluation successful
Nov 09 18:49:04 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 4 evaluation successful
Nov 09 18:49:04 fedora kernel: ACPI: EC: interrupt unblocked
Nov 09 18:49:04 fedora kernel: PM: noirq resume of devices complete after 261.881 msecs
Nov 09 18:49:04 fedora kernel: asus_wmi: Unknown key code 0x7b
Nov 09 18:49:04 fedora kernel: asus_wmi: Unknown key code 0x7b
Nov 09 18:49:04 fedora kernel: asus_wmi: Unknown key code 0x7b
Nov 09 18:49:04 fedora kernel: PM: early resume of devices complete after 0.491 msecs
Nov 09 18:49:04 fedora kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
Nov 09 18:49:04 fedora kernel: pci 0000:00:00.2: PCI INT A: no GSI
Nov 09 18:49:04 fedora kernel: [drm] PCIE GART of 1024M enabled.
Nov 09 18:49:04 fedora kernel: [drm] PTB located at 0x000000F41FC00000
Nov 09 18:49:04 fedora kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
Nov 09 18:49:04 fedora kernel: amdgpu 0000:04:00.0: amdgpu: dpm has been disabled
Nov 09 18:49:04 fedora kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
Nov 09 18:49:04 fedora kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Nov 09 18:49:04 fedora kernel: [drm] JPEG decode initialized successfully.
Nov 09 18:49:04 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
Nov 09 18:49:04 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Nov 09 18:49:04 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Nov 09 18:49:04 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Nov 09 18:49:04 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Nov 09 18:49:04 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Nov 09 18:49:04 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Nov 09 18:49:04 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Nov 09 18:49:04 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
Nov 09 18:49:04 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
Nov 09 18:49:04 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
Nov 09 18:49:04 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
Nov 09 18:49:04 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
Nov 09 18:49:04 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
Nov 09 18:49:04 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
Nov 09 18:49:04 fedora kernel: nvme nvme0: 16/0/0 default/read/poll queues
Nov 09 18:49:04 fedora kernel: nvme nvme0: Ignoring bogus Namespace Identifiers
Nov 09 18:49:04 fedora kernel: PM: resume of devices complete after 273.779 msecs
Nov 09 18:49:04 fedora kernel: PM: resume devices took 0.274 seconds
Nov 09 18:49:04 fedora kernel: PM: Finishing wakeup.
Nov 09 18:49:04 fedora kernel: OOM killer enabled.
Nov 09 18:49:04 fedora kernel: Restarting tasks ... done.
Nov 09 18:49:04 fedora kernel: random: crng reseeded on system resumption
Nov 09 18:49:04 fedora kernel: PM: suspend exit

Event 0x7b seems to be received when either plugged in and out

lid close and open also still work with this.

In this Log we can't see those triggered events though: #2248 (comment 1630355)

I've got a theory on the cause of this. Can you please drop the workaround and try to revert f3986e86b2d8 ("drm/amdgpu: skipping SDMA hw_init and hw_fini for S0ix.")?

would this suffice? 0003-revert-f3986e86b2d8.patch

This seems to work so that when un-/plugging AC it stays suspended. Fans don't come up.

unplugged and re-plugged shortly after.

Nov 10 09:28:19 fedora kernel: PM: suspend entry (s2idle)
Nov 10 09:28:19 fedora kernel: Filesystems sync: 0.014 seconds
Nov 10 09:28:19 fedora kernel: PM: Preparing system for sleep (s2idle)
Nov 10 09:30:00 fedora kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Nov 10 09:30:00 fedora kernel: OOM killer disabled.
Nov 10 09:30:00 fedora kernel: Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done.
Nov 10 09:30:00 fedora kernel: PM: Suspending system (s2idle)
Nov 10 09:30:00 fedora kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Nov 10 09:30:00 fedora kernel: queueing ieee80211 work while going to suspend
Nov 10 09:30:00 fedora kernel: PM: suspend of devices complete after 128.942 msecs
Nov 10 09:30:00 fedora kernel: PM: start suspend of devices complete after 129.092 msecs
Nov 10 09:30:00 fedora kernel: PM: suspend devices took 0.129 seconds
Nov 10 09:30:00 fedora kernel: PM: late suspend of devices complete after 0.432 msecs
Nov 10 09:30:00 fedora kernel: ACPI: EC: interrupt blocked
Nov 10 09:30:00 fedora kernel: PM: noirq suspend of devices complete after 46.833 msecs
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P000: LPI: required min power state:D3hot current power state:D0
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P000: LPI: Device not power manageable
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P001: LPI: required min power state:D3hot current power state:D0
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P001: LPI: Device not power manageable
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P002: LPI: required min power state:D3hot current power state:D0
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P002: LPI: Device not power manageable
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P003: LPI: required min power state:D3hot current power state:D0
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P003: LPI: Device not power manageable
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P004: LPI: required min power state:D3hot current power state:D0
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P004: LPI: Device not power manageable
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P005: LPI: required min power state:D3hot current power state:D0
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P005: LPI: Device not power manageable
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P006: LPI: required min power state:D3hot current power state:D0
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P006: LPI: Device not power manageable
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P007: LPI: required min power state:D3hot current power state:D0
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P007: LPI: Device not power manageable
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P008: LPI: required min power state:D3hot current power state:D0
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P008: LPI: Device not power manageable
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P009: LPI: required min power state:D3hot current power state:D0
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P009: LPI: Device not power manageable
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P00A: LPI: required min power state:D3hot current power state:D0
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P00A: LPI: Device not power manageable
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P00B: LPI: required min power state:D3hot current power state:D0
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P00B: LPI: Device not power manageable
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P00C: LPI: required min power state:D3hot current power state:D0
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P00C: LPI: Device not power manageable
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P00D: LPI: required min power state:D3hot current power state:D0
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P00D: LPI: Device not power manageable
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P00E: LPI: required min power state:D3hot current power state:D0
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P00E: LPI: Device not power manageable
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P00F: LPI: required min power state:D3hot current power state:D0
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PLTF.P00F: LPI: Device not power manageable
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PCI0.GPP0: LPI: required min power state:D3hot current power state:D3cold
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PCI0.GPP1: LPI: required min power state:D1 current power state:D0
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PCI0.GPP1: LPI: Device not power manageable
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PCI0.GPP2: LPI: required min power state:D1 current power state:D0
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PCI0.GPP2: LPI: Device not power manageable
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PCI0.GPP4: LPI: required min power state:D1 current power state:D0
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PCI0.GPP4: LPI: Device not power manageable
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PCI0.GPP4.WLAN: LPI: required min power state:D3hot current power state:D0
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PCI0.GPP4.WLAN: LPI: Device not power manageable
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PCI0.GPP6.NVME: LPI: required min power state:D3hot current power state:D3cold
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PCI0.GP17.VGA_: LPI: required min power state:D3hot current power state:D0
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PCI0.GP17.VGA_: LPI: Device not power manageable
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PCI0.GP17.AZAL: LPI: required min power state:D3hot current power state:D3hot
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: required min power state:D3hot current power state:D0
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: Constraint not met; min power state:D3hot current power state:D0
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PCI0.GP17.HDAU: LPI: required min power state:D3hot current power state:D0
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PCI0.GP17.HDAU: LPI: Device not power manageable
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PCI0.GP17.XHC0: LPI: required min power state:D3hot current power state:D3hot
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PCI0.GP17.XHC1: LPI: required min power state:D3hot current power state:D3hot
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PCI0.GP18.SATA: LPI: required min power state:D3hot current power state:D0
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PCI0.GP18.SATA: LPI: Device not power manageable
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PCI0.GP18.SAT1: LPI: required min power state:D3hot current power state:D0
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PCI0.GP18.SAT1: LPI: Device not power manageable
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 3 evaluation successful
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 2 evaluation successful
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 5 evaluation successful
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 7 evaluation successful
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:73f
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:9
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:ec1c8a80
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:5
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:4
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:7
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:6
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:1
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
Nov 10 09:30:00 fedora kernel: PM: suspend-to-idle
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02e0eb5
Nov 10 09:30:00 fedora kernel: Timekeeping suspended for 23.540 seconds
Nov 10 09:30:00 fedora kernel: PM: Triggering wakeup from IRQ 9
Nov 10 09:30:00 fedora kernel: ACPI: EC: ACPI EC GPE status set
Nov 10 09:30:00 fedora kernel: ACPI: EC: ACPI EC GPE dispatched
Nov 10 09:30:00 fedora kernel: asus_wmi: Unknown key code 0x7b
Nov 10 09:30:00 fedora kernel: ACPI: EC: ACPI EC work flushed
Nov 10 09:30:00 fedora kernel: ACPI: PM: Rearming ACPI SCI for wakeup
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
Nov 10 09:30:00 fedora kernel: Timekeeping suspended for 19.882 seconds
Nov 10 09:30:00 fedora kernel: PM: Triggering wakeup from IRQ 9
Nov 10 09:30:00 fedora kernel: ACPI: EC: ACPI EC GPE status set
Nov 10 09:30:00 fedora kernel: ACPI: EC: ACPI EC GPE dispatched
Nov 10 09:30:00 fedora kernel: asus_wmi: Unknown key code 0xcf
Nov 10 09:30:00 fedora kernel: asus_wmi: Unknown key code 0x7b
Nov 10 09:30:00 fedora kernel: ACPI: EC: ACPI EC work flushed
Nov 10 09:30:00 fedora kernel: ACPI: PM: Rearming ACPI SCI for wakeup
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02e0eb5
Nov 10 09:30:00 fedora kernel: PM: Triggering wakeup from IRQ 9
Nov 10 09:30:00 fedora kernel: ACPI: EC: ACPI EC GPE status set
Nov 10 09:30:00 fedora kernel: ACPI: PM: Rearming ACPI SCI for wakeup
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02e0eb5
Nov 10 09:30:00 fedora kernel: Timekeeping suspended for 0.879 seconds
Nov 10 09:30:00 fedora kernel: PM: Triggering wakeup from IRQ 9
Nov 10 09:30:00 fedora kernel: ACPI: EC: ACPI EC GPE status set
Nov 10 09:30:00 fedora kernel: ACPI: EC: ACPI EC GPE dispatched
Nov 10 09:30:00 fedora kernel: ACPI: EC: ACPI EC work flushed
Nov 10 09:30:00 fedora kernel: ACPI: PM: Rearming ACPI SCI for wakeup
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02e0eb5
Nov 10 09:30:00 fedora kernel: PM: Triggering wakeup from IRQ 9
Nov 10 09:30:00 fedora kernel: ACPI: EC: ACPI EC GPE status set
Nov 10 09:30:00 fedora kernel: ACPI: PM: Rearming ACPI SCI for wakeup
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02e0eb5
Nov 10 09:30:00 fedora kernel: Timekeeping suspended for 55.999 seconds
Nov 10 09:30:00 fedora kernel: PM: Triggering wakeup from IRQ 7
Nov 10 09:30:00 fedora kernel: PM: Triggering wakeup from IRQ 9
Nov 10 09:30:00 fedora kernel: ACPI: PM: ACPI non-EC GPE wakeup
Nov 10 09:30:00 fedora kernel: PM: resume from suspend-to-idle
Nov 10 09:30:00 fedora kernel: PM: Triggering wakeup from IRQ 0
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:8
Nov 10 09:30:00 fedora kernel: amd_pmc AMDI0005:00: Last suspend in deepest state for 99864226us
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 8 evaluation successful
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 3 evaluation successful
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 6 evaluation successful
Nov 10 09:30:00 fedora kernel: ACPI: \_SB_.PEP_: _DSM function 4 evaluation successful
Nov 10 09:30:00 fedora kernel: ACPI: EC: interrupt unblocked
Nov 10 09:30:00 fedora kernel: PM: noirq resume of devices complete after 272.944 msecs
Nov 10 09:30:00 fedora kernel: PM: early resume of devices complete after 0.537 msecs
Nov 10 09:30:00 fedora kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
Nov 10 09:30:00 fedora kernel: pci 0000:00:00.2: PCI INT A: no GSI
Nov 10 09:30:00 fedora kernel: [drm] PCIE GART of 1024M enabled.
Nov 10 09:30:00 fedora kernel: [drm] PTB located at 0x000000F41FC00000
Nov 10 09:30:00 fedora kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
Nov 10 09:30:00 fedora kernel: amdgpu 0000:04:00.0: amdgpu: dpm has been disabled
Nov 10 09:30:00 fedora kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
Nov 10 09:30:00 fedora kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Nov 10 09:30:00 fedora kernel: [drm] JPEG decode initialized successfully.
Nov 10 09:30:00 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
Nov 10 09:30:00 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Nov 10 09:30:00 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Nov 10 09:30:00 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Nov 10 09:30:00 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Nov 10 09:30:00 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Nov 10 09:30:00 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Nov 10 09:30:00 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Nov 10 09:30:00 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
Nov 10 09:30:00 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
Nov 10 09:30:00 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
Nov 10 09:30:00 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
Nov 10 09:30:00 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
Nov 10 09:30:00 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
Nov 10 09:30:00 fedora kernel: amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
Nov 10 09:30:00 fedora kernel: nvme nvme0: 16/0/0 default/read/poll queues
Nov 10 09:30:00 fedora kernel: nvme nvme0: Ignoring bogus Namespace Identifiers
Nov 10 09:30:00 fedora kernel: PM: resume of devices complete after 275.697 msecs
Nov 10 09:30:00 fedora kernel: PM: resume devices took 0.276 seconds
Nov 10 09:30:00 fedora kernel: PM: Finishing wakeup.
Nov 10 09:30:00 fedora kernel: OOM killer enabled.
Nov 10 09:30:00 fedora kernel: Restarting tasks ... done.
Nov 10 09:30:00 fedora kernel: random: crng reseeded on system resumption
Nov 10 09:30:00 fedora kernel: PM: suspend exit

I can also confirm, with 0003-revert-f3986e86b2d8.patch applied, 36 minutes sleep session, around 35.3 minutes spent in deep sleep.

Edit: basically without any battery drain.

OK thanks. This is well understood now then. There is going to be a revert that goes up for that specific commit, but it's going to be part of a larger series. @agd5f can you make sure you tag this bug in the series too when it goes up?

@marcaux you can carry the revert locally but I'll warn you that if you have an aborted suspend for some reason it will be problematic.

It's happening again, with 0003-revert-f3986e86b2d8.patch applied.

I had a longer suspend session today, with very minimal battery drain, most of the time spent in the deepest state.

During the next suspend session, battery discharged from 95% to 81% in 2 hours, only 3 seconds spent in the deepest state. Logs are following:

nov 13 17:40:13 g14 kernel: PM: suspend entry (s2idle)
nov 13 17:40:13 g14 kernel: Filesystems sync: 0.009 seconds
nov 13 17:40:13 g14 kernel: PM: Preparing system for sleep (s2idle)
nov 13 19:55:01 g14 kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
nov 13 19:55:01 g14 kernel: OOM killer disabled.
nov 13 19:55:01 g14 kernel: Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done.
nov 13 19:55:01 g14 kernel: PM: Suspending system (s2idle)
nov 13 19:55:01 g14 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
nov 13 19:55:01 g14 kernel: PM: suspend of devices complete after 159.956 msecs
nov 13 19:55:01 g14 kernel: PM: start suspend of devices complete after 160.153 msecs
nov 13 19:55:01 g14 kernel: PM: late suspend of devices complete after 0.769 msecs
nov 13 19:55:01 g14 kernel: ACPI: EC: interrupt blocked
nov 13 19:55:01 g14 kernel: PM: noirq suspend of devices complete after 55.832 msecs
nov 13 19:55:01 g14 kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: Constraint not met; min power state:D3hot current power state:D0
nov 13 19:55:01 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 13 19:55:01 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 13 19:55:01 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:7
nov 13 19:55:01 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 13 19:55:01 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 13 19:55:01 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:6
nov 13 19:55:01 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 13 19:55:01 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:1
nov 13 19:55:01 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
nov 13 19:55:01 g14 kernel: PM: suspend-to-idle
nov 13 19:55:01 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02e0eb5
nov 13 19:55:01 g14 kernel: Timekeeping suspended for 1.787 seconds
nov 13 19:55:01 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 13 19:55:01 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 13 19:55:01 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 13 19:55:01 g14 kernel: asus_wmi: Unknown key code 0x7b
nov 13 19:55:01 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 13 19:55:01 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 13 19:55:01 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 13 19:55:01 g14 kernel: Timekeeping suspended for 0.875 seconds
nov 13 19:55:01 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 13 19:55:01 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 13 19:55:01 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 13 19:55:01 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 13 19:55:01 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 13 19:55:01 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 13 19:55:01 g14 kernel: Timekeeping suspended for 8080.999 seconds
nov 13 19:55:01 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 13 19:55:01 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 13 19:55:01 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 13 19:55:01 g14 kernel: asus_wmi: Unknown key code 0xcf
nov 13 19:55:01 g14 kernel: asus_wmi: Unknown key code 0x7b
nov 13 19:55:01 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 13 19:55:01 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 13 19:55:01 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02e0eb5
nov 13 19:55:01 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 13 19:55:01 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 13 19:55:01 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 13 19:55:01 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02e0eb5
nov 13 19:55:01 g14 kernel: Timekeeping suspended for 0.861 seconds
nov 13 19:55:01 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 13 19:55:01 g14 kernel: PM: Triggering wakeup from IRQ 7
nov 13 19:55:01 g14 kernel: ACPI: PM: ACPI non-EC GPE wakeup
nov 13 19:55:01 g14 kernel: PM: resume from suspend-to-idle
nov 13 19:55:01 g14 kernel: PM: Triggering wakeup from IRQ 0
nov 13 19:55:01 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 13 19:55:01 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 13 19:55:01 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
nov 13 19:55:01 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 13 19:55:01 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 13 19:55:01 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:8
nov 13 19:55:01 g14 kernel: amd_pmc AMDI0005:00: Last suspend in deepest state for 3013762us
nov 13 19:55:01 g14 kernel: ACPI: EC: interrupt unblocked
nov 13 19:55:01 g14 kernel: PM: noirq resume of devices complete after 1240.215 msecs
nov 13 19:55:01 g14 kernel: PM: early resume of devices complete after 0.513 msecs
nov 13 19:55:01 g14 kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
nov 13 19:55:01 g14 kernel: pci 0000:00:00.2: PCI INT A: no GSI
nov 13 19:55:01 g14 kernel: [drm] PCIE GART of 1024M enabled.
nov 13 19:55:01 g14 kernel: [drm] PTB located at 0x000000F41FC00000
nov 13 19:55:01 g14 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
nov 13 19:55:01 g14 kernel: amdgpu 0000:04:00.0: amdgpu: dpm has been disabled
nov 13 19:55:01 g14 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
nov 13 19:55:01 g14 kernel: nvme nvme0: 8/0/0 default/read/poll queues
nov 13 19:55:01 g14 kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
nov 13 19:55:01 g14 kernel: [drm] JPEG decode initialized successfully.
nov 13 19:55:01 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
nov 13 19:55:01 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
nov 13 19:55:01 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
nov 13 19:55:01 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
nov 13 19:55:01 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
nov 13 19:55:01 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
nov 13 19:55:01 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
nov 13 19:55:01 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
nov 13 19:55:01 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
nov 13 19:55:01 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
nov 13 19:55:01 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
nov 13 19:55:01 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
nov 13 19:55:01 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
nov 13 19:55:01 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
nov 13 19:55:01 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
nov 13 19:55:01 g14 kernel: usb 1-1: reset high-speed USB device number 2 using xhci_hcd
nov 13 19:55:01 g14 kernel: usb 2-1: reset SuperSpeed USB device number 2 using xhci_hcd
nov 13 19:55:01 g14 kernel: usb 1-1.1: reset high-speed USB device number 4 using xhci_hcd
nov 13 19:55:01 g14 kernel: usb 1-1.3: reset high-speed USB device number 6 using xhci_hcd
nov 13 19:55:01 g14 kernel: usb 2-1.2: reset SuperSpeed USB device number 3 using xhci_hcd
nov 13 19:55:01 g14 kernel: r8152 2-1.2:1.0: skip request firmware
nov 13 19:55:01 g14 kernel: r8152 2-1.2:1.0: load rtl8153b-2 v1 10/23/19 successfully
nov 13 19:55:01 g14 kernel: PM: resume of devices complete after 1558.889 msecs
nov 13 19:55:01 g14 kernel: PM: Finishing wakeup.
nov 13 19:55:01 g14 kernel: OOM killer enabled.
nov 13 19:55:01 g14 kernel: Restarting tasks ... done.
nov 13 19:55:01 g14 kernel: random: crng reseeded on system resumption
nov 13 19:55:01 g14 kernel: PM: suspend exit

OK, unfortunately that debug log doesn't have enough information to explain why that happened. If this is the same root cause as why the revert helps two registers will indicate it. Please add debugging patch to your testing kernel. Next time it happens share the log again and extra information will be added. 0001-Debugging-patch-to-check-XNACK0-XNACK1-during-s2idle.patch

Last suspend session logs, some 30 minutes, 9 seconds in the deepest state. No USB/HDMI/whatever attached to the laptop.

nov 15 08:03:00 g14 kernel: PM: suspend entry (s2idle)
nov 15 08:03:00 g14 kernel: Filesystems sync: 0.002 seconds
nov 15 08:03:00 g14 kernel: PM: Preparing system for sleep (s2idle)
nov 15 08:37:09 g14 kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
nov 15 08:37:09 g14 kernel: OOM killer disabled.
nov 15 08:37:09 g14 kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
nov 15 08:37:09 g14 kernel: PM: Suspending system (s2idle)
nov 15 08:37:09 g14 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
nov 15 08:37:09 g14 kernel: PM: suspend of devices complete after 163.123 msecs
nov 15 08:37:09 g14 kernel: PM: start suspend of devices complete after 163.297 msecs
nov 15 08:37:09 g14 kernel: PM: late suspend of devices complete after 0.631 msecs
nov 15 08:37:09 g14 kernel: ACPI: EC: interrupt blocked
nov 15 08:37:09 g14 kernel: PM: noirq suspend of devices complete after 56.336 msecs
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P000: LPI: required min power state:D3hot current power state:D0
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P000: LPI: Device not power manageable
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P001: LPI: required min power state:D3hot current power state:D0
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P001: LPI: Device not power manageable
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P002: LPI: required min power state:D3hot current power state:D0
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P002: LPI: Device not power manageable
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P003: LPI: required min power state:D3hot current power state:D0
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P003: LPI: Device not power manageable
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P004: LPI: required min power state:D3hot current power state:D0
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P004: LPI: Device not power manageable
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P005: LPI: required min power state:D3hot current power state:D0
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P005: LPI: Device not power manageable
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P006: LPI: required min power state:D3hot current power state:D0
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P006: LPI: Device not power manageable
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P007: LPI: required min power state:D3hot current power state:D0
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P007: LPI: Device not power manageable
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P008: LPI: required min power state:D3hot current power state:D0
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P008: LPI: Device not power manageable
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P009: LPI: required min power state:D3hot current power state:D0
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P009: LPI: Device not power manageable
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P00A: LPI: required min power state:D3hot current power state:D0
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P00A: LPI: Device not power manageable
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P00B: LPI: required min power state:D3hot current power state:D0
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P00B: LPI: Device not power manageable
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P00C: LPI: required min power state:D3hot current power state:D0
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P00C: LPI: Device not power manageable
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P00D: LPI: required min power state:D3hot current power state:D0
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P00D: LPI: Device not power manageable
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P00E: LPI: required min power state:D3hot current power state:D0
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P00E: LPI: Device not power manageable
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P00F: LPI: required min power state:D3hot current power state:D0
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PLTF.P00F: LPI: Device not power manageable
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PCI0.GPP0: LPI: required min power state:D3hot current power state:D3cold
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PCI0.GPP1: LPI: required min power state:D1 current power state:D0
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PCI0.GPP1: LPI: Device not power manageable
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PCI0.GPP2: LPI: required min power state:D1 current power state:D0
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PCI0.GPP2: LPI: Device not power manageable
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PCI0.GPP4: LPI: required min power state:D1 current power state:D0
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PCI0.GPP4: LPI: Device not power manageable
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PCI0.GPP4.WLAN: LPI: required min power state:D3hot current power state:D0
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PCI0.GPP4.WLAN: LPI: Device not power manageable
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PCI0.GPP6.NVME: LPI: required min power state:D3hot current power state:D3cold
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PCI0.GP17.VGA_: LPI: required min power state:D3hot current power state:D0
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PCI0.GP17.VGA_: LPI: Device not power manageable
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PCI0.GP17.AZAL: LPI: required min power state:D3hot current power state:D3hot
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: required min power state:D3hot current power state:D0
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: Constraint not met; min power state:D3hot current power state:D0
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PCI0.GP17.HDAU: LPI: required min power state:D3hot current power state:D0
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PCI0.GP17.HDAU: LPI: Device not power manageable
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PCI0.GP17.XHC0: LPI: required min power state:D3hot current power state:D3hot
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PCI0.GP17.XHC1: LPI: required min power state:D3hot current power state:D3hot
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PCI0.GP18.SATA: LPI: required min power state:D3hot current power state:D0
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PCI0.GP18.SATA: LPI: Device not power manageable
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PCI0.GP18.SAT1: LPI: required min power state:D3hot current power state:D0
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PCI0.GP18.SAT1: LPI: Device not power manageable
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 3 evaluation successful
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 2 evaluation successful
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 5 evaluation successful
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 7 evaluation successful
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:73f
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:9
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:ec1c7a80
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:5
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:4
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:7
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:6
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:402c00
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:2
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: SMU program 0 version is 64.44.0
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:1
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
nov 15 08:37:09 g14 kernel: PM: suspend-to-idle
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02e0eb5
nov 15 08:37:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: [drm] SMN xnack0: 0x0; xnack1: 0x0
nov 15 08:37:09 g14 kernel: Timekeeping suspended for 8.288 seconds
nov 15 08:37:09 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 15 08:37:09 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 15 08:37:09 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 15 08:37:09 g14 kernel: asus_wmi: Unknown key code 0x7b
nov 15 08:37:09 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 15 08:37:09 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 15 08:37:09 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 15 08:37:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: [drm] SMN xnack0: 0x0; xnack1: 0x0
nov 15 08:37:09 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 15 08:37:09 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 15 08:37:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: [drm] SMN xnack0: 0x0; xnack1: 0x0
nov 15 08:37:09 g14 kernel: Timekeeping suspended for 0.875 seconds
nov 15 08:37:09 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 15 08:37:09 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 15 08:37:09 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 15 08:37:09 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 15 08:37:09 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 15 08:37:09 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 15 08:37:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: [drm] SMN xnack0: 0x0; xnack1: 0x0
nov 15 08:37:09 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 15 08:37:09 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 15 08:37:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: [drm] SMN xnack0: 0x0; xnack1: 0x0
nov 15 08:37:09 g14 kernel: Timekeeping suspended for 2037.999 seconds
nov 15 08:37:09 g14 kernel: PM: Triggering wakeup from IRQ 34
nov 15 08:37:09 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 15 08:37:09 g14 kernel: PM: Triggering wakeup from IRQ 0
nov 15 08:37:09 g14 kernel: ACPI: PM: ACPI non-EC GPE wakeup
nov 15 08:37:09 g14 kernel: PM: resume from suspend-to-idle
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:8
nov 15 08:37:09 g14 kernel: amd_pmc AMDI0005:00: Last suspend in deepest state for 9633514us
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 8 evaluation successful
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 3 evaluation successful
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 6 evaluation successful
nov 15 08:37:09 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 4 evaluation successful
nov 15 08:37:09 g14 kernel: ACPI: EC: interrupt unblocked
nov 15 08:37:09 g14 kernel: PM: noirq resume of devices complete after 1271.244 msecs
nov 15 08:37:09 g14 kernel: PM: early resume of devices complete after 0.560 msecs
nov 15 08:37:09 g14 kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
nov 15 08:37:09 g14 kernel: pci 0000:00:00.2: PCI INT A: no GSI
nov 15 08:37:09 g14 kernel: [drm] PCIE GART of 1024M enabled.
nov 15 08:37:09 g14 kernel: [drm] PTB located at 0x000000F41FC00000
nov 15 08:37:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
nov 15 08:37:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: dpm has been disabled
nov 15 08:37:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
nov 15 08:37:09 g14 kernel: nvme nvme0: 8/0/0 default/read/poll queues
nov 15 08:37:09 g14 kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
nov 15 08:37:09 g14 kernel: [drm] JPEG decode initialized successfully.
nov 15 08:37:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
nov 15 08:37:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
nov 15 08:37:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
nov 15 08:37:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
nov 15 08:37:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
nov 15 08:37:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
nov 15 08:37:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
nov 15 08:37:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
nov 15 08:37:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
nov 15 08:37:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
nov 15 08:37:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
nov 15 08:37:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
nov 15 08:37:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
nov 15 08:37:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
nov 15 08:37:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
nov 15 08:37:09 g14 kernel: PM: resume of devices complete after 293.432 msecs
nov 15 08:37:09 g14 kernel: PM: Finishing wakeup.
nov 15 08:37:09 g14 kernel: OOM killer enabled.
nov 15 08:37:09 g14 kernel: Restarting tasks ... done.
nov 15 08:37:09 g14 kernel: random: crng reseeded on system resumption
nov 15 08:37:09 g14 kernel: PM: suspend exit

Another log with relatively small amount of deep sleep state:

nov 15 08:55:55 g14 kernel: PM: suspend entry (s2idle)
nov 15 08:55:55 g14 kernel: Filesystems sync: 0.007 seconds
nov 15 08:55:55 g14 kernel: PM: Preparing system for sleep (s2idle)
nov 15 09:47:04 g14 kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
nov 15 09:47:04 g14 kernel: OOM killer disabled.
nov 15 09:47:04 g14 kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
nov 15 09:47:04 g14 kernel: PM: Suspending system (s2idle)
nov 15 09:47:04 g14 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
nov 15 09:47:04 g14 kernel: PM: suspend of devices complete after 149.615 msecs
nov 15 09:47:04 g14 kernel: PM: start suspend of devices complete after 149.761 msecs
nov 15 09:47:04 g14 kernel: PM: late suspend of devices complete after 0.668 msecs
nov 15 09:47:04 g14 kernel: ACPI: EC: interrupt blocked
nov 15 09:47:04 g14 kernel: PM: noirq suspend of devices complete after 56.113 msecs
nov 15 09:47:04 g14 kernel: ACPI: \_SB_.PCI0.GPP0: LPI: required min power state:D3hot current power state:D3cold
nov 15 09:47:04 g14 kernel: ACPI: \_SB_.PCI0.GPP6.NVME: LPI: required min power state:D3hot current power state:D3cold
nov 15 09:47:04 g14 kernel: ACPI: \_SB_.PCI0.GP17.AZAL: LPI: required min power state:D3hot current power state:D3hot
nov 15 09:47:04 g14 kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: required min power state:D3hot current power state:D0
nov 15 09:47:04 g14 kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: Constraint not met; min power state:D3hot current power state:D0
nov 15 09:47:04 g14 kernel: ACPI: \_SB_.PCI0.GP17.XHC0: LPI: required min power state:D3hot current power state:D3hot
nov 15 09:47:04 g14 kernel: ACPI: \_SB_.PCI0.GP17.XHC1: LPI: required min power state:D3hot current power state:D3hot
nov 15 09:47:04 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 3 evaluation successful
nov 15 09:47:04 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 2 evaluation successful
nov 15 09:47:04 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 5 evaluation successful
nov 15 09:47:04 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 7 evaluation successful
nov 15 09:47:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 15 09:47:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 15 09:47:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:7
nov 15 09:47:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 15 09:47:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 15 09:47:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:6
nov 15 09:47:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 15 09:47:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:1
nov 15 09:47:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
nov 15 09:47:04 g14 kernel: PM: suspend-to-idle
nov 15 09:47:04 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02e0eb5
nov 15 09:47:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: [drm] SMN xnack0: 0x0; xnack1: 0x0
nov 15 09:47:04 g14 kernel: Timekeeping suspended for 47.539 seconds
nov 15 09:47:04 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 15 09:47:04 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 15 09:47:04 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 15 09:47:04 g14 kernel: asus_wmi: Unknown key code 0x7b
nov 15 09:47:04 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 15 09:47:04 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 15 09:47:04 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 15 09:47:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: [drm] SMN xnack0: 0x0; xnack1: 0x0
nov 15 09:47:04 g14 kernel: Timekeeping suspended for 0.866 seconds
nov 15 09:47:04 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 15 09:47:04 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 15 09:47:04 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 15 09:47:04 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 15 09:47:04 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 15 09:47:04 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 15 09:47:04 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 15 09:47:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: [drm] SMN xnack0: 0x0; xnack1: 0x0
nov 15 09:47:04 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 15 09:47:04 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 15 09:47:04 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 15 09:47:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: [drm] SMN xnack0: 0x0; xnack1: 0x0
nov 15 09:47:04 g14 kernel: Timekeeping suspended for 3019.999 seconds
nov 15 09:47:04 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 15 09:47:04 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 15 09:47:04 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 15 09:47:04 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 15 09:47:04 g14 kernel: ACPI: PM: Wakeup after ACPI Notify sync
nov 15 09:47:04 g14 kernel: PM: resume from suspend-to-idle
nov 15 09:47:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 15 09:47:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 15 09:47:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
nov 15 09:47:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 15 09:47:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 15 09:47:04 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:8
nov 15 09:47:04 g14 kernel: amd_pmc AMDI0005:00: Last suspend in deepest state for 48291960us
nov 15 09:47:04 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 8 evaluation successful
nov 15 09:47:04 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 3 evaluation successful
nov 15 09:47:04 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 6 evaluation successful
nov 15 09:47:04 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 4 evaluation successful
nov 15 09:47:04 g14 kernel: ACPI: EC: interrupt unblocked
nov 15 09:47:04 g14 kernel: PM: noirq resume of devices complete after 286.909 msecs
nov 15 09:47:04 g14 kernel: PM: early resume of devices complete after 0.568 msecs
nov 15 09:47:04 g14 kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
nov 15 09:47:04 g14 kernel: pci 0000:00:00.2: PCI INT A: no GSI
nov 15 09:47:04 g14 kernel: [drm] PCIE GART of 1024M enabled.
nov 15 09:47:04 g14 kernel: [drm] PTB located at 0x000000F41FC00000
nov 15 09:47:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
nov 15 09:47:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: dpm has been disabled
nov 15 09:47:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
nov 15 09:47:04 g14 kernel: nvme nvme0: 8/0/0 default/read/poll queues
nov 15 09:47:04 g14 kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
nov 15 09:47:04 g14 kernel: [drm] JPEG decode initialized successfully.
nov 15 09:47:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
nov 15 09:47:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
nov 15 09:47:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
nov 15 09:47:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
nov 15 09:47:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
nov 15 09:47:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
nov 15 09:47:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
nov 15 09:47:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
nov 15 09:47:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
nov 15 09:47:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
nov 15 09:47:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
nov 15 09:47:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
nov 15 09:47:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
nov 15 09:47:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
nov 15 09:47:04 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
nov 15 09:47:04 g14 kernel: PM: resume of devices complete after 296.173 msecs
nov 15 09:47:04 g14 kernel: PM: Finishing wakeup.
nov 15 09:47:04 g14 kernel: OOM killer enabled.
nov 15 09:47:04 g14 kernel: Restarting tasks ... done.
nov 15 09:47:04 g14 kernel: random: crng reseeded on system resumption
nov 15 09:47:04 g14 kernel: PM: suspend exit

And now a shorter suspend cycle, but most of the time spent in deep sleep:

nov 15 10:07:56 g14 kernel: PM: suspend entry (s2idle)
nov 15 10:07:56 g14 kernel: Filesystems sync: 0.007 seconds
nov 15 10:07:56 g14 kernel: PM: Preparing system for sleep (s2idle)
nov 15 10:22:19 g14 kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
nov 15 10:22:19 g14 kernel: OOM killer disabled.
nov 15 10:22:19 g14 kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
nov 15 10:22:19 g14 kernel: PM: Suspending system (s2idle)
nov 15 10:22:19 g14 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
nov 15 10:22:19 g14 kernel: PM: suspend of devices complete after 135.915 msecs
nov 15 10:22:19 g14 kernel: PM: start suspend of devices complete after 136.251 msecs
nov 15 10:22:19 g14 kernel: PM: late suspend of devices complete after 0.737 msecs
nov 15 10:22:19 g14 kernel: ACPI: EC: interrupt blocked
nov 15 10:22:19 g14 kernel: PM: noirq suspend of devices complete after 56.388 msecs
nov 15 10:22:19 g14 kernel: ACPI: \_SB_.PCI0.GPP0: LPI: required min power state:D3hot current power state:D3cold
nov 15 10:22:19 g14 kernel: ACPI: \_SB_.PCI0.GPP6.NVME: LPI: required min power state:D3hot current power state:D3cold
nov 15 10:22:19 g14 kernel: ACPI: \_SB_.PCI0.GP17.AZAL: LPI: required min power state:D3hot current power state:D3hot
nov 15 10:22:19 g14 kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: required min power state:D3hot current power state:D0
nov 15 10:22:19 g14 kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: Constraint not met; min power state:D3hot current power state:D0
nov 15 10:22:19 g14 kernel: ACPI: \_SB_.PCI0.GP17.XHC0: LPI: required min power state:D3hot current power state:D3hot
nov 15 10:22:19 g14 kernel: ACPI: \_SB_.PCI0.GP17.XHC1: LPI: required min power state:D3hot current power state:D3hot
nov 15 10:22:19 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 3 evaluation successful
nov 15 10:22:19 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 2 evaluation successful
nov 15 10:22:19 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 5 evaluation successful
nov 15 10:22:19 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 7 evaluation successful
nov 15 10:22:19 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 15 10:22:19 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 15 10:22:19 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:7
nov 15 10:22:19 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 15 10:22:19 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 15 10:22:19 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:6
nov 15 10:22:19 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 15 10:22:19 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:1
nov 15 10:22:19 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
nov 15 10:22:19 g14 kernel: PM: suspend-to-idle
nov 15 10:22:19 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 15 10:22:19 g14 kernel: amdgpu 0000:04:00.0: amdgpu: [drm] SMN xnack0: 0x0; xnack1: 0x0
nov 15 10:22:19 g14 kernel: Timekeeping suspended for 3.069 seconds
nov 15 10:22:19 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 15 10:22:19 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 15 10:22:19 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 15 10:22:19 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 15 10:22:19 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 15 10:22:19 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 15 10:22:19 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 15 10:22:19 g14 kernel: amdgpu 0000:04:00.0: amdgpu: [drm] SMN xnack0: 0x0; xnack1: 0x0
nov 15 10:22:19 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 15 10:22:19 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 15 10:22:19 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 15 10:22:19 g14 kernel: amdgpu 0000:04:00.0: amdgpu: [drm] SMN xnack0: 0x0; xnack1: 0x0
nov 15 10:22:19 g14 kernel: Timekeeping suspended for 858.993 seconds
nov 15 10:22:19 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 15 10:22:19 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 15 10:22:19 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 15 10:22:19 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 15 10:22:19 g14 kernel: ACPI: PM: Wakeup after ACPI Notify sync
nov 15 10:22:19 g14 kernel: PM: resume from suspend-to-idle
nov 15 10:22:19 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 15 10:22:19 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 15 10:22:19 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
nov 15 10:22:19 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 15 10:22:19 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 15 10:22:19 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:8
nov 15 10:22:19 g14 kernel: amd_pmc AMDI0005:00: Last suspend in deepest state for 860937163us
nov 15 10:22:19 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 8 evaluation successful
nov 15 10:22:19 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 3 evaluation successful
nov 15 10:22:19 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 6 evaluation successful
nov 15 10:22:19 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 4 evaluation successful
nov 15 10:22:19 g14 kernel: ACPI: EC: interrupt unblocked
nov 15 10:22:19 g14 kernel: PM: noirq resume of devices complete after 650.870 msecs
nov 15 10:22:19 g14 kernel: PM: early resume of devices complete after 0.576 msecs
nov 15 10:22:19 g14 kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
nov 15 10:22:19 g14 kernel: pci 0000:00:00.2: PCI INT A: no GSI
nov 15 10:22:19 g14 kernel: [drm] PCIE GART of 1024M enabled.
nov 15 10:22:19 g14 kernel: [drm] PTB located at 0x000000F41FC00000
nov 15 10:22:19 g14 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
nov 15 10:22:19 g14 kernel: amdgpu 0000:04:00.0: amdgpu: dpm has been disabled
nov 15 10:22:19 g14 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
nov 15 10:22:19 g14 kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
nov 15 10:22:19 g14 kernel: [drm] JPEG decode initialized successfully.
nov 15 10:22:19 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
nov 15 10:22:19 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
nov 15 10:22:19 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
nov 15 10:22:19 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
nov 15 10:22:19 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
nov 15 10:22:19 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
nov 15 10:22:19 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
nov 15 10:22:19 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
nov 15 10:22:19 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
nov 15 10:22:19 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
nov 15 10:22:19 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
nov 15 10:22:19 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
nov 15 10:22:19 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
nov 15 10:22:19 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
nov 15 10:22:19 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
nov 15 10:22:19 g14 kernel: nvme nvme0: 8/0/0 default/read/poll queues
nov 15 10:22:19 g14 kernel: PM: resume of devices complete after 299.659 msecs
nov 15 10:22:19 g14 kernel: PM: Finishing wakeup.
nov 15 10:22:19 g14 kernel: OOM killer enabled.
nov 15 10:22:19 g14 kernel: Restarting tasks ... done.
nov 15 10:22:19 g14 kernel: random: crng reseeded on system resumption
nov 15 10:22:19 g14 kernel: PM: suspend exit

Thanks for sharing those logs. That means there is a secondary problem to the thing reverting fixes. Can you describe more of the physical circumstances involved that leads to this? If it's not obvious from those we might need to add a layer of ACPI logging.

In general: no USB/HDMI/whatever connected to the laptop.

There are two use-cases:

• laptop on charger, suspended, lid closing, charger is removed a few seconds after the laptop is suspended,
• laptop on battery, suspended, lid closing.

Before we jump to the ACPI logging, please re-apply the above https://gitlab.freedesktop.org/drm/amd/uploads/e07ef11b930f18ac5df1e723e646461b/0001-platform-x86-amd-pmc-Add-a-workaround-for-s0i3-issue.patch. So should be 3 patches:

• Revert the problematic commit
• The debugging for those two registers over SMN
• That W/A patch I linked.

If it's still happening next we'll add ACPI debug logs.

All three patches applied. Had today around 15 suspend sessions, durations ranging from a few minutes up to 3 hours. According to the kernel logs, mostly in the deepest state. Should I post the logs of a few?

No need; let's wait until a log that fails again (if that happens).

FYI that 3rd patch has been submitted upstream.

Now this happened during last night's suspend again. This was the very first suspend session after a reboot:

nov 21 21:11:38 g14 kernel: PM: suspend entry (s2idle)
nov 21 21:11:38 g14 kernel: Filesystems sync: 0.001 seconds
nov 21 21:11:38 g14 kernel: PM: Preparing system for sleep (s2idle)
nov 22 06:34:09 g14 kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
nov 22 06:34:09 g14 kernel: OOM killer disabled.
nov 22 06:34:09 g14 kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
nov 22 06:34:09 g14 kernel: PM: Suspending system (s2idle)
nov 22 06:34:09 g14 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
nov 22 06:34:09 g14 kernel: PM: suspend of devices complete after 159.796 msecs
nov 22 06:34:09 g14 kernel: PM: start suspend of devices complete after 159.992 msecs
nov 22 06:34:09 g14 kernel: PM: late suspend of devices complete after 1.011 msecs
nov 22 06:34:09 g14 kernel: ACPI: EC: interrupt blocked
nov 22 06:34:09 g14 kernel: ccp 0000:04:00.2: Refused to change power state from D0 to D3hot
nov 22 06:34:09 g14 kernel: PM: noirq suspend of devices complete after 55.863 msecs
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P000: LPI: required min power state:D3hot current power state:D0
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P000: LPI: Device not power manageable
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P001: LPI: required min power state:D3hot current power state:D0
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P001: LPI: Device not power manageable
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P002: LPI: required min power state:D3hot current power state:D0
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P002: LPI: Device not power manageable
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P003: LPI: required min power state:D3hot current power state:D0
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P003: LPI: Device not power manageable
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P004: LPI: required min power state:D3hot current power state:D0
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P004: LPI: Device not power manageable
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P005: LPI: required min power state:D3hot current power state:D0
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P005: LPI: Device not power manageable
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P006: LPI: required min power state:D3hot current power state:D0
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P006: LPI: Device not power manageable
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P007: LPI: required min power state:D3hot current power state:D0
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P007: LPI: Device not power manageable
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P008: LPI: required min power state:D3hot current power state:D0
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P008: LPI: Device not power manageable
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P009: LPI: required min power state:D3hot current power state:D0
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P009: LPI: Device not power manageable
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P00A: LPI: required min power state:D3hot current power state:D0
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P00A: LPI: Device not power manageable
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P00B: LPI: required min power state:D3hot current power state:D0
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P00B: LPI: Device not power manageable
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P00C: LPI: required min power state:D3hot current power state:D0
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P00C: LPI: Device not power manageable
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P00D: LPI: required min power state:D3hot current power state:D0
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P00D: LPI: Device not power manageable
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P00E: LPI: required min power state:D3hot current power state:D0
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P00E: LPI: Device not power manageable
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P00F: LPI: required min power state:D3hot current power state:D0
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PLTF.P00F: LPI: Device not power manageable
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PCI0.GPP0: LPI: required min power state:D3hot current power state:D3cold
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PCI0.GPP1: LPI: required min power state:D1 current power state:D0
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PCI0.GPP1: LPI: Device not power manageable
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PCI0.GPP2: LPI: required min power state:D1 current power state:D0
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PCI0.GPP2: LPI: Device not power manageable
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PCI0.GPP4: LPI: required min power state:D1 current power state:D0
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PCI0.GPP4: LPI: Device not power manageable
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PCI0.GPP4.WLAN: LPI: required min power state:D3hot current power state:D0
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PCI0.GPP4.WLAN: LPI: Device not power manageable
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PCI0.GPP6.NVME: LPI: required min power state:D3hot current power state:D3cold
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PCI0.GP17.VGA_: LPI: required min power state:D3hot current power state:D0
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PCI0.GP17.VGA_: LPI: Device not power manageable
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PCI0.GP17.AZAL: LPI: required min power state:D3hot current power state:D3hot
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: required min power state:D3hot current power state:D0
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PCI0.GP17.ACP_: LPI: Constraint not met; min power state:D3hot current power state:D0
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PCI0.GP17.HDAU: LPI: required min power state:D3hot current power state:D0
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PCI0.GP17.HDAU: LPI: Device not power manageable
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PCI0.GP17.XHC0: LPI: required min power state:D3hot current power state:D3hot
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PCI0.GP17.XHC1: LPI: required min power state:D3hot current power state:D3hot
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PCI0.GP18.SATA: LPI: required min power state:D3hot current power state:D0
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PCI0.GP18.SATA: LPI: Device not power manageable
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PCI0.GP18.SAT1: LPI: required min power state:D3hot current power state:D0
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PCI0.GP18.SAT1: LPI: Device not power manageable
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 3 evaluation successful
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 2 evaluation successful
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 5 evaluation successful
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 7 evaluation successful
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:73f
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:9
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:ec1c7a80
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:5
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:4
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:7
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:6
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:402c00
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:2
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: SMU program 0 version is 64.44.0
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:1
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
nov 22 06:34:09 g14 kernel: PM: suspend-to-idle
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02e0eb5
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: [drm] SMN xnack0: 0x0; xnack1: 0x0
nov 22 06:34:09 g14 kernel: Timekeeping suspended for 12.338 seconds
nov 22 06:34:09 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 22 06:34:09 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 22 06:34:09 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 22 06:34:09 g14 kernel: asus_wmi: Unknown key code 0x7b
nov 22 06:34:09 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 22 06:34:09 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 22 06:34:09 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: [drm] SMN xnack0: 0x0; xnack1: 0x0
nov 22 06:34:09 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 22 06:34:09 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: [drm] SMN xnack0: 0x0; xnack1: 0x0
nov 22 06:34:09 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 22 06:34:09 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 22 06:34:09 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 22 06:34:09 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 22 06:34:09 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 22 06:34:09 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: [drm] SMN xnack0: 0x0; xnack1: 0x0
nov 22 06:34:09 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 22 06:34:09 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: [drm] SMN xnack0: 0x0; xnack1: 0x0
nov 22 06:34:09 g14 kernel: Timekeeping suspended for 0.872 seconds
nov 22 06:34:09 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 22 06:34:09 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 22 06:34:09 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 22 06:34:09 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 22 06:34:09 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 22 06:34:09 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: [drm] SMN xnack0: 0x0; xnack1: 0x0
nov 22 06:34:09 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 22 06:34:09 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02f0eb5
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: [drm] SMN xnack0: 0x0; xnack1: 0x0
nov 22 06:34:09 g14 kernel: Timekeeping suspended for 33720.999 seconds
nov 22 06:34:09 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 22 06:34:09 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 22 06:34:09 g14 kernel: ACPI: EC: ACPI EC GPE dispatched
nov 22 06:34:09 g14 kernel: asus_wmi: Unknown key code 0xcf
nov 22 06:34:09 g14 kernel: asus_wmi: Unknown key code 0x7b
nov 22 06:34:09 g14 kernel: ACPI: EC: ACPI EC work flushed
nov 22 06:34:09 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 22 06:34:09 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02e0eb5
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: [drm] SMN xnack0: 0x0; xnack1: 0x0
nov 22 06:34:09 g14 kernel: ACPI: EC: ACPI EC GPE status set
nov 22 06:34:09 g14 kernel: ACPI: PM: Rearming ACPI SCI for wakeup
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: SMU idlemask s0i3: 0xc02e0eb5
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: [drm] SMN xnack0: 0x0; xnack1: 0x0
nov 22 06:34:09 g14 kernel: Timekeeping suspended for 12.863 seconds
nov 22 06:34:09 g14 kernel: PM: Triggering wakeup from IRQ 9
nov 22 06:34:09 g14 kernel: PM: Triggering wakeup from IRQ 7
nov 22 06:34:09 g14 kernel: ACPI: PM: ACPI non-EC GPE wakeup
nov 22 06:34:09 g14 kernel: PM: resume from suspend-to-idle
nov 22 06:34:09 g14 kernel: PM: Triggering wakeup from IRQ 0
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:3
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_RESPONSE:1
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_ARGUMENT:0
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: AMD_PMC_REGISTER_MESSAGE:8
nov 22 06:34:09 g14 kernel: amd_pmc AMDI0005:00: Last suspend in deepest state for 24864164us
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 8 evaluation successful
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 3 evaluation successful
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 6 evaluation successful
nov 22 06:34:09 g14 kernel: ACPI: \_SB_.PEP_: _DSM function 4 evaluation successful
nov 22 06:34:09 g14 kernel: ACPI: EC: interrupt unblocked
nov 22 06:34:09 g14 kernel: PM: noirq resume of devices complete after 2220.220 msecs
nov 22 06:34:09 g14 kernel: PM: early resume of devices complete after 0.444 msecs
nov 22 06:34:09 g14 kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
nov 22 06:34:09 g14 kernel: pci 0000:00:00.2: PCI INT A: no GSI
nov 22 06:34:09 g14 kernel: [drm] PCIE GART of 1024M enabled.
nov 22 06:34:09 g14 kernel: [drm] PTB located at 0x000000F41FC00000
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: dpm has been disabled
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
nov 22 06:34:09 g14 kernel: nvme nvme0: 8/0/0 default/read/poll queues
nov 22 06:34:09 g14 kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
nov 22 06:34:09 g14 kernel: [drm] JPEG decode initialized successfully.
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
nov 22 06:34:09 g14 kernel: amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
nov 22 06:34:09 g14 kernel: usb 1-1: reset high-speed USB device number 2 using xhci_hcd
nov 22 06:34:09 g14 kernel: usb 2-1: reset SuperSpeed USB device number 2 using xhci_hcd
nov 22 06:34:09 g14 kernel: usb 1-1.1: reset high-speed USB device number 4 using xhci_hcd
nov 22 06:34:09 g14 kernel: usb 1-1.3: reset high-speed USB device number 6 using xhci_hcd
nov 22 06:34:09 g14 kernel: usb 2-1.2: reset SuperSpeed USB device number 3 using xhci_hcd
nov 22 06:34:09 g14 kernel: r8152 2-1.2:1.0: skip request firmware
nov 22 06:34:09 g14 kernel: r8152 2-1.2:1.0: load rtl8153b-2 v1 10/23/19 successfully
nov 22 06:34:09 g14 kernel: PM: resume of devices complete after 1699.466 msecs
nov 22 06:34:09 g14 kernel: PM: Finishing wakeup.
nov 22 06:34:09 g14 kernel: OOM killer enabled.
nov 22 06:34:09 g14 kernel: Restarting tasks ... done.
nov 22 06:34:09 g14 kernel: random: crng reseeded on system resumption
nov 22 06:34:09 g14 kernel: PM: suspend exit

The suspend session of right after this did work properly (log part shown):

nov 22 06:39:45 g14 kernel: PM: suspend entry (s2idle)
nov 22 07:39:07 g14 kernel: amd_pmc AMDI0005:00: Last suspend in deepest state for 3561962677us
nov 22 07:39:07 g14 kernel: PM: suspend exit

All subsequent suspend session did work fine today - until a reboot.

I've rebooted the laptop, the first suspend session had the problem (30 minutes, out of which 4 seconds spent in deepest state). Logs are here: https://pastebin.com/kBpR5XHh

The seconds suspend session seemed fine (16 minutes, 16 minutes spent in deepest state). However, the power led of the laptop did not start to blink, only faded a bit. Logs are here: https://pastebin.com/KmpKuv63

This should fix the sdma issue from an acpi event.

https://patchwork.freedesktop.org/patch/513654/

Can you guys please confirm?

Seems to be OK! First suspend after reboot, time spent in the deepest state is as expected:

dec 02 06:37:36 g14 kernel: PM: suspend entry (s2idle)
...
dec 02 07:40:37 g14 kernel: amd_pmc AMDI0005:00: Last suspend in deepest state for 3776434508us
...
dec 02 07:40:37 g14 kernel: PM: suspend exit

Detailed logs: https://pastebin.com/eBdZc5QX

Great, thanks! Looks good. This should merge for 6.2 and then backport to various stable kernels.

Just for completeness to document you're using basically a 6.1-rc7 kernel, my debugging patch to show XNACK registers and then this fix; right?

It's a 6.1-rc4 kernel, with the following patches applied:

• 0001-platform-x86-amd-pmc-Add-a-workaround-for-s0i3-issue.patch
• 0001-Debugging-patch-to-check-XNACK0-XNACK1-during-s2idle.patch
• https://patchwork.freedesktop.org/patch/513654/

Should I go a round with 6.1-rc7 as well? Maybe with other set of patches applied?

At least for me, I'd like to know if you actually need https://gitlab.freedesktop.org/drm/amd/uploads/e07ef11b930f18ac5df1e723e646461b/0001-platform-x86-amd-pmc-Add-a-workaround-for-s0i3-issue.patch for your hardware or not.

So to confirm it's really just this one patch helps your issue you can do it with 6.1-rc7 with just the patch on patchwork (agd5f/linux@b35a2a12 which is headed to 6.2 now).

Seems like 6.1-rc7 with only the https://patchwork.freedesktop.org/patch/513654/ patch is not enough (first suspend after boot):

dec 02 20:34:02 g14 kernel: PM: suspend entry (s2idle)
dec 02 20:54:00 g14 kernel: amd_pmc AMDI0005:00: Last suspend in deepest state for 9665190us
dec 02 20:54:00 g14 kernel: PM: suspend exit

Full suspend log: https://pastebin.com/4q9Wwu0c

Second suspend after boot looks good:

dec 02 20:57:48 g14 kernel: PM: suspend entry (s2idle)
dec 02 21:00:58 g14 kernel: amd_pmc AMDI0005:00: Last suspend in deepest state for 187633972us
dec 02 21:00:58 g14 kernel: PM: suspend exit

OK, good to know. So you're hitting both issues then and we need both fixes. Thanks!

Seems so. Now with https://gitlab.freedesktop.org/drm/amd/uploads/e07ef11b930f18ac5df1e723e646461b/0001-platform-x86-amd-pmc-Add-a-workaround-for-s0i3-issue.patch also applied, the first suspend is also working fine.

OK, thanks for confirming!

mentioned in issue #2171 (closed)

mentioned in commit agd5f/linux@fb949789

mentioned in commit agd5f/linux@b35a2a12

mentioned in commit agd5f/linux@bc21fe9a

Update on the status:

The amd-pmc half of it is merged in Linus' tree for 6.1: https://github.com/torvalds/linux/commit/e4678483f9bc400642bbc05c6b75a1b44bcb6c25

Alex queued up the other half of it (amdgpu) for a last 6.1 pull request, so this should be fixed for 6.1.

mentioned in issue #2292 (closed)

The other half is in master now, so this is now fixed in 6.1 final. Thanks for reporting it! https://github.com/torvalds/linux/commit/bc21fe9a5844c5bc8f7ec319b11d2671a94eb867

closed

Hi Mario While I am excited waiting for the next release of 6.1 for all the changes so far, I was wondering that my turbostat reported only 4 C-stats: busy, C1, C2, C3. I can see that my idle driver is actually "acpi_idle".

Is this normal on AMD platform? (I assumed that on Intel platform it will be intel_idle and turbostat will report more Cn)

Thanks Eric

Using acpi-cpufreq this is the expected behavior. When using amd-pstate you'll have more granularity available. Unfortunately recently there were changes in 6.1-rc7+ that will effectively disable amd-pstate by default.

This is because of some regressions with the default behavior for it on certain CPUs. If you want to enable it, you can use the kernel command line to do so.

There will be some new modes (EPP and guided) that are introduced to amd-pstate over the 6.2/6.3 timeframe. Depending on how those behave, the policy may be changed again to have it enabled by default in one of them.

Oh..... thanks a lot for explaining...

Using acpi-cpufreq this is the expected behavior. When using amd-pstate you'll have more granularity available.

On my ubuntu stock 5.19 kernel it is actually on amd-pstate (before EPP), but I get the same amount of info as if it is acpi-cpufreq (which is the one when running 6.1-rc7). And turbostat says it is on acpi_idle while the scaling driver is amd_pstate, but yeah I know that one is old now.

Unfortunately recently there were changes in 6.1-rc7+ that will disable effectively disable amd-pstate by default.

I wish I have asked you 2 hours earlier because I have literally spent last 2 hours trying to get amd-pstate working on 6.1-rc7 without luck. I should just go to bed back then:)

This is because of some regressions with the default behavior for it on certain CPUs. If you want to enable it, you can use the kernel command line to do so.

Unfortunately I couldn't figure out what these options are last two hours. But I think I will give up now and just wait for your s0ix fix to be released.

Again thank you.

Unfortunately I couldn't figure out what these options are last two hours. But I think I will give up now and just wait for your s0ix fix to be released.

amd_pstate=passive Here's the link for it: https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/kernel-parameters.txt#L6967

Oh I misunderstood... now I get it... because I thought EPP is being in 6.1 so I have to give it as "amd_pstate=active"

Thanks for pointing me to that document.

@superm1

After 6.1 release I just compiled it and tried it out today. I tried it with kernel parameter:

amd_pstate=passive pm_debug_messages amd_pmc.dyndbg

And I know for me the problem is not fixed. I tried with 120 seconds sleep and 5 hours sleep.

However, I have noticed that the Lenovo side actually never fixed their bios issue:

"ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.LPC0.EC0.HKEY.MSCB], AE_NOT_FOUND (20220331/psargs-330)"

which I am suspecting is (part of) the problem I have. I have contacted Mark on Lenovo support side regarding this.

I wanna know if you still want to see my logs (dmesg, turbostat and journal), or maybe even open an new issue since it may not be the same as this thread?

Sincerely Eric

If you're having problems on 6.1 still, it's something different. Let's see your own issue opened up. Use all the same log capture strategies from this bug please.

mentioned in issue #2296 (closed)

mentioned in commit nouveau@249011f4

mentioned in commit nouveau@2d997738