Created attachment 2131179 [details] IOMMU errors. 1. Please describe the problem: I am testing the 6.19.3 kernel on my desktop PC and it is unbootable. I cannot get far enough to produce a journal log on Fedora as it just gives me a blank page after choosing the kernel from Grub. Note that Arch is on an nvme, I tested the nvme and it is healthy. Fedora is on a SATA SSD. I also have the a Ryzen 9800x3D and a 9070. Turning off IOMMU (or using IOMMU passthrough) allows the kernel to boot but obviously it isn't ideal. On Arch I get at least some messages, during the boot process, I am attaching a photo. I think this is probably an upstream issue. 2. What is the Version-Release number of the kernel: kernel-6.19.3-300.fc43 Koji build. 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 : 6.18 (all versions) work fine. Never had this issue before. 6.19.2 also had this issue. I also had it when I tried the release candidates for 6.19 before it became stable and I figured it would get fixed before it reached stable. Also please note a number of people on the CachyOS forums have reported this problem with their 6.19.* kernels. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Install kernel 6.19.3, boot from it. 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 used the koji build as stated above. 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. For Fedora the boot doesn't go far enough to produce logs. All logs I have are from successful 6.18.* boots. Please see attached photo from the Arch test.
I've just tried compiling 6.19.4 with this patch and then realised it was already in it: https://lore.kernel.org/lkml/20260227080638.208693-1-lkml@antheas.dev/ Then I proceeded with installing 6.19.5 (as it was already available), the kernel boots, you can see the patch at work here: [ 0.291995] pci 0000:00:14.3: iommu: identity mapping at addr 0x0 already exists, skipping [ 0.293152] AMD-Vi: Extended features (0x246577efa2254afa, 0x0): PPR NX GT [5] IA GA PC GA_vAPIC [ 0.293156] AMD-Vi: Interrupt remapping enabled [ 0.304951] AMD-Vi: Virtual APIC enabled [ 0.305012] perf/amd_iommu: Detected AMD IOMMU #0 (2 banks, 4 counters/bank). So this should be fixable by skipping to version 6.14 or patching 6.13.
Sorry one more update. I made the assumption that the patch that would fix this (listed earlier was applied upstream), but it was instead applied by the distro I was testing (CachyOS). The patch would need to be applied I believe, even with 6.19.5. Apologies still new to testing. I do want to clarify though that the bug WAS found on the Fedora kernel too, as I explained initially.
Proposed as a Blocker for 44-beta by Fedora user xariann using the blocker tracking app because: The current Fedora 44 Beta RC-1.2 has the kernel 6.19.2. After testing it with a live USB stick, I cannot boot it due to the bug I reported in Bugzilla. This will make it so a portion of the user base won't be able to boot the kernel without turning off IOMMU. There were a number of people in the CachyOS forums with this issue (as they released 6.19 as soon as it came out), so while it might not be the majority, but it is spread enough even with people who do not have my exact hardware: https://discuss.cachyos.org/t/boot-freeze-hang-on-linux-cachyos-6-19-0-2/22963 6.19.3 and 6.19.5 also didn't boot for me (this is from the Arch versions). CachyOS has patched their 6.19.5 and that boots. The patch that should fix this is also included in my BugZilla report.
Hi, I have a similar issue with the new kernel 6.18.16-200 on Fedora 43. It fails to mount my (LUKS-encrypted) root partition. Booting the older kernel works just fine. I haven't looked into the logs because I could not even open a shell ("root account is locked"). Maybe it has saved it somewhere but I have no idea.
Heya! I don't think it's the same issue. I boot that kernel fine. The fact that you can get that far to me suggests it is a different problem. What error do you get above “Cannot open access to console, the root account is locked.”? Can you take a photo? Try to boot again with the problem kernel, then boot back to the fallback kernel and gather the log of the previous boot with: `journalctl -b -1 -p err`. Then we can know for sure, but I am fairly positive that this is a different error and might need a different bug report.
Hi, I had already removed the newer kernel thus the system will not try to load it. Now I reinstalled it to get the logs with the command you posted. And well, it suddenly booted up just fine! I guess something went wrong during the previous installation. I have no clue how and why, but it does work now. Thank you anyways!
No worries, glad it sorted itself out. If I had a guess your intramfs didn't regenerate properly when you first installed it.
(In reply to Fedora Blocker Bugs Application from comment #3) > Proposed as a Blocker for 44-beta by Fedora user xariann Beta is already approved, moving your nomination to Final
Thanks! Sorry still a new tester. Would like to add that 6.19.6 also doesn't boot, same problem. This is the current kernel on the testing repos.
Discussed in a blocker review meeting [1] on 2026-03-09. The outcome was: !agreed 2443049 - punt (delay decision) - there's some uncertainty around just how many systems are affected by this. we'll delay the decision for a bit to see how feedback looks after the public Beta release, and maybe see if the fix lands in the kernel (making the decision irrelevant) [1] https://meetbot-raw.fedoraproject.org//blocker-review_matrix_fedoraproject-org/
FEDORA-2026-b9bd91408a (kernel-6.19.7-300.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-b9bd91408a
FEDORA-2026-21a28a358f (kernel-6.19.7-100.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2026-21a28a358f
FEDORA-2026-2f3dbc95bc (kernel-6.19.7-200.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-2f3dbc95bc
*** Bug 2447102 has been marked as a duplicate of this bug. ***
FEDORA-2026-b9bd91408a has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-b9bd91408a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-b9bd91408a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-2f3dbc95bc has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-2f3dbc95bc` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-2f3dbc95bc See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-21a28a358f has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-21a28a358f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-21a28a358f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
I will test this properly and provide feedback on bodhi, but I just wanted to say that I installed it this morning and it works. PC boots with IOMMU on. Bear in mind that the beta image is still shipping with 6.19.2 at the moment so I had to install it with IOMMU off at first.
Thanks for feedback, Xariann.
After my system not booting with 6.19.6, I can confirm that the 6.19.7 build on bodhi fixes this issue using fedora ostree
FEDORA-2026-b9bd91408a (kernel-6.19.7-300.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-2f3dbc95bc (kernel-6.19.7-200.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-21a28a358f (kernel-6.19.7-100.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.