Bug 1803706

Created attachment 1663479 [details]
kernel logs with three suspend/resume cycles: first one successful.

1. Please describe the problem:

Installed the 5.5.2 kernel for the Fedora Kernel Test Day and booted into it. After using it for some time, tried to suspend. First time works, subsequent attempts fail: system seems to power down for a second (screen goes dark, keyboard LEDs turn off), but then comes back on.

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

5.5.2-200.fc31.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 :

Suspend worked fine up to and including 5.3.16-300.fc31.x86_64. After that (5.4 series) it has been hit and miss. I cannot say too much about the 5.4 series, since they exhibited bug #1780800, which made the whole 5.4 series unusable for me.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

   1. Boot into 5.5.2 kernel.
   2. Log in (GNOME desktop).
   3. Press power button to suspend. First attempt usually works.
   4. Resume.
   5. Press power button to suspend again. System powers down for a second, then comes back on.

When manually turning off Bluetooth before suspending, this problem does not seem to occur. I tried to automate this with systemd triggers, but I end up in a hit and miss situation (sometimes it works, often it doesn't). This makes me suspect a timing issue... By manually disabling Bluetooth, there's a delay between turning off Bluetooth and starting the suspend cycle. Could this be a clue?

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``:

Not tested with rawhide.

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

No, only modules from kernel-core, kernel-modules, kernel-modules-extra

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.