From: Michael Lawnick <ml.lawnick@gmx.de>
To: u-boot@lists.denx.de
Subject: Re: RFC: exclude partitions from efi_selftest
Date: Wed, 15 Sep 2021 17:06:09 +0200 [thread overview]
Message-ID: <76c02922-0be9-d80d-d853-aeefe3ea124c@gmx.de> (raw)
In-Reply-To: <08bac57f-e970-1ddf-3e3d-1f9c0415e74d@gmx.de>
Am 15.09.2021 um 13:36 schrieb Michael Lawnick:
> Am 15.09.2021 um 13:22 schrieb Heinrich Schuchardt:
>>
>>
>> Am 15. September 2021 12:54:06 MESZ schrieb Michael Lawnick <ml.lawnick@gmx.de>:
>>> Am 15.09.2021 um 12:42 schrieb Heinrich Schuchardt:
>>>
>>>> Could you, please send the complete output starting with 'bootefi selftest'.
>>>
>>> ASIM-CN10KAS> setenv efi_selftest block device
>>> ASIM-CN10KAS> bootefi selftest
>>>
>>> Testing EFI API implementation
>>>
>>> Selected test: 'block device'
>>>
>>> Setting up 'block device'
>>> Setting up 'block device' succeeded
>>>
>>> Executing 'block device'
>>> ** Unrecognized filesystem type **
>>
>> Is the FAT file system enabled in the configuration?
>
> No
>
>>
>>> lib/efi_selftest/efi_selftest_block_device.c(362):
>>> ERROR: Failed to open simple file system protocol
>>> lib/efi_selftest/efi_selftest.c(111):
>>> ERROR: Executing 'block device' failed
>>>
>>> Tearing down 'block device'
>>> Tearing down 'block device' succeeded
>>>
>>> Boot services terminated
>>>
>>> Summary: 1 failures
>
> Sorry Heinrich, I managed to send below part to only you, so I repeat
> for the group:
> What might be worth to be noted:
> We are working on U-Boot provided by Marvell for upcoming SoC based on
> ThunderX. It is rather up to main branch but not the latest version.
> Latest change from main:
> Author: Patrick Wildt <patrick@blueri.se>
> Date: Wed Oct 7 11:04:33 2020 +0200
> efi_loader: fix use after free in receive path
> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
>
> If you can give a list of relevant modules I can make comparison, but
> just updating everything to latest or comparing full source tree won't
> be possible.
>
We have 8 partitions of which no. 5 isn't initialized.
I have put a bunch of printf to the code and see that the execute() is
done exactly on the partition which is unknown, no other gets touched !?
--
KR
Michael
next prev parent reply other threads:[~2021-09-15 15:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 14:56 RFC: exclude partitions from efi_selftest Michael Lawnick
2021-09-14 15:57 ` Heinrich Schuchardt
2021-09-15 9:56 ` Michael Lawnick
2021-09-15 10:42 ` Heinrich Schuchardt
2021-09-15 10:54 ` Michael Lawnick
2021-09-15 11:22 ` Heinrich Schuchardt
2021-09-15 11:36 ` Michael Lawnick
2021-09-15 15:06 ` Michael Lawnick [this message]
2021-09-16 7:12 ` AKASHI Takahiro
2021-09-16 7:15 ` Michael Lawnick
2021-09-16 7:48 ` Michael Lawnick
2021-09-16 8:02 ` AKASHI Takahiro
2021-09-16 9:14 ` Michael Lawnick
2021-09-16 9:37 ` AKASHI Takahiro
2021-09-16 11:19 ` Michael Lawnick
2021-09-15 12:00 ` Mark Kettenis
2021-09-16 6:59 ` 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=76c02922-0be9-d80d-d853-aeefe3ea124c@gmx.de \
--to=ml.lawnick@gmx.de \
--cc=u-boot@lists.denx.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.