Bug 1654225
| Summary: | kernel fails to boot on edk2 (via efi stub) on arm (32bit). | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gerd Hoffmann <kraxel> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 28 | CC: | airlied, bskeggs, eauger, ewk, hdegoede, ichavero, itamar, jarodwilson, jglisse, john.j5live, jonathan, josef, kernel-maint, lersek, linville, mchehab, mjg59, steved | ||||
| Target Milestone: | --- | Keywords: | Reopened | ||||
| 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: | 2019-02-21 21:13: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: | |||||||
| Attachments: |
|
||||||
possibly this is something in edk2, so cc'ing Laszlo. Hi Gerd, (+Eric,) I think this is a duplicate of bug 1633328. Using virt-3.0+ machine types, if your 32-bit ARM guest kernel lacks LPAE, then you need to specify "-machine highmem=off" explicitly. In comment #0 you mention the "kernel-core" package. Can you perhaps retry with "kernel-lpae-core"? Thanks. *** This bug has been marked as a duplicate of bug 1633328 *** > In comment #0 you mention the "kernel-core" package. Can you perhaps retry
> with "kernel-lpae-core"? Thanks.
The lpae kernel crashes the same way, and "-machine highmem=off" doesn't help either.
OK, thanks; different issue then. I think I'll ask Ard to take a look; the backtrace might ring a bell with him. Ard suggests trying a backport of <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/firmware/efi?id=33412b8673135b18ea42beb7f5117ed0091798b6>. *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs. Fedora 28 has now been rebased to 4.20.5-100.fc28. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29. If you experience different issues, please open a new bug report for those. *********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously. |
Created attachment 1509423 [details] kernel log file Description of problem: $subject Version-Release number of selected component (if applicable): edk2-arm-20180815gitcb5f4f45ce-2.fc28.noarch kernel-core-4.19.3-200.fc28.armv7hl How reproducible: 100% Steps to Reproduce: #!/bin/sh # config qemu="qemu-system-arm" proc="cortex-a15" type="virt,accel=tcg,usb=off" code="/usr/share/edk2/arm/QEMU_EFI-pflash.raw" tmpl="/usr/share/edk2/arm/vars-template-pflash.raw" vars="$(mktemp ${TMPDIR-/tmp}/efi-vars-XXXXXXXX.raw)" # setup writable efi vars trap 'rm -f "$vars"' EXIT cp -v "$tmpl" "$vars" fwargs="" fwargs="$fwargs -drive file=${code},format=raw,if=pflash,readonly=on" fwargs="$fwargs -drive file=${vars},format=raw,if=pflash" kernel="/boot/vmlinuz-$(uname -r)" append="console=ttyAMA0 earlycon" set -ex $qemu -nographic \ -m 1G \ -machine ${type} \ -cpu ${proc} \ $fwargs \ \ -kernel "$kernel" \ -append "$append" \ \ "$@" Actual results: see attached log