From: Gerd Hoffmann <kraxel@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
"László Érsek" <lersek@redhat.com>
Subject: Re: [PULL 0/3] Edk2 stable202302 20230309 patches
Date: Wed, 15 Mar 2023 16:56:55 +0100 [thread overview]
Message-ID: <20230315155655.ww75ox7hougl32wk@sirius.home.kraxel.org> (raw)
In-Reply-To: <CAFEAcA_KwKQjgsx+4C_3an6ujhN=ETYFbaOjgU7Bg4OYt10OgA@mail.gmail.com>
Hi,
> ▶ 206/206 ERROR:../tests/qtest/acpi-utils.c:158:acpi_find_rsdp_address_uefi:
> code should not be reached ERROR
> 206/206 qemu:qtest+qtest-aarch64 / qtest-aarch64/bios-tables-test
> ERROR 706.75s killed by signal 6 SIGABRT
mst? laszlo? Any hints how to debug that?
Tried to start qemu manually with the command line I get from
"make V=1 check-qtest-aarch64", that seems to start the uefi
app from the iso image just fine ...
take care,
Gerd
next prev parent reply other threads:[~2023-03-15 15:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 11:57 [PULL 0/3] Edk2 stable202302 20230309 patches Gerd Hoffmann
2023-03-09 11:57 ` [PULL 1/3] edk2: update submodule to edk2-stable202302 Gerd Hoffmann
2023-03-09 11:57 ` [PULL 2/3] edk2: replace build scripts Gerd Hoffmann
2023-03-10 13:58 ` Simon Glass
2023-03-15 15:49 ` Gerd Hoffmann
2023-03-20 19:19 ` Simon Glass
2023-03-09 11:57 ` [PULL 3/3] edk2: update firmware binaries Gerd Hoffmann
2023-03-09 22:09 ` Simon Glass
2023-03-10 6:37 ` Gerd Hoffmann
2023-03-10 21:00 ` Simon Glass
2023-03-10 11:30 ` [PULL 0/3] Edk2 stable202302 20230309 patches Peter Maydell
2023-03-10 13:09 ` Philippe Mathieu-Daudé
2023-03-15 15:56 ` Gerd Hoffmann [this message]
2023-03-15 16:16 ` Laszlo Ersek
2023-03-16 7:55 ` Gerd Hoffmann
2023-03-10 13:18 ` Philippe Mathieu-Daudé
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=20230315155655.ww75ox7hougl32wk@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=lersek@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).