EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
grub2-unsigned (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Recent kernels emit the following error message when booting on arm64 platforms:
EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary
While this doesn't appear to cause any functional issues - and indeed, the kernel commit that added the error[*] says "We can deal with this, but let's check for this condition anyway", it is still likely to cause user concern.
[Test Case]
This issue can be reproduced by launching a VM with secure boot enabled on an arm64 machine running jammy, e.g.
lxc launch ubuntu:jammy testsb --vm -c security.
The message shows in early boot, so we need to connect to VM console to see the warning message:
lxc console testsb
With the fix, the kernel image loaded by grub will be 64k aligned and the warning message disappears as below:
BdsDxe: loading Boot0008 "ubuntu" from HD(15,GPT,
BdsDxe: starting Boot0008 "ubuntu" from HD(15,GPT,
EFI stub: Booting Linux Kernel...
EFI stub: UEFI Secure Boot is enabled.
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services...
EFI stub: UEFI Secure Boot is enabled.
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd082]
[ 0.000000] Linux version 5.15.0-91-generic (buildd@
For testing secure boot, refer to the following link for creating test key, enroll to shim and sign the test grub
https:/
[Fix]
https:/
[What Could Go Wrong]
no longer affects: | grub2-unsigned (Ubuntu) |
description: | updated |
description: | updated |
Changed in grub2 (Ubuntu): | |
status: | New → In Progress |
assignee: | nobody → dann frazier (dannf) |
Changed in grub2 (Ubuntu): | |
milestone: | none → ubuntu-20.04.4 |
Changed in grub2 (Ubuntu): | |
assignee: | dann frazier (dannf) → nobody |
Changed in grub2 (Ubuntu): | |
milestone: | ubuntu-20.04.4 → focal-updates |
tags: | added: rls-jj-incoming |
tags: | added: fr-2066 |
tags: | removed: rls-jj-incoming |
Changed in grub2 (Ubuntu Jammy): | |
milestone: | focal-updates → ubuntu-22.04-beta |
Changed in grub2 (Ubuntu Jammy): | |
status: | In Progress → Fix Released |
assignee: | gerald.yang (gerald-yang-tw) → nobody |
Changed in grub2-unsigned (Ubuntu): | |
status: | New → Fix Released |
Changed in grub2-unsigned (Ubuntu Jammy): | |
status: | New → Triaged |
I've experienced this after installing Impish host on Raspberry Pi 4 with an Impish VM. The VM was working correctly up until just a moment ago, as I type this, I've installed `linux- modules- extra-raspi in order to get usb serial adapters to work inside the virtual machine. The package installed normally and initrd was created normally as well. Upon reboot, the only thing I see is the error mentioned in this bug report (you can see it if you do: lxc start --attach) and the VM is spinning at 100% CPU but linux is not booting.