[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Problem running qos-test when building with gcc12 and LTO
|
From: |
Dario Faggioli |
|
Subject: |
Re: Problem running qos-test when building with gcc12 and LTO |
|
Date: |
Wed, 25 May 2022 11:30:39 +0000 |
|
User-agent: |
Evolution 3.44.1 (by Flathub.org)) |
On Wed, 2022-05-25 at 09:40 +0000, Dario Faggioli wrote:
> On Wed, 2022-05-25 at 07:41 +0100, Alex Bennée wrote:
>
>
> > Does it still trigger errors with my latest virtio cleanup series
> > (which
> > adds more tests to qos-test):
> >
> > Subject: [PATCH v2 00/15] virtio-gpio and various virtio
> > cleanups
> > Date: Tue, 24 May 2022 16:40:41 +0100
> > Message-Id: <20220524154056.2896913-1-alex.bennee@linaro.org>
> >
> I'll try it. I know it fails on master (at least two days ago's
> master). I'll apply the series and re-test.
>
Ok, so, yes: current master + the v2 of "virtio-gpio and various virtio
cleanups", still fails (with GCC12 and LTO, of course), pretty much in
the same way I've described in this thread.
I've also tried current master + above series + revert of
8dcb404bff6d914 , although I'm not sure it even makes sense... :-O
Anyway, it also fails, but differently:
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} \
> QTEST_QEMU_IMG=./qemu-img
> G_TEST_DBUS_DAEMON=../tests/dbus-vmstate-daemon.sh \
>
>
> QTEST_QEMU_STORAGE_DAEMON_BINARY=./storage-daemon/qemu-storage-daemon \
>
>
>
> QTEST_QEMU_BINARY=./qemu-system-x86_64 ./tests/qtest/qos-test --tap -k
>
>
>
# random seed: R02S69b7a984047f827959f7adb2e4161fb7
# starting QEMU: exec ./qemu-system-x86_64 -qtest unix:/tmp/qtest-31788.sock
-qtest-log /dev/null -chardev socket,path=/tmp/qtest-31788.qmp,id=char0 -mon
chardev=char0,mode=control -display none -machine none -accel qtest
1..101
# Start of x86_64 tests
# Start of pc tests
# Start of i440FX-pcihost tests
# Start of pci-bus-pc tests
# Start of pci-bus tests
# Start of vhost-user-gpio-pci tests
# Start of vhost-user-gpio tests
# Start of vhost-user-gpio-tests tests
# Start of read-guest-mem tests
qemu-system-x86_64: Failed to set msg fds.
qemu-system-x86_64: vhost VQ 0 ring restore failed: -22: Invalid argument (22)
qemu-system-x86_64: Failed to set msg fds.
qemu-system-x86_64: vhost VQ 1 ring restore failed: -22: Invalid argument (22)
qemu-system-x86_64: Failed to set msg fds.
qemu-system-x86_64: vhost_set_vring_call failed: Invalid argument (22)
qemu-system-x86_64: Failed to set msg fds.
qemu-system-x86_64: vhost_set_vring_call failed: Invalid argument (22)
qemu-system-x86_64: Failed to write msg. Wrote -1 instead of 20.
qemu-system-x86_64: vhost VQ 0 ring restore failed: -5: Input/output error (5)
../tests/qtest/libqtest.c:165: kill_qemu() detected QEMU death from signal 11
(Segmentation fault)
# child process
(/x86_64/pc/i440FX-pcihost/pci-bus-pc/pci-bus/vhost-user-gpio-pci/vhost-user-gpio/vhost-user-gpio-tests/read-guest-mem/memfile/subprocess
[31850]) killed by signal 6 (Aborted)
# child process
(/x86_64/pc/i440FX-pcihost/pci-bus-pc/pci-bus/vhost-user-gpio-pci/vhost-user-gpio/vhost-user-gpio-tests/read-guest-mem/memfile/subprocess
[31850]) stdout: ""
# child process
(/x86_64/pc/i440FX-pcihost/pci-bus-pc/pci-bus/vhost-user-gpio-pci/vhost-user-gpio/vhost-user-gpio-tests/read-guest-mem/memfile/subprocess
[31850]) stderr: "qemu-system-x86_64: Failed to set msg
fds.\nqemu-system-x86_64: vh
ost VQ 0 ring restore failed: -22: Invalid argument (22)\nqemu-system-x86_64:
Failed to set msg fds.\nqemu-system-x86_64: vhost VQ 1 ring restore failed:
-22: Invalid argument (22)\nqemu-system-x86_64: Failed to set msg
fds.\nqemu-system-
x86_64: vhost_set_vring_call failed: Invalid argument (22)\nqemu-system-x86_64:
Failed to set msg fds.\nqemu-system-x86_64: vhost_set_vring_call failed:
Invalid argument (22)\nqemu-system-x86_64: Failed to write msg. Wrote -1
instead of 2
0.\nqemu-system-x86_64: vhost VQ 0 ring restore failed: -5: Input/output error
(5)\n../tests/qtest/libqtest.c:165: kill_qemu() detected QEMU death from signal
11 (Segmentation fault)\n"
**
ERROR:../tests/qtest/qos-test.c:190:subprocess_run_one_test: child process
(/x86_64/pc/i440FX-pcihost/pci-bus-pc/pci-bus/vhost-user-gpio-pci/vhost-user-gpio/vhost-user-gpio-tests/read-guest-mem/memfile/subprocess
[31850]) failed unexpecte
dly
Bail out! ERROR:../tests/qtest/qos-test.c:190:subprocess_run_one_test: child
process
(/x86_64/pc/i440FX-pcihost/pci-bus-pc/pci-bus/vhost-user-gpio-pci/vhost-user-gpio/vhost-user-gpio-tests/read-guest-mem/memfile/subprocess
[31850]) failed
unexpectedly
Aborted
With also this in dmesg:
[mer mag 25 13:11:18 2022] show_signal_msg: 46 callbacks suppressed
[mer mag 25 13:11:18 2022] qemu-system-x86[23711]: segfault at 58 ip
000055e6a0daa4b3 sp 00007ffc5699b870 error 4 in
qemu-system-x86_64[55e6a0bdb000+617000]
[mer mag 25 13:11:18 2022] Code: 83 26 4d 00 48 8d 2d 66 1e 4d 00 53 48 8d 1d
74 7d 44 00 48 89 da e8 cc a5 26 00 48 89 da 4c 8d 05 c0 78 50 00 b9 d8 00 00
00 <48> 8b 78 58 48 8d 35 d0 78 49 00 e8 ad a5 26 00 b9 23 00 00 00 4c
Of course, I've also tried current master + above series, with GCC12
and _no_ LTO. And that works.
Any other test I can run? :-)
Regards
--
Dario Faggioli, Ph.D
http://about.me/dario.faggioli
Virtualization Software Engineer
SUSE Labs, SUSE https://www.suse.com/
-------------------------------------------------------------------
<<This happens because _I_ choose it to happen!>> (Raistlin Majere)
signature.asc
Description: This is a digitally signed message part