Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1967147 - error: ../../grub-core/loader/arm64/linux.c:81:failed to load FDT
Summary: error: ../../grub-core/loader/arm64/linux.c:81:failed to load FDT
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 33
Hardware: aarch64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ARMTracker
TreeView+ depends on / blocked
 
Reported: 2021-06-02 13:55 UTC by Paul Whalen
Modified: 2022-07-01 10:48 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Paul Whalen 2021-06-02 13:55:57 UTC 
Description of problem:
After upgrading to the latest Fedora 33, mustang fails to boot with the error

error: ../../grub-core/loader/arm64/linux.c:81:failed to load FDT

None of the previous working kernels boot either. 

Booting with debugging the last messages:

kern/efi/fdt.c:38: found registered FDT @ 0x43fd2c5000
loader/efi/fdt.c:65: allocating 26028 bytes for fdt
kern/efi/mm.c:173: allocate_pages(1, 9, 0x7, 0x0000ffffffffffff) =
0x800000000000000e
"error: ../../grub-core/loader/arm64/linux.c:81:failed to load FDT."

From
https://github.com/rhboot/grub2/blob/fedora-33/grub-core/kern/efi/mm.c#L173

Version-Release number of selected component (if applicable):
grub2-2.06~rc1-2.fc33

How reproducible:
Almost always.
Comment 1 Javier Martinez Canillas 2021-06-02 14:24:34 UTC 
(In reply to Paul Whalen from comment #0)

[snip]

> kern/efi/mm.c:173: allocate_pages(1, 9, 0x7, 0x0000ffffffffffff) = 0x800000000000000e

This is the key debug message, this is:

kern/efi/mm.c:173: allocate_pages(GRUB_EFI_ALLOCATE_MAX_ADDRESS, GRUB_EFI_ACPI_RECLAIM_MEMORY, 0x7, 0x0000ffffffffffff) = GRUB_EFI_NOT_FOUND

according to the "Unified Extensible Firmware Interface (UEFI) Specification,
Version 2.9, March 2021" in the "EFI_BOOT_SERVICES.AllocatePages()" section,
this error message means:

"EFI_NOT_FOUND: The requested pages could not be found."

Now, I don't know if in this case is GRUB that's not choosing the correct Type, MemoryType
and address for the pages allocation or is the firmware to blame here that's not able to
fulfill the allocation requested by GRUB.
Comment 2 Peter Robinson 2021-06-02 15:27:28 UTC 
> kern/efi/mm.c:173: allocate_pages(GRUB_EFI_ALLOCATE_MAX_ADDRESS,
> GRUB_EFI_ACPI_RECLAIM_MEMORY, 0x7, 0x0000ffffffffffff) = GRUB_EFI_NOT_FOUND
> 
> according to the "Unified Extensible Firmware Interface (UEFI) Specification,
> Version 2.9, March 2021" in the "EFI_BOOT_SERVICES.AllocatePages()" section,
> this error message means:
> 
> "EFI_NOT_FOUND: The requested pages could not be found."
> 
> Now, I don't know if in this case is GRUB that's not choosing the correct
> Type, MemoryType
> and address for the pages allocation or is the firmware to blame here that's
> not able to
> fulfill the allocation requested by GRUB.

I'm guessing the DT blob might be put into memory in the wrong location, or the wrong memory address is passed or labeled incorrectly, by the firmware, AKA likely U-Boot
Comment 3 Jakub Čajka 2021-06-07 09:28:12 UTC 
I have also hit this, also on mustang, after update to the latest of f33. For me it seems to be always reproducible. I haven't been able to boot that system since the update.
Comment 4 Fedora Admin user for bugzilla script actions 2022-07-01 10:48:45 UTC 
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
Note You need to log in before you can comment on or make changes to this bug.