From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: u-boot@lists.denx.de, trini@konsulko.com, sjg@chromium.org,
ilias.apalodimas@linaro.org
Subject: Re: [PATCH v4 2/4] efi_loader: rename BOOTEFI_BOOTMGR to EFI_BOOTMGR
Date: Tue, 16 Jan 2024 10:43:19 +0900 [thread overview]
Message-ID: <ZaXfNy2V8y0N1o08@octopus> (raw)
In-Reply-To: <379beb70-c147-470d-ac45-ecc8c93a5f52@gmx.de>
On Mon, Jan 15, 2024 at 03:16:22PM +0100, Heinrich Schuchardt wrote:
> On 15.01.24 11:12, AKASHI Takahiro wrote:
> > On Mon, Jan 15, 2024 at 09:34:51AM +0100, Heinrich Schuchardt wrote:
> > > On 1/15/24 01:58, AKASHI Takahiro wrote:
> > > > On Sun, Jan 14, 2024 at 01:46:45PM +0100, Heinrich Schuchardt wrote:
> > > > > On 1/10/24 02:16, AKASHI Takahiro wrote:
> > > > > > At this point, EFI boot manager interfaces is fully independent from
> > > > > > bootefi command. So just rename the configuration parameter.
> > > > > >
> > > > > > Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
> > > > > > Reviewed-by: Simon Glass <sjg@chromium.org>
> > > > >
> > > > > This patch breaks the 'bootefi hello' command in
> > > > > qemu-riscv64_smode_defconfig and other QEMU defconfigs.
> > > >
> > > > What happened? Please elaborate details so that I can trace your issue.
> > > >
> > > > On my side, I didn't see any problem with "bootefi hello" on qemu-arm64
> > > > and moreover CI check (github pull request) didn't complain anything.
> > >
> > > The failures are logged in
> > > https://source.denx.de/u-boot/custodians/u-boot-efi/-/pipelines/19302
> >
> > In the logs for qemu-arm64, qemu-risc64 and maybe others as well,
> > I see the same error:
> > --- ---
> > ______________________________ test_efi_grub_net _______________________________
> > test/py/tests/test_efi_loader.py:188: in test_efi_grub_net
> > addr = fetch_tftp_file(u_boot_console, 'env__efi_loader_grub_file')
> > test/py/tests/test_efi_loader.py:136: in fetch_tftp_file
> > assert expected_text in output
> > E assert 'Bytes transferred = 520192' in "*** ERROR: `serverip' not set"
> > --- ---
> >
> > This seems to be the root cause and my commit will have nothing to do
> > with the problem.
> > Please check the test environment.
>
> You are looking at test_efi_grub_net. I referred to 'bootefi hello',
> i.e. test_efi_helloworld_builtin:
>
>
> ----------------------------- Captured stdout call
> -----------------------------
> => bootefi hello
>
> =>
>
>
> The command does not provide any output.
Ah, yeah, but
> Best regards
>
> Heinrich
>
>
> >
> > -Takahiro Akashi
> >
> > > I have pushed the tag failed_20240114 to
> > > https://source.denx.de/u-boot/custodians/u-boot-efi.git for analysis.
While I compiled this code and tried to run "bootefi hello",
I could not reproduce this issue, always seeing the right output
either on qemu-arm64 or sandbox64.
(I also invoked test_efi_loader/efi_helloworld_builtin locally,
but the test passed.)
So no clue.
-Takahiro Akashi
> > > Best regards
> > >
> > > Heinrich
>
next prev parent reply other threads:[~2024-01-16 1:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 1:16 [PATCH v4 0/4] cmd: bootefi: refactor the code for bootmgr AKASHI Takahiro
2024-01-10 1:16 ` [PATCH v4 1/4] efi_loader: split unrelated code from efi_bootmgr.c AKASHI Takahiro
2024-01-10 1:16 ` [PATCH v4 2/4] efi_loader: rename BOOTEFI_BOOTMGR to EFI_BOOTMGR AKASHI Takahiro
2024-01-14 12:46 ` Heinrich Schuchardt
2024-01-15 0:58 ` AKASHI Takahiro
2024-01-15 8:34 ` Heinrich Schuchardt
2024-01-15 10:12 ` AKASHI Takahiro
2024-01-15 14:16 ` Heinrich Schuchardt
2024-01-16 1:43 ` AKASHI Takahiro [this message]
2024-01-16 18:44 ` Heinrich Schuchardt
2024-01-17 0:40 ` AKASHI Takahiro
2024-01-10 1:16 ` [PATCH v4 3/4] net: tftp: remove explicit efi configuration dependency AKASHI Takahiro
2024-01-10 1:16 ` [PATCH v4 4/4] fs: " AKASHI Takahiro
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=ZaXfNy2V8y0N1o08@octopus \
--to=takahiro.akashi@linaro.org \
--cc=ilias.apalodimas@linaro.org \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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.