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
Summary: | error: ../../grub-core/loader/arm64/linux.c:81:failed to load FDT | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Paul Whalen <pwhalen> |
Component: | grub2 | Assignee: | Javier Martinez Canillas <fmartine> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 33 | CC: | dan, dennis, fmartine, jcajka, jean, jordan, lkundrak, nrevo, ole.d, pbrobinson, pgnet.dev, pjones, pwhalen, rharwood |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | aarch64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-11-19 15:15:13 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: | |||
Bug Blocks: | 245418 |
Description
Paul Whalen
2021-06-02 13:55:57 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. > 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
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. This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Moving to das uboot per #c2. (In reply to Robbie Harwood from comment #7) > Moving to das uboot per #c2. Actually this isn't U-Boot as mustang doesn't use U-Boot. Although I believe it may now be fixed. Paul can you confirm? (In reply to Peter Robinson from comment #8) > (In reply to Robbie Harwood from comment #7) > > Moving to das uboot per #c2. > > Actually this isn't U-Boot as mustang doesn't use U-Boot. Although I believe > it may now be fixed. Paul can you confirm? Yes, no longer seeing this on any of the mustangs. Closing. |