Greetings, Commit 5817d78eba34f6c86f5462ae2c5212f80a013357 (written by Mika Westerberg) causes regressions on resume from S3 suspend on my MSI X370 w/ Ryzen 7 1700, which is, TTBOMK, a PCI Express 3.0 platform. Consequences are hung disk and net I/O although re-login to GNOME works on 5.1.20, albeit very slowly. The machine is unusable after resume from that point. 5.2.5 and 5.3-rc2 will go into a tight loop of pcieport 0000:00:01.3: PME: Spurious native interrupt! and need to be rebooted. bad: v5.3-rc2 good: v5.3-rc2-111-g97b00aff2c45 + "git revert 5817d78eba" Reverting that commit shown above restores suspend functionality for me, two S3 suspend/resume cycles work. For details, more information (lspci, versions found) is at: * Kernel Bugzilla, https://bugzilla.kernel.org/show_bug.cgi?id=204413 * Fedora/Redhat Bugzilla, https://bugzilla.redhat.com/show_bug.cgi?id=1737046 Same findings for v5.2.5 on stable kernel, reverting the relevant commit (SHA is 5817d78eba34f6c86f5462ae2c5212f80a013357 there) also fixes suspend/resume problems for me. Let me know if you need me to pull out any further hardware or kernel debug info, but please be specific with instructions - I am not a kernel hacker (although I have been exposed to C for nearly 30 years and Linux/FreeBSD for some 20 years). Pointing me to relevant URLs with debug instructions is fine. I have a Git tree handy and this octocore sitting here compiles a kernel in < 10 minutes. Regards, Matthias
