1. Please describe the problem:
System fails to resume from suspend on kernel 5.10.4. Monitors wake up but have a blank display and no input response or disk activity.
2. What is the Version-Release number of the kernel:
5.10.4-200.fc33.x86_64 (from https://koji.fedoraproject.org/koji/buildinfo?buildID=1663265)
3. Did it work previously in Fedora? If so, what kernel version did the issue
*first* appear? Old kernels are available for download at
Worked in 5.9.16-200.fc33.x86_64
4. Can you reproduce this issue? If so, please provide the steps to reproduce
the issue below:
Yes - just suspend and try to resume on this system (Asus PRIME H270-PRO motherboard, Core i5-7500 CPU)
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``:
n/a - 5.10 kernel test
6. Are you running any modules that not shipped with directly Fedora's kernel?:
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.
Used "echo 1 > /sys/power/pm_trace" prior to suspending. After failed resume and reset into the same kernel, saw this:
Dec 07 18:00:00 haswell kernel: PM: Magic number: 0:161:320
Dec 07 18:00:00 haswell kernel: platform microcode: hash matches
Dec 07 18:00:00 haswell kernel: tty tty45: hash matches
The microcode driver seems like a possible culprit.
Will attach kernel log from normal boot with this kernel.
Created attachment 1743984 [details]
dmesg from normal bootup
I have same issue with i7-9700K(UHD Graphics 630), ASRock Z390 Extreme4 baseboard.
5.9.16-200.fc33.x86_64 works fine.
I confirmed that linux 5.10.6 fixed this issue.
This patch fixed this issue. https://github.com/torvalds/linux/commit/3d5c5fdcee0f9a94deb0472e594706018b00aa31
Not seeing this problem anymore with kernel-5.10.6-200.fc33.x86_64 but I have also since upgraded to discrete graphics so I'm not testing the exact same config. However, it sounds like this is resolved from comments above.