Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
1. Please describe the problem:
Attempting to boot 5.11 kernels in qemu on armhfp fails with no output from the kernel.
2. What is the Version-Release number of the kernel:
5.11.rcX including the GA - 5.11.0-155.fc34
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 :
5.10 kernels boot fine.
4. Can you reproduce this issue? If so, please provide the steps to reproduce
the issue below:
Using an armhfp F33 uefi enabled disk image, upgrade to 5.11 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``:
Yes.
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.
Output before grub is displayed:
)/\EFI\fedora\grubarm.efi.
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B FE831EA8
Loading driver at 0x000FC262000 EntryPoint=0x000FC263000
Loading driver at 0x000FC262000 EntryPoint=0x000FC263000
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF FEDE8C90
ProtectUefiImageCommon - 0xFE831EA8
- 0x00000000FC262000 - 0x00000000001CA000
SetUefiImageMemoryAttributes - 0x00000000FC262000 - 0x0000000000001000 (0x0000000000004000)
SetUefiImageMemoryAttributes - 0x00000000FC263000 - 0x000000000001B000 (0x0000000000020000)
SetUefiImageMemoryAttributes - 0x00000000FC27E000 - 0x00000000001AE000 (0x0000000000004000)
BdsDxe: starting Boot0001 "Fedora" from HD(1,MBR,0xED670137,0x800,0x12C000)/\EFI\fedora\grubarm.efi
error: ../../grub-core/term/serial.c:217:serial port `com0' isn't found.
error: ../../grub-core/commands/terminal.c:138:terminal `serial' isn't found.
error: ../../grub-core/commands/terminal.c:138:terminal `serial' isn't found.
When booting the kernel:
EFI stub: Entering in SVC mode with MMU enabled
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services and installing virtual address map...
SetUefiImageMemoryAttributes - 0x00000000FF859000 - 0x0000000000006000 (0x0000000000000000)
SetUefiImageMemoryAttributes - 0x00000000FF852000 - 0x0000000000007000 (0x0000000000000000)
SetUefiImageMemoryAttributes - 0x00000000FF84C000 - 0x0000000000006000 (0x0000000000000000)
SetUefiImageMemoryAttributes - 0x00000000FF846000 - 0x0000000000006000 (0x0000000000000008)
SetUefiImageMemoryAttributes - 0x00000000FF83D000 - 0x0000000000009000 (0x0000000000000008)
SetUefiImageMemoryAttributes - 0x00000000FF831000 - 0x000000000000C000 (0x0000000000000008)
SetUefiImageMemoryAttributes - 0x00000000FF82B000 - 0x0000000000006000 (0x0000000000000008)
SetUefiImageMemoryAttributes - 0x00000000FF825000 - 0x0000000000006000 (0x0000000000000008)
Upstream fix:
https://www.spinics.net/lists/arm-kernel/msg876547.html
For F-34 it's fixed by the explicit config changes, tested and it's in kernel-5.11.0-156.fc34. There will be a little more review and a PR will be done for rawhide in the next day or so.