diff options
Diffstat (limited to '')
| -rw-r--r-- | results/classifier/108/other/1568 | 54 | ||||
| -rw-r--r-- | results/classifier/108/other/1568107 | 31 | ||||
| -rw-r--r-- | results/classifier/108/other/1568589 | 66 | ||||
| -rw-r--r-- | results/classifier/108/other/1568621 | 49 |
4 files changed, 200 insertions, 0 deletions
diff --git a/results/classifier/108/other/1568 b/results/classifier/108/other/1568 new file mode 100644 index 00000000..18b0d8a5 --- /dev/null +++ b/results/classifier/108/other/1568 @@ -0,0 +1,54 @@ +other: 0.899 +KVM: 0.865 +performance: 0.855 +device: 0.854 +debug: 0.848 +graphic: 0.843 +semantic: 0.843 +PID: 0.822 +boot: 0.811 +permissions: 0.758 +socket: 0.750 +vnc: 0.742 +network: 0.651 +files: 0.596 + +qemu-system-m68k fails whenever the option "-d cpu_reset" is specified +Description of problem: +When specifying the option "-d cpu_reset", the following output is generated, and QEMU eventually crashes with a Segmentation fault: +``` +CPU Reset (CPU 0) +D0 = 00000000 A0 = 00000000 F0 = 0000 0000000000000000 ( 0) +D1 = 00000000 A1 = 00000000 F1 = 0000 0000000000000000 ( 0) +D2 = 00000000 A2 = 00000000 F2 = 0000 0000000000000000 ( 0) +D3 = 00000000 A3 = 00000000 F3 = 0000 0000000000000000 ( 0) +D4 = 00000000 A4 = 00000000 F4 = 0000 0000000000000000 ( 0) +D5 = 00000000 A5 = 00000000 F5 = 0000 0000000000000000 ( 0) +D6 = 00000000 A6 = 00000000 F6 = 0000 0000000000000000 ( 0) +D7 = 00000000 A7 = 00000000 F7 = 0000 0000000000000000 ( 0) +PC = 00000000 qemu: fatal: Bad CC_OP 0 +D0 = 00000000 A0 = 00000000 F0 = 0000 0000000000000000 ( 0) +D1 = 00000000 A1 = 00000000 F1 = 0000 0000000000000000 ( 0) +D2 = 00000000 A2 = 00000000 F2 = 0000 0000000000000000 ( 0) +D3 = 00000000 A3 = 00000000 F3 = 0000 0000000000000000 ( 0) +D4 = 00000000 A4 = 00000000 F4 = 0000 0000000000000000 ( 0) +D5 = 00000000 A5 = 00000000 F5 = 0000 0000000000000000 ( 0) +D6 = 00000000 A6 = 00000000 F6 = 0000 0000000000000000 ( 0) +D7 = 00000000 A7 = 00000000 F7 = 0000 0000000000000000 ( 0) +... +D0 = 00000000 A0 = 00000000 F0 = 0000 0000000000000000 ( 0) +D1 = 00000000 A1 = 00000000 F1 = 0000 0000000000000000 ( 0) +D2 = 00000000 A2 = 00000000 F2 = 0000 0000000000000000 ( 0) +D3 = 00000000 A3 = 00000000 F3 = 0000 0000000000000000 ( 0) +D4 = 00000000 A4 = 00000000 F4 = 0000 0000000000000000 ( 0) +D5 = 00000000 A5 = 00000000 F5 = 0000 0000000000000000 ( 0) +D6 = 00000000 A6 = 00000000 F6 = 0000 0000000000000000 ( 0) +D7 = 00000000 A7 = 00000000 F7 = 0000 0000000000000000 ( 0) +PC = 00000000 qemu: fatal: Bad CC_OP 0 +Segmentation fault (core dumped) +``` +This also happens with the other m68k machine types. +Steps to reproduce: +1. Run QEMU with the given command line. +Additional information: + diff --git a/results/classifier/108/other/1568107 b/results/classifier/108/other/1568107 new file mode 100644 index 00000000..21c48f3e --- /dev/null +++ b/results/classifier/108/other/1568107 @@ -0,0 +1,31 @@ +device: 0.896 +graphic: 0.894 +semantic: 0.675 +network: 0.658 +debug: 0.598 +performance: 0.547 +permissions: 0.535 +files: 0.525 +PID: 0.483 +socket: 0.469 +boot: 0.457 +other: 0.446 +vnc: 0.424 +KVM: 0.025 + +x86_64 linux-user: setup_rt_frame: not implemented + +Trying to run this binary (https://github.com/ethcore/parity/releases/download/v1.0.1/parity_linux_1.0.1-0_amd64.deb) under qemu-x86_64 on ARM, ends like this: + +$ qemu-x86_64 parity --pruning fast + +setup_rt_frame: not implemented +qemu: uncaught target signal 11 (Segmentation fault) - core dumped +Segmentation fault + +Yes, the x86-64 linux-user target does not have any implementation of signal handling. + + +This bug was fixed in 2.9 (we added x86-64 linux-user signal handling support.) + + diff --git a/results/classifier/108/other/1568589 b/results/classifier/108/other/1568589 new file mode 100644 index 00000000..28acdf25 --- /dev/null +++ b/results/classifier/108/other/1568589 @@ -0,0 +1,66 @@ +device: 0.917 +graphic: 0.909 +semantic: 0.851 +files: 0.827 +PID: 0.813 +other: 0.798 +debug: 0.711 +permissions: 0.681 +socket: 0.663 +network: 0.646 +performance: 0.633 +vnc: 0.585 +boot: 0.526 +KVM: 0.093 + +Compile for os x host failed + +Hello QEMU, + +I try compile qemu from git pulled by me today and have a troubles: + + GEN trace/generated-helpers.c + CC aarch64-softmmu/trace/generated-helpers.o + LINK aarch64-softmmu/qemu-system-aarch64 +Undefined symbols for architecture x86_64: + "_event_notifier_init_fd", referenced from: + _process_msg in ivshmem.o +ld: symbol(s) not found for architecture x86_64 +clang: error: linker command failed with exit code 1 (use -v to see invocation) +make[1]: *** [qemu-system-aarch64] Error 1 +make: *** [subdir-aarch64-softmmu] Error 2 + +Host: +# uname -a +Darwin MacBook-Pro 15.4.0 Darwin Kernel Version 15.4.0: Fri Feb 26 22:08:05 PST 2016; root:xnu-3248.40.184~3/RELEASE_X86_64 x86_64 + +# ./configure +Configure: http://pastebin.com/L9ytLFDE + +# make -v +GNU Make 3.81 +Copyright (C) 2006 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. + +This program built for i386-apple-darwin11.3.0 + +Also for i386 + + LINK i386-softmmu/qemu-system-i386 +Undefined symbols for architecture x86_64: + "_event_notifier_init_fd", referenced from: + _process_msg in ivshmem.o +ld: symbol(s) not found for architecture x86_64 +clang: error: linker command failed with exit code 1 (use -v to see invocation) +make[1]: *** [qemu-system-i386] Error 1 +make: *** [subdir-i386-softmmu] Error 2 + +fix: http://patchwork.ozlabs.org/patch/603499/ + +According to the discussion for the patch that you've mentioned, the problem should go away after a "make distclean". Can you still reproduce it after doing a fresh build? + +Closing this bug since the submitter never responded to Thomas' query in comment #4 in 2016, and we believe it to have been a transient issue fixed by 'make distclean'. + + diff --git a/results/classifier/108/other/1568621 b/results/classifier/108/other/1568621 new file mode 100644 index 00000000..7c7f985e --- /dev/null +++ b/results/classifier/108/other/1568621 @@ -0,0 +1,49 @@ +permissions: 0.633 +other: 0.631 +boot: 0.590 +debug: 0.580 +performance: 0.567 +vnc: 0.551 +KVM: 0.547 +device: 0.547 +files: 0.500 +network: 0.487 +graphic: 0.479 +semantic: 0.470 +socket: 0.436 +PID: 0.426 + +input-linux misdetects Logitech keyboard as a mouse + +The new input-linux.c code misdetects my Logitech K350 keyboard as a mouse. The bug is in the input_linux_complete function. The evdev for this keyboard returns an "evtmap" with the EV_REL bit set. Full evtmap is 0x0012001F. Using a different keyboard everything works as intended, so my configuration and setup are correct otherwise. + + +Suggestion: + +I suggest adding an object property called something like "type" where the user can specify what the device type is manually. This K350 keyboard shows that "evtmap" cannot be used to reliably detect the device type. Since specifying the device type manually is not an undue burden, perhaps it should be a required option and there should be no autodetection? + + +System: + +Arch linux, using qemu-git AUR package installed 20160409. + + +Command line: + +LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=none /usr/sbin/qemu-system-x86_64 -name win10,debug-threads=on -S -machine pc-i440fx-2.4,accel=kvm,usb=off,vmport=off -cpu host,kvm=off -drive file=/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/var/lib/libvirt/qemu/nvram/win10_VARS.fd,if=pflash,format=raw,unit=1 -m 8196 -realtime mlock=off -smp 8,sockets=1,cores=4,threads=2 -uuid 58623778-9d9d-4d30-8ec0-b37e12a30fdc -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-17-win10/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x6.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x6 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x6.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x6.0x2 -drive file=/var/lib/libvirt/images/ISOs/Win10_1511_English_x64.iso,format=raw,if=none,id=drive-ide0-0-1,readonly=on -device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 -drive file=/var/lib/libvirt/images/ISOs/virtio-win-0.1.112.iso,format=raw,if=none,id=drive-ide0-1-0,readonly=on -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/dev/sda,format=raw,if=none,id=drive-virtio-disk1 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,drive=drive-virtio-disk1,id=virtio-disk1,bootindex=1 -netdev tap,fd=26,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:70:8a:db,bus=pci.0,addr=0x3 -netdev tap,fd=28,id=hostnet1 -device rtl8139,netdev=hostnet1,id=net1,mac=d4:be:d9:56:2e:35,bus=pci.0,addr=0x9 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device vfio-pci,host=04:00.0,id=hostdev0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -object input-linux,id=kbd1,evdev=/dev/input/event19,grab_all=on -object input-linux,id=kbb2,evdev=/dev/input/event2 -msg timestamp=on + +The QEMU project is currently considering to move its bug tracking to +another system. For this we need to know which bugs are still valid +and which could be closed already. Thus we are setting older bugs to +"Incomplete" now. + +If you still think this bug report here is valid, then please switch +the state back to "New" within the next 60 days, otherwise this report +will be marked as "Expired". Or please mark it as "Fix Released" if +the problem has been solved with a newer version of QEMU already. + +Thank you and sorry for the inconvenience. + + +[Expired for QEMU because there has been no activity for 60 days.] + |