Bug 1319083
| Summary: | boot fails with Synchronous Exception on aarch64 with grub2 built with gcc6 | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Paul Whalen <pwhalen> | ||||||||||
| Component: | grub2 | Assignee: | Peter Jones <pjones> | ||||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 24 | CC: | bcl, dan, jcm, lkundrak, mads, mjg59, msalter, pbrobinson, pjones, pwhalen | ||||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | aarch64 | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2016-08-21 02:23:19 UTC | Type: | Bug | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Bug Depends On: | 1335654 | ||||||||||||
| Bug Blocks: | 922257 | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Paul Whalen
2016-03-18 15:42:28 UTC
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 |