[Bug 1900774] Autopkgtest regression report (grub2/2.04-1ubuntu26.7)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted grub2 (2.04-1ubuntu26.7) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

ubuntu-image/1.10+20.04ubuntu1 (arm64)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#grub2

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1900774

Title:
  [arm64] EFI stub: ERROR: FIRMWARE BUG: efi_loaded_image_t::image_base
  has bogus value

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Committed
Status in grub2 source package in Bionic:
  Fix Committed
Status in grub2 source package in Focal:
  Fix Committed
Status in grub2 source package in Groovy:
  Fix Committed
Status in grub2 source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  When booting a kernel >= 5.7 via GRUB on an arm64 server, the EFI stub falsely reports a firmware bug:

  EFI stub: Booting Linux Kernel...
  EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied
  EFI stub: ERROR: FIRMWARE BUG: efi_loaded_image_t::image_base has bogus value
  EFI stub: Using DTB from configuration table
  EFI stub: Exiting boot services and installing virtual address map...
  [    0.000000] Booting Linux on physical CPU 0x0000000000 [0x431f0a10]

  [Test Case]
  Boot the arm64 groovy kernel, or any other kernel >= 5.7.
  Regression test on an EFI based x86 system (e.g. lxc --vm)

  [Fix]
  https://github.com/rhboot/grub2/commit/1d5ef08216edec4d31d0e10cfdb30b5ebfef7a45

  [Where Problems Could Occur]
  The fix is in GRUB's EFI loader, so problems would likely appear early in the boot of the kernel (during EFI stub processing).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1900774/+subscriptions