From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Quentin Schulz <quentin.schulz@cherry.de>
Cc: openembedded-core@lists.openembedded.org,
Ilias Apalodimas <ilias.apalodimas@linaro.org>
Subject: Re: [OE-core] [PATCH] u-boot: disable CONFIG_BLOBLIST on aarch64
Date: Wed, 21 May 2025 15:52:44 +0100 [thread overview]
Message-ID: <aC3ovAPrRnwhogik@nuoska> (raw)
In-Reply-To: <b85c6a6c-250c-4b87-b9cc-92ed5fd51d19@cherry.de>
Hi,
On Wed, May 21, 2025 at 04:14:04PM +0200, Quentin Schulz wrote:
> Hi Mikko,
>
> On 5/21/25 3:51 PM, Mikko Rapeli via lists.openembedded.org wrote:
> > Booting on qemu with kvm is currently hanging on aarch64.
> > Root cause is in u-boot and CONFIG_BLOBLIST can be disabled
> > as a workaround.
> >
> > To reproduce, build on kvm enabled host where "kvm-ok"
> > succeeds. For example genericarm64 machine and core-image-base
> > should then boot with:
> >
> > $ runqemu slirp nographic novga snapshot kvm
> >
> > Without this config workaround, the boot hangs without
> > any messages in qemu output but ctrl-a-c to qemu console
> > can shutdown the emulated machine.
> >
> > This seems to have regressed after u-boot 2025.04 update.
> > KVM boot can be detected from speed, for example genericarm64
> > boots in 550 ms with KVM and without in over 5 seconds.
> >
> > Fixes: [YOCTO #15872]
> >
> > Cc: Ilias Apalodimas <ilias.apalodimas@linaro.org>
> > Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
> > ---
> > meta/recipes-bsp/u-boot/files/disable-CONFIG_BLOBLIST.cfg | 1 +
> > meta/recipes-bsp/u-boot/u-boot-common.inc | 3 +++
> > 2 files changed, 4 insertions(+)
> > create mode 100644 meta/recipes-bsp/u-boot/files/disable-CONFIG_BLOBLIST.cfg
> >
> > diff --git a/meta/recipes-bsp/u-boot/files/disable-CONFIG_BLOBLIST.cfg b/meta/recipes-bsp/u-boot/files/disable-CONFIG_BLOBLIST.cfg
> > new file mode 100644
> > index 0000000000..d01d3d12d8
> > --- /dev/null
> > +++ b/meta/recipes-bsp/u-boot/files/disable-CONFIG_BLOBLIST.cfg
> > @@ -0,0 +1 @@
> > +# CONFIG_BLOBLIST is not set
> > diff --git a/meta/recipes-bsp/u-boot/u-boot-common.inc b/meta/recipes-bsp/u-boot/u-boot-common.inc
> > index fd1eab5cdd..d8c70da782 100644
> > --- a/meta/recipes-bsp/u-boot/u-boot-common.inc
> > +++ b/meta/recipes-bsp/u-boot/u-boot-common.inc
> > @@ -16,6 +16,9 @@ SRCREV = "34820924edbc4ec7803eb89d9852f4b870fa760a"
> > SRC_URI = "git://source.denx.de/u-boot/u-boot.git;protocol=https;branch=master;tag=v${PV}"
> > +# workaround for aarch64 kvm qemu boot regression
> > +SRC_URI:append:aarch64 = " file://disable-CONFIG_BLOBLIST.cfg"
> > +
>
> Can you make this qemu specific? I don't think we want every aarch64 board
> to have bloblist disabled?
True, at least qemu and genericarm64 need this. Or should this be tied
to some machine/distro feature or something else?
I guess KVM support is not a machine feature atm.
Cheers,
-Mikko
next prev parent reply other threads:[~2025-05-21 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 13:51 [PATCH] u-boot: disable CONFIG_BLOBLIST on aarch64 Mikko Rapeli
2025-05-21 14:14 ` [OE-core] " Quentin Schulz
2025-05-21 14:52 ` Mikko Rapeli [this message]
2025-05-21 14:58 ` Quentin Schulz
2025-05-21 15:03 ` Mikko Rapeli
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=aC3ovAPrRnwhogik@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=ilias.apalodimas@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=quentin.schulz@cherry.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