Bug 1615969
| Summary: | AArch64 - Error when booting "error: out of memory." | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Paul Whalen <pwhalen> | ||||
| Component: | grub2 | Assignee: | Peter Jones <pjones> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 29 | CC: | awilliam, fzatlouk, gmarr, kevin, lkundrak, marc.c.dionne, pbrobinson, pjones, robatino | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | aarch64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | AcceptedBlocker | ||||||
| Fixed In Version: | grub2-2.02-52.fc29 grub2-2.02-57.fc29 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-09-12 02:54:03 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, 1517011 | ||||||
| Attachments: |
|
||||||
|
Description
Paul Whalen
2018-08-14 15:52:02 UTC
Created attachment 1475897 [details]
boot msgs
Testing with grub2-2.02-50.fc29: loader/arm64/linux.c:62: UEFI stub kernel: loader/arm64/linux.c:63: PE/COFF header @ 00000040 loader/arm64/linux.c:351: kernel file size: 24844800 loader/arm64/linux.c:354: kernel numpages: 6066 loader/arm64/linux.c:370: kernel @ 0x83fb020000 loader/efi/linux.c:44: shim_lock: 0x83fce316c8 loader/efi/linux.c:51: Asking shim to verify kernel signature loader/efi/linux.c:53: shim_lock->verify(): 0 loader/efi/linux.c:56: Kernel signature verification passed loader/arm64/linux.c:293: Loading initrd error: out of memory. Press any key to continue... kern/efi/fdt.c:38: found registered FDT @ 0x801fffc000 loader/efi/fdt.c:64: allocating 13575 bytes for fdt loader/arm64/linux.c:144: Installed/updated FDT configuration table @ 0x83fb01c000 loader/arm64/linux.c:200: linux command line: 'BOOT_IMAGE=(tftp)/fedora/Fedora-29-20180817.n.0/Everything/vmlinuz inst.repo=https://kojipkgs.fedoraproject.org/compose/branched//Fedora-29-201808 17.n.0/compose/Everything/aarch64/os/' loader/efi/linux.c:83: kernel_addr: 0x83fb020000 handover_offset: 0x1036004 params: 0x83fb020000 loader/efi/linux.c:85: handover_func() = 0x83fc056004 EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x411fd072] [ 0.000000] Linux version 4.18.1-300.fc29.aarch64 (mockbuild.fedoraproject.org) (gcc version 8.2.1 20180801 (Red Hat 8.2.1-2) (GCC)) #1 SMP Thu Aug 16 16:53:57 UTC 2018 Any more insights on this problem? I'm seeing roughly the same thing when trying to boot an OverDrive 1000: error: out of memory. Press any key to continue... EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x411fd072] [ 0.000000] Linux version 4.18.5-300.fc29.aarch64 (mockbuild.fedoraproject.org) (gcc version 8.2.1 20180801 (Red Hat 8.2.1-2) (GCC)) #1 SMP Fri Aug 24 17:18:34 UTC 2018 [ 0.000000] Machine model: SoftIron Overdrive 1000 (AMD Seattle (Rev.B1)) [ 0.000000] efi: Getting EFI parameters from FDT: [ 0.000000] efi: EFI v2.60 by SoftIron Overdrive 1000 ..... [ 1.924078] VFS: Cannot open root device "UUID=de35480d-3e54-4296-b171-77876ce9c976" or unknown-block(0,0): error -6 [ 1.934599] Please append a correct "root=" boot option; here are the available partitions: [ 1.942949] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Proposing as a blocker for F29 Beta, this breaks aarch64 installs. (In reply to Paul Whalen from comment #4) > Proposing as a blocker for F29 Beta, this breaks aarch64 installs. Paul, if I didn't miss anything, aarch64 is not a primary architecture and I guess this won't be accepted as a blocker because of that. https://fedoraproject.org/wiki/Architectures > Paul, if I didn't miss anything, aarch64 is not a primary architecture and I
> guess this won't be accepted as a blocker because of that.
ARM64 for Server is primary architecture and hence blocking as of F-28
+1 blocker. +1 blocker Voted as a blocker in-bug: The decision to classify this bug as an "AcceptedBlocker" (Beta) was made as it violates the following criteria: "The installer must run when launched normally from the release-blocking images." For reference grub2-2.02-52.fc29 fixes this for me. Will be on it's way to f29 updates-testing shortly Verified fixed in grub2-2.02-52.fc29 grub2-2.02-52.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-2756e3a374 FYI grub2-2.02-52.fc29 also fixes the boot problem for my aarch64 box. grub2-2.02-52.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-2756e3a374 grub2-2.02-52.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-2756e3a374 grub2-2.02-52.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-2756e3a374 Switching to VERIFIED as per Comment 11 . (In reply to František Zatloukal from comment #17) > Switching to VERIFIED as per Comment 11 . The update has been dropped due to issues with x86 grub2-2.02-54.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-2756e3a374 grub2-2.02-54.fc29 worked fine on x86_64 UEFI (VM). Can't test aarch64 though... grub2-2.02-54.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-2756e3a374 I did a couple of scratch builds of different possibilities to fix this while not regressing x86_64 UEFI. If folks with affected aarch64 systems could try them, it'd be great. Here they are: * https://koji.fedoraproject.org/koji/taskinfo?taskID=29603292 * https://koji.fedoraproject.org/koji/taskinfo?taskID=29603437 The first contains all the changes from -52, plus amartinez's fix for the x86_64 UEFI boot issue instead of Hans' that we shipped in -54. The second contains only the bits from -51, plus the change that was intended to fix *this* bug (and one other that is a precursor for it). Other changes were dropped. It'd be useful to know how both of these work compared to -51 and to -54. Thanks! (In reply to Adam Williamson from comment #22) > I did a couple of scratch builds of different possibilities to fix this > while not regressing x86_64 UEFI. If folks with affected aarch64 systems > could try them, it'd be great. Here they are: > > * https://koji.fedoraproject.org/koji/taskinfo?taskID=29603292 > * https://koji.fedoraproject.org/koji/taskinfo?taskID=29603437 > > The first contains all the changes from -52, plus amartinez's fix for the > x86_64 UEFI boot issue instead of Hans' that we shipped in -54. > > The second contains only the bits from -51, plus the change that was > intended to fix *this* bug (and one other that is a precursor for it). Other > changes were dropped. > > It'd be useful to know how both of these work compared to -51 and to -54. > Thanks! Both of those boot fine for me on my aarch64 box. For reference, -51 did not boot, -54 was ok. Thanks a lot. Can you also test pjones' -55 build? https://koji.fedoraproject.org/koji/buildinfo?buildID=1143536 Thanks again! grub2-2.02-55.fc29 working on mustang, seattle 2.02-55.fc29.aarch64 looks fine here pwhalen: does the 'minimal' build - https://koji.fedoraproject.org/koji/taskinfo?taskID=29603437 - work OK on your aarch64 systems? Thanks! (In reply to Adam Williamson from comment #27) > pwhalen: does the 'minimal' build - > https://koji.fedoraproject.org/koji/taskinfo?taskID=29603437 - work OK on > your aarch64 systems? Thanks! It does here, as I reported in comment #23 Marc: I know *you* reported success, I was looking for results from pwhalen as well :) Multiple tests is always good for safety. Adam, sorry, I interpreted the label incorrectly, thought you meant pwhalen was asking the question... :) No problem :) Sorry to be a pain, can you both also please test -56: https://koji.fedoraproject.org/koji/taskinfo?taskID=29618610 and check that still works? Thanks! -56 works fine for me adamw : 2.02-54.2.minimal working on the seattle 2.02-56.fc29 working on seattle and rpi3 Thanks a lot guys! grub2-2.02-54.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-2756e3a374 grub2-2.02-57.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. |