Created attachment 1764958 [details] description of hardware - output from lshw 1. Please describe the problem: After one chooses 5.11.7 from the boot screen, the screen blanks and the computer is unresponsive. Some initial increase in fan noise suggests something was being attempted, but there is no other indication, not even logging output, as discussed below. 2. What is the Version-Release number of the kernel: 5.11.7-200.fc33.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 : The previous kernel 5.10.23-200.fc33.x86_64 still works as before when one chooses it from the boot screen. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: This issue occurs at each attempt to boot the 5.11.7 kernel. 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``: I have not yet tried this. I will attempt to do so. 6. Are you running any modules that not shipped with directly Fedora's kernel?: I do not believe so. 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. These commands do not yield any output from the attempt at booting the 5.11.7 kernel, only from the subsequent boot of the 5.10.23 kernel. I have looked at the files in /var/log and it appears that the attempts to boot the 5.11.7 kernel produce no logging output. In the files /var/log/boot.log /var/log/messages and /var/log/secure the messages jump from the final messages in the shutdown of the 5.10.23 kernel prior to the reboot to the first messages from the reboot of the 5.10.23 kernel after the attempt to boot 5.11.7, with no messages from between these points in time. In case it is useful, I attach a file with output from lshw (describing the hardware).
I attempted to try the latest Rawhide kernel as per point 5 above, but failed to do so, receiving the following error messages from dnf after downloading had completed: warning: /var/cache/dnf/rawhide-2d95c80a1fa0a67d/packages/kernel-5.12.0-0.rc3.20210319git8b12a62a4e3e.172.fc35.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID 9867c58f: NOKEY Fedora - Rawhide - Developmental packages for the 655 kB/s | 1.6 kB 00:00 GPG key at file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-33-x86_64 (0x9570FF31) is already installed The GPG keys listed for the "Fedora - Rawhide - Developmental packages for the next Fedora release" repository are already installed but they are not correct for this package. Check that the correct key URLs are configured for this repository.. Failing package is: kernel-5.12.0-0.rc3.20210319git8b12a62a4e3e.172.fc35.x86_64 GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-33-x86_64 Public key for kernel-core-5.12.0-0.rc3.20210319git8b12a62a4e3e.172.fc35.x86_64.rpm is not installed. Failing package is: kernel-core-5.12.0-0.rc3.20210319git8b12a62a4e3e.172.fc35.x86_64 GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-33-x86_64 Public key for kernel-modules-5.12.0-0.rc3.20210319git8b12a62a4e3e.172.fc35.x86_64.rpm is not installed. Failing package is: kernel-modules-5.12.0-0.rc3.20210319git8b12a62a4e3e.172.fc35.x86_64 GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-33-x86_64 The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'. Error: GPG check FAILED Given that these messages claim that the keys for the "Fedora - Rawhide - Developmental packages for the next Fedora release" repository are already installed but they are not correct for this package, I don't see how to fix this.
This seems to be a duplicate of bug 1936791, which is also about some HP AMD CPU systems not booting with 5.11. According to bug 1936791, adding "iommu=soft" to the kernel commandline helps to work around this, can you give this a try and confirm if that helps ?
Yes, thanks! Adding "iommu=soft" via the command sudo grubby --update-kernel=ALL --args="iommu=soft" as per your email (thanks very much!) does indeed appear to work around the problem on my computer. Reboot into kernel 5.11.7 then appears to proceed normally.
Ok, marking this a duplicate of bug 1936791 then. *** This bug has been marked as a duplicate of bug 1936791 ***