From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PULL 0/3] Firmware/seabios 20230912 patches
Date: Mon, 18 Sep 2023 14:05:39 +0100 [thread overview]
Message-ID: <ZQhLI0EzYFbXv9sW@redhat.com> (raw)
In-Reply-To: <CAJSP0QU4EocB1FaAwwcUS9aZShXb5nr+ME1LEqe=Gujn39h-Lw@mail.gmail.com>
On Mon, Sep 18, 2023 at 08:52:57AM -0400, Stefan Hajnoczi wrote:
> On Mon, 18 Sept 2023 at 06:00, Gerd Hoffmann <kraxel@redhat.com> wrote:
> >
> > > Hi Gerd,
> > > I think either this pull request or your edk2 pull request causes the
> > > following CI failure:
> > >
> > > >>> G_TEST_DBUS_DAEMON=/builds/qemu-project/qemu/tests/dbus-vmstate-daemon.sh QTEST_QEMU_BINARY=./qemu-system-aarch64 MALLOC_PERTURB_=199 /builds/qemu-project/qemu/build/tests/qtest/bios-tables-test --tap -k
> > > ――――――――――――――――――――――――――――――――――――― ✀ ―――――――――――――――――――――――――――――――――――――
> >
> > Address change in ACPI tables (edk2 PR):
> >
> > DefinitionBlock ("", "SSDT", 1, "BOCHS ", "NVDIMM", 0x00000001)
> > {
> > Scope (\_SB)
> > {
> > Device (NVDR)
> > {
> > Name (_HID, "ACPI0012" /* NVDIMM Root Device */) // _HID: Hardware ID
> > [ ... ]
> > }
> > }
> >
> > - Name (MEMA, 0x43D10000)
> > + Name (MEMA, 0x43C90000)
> > }
> >
> > seabios PR is fine and passes "make check".
>
> I'm still seeing a CI failure:
>
> 3/61 qemu:qtest+qtest-x86_64 / qtest-x86_64/bios-tables-test ERROR
> 19.18s killed by signal 6 SIGABRT
> ――――――――――――――――――――――――――――――――――――― ✀ ―――――――――――――――――――――――――――――――――――――
> stderr:
> acpi-test: Warning! DSDT binary file mismatch. Actual
> [aml:/var/folders/76/zy5ktkns50v6gt5g8r0sf6sc0000gn/T/aml-SW7IB2],
> 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)
Hmm, that's rather unhelpful - we need to get iasl added to the build
env by default.
> (test program exited with status code -6)
>
> https://gitlab.com/qemu-project/qemu/-/jobs/5110608123
Note this is a aarch64 macOS environment
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2023-09-18 13:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 10:53 [PULL 0/3] Firmware/seabios 20230912 patches Gerd Hoffmann
2023-09-12 10:53 ` [PULL 1/3] seabios: update submodule to git snapshot Gerd Hoffmann
2023-09-12 10:53 ` [PULL 2/3] seabios: turn off CONFIG_APMBIOS for 128k build Gerd Hoffmann
2023-09-12 13:55 ` Paolo Bonzini
2023-09-18 9:50 ` Gerd Hoffmann
2023-09-12 10:53 ` [PULL 3/3] seabios: update binaries to git snapshot Gerd Hoffmann
2023-09-12 12:56 ` [PULL 0/3] Firmware/seabios 20230912 patches Stefan Hajnoczi
2023-09-18 9:59 ` Gerd Hoffmann
2023-09-18 12:52 ` Stefan Hajnoczi
2023-09-18 13:05 ` Daniel P. Berrangé [this message]
2023-09-18 13:40 ` Gerd Hoffmann
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=ZQhLI0EzYFbXv9sW@redhat.com \
--to=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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.