https://git.qemu.org/?p=qemu.git;a=commitdiff;h=db221e66d8117f810c804
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1713434
Title:
OK, so this was "only" the TCG-interpreter that was causing the sparc64
problem here. Since there are known issues with the TCG-interpreter on
certain architectures, this is not really related to the prom-env-test.
And since the fix for the original
"ERROR:tests/libqtest.c:628:qtest_get_arch: asser
Thomas thanks for your hint about the configuration option named
"--enable-tcg-interpreter". By removing it the test case started working
fine.
[root@zzfp365-lp1 qemu]# ./sparc64-softmmu/qemu-system-sparc64 -nographic -M
sun4u -prom-env 'use-nvramrc?=true' -prom-env 'nvramrc=." Hello World!" cr'
Some times it's still puzzling, when I got the clean git tree still
seeing crash with correct OpenBIOS file.
[root@zzfp365-lp1 test]# git clone git://git.qemu.org/qemu.git
Cloning into 'qemu'...
remote: Counting objects: 349636, done.
remote: Compressing objects: 100% (66763/66763), done.
remote:
After talking to Mark Cave-Ayland over e-mail, to make sure I have the proper
versions of OpenBIOS binaries - removed the existing git tree and with a fresh
clone not seeing the 'qemu-system-sparc64' related crash.
Before cleanup I was seeing the crash all the times.
Thanks!!
--
You received th
The above problem is getting re-producible only with configure option
"--enable-crypto-afalg" This got introduced in between 2.9.1 and 2.10.0.
I will bisect it and update.
When I tried earlier with 2.9.1 it complained saying "--enable-crypto-afalg"
option is not available so I did with out it and
This test case was working till 2.10.0 and got broken in 2.10.1
I checked with 2.9.1, 2.10.0-rc2, 2.10.0-rc3, 2.10.0-rc4, 2.10.0
Working scenario:
# ./sparc64-softmmu/qemu-system-sparc64 -nographic -M sun4u -prom-env
'use-nvramrc?=true' -prom-env 'nvramrc=." Hello World!" cr'
OpenBIOS for Sparc6
Here is the md5sum of openbios-sparc64
# md5sum ./pc-bios/openbios-sparc64
15418a4c9429d9ee9c637701b94c7ffb ./pc-bios/openbios-sparc64
> Could you please check with the QEMU 2.10 release to see whether this is a
> regression or whether it was already failing there?
Sure, I will update here. Mo
On 07.11.2017 11:58, R.Nageswara Sastry wrote:
> Git head is at 299d1ea9bb56bd9f45f905125489bdd7d543a1aa
> latest today
>
> 100% re-producible. This is different & working Power9 machine than the
> other day.
>
> # ./sparc64-softmmu/qemu-system-sparc64 -nographic -M sun4u -prom-env
> 'use-nvramr
Git head is at 299d1ea9bb56bd9f45f905125489bdd7d543a1aa
latest today
100% re-producible. This is different & working Power9 machine than the
other day.
# ./sparc64-softmmu/qemu-system-sparc64 -nographic -M sun4u -prom-env
'use-nvramrc?=true' -prom-env 'nvramrc=." Hello World!" cr'
OpenBIOS for S
Is that 100% reproducible? Which version of QEMU did you use here? And
which host are you using, POWER9 again? The very latest git master
branch is using a timeout of 10 minutes now, so that should be
sufficient for all cases...
Could you please try to run this manually:
qemu-system-sparc64 -nogr
Similar failure seen with the following test too.
# make check-qtest-sparc64 V=1
(cd /home/nasastry/qemu; printf '#define QEMU_PKGVERSION '; if test -n ""; then
printf '""\n'; else if test -d .git; then printf '" ('; git describe --match
'v*' 2>/dev/null | tr -d '\n'; if ! git diff-index --quiet
OK, thanks for testing! Anyway, I'll keep the bug opened to track the
original issue that you've mentioned in the description
("ERROR:tests/libqtest.c:628:qtest_get_arch: assertion failed") here.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed
On other machine with same OS and gcc level, it's working fine. Not getting
what went wrong in the machine where I can re-produce this issue.
I guess this bug can be closed. Thank you.
/ppc64/prom-env/pseries:
SLOF **
QEMU Sta
# md5sum ./pc-bios/slof.bin
db83598b28052e9c12972d86c37b0c69 ./pc-bios/slof.bin
Same as what you mentioned.
Will try to get a different machine and try. If the problem still
persists, I will check with Nikunj.
Thanks a lot for your time. I have learned many things while interacting
with you.
Very weird, looks like SLOF crashed at a very early stage here. I've got
no further clue how to debug this ... could you maybe try it on another
POWER9 host if possible? Or check whether slof.bin accidentially got
corrupted (md5sum pc-bios/slof.bin should give you
db83598b28052e9c12972d86c37b0c69)?
Strange,
# gcc --version
gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-16)
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
OS is RHEL based.
# uname -
Weird. I managed to run the test on a POWER9 box today, too, and it
works for me:
TEST: tests/prom-env-test... (pid=18912)
/ppc64/prom-env/mac99: OK
/ppc64/prom-env/g3beige: OK
/ppc64/prom-env/pseries:
TEST: tests/prom-env-test... (pid=9915)
/ppc64/prom-env/mac99: OK
/ppc64/prom-env/g3beige: OK
/ppc64/prom-env/pseries: **
ERROR:tests/prom-env-test.c:42:check_
Hmm, that looks like -prom-env is working correctly with the pseries
machine. I wonder whether the problem is somewhere else... Could you
please run "make check-qtest-ppc64 V=1" to see whether it rather fails
for the mac99 or g3beige machines?
--
You received this bug notification because you are
I am using a Power9 machine.
# ppc64-softmmu/qemu-system-ppc64 -nographic -M pseries,accel=tcg
-nodefaults -serial stdio -prom-env 'use-nvramrc?=true' -prom-env
'nvramrc=." Hello World!" cr power-off'
SLOF **
QEMU Starting
Buil
That works for me - no problems with tests/prom-env-test on a POWER8
little endian system here. What host system are you using? Could you
also check what happens if you run QEMU directly like this, and post the
console output here:
ppc64-softmmu/qemu-system-ppc64 -nographic -M pseries,accel=tcg
-n
Host was not loaded at that time. And can be re-producable all the times
GTESTER check-qtest-ppc64
**
ERROR:tests/prom-env-test.c:42:check_guest_memory: assertion failed (signature
== MAGIC): (0x7c7f1b78 == 0xcafec0de)
GTester: last random seed: R02S5625099e4ad7700238a4e83dbd6576e0
this is wit
The "ERROR:tests/prom-env-test.c:42:check_guest_memory" error is a
timeout error... is it reproducible? Was the host you're testing on very
loaded at that point in time?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.lau
The actual failure was the following
LINKtests/test-hmp
GTESTER check-qtest-ppc64
**
ERROR:tests/prom-env-test.c:42:check_guest_memory: assertion failed (signature
== MAGIC): (0x7c7f1b78 == 0xcafec0de)
GTester: last random seed: R02Sfb567618f7c703a032934c0c11e263c6
make: *** [check-qtest-
When running tests directly, you've got to specify the QEMU binary like
this:
QTEST_QEMU_BINARY=ppc64-softmmu/qemu-system-ppc64 tests/prom-env-test
--quiet --keep-going -m=quick
But the abort() is indeed ugly here and I think we should print out a
user-friendly error message instead.
** Changed
26 matches
Mail list logo
