From: Stefan Hajnoczi <stefanha@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PULL 0/2] Firmware/seabios 20230929 patches
Date: Mon, 2 Oct 2023 17:58:59 -0400 [thread overview]
Message-ID: <CAJSP0QUR0g9gFRbRqmVeHBDqA2Tu9t_64sNYQk=hedSq9MSEeg@mail.gmail.com> (raw)
In-Reply-To: <20230929112936.2852930-1-kraxel@redhat.com>
On Fri, 29 Sept 2023 at 07:30, Gerd Hoffmann <kraxel@redhat.com> wrote:
>
> The following changes since commit 36e9aab3c569d4c9ad780473596e18479838d1aa:
>
> migration: Move return path cleanup to main migration thread (2023-09-27 13:58:02 -0400)
>
> are available in the Git repository at:
>
> https://gitlab.com/kraxel/qemu.git tags/firmware/seabios-20230929-pull-request
>
> for you to fetch changes up to 1f75b1beeb8d958cc56113ba229348d6a0be9d9d:
>
> seabios: update binaries to git snapshot (2023-09-29 13:15:44 +0200)
>
> ----------------------------------------------------------------
> seabios: update to git snapshot
>
> Give seabios a bit real world testing before tagging a release.
> Update to release will follow later in the devel cycle.
The following CI failure has occurred:
3/61 qemu:qtest+qtest-x86_64 / qtest-x86_64/bios-tables-test
ERROR 19.15s killed by signal 6 SIGABRT
――――――――――――――――――――――――――――――――――――― ✀ ―――――――――――――――――――――――――――――――――――――
stderr:
acpi-test: Warning! DSDT binary file mismatch. Actual
[aml:/var/folders/76/zy5ktkns50v6gt5g8r0sf6sc0000gn/T/aml-K2USB2],
Expected [aml:tests/data/acpi/q35/DSDT.mmio64].
See source file tests/qtest/bios-tables-test.c for instructions on how
to update expected files.
to see ASL diff between mismatched files install IASL, rebuild QEMU
from scratch and re-run tests with V=1 environment variable set**
ERROR:../tests/qtest/bios-tables-test.c:535:test_acpi_asl: assertion
failed: (all_tables_match)
(test program exited with status code -6)
https://gitlab.com/qemu-project/qemu/-/jobs/5204949160
Please take a look. Thanks!
Stefan
>
> ----------------------------------------------------------------
>
> Gerd Hoffmann (2):
> seabios: update submodule to git snapshot
> seabios: update binaries to git snapshot
>
> pc-bios/bios-256k.bin | Bin 262144 -> 262144 bytes
> pc-bios/bios-microvm.bin | Bin 131072 -> 131072 bytes
> pc-bios/bios.bin | Bin 131072 -> 131072 bytes
> pc-bios/vgabios-ati.bin | Bin 39936 -> 39424 bytes
> pc-bios/vgabios-bochs-display.bin | Bin 28672 -> 28672 bytes
> pc-bios/vgabios-cirrus.bin | Bin 39424 -> 38912 bytes
> pc-bios/vgabios-qxl.bin | Bin 39936 -> 39424 bytes
> pc-bios/vgabios-ramfb.bin | Bin 29184 -> 28672 bytes
> pc-bios/vgabios-stdvga.bin | Bin 39936 -> 39424 bytes
> pc-bios/vgabios-virtio.bin | Bin 39936 -> 39424 bytes
> pc-bios/vgabios-vmware.bin | Bin 39936 -> 39424 bytes
> pc-bios/vgabios.bin | Bin 39424 -> 38912 bytes
> roms/seabios | 2 +-
> 13 files changed, 1 insertion(+), 1 deletion(-)
>
> --
> 2.41.0
>
>
prev parent reply other threads:[~2023-10-02 21:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 11:29 [PULL 0/2] Firmware/seabios 20230929 patches Gerd Hoffmann
2023-09-29 11:29 ` [PULL 1/2] seabios: update submodule to git snapshot Gerd Hoffmann
2023-09-29 11:29 ` [PULL 2/2] seabios: update binaries " Gerd Hoffmann
2023-10-02 21:58 ` Stefan Hajnoczi [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='CAJSP0QUR0g9gFRbRqmVeHBDqA2Tu9t_64sNYQk=hedSq9MSEeg@mail.gmail.com' \
--to=stefanha@gmail.com \
--cc=kraxel@redhat.com \
--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 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.