From: Launchpad Bug Tracker <1732177@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1732177] Re: SBSA ACS test freezes inside qemu-system-aarch64
Date: Sun, 10 Jan 2021 04:17:40 -0000 [thread overview]
Message-ID: <161025226019.18863.6230570356323293214.malone@loganberry.canonical.com> (raw)
In-Reply-To: 151066478781.7464.15116659457637721936.malonedeb@soybean.canonical.com
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1732177
Title:
SBSA ACS test freezes inside qemu-system-aarch64
Status in QEMU:
Expired
Bug description:
In an effort to get Windows 10 for ARM64 (which is supposed to boot on
SBSA/SBBR-compliant platforms) to boot inside qemu, I tried to run the
SBSA ACS test suite. I used the UEFI image from the latest Linaro
snapshot, and built the SBSA ACS UEFI application from
https://github.com/ARM-software/sbsa-acs myself using a Linaro aarch64
compiler.
Test #8 causes an infinite exception loop, as the exception vectors
themselves somehow become inaccessible, and accessing them triggers
another exception to be handled by the same vector. (With some older
Linaro UEFI images, the hard lockup is avoided, and the SBSA UEFI app
crashes instead.) If I disable that test, the testsuite locks up in
other tests in very similar ways. We aren't even able to get a
pass/fail score from the app because of this.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1732177/+subscriptions
prev parent reply other threads:[~2021-01-10 4:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 13:06 [Qemu-devel] [Bug 1732177] [NEW] SBSA ACS test freezes inside qemu-system-aarch64 Googulator
2020-11-10 17:50 ` [Bug 1732177] " Thomas Huth
2021-01-10 4:17 ` Launchpad Bug Tracker [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=161025226019.18863.6230570356323293214.malone@loganberry.canonical.com \
--to=1732177@bugs.launchpad.net \
--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.