From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>,
ml.lawnick@gmx.de, sjg@chromium.org, u-boot@lists.denx.de
Subject: Re: RFC: exclude partitions from efi_selftest
Date: Thu, 16 Sep 2021 15:59:21 +0900 [thread overview]
Message-ID: <20210916065921.GA59501@laputa> (raw)
In-Reply-To: <56145f9882899efe@bloch.sibelius.xs4all.nl>
On Wed, Sep 15, 2021 at 02:00:31PM +0200, Mark Kettenis wrote:
> > Date: Wed, 15 Sep 2021 12:42:16 +0200
> > From: Heinrich Schuchardt <xypron.glpk@gmx.de>
> >
> > Am 15. September 2021 11:56:07 MESZ schrieb Michael Lawnick <ml.lawnick@gmx.de>:
> > >Am 14.09.2021 um 17:57 schrieb Heinrich Schuchardt:
> > >> On 9/14/21 4:56 PM, Michael Lawnick wrote:
> > >>> Hi,
> > >>>
> > >>> in our environment we get error on efi_selftest if one of several SSD
> > >>> partitions isn't properly initialized (due to some other error, but
> > >>> that's a different topic). I tried to track down to where the partitions
> > >>> get registered for test but got a bit lost so I request advice from you.
> > >>
> > >> When the UEFI sub-system is intialized we call efi_disk_register(). If
> > >> it fails, we don't enter the UEFI sub-system.
> > >>
> > >> Are you able to identify where efi_disk_register() fails?
> > >
> > >The system starts up properly.
> > >This is what I see:
> > >ASIM-CN10KAS> efiload $loadaddr
> > >Loaded EFI App image at 0x40080000 with 0x216000 bytes
> > >ASIM-CN10KAS> bootefi $loadaddr $fdtaddr
> > >Scanning disk sdhci@824000000000.blk...
> > >** Unrecognized filesystem type **
> > >** Unrecognized filesystem type **
> > >** Unrecognized filesystem type **
> >
> > This is not an error. Just an info.
>
> It is somewhat annoying though. The way disks are partitioned on the
> Apple M1 systems, there are several Apple native partition types that
> need to be retained and that U-Boot doesn't support. So you see a lot
> of these warnings.
>
> Or maybe we should have a whitelist of partition types not to warn
> about?
This message is not UEFI specific, but generic filesystem code
generates it. So you could
1) At fs_probe_unsupported() in fs/fs.c,
change log_err() to log_warning() [or log_info()]
2) Set CONFIG_DEFAULT_LOG_LEVEL to 3(error) [or 4(warning)]
to suppress the message.
Or you may simply want to modify _log() so as to add a preamble,
like "WARN:", in front of the message.
-Takahiro Akashi
prev parent reply other threads:[~2021-09-16 6:59 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
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 [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=20210916065921.GA59501@laputa \
--to=takahiro.akashi@linaro.org \
--cc=mark.kettenis@xs4all.nl \
--cc=ml.lawnick@gmx.de \
--cc=sjg@chromium.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox