summary refs log tree commit diff stats
path: root/results/classifier/108/other/1840
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--results/classifier/108/other/184016
-rw-r--r--results/classifier/108/other/184024937
-rw-r--r--results/classifier/108/other/184025036
-rw-r--r--results/classifier/108/other/184025282
-rw-r--r--results/classifier/108/other/184064633
-rw-r--r--results/classifier/108/other/184064832
-rw-r--r--results/classifier/108/other/1840719127
-rw-r--r--results/classifier/108/other/184077791
-rw-r--r--results/classifier/108/other/184086559
-rw-r--r--results/classifier/108/other/184092284
10 files changed, 597 insertions, 0 deletions
diff --git a/results/classifier/108/other/1840 b/results/classifier/108/other/1840
new file mode 100644
index 000000000..7b9686e62
--- /dev/null
+++ b/results/classifier/108/other/1840
@@ -0,0 +1,16 @@
+device: 0.672
+performance: 0.522
+semantic: 0.499
+graphic: 0.390
+debug: 0.263
+permissions: 0.184
+boot: 0.173
+other: 0.166
+files: 0.140
+vnc: 0.129
+network: 0.075
+socket: 0.028
+PID: 0.005
+KVM: 0.003
+
+Amend RISCV machine default value
diff --git a/results/classifier/108/other/1840249 b/results/classifier/108/other/1840249
new file mode 100644
index 000000000..c46d98f39
--- /dev/null
+++ b/results/classifier/108/other/1840249
@@ -0,0 +1,37 @@
+graphic: 0.800
+other: 0.760
+semantic: 0.653
+device: 0.636
+PID: 0.605
+vnc: 0.554
+network: 0.503
+permissions: 0.494
+files: 0.469
+performance: 0.467
+socket: 0.434
+boot: 0.344
+debug: 0.311
+KVM: 0.215
+
+Cancelling 'make docker-test-build' does not cancel running containers
+
+version: v4.1.0-rc5
+
+Run 'make -k docker-test-build', wait a few, cancel with ^C:
+
+$ make -k docker-test-build 2>&1 > /dev/null
+^C
+
+$ docker ps
+CONTAINER ID        IMAGE                            COMMAND                  CREATED             STATUS
+62264a2d777a        qemu:debian-mips-cross           "/var/tmp/qemu/run t…"   10 minutes ago      Up 10 minutes
+80807c47d0df        qemu:debian-armel-cross          "/var/tmp/qemu/run t…"   10 minutes ago      Up 10 minutes
+06027b5dfd4a        qemu:debian-amd64                "/var/tmp/qemu/run t…"   10 minutes ago      Up 10 minutes
+
+The docker containers are still up building QEMU.
+
+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 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.]
+
diff --git a/results/classifier/108/other/1840250 b/results/classifier/108/other/1840250
new file mode 100644
index 000000000..bedc35855
--- /dev/null
+++ b/results/classifier/108/other/1840250
@@ -0,0 +1,36 @@
+graphic: 0.853
+other: 0.732
+device: 0.671
+semantic: 0.652
+PID: 0.606
+network: 0.556
+socket: 0.536
+performance: 0.523
+vnc: 0.511
+permissions: 0.498
+files: 0.423
+KVM: 0.395
+debug: 0.332
+boot: 0.307
+
+'make -j1 docker-test-build' uses more than one job
+
+version: v4.1.0-rc5
+
+Run 'make -j1 docker-test-build', wait a few, various containers get instantiated.
+
+$ make -j1 docker-test-build 2>&1 > /dev/null
+
+On another terminal:
+
+$ docker ps
+CONTAINER ID        IMAGE                            COMMAND                  CREATED             STATUS
+62264a2d777a        qemu:debian-mips-cross           "/var/tmp/qemu/run t…"   10 minutes ago      Up 10 minutes
+80807c47d0df        qemu:debian-armel-cross          "/var/tmp/qemu/run t…"   10 minutes ago      Up 10 minutes
+06027b5dfd4a        qemu:debian-amd64                "/var/tmp/qemu/run t…"   10 minutes ago      Up 10 minutes
+
+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 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.]
+
diff --git a/results/classifier/108/other/1840252 b/results/classifier/108/other/1840252
new file mode 100644
index 000000000..65d2f3a9f
--- /dev/null
+++ b/results/classifier/108/other/1840252
@@ -0,0 +1,82 @@
+other: 0.964
+graphic: 0.913
+permissions: 0.899
+debug: 0.883
+semantic: 0.872
+device: 0.860
+performance: 0.856
+socket: 0.855
+vnc: 0.852
+files: 0.840
+PID: 0.835
+KVM: 0.817
+network: 0.796
+boot: 0.742
+
+Infinite loop over  ERANGE from getsockopt
+
+Host system: Ubuntu 18.04.3 AMD64
+Qemu Version: qemu-arm-static --version
+qemu-arm version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.17)
+
+Emulated System: 
+Root file system taken from RaspberryPi 3 image
+ubuntu-18.04.3-preinstalled-server-armhf+raspi3.img
+from http://cdimage.ubuntu.com/releases/18.04/release/ubuntu-18.04.3-preinstalled-server-armhf+raspi3.img.xz.
+
+Then using system-nspawn with with /usr/bin/qemu-arm-static copied in.
+
+When executing commands like 
+  dpkg -i (--force-all) <...>.deb
+or
+  tar tvf ..
+or
+  tar xvf ..
+the hosting qemu-arm-static process goes into an infinite loop of getsockopt calls of the form:
+getsockopt(12, SOL_SOCKET, SO_PEERSEC, 0x7fff7cac49d8, [4]) = -1 ERANGE (Numerical result out of range)
+I assume that this is because of an infinite retry without checking the actual error code of the call.
+
+strace:
+openat(AT_FDCWD, "/lib/arm-linux-gnueabihf/librt.so.1", O_RDONLY|O_CLOEXEC) = 12
+read(12, "\177ELF\1\1\1\3\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\20\30\0\0004\0\0\0"..., 512) = 512
+lseek(12, 21236, SEEK_SET)              = 21236
+read(12, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1240) = 1240
+lseek(12, 20856, SEEK_SET)              = 20856
+read(12, "A2\0\0\0aeabi\0\1(\0\0\0\0057-A\0\6\n\7A\10\1\t\2\n\4\22"..., 51) = 51
+fstat(12, {st_mode=S_IFREG|0644, st_size=22476, ...}) = 0
+mmap(0x7f419952c000, 90112, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS|MAP_DENYWRIT
+E, -1, 0) = 0x7f419952c000
+mmap(0x7f419952c000, 90112, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 12, 0) = 0x
+7f419952c000
+mprotect(0x7f4199531000, 61440, PROT_NONE) = 0
+mmap(0x7f4199540000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 12, 0x4000)
+ = 0x7f4199540000
+close(12)                               = 0
+mprotect(0x7f4199540000, 4096, PROT_READ) = 0
+mprotect(0x7f4199578000, 8192, PROT_READ) = 0
+mmap(0x7f419957b000, 28672, PROT_NONE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS|MAP_NORESERVE, -1, 0) 
+= 0x7f419957b000
+rt_sigprocmask(SIG_SETMASK, ~[RTMIN RT_1], NULL, 8) = 0
+rt_sigprocmask(SIG_SETMASK, ~[RTMIN RT_1], NULL, 8) = 0
+rt_sigprocmask(SIG_SETMASK, [HUP USR1 USR2 PIPE ALRM CHLD TSTP URG VTALRM PROF WINCH IO], NULL, 8
+) = 0
+access("/etc/systemd/dont-synthesize-nobody", F_OK) = -1 ENOENT (No such file or directory)
+getpid()                                = 26
+socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 12
+getsockopt(12, SOL_SOCKET, SO_RCVBUF, [212992], [4]) = 0
+setsockopt(12, SOL_SOCKET, SO_RCVBUFFORCE, [8388608], 4) = -1 EPERM (Operation not permitted)
+setsockopt(12, SOL_SOCKET, SO_RCVBUF, [8388608], 4) = 0
+getsockopt(12, SOL_SOCKET, SO_SNDBUF, [212992], [4]) = 0
+setsockopt(12, SOL_SOCKET, SO_SNDBUFFORCE, [8388608], 4) = -1 EPERM (Operation not permitted)
+setsockopt(12, SOL_SOCKET, SO_SNDBUF, [8388608], 4) = 0
+connect(12, {sa_family=AF_UNIX, sun_path="/run/dbus/system_bus_socket"}, 29) = 0
+getsockopt(12, SOL_SOCKET, SO_PEERCRED, {pid=0, uid=0, gid=0}, [12]) = 0
+getsockopt(12, SOL_SOCKET, SO_PEERSEC, 0x7fff7cac49d8, [4]) = -1 ERANGE (Numerical result out of 
+range)
+
+Hi; thanks for this bug report. It looks like it's the same as LP:1823790. The underlying cause is that we don't implement the SO_PEERSEC getsockopt option properly. Unfortunately this option appears to be completely undocumented, which makes it pretty hard for us to implement :-(
+
+
+See my comment at  LP:1823790.
+
+
diff --git a/results/classifier/108/other/1840646 b/results/classifier/108/other/1840646
new file mode 100644
index 000000000..008e275d7
--- /dev/null
+++ b/results/classifier/108/other/1840646
@@ -0,0 +1,33 @@
+other: 0.822
+network: 0.767
+graphic: 0.676
+device: 0.655
+socket: 0.620
+semantic: 0.430
+performance: 0.317
+PID: 0.250
+debug: 0.249
+vnc: 0.238
+files: 0.220
+boot: 0.118
+permissions: 0.076
+KVM: 0.020
+
+qemu-4.1.0/roms/SLOF/lib/libnet/ping.c:122: logical fault
+
+qemu-4.1.0/roms/SLOF/lib/libnet/ping.c:122:16: warning: Logical conjunction always evaluates to false: alen <= 0 && alen >= sizeof(args) - 1. [incorrectLogicOperator]
+
+Source code is
+
+   if (alen <= 0 && alen >= sizeof(args) - 1) {
+
+Maybe better code:
+
+   if (alen <= 0 || alen >= sizeof(args) - 1) {
+
+This isn't QEMU code -- it's just the source for third-party ROMs that we ship with QEMU because we also ship the ROM binaries. Please report it to the upstream project.
+
+
+(Anything in a git submodule will be third-party code that's not part of QEMU.)
+
+
diff --git a/results/classifier/108/other/1840648 b/results/classifier/108/other/1840648
new file mode 100644
index 000000000..ad3b3840a
--- /dev/null
+++ b/results/classifier/108/other/1840648
@@ -0,0 +1,32 @@
+other: 0.749
+device: 0.617
+socket: 0.612
+semantic: 0.594
+graphic: 0.577
+network: 0.492
+files: 0.425
+performance: 0.303
+debug: 0.302
+vnc: 0.260
+boot: 0.255
+PID: 0.238
+permissions: 0.207
+KVM: 0.084
+
+qemu-4.1.0/roms/edk2/MdeModulePkg/Universal/Disk/UdfDxe/FileName.c:161: logical fault ?
+
+qemu-4.1.0/roms/edk2/MdeModulePkg/Universal/Disk/UdfDxe/FileName.c:161:71: warning: Logical disjunction always evaluates to true: EXPR != '\\' || EXPR != '\0'. [incorrectLogicOperator]
+
+Source code is
+
+       if ((*(FileName - 1) != L'\\') && ((*(FileName + 2) != L'\\') ||
+                                           (*(FileName + 2) != L'\0'))) {
+
+Maybe better code:
+
+       if ((*(FileName - 1) != L'\\') && ((*(FileName + 2) != L'\\') &&
+                                           (*(FileName + 2) != L'\0'))) {
+
+This isn't QEMU code -- it's just the source for third-party ROMs that we ship with QEMU because we also ship the ROM binaries. Please report it to the upstream project.
+
+
diff --git a/results/classifier/108/other/1840719 b/results/classifier/108/other/1840719
new file mode 100644
index 000000000..513d493b4
--- /dev/null
+++ b/results/classifier/108/other/1840719
@@ -0,0 +1,127 @@
+graphic: 0.892
+other: 0.891
+boot: 0.885
+KVM: 0.879
+device: 0.878
+semantic: 0.868
+debug: 0.868
+PID: 0.862
+vnc: 0.862
+socket: 0.854
+performance: 0.840
+network: 0.826
+permissions: 0.814
+files: 0.768
+
+win98se floppy fails to boot with isapc machine
+
+QEMU emulator version 4.1.50 (commit 50d69ee0d)
+
+floppy image from:
+https://winworldpc.com/download/417d71c2-ae18-c39a-11c3-a4e284a2c3a5
+
+$ qemu-system-i386 -M isapc -fda Windows\ 98\ Second\ Edition\ Boot.img
+SeaBIOS (version rel-1.12.1-0...)
+Booting from Floppy...
+Boot failed: could not read the boot disk
+
+Bisected following note from http://gunkies.org/wiki/I386-softmmu:
+
+the isapc configuration no longer works... So legacy systems must resort to Qemu 0.9.0 or Qemu 0.10.0 
+
+I get:
+
+fd646122418ecefcde228d43821d07da79dd99bb is the first bad commit
+commit fd646122418ecefcde228d43821d07da79dd99bb
+Author: Anthony Liguori <email address hidden>
+Date:   Fri Oct 30 09:06:09 2009 -0500
+
+    Switch pc bios from pc-bios to seabios
+    
+    SeaBIOS is a port of pc-bios to GCC.  Besides using a more modern tool chain,
+    SeaBIOS introduces a number of new features including PMM support, better
+    BEV and BCV support, and better PnP support.
+
+Apparently the bisection result from comment #1 comes from a different issue, the VGA display stays blank, can not test the floppy drive.
+
+Bisecting using the pcbios.bin from fd646122418~, the VGA display stops working at:
+
+345c22aa80d1f6ddfe7898f721fd1be3bccb08f1 is the first bad commit
+commit 345c22aa80d1f6ddfe7898f721fd1be3bccb08f1
+Author: Gerd Hoffmann <email address hidden>
+Date:   Fri Dec 18 12:01:12 2009 +0100
+
+    roms: remove option rom packing logic
+    
+    Now that we load the option roms via fw_cfg, we can stop copying
+    them to the 0xc000 -> 0xe000.  The patch does just that.
+    
+    Also the rom loader gets simplified as all remaining users of the
+    rom loader load the bits at a fixed address so the packing and
+    aligning logic can go away.
+
+So finally, the commit that introduced this regression is not directly related to QEMU:
+
+0b8f74488e50f98b04e63157f85fde8a13f8d6aa is the first bad commit
+commit 0b8f74488e50f98b04e63157f85fde8a13f8d6aa
+Author: Gerd Hoffmann <email address hidden>
+Date:   Tue Nov 6 12:23:53 2018 +0100
+
+    update seabios to master snapshot
+    
+    seabios 1.12 release is planned for november.
+    
+    update seabios to a master branch snapshot so it gets more testing
+    and to make the delta smaller when updating to -final during freeze.
+
+And the (SeaBIOS) winner is...
+
+4a6dbcea3e412fe12effa2f812f50dd7eae90955 is the first bad commit
+commit 4a6dbcea3e412fe12effa2f812f50dd7eae90955
+Author: Nikolay Nikolov <email address hidden>
+Date:   Sun Feb 4 17:27:01 2018 +0200
+
+    floppy: Use timer_check() in floppy_wait_irq()
+    
+    Use timer_check() instead of using floppy_motor_counter in BDA for the
+    timeout check in floppy_wait_irq().
+    
+    The problem with using floppy_motor_counter was that, after it reaches
+    0, it immediately stops the floppy motors, which is not what is
+    supposed to happen on real hardware. Instead, after a timeout (like in
+    the end of every floppy operation, regardless of the result - success,
+    timeout or error), the floppy motors must be kept spinning for
+    additional 2 seconds (the FLOPPY_MOTOR_TICKS). So, now the
+    floppy_motor_counter is initialized to 255 (the max value) in the
+    beginning of the floppy operation. For IRQ timeouts, a different
+    timeout is used, specified by the new FLOPPY_IRQ_TIMEOUT constant
+    (currently set to 5 seconds - a fairly conservative value, but should
+    work reliably on most floppies).
+    
+    After the floppy operation, floppy_drive_pio() resets the
+    floppy_motor_counter to 2 seconds (FLOPPY_MOTOR_TICKS).
+    
+    This is also consistent with what other PC BIOSes do.
+
+I'm not sure if it's related to SeaBIOS because SeaBIOS configuration is stored in QEMU.
+So I think CONFIG_TSC_TIMER should be disabled in seabios-128k.config and the 128k variant of SeaBIOS should be used for isapc.
+
+Please see the thread for details: 
+
+  https://lists.gnu.org/archive/html/qemu-devel/2019-08/msg03924.html
+
+If I disable TSC in SeaBIOS (i.e. CONFIG_TSC_TIMER=n) the floppy can't be booted with or without TSC-capable CPU. So, it can't be fixed on QEMU side.
+
+Fun thing, that if I set CONFIG_TSC_TIMER=n and start it with isa-debugcon, it works:
+$QEMU -cpu 486 -M isapc,accel=hvf -fda ~/win98-fe-boot-floppy.img -chardev file,id=debugcon,path=seabios.log -device isa-debugcon,iobase=0x402,chardev=debugcon
+
+This one doesn't work:
+$QEMU -cpu 486 -M isapc,accel=hvf -fda ~/win98-fe-boot-floppy.img
+
+The ticket should be closed as soon as SeaBIOS gets updated in QEMU. A patch has been posted to SeaBIOS mailing list:
+https://<email address hidden>/thread/XPKQNLVWZX55TSLSXZVY5S5DMFYS4CNO/
+
+The commit fixes the issue in master branch: https://git.qemu.org/?p=qemu.git;a=commit;h=de15df5ead400b7c3d0cf21c8164a7686dc81933
+
+The fix is going to be released in 5.1
+
diff --git a/results/classifier/108/other/1840777 b/results/classifier/108/other/1840777
new file mode 100644
index 000000000..1606b2041
--- /dev/null
+++ b/results/classifier/108/other/1840777
@@ -0,0 +1,91 @@
+graphic: 0.909
+device: 0.901
+permissions: 0.897
+KVM: 0.892
+performance: 0.892
+other: 0.880
+boot: 0.875
+vnc: 0.860
+debug: 0.858
+PID: 0.856
+semantic: 0.846
+socket: 0.780
+files: 0.773
+network: 0.773
+
+raspi3 machine can not shutdown
+
+tag v4.1.0
+
+Running "shutdown" within a raspi3 image leads to kernel panic:
+
+         Starting Power-Off...
+[   39.719617] systemd-shutdow: 39 output lines suppressed due to ratelimiting
+[   39.922997] systemd-shutdown[1]: Syncing filesystems and block devices.
+[   39.962415] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
+[   40.006842] systemd-journald[186]: Received SIGTERM from PID 1 (systemd-shutdow).
+[   40.060745] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
+[   40.098318] systemd-shutdown[1]: Unmounting file systems.
+[   40.108351] systemd-shutdown[455]: Remounting '/' read-only in with options 'data=ordered'.
+[   40.128919] EXT4-fs (mmcblk0p2): re-mounted. Opts: data=ordered
+[   40.152844] systemd-shutdown[1]: All filesystems unmounted.
+[   40.153239] systemd-shutdown[1]: Deactivating swaps.
+[   40.154701] systemd-shutdown[1]: All swaps deactivated.
+[   40.155062] systemd-shutdown[1]: Detaching loop devices.
+[   40.159792] systemd-shutdown[1]: All loop devices detached.
+[   40.201746] kvm: exiting hardware virtualization
+[   40.207628] reboot: Power down
+bcm2835-pm: unimplemented device read (size 4, offset 0x20)
+bcm2835-pm: unimplemented device write (size 4, value 0x5a000555, offset 0x20)
+bcm2835-pm: unimplemented device write (size 4, value 0x5a00000a, offset 0x24)
+bcm2835-pm: unimplemented device read (size 4, offset 0x1c)
+bcm2835-pm: unimplemented device write (size 4, value 0x5a000020, offset 0x1c)
+[   40.229604] systemd-shutdow: 4 output lines suppressed due to ratelimiting
+[   40.230849] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000
+[   40.230849] 
+[   40.231781] CPU: 0 PID: 1 Comm: systemd-shutdow Not tainted 4.14.0-3-arm64 #1 Debian 4.14.12-2
+[   40.232470] Hardware name: Raspberry Pi 3 Model B (DT)
+[   40.233206] Call trace:
+[   40.234096] [<ffff00000808a708>] dump_backtrace+0x0/0x280
+[   40.234519] [<ffff00000808a9ac>] show_stack+0x24/0x30
+[   40.234972] [<ffff00000885bb7c>] dump_stack+0x9c/0xc0
+[   40.235378] [<ffff0000080d1bd4>] panic+0x138/0x2b4
+[   40.235805] [<ffff0000080d72d4>] do_exit+0xa04/0xa08
+[   40.236260] [<ffff0000080fa9d8>] SyS_reboot+0x178/0x260
+[   40.236915] Exception stack(0xffff00000802bec0 to 0xffff00000802c000)
+[   40.237487] bec0: fffffffffee1dead 0000000028121969 000000004321fedc adc576109fd73c00
+[   40.237949] bee0: 0000000000000028 8080800000000000 0000ffffad2392f8 7f7f7f7f7f7f7f7f
+[   40.238376] bf00: 000000000000008e 0000000000000000 0000000000000069 0000000000000000
+[   40.238744] bf20: 0000000000000000 0000000000000020 0000000000000000 0000000000000000
+[   40.239101] bf40: 0000aaaabeb9bf10 0000ffffad3030a8 0000000000000001 0000000000000000
+[   40.239462] bf60: 0000000000000000 0000aaaaeb6e0040 0000aaaabeb8a008 0000fffff7ce8d30
+[   40.239802] bf80: 0000001b00000004 0000aaaabeb8a000 0000fffff7ce8fa8 0000000000000000
+[   40.240134] bfa0: 0000aaaabeb9b000 0000fffff7ce8ac0 0000aaaabeb8741c 0000fffff7ce8aa0
+[   40.240468] bfc0: 0000ffffad3030c4 0000000000000000 fffffffffee1dead 000000000000008e
+[   40.240809] bfe0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
+[   40.241194] [<ffff0000080837b0>] el0_svc_naked+0x24/0x28
+[   40.241930] Kernel Offset: disabled
+[   40.242197] CPU features: 0x002004
+[   40.242450] Memory Limit: none
+[   40.243063] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000
+[   40.243063] 
+qemu-system-aarch64: terminating on signal 2
+
+I'm guessing from:
+
+  bcm2835-pm: unimplemented device read (size 4, offset 0x20)
+  bcm2835-pm: unimplemented device write (size 4, value 0x5a000555, offset 0x20)
+  bcm2835-pm: unimplemented device write (size 4, value 0x5a00000a, offset 0x24)
+  bcm2835-pm: unimplemented device read (size 4, offset 0x1c)
+  bcm2835-pm: unimplemented device write (size 4, value 0x5a000020, offset 0x1c)
+
+That we don't implement the power control parts of the SoC and therefor the kernel got to a bit it wasn't expecting.
+
+
+This is an automated cleanup. This bug report has been moved
+to QEMU's new bug tracker on gitlab.com and thus gets marked
+as 'expired' now. Please continue with the discussion here:
+
+ https://gitlab.com/qemu-project/qemu/-/issues/64
+
+
diff --git a/results/classifier/108/other/1840865 b/results/classifier/108/other/1840865
new file mode 100644
index 000000000..428e94bd3
--- /dev/null
+++ b/results/classifier/108/other/1840865
@@ -0,0 +1,59 @@
+performance: 0.825
+device: 0.805
+PID: 0.795
+graphic: 0.769
+files: 0.669
+network: 0.586
+debug: 0.584
+vnc: 0.575
+permissions: 0.553
+socket: 0.509
+semantic: 0.476
+boot: 0.383
+other: 0.268
+KVM: 0.181
+
+qemu crashes when doing iotest on  virtio-9p filesystem 
+
+Qemu crashes when doing avocado-vt test on virtio-9p filesystem.
+This bug can be reproduced running https://github.com/autotest/tp-qemu/blob/master/qemu/tests/9p.py.
+The crash stack goes like:
+
+Program terminated with signal SIGSEGV, Segmentation fault.
+#0  v9fs_mark_fids_unreclaim (pdu=pdu@entry=0xaaab00046868, path=path@entry=0xffff851e2fa8)
+    at hw/9pfs/9p.c:505
+#1  0x0000aaaae3585acc in v9fs_unlinkat (opaque=0xaaab00046868) at hw/9pfs/9p.c:2590
+#2  0x0000aaaae3811c10 in coroutine_trampoline (i0=<optimized out>, i1=<optimized out>)
+    at util/coroutine-ucontext.c:116
+#3  0x0000ffffa13ddb20 in ?? () from /lib64/libc.so.6
+Backtrace stopped: not enough registers or memory available to unwind further
+
+A segment fault is triggered at hw/9pfs/9p.c line 505
+
+    for (fidp = s->fid_list; fidp; fidp = fidp->next) {
+        if (fidp->path.size != path->size) {     # fidp is invalid 
+            continue;
+        }
+
+(gdb) p path
+$10 = (V9fsPath *) 0xffff851e2fa8
+(gdb) p *path
+$11 = {size = 21, data = 0xaaaafed6f420 "./9p_test/p2a1/d0/f1"}
+(gdb) p *fidp
+Cannot access memory at address 0x101010101010101
+(gdb) p *pdu
+$12 = {size = 19, tag = 54, id = 76 'L', cancelled = 0 '\000', complete = {entries = {
+      sqh_first = 0x0, sqh_last = 0xaaab00046870}}, s = 0xaaab000454b8, next = {
+    le_next = 0xaaab000467c0, le_prev = 0xaaab00046f88}, idx = 88}
+(gdb) 
+
+Address Sanitizer shows error and saying that there is a heap-use-after-free on *fidp*.
+
+
+This is an automated cleanup. This bug report has been moved to QEMU's
+new bug tracker on gitlab.com and thus gets marked as 'expired' now.
+Please continue with the discussion here:
+
+ https://gitlab.com/qemu-project/qemu/-/issues/181
+
+
diff --git a/results/classifier/108/other/1840922 b/results/classifier/108/other/1840922
new file mode 100644
index 000000000..22609449a
--- /dev/null
+++ b/results/classifier/108/other/1840922
@@ -0,0 +1,84 @@
+performance: 0.692
+other: 0.652
+semantic: 0.642
+permissions: 0.558
+vnc: 0.521
+graphic: 0.492
+device: 0.472
+network: 0.449
+socket: 0.377
+boot: 0.352
+PID: 0.331
+debug: 0.242
+KVM: 0.161
+files: 0.159
+
+qemu-arm for cortex-m33 aborts with unhandled CPU exception 0x8
+
+Hi,
+
+While experimenting with running the GCC testsuite with cortex-m33 as target (to exercise v8-m code), I came across this failure:
+qemu: unhandled CPU exception 0x8 - aborting
+R00=fffeaf58 R01=fffeaf58 R02=00000000 R03=fffeaf5d
+R04=fffeaf5c R05=fffeaf9c R06=00000000 R07=fffeaf80
+R08=00000000 R09=00000000 R10=00019dbc R11=00000000
+R12=000000f0 R13=fffeaf58 R14=000081f3 R15=fffeaf5c
+XPSR=61000000 -ZC- T NS priv-thread
+qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x6033c908
+
+I'm using arm-eabi-gcc, so it targets bare-metal, not linux.
+
+The testcase is GCC's gcc/testsuite/gcc.c-torture/execute/20000822-1.c; it works when compiled at -O2, but crashes when compiled at -Os. The test uses nested functions, so it creates a trampoline on the stack, whose address may be a problem. But since the stack address seems to be in the same range in the O2 and Os cases, it's not that clear.
+
+I'm attaching the C source, asm, binary executables and qemu traces with in_asm,cpu.
+
+I execute the binaries with:
+qemu-arm --cpu cortex-m33  ./20000822-1.exe.Os
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+This happens because we're applying a loose test for the v8m magic
+exception return address.
+
+There are two possible fixes for this, and perhaps we should
+apply both of them:
+
+(1) Unset ARM_FEATURE_M_SECURITY for arm-linux-user.
+    This would disable the FNC_RETURN_MIN_MAGIC test,
+    which, unlike EXC_RETURN_MIN_MAGIC, is not protected
+    by a condition that linux-user cannot satisfy (Handler mode).
+
+(2) Limit the address space to 0x7ffffff, the normal end of
+    write-back cached ram.  Since M-profile doesn't have an MMU,
+    this would make linux-user addresses more like what we'd see
+    running the same test under system mode.
+
+The test for v8m magic return addresses is not too loose -- see the v8M pseudocode IsReturn(). Architecturally the whole range of these values is special, even though in fact the exception return address encoding currently doesn't use all the bits that are reserved in this manner.
+
+I would prefer not to unset ARM_FEATURE_M_SECURITY if we can avoid it.
+
+We should definitely not allow guest code to be loaded at weird addresses in linux-user mode, I agree.
+
+
+Just posted 
+https://<email address hidden>/
+
+which is basically RTH's hack from #8 with a big pile of commentary and commit message...
+
+Thanks Peter and Richard for the quick patch. It works for me.
+
+Fixed in master as commit 5e5584c89f36b, will be in the 4.2 release.
+
+