From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Romain Naour <romain.naour@gmail.com>
Cc: Julien Olivain <ju.o@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] support/testing: Override the EDK2 CPU hotplug bug check
Date: Sat, 29 Jul 2023 11:02:00 +0200 [thread overview]
Message-ID: <20230729110200.6c01af7d@windsurf> (raw)
In-Reply-To: <20230728225354.269776-1-romain.naour@gmail.com>
On Sat, 29 Jul 2023 00:53:54 +0200
Romain Naour <romain.naour@gmail.com> wrote:
> In QEMU v5.1.0 up to v7.2.0, the CPU hotplug register block misbehaves.
> EDK2 hang if the bug is detected in Qemu after printing errors to IO port 0x402
> (requires BR2_TARGET_EDK2_OVMF_DEBUG_ON_SERIAL to see them)
>
> The Docker image used by the Buildroot gitlab-ci uses Qemu 5.2.0, the workaround
> can be removed as soon as the Docker image is updated to provided Qemu >= 8.0.0.
>
> https://github.com/tianocore/edk2/commit/bf5678b5802685e07583e3c7ec56d883cbdd5da3
> http://lists.busybox.net/pipermail/buildroot/2023-July/670825.html
>
> Fixes:
> https://gitlab.com/buildroot.org/buildroot/-/jobs/4725186190 (TestGrubX8664EFI)
> https://gitlab.com/buildroot.org/buildroot/-/jobs/4725186198 (TestGrubi386EFI)
> https://gitlab.com/buildroot.org/buildroot/-/jobs/4725186306 (TestIso9660Grub2EFI)
> https://gitlab.com/buildroot.org/buildroot/-/jobs/4725186317 (TestIso9660Grub2Hybrid)
>
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> Cc: Julien Olivain <ju.o@free.fr>
> ---
> Adding Debian bullseye backport repository in the Docker image used by the Buildroot Gitlab-ci
> is not enough, since the bug is really fixed in Qemu 8.0.0 and only Qemu 7.2.0 is provided.
> ---
> support/testing/tests/boot/test_grub.py | 20 ++++++++++++++++++--
> support/testing/tests/fs/test_iso9660.py | 11 ++++++++++-
> 2 files changed, 28 insertions(+), 3 deletions(-)
Looking at this, I was wondering if it could be factorized some way.
But OK, that's just 3 occurrences, and it's supposed to be temporary
until we switch to Qemu 8.0.0. So: applied as-is. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-07-29 9:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 22:53 [Buildroot] [PATCH] support/testing: Override the EDK2 CPU hotplug bug check Romain Naour
2023-07-29 9:02 ` Thomas Petazzoni via buildroot [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=20230729110200.6c01af7d@windsurf \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=romain.naour@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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.