Bug 1362257

Summary:	System hang after emitting "System BootOrder not found. Initializing defaults"
Product:	[Fedora] Fedora	Reporter:	Dan Williams <dan.j.williams>
Component:	shim	Assignee:	Matthew Garrett <mjg59>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	24	CC:	drjones, elliott, extras-qa, lersek, mjg59, pjones, rjones, vishal.l.verma
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1196114	Environment:
Last Closed:	2016-10-27 11:54:21 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:	1196114
Bug Blocks:

Description Dan Williams 2016-08-01 18:17:29 UTC

+++ This bug was initially created as a clone of Bug #1196114 +++

System startup hangs after fallback.efi appears to cause an invalid memory access.  The UEFI assert mentioned in bz#1196114:

    "ASSERT .../MdeModulePkg/Core/Dxe/Mem/Pool.c(488): Tail->Signature == ((('p') | ('t' << 8)) | ((('a') | ('l' << 8)) << 16))"

...is reproducible on other EFI platforms.

The hang can be reproduced by installing Fedora 24 onto a qemu Linux VM in EFI mode [1].

[1]: https://fedoraproject.org/wiki/Using_UEFI_with_QEMU

Comment 1 Dan Williams 2016-08-02 15:07:15 UTC

Tagging Peter for info as package administrator.

I'll note that if I extract the fallback.efi binary out of the CentOS 7 build of the shim package and place it on the target image it resolves the problem.

The version from CentOS is v0.9 while Fedora is back at v0.8, so it seems like all we need is to synchronize Fedora on v0.9.

Comment 2 Laszlo Ersek 2016-10-27 11:54:21 UTC

Dan, I changed the Hardware field on clone-origin bug 1196114 to "All", and I also bumped the Version field to 24 there. Please see bug 1196114 comment 16 as well.

With that, these two bugs are now identical, so I'm closing this one as a duplicate. Thanks.

*** This bug has been marked as a duplicate of bug 1196114 ***