Bug 11940 - IPFire kernel 4.14.x does not boot on AWS ARM
Summary: IPFire kernel 4.14.x does not boot on AWS ARM
Status: CLOSED FIXED
Alias: None
Product: IPFire
Classification: Unclassified
Component: --- (show other bugs)
Version: 2
Hardware: unspecified Unspecified
: Will only affect a few users Crash
Assignee: Arne.F
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-28 13:30 UTC by Michael Tremer
Modified: 2021-10-23 11:32 UTC (History)
2 users (show)

See Also:


Attachments
Boot Log (3.23 KB, text/plain)
2018-11-28 13:30 UTC, Michael Tremer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Tremer 2018-11-28 13:30:33 UTC
Created attachment 646 [details]
Boot Log

The current aarch64 image does not boot on Amazon's new ARM-based VMs. See the attached log. The kernel does not seem to be able to come up.

This has been tested with kernel 4.14.72 and .83 and both show the same log output.
Comment 1 Peter Müller 2019-10-13 10:36:30 UTC
What is the status of this issue?
Comment 2 Michael Tremer 2019-10-13 13:27:23 UTC
(In reply to Peter Müller from comment #1)
> What is the status of this issue?

I didn't try again, because I did not think that it was worth investing the time.

Since we have a couple of updated kernels, I could try this again.
Comment 3 Michael Tremer 2019-10-14 11:12:19 UTC
I uploaded an image again today, but unfortunately there is not a single characters being shown on the serial console.

I have no idea how we can debug this.
Comment 4 Michael Tremer 2020-09-18 08:46:09 UTC
According to Mathew, this could have fixed it:

> https://lists.ipfire.org/pipermail/development/2020-September/008335.html

I tested this image on AWS this morning:

> https://nightly.ipfire.org/next/2020-09-17%2018:53:16%20+0000-b04f532f/aarch64/

And unfortunately did not even get the output from GRUB. Any idea what could have caused that?
Comment 5 Michael Tremer 2020-09-18 08:48:55 UTC
Okay, I was too impatient. After about 10 minutes, I got the same output as before. Last line is:

> EFI stub: Exiting boot services and installing virtual address map...
Comment 6 Peter Müller 2020-12-10 16:45:49 UTC
Since I am currently walking through Bugzilla again: Any news on this? :-)
Comment 7 Michael Tremer 2020-12-10 19:23:00 UTC
No, but since ARM on AWS is skyrocketing right now, I am interested in fixing this hopefully with the new kernel.
Comment 8 Michael Tremer 2020-12-14 14:22:24 UTC
> Loading Linux 4.14.211-ipfire ...
> Loading initial ramdisk ...
> EFI stub: Booting Linux Kernel...
> EFI stub: Using DTB from configuration table
> EFI stub: Exiting boot services and installing virtual address map...

This still does not boot.
Comment 9 Michael Tremer 2021-03-31 14:25:20 UTC
Today, AWS released serial console access for all instances. Unfortunately I do not see any output with core155. Not even the bootloader and I do not see it on the "system log" output anymore either.

Did we change anything?
Comment 10 Arne.F 2021-03-31 16:12:12 UTC
I think not.

Runs amazon the image in uEFI or legacy mode?

In uEFI mode the uEFI-firmware should redirect the output to the serial console and in legacy it should output on VGA and COM1 and first boot and you have to choose the correct menuentry to continue use serial port.
Comment 11 Michael Tremer 2021-03-31 16:13:16 UTC
I believe they are using EFI for ARM.

I am aware that I need to select something if I want to see the boot process, but shouldn’t I see GRUB?
Comment 12 Peter Müller 2021-10-23 11:32:37 UTC
I assume this has been fixed with Core Update 159 and Linux kernel 5.10.x

Please reopen, if necessary.