| Summary: | Kernel does not boot on Gigabyte MP30-AR0 system (APM X-Gene 1) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ronald Maas <rmaas> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 25 | CC: | gansalmon, g.kaviyarasu, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, pbrobinson, rjones, rmaas, vanmeeuwen+fedora, yyc1992 |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | aarch64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-18 05:19: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: | |
|
Description
Ronald Maas
2016-04-01 15:36:51 UTC
> EFI stub: Booting Linux Kernel...
> EFI stub: Using DTB from configuration table
> EFI stub: Existing boot services and installing virtual address map...
> L3c Cache: 8MB
I had the same problem with the ArchLinux ARM kernel and then I realized that the issue I has is caused by having the wrong setting when adding the boot entry.
It seems that the answer to the question "Is an EFI Application?" should be "n" since it follows the question "File path of the EFI Application or the kernel" and "not an EFI Application" means it is kernel.
The message seems to be confusing (assuming my interpretation is right) but with this change I am able to see boot messages from the kernel now (my userspace is not properly set up yet so I can't say if this solves all my issues yet.)
Issue was not resolved in Fedora 24 Server beta ISO downloaded from https://dl.fedoraproject.org/pub/fedora-secondary/releases/test/24_Beta/Everything/aarch64/iso/Fedora-Everything-netinst-aarch64-24_Beta-1.2.iso I tried adding the following kernel options, but kernel failed to boot: console=ttyS0,115200 acpi=off console=ttyS0,115200 acpi=off Any advise what I can try to get kernel to boot properly? Another observation I has was that the default address setting does not support a big kernel image. At least for UBOOT, when I tried to load the kernel with the default boot sequence, the device tree overrides the kernel code causing the kernel to hang on boot. with the message mentioned above. Changing the load address solves this issue (although I haven't got it boot to userspace last time I tried it...) (In reply to Yichao Yu from comment #3) > Another observation I has was that the default address setting does not > support a big kernel image. At least for UBOOT, when I tried to load the > kernel with the default boot sequence, the device tree overrides the kernel > code causing the kernel to hang on boot. with the message mentioned above. > Changing the load address solves this issue (although I haven't got it boot > to userspace last time I tried it...) Booting with grub using uEFI (the only thing supported with the x-gene) you don't need to be setting any load address. This should be fixed with today's compose on uEFI. Please test https://dl.fedoraproject.org/pub/fedora-secondary/development/24/ (In reply to Peter Robinson from comment #5) > This should be fixed with today's compose on uEFI. Please test > > https://dl.fedoraproject.org/pub/fedora-secondary/development/24/ Problem still exists. This time added the following kernel parameters: console=ttyS0,115200 earlycon=uart8250,mmio32,0x1c020000 and was able to capture the kernel panic trace: http://pastebin.com/C6tx5MYe
> Problem still exists. This time added the following kernel parameters:
How are you booting this? I see you select EFI shell, then there's a bunch of garbage. Then I see:
Failed to set MokListRT: Invalid Parameter
Which leads me to believe you're using an old uEFI shim. Is this booting PXE from the network? If so you will need to update the shim/grub2 on your PXE server too to the one that ships on the ISO.
(In reply to Peter Robinson from comment #7) > > Problem still exists. This time added the following kernel parameters: > > How are you booting this? I see you select EFI shell, then there's a bunch > of garbage. Then I see: In UEFI shell I type the command: FS1:\EFI\BOOT\BOOTAA64.EFI This is the garbage you see as UEFI renders the whole line for each character I type. Detailed steps are listed in the initial post > > Failed to set MokListRT: Invalid Parameter > > Which leads me to believe you're using an old uEFI shim. Is this booting PXE > from the network? If so you will need to update the shim/grub2 on your PXE > server too to the one that ships on the ISO. I boot from USB drive. No network booting. Note the GRUB menu is working fine. When I select an entry from the menu, then the kernel blows up. If it is expecting a specific kernel parameter, then I can add it before booting and try again. Saw the same thing happening with RHEL aarch64 kernels too: https://bugzilla.redhat.com/show_bug.cgi?id=1337705 Ignore comment 9, the stack trace from that bug is quite different. However thanks for the tip for getting the right earlyprintk line for this hardware. *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is 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 24 kernel bugs. Fedora 24 has now been rebased to 4.7.4-200.fc24. 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 25, and are still experiencing this issue, please change the version to Fedora 25. If you experience different issues, please open a new bug report for those. Both Fedora 24 release version (Fedora-Everything-netinst-aarch64-24-1.1.iso) and Fedora 25 development (Fedora-Everything-netinst-aarch64-25-20161010.n.0.iso) do not boot. Reported problem has not been resolved. I updated Version field from 24 to 25 So on x-gene with latest upstream kernels you'll need the latest vendor firmware. Do you happen to have the version that you're running? The standard U-Boot firmware has been replaced by TianoCore UEFI using the steps described in: https://rwmj.wordpress.com/2016/03/08/gigabyte-mp30-ar0-flashing-uefi/ There is no official UEFI version available on the Gigabyte support site for MP30-AR0 - although it is available for a later model MP30-AR1. At the moment OpenSuse 42.1 works 100% stable with the current firmware, so therefore I have no plans to upgrade it any time soon. Ronald I was able to install the latest Fedora 25 RC 1.3 successfully after upgrading the TianoCore UEFI to the latest Gigabyte MP30-AR1 UEFI firmware. Only thing I needed to add the following kernel option because otherwise the graphical Anaconda UI was garbled on the AST2400 VGA adapter: console=ttyS0,115200 Then installation using both text mode and VNC worked fine. Thanks all for your help and suggestions. Links ----- Gigabyte UEFI firmware: http://download.gigabyte.us/FileList/BIOS/server_bios_mp30-ar1_f01.zip Fedora 25 RC 1.3 ISO: https://arm.koji.fedoraproject.org/compose/25/Fedora-25-20161117.0/compose/Server/aarch64/iso/Fedora-Server-dvd-aarch64-25-1.3.iso |