Because the issue is difficult to hit - and therefore bisect - I ended up using 10 VMs in a reboot loop. Turns out even with the latest edk2 source, I could hit a boot-time crash. So I dug a little deeper and found that the crash I'm seeing w/ latest edk2 is actually in shim code. We didn't yet build shim for arm64 in zesty, so it's likely not the same bug I reported here[*], so reported it in new bug 1928010.
[*] Although it is possible that the bug is in some common code that impacts both shim and GRUB (e.g. gnu-efi) -- 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/1675522 Title: arm64: Synchronous Exception at 0x00000000BBC129BC Status in edk2 package in Ubuntu: Confirmed Status in grub2 package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Bug description: I installed a KVM VM with the zesty beta server ISO. The install went well but, upon reboot, GRUB entered a Synchronous Exception loop after selecting the Ubuntu boot option. After killing qemu-system-aarch64 and restarting the VM, the system booted to a prompt w/o issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1675522/+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
