Bug 1853960

Created attachment 1699965 [details]
dmesg from bootup, suspend attempt

1. Please describe the problem:
My system (based on an Asus PRIME H270-PRO motherboard) fails to suspend properly under 5.7 kernels. It starts to suspend but then immediately wakes back up again.

I also noticed a bunch of PCIe AER error spam in dmesg that did not occur with 5.6-based kernels, for example:

[   12.909890] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
[   12.909890] pcieport 0000:00:1c.0: AER:   device [8086:a292] error status/mask=00003000/00002000
[   12.909891] pcieport 0000:00:1c.0: AER:    [12] Timeout               
[   12.909896] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[   12.909899] pcieport 0000:00:1c.0: AER: can't find device of ID00e0
[   12.909900] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[   12.909902] pcieport 0000:00:1c.0: AER: can't find device of ID00e0
[   12.909903] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[   12.909906] pcieport 0000:00:1c.0: AER: can't find device of ID00e0
[   12.910012] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[   12.910015] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
[   12.910015] pcieport 0000:00:1c.0: AER:   device [8086:a292] error status/mask=00001000/00002000
[   12.910016] pcieport 0000:00:1c.0: AER:    [12] Timeout               
[   12.910020] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[   12.910023] pcieport 0000:00:1c.0: AER: can't find device of ID00e0
[   12.910157] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:00:1c.0

Device 1c.0 is a PCI Express root port, which is connected to an ASMedia PCIe to PCI bridge:

00:1c.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #3 (rev f0)
02:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 04)

2. What is the Version-Release number of the kernel:

kernel-5.7.7-200.fc32.x86_64

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

kernel-5.7.6-201.fc32.x86_64 was the first version I have seen that had the problem. kernel-5.6.19-300.fc32.x86_64 works fine.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Fails every time on this system.

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

Have not tried

6. Are you running any modules that not shipped with directly Fedora's kernel?:

No

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.