From: aaron.young@oracle.com
To: edk2-devel@lists.01.org
Cc: lersek@redhat.com, brijesh.singh@amd.com
Subject: Regression with PXE boot on OvmfPkg/VirtioNetDxe driver on aarch64 system
Date: Thu, 30 Aug 2018 13:17:21 -0700 [thread overview]
Message-ID: <ccea8a82-1696-84ac-1cb6-0f1b62e3c9b1@oracle.com> (raw)
We have encountered what we believe to be a regression in the
OvmfPkg/VirtioNetDxe driver.
This regression causes PXE boot to fail with the following ASSERT:
ASSERT
[VirtioNetDxe]/builddir/build/BUILD/ovmf-92d07e48907f/OvmfPkg/VirtioNetDxe/SnpSharedHelpers.c(184):
((BOOLEAN)(0==1))
The failure was encountered on a aarch64/Armv8 system (Ampere server)
using the latest mainline (edk2.git/master) code as of 8-28-2018.
On a hunch, I reverted the following patchset which resulted in PXE
boot being successful - which suggests this patchset is likely the culprit:
https://lists.01.org/pipermail/edk2-devel/2017-September/014679.html
The command used to initiate the VM PXE boot/install is:
virt-install --name guest1 --vcpus 16 --ram 32000 --arch aarch64
--disk guest1.img,size=100 --network
type=direct,source=enP4p1s0,model=virtio --pxe
NOTE that I also tried simply removing the offending ASSERT() and PXE
boot still fails with multiple errors (exceptions of some sort that I
didn't log).
What I'd like to know:
1. Is this a known failure?
2. Was aarch64 given much testing with this new patchset?
3. Is reverting this patchset a safe workaround for now until a fix
is found? Or is there another simple workaround perhaps?
4. Any hunches what the issue could be?
Thanks for any info/help/suggestions,
-Aaron Young
next reply other threads:[~2018-08-30 20:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 20:17 aaron.young [this message]
2018-08-31 13:17 ` Regression with PXE boot on OvmfPkg/VirtioNetDxe driver on aarch64 system Laszlo Ersek
2018-10-03 16:56 ` aaron.young
2018-10-03 17:35 ` Ard Biesheuvel
2018-10-03 23:59 ` aaron.young
2018-10-04 9:24 ` Leif Lindholm
2018-10-04 13:06 ` Laszlo Ersek
2018-10-15 20:52 ` aaron.young
2018-10-16 1:55 ` Ard Biesheuvel
2018-10-17 9:50 ` Laszlo Ersek
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-list 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=ccea8a82-1696-84ac-1cb6-0f1b62e3c9b1@oracle.com \
--to=devel@edk2.groups.io \
/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