Bug 1624639

Summary:	grub2-efi-x64-2.02-52.fc29 fails to boot on Dell Latitude E6520
Product:	[Fedora] Fedora	Reporter:	Hans de Goede <hdegoede>
Component:	grub2	Assignee:	Peter Jones <pjones>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	29	CC:	fedora, lkundrak, pjones
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-03 08:03:37 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:

Description Hans de Goede 2018-09-02 18:22:55 UTC

After a fresh install of a recent F29 nightly on a Dell Latitude E6520 everything worked fine, until I did a dnf update and got grub2-efi-x64-2.02-52.fc29, after that I got the following errors on boot (and a non booting machine):

grub-core/loader/i386/efi/linux.c:217:cannot allocate kernel parameters.
grub-core/loader/i386/efi/linux.c:94:you need to load the kernel first.

This is a Sandy Bridge machine in UEFI mode.

Replacing /boot/efi/EFI/fedora/grubx64.efi with the binary from grub2-efi-x64-2.02-51.fc29 fixes this.

I suspect that this is caused by this change (from the spec changelog):

- Better allocation of kernel+initramfs on x86_64 and aarch64 Resolves: rhbz#1572126 

I can build my own grub binaries for testing, so if you've a patch to test, or just a patch to get more debugging info, let me know and I will give it a test-spin.

Comment 1 Thorsten Leemhuis 2018-09-03 08:03:37 UTC


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