Bug 2427355

1. Please describe the problem:

Going into hibernate on my Framework 13 AMD Ryzen 5 340 just causes it to freeze.
Display is off, power button LED is on. System unresponsive.

Have to hold the power button to hard power off and boot up again.

Sometimes it seems like the image is there, so it can resume from hibernation after the hard power off. Not really sure of this behaviour.

Note: I run a custom kernel which allows for secure boot with hibernation.
And then my laptop is running suspend then hibernate on lid action close. Has been working great since kernel 6.14.x.

Follows this guide:
https://community.frame.work/t/guide-fedora-36-hibernation-with-enabled-secure-boot-and-full-disk-encryption-fde-decrypting-over-tpm2/25474

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

6.17.12-300.fc43.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 :

Yes. I believe the issue was introduced in 6.17.10.

See here:
https://github.com/torvalds/linux/commit/3925683515e93844be204381d2d5a1df5de34f31

And here:
https://community.frame.work/t/wake-from-suspend/76109/8


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

Boot kernel 6.17.12-300 or 6.17.10-300.

Begin hibernation.
It will freeze.

I also use suspend then hibernate - once it gets to hibernating after X time suspended it freezes.

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

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.
   
8. Additional notes

Compiling the kernel with this patch:
https://lore.kernel.org/amd-gfx/20251130014631.29755-1-superm1@kernel.org/

Solves the issue.


Reproducible: Always