This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- eoan' to 'verification-done-eoan'. If the problem still exists, change the tag 'verification-needed-eoan' to 'verification-failed-eoan'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851810 Title: Some EFI systems fail to boot in efi_init() when booted via maas Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: In Progress Bug description: [Impact] Cirtain EFI systems will no longer boot with updated versions of maas. They will still boot in BIOS compatibility mode where available. [Test Case] Affected systems have already been tested with this fix applied and now boot successfully in EFI mode. The key test is does any EFI based system boot with this applied. [Regression Potential] The change increased the headroom by a very small amount, an additional 8 slots. This is very unlikely to lead to additional failures. === When booting via newer versions of maas we use grub extensions to load additional files. This leads the kernel to panic in efi_main(): exit_boot() failed! efi_main() failed! This occurs because the EFI memory map is more fragmented. When we exit boot services that returns an updated memory map in a buffer we supply. This has to be large enough to contain the updated map. If the exit fails because of lack of map space we are dead in the water because the call to allocate memory is lost to us. We therefore add some headroom in the allocation to allow for any expansion during close. This headroom is insufficient. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851810/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
