12 files changed, 599 insertions, 0 deletions
diff --git a/results/classifier/108/other/62 b/results/classifier/108/other/62
new file mode 100644
index 00000000..4757ecb3
--- /dev/null
+++ b/results/classifier/108/other/62
@@ -0,0 +1,16 @@
+performance: 0.835
+device: 0.765
+debug: 0.719
+boot: 0.530
+network: 0.471
+graphic: 0.419
+semantic: 0.146
+PID: 0.141
+vnc: 0.047
+other: 0.029
+KVM: 0.016
+socket: 0.015
+files: 0.011
+permissions: 0.010
+
+[OSS-Fuzz] ahci: stack overflow in ahci_cond_start_engines
diff --git a/results/classifier/108/other/620 b/results/classifier/108/other/620
new file mode 100644
index 00000000..284db31e
--- /dev/null
+++ b/results/classifier/108/other/620
@@ -0,0 +1,16 @@
+device: 0.826
+network: 0.734
+debug: 0.498
+performance: 0.445
+boot: 0.375
+PID: 0.318
+files: 0.293
+graphic: 0.288
+socket: 0.286
+semantic: 0.226
+vnc: 0.218
+permissions: 0.111
+other: 0.085
+KVM: 0.045
+
+QEMU gdbstub should add memtag support for aarch64 MTE
diff --git a/results/classifier/108/other/621 b/results/classifier/108/other/621
new file mode 100644
index 00000000..44c7355b
--- /dev/null
+++ b/results/classifier/108/other/621
@@ -0,0 +1,16 @@
+device: 0.746
+performance: 0.732
+KVM: 0.377
+network: 0.340
+permissions: 0.337
+other: 0.289
+semantic: 0.289
+debug: 0.261
+graphic: 0.255
+PID: 0.218
+vnc: 0.160
+socket: 0.144
+files: 0.104
+boot: 0.084
+
+make after configure not working
diff --git a/results/classifier/108/other/622367 b/results/classifier/108/other/622367
new file mode 100644
index 00000000..df50a036
--- /dev/null
+++ b/results/classifier/108/other/622367
@@ -0,0 +1,34 @@
+graphic: 0.911
+debug: 0.886
+performance: 0.829
+device: 0.744
+other: 0.742
+network: 0.725
+socket: 0.695
+PID: 0.683
+files: 0.681
+semantic: 0.663
+permissions: 0.600
+vnc: 0.534
+boot: 0.401
+KVM: 0.335
+
+No BIOS MPFP structure with smp=92 and more
+
+qemu 0.12.2, SeaBios 0.5.1, running qemu-system-x86_64.exe with option -smp.
+If smp>=92 then no MP floating point structure present in 1 Mb. This may be verified by pmemsave 0 0x100000 in debugger and search for _MP_ signature in file.
+
+qemu 0.10.5 (bios build 05/08/09) can smp=128 (and even 255 if not hangs :).
+
+Host win 7 x64 RTM 7600.
+
+QEMU 0.12 is quite outdated nowadays ... can you still reproduce this issue with the latest version of QEMU (currently version 2.8)?
+
+Man, really? xD
+6 years have passed...
+Close the ticket please, I don't have this code anymore.
+...
+still laughing... sorry
+
+Better late than never ;-)
+
diff --git a/results/classifier/108/other/623 b/results/classifier/108/other/623
new file mode 100644
index 00000000..cb8f52b9
--- /dev/null
+++ b/results/classifier/108/other/623
@@ -0,0 +1,23 @@
+device: 0.869
+graphic: 0.778
+permissions: 0.762
+files: 0.749
+network: 0.716
+socket: 0.714
+vnc: 0.690
+boot: 0.672
+semantic: 0.622
+PID: 0.544
+other: 0.397
+debug: 0.388
+performance: 0.372
+KVM: 0.112
+
+Allow direct access to windows disks on hyper-V as well as virtiofsd, DAX
+Additional information:
+Depends on, first needs fixing of, Issue #346 / Issue #430 , Essentially accel=whpx is not working/is broken/has regression.
+```
+J:\>E:\scoopg\shims\qemu-system-x86_64.exe --version
+QEMU emulator version 6.1.0 (v6.1.0-11882-g7deea770bf-dirty)
+Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers
+```
diff --git a/results/classifier/108/other/623852 b/results/classifier/108/other/623852
new file mode 100644
index 00000000..3ee7004d
--- /dev/null
+++ b/results/classifier/108/other/623852
@@ -0,0 +1,338 @@
+device: 0.865
+boot: 0.863
+other: 0.862
+permissions: 0.858
+debug: 0.853
+socket: 0.848
+performance: 0.847
+semantic: 0.843
+PID: 0.838
+graphic: 0.824
+files: 0.816
+network: 0.802
+vnc: 0.767
+KVM: 0.740
+
+PPC emulation loops on booting a FreeBSD kernel
+
+Has anyone tried booting FreeBSD8.1-ppc under QEMU (Linux x86_64 host; PPC guest)?  I can get Linux/PPC to run fine, and FreeBSD8.1-i386 as well; but there seems to be a problem with whatever the FreeBSD8.1 kernel does, that QEMU's PPC emulation can't handle.
+
+I am using the latest version of QEMU from GIT as of 25/8/10.  I don't know how to get a "git commit hash", so I can't quote it.
+
+The kernel starts OK then loops after "Kernel entry at 0x100100 ...".
+
+The command I am running is
+
+qemu-system-ppc -cdrom FreeBSD-8.1-RELEASE-powerpc-disc1.iso -hda freebsd8.1-ppc -m 94 -boot d"
+
+I obtained the kernel from ftp://ftp.freebsd.org/pub/FreeBSD/releases/powerpc/ISO-IMAGES/8.1/FreeBSD-8.1-RELEASE-powerpc-disc1.iso.
+
+I did a "git log" command, and the first line is "2446333cd5b5c985f6517dee7004e542ecacd21c".  Is that what you mean by a git hash?  If so, I hope it helps.
+
+It looks like a firmware issue. Please report this to <email address hidden>. You get the output below by using the -nographic option.
+
+
+>> =============================================================
+>> OpenBIOS 1.0 [Aug 17 2010 14:41]
+>> Configuration device id QEMU version 1 machine id 2
+>> CPUs: 1
+>> Memory: 512M
+>> UUID: 00000000-0000-0000-0000-000000000000
+>> CPU type PowerPC,750
+Welcome to OpenBIOS v1.0 built on Aug 17 2010 14:41
+Trying cd:,\\:tbxi...
+Consoles: Open Firmware console  
+
+FreeBSD/powerpc Open Firmware loader, Revision 0.1
+(<email address hidden>, Sun Jul 18 04:50:11 UTC 2010)
+Memory: 524288KB
+Booted from: cd
+
+Loading /boot/defaults/loader.conf 
+/boot/kernel/kernel data=0x72c6b8+0x3e280 syms=[0x4+0x5ac10+0x4+0x7d8ad]
+/
+Hit [Enter] to boot immediately, or any other key for command prompt.
+Booting [/boot/kernel/kernel]...               
+Kernel entry at 0x100100 ...
+panic: OFW translations above 32-bit boundary!
+Uptime: 1s
+
+
+I have been asked to forward this to you - could you help, please?
+
+Thanks!
+
+-Nigel
+
+
+-------- Original Message --------
+
+It looks like a firmware issue. Please report this to
+<email address hidden>. You get the output below by using the -nographic
+option.
+
+
+>>  =============================================================
+>>  OpenBIOS 1.0 [Aug 17 2010 14:41]
+>>  Configuration device id QEMU version 1 machine id 2
+>>  CPUs: 1
+>>  Memory: 512M
+>>  UUID: 00000000-0000-0000-0000-000000000000
+>>  CPU type PowerPC,750
+Welcome to OpenBIOS v1.0 built on Aug 17 2010 14:41
+Trying cd:,\\:tbxi...
+Consoles: Open Firmware console
+
+FreeBSD/powerpc Open Firmware loader, Revision 0.1
+(<email address hidden>, Sun Jul 18 04:50:11 UTC 2010)
+Memory: 524288KB
+Booted from: cd
+
+Loading /boot/defaults/loader.conf
+/boot/kernel/kernel data=0x72c6b8+0x3e280 syms=[0x4+0x5ac10+0x4+0x7d8ad]
+/
+Hit [Enter] to boot immediately, or any other key for command prompt.
+Booting [/boot/kernel/kernel]...
+Kernel entry at 0x100100 ...
+panic: OFW translations above 32-bit boundary!
+Uptime: 1s
+
+-- 
+PPC emulation loops on booting a FreeBSD kernel
+https://bugs.launchpad.net/bugs/623852
+You received this bug notification because you are a direct subscriber
+of the bug.
+
+Status in QEMU: New
+
+Bug description:
+Has anyone tried booting FreeBSD8.1-ppc under QEMU (Linux x86_64 host; PPC guest)?  I can get Linux/PPC to run fine, and FreeBSD8.1-i386 as well; but there seems to be a problem with whatever the FreeBSD8.1 kernel does, that QEMU's PPC emulation can't handle.
+
+I am using the latest version of QEMU from GIT as of 25/8/10.  I don't know how to get a "git commit hash", so I can't quote it.
+
+The kernel starts OK then loops after "Kernel entry at 0x100100 ...".
+
+The command I am running is
+
+qemu-system-ppc -cdrom FreeBSD-8.1-RELEASE-powerpc-disc1.iso -hda freebsd8.1-ppc -m 94 -boot d"
+
+I obtained the kernel from ftp://ftp.freebsd.org/pub/FreeBSD/releases/powerpc/ISO-IMAGES/8.1/FreeBSD-8.1-RELEASE-powerpc-disc1.iso.
+
+To unsubscribe from this bug, go to:
+https://bugs.launchpad.net/qemu/+bug/623852/+subscribe
+
+
+On 25/08/10 10:08, agraf wrote:
+> It looks like a firmware issue. Please report this to
+> <email address hidden>. You get the output below by using the -nographic
+> option.
+>    
+I have done so, though to be honest I don't see that panic even if I use 
+-nographic, QEMU still silently loops for me.
+>>> =============================================================
+>>> OpenBIOS 1.0 [Aug 17 2010 14:41]
+>>> Configuration device id QEMU version 1 machine id 2
+>>> CPUs: 1
+>>> Memory: 512M
+>>> UUID: 00000000-0000-0000-0000-000000000000
+>>> CPU type PowerPC,750
+>>>        
+> Welcome to OpenBIOS v1.0 built on Aug 17 2010 14:41
+> Trying cd:,\\:tbxi...
+> Consoles: Open Firmware console
+>
+> FreeBSD/powerpc Open Firmware loader, Revision 0.1
+> (<email address hidden>, Sun Jul 18 04:50:11 UTC 2010)
+> Memory: 524288KB
+> Booted from: cd
+>
+> Loading /boot/defaults/loader.conf
+> /boot/kernel/kernel data=0x72c6b8+0x3e280 syms=[0x4+0x5ac10+0x4+0x7d8ad]
+> /
+> Hit [Enter] to boot immediately, or any other key for command prompt.
+> Booting [/boot/kernel/kernel]...
+> Kernel entry at 0x100100 ...
+> panic: OFW translations above 32-bit boundary!
+> Uptime: 1s
+>
+>    
+-Nigel
+
+-- 
+Nigel Horne. Arranger, Adjudicator, Band Trainer, Composer, Tutor, Typesetter.
+NJH Music, ICQ#20252325, twitter: @nigelhorne
+<email address hidden> http://www.bandsman.co.uk
+
+
+Please confirm that you tested with qemu-system-ppc, not qemu-system-ppc64.
+
+I got the "above 32-bit boundary" message with ppc64 - but that's to be expected.  And given that I didn't see your message running 32-bit PPC I want to ensure that you did try with the 32-bit emulator.
+
+Also I can confirm that I have this problem on QEMU.
+I had tried booting FreeBSD8.1-ppc under QEMU (Linux x86_64 host; PPC guest) but there seems to be a problem with whatever the FreeBSD8.1 kernel does, that QEMU's PPC emulation can't handle.
+
+I am using the latest version of QEMU from GIT as of 11/9/10.
+The kernel starts OK then loops after "Kernel entry at 0x100100 ...".
+
+Hi.
+
+The same issue from here.
+
+---------------------------------------------
+me@host:~$ qemu-system-ppc -cdrom FreeBSD-8.2-RELEASE-powerpc-disc1.iso \
+-hda freebsd8.2-ppc.img -m 94 -boot d -bios /usr/share/openbios/openbios-ppc -nographic
+qemu: warning: could not load VGA bios 'video.x'
+
+>> =============================================================
+>> OpenBIOS 1.0 [Feb 19 2011 11:37]
+>> Configuration device id QEMU version 1 machine id 2
+>> CPUs: 1
+>> Memory: 94M
+>> UUID: 00000000-0000-0000-0000-000000000000
+>> CPU type PowerPC,750
+Welcome to OpenBIOS v1.0 built on Feb 19 2011 11:37
+Trying cd:,\\:tbxi...
+Consoles: Open Firmware console  
+
+FreeBSD/powerpc Open Firmware loader, Revision 0.1
+(<email address hidden>, Fri Feb 18 18:49:01 UTC 2011)
+Memory: 96256KB
+Booted from: cd
+
+Loading /boot/defaults/loader.conf 
+/boot/kernel/kernel data=0x7417ac+0x3e3dc syms=[0x4+0x5c110+0x4+0x7f9c7]
+|
+Hit [Enter] to boot immediately, or any other key for command prompt.
+Booting [/boot/kernel/kernel]...               
+Kernel entry at 0x100100 ...
+invalid/unsupported opcode: 1f - 12 - 05 (7d200164) 005a6ae0 0
+---------------------------------------------------
+
+My host machine is a Debian "squeeze".
+I'm using the openbios-ppc from "wheeze" package.
+
+QEMU version: 0.12.5+dfsg-3squeeze1
+openbios-ppc version: 1.0+svn1018-1_all
+freebsd version: FreeBSD-8.2-RELEASE-powerpc-disc1.iso
+
+
+The only diference from previos posts is the last line.
+
+------------------------
+invalid/unsupported opcode: 1f - 12 - 05 (7d200164) 005a6ae0 0
+------------------------
+
+Thanks.
+
+On 732c66ce641c69702a7e7fdb73b68f0c1b583ab5, I instead get:
+
+
+Welcome to OpenBIOS v1.1 built on Oct 2 2013 22:57
+Trying cd:,\\:tbxi...
+Consoles: Open Firmware console  
+
+FreeBSD/powerpc Open Firmware loader, Revision 0.1
+(<email address hidden>, Sun Jul 18 04:50:11 UTC 2010)
+Memory: 96256KB
+Booted from: /pci@80000000/mac-io@3/ata-2@21000/cdrom@0
+
+panic: free: guard1 fail @ 0x5d80418 from /usr/src/sys/boot/powerpc/ofw/../../common/interp_parse.c:184
+--> Press a key on the console to reboot <--
+
+
+Latest version from git, using FreeBSD10.0:
+
+qemu-system-ppc64 -cdrom FreeBSD-10.0-RELEASE-powerpc-disc1.iso -hda freebsd10.0-ppc -m 256 -boot d -k en-us:
+
+
+
+SLOF **********************************************************************
+QEMU Starting
+ Build Date = Mar 13 2015 22:37:28
+ FW Version = git-c89b0df661c0a6bf
+ Press "s" to enter Open Firmware.
+
+Populating /vdevice methods
+Populating /vdevice/vty@71000000
+Populating /vdevice/nvram@71000001
+Populating /vdevice/l-lan@71000002
+Populating /vdevice/v-scsi@71000003
+       SCSI: Looking for devices
+          8000000000000000 DISK     : "QEMU     QEMU HARDDISK    2.3."
+          8200000000000000 CD-ROM   : "QEMU     QEMU CD-ROM      2.3."
+Populating /pci@800000020000000
+ Adapters on 0800000020000000
+                     00 0000 (D) : 1234 1111    qemu vga
+                     00 0800 (D) : 106b 003f    serial bus [ usb-ohci ]
+No NVRAM common partition, re-initializing...
+Installing QEMU fb
+
+
+
+Scanning USB 
+  OHCI: initializing
+    USB Keyboard 
+    USB mouse 
+No console specified using screen & keyboard
+     
+
+
+  Welcome to Open Firmware
+
+  Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
+  This program and the accompanying materials are made available
+  under the terms of the BSD License available at
+  http://www.opensource.org/licenses/bsd-license.php
+
+
+Trying to load:  from: cdrom ...   Successfully loaded
+Trying to write invalid spr 540 (0x21c) at 0000000000731954
+ 
+
+( 700 ) Program Exception [ 7319dc ]
+
+
+    R0 .. R7           R8 .. R15         R16 .. R23         R24 .. R31
+0000000000000000   0000000000000000   0000000000000000   000000000048099c   
+00000000009d9e50   0000000000000000   0000000000000000   00000000009d9ef4   
+0000000000a5e160   000000000000bf30   0000000000000000   00000000007319dc   
+00000000009d9f2c   0000000000000000   0000000000000000   000000000048099c   
+000000000048099c   0000000000000000   0000000000c0a000   0000000000000000   
+00000000007319dc   0000000000000000   0000000000000004   0000000000000000   
+000000000048099c   0000000000000000   0000000000000000   0000000000002000   
+00000000009d9ef4   0000000000000000   0000000000000000   00000000009d9e50   
+
+    CR / XER           LR / CTR          SRR0 / SRR1        DAR / DSISR
+        84000022   0000000000731a14   0000000000731954   0000000000000000   
+0000000000000000   00000000007319dc   0000000000082000           00000000  
+
+I used the -nographic option as well, but lost it in the copy and paste.
+
+Nigel, looking at https://www.freebsd.org/platforms/ppc.html it seems like FreeBSD does not support the pseries machines yet, only some flavours of PowerMac machines. So you should either use the "qemu-system-ppc" binary (without the "64" suffix), or you've got to specify one of the Mac machines, i.e. either "-M g3beige" or "-M mac99".
+
+Hi, Nigel.
+
+Support for powerpc64 is available since FreeBSD 9.0-RELEASE, I think.
+FreeBSD 11.2-RC2 boots fine in QEMU (at commit 46012db666990ff2eed1d3dc)
+running on an x86 host with accel=tcg.  Below are the steps I have
+followed to boot it.
+
+Build QEMU:
+
+$ mkdir build && cd build
+$ ../configure --target-list=ppc64-softmmu
+$ make -j$(nproc)
+
+Boot FreeBSD:
+
+$ wget http://ftp.freebsd.org/pub/FreeBSD/releases/powerpc/powerpc64/ISO-IMAGES/11.2/FreeBSD-11.2-RC2-powerpc-powerpc64-disc1.iso
+$ ./qemu-img create -f qcow2 freebsd.qcow2 10G
+$ ./ppc64-softmmu/qemu-system-ppc64 -name freebsd -machine pseries,accel=tcg,usb=off -m 1024 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -nographic -no-user-config -nodefaults -rtc base=utc -no-shutdown -boot strict=on -device pci-bridge,chassis_nr=1,id=pci.1,bus=pci.0,addr=0x1 -device pci-ohci,id=usb,bus=pci.0,addr=0x2 -device spapr-vscsi,id=scsi0,reg=0x2000 -drive file=freebsd.qcow2,format=qcow2,if=none,id=drive-scsi0-0-0-0 -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1 -drive file=FreeBSD-11.2-RC2-powerpc-powerpc64-disc1.iso,format=raw,if=none,id=drive-scsi0-0-1-0,readonly=on -device scsi-cd,bus=scsi0.0,channel=0,scsi-id=1,lun=0,drive=drive-scsi0-0-1-0,id=scsi0-0-1-0,bootindex=2 -netdev user,id=hostnet0 -device spapr-vlan,netdev=hostnet0,id=net0,mac=4c:45:42:45:01:18,reg=0x1000 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on -serial mon:stdio
+
+Since this bug is almost 8 years old and FreeBSD powerpc64 seems to be
+working just fine, I will close it.  Feel free to submit a new one if
+needed.
+
+Cheers
+Murilo
+
diff --git a/results/classifier/108/other/625 b/results/classifier/108/other/625
new file mode 100644
index 00000000..ac662fda
--- /dev/null
+++ b/results/classifier/108/other/625
@@ -0,0 +1,38 @@
+graphic: 0.799
+device: 0.746
+permissions: 0.581
+performance: 0.578
+PID: 0.390
+vnc: 0.371
+semantic: 0.360
+files: 0.275
+debug: 0.224
+boot: 0.198
+network: 0.176
+socket: 0.152
+KVM: 0.149
+other: 0.074
+
+qemu-hppa floating point POWER function is incorrect
+Description of problem:
+The floating point power function produces incorrect values, and possibly stack misshapes as well.
+Steps to reproduce:
+1. $ hppa1.1-unknown-linux-gnu-gcc pow.c -o pow -lm -static
+2. $ qemu-hppa pow
+3. the expected result is 10.0 ^ 6.0 = 6000000.0, instead of 403.45
+Additional information:
+Example C source to reproduce, pow.c:
+```
+#include <stdio.h>
+#include <math.h>
+int main()
+{
+    double base, expo, res;
+    base=10.0;
+    expo=6.0;
+    // res sould be 1e+6
+    res = pow(base, expo);
+    printf("%.1lf^%.1lf = %.2lf\n", base, expo, res);
+    return 0;
+}
+```
diff --git a/results/classifier/108/other/626 b/results/classifier/108/other/626
new file mode 100644
index 00000000..21acf0ba
--- /dev/null
+++ b/results/classifier/108/other/626
@@ -0,0 +1,16 @@
+performance: 0.696
+network: 0.682
+debug: 0.659
+device: 0.641
+graphic: 0.415
+semantic: 0.372
+boot: 0.369
+files: 0.197
+other: 0.175
+PID: 0.154
+socket: 0.130
+permissions: 0.124
+vnc: 0.106
+KVM: 0.035
+
+plugin reference to qemu_plugin_hwaddr_phys_addr fails to dynamically link
diff --git a/results/classifier/108/other/628 b/results/classifier/108/other/628
new file mode 100644
index 00000000..3e3afdb4
--- /dev/null
+++ b/results/classifier/108/other/628
@@ -0,0 +1,23 @@
+device: 0.853
+network: 0.823
+graphic: 0.729
+files: 0.695
+socket: 0.639
+performance: 0.634
+boot: 0.626
+vnc: 0.592
+semantic: 0.591
+permissions: 0.524
+debug: 0.471
+PID: 0.459
+other: 0.353
+KVM: 0.075
+
+nested virtualization on whpx
+Additional information:
+Depends on, first needs fixing of, Issue #346 / Issue #430 , Essentially accel=whpx is not working/is broken/has regression.
+```
+PS J:\> E:\scoopg\shims\qemu-system-x86_64.exe  --version
+QEMU emulator version 6.1.0 (v6.1.0-11882-g7deea770bf-dirty)
+Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers
+```
diff --git a/results/classifier/108/other/628082 b/results/classifier/108/other/628082
new file mode 100644
index 00000000..1676fe5a
--- /dev/null
+++ b/results/classifier/108/other/628082
@@ -0,0 +1,31 @@
+device: 0.820
+graphic: 0.686
+network: 0.655
+debug: 0.577
+socket: 0.554
+permissions: 0.523
+vnc: 0.486
+semantic: 0.443
+other: 0.399
+files: 0.393
+PID: 0.377
+boot: 0.317
+performance: 0.307
+KVM: 0.203
+
+nl-be keymap is wrong
+
+As mentioned on https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/429965 as well as the kvm mailinglist (http://thread.gmane.org/gmane.comp.emulators.kvm.devel/14413), the nl-be keymap does not work. The number keys above the regular keys (non-numeric keypad numbers) as well as vital keys such as slash, backslash, dash, ... are not working.
+
+The nl-be keymap that is presented in the above URLs (and also attached to this bug) does work properly.
+
+Would it be possible to include this keymap rather than the current one?
+
+
+
+Hi, is this still a problem with the latest version of QEMU? If yes, please submit your keymap as a patch to the qemu-devel mailing list (see http://qemu-project.org/Contribute/SubmitAPatch for details). Thanks!
+
+There have been quite a lot of changes with regards to keyboard mapping in QEMU recently, could you please try again with QEMU 2.12 to see whether this has been fixed now?
+
+[Expired for QEMU because there has been no activity for 60 days.]
+
diff --git a/results/classifier/108/other/629 b/results/classifier/108/other/629
new file mode 100644
index 00000000..4305b289
--- /dev/null
+++ b/results/classifier/108/other/629
@@ -0,0 +1,25 @@
+graphic: 0.875
+device: 0.767
+boot: 0.638
+other: 0.506
+semantic: 0.499
+permissions: 0.428
+socket: 0.419
+performance: 0.374
+debug: 0.336
+files: 0.286
+PID: 0.204
+network: 0.172
+vnc: 0.154
+KVM: 0.023
+
+Trying to use EGA or VGA functions from QBASIC doesn't work
+Description of problem:
+QBASIC can't start any graphics mode beyond CGA
+
+Some other programs that default to EGA crash trying to start graphics; none that I've tried can start EGA at all; believe to be the same bug; will file separately if it turns out to not be
+Steps to reproduce:
+1. Boot
+2. Start QBASIC
+3. Run a program consisting of only "SCREEN 12" for VGA or "SCREEN 9" for EGA
+4. Get error message "Illegal Function Call"
diff --git a/results/classifier/108/other/629791 b/results/classifier/108/other/629791
new file mode 100644
index 00000000..af7954e0
--- /dev/null
+++ b/results/classifier/108/other/629791
@@ -0,0 +1,23 @@
+other: 0.862
+device: 0.848
+semantic: 0.806
+graphic: 0.765
+debug: 0.654
+performance: 0.632
+socket: 0.447
+PID: 0.422
+boot: 0.420
+vnc: 0.417
+network: 0.381
+permissions: 0.300
+files: 0.264
+KVM: 0.142
+
+sysret sets invalid ss
+
+I'm developing an OS. I use only sysret to enter user space. When an interrupt occurred, it would GPF on iretq'ing from it. On investigating, the cs on the stack is 0x2b (valid and correct). The ss on the stack is 0x20, which has a rpl of 0 which is incorrect. iretq checks that and gpf's. Making the irq handler manually modify it to 0x23 fixes it locally.
+
+This happens on the non-kvm'ed qemu. I haven't tried the kvm'ed one. Qemu version 0.12.5. I haven't tried with the current development version either.
+
+Minor update, I found that I made a mistake with the value in STAR. I loaded 0x18 into the top 16 bits, so the bug is not that SS is 0x20 (which I thought to be wrong but was my own mistake). Why does it set CS=0x2b from that value & run?
+