From: Ben Schneider <ben@bens.haus>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: Regressions <regressions@lists.linux.dev>,
Linux Efi <linux-efi@vger.kernel.org>,
Stable <stable@vger.kernel.org>, Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [REGRESSION] boot fails for EFI boot stub loaded by u-boot
Date: Wed, 31 Jan 2024 19:00:59 +0100 (CET) [thread overview]
Message-ID: <NpVfaMj--3-9@bens.haus> (raw)
In-Reply-To: <817366c2-33e0-4908-90ec-57c63e3eb471@canonical.com>
Oct 18, 2023, 09:17 by heinrich.schuchardt@canonical.com:
> On 10/18/23 10:34, Ard Biesheuvel wrote:
>
>> (cc Heinrich)
>>
>> Hello Ben,
>>
>> Thanks for the report.
>>
>> On Wed, 18 Oct 2023 at 03:19, Ben Schneider <ben@bens.haus> wrote:
>>
>>>
>>> Hi Ard,
>>>
>>> I have an ESPRESSObin Ultra (aarch64) that uses U-Boot as its bootloader. It shipped from the manufacturer with with v5.10, and I've been trying to upgrade. U-Boot supports booting Image directly via EFI (https://u-boot.readthedocs.io/en/latest/usage/cmd/bootefi.html), and I have been using it that way to successfully boot the system up to and including v6.0.19. However, v6.1 and v6.5 kernels fail to boot.
>>>
>>> When booting successfully, the following messages are displayed:
>>>
>>> EFI stub: Booting Linux Kernel...EFI stub: ERROR: FIRMWARE BUG: efi_loaded_image_t::image_base has bogus value
>>> EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary
>>> EFI stub: Using DTB from configuration table
>>> EFI stub: ERROR: Failed to install memreserve config table!
>>> EFI stub: Exiting boot services...
>>> [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
>>>
>>> I suspect many of the above error messages are simply attributable to using U-Boot to load an EFI stub and can be safely ignored given that the system boots and runs fine.
>>>
>
> These messages are not typical for launching a kernel via the EFI stub from U-Boot. It should look like this:
>
All, I can confirm that this issue is not present using upstream U-Boot (v2024.01). That is, EFI stub booting works as expected and does not display any error messages. Thanks!
Ben
#regzbot invalid: issue is with device firmware (u-boot)
prev parent reply other threads:[~2024-01-31 18:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 1:18 [REGRESSION] boot fails for EFI boot stub loaded by u-boot Ben Schneider
2023-10-18 8:34 ` Ard Biesheuvel
2023-10-18 9:17 ` Heinrich Schuchardt
2023-10-18 9:29 ` Ilias Apalodimas
2023-10-19 1:51 ` Ben Schneider
2023-10-19 7:21 ` Heinrich Schuchardt
2023-10-20 1:25 ` Ben Schneider
2023-10-21 0:07 ` Ben Schneider
2023-10-22 10:17 ` Heinrich Schuchardt
2024-01-31 18:00 ` Ben Schneider [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=NpVfaMj--3-9@bens.haus \
--to=ben@bens.haus \
--cc=ardb@kernel.org \
--cc=heinrich.schuchardt@canonical.com \
--cc=linux-efi@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.