Description of problem: BOOTAA64.EFI fails with Synchronous Exception on aarch64 Version-Release number of selected component (if applicable): shim-unsigned-0.8-2.fc22 grub2-efi-2.02-0.27.fc24.aarch64 How reproducible: Everytime Steps to Reproduce: 1. Attempt an install of F24 using PXE or media on any hardware or virt (tested on Seattle, Mustang and QEMU) http://dl.fedoraproject.org/pub/fedora-secondary/development/24/Everything/aarch64/os/ Actual results: ..Failed to set MokListRT: Invalid Parameter Fetching Netboot Image Synchronous Exception at 0x00000043FA1AE4A8 0: FP 0x00000043FFA7EA80 SP 0x00000043FFA7EA80 PC 0x00000043FA1AF050 1: FP 0x00000043FFA7EAC0 SP 0x00000043FFA7EA90 PC 0x00000043FA1AF04C 2: FP 0x00000043FFA7EB00 SP 0x00000043FFA7EAD0 PC 0x00000043FA1AC470 3: FP 0x00000043FFA7EB10 SP 0x00000043FFA7EB10 PC 0x00000043FA1B4C78 4: FP 0x00000043FFA7EB60 SP 0x00000043FFA7EB20 PC 0x00000043FA6B0188 5: FP 0x00000043FFA7EC60 SP 0x00000043FFA7EB70 PC 0x00000043FA6B0218 6: FP 0x00000043FFA7EC90 SP 0x00000043FFA7EC70 PC 0x00000043FA6B102C 7: FP 0x00000043FFA7ECD0 SP 0x00000043FFA7ECA0 PC 0x00000043FA6AC174 8: FP 0x00000043FFA7ECF0 SP 0x00000043FFA7ECE0 PC 0x00000043FFA81BD0 9: FP 0x00000043FFA7ED40 SP 0x00000043FFA7ED00 PC 0x00000043FF99A2DC 10: FP 0x00000043FFA7EDA0 SP 0x00000043FFA7ED50 PC 0x00000043FF993D18 11: FP 0x00000043FFA7EDF0 SP 0x00000043FFA7EDB0 PC 0x00000043FF99388C 12: FP 0x00000043FFA7EE80 SP 0x00000043FFA7EE00 PC 0x00000043FF991D4C 13: FP 0x00000043FFA7EEF0 SP 0x00000043FFA7EE90 PC 0x00000043FFA7F7F4 14: FP 0x00000043FFA7EFE0 SP 0x00000043FFA7EF00 PC 0x00000043FFA7F270 Expected results: loads grub.cfg Additional info: using grubaa64.efi loaded grub.cfg
grub2-efi-2.02-0.27.fc24 was untagged on arm.koji, yesterdays (03212016) install media worked as expected. The resulting install did not boot with 'shim.efi' as noted in bz#1309147, failing to unpack the initrd. When replaced with 'grubaa64.efi' the system boots to log in on the mustang.
This was appeared to be a issue with 64K pages that was fixed in -302 kernel. http://pkgs.fedoraproject.org/cgit/rpms/kernel.git/diff/efi-arm64-don-t-apply-MEMBLOCK_NOMAP-to-UEFI-memory-map-mapping.patch?h=f24&id=2463f3be22278b3001e3e7a94ec88d658d80780d
Reopening, this is also happening with grub2-2.02-0.30.fc24 . Again I am able to boot with the 'grubaa64.efi', using the default 'shim.efi' results in a syncrhonous exception on both the mustang and seattle.
Adding Mark for his input.
When built with F23 tools, grub2-2.02-0.30 works as expected with no Synchronous Exception.
F23: http://arm.koji.fedoraproject.org/koji/taskinfo?taskID=3509029 F24: http://arm.koji.fedoraproject.org/koji/taskinfo?taskID=3509700 F23: binutils: 2.25-17.fc23 gcc: 5.3.1-6.fc23 elfutils: 0.166-1.fc23 F24: binutils: 2.26-14.fc24 gcc: 6.0.0-0.20.fc24 elfutils: 0.166-2.fc24
Created attachment 1148950 [details] F23 grub2 root.log The root.log install from the F23 scratch build
Created attachment 1148951 [details] F24 grub2 root.log The buildroot package install log for the F24 scratch
Created attachment 1148953 [details] F23 grub2 scratch build log The scratch build log built with gcc 5.3.1 on f23
Created attachment 1148954 [details] F24 grub2 scratch build log The scratch build log built with gcc 6 on f24
The shim does a bunch of relocation of the EFI (GRUB2) binary that's probably failing in handle_image. I've just started poking, but what I will do is instrument the code and see where it is falling over.
We determined that the shim had a bad patch and needed upgrading to a newer build. Pending update on status of that.
We're packaging shim for aarch64 separately so we don't need to keep it in lockstep for x86_64 or ia32. Review done, should be built today and in tomorrow's compose with luck.
Should be fixed in today's compose: https://dl.fedoraproject.org/pub/fedora-secondary/development/24/
Fixed