[Qemu-devel] [Bug 1821430] Re: qemu-user-arm (4.0.0-rc0) crashes
qemu-user-arm 4.0.0-rc1 no longer produces any crashes for me.
Huge thanks.
** 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/1821430
Title:
qemu-user-arm (4.0.0-rc0) crashes
Status in QEMU:
Fix Released
Bug description:
I'm using qemu-user-arm for crosscompilation needs, usually via a wrapper.
qemu-user-arm (4.0.0-rc0) crashes with SIGILL on at least 2 instructions:
first case (sadly I don't have more data handy, can reproduce at a later time
if needed):
(gdb) x/i $pc
=> 0xfffce314: vseleq.f64 d0, d17, d0
second case (llvm-config):
qemu cmdline:
qemu-arm -strace -cpu max -r 5.0.0 -L /home/asavah/kross/build/rpi3/rootfs -E
LD_LIBRARY_PATH=/home/asavah/kross/build/rpi3/rootfs/usr/bin:/home/asavah/kross/build/rpi3/rootfs/usr/lib
/home/asavah/kross/build/rpi3/rootfs/usr/bin/llvm-config --shared-mode
--- SIGILL {si_signo=SIGILL, si_code=2, si_addr=0xf9f89f80} ---
qemu: uncaught target signal 4 (Illegal instruction) - core dumped
output from gdb(arm) attached to qemu-user-arm
Program received signal SIGILL, Illegal instruction.
0xf9f77f80 in ?? ()
(gdb) bt
#0 0xf9f77f80 in ?? ()
#1 0xfffd796c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) x/i $pc
=> 0xf9f77f80: vrintm.f64 d18, d18
The very same binaries when run with qemu-user-arm 3.1.0 (both from ubuntu
19.04 package and self built)
work flawlessly.
This is clearly a regression.
Please fix before releasing 4.0.0.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1821430/+subscriptions
[Qemu-devel] [Bug 1821430] Re: qemu-user-arm (4.0.0-rc0) crashes
I should point that -cpu cortex-a53 is not available in qemu-arm,
I'm building arm 32 bit stuff.
qemu-arm -cpu help
Available CPUs:
arm1026
arm1136
arm1136-r2
arm1176
arm11mpcore
arm926
arm946
cortex-a15
cortex-a7
cortex-a8
cortex-a9
cortex-m0
cortex-m3
cortex-m33
cortex-m4
cortex-r5
cortex-r5f
max
pxa250
pxa255
pxa260
pxa261
pxa262
pxa270-a0
pxa270-a1
pxa270
pxa270-b0
pxa270-b1
pxa270-c0
pxa270-c5
sa1100
sa1110
ti925t
any
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1821430
Title:
qemu-user-arm (4.0.0-rc0) crashes
Status in QEMU:
New
Bug description:
I'm using qemu-user-arm for crosscompilation needs, usually via a wrapper.
qemu-user-arm (4.0.0-rc0) crashes with SIGILL on at least 2 instructions:
first case (sadly I don't have more data handy, can reproduce at a later time
if needed):
(gdb) x/i $pc
=> 0xfffce314: vseleq.f64 d0, d17, d0
second case (llvm-config):
qemu cmdline:
qemu-arm -strace -cpu max -r 5.0.0 -L /home/asavah/kross/build/rpi3/rootfs -E
LD_LIBRARY_PATH=/home/asavah/kross/build/rpi3/rootfs/usr/bin:/home/asavah/kross/build/rpi3/rootfs/usr/lib
/home/asavah/kross/build/rpi3/rootfs/usr/bin/llvm-config --shared-mode
--- SIGILL {si_signo=SIGILL, si_code=2, si_addr=0xf9f89f80} ---
qemu: uncaught target signal 4 (Illegal instruction) - core dumped
output from gdb(arm) attached to qemu-user-arm
Program received signal SIGILL, Illegal instruction.
0xf9f77f80 in ?? ()
(gdb) bt
#0 0xf9f77f80 in ?? ()
#1 0xfffd796c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) x/i $pc
=> 0xf9f77f80: vrintm.f64 d18, d18
The very same binaries when run with qemu-user-arm 3.1.0 (both from ubuntu
19.04 package and self built)
work flawlessly.
This is clearly a regression.
Please fix before releasing 4.0.0.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1821430/+subscriptions
[Qemu-devel] [Bug 1821430] Re: qemu-user-arm (4.0.0-rc0) crashes
As requested I tarred the failing binaries.
The first one (first case in the original report) is g-ir-compiler from
gobjact-introspection, this one has another interesting detail:
if compiled with -mcpu=cortex-a53 -mfpu=neon-fp-armv8 (the correct flags for
raspberry pi 3) it crashes on 4.0.0-rc, but works fine even on 4.0.0 if
compiled with -mcpu=cortex-a53 -mfpu=neon-vfpv4 , on 3.1.0 it runs fine with
-mfpu=neon-fp-armv8 .
The second one (second case in original report), I'm not sure if its the
llvm-config binary itself,
or the code from libLLVM so I attached the whole thing.
It only crashes if called with llvm-config --shared-mode , llvm-config
--version and llvm-config --ldflags works fine.
-mfpu=neon-vfpv4 does not help here, crashes anyway, but has worked fine with
3.1.0
** Attachment added: "bug1821430.tar.xz"
https://bugs.launchpad.net/qemu/+bug/1821430/+attachment/5248857/+files/bug1821430.tar.xz
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1821430
Title:
qemu-user-arm (4.0.0-rc0) crashes
Status in QEMU:
New
Bug description:
I'm using qemu-user-arm for crosscompilation needs, usually via a wrapper.
qemu-user-arm (4.0.0-rc0) crashes with SIGILL on at least 2 instructions:
first case (sadly I don't have more data handy, can reproduce at a later time
if needed):
(gdb) x/i $pc
=> 0xfffce314: vseleq.f64 d0, d17, d0
second case (llvm-config):
qemu cmdline:
qemu-arm -strace -cpu max -r 5.0.0 -L /home/asavah/kross/build/rpi3/rootfs -E
LD_LIBRARY_PATH=/home/asavah/kross/build/rpi3/rootfs/usr/bin:/home/asavah/kross/build/rpi3/rootfs/usr/lib
/home/asavah/kross/build/rpi3/rootfs/usr/bin/llvm-config --shared-mode
--- SIGILL {si_signo=SIGILL, si_code=2, si_addr=0xf9f89f80} ---
qemu: uncaught target signal 4 (Illegal instruction) - core dumped
output from gdb(arm) attached to qemu-user-arm
Program received signal SIGILL, Illegal instruction.
0xf9f77f80 in ?? ()
(gdb) bt
#0 0xf9f77f80 in ?? ()
#1 0xfffd796c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) x/i $pc
=> 0xf9f77f80: vrintm.f64 d18, d18
The very same binaries when run with qemu-user-arm 3.1.0 (both from ubuntu
19.04 package and self built)
work flawlessly.
This is clearly a regression.
Please fix before releasing 4.0.0.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1821430/+subscriptions
[Qemu-devel] [Bug 1821430] [NEW] qemu-user-arm (4.0.0-rc0) crashes
Public bug reported:
I'm using qemu-user-arm for crosscompilation needs, usually via a wrapper.
qemu-user-arm (4.0.0-rc0) crashes with SIGILL on at least 2 instructions:
first case (sadly I don't have more data handy, can reproduce at a later time
if needed):
(gdb) x/i $pc
=> 0xfffce314: vseleq.f64 d0, d17, d0
second case (llvm-config):
qemu cmdline:
qemu-arm -strace -cpu max -r 5.0.0 -L /home/asavah/kross/build/rpi3/rootfs -E
LD_LIBRARY_PATH=/home/asavah/kross/build/rpi3/rootfs/usr/bin:/home/asavah/kross/build/rpi3/rootfs/usr/lib
/home/asavah/kross/build/rpi3/rootfs/usr/bin/llvm-config --shared-mode
--- SIGILL {si_signo=SIGILL, si_code=2, si_addr=0xf9f89f80} ---
qemu: uncaught target signal 4 (Illegal instruction) - core dumped
output from gdb(arm) attached to qemu-user-arm
Program received signal SIGILL, Illegal instruction.
0xf9f77f80 in ?? ()
(gdb) bt
#0 0xf9f77f80 in ?? ()
#1 0xfffd796c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) x/i $pc
=> 0xf9f77f80: vrintm.f64 d18, d18
The very same binaries when run with qemu-user-arm 3.1.0 (both from ubuntu
19.04 package and self built)
work flawlessly.
This is clearly a regression.
Please fix before releasing 4.0.0.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1821430
Title:
qemu-user-arm (4.0.0-rc0) crashes
Status in QEMU:
New
Bug description:
I'm using qemu-user-arm for crosscompilation needs, usually via a wrapper.
qemu-user-arm (4.0.0-rc0) crashes with SIGILL on at least 2 instructions:
first case (sadly I don't have more data handy, can reproduce at a later time
if needed):
(gdb) x/i $pc
=> 0xfffce314: vseleq.f64 d0, d17, d0
second case (llvm-config):
qemu cmdline:
qemu-arm -strace -cpu max -r 5.0.0 -L /home/asavah/kross/build/rpi3/rootfs -E
LD_LIBRARY_PATH=/home/asavah/kross/build/rpi3/rootfs/usr/bin:/home/asavah/kross/build/rpi3/rootfs/usr/lib
/home/asavah/kross/build/rpi3/rootfs/usr/bin/llvm-config --shared-mode
--- SIGILL {si_signo=SIGILL, si_code=2, si_addr=0xf9f89f80} ---
qemu: uncaught target signal 4 (Illegal instruction) - core dumped
output from gdb(arm) attached to qemu-user-arm
Program received signal SIGILL, Illegal instruction.
0xf9f77f80 in ?? ()
(gdb) bt
#0 0xf9f77f80 in ?? ()
#1 0xfffd796c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) x/i $pc
=> 0xf9f77f80: vrintm.f64 d18, d18
The very same binaries when run with qemu-user-arm 3.1.0 (both from ubuntu
19.04 package and self built)
work flawlessly.
This is clearly a regression.
Please fix before releasing 4.0.0.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1821430/+subscriptions
[Qemu-devel] [Bug 1353149] [NEW] qemu 2.1.0 fails to start if number of cores is greater than 1.
Public bug reported: qemu (kvm) 2.1.0 (built from sources) fails to start if number of cores is greater than 1. relevant part of commandline arguments: /usr/bin/qemu-system-x86_64 -name test3 -S -machine pc- i440fx-2.1,accel=kvm,usb=off -cpu Westmere -m 4096 -realtime mlock=off -smp 1,maxcpus=4,sockets=1,cores=4,threads=1 the error reported is: qemu-system-x86_64: /home/asavah/pkgbuild/qemu-2.1.0/hw/i386/smbios.c:825: smbios_get_tables: Assertion `smbios_smp_sockets = 1' failed. 2014-08-05 21:45:35.825+: shutting down however setting 4 sockets with 1 core each allows me to start the machine just fine. the system is debian wheezy Linux hostname 3.16.0-hostname2 #2 SMP Mon Aug 4 17:02:16 EEST 2014 x86_64 GNU/Linux libvirt 1.2.7 (built from sources) ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1353149 Title: qemu 2.1.0 fails to start if number of cores is greater than 1. Status in QEMU: New Bug description: qemu (kvm) 2.1.0 (built from sources) fails to start if number of cores is greater than 1. relevant part of commandline arguments: /usr/bin/qemu-system-x86_64 -name test3 -S -machine pc- i440fx-2.1,accel=kvm,usb=off -cpu Westmere -m 4096 -realtime mlock=off -smp 1,maxcpus=4,sockets=1,cores=4,threads=1 the error reported is: qemu-system-x86_64: /home/asavah/pkgbuild/qemu-2.1.0/hw/i386/smbios.c:825: smbios_get_tables: Assertion `smbios_smp_sockets = 1' failed. 2014-08-05 21:45:35.825+: shutting down however setting 4 sockets with 1 core each allows me to start the machine just fine. the system is debian wheezy Linux hostname 3.16.0-hostname2 #2 SMP Mon Aug 4 17:02:16 EEST 2014 x86_64 GNU/Linux libvirt 1.2.7 (built from sources) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1353149/+subscriptions
[Qemu-devel] [Bug 1353149] Re: qemu 2.1.0 fails to start if number of cores is greater than 1.
I forgot to mention that VM was created and managed remotely via virt-manager 0.9.5 from another host. I used custom cpu topology. however this config worked fine on qemu 2.0.0 with virt-manager 0.9.5 just tried virt-manager 1.0.1 - it creates the proper argument -smp 4,maxcpus=4,sockets=1,cores=4,threads=1 so this was a virt-manager bug already fixed upstream. this bug can be closed :) -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1353149 Title: qemu 2.1.0 fails to start if number of cores is greater than 1. Status in QEMU: New Bug description: qemu (kvm) 2.1.0 (built from sources) fails to start if number of cores is greater than 1. relevant part of commandline arguments: /usr/bin/qemu-system-x86_64 -name test3 -S -machine pc- i440fx-2.1,accel=kvm,usb=off -cpu Westmere -m 4096 -realtime mlock=off -smp 1,maxcpus=4,sockets=1,cores=4,threads=1 the error reported is: qemu-system-x86_64: /home/asavah/pkgbuild/qemu-2.1.0/hw/i386/smbios.c:825: smbios_get_tables: Assertion `smbios_smp_sockets = 1' failed. 2014-08-05 21:45:35.825+: shutting down however setting 4 sockets with 1 core each allows me to start the machine just fine. the system is debian wheezy Linux hostname 3.16.0-hostname2 #2 SMP Mon Aug 4 17:02:16 EEST 2014 x86_64 GNU/Linux libvirt 1.2.7 (built from sources) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1353149/+subscriptions
