add deepseek and gemma results

author: Christian Krinitsin <mail@krinitsin.com> 2025-07-03 07:27:52 +0000
committer: Christian Krinitsin <mail@krinitsin.com> 2025-07-03 07:27:52 +0000
commit: d0c85e36e4de67af628d54e9ab577cc3fad7796a (patch)
tree: f8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/gemma3:12b/kernel
parent: 7f4364274750eb8cb39a3e7493132fca1c01232e (diff)
download: emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz
emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip
455 files changed, 18047 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/kernel/1007 b/results/classifier/gemma3:12b/kernel/1007
new file mode 100644
index 00000000..83851d53
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1007
@@ -0,0 +1,2 @@
+
+qemu-user: add execveat syscall support
diff --git a/results/classifier/gemma3:12b/kernel/1008136 b/results/classifier/gemma3:12b/kernel/1008136
new file mode 100644
index 00000000..7da61e36
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1008136
@@ -0,0 +1,25 @@
+
+Cannot compile 1.1.0
+
+Howdy,
+
+Testing QEMU 1.1.0 but doesn't compile:
+
+
+  CC    fsdev/virtfs-proxy-helper.o
+In file included from /usr/include/i386-linux-gnu/bits/sigcontext.h:28:0,
+                 from /usr/include/signal.h:339,
+                 from ./qemu-common.h:38,
+                 from fsdev/virtfs-proxy-helper.c:23:
+/usr/include/i386-linux-gnu/asm/sigcontext.h:28:2: error: unknown type name '__u64'
+/usr/include/i386-linux-gnu/asm/sigcontext.h:191:2: error: unknown type name '__u64'
+/usr/include/i386-linux-gnu/asm/sigcontext.h:192:2: error: unknown type name '__u64'
+/usr/include/i386-linux-gnu/asm/sigcontext.h:193:2: error: unknown type name '__u64'
+make: *** [fsdev/virtfs-proxy-helper.o] Error 1
+
+
+Ideas?
+GCC 4.7, kernel 3.2x
+
+Thanks in advanced,
+Jorge,
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1012023 b/results/classifier/gemma3:12b/kernel/1012023
new file mode 100644
index 00000000..a1fa043e
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1012023
@@ -0,0 +1,6 @@
+
+Windows 7 bluescreen STOP: 00000005D
+
+Hello, with installed windows, or with install cd I have a blue screen (crash) after the first windows logo, see the screenshot.
+
+Thanks to fix it.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1014681 b/results/classifier/gemma3:12b/kernel/1014681
new file mode 100644
index 00000000..7ac3964f
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1014681
@@ -0,0 +1,35 @@
+
+BSOD with newer host kernels (x64) and W2k8S guest (x64)
+
+Hallo, I attempted to move virtual machines from one host to another but got stuck with Windows-BSODs on the target host. The host-side console message is "virtio_ioport_write: unexpected address 0x13 value 0x1". Eventually there are overlaps to bug #990364, but I'm not sure.
+
+Host machine: 2x Opteron 4238 a 6 cores, 32GB RAM, Linux x86_64
+Guest machine(s): Windows 2008 Server R2 x64
+
+I tried different combinations of component versions, but only kernel 2.6.34 could run the guests (but has other difficulties):
+
+host kernel	Qemu-KVM	paravirtualization	guest paravirt driver
+=============================================
+2.6.34		1.0.1		virtio				0.1.15		ok
+										0.1.22		ok
+										0.1.prewhql	ok
+			git 20120615	virtio				0.1.15		ok
+										0.1.22		ok
+										0.1.prewhql	ok
+=============================================
+2.6.39		1.0.1		virtio				0.1.15		BSOD
+			git 20120615	virtio				0.1.15		BSOD
+3.0.3		1.0.1		virtio				0.1.15		BSOD
+			git 20120615	virtio				0.1.15		BSOD
+3.3.8		1.0.1		virtio				0.1.15		BSOD
+			git 20120615	virtio				0.1.15		BSOD
+						virtio-pci			0.1.15		BSOD
+3.4.2		1.0.1		virtio				0.1.15		BSOD
+										0.1.prewhql	BSOD
+						virtio-pci			0.1.15		BSOD
+			git 20120615	virtio				0.1.15		BSOD
+										0.1.prewhql	BSOD
+						virtio-pci			0.1.15		BSOD
+=============================================
+
+Run arguments are attached. Minidump follows immediately.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1033494 b/results/classifier/gemma3:12b/kernel/1033494
new file mode 100644
index 00000000..d1e0ca51
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1033494
@@ -0,0 +1,11 @@
+
+qemu-system-x86_64 segfaults with kernel 3.5.0
+
+qemu-kvm 1.1.1 stable is running fine for me with RHEL 6 2.6.32 based kernel.
+
+But with 3.5.0 kernel qemu-system-x86_64 segfaults while i'm trying to install ubuntu 12.04 server reproducable.
+
+You find three backtraces here:
+http://pastebin.com/raw.php?i=xCy2pEcP
+
+Stefan
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1037675 b/results/classifier/gemma3:12b/kernel/1037675
new file mode 100644
index 00000000..01de15e8
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1037675
@@ -0,0 +1,10 @@
+
+Guest Kernel Panic if using "-cpu host" in qemu-kvm 1.1.1
+
+After Upgrading to qemu-kvm-1.1.1-r1 from version 1.0.1-r1 my virtual machines (running gentoo linux) panic at intel_pmu_init. (detailed information including stacktrace are in the uploaded screenshot). When i remove the "-cpu host" option, the system starts normally. 
+
+the command line from whicht the system is bootet: 
+
+qemu-kvm -vnc :7 -usbdevice tablet -daemonize -m 256 -drive file=/data/virtual_machines/wgs-l08.img,if=virtio  -boot c -k de -net nic,model=virtio,macaddr=12:12:00:12:34:63,vlan=0 -net tap,ifname=qtap6,script=no,downscript=no,vlan=0 -smp 2 -enable-kvm -cpu host -monitor unix:/var/run/qemu-kvm/wgs-l08.monitor,server,nowait
+
+also reported on gentoo bug tracker (with some more details of the host): https://bugs.gentoo.org/show_bug.cgi?id=431640
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1041 b/results/classifier/gemma3:12b/kernel/1041
new file mode 100644
index 00000000..4043b247
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1041
@@ -0,0 +1,32 @@
+
+x86_64 Auxillary vector reports platform as i686 which doesn't match the linux kernel
+Description of problem:
+Based on the kernel source in the auxiliary vector AT_PLATFORM should be `x86_64` (confirmed by running outside qemu). However qemu sets it to `i686`.
+
+This was originally reported with docker-for-mac, but was reduced on `x86_64` which is why it is pointless
+Steps to reproduce:
+1. Compile the following for x86_64 (statically if you don't want have an x86_64 dynamic linker) (code originally from https://stackoverflow.com/questions/26520163/accessing-auxiliary-vectors-c)
+
+```
+#include <stdio.h>
+#include <elf.h>
+
+int main(int argc, char** argv, char* envp[]) {
+  Elf64_auxv_t *auxv;
+  while(*envp++ != NULL);
+
+  /*from stack diagram above: *envp = NULL marks end of envp*/
+  int i = 0 ;
+  for (auxv = (Elf64_auxv_t *)envp; auxv->a_type != AT_NULL; auxv++)
+    /* auxv->a_type = AT_NULL marks the end of auxv */
+  {
+    if( auxv->a_type == AT_PLATFORM)
+      printf("AT_PLATFORM is: %s\n", ((char*)auxv->a_un.a_val));
+  }
+}
+```
+2. Run with `qemu-x86_64-static`
+3. See `AT_PLATFORM is: i686`
+4. Compare to "real" x86_64 bit system which gives `AT_PLATFORM is: x86_64`
+Additional information:
+I think that adding `#define ELF_PLATFORM "x86_64"` [here](https://gitlab.com/qemu-project/qemu/-/blob/master/linux-user/elfload.c#L134) should work (but I don't fully understand the code). Otherwise we just end up getting the 32-bit case.
diff --git a/results/classifier/gemma3:12b/kernel/1042388 b/results/classifier/gemma3:12b/kernel/1042388
new file mode 100644
index 00000000..6d8c191e
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1042388
@@ -0,0 +1,15 @@
+
+qemu: Unsupported syscall: 257 (timer_create)
+
+Running qemu-arm-static for git HEAD. When I try to install ghc from debian into my arm chroot I get:
+
+Setting up ghc (7.4.1-4) ...
+qemu: Unsupported syscall: 257
+ghc: timer_create: Function not implemented
+qemu: Unsupported syscall: 257
+ghc-pkg: timer_create: Function not implemented
+dpkg: error processing ghc (--configure):
+ subprocess installed post-installation script returned error exit status 1
+Errors were encountered while processing:
+ ghc
+E: Sub-process /usr/bin/dpkg returned an error code (1)
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1051 b/results/classifier/gemma3:12b/kernel/1051
new file mode 100644
index 00000000..25b3c33c
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1051
@@ -0,0 +1,2 @@
+
+or1k tcg SIGILL
diff --git a/results/classifier/gemma3:12b/kernel/1052857 b/results/classifier/gemma3:12b/kernel/1052857
new file mode 100644
index 00000000..4c3575a8
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1052857
@@ -0,0 +1,16 @@
+
+qemu-user compiled static for ppc fails on 64bit hosts
+
+On debian I used debootstrap to set up a powerpc chroot. If I then copy in a statically linked qemu-user ppc binary it will work for some commands in the chroot and fail for others. Steps to reproduce:
+
+host$ mkdir powerpc
+host$ sudo debootstrap --arch=powerpc --foreign wheezy powerpc http://ftp.debian.org/debian
+host$ sudo cp /usr/bin/qemu-ppc-static powerpc/usr/bin/
+host$  LANG=C sudo chroot powerpc /usr/bin/qemu-ppc-static /bin/bash
+I have no name!@guest:/# pwd
+/
+I have no name!@guest:/# cd home/
+I have no name!@guest:/home# ls
+qemu-ppc-static: /tmp/buildd/qemu-1.1.2+dfsg/linux-user/signal.c:4341: setup_frame: Assertion `({ unsigned long __guest = (unsigned long)(ka->_sa_handler) - guest_base; (__guest < (1ul << 32)) && (!reserved_va || (__guest < reserved_va)); })' failed.
+
+I have also built this from the git HEAD sources (hash 6b80f7db8a7f84d21e46d01e30c8497733bb23a0) and I get the same result.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1062 b/results/classifier/gemma3:12b/kernel/1062
new file mode 100644
index 00000000..72f023ab
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1062
@@ -0,0 +1,17 @@
+
+AArch64: SCR_EL3.RW behaves incorrectly for CPUs with no AArch32
+Description of problem:
+In the ARM DDI 0487G.a, D13-3572, the SCR_EL3.RW bit is defined as RAO/WI if both EL2 and EL1 don't support Aarch32. However, the function `scr_write` in `target/arm/helper.c` does not reflect this behavior, even though it checks for Aarch32 EL1 support.
+
+This would break this EL3 code, which should run on cpu reset to attempt to return to EL1:
+```asm
+mov x1, #((1<<0)|(1<<2)|(1<<6)|(1<<7)|(1<<8)|(1<<9)) ; EL1h, DAIF masked
+mov SPSR_EL3, x1
+adr x1, 1f
+msr ELR_EL3, x1
+eret
+1:
+; something something
+```
+Additional information:
+
diff --git a/results/classifier/gemma3:12b/kernel/1066909 b/results/classifier/gemma3:12b/kernel/1066909
new file mode 100644
index 00000000..f41cd76e
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1066909
@@ -0,0 +1,8 @@
+
+App-level clone emulation for microblaze is broken
+
+When CLONE_THREAD is used, the new process starts with the program counter pointing to the system call instruction, rather than the instruction immediately following it. This causes an infinite cascade (linear growth, not exponential) of thread creation, which quickly crashes when the threads start running and they're all using the same stack.
+
+I'm using qemu 1.1.2 packaged with Debian, but I'm not aware of any fixes since then that would address the problem.
+
+I can provide a test program if needed; a short C program using syscall() directly or an even-shorter asm program can demonstrate the issue without need for debugging around pthread library routines.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1068 b/results/classifier/gemma3:12b/kernel/1068
new file mode 100644
index 00000000..7d82c1e2
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1068
@@ -0,0 +1,12 @@
+
+VMs stuck loading Kernel "Freeing unused Kernel image (initmem) memory" with host running Vanilla Kernel >= 5.18.0
+Description of problem:
+The VMs are stuck after "Freeing unused Kernel image (initmem) memory"  
+See attached screen recording.  
+Rebooting the host with Kernel 5.17.13 solves the problem.
+Steps to reproduce:
+1. Boot host with Kernel >= 5.18.0
+2. Start VM
+Additional information:
+[bug.log](/uploads/faa14ac0bf84a21beb2ffeeb650df4b9/bug.log)
+[qemu-libvirt-host-kernel-5.18.2.mkv](/uploads/87a064f171833e9fb3d46fd3ece32152/qemu-libvirt-host-kernel-5.18.2.mkv)
diff --git a/results/classifier/gemma3:12b/kernel/1068900 b/results/classifier/gemma3:12b/kernel/1068900
new file mode 100644
index 00000000..9b2085f2
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1068900
@@ -0,0 +1,6 @@
+
+Thread cancellation broken in app-level emulation
+
+Thread cancellation (and certain other implementation-internal things such as set*id() and timers) are implemented in userspace on Linux by stealing a couple of the realtime signals for internal use by the implementation, leaving them unavailable to applications. Unfortunately, this bites qemu application-level emulation when the application being run uses thread cancellation or other features that need such signals. The signal handler is unable to be set (because sigaction on the host rejects the signal numbers) and attempts to send the signals result in it being received not by the emulated application code, but by the libc/libpthread code on which qemu is running; this in turn seems to cause qemu to crash.
+
+The best solution I can think of is for qemu to steal one of the realtime signals for its own use, and multiplex signal numbers outside the range SIGRTMIN..SIGRTMAX, as well as the stolen signal itself, on top of this stolen signal. This would both allow cancellation to work, and would allow applications the full range of realtime signals when the guest has more signals than the host (e.g. MIPS running on x86 host).
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1069 b/results/classifier/gemma3:12b/kernel/1069
new file mode 100644
index 00000000..0f4515b3
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1069
@@ -0,0 +1,14 @@
+
+Qemu triggers the split lock detection of the Linux kernel
+Description of problem:
+Windows displays a "blue screen of death" and the Linux kernel logs this error message:
+
+```
+[  180.886150] x86/split lock detection: #AC: qemu-system-x86/10167 took a split_lock trap at address: 0x3ff2624d
+[  180.946151] x86/split lock detection: #AC: qemu-system-x86/10168 took a split_lock trap at address: 0x3ff2624d
+```
+Steps to reproduce:
+1. Start the guest OS
+2. Do some stuff in the Windows guest (for instance OS updates)
+Additional information:
+Is this a bug in Windows or in Qemu ?
diff --git a/results/classifier/gemma3:12b/kernel/1078 b/results/classifier/gemma3:12b/kernel/1078
new file mode 100644
index 00000000..81f3a495
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1078
@@ -0,0 +1,45 @@
+
+qemu-system-arm: unable to use LPAE
+Description of problem:
+Failed to run qemu: qemu-system-arm: Addressing limited to 32 bits,
+but memory exceeds it by 1073741824 bytes
+Steps to reproduce:
+1. ./configure --target-list=arm-softmmu
+2. make
+3.
+./qemu-system-arm \
+-machine virt,highmem=on \
+-cpu cortex-a15 -smp 4 \
+-m 4096 \
+-kernel ./zImage \
+-drive id=disk0,file=./rootfs.ext4,if=none,format=raw \
+-object rng-random,filename=/dev/urandom,id=rng0 \
+-device virtio-rng-pci,rng=rng0 \
+-device virtio-blk-device,drive=disk0 \
+-device virtio-gpu-pci \
+-serial mon:stdio -serial null \
+-nographic \
+-append 'root=/dev/vda rw mem=4096M ip=dhcp console=ttyAMA0 console=hvc0'
+Additional information:
+We set physical address bits to 40 if ARM_FEATURE_LPAE is enabled. But ARM_FEATURE_V7VE also implies ARM_FEATURE_LPAE as set later in arm_cpu_realizefn.
+
+We should add condition for ARM_FEATURE_V7VE, otherwise we would not be able to use highmem larger than 3GB even though we have enabled highmem, since we would fail and return right from machvirt_init. 
+
+I have already made a patch to fix this issue.
+https://gitlab.com/realhezhe/qemu/-/commit/4dad8167c1c1a7695af88d8929e8d7f6399177de
+`hw/arm/virt.c`
+```c
+        if (object_property_get_bool(cpuobj, "aarch64", NULL)) {
+            pa_bits = arm_pamax(armcpu);
+        } else if (arm_feature(&armcpu->env, ARM_FEATURE_LPAE)) {
+        } else if (arm_feature(&armcpu->env, ARM_FEATURE_LPAE)
+                || arm_feature(&armcpu->env, ARM_FEATURE_V7VE)) {
+            /* v7 with LPAE */
+            pa_bits = 40;
+        } else {
+```
+
+After applying the patch, I can make sure that the pa_bits has already been set to 40, but qemu hangs later. By bisecting I found if the following commit is reverted qemu can boot up successfully..
+39a1fd2528 ("target/arm: Fix handling of LPAE block descriptors")
+
+It can't be quickly determined what's going on here at my side. Maybe the author can help give some hints. Thanks.
diff --git a/results/classifier/gemma3:12b/kernel/1083 b/results/classifier/gemma3:12b/kernel/1083
new file mode 100644
index 00000000..87da5aee
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1083
@@ -0,0 +1,2 @@
+
+Qemu on Windows - Emulate 64Bit CPU
diff --git a/results/classifier/gemma3:12b/kernel/1088617 b/results/classifier/gemma3:12b/kernel/1088617
new file mode 100644
index 00000000..6100a9f2
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1088617
@@ -0,0 +1,15 @@
+
+qemu-system-mipsel save/restore broken
+
+Save and restore on mipsel seems to be broken (tested with commit 1c97e303d4ea80a2691334b0febe87a50660f99d). To reproduce:
+
+1. Download debian_squeeze_mipsel_standard.qcow2 and vmlinux-2.6.32-5-4kc-malta from from http://people.debian.org/~aurel32/qemu/mipsel/
+
+2. Boot the system. I had to ^D past a Bus error in fsck, which may be another bug (haven't investigated). The command line used was:
+qemu-system-mipsel -M malta -kernel vmlinux-2.6.32-5-4kc-malta -hda debian_squeeze_mipsel_standard.qcow2 -append "root=/dev/sda1 console=tty0" -k en-us -vnc :0
+
+3. Once the system is booted, go to the monitor and do "savevm booted". Then quit.
+
+4. Re-run qemu-system-mipsel again with "-loadvm booted". The guest system comes back but is hung (the monitor remains responsive, however).
+
+I also captured a debug log, which is attached. The immediate cause of the freeze seems to be that it's stuck in a loop repeatedly handling the same page fault over and over.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1091115 b/results/classifier/gemma3:12b/kernel/1091115
new file mode 100644
index 00000000..3742fdce
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1091115
@@ -0,0 +1,16 @@
+
+windowsXP install in qemu-system-i386 1.3.0 ends with a BSOD 0x7E in acpi.sys
+
+These are the commands:
+$git checkout v1.3.0
+$./configure --prefix=/home/user/tmp --target-list=i386-softmmu --enable-sdl --disable-curses --disable-vnc --enable-kvm --disable-docs
+$make
+$make install
+In /home/user/tmp directory:
+$./bin/qemu-img create imgs/winxp.img 4G
+$./bin/qemu-system-i386 imgs/winxp.img -cdrom ~/Downloads/zh-hans_windows_xp_professional_with_service_pack_3_x86_cd_x14-80404.iso
+
+then it show a bluescreen after a few seconds.
+See the attachment for more information, please.
+
+It works well when checking out v1.2.0.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1093 b/results/classifier/gemma3:12b/kernel/1093
new file mode 100644
index 00000000..723d5bc3
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1093
@@ -0,0 +1,34 @@
+
+RISC-V: signal frame is misaligned in signal handlers
+Description of problem:
+`qemu-user` misaligns the signal frame (to 4 bytes rather than 16 bytes) on RISC-V 64, e.g causing pointer misalignment diagnostics to be triggered by UBSan.
+Steps to reproduce:
+1. Create a C file with the following contents:
+```c
+#include <signal.h>
+#include <stdio.h>
+
+void handler(int sig, siginfo_t *info, void *context) {
+	printf("signal occurred, info: %p, context: %p\n", info, context);
+}
+
+int main() {
+	struct sigaction act;
+	act.sa_flags = SA_SIGINFO;
+	act.sa_sigaction = handler;
+	sigaction(SIGINT, &act, NULL);
+
+	// Deliberately misalign the stack
+	asm volatile ("addi sp, sp, -4");
+
+	while(1);
+	// Unreachable
+}
+```
+2. Compile with an appropriate RISC-V toolchain and run with `qemu-riscv64 ./a.out`.
+3. Send a `SIGINT` (e.g by hitting Ctrl-C), and observe that the signal frame will be misaligned:
+```
+signal occurred, info: 0x400080025c, context: 0x40008002dc
+```
+Additional information:
+This issue is alluded to in the source code, see https://gitlab.com/qemu-project/qemu/-/blob/master/linux-user/riscv/signal.c#L68-69. It should be sufficient to change that constant to 15.
diff --git a/results/classifier/gemma3:12b/kernel/1095857 b/results/classifier/gemma3:12b/kernel/1095857
new file mode 100644
index 00000000..19254e78
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1095857
@@ -0,0 +1,12 @@
+
+incorrect handling of [r32] address (long mode)
+
+while executing in Long Mode (x86-64) instructions such as
+
+mov eax,[r15d]
+
+end up executing as
+
+mov eax,[r15]
+
+according to x86 programmer manuals the behavior of using the Address-Size override (in long mode) is supposed to ignore the high 32bits of the register. I use this fact in my operating system to reduce register usage (the high 32 bits of r15 holds other data). consequently a general protection exception occurs since the memory address isn't "canonical". this error doesn't always appear since the high 32 bits might not be zero in those conditions.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1111 b/results/classifier/gemma3:12b/kernel/1111
new file mode 100644
index 00000000..b7cbf51d
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1111
@@ -0,0 +1,19 @@
+
+Calling FUTEX_LOCK_PI with qemu-x86_64-static caused ENOSYS error.
+Description of problem:
+When I executed the command "perf bench futex lock-pi" in amd64 docker image on s390x, I got the following error.
+```
+perf: thread 2: Could not lock pi-lock for 0x40006c4480 (-1): Function not implemented
+perf: thread 2: Could not lock pi-lock for 0x40006c4480 (-1): Function not implemented
+perf: thread 2: Could not lock pi-lock for 0x40006c4480 (-1): Function not implemented
+perf: thread 2: Could not lock pi-lock for 0x40006c4480 (-1): Function not implemented
+```
+
+I searched for this error message in the source code of perf-bench. I think that the following system call caused ENOSYS error.
+`  syscall(SYS_futex, uaddr, FUTEX_LOCK_PI | opflags, val, timeout, uaddr2, val3)`
+Steps to reproduce:
+1. Execute the command "perf bench futex lock-pi" in amd64 docker image on s390x
+2.
+3.
+Additional information:
+
diff --git a/results/classifier/gemma3:12b/kernel/1124 b/results/classifier/gemma3:12b/kernel/1124
new file mode 100644
index 00000000..a1c32ded
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1124
@@ -0,0 +1,2 @@
+
+AIX 5 not working with qemu-system-ppc64
diff --git a/results/classifier/gemma3:12b/kernel/1129 b/results/classifier/gemma3:12b/kernel/1129
new file mode 100644
index 00000000..d5efd053
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1129
@@ -0,0 +1,24 @@
+
+aarch64:qemu7.0.0 static compile error
+Description of problem:
+I'm trying to static compile qemu so I can chroot into different architectures and use podman for simulating amd64 containers.
+However, when I tried to configure using the command above, I got the following error:
+
+```
+FAILED: qemu-aarch64_be 
+c++  -o qemu-aarch64_be libcommon.fa.p/cpus-common.c.o libcommon.fa.p/page-vary-common.c.o libcommon.fa.p/disas_arm-a64.cc.o libcommon.fa.p/disas_libvixl_vixl_a64_decoder-a64.cc.o libcommon.fa.p/disas_libvixl_vixl_a64_disasm-a64.cc.o libcommon.fa.p/disas_libvixl_vixl_a64_instructions-a64.cc.o libcommon.fa.p/disas_libvixl_vixl_compiler-intrinsics.cc.o libcommon.fa.p/disas_libvixl_vixl_utils.cc.o libcommon.fa.p/disas_arm.c.o libcommon.fa.p/hw_core_cpu-common.c.o libcommon.fa.p/hw_core_machine-smp.c.o libcommon.fa.p/accel_accel-user.c.o libcommon.fa.p/common-user_safe-syscall.S.o libcommon.fa.p/common-user_safe-syscall-error.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_aarch64_signal.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_aarch64_cpu_loop.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_cpu.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_crypto_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_debug_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_gdbstub.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_iwmmxt_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_m_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_mve_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_neon_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_op_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_tlb_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate-m-nocp.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate-mve.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate-neon.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate-vfp.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_vec_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_vfp_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_cpu_tcg.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_kvm-stub.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_cpu64.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_gdbstub64.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_helper-a64.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_mte_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_pauth_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_sve_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate-a64.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate-sve.c.o libqemu-aarch64_be-linux-user.fa.p/trace_control-target.c.o libqemu-aarch64_be-linux-user.fa.p/cpu.c.o libqemu-aarch64_be-linux-user.fa.p/disas.c.o libqemu-aarch64_be-linux-user.fa.p/gdbstub.c.o libqemu-aarch64_be-linux-user.fa.p/page-vary.c.o libqemu-aarch64_be-linux-user.fa.p/semihosting_arm-compat-semi.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_optimize.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_region.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_tcg.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_tcg-common.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_tcg-op.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_tcg-op-gvec.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_tcg-op-vec.c.o libqemu-aarch64_be-linux-user.fa.p/fpu_softfloat.c.o libqemu-aarch64_be-linux-user.fa.p/accel_accel-common.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_tcg-all.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_cpu-exec-common.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_cpu-exec.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_tcg-runtime-gvec.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_tcg-runtime.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_translate-all.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_translator.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_user-exec.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_user-exec-stub.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_elfload.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_exit.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_fd-trans.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_linuxload.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_main.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_mmap.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_signal.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_strace.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_syscall.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_thunk.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_uaccess.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_uname.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_flatload.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_semihost.c.o libqemu-aarch64_be-linux-user.fa.p/meson-generated_.._aarch64_be-linux-user-gdbstub-xml.c.o -Wl,--as-needed -Wl,--no-undefined -pie -Wl,--whole-archive libhwcore.fa libqom.fa -Wl,--no-whole-archive -Wl,--warn-common -Wl,-z,relro -Wl,-z,now -static-pie -fstack-protector-strong -march=armv8-a -O2 -pipe -fstack-protector-strong -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -Wp,-D_GLIBCXX_ASSERTIONS -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -Wl,--start-group libqemuutil.a libhwcore.fa libqom.fa /usr/lib/libz.a -lrt -lutil -lm -pthread -lgthread-2.0 -lglib-2.0 -lpcre -lsysprof-capture-4 -lstdc++ -Wl,--end-group
+/usr/bin/ld: /usr/lib/gcc/aarch64-unknown-linux-gnu/12.1.0/../../../../lib/libglib-2.0.a(gutils.c.o): in function `g_get_user_database_entry':
+gutils.c:(.text+0x324): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
+/usr/bin/ld: gutils.c:(.text+0xf4): warning: Using 'getpwnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
+/usr/bin/ld: gutils.c:(.text+0xe0): warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
+/usr/lib/gcc/aarch64-unknown-linux-gnu/12.1.0/../../../../lib/libc.a(init-first.o): in function `__libc_init_first':
+(.text+0x10): relocation truncated to fit: R_AARCH64_LD64_GOTPAGE_LO15 against symbol `__environ' defined in .bss section in /usr/lib/gcc/aarch64-unknown-linux-gnu/12.1.0/../../../../lib/libc.a(environ.o)
+/usr/bin/ld: (.text+0x10): warning: too many GOT entries for -fpic, please recompile with -fPIC
+collect2: error: ld returned 1 exit status
+ninja: build stopped: subcommand failed.
+make: *** [Makefile:163: run-ninja] Error 1
+```
+Same error for both mentioned kernels in different aarch64 hardwares.
+Steps to reproduce:
+1. Download the tarball from version 7.0.0
+2. Run the configure as mentioned on the above command
diff --git a/results/classifier/gemma3:12b/kernel/1130 b/results/classifier/gemma3:12b/kernel/1130
new file mode 100644
index 00000000..e401968c
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1130
@@ -0,0 +1,30 @@
+
+error on run qemu-system-aarch64 -icount shift=1,align=off,sleep=on -smp 2
+Description of problem:
+This issue happen with the most recent version. 
+* Compile parameters:
+```
+./configure --target-list=aarch64-softmmu  --prefix=pwd/release  --disable-werror --enable-lto --enable-capstone --enable-system --enable-fdt --disable-xen --disable-kvm --enable-plugins
+```
+* run：
+```
+qemu-system-aarch64 -nographic -machine virt -cpu cortex-a57 -icount shift=1,align=off,sleep=on -smp 2 -vnc :2 -m 4080 -kernel /home/yuzy/mywork/linux/linux-5.15.30/arch/arm64/boot/Image.gz -initrd /home/yuzy/mywork/build/rootfs.cpio.gz
+```
+* error occurred：
+```
+**
+ERROR:../accel/tcg/tcg-accel-ops.c:79:tcg_handle_interrupt: assertion failed: (qemu_mutex_iothread_locked())
+Aborted (core dumped)
+```
+Steps to reproduce:
+1. run qemu-system-aarch64 -machine virt -cpu cortex-a57 -icount shift=1,align=off,sleep=on -smp 2 -m 4080 -kernel Image.gz -initrd rootfs.cpio.gz 
+2. it will assertion failed: (qemu_mutex_iothread_locked())
+Additional information:
+The following two situations are good：
+```
+qemu-system-aarch64 -machine virt -cpu cortex-a57 -icount shift=1,align=off,sleep=on -smp 1 -m 4080 -kernel Image.gz -initrd rootfs.cpio.gz
+```
+```
+qemu-system-aarch64 -machine virt -cpu cortex-a57 -smp 2 -m 4080 -kernel Image.gz -initrd rootfs.cpio.gz
+```
+I assume the issues are: gic
diff --git a/results/classifier/gemma3:12b/kernel/1133668 b/results/classifier/gemma3:12b/kernel/1133668
new file mode 100644
index 00000000..26ef420b
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1133668
@@ -0,0 +1,6 @@
+
+Bad validate ELF MIPSel format
+
+Detail and temporary path:
+
+http://www.devttys0.com/2011/12/qemu-vs-sstrip/#comment-10161
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1142 b/results/classifier/gemma3:12b/kernel/1142
new file mode 100644
index 00000000..11687578
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1142
@@ -0,0 +1,47 @@
+
+Measurements fail with direct kernel boot for AMD SEV confidential virtualization with 7.1 machine type
+Description of problem:
+When booting the QEMU with the 'kernel-hashes:true' property set for 'sev-guest' confidential virtualization, the contents of the `-kernel` file are measured by the firmware.
+
+A remote tenant can then validate the measurement against its expected contents to see if the boot was trustworthy.
+
+With the pc-q35-7.1 machine type the measurement always fails to validate against expected state.
+
+Making the following code change 
+
+```
+diff --git a/hw/i386/pc.c b/hw/i386/pc.c
+index 7280c02ce3..3a4bf5cba3 100644
+--- a/hw/i386/pc.c
++++ b/hw/i386/pc.c
+@@ -1899,6 +1899,8 @@ static void pc_machine_class_init(ObjectClass *oc, void *data)
+     pcmc->rsdp_in_ram = true;
+     pcmc->smbios_defaults = true;
+     pcmc->smbios_uuid_encoded = true;
++    pcmc->legacy_no_rng_seed = true;
++
+     pcmc->gigabyte_align = true;
+     pcmc->has_reserved_memory = true;
+     pcmc->kvmclock_enabled = true;
+```
+
+results in successfully validating the measurement.
+
+THis is not surprising, the RNG seed patch introduced in 
+
+```
+commit 67f7e426e53833a5db75b0d813e8d537b8a75bd2
+Author: Jason A. Donenfeld <Jason@zx2c4.com>
+Date:   Thu Jul 21 14:56:36 2022 +0200
+
+    hw/i386: pass RNG seed via setup_data entry
+```
+
+intentionally modifies the contents of the kernel image before passing it to the firmware, to inject a random seed. This will ensure the boot measuremnts are different every time.
+
+This RNG seed functionality must NOT be used when AMD SEV is active.
+Steps to reproduce:
+1. Create an AMD SEV guest with kernel-hashes=true and pc-q35-7.1 machine type
+2. Attempt to validate the boot measurement
+Additional information:
+
diff --git a/results/classifier/gemma3:12b/kernel/1147 b/results/classifier/gemma3:12b/kernel/1147
new file mode 100644
index 00000000..60a009f2
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1147
@@ -0,0 +1,10 @@
+
+x86_64 emu on aarch64 host: cpu_exec: assertion failed: (cpu == current_cpu)
+Description of problem:
+Execution of some binaries crashes with `Bail out! ERROR:../qemu-7.0.0/accel/tcg/cpu-exec.c:933:cpu_exec: assertion failed: (cpu == current_cpu)`. Looking at the code, that code is wrapped in a gcc/clang ifdef. Recompiling with clang produces this crash instead: `... include/qemu/rcu.h:102: void rcu_read_unlock(void): Assertion 'p_rcu_reader->depth != 0' failed.`
+
+No easier steps to reproduce (yet) than `systemd-nspawn`ing into an x86_64 Ubuntu container invoking qemu-x86_64-static through binfmt. Commands such as `ls` work fine, while `apt-get` will immediately crash with the error listed above.
+
+Note that this happens running Asahi Linux on the bare metal of an M1-based Macbook Pro. This same issue does *not* occur running the *same* binaries with the *same* x86_64 Ubuntu image on an Arch or Ubuntu VM under macOS on the same machine - regardless of if the QEMU binaries were built in a VM or in Asahi.
+
+These are big.LITTLE chips. Using taskset/affinity to limit the target process to a single specific core does not help. The Asahi kernel has a 16K page-size, which is known to cause trouble for some programs. qemu-arm(-static) however works without any issues (the M1 cannot run 32-bit ARM code natively, only 64-bit).
diff --git a/results/classifier/gemma3:12b/kernel/1156313 b/results/classifier/gemma3:12b/kernel/1156313
new file mode 100644
index 00000000..3761928f
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1156313
@@ -0,0 +1,71 @@
+
+X86-64 flags handling broken
+
+The current qemu sources cause improper handling of flags on x86-64.
+This bug seems to have shown up a few weeks ago.
+
+A plain install of Debian GNU/Linux makes user processes catch
+spurious signals.  The kernel seems to run stably, though.
+
+The ADX feature works very poorly.  It might be related; at least it
+allows for reproducibly provoking invalid behaviour.
+
+Here is a test case:
+
+================================================================
+qemumain.c
+#include <stdio.h>
+long adx();
+int
+main ()
+{
+  printf ("%lx\n", adx (0xffbeef, 17));
+  return 0;
+}
+================================================================
+qemuadx.s:
+        .globl  adx
+adx:    xor     %rax, %rax
+1:      dec     %rdi
+        jnz     1b
+        .byte 0xf3, 0x48, 0x0f, 0x38, 0xf6, 0xc0        # adox  %rax, %rax
+        .byte 0x66, 0x48, 0x0f, 0x38, 0xf6, 0xc0        # adcx  %rax, %rax
+        ret
+================================================================
+
+Compile and execute:
+$ gcc -m64 qemumain.c qemuadx.s
+$ a.out
+ffffff8000378cd8
+
+Expected output is simply "0".  The garbage value varies between qemu
+compiles and guest systems.
+
+Note that one needs a recent GNU assembler in order to handle adox and
+adcx.  For convenience I have supplied them as byte sequences.
+
+Exaplanation and feeble analysis:
+
+The 0xffbeef argument is a loop count.  It is necessary to loop for a
+while in order to trigger this bug.  If the loop count is decreased,
+the bug will seen intermittently; the lower the count, the less
+frequent the invalid behaviour.
+
+It seems like a reasonable assumption that this bug is related to
+flags handling at context switch.  Presumably, qemu keeps flags state
+in some internal format, then recomputes then when needing to form the
+eflags register, as needed for example for context switching.
+
+I haven't tried to reproduce this bug using qemu-x86_64 and SYSROOT,
+but I strongly suspect that to be impossible.  I use
+qemu-system-x86_64 and the guest Debian GNU/Linux x86_64 (version
+6.0.6) .
+
+The bug happens also with the guest FreeBSD x86_64 version 9.1.  (The
+iteration count for triggering the problem 50% of the runs is not the
+same when using the kernel Linux and FreeBSD's kernel, presumably due
+to different ticks.)
+
+The bug happens much more frequently for a loaded system; in fact, the
+loop count can be radically decreased if two instances of the trigger
+program are run in parallel.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1157 b/results/classifier/gemma3:12b/kernel/1157
new file mode 100644
index 00000000..b68d7d20
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1157
@@ -0,0 +1,14 @@
+
+aarch64: enabling MMU causes instruction abort
+Description of problem:
+The title describes the problem pretty accurately, we get an instruction abort when enabling the MMU with a pretty simple set of page tables. This has been regressed from qemu 6.x.
+Steps to reproduce:
+1. Run the provided Kernel binary with the command line specified above.
+2. Notice the hang after 'Initialize MMU'. I traced it down to being an instructions abort after the write to the SCTLR_EL1 register.
+3. Try to run with qemu 6.x, and notice that it works.
+Additional information:
+This does work on actual hardware, so it has to be a qemu bug.
+
+A binary of the Serenity Kernel has been attached to the issue. The source of that binary can be found at commit ca0e32e59fcf67a662e5d3a994d44cd7c941624a of [SerenityOS](https://github.com/SerenityOS/serenity).
+
+[Kernel](/uploads/f731edbf81d8e575035e9693b0a51dbf/Kernel)
diff --git a/results/classifier/gemma3:12b/kernel/1165 b/results/classifier/gemma3:12b/kernel/1165
new file mode 100644
index 00000000..3e3e989f
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1165
@@ -0,0 +1,4 @@
+
+About support LoongArch architecture
+Additional information:
+Start from Linux 5.19, maybe can find the compatible source code for LoongArch in the Linux Kernel source code archive.
diff --git a/results/classifier/gemma3:12b/kernel/1170 b/results/classifier/gemma3:12b/kernel/1170
new file mode 100644
index 00000000..ddc90eb5
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1170
@@ -0,0 +1,57 @@
+
+Unable to compile in Ubuntu 22.04, at compiling linux-user_arm_nwfpe_double_cpdo.c.o
+Description of problem:
+Compiling of QEMU 7.1.0-rc3 stops here for me:
+```
+[7172/9855] Compiling C object libqemu-armeb-linux-user.fa.p/linux-user_arm_nwfpe_double_cpdo.c.o
+FAILED: libqemu-armeb-linux-user.fa.p/linux-user_arm_nwfpe_double_cpdo.c.o 
+cc -m64 -mcx16 -Ilibqemu-armeb-linux-user.fa.p -I. -I.. -Itarget/arm -I../target/arm -I../common-user/host/x86_64 -I../linux-user/include/host/x86_64 -I../linux-user/include -Ilinux-user -I../linux-user -Ilinux-user/arm -I../linux-user/arm -Iqapi -Itrace -Iui -Iui/shader -I/usr/include/capstone -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -fdiagnostics-color=auto -Wall -Winvalid-pch -std=gnu11 -O2 -g -isystem /home/andrea/Downloads/qemu-7.1.0-rc3/linux-headers -isystem linux-headers -iquote . -iquote /home/andrea/Downloads/qemu-7.1.0-rc3 -iquote /home/andrea/Downloads/qemu-7.1.0-rc3/include -iquote /home/andrea/Downloads/qemu-7.1.0-rc3/tcg/i386 -pthread -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wold-style-declaration -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wimplicit-fallthrough=2 -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -fPIE -isystem../linux-headers -isystemlinux-headers -DNEED_CPU_H '-DCONFIG_TARGET="armeb-linux-user-config-target.h"' '-DCONFIG_DEVICES="armeb-linux-user-config-devices.h"' -MD -MQ libqemu-armeb-linux-user.fa.p/linux-user_arm_nwfpe_double_cpdo.c.o -MF libqemu-armeb-linux-user.fa.p/linux-user_arm_nwfpe_double_cpdo.c.o.d -o libqemu-armeb-linux-user.fa.p/linux-user_arm_nwfpe_double_cpdo.c.o -c ../linux-user/arm/nwfpe/double_cpdo.c
+during RTL pass: expand
+../linux-user/arm/nwfpe/double_cpdo.c: In function ‘DoubleCPDO’:
+../linux-user/arm/nwfpe/double_cpdo.c:232:1: internal compiler error: Segmentation fault
+  232 | }
+      | ^
+0x7fe5b824251f ???
+	./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
+0x7fe5b8229d8f __libc_start_call_main
+	../sysdeps/nptl/libc_start_call_main.h:58
+0x7fe5b8229e3f __libc_start_main_impl
+	../csu/libc-start.c:392
+Please submit a full bug report,
+with preprocessed source if appropriate.
+Please include the complete backtrace with any bug report.
+See <file:///usr/share/doc/gcc-11/README.Bugs> for instructions.
+ninja: build stopped: subcommand failed.
+make[1]: *** [Makefile:162: run-ninja] Error 1
+make[1]: Leaving directory '/home/andrea/Downloads/qemu-7.1.0-rc3/build'
+make: *** [GNUmakefile:11: all] Error 2
+```
+
+Configure Output:
+[Configure_Output.txt](/uploads/40055846573b79cc2817d5cb338e18c1/Configure_Output.txt)
+
+Compiles on 7.0.0.
+Steps to reproduce:
+1. Run 'sudo apt purge qemu-kvm qemu-utils libvirt-daemon-system libvirt-clients bridge-utils virt-manager ovmf'
+2. Run 'sudo apt-get install git libglib2.0-dev libfdt-dev libpixman-1-dev zlib1g-dev ninja-build' ([Wiki](https://wiki.qemu.org/Hosts/Linux))
+3. Additional Packages:
+```
+sudo apt-get install git-email
+sudo apt-get install libaio-dev libbluetooth-dev libcapstone-dev libbrlapi-dev libbz2-dev
+sudo apt-get install libcap-ng-dev libcurl4-gnutls-dev libgtk-3-dev
+sudo apt-get install libibverbs-dev libjpeg8-dev libncurses5-dev libnuma-dev
+sudo apt-get install librbd-dev librdmacm-dev
+sudo apt-get install libsasl2-dev libsdl2-dev libseccomp-dev libsnappy-dev libssh-dev
+sudo apt-get install libvde-dev libvdeplug-dev libvte-2.91-dev libxen-dev liblzo2-dev
+sudo apt-get install valgrind xfslibs-dev 
+
+sudo apt-get install libnfs-dev libiscsi-dev
+```
+4. Build instructions for QEMU:
+```
+wget https://download.qemu.org/qemu-7.1.0-rc3.tar.xz
+tar xvJf qemu-7.1.0-rc3.tar.xz
+cd qemu-7.1.0-rc3
+./configure
+make
+```
diff --git a/results/classifier/gemma3:12b/kernel/1173 b/results/classifier/gemma3:12b/kernel/1173
new file mode 100644
index 00000000..e7c89500
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1173
@@ -0,0 +1,2 @@
+
+is that `fsgnjn.s` will affect other bits except sign bit.
diff --git a/results/classifier/gemma3:12b/kernel/1179664 b/results/classifier/gemma3:12b/kernel/1179664
new file mode 100644
index 00000000..dab56c03
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1179664
@@ -0,0 +1,16 @@
+
+migration.c:293: undefined reference to  `__sync_val_compare_and_swap_4'
+
+latest git qemu error i get on compiling with mingw
+
+  LINK  i386-softmmu/qemu-system-i386w.exe
+../migration.o: In function `migrate_finish_set_state':
+C:\MinGW\msys\1.0\home\therock247uk\qemu/migration.c:293: undefined reference to
+ `__sync_val_compare_and_swap_4'
+C:\MinGW\msys\1.0\home\therock247uk\qemu/migration.c:293: undefined reference to
+ `__sync_val_compare_and_swap_4'
+C:\MinGW\msys\1.0\home\therock247uk\qemu/migration.c:293: undefined reference to
+ `__sync_val_compare_and_swap_4'
+collect2.exe: error: ld returned 1 exit status
+make[1]: *** [qemu-system-i386w.exe] Error 1
+make: *** [subdir-i386-softmmu] Error 2
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1187 b/results/classifier/gemma3:12b/kernel/1187
new file mode 100644
index 00000000..13f7db86
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1187
@@ -0,0 +1,2 @@
+
+can not handler real-time signal (signal number > 30) by sigqueue on linux user mode
diff --git a/results/classifier/gemma3:12b/kernel/1193628 b/results/classifier/gemma3:12b/kernel/1193628
new file mode 100644
index 00000000..f6659ade
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1193628
@@ -0,0 +1,23 @@
+
+Undefined References
+
+I've been able to make qemu on ubuntu 13.04 for all last releases: 1.4.0 -> 1.5.0
+
+Unfortunately, when I launch one of them with a Cisco ASA, it crashes inside GNS3 (latest release) for Ubuntu.
+The top GNS3 developer told me they experienced similar results and advised me to use qemu 1.1.0.
+
+The problem is that I cannot link that version. I always have these errors:
+ 
+"LINK  qemu-ga
+qemu-timer.o: In function `dynticks_rearm_timer':
+/home/actionmystique/Downloads/qemu-1.1.0/qemu-timer.c:538: undefined reference to `timer_gettime'
+/home/actionmystique/Downloads/qemu-1.1.0/qemu-timer.c:551: undefined reference to `timer_settime'
+qemu-timer.o: In function `dynticks_stop_timer':
+/home/actionmystique/Downloads/qemu-1.1.0/qemu-timer.c:524: undefined reference to `timer_delete'
+qemu-timer.o: In function `dynticks_start_timer':
+/home/actionmystique/Downloads/qemu-1.1.0/qemu-timer.c:510: undefined reference to `timer_create'
+collect2: error: ld returned 1 exit status
+make: *** [qemu-ga] Error 1"
+
+The man pages say we need to link with '-lrt' option, but I could not find it in the Makefile.
+I do not know how to correct this issue.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1195012 b/results/classifier/gemma3:12b/kernel/1195012
new file mode 100644
index 00000000..eb37186c
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1195012
@@ -0,0 +1,23 @@
+
+x86_64 and i386 return 0 when reading MSR_TSC
+
+Running NetBSD 6.1 (i386 and amd64) under QEMU (from git - 1.5.50 is the version it shows) results in an incorrectly set
+TSC frequency (set to 0), because NetBSD uses rdmsr(TSC_MSR) for its serializing CPU counter.
+
+To reproduce the problem, you can run an install ISO of NetBSD 6.1 (either i386 or amd64, depending on which qemu).  Quit out of the installer, and you're left at a root prompt:
+
+# sysctl machdep.tsc_freq
+machdep.tsc_freq = 0
+
+...on real hardware, it will return the TSC frequency:
+
+# sysctl machdep.tsc_freq
+machdep.tsc_freq = 3292685070
+
+...this causes problems with a number of applications.
+
+The NetBSD code which reads the MSR is here:
+
+http://nxr.netbsd.org/xref/src/sys/arch/x86/x86/tsc.c#262
+
+... the "rdmsr(MSR_TSC)" call in cpu_counter_serializing() always returns 0 when run under QEMU.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1207686 b/results/classifier/gemma3:12b/kernel/1207686
new file mode 100644
index 00000000..69f5138d
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1207686
@@ -0,0 +1,29 @@
+
+qemu-1.4.0 and onwards, linux kernel 3.2.x, heavy I/O leads to kernel_hung_tasks_timout_secs message and unresponsive qemu-process
+
+Hi,
+
+after some testing I tried to narrow down a problem, which was initially reported by some users.
+Seen on different distros - debian 7.1, ubuntu 12.04 LTS, IPFire-2.3 as reported by now.
+
+All using some flavour of linux-3.2.x kernel.
+
+Tried e.g. under Ubuntu an upgrade to "Linux 3.8.0-27-generic x86_64" which solves the problem.
+Problem could be triggert with some workload ala:
+
+spew -v --raw -P -t -i 3 -b 4k -p random -B 4k 1G /tmp/doof.dat
+and in parallel do some apt-get install/remove/whatever.
+
+That results in a somewhat stuck qemu-session with the bad "kernel_hung_task..." messages.
+
+A typical command-line is as follows:
+
+/usr/local/qemu-1.6.0/bin/qemu-system-x86_64 -usbdevice tablet -enable-kvm -daemonize -pidfile /var/run/qemu-server/760.pid -monitor unix:/var/run/qemu-server/760.mon,server,nowait -vnc unix:/var/run/qemu-server/760.vnc,password -qmp unix:/var/run/qemu-server/760.qmp,server,nowait -nodefaults -serial none -parallel none -device virtio-net-pci,mac=00:F1:70:00:2F:80,netdev=vlan0d0 -netdev type=tap,id=vlan0d0,ifname=tap760i0d0,script=/etc/fcms/add_if.sh,downscript=/etc/fcms/downscript.sh -name 1155823384-4 -m 512 -vga cirrus -k de -smp sockets=1,cores=1 -device virtio-blk-pci,drive=virtio0 -drive format=raw,file=rbd:1155823384/vm-760-disk-1.rbd:rbd_cache=false,cache=writeback,if=none,id=virtio0,media=disk,index=0,aio=native -drive format=raw,file=rbd:1155823384/vm-760-swap-1.rbd:rbd_cache=false,cache=writeback,if=virtio,media=disk,index=1,aio=native -drive if=ide,media=cdrom,id=ide1-cd0,readonly=on -drive if=ide,media=cdrom,id=ide1-cd1,readonly=on -boot order=dc
+
+no "system_reset", "sendkey ctrl-alt-delete" or "q" in monitoring-session is accepted, need to hard-kill the process.
+
+Please give any advice on what to do for tracing/debugging, because the number of tickets here are raising, and noone knows, what users are doing inside their VM.
+
+Kind regards,
+
+Oliver Francke.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1211943 b/results/classifier/gemma3:12b/kernel/1211943
new file mode 100644
index 00000000..f970f151
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1211943
@@ -0,0 +1,4 @@
+
+#GP and aligned move instruction
+
+When the operand of movaps, movapd or movdqa instruction isn't aligned, general-protection exception should be generated.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1218098 b/results/classifier/gemma3:12b/kernel/1218098
new file mode 100644
index 00000000..85811319
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1218098
@@ -0,0 +1,71 @@
+
+qemu-system-ppc64 segfaults in helper_ldl_mmu
+
+Download a Fedora 19 ISO from:
+http://mirrors.kernel.org/fedora-secondary/releases/19/Fedora/ppc64/iso/
+
+Compile qemu from git (I'm using 401c227b0a1134245ec61c6c5a9997cfc963c8e4
+from today).
+
+Run qemu-system-ppc64 like this:
+
+ppc64-softmmu/qemu-system-ppc64 -M pseries -m 4096 -hda /dev/fedora/f20ppc64 -cdrom /tmp/Fedora-19-ppc64-DVD.iso -netdev user,id=usernet,net=169.254.0.0/16 -device virtio-net-pci,netdev=usernet
+
+Guest gets to yaboot.  If you hit return, qemu segfaults:
+
+Program received signal SIGABRT, Aborted.
+0x00007ffff041fa19 in __GI_raise (sig=sig@entry=6)
+    at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
+56	  return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
+(gdb) t a a bt
+
+Thread 4 (Thread 0x7fff6eef7700 (LWP 7553)):
+#0  sem_timedwait ()
+    at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_timedwait.S:101
+#1  0x00005555559a5897 in qemu_sem_timedwait (sem=sem@entry=0x55555631e788, 
+    ms=ms@entry=10000) at util/qemu-thread-posix.c:238
+#2  0x000055555577e54c in worker_thread (opaque=0x55555631e6f0)
+    at thread-pool.c:97
+#3  0x00007ffff625ec53 in start_thread (arg=0x7fff6eef7700)
+    at pthread_create.c:308
+#4  0x00007ffff04df13d in clone ()
+    at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
+
+Thread 3 (Thread 0x7fff6e605700 (LWP 7547)):
+#0  0x00007ffff041fa19 in __GI_raise (sig=sig@entry=6)
+    at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
+#1  0x00007ffff0421128 in __GI_abort () at abort.c:90
+#2  0x000055555583ea33 in helper_ldl_mmu (env=0x7ffff7fd7140, addr=1572864, 
+    mmu_idx=1) at /home/rjones/d/qemu/include/exec/softmmu_template.h:153
+#3  0x00007fffab0819d8 in code_gen_buffer ()
+#4  0x00005555557aa7ae in cpu_tb_exec (tb_ptr=<optimized out>, 
+    cpu=0x7ffff7fd7010) at /home/rjones/d/qemu/cpu-exec.c:56
+#5  cpu_ppc_exec (env=env@entry=0x7ffff7fd7140)
+    at /home/rjones/d/qemu/cpu-exec.c:631
+#6  0x00005555557abc35 in tcg_cpu_exec (env=0x7ffff7fd7140)
+    at /home/rjones/d/qemu/cpus.c:1193
+#7  tcg_exec_all () at /home/rjones/d/qemu/cpus.c:1226
+#8  qemu_tcg_cpu_thread_fn (arg=<optimized out>)
+    at /home/rjones/d/qemu/cpus.c:885
+#9  0x00007ffff625ec53 in start_thread (arg=0x7fff6e605700)
+    at pthread_create.c:308
+#10 0x00007ffff04df13d in clone ()
+    at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
+
+Thread 1 (Thread 0x7ffff7fa9a40 (LWP 7542)):
+#0  0x00007ffff04d4c2f in __GI_ppoll (fds=0x555556483210, nfds=4, 
+    timeout=<optimized out>, timeout@entry=0x7fffffffd940, 
+    sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:56
+#1  0x0000555555762db9 in ppoll (__ss=0x0, __timeout=0x7fffffffd940, 
+    __nfds=<optimized out>, __fds=<optimized out>)
+    at /usr/include/bits/poll2.h:77
+#2  qemu_poll_ns (fds=<optimized out>, nfds=<optimized out>, 
+    timeout=timeout@entry=951497) at qemu-timer.c:276
+#3  0x000055555572b58c in os_host_main_loop_wait (timeout=951497)
+    at main-loop.c:228
+#4  main_loop_wait (nonblocking=<optimized out>) at main-loop.c:484
+#5  0x00005555555ef9d8 in main_loop () at vl.c:2090
+#6  main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>)
+    at vl.c:4435
+
+NB: This does NOT happen if you specify -cpu POWER7 on the command line.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1242963 b/results/classifier/gemma3:12b/kernel/1242963
new file mode 100644
index 00000000..38e95b43
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1242963
@@ -0,0 +1,27 @@
+
+QEMU loadvm causes guest OS freeze
+
+HOST: ubuntu 13.10 x64
+GUEST: winxp sp 3 x86
+
+AFFECT QEMU(tested): v1.5.2, v1.5.3,  v1.6.0, v1.6.1
+
+I compile QEMU by myself with "./configure --target-list=i386-softmmu && make && make install".
+After installing a winxp sp3 into the qemu-system-i386 with command line:
+> qemu-system-i386 -m 512 -hda xp.img -net user -net nic,model=rtl8139 -rtc base=localtime,clock=vm
+
+I use monitor to create a live snapshot: 
+> stop
+> savevm xxx
+> cont
+
+And then I load this snapshot (I also try it in commad line: -loadvm xxx):
+> loadvm xxx
+> cont
+
+After that, the windows system is freeze (don't accept any keyboard or mouse input, although I knew vcpu is still working).
+
+If I compile with -enable-kvm and launch qemu-system-i386 with -enable-kvm, it looks like everything works well.
+I think it is a bug for qemu system.
+
+BTW: freeze is not appearing 100%, but in my test, 95% cases would cause system freeze.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1245 b/results/classifier/gemma3:12b/kernel/1245
new file mode 100644
index 00000000..c65a33fd
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1245
@@ -0,0 +1,2 @@
+
+arm: cp15 support
diff --git a/results/classifier/gemma3:12b/kernel/1254786 b/results/classifier/gemma3:12b/kernel/1254786
new file mode 100644
index 00000000..ba4129c2
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1254786
@@ -0,0 +1,43 @@
+
+qemu-m68k-static: illegal instruction ebc0 during debootstrap second stage
+
+Host: Ubuntu Precise amd64
+Guest: Debian (ports) sid m68k
+
+$ sudo qemu-debootstrap --no-check-gpg --arch=m68k sid m68k http://ftp.debian-ports.org/debian
+I: Running command: debootstrap --arch m68k --foreign --no-check-gpg sid m68k http://ftp.debian-ports.org/debian
+[...]
+I: Running command: chroot m68k /debootstrap/debootstrap --second-stage
+qemu: fatal: Illegal instruction: ebc0 @ f67e5662
+D0 = 6ffffef5   A0 = f67fbf58   F0 = 0000000000000000 (           0)
+D1 = 0000010a   A1 = 00000000   F1 = 0000000000000000 (           0)
+D2 = 0000000f   A2 = 00000000   F2 = 0000000000000000 (           0)
+D3 = 00000000   A3 = f67e0000   F3 = 0000000000000000 (           0)
+D4 = 00000000   A4 = 00000000   F4 = 0000000000000000 (           0)
+D5 = 00000000   A5 = f67fc000   F5 = 0000000000000000 (           0)
+D6 = 00000000   A6 = f6fff7cc   F6 = 0000000000000000 (           0)
+D7 = 00000000   A7 = f6fff580   F7 = 0000000000000000 (           0)
+PC = f67e5662   SR = 0000 ----- FPRESULT =            0
+Aborted (core dumped)
+
+ProblemType: Bug
+DistroRelease: Ubuntu 12.04
+Package: qemu-user-static 1.0.50-2012.03-0ubuntu2.1
+ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11
+Uname: Linux 3.8.0-33-generic x86_64
+NonfreeKernelModules: wl
+ApportVersion: 2.0.1-0ubuntu17.6
+Architecture: amd64
+Date: Mon Nov 25 16:08:26 2013
+Dependencies:
+ 
+InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1)
+MarkForUpload: True
+ProcEnviron:
+ LANGUAGE=en_GB:en
+ TERM=xterm
+ PATH=(custom, no user)
+ LANG=en_GB.UTF-8
+ SHELL=/bin/bash
+SourcePackage: qemu-linaro
+UpgradeStatus: No upgrade log present (probably fresh install)
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1256548 b/results/classifier/gemma3:12b/kernel/1256548
new file mode 100644
index 00000000..3352880e
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1256548
@@ -0,0 +1,12 @@
+
+qemu windows guest issues
+
+Ive noticed the following in the latest qemu build on mingw 64bit for windows
+
+older guests like windows 9* no longer boot they mostly just bsod its been this way for ages same with 32bit builds
+xp 64bit and other 64bit windows guests no longer work and havent for ages same with 32bit builds 
+xp 32bit guest doesent work under 64bit builds but they work on 32bit builds
+
+are the issues with the coroutine stuff on windows builds being worked on? id gladly test patches
+
+just a few observations is all :)
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1277 b/results/classifier/gemma3:12b/kernel/1277
new file mode 100644
index 00000000..01975a5d
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1277
@@ -0,0 +1,2 @@
+
+two instructions has executed twice
diff --git a/results/classifier/gemma3:12b/kernel/1278166 b/results/classifier/gemma3:12b/kernel/1278166
new file mode 100644
index 00000000..0220ebed
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1278166
@@ -0,0 +1,4 @@
+
+Last commit to exec.c causes BSOD installing WinXP on i386-softmmu
+
+The last commit to exec.c (360e607b88a23d378f6efaa769c76d26f538234d), causes a BSOD when trying to install a 32bit Windows XP SP-3 image using the pure emulation version of i386-softmmu. A checkout of the previous version of the file (commited in 0169c511554cb0014a00290b0d3d26c31a49818f) solves the problem. Nevertheless, this last commit was intented to solve a BSOD when Xen was used as a hypervisor.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1287195 b/results/classifier/gemma3:12b/kernel/1287195
new file mode 100644
index 00000000..fc7009d1
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1287195
@@ -0,0 +1,4 @@
+
+validate_guest_space incorrectly enabled on AArch64
+
+When running linux-user targetting AArch64, validate_guest_space() in elfload.c reserves space in the guest address space for the ARM commpage. Since there is no commpage on AArch64, this function should be disable on that target.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1290370 b/results/classifier/gemma3:12b/kernel/1290370
new file mode 100644
index 00000000..d62e3457
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1290370
@@ -0,0 +1,31 @@
+
+FreeBSD 9.2 shell crashes when run with -smp 4 option
+
+This is a bug that i have noticed in qemu 1.7.50 as well as 1.1.50. It was the latter that forced me to clone the repository to check if this is the case with the resent version as well . The latest commit on which the bug is found is f53f3d0a00b6df39ce8dfca942608e5b6a9a4f71 on qemu.git
+
+configured with target list i386-softmmu
+and then 
+make
+ 
+OS: FreeBSD 9.2 Text Install ISO
+Installed it to a qcow2 format image.
+
+./i386-softmmu/qemu-system-i386 -hda <bsd-image> -m 2G -smp 4 -net nic -net user -monitor stdio
+
+(boot into multi-user mode)->(login to root account)
+
+I have the filebench benchmark installed on the image and when i run it the default root shell (csh) crashes with the error.
+[pid xxxx (csh) sigreturn eflag = 0xXXXX]
+Here is the piece of kernel code that is getting executed (i think) http://svnweb.freebsd.org/base/release/9.2.0/sys/i386/i386/machdep.c?view=markup#l1095 
+
+Here is a related bug
+https://www.virtualbox.org/ticket/458
+
+The crash happens randomly. It is not just related with filebench. 
+Here are a few scenarios:
+* When i run fileserver workload of filebench
+* After i issue the shutdown -h now shutdown -r now commands
+* Issuing mount -t linprocfs proc /proc
+
+Moreover it is not guaranteed that the above scenarios will reproduce it (reliably). 
+Basically after running some commands and getting the CPU and the kernel worked up i think.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1292037 b/results/classifier/gemma3:12b/kernel/1292037
new file mode 100644
index 00000000..8dca5543
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1292037
@@ -0,0 +1,15 @@
+
+Solaris 10 x86 guest crashes qemu with -icount 1 option
+
+Commit: f53f3d0a00b6df39ce8dfca942608e5b6a9a4f71 on qemu.git
+
+Solaris image: Solaris 10 x86 (32 bit)
+
+command: ./i386-softmmu/qemu-system-i386 -hda <image-file> -m 2G -icount 1 -monitor stdio 
+
+Crashes saying:
+qemu: Fatal: Raised interrupt while not in I/O function
+
+Host:
+ubuntu x86_64 3.2.0-56 generic
+intel xeon E5649 @ 2.53GHz
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1299858 b/results/classifier/gemma3:12b/kernel/1299858
new file mode 100644
index 00000000..f6b95d8f
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1299858
@@ -0,0 +1,10 @@
+
+qemu all apps crash on OS X 10.6.8
+
+qemu-2.0.0-rc0 (and 1.7.1) crashes with SIGABORT in all apps when configured with --with-coroutine=sigaltstack (which is what configure selects by default) but all  run fine if configured with --with-coroutine=gthread.
+
+Crash is at line 253 (last line of Coroutine *qemu_coroutine_new(void)) in coroutine-sigaltstack.c in 2.0.0-rc0 tarball.
+
+Platform is OS X 10.6.8 (Darwin Kernel Version 10.8.0), compiler gcc 4.2.1
+
+Sorry for the sparse report but I'm short on time today.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1300021 b/results/classifier/gemma3:12b/kernel/1300021
new file mode 100644
index 00000000..bb5e03ea
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1300021
@@ -0,0 +1,5 @@
+
+after loadvm the system clock isn't current time
+
+hi,
+when i load a  snapshot of month ago using "loadvm  name"command, the vm system time is past time,not recover current time.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1303 b/results/classifier/gemma3:12b/kernel/1303
new file mode 100644
index 00000000..fc1db761
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1303
@@ -0,0 +1,2 @@
+
+tcg/cputlb: code path is reachable in load_memop/store_memop()
diff --git a/results/classifier/gemma3:12b/kernel/1318281 b/results/classifier/gemma3:12b/kernel/1318281
new file mode 100644
index 00000000..2d07cc82
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1318281
@@ -0,0 +1,35 @@
+
+linux-user: x86_64 target fails to call sys_futex()
+
+I'm building the latest QEMU (06b4f00d53637f2c16a62c2cbaa30bffb045cf88) on ARM to run some x86_64 executables in user mode. This is my configuration:
+
+./configure \
+  --prefix=/root/qemu-x86_64 \
+  --target-list=x86_64-linux-user \
+  --disable-system \
+  --disable-tools
+
+The following program is used for testing:
+
+https://gist.github.com/hujiajie/e8cff43b574b399c8f59#file-test-c
+
+I compile the test program in Debian-7.5-amd64 like this:
+
+gcc -o test `pkg-config --cflags glib-2.0` test.c `pkg-config --static --libs glib-2.0` -static
+
+and launch the program on ARM with
+
+qemu-x86_64 test
+
+The test crashes with the following message:
+
+qemu: uncaught target signal 11 (Segmentation fault) - core dumped
+Segmentation fault
+
+The output of `strace qemu-x86_64 test` is here:
+
+https://gist.github.com/hujiajie/88d1d5e580d432d11b2d#file-test-strace-log
+
+It seems that the error is caused by the failure of the futex syscall.
+
+qemu-i386 could launch the 32-bit test perfectly, the problem only happens on a x86_64 target.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1320968 b/results/classifier/gemma3:12b/kernel/1320968
new file mode 100644
index 00000000..3d4031b4
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1320968
@@ -0,0 +1,10 @@
+
+qemu-system-ppc -cpu G2leGP3 crashes
+
+qemu crashes when running qemu-system-ppc -cpu G2leGP3 :
+
+qemu-system-ppc -cpu G2leGP3
+Error: Trying to register SPR 1013 (3f5) twice !
+
+qemu-system-ppc -version
+QEMU emulator version 2.0.50, Copyright (c) 2003-2008 Fabrice Bellard
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1324727 b/results/classifier/gemma3:12b/kernel/1324727
new file mode 100644
index 00000000..27335d30
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1324727
@@ -0,0 +1,30 @@
+
+qemu-system-arm segfaults without KVM on ARM
+
+I'm running on Odroid-XU, Debian Jessie armhf
+qemu built from today's head d7d3d6092cb7edc75dc49fb90c86dd5425ab4805
+
+sudo  qemu-system-arm -M vexpress-a15 -drive if=none,file=arm.img,cache=writeback,id=foo -device virtio-blk-device,drive=foo -netdev user,id=user.0 -device virtio-net-device,netdev=user.0 -nographic -append 'root=/dev/vda rw console=ttyAMA0 rootwait' -kernel /usr/src/build/arm/linux-guest/arch/arm/boot/zImage -dtb a15x2.dtb
+audio: Could not init `oss' audio driver
+Uncompressing Linux... done, booting the kernel.
+Segmentation fault
+
+If I run under GDB, the linux guest instance panics or hangs -- the behaviour is variable run to run.
+
+If I do:
+sudo  qemu-system-arm --enable-kvm -M vexpress-a15 -drive if=none,file=arm.img,cache=writeback,id=foo -device virtio-blk-device,drive=foo -netdev user,id=user.0 -device virtio-net-device,netdev=user.0 -nographic -append 'root=/dev/vda rw console=ttyAMA0 rootwait' -kernel /usr/src/build/arm/linux-guest/arch/arm/boot/zImage -dtb a15x2.dtb
+
+then the guest boots as expected.
+
+I tried to get a backtrace by allowinghte SEGV to dump core, and using gdb to inspect it:
+Core was generated by `qemu-system-arm -M vexpress-a15 -drive if=none,file=arm.img,cache=writeback,id='.
+Program terminated with signal 11, Segmentation fault.
+#0  0xb53399c0 in ?? ()
+(gdb) bt
+#0  0xb53399c0 in ?? ()
+Cannot access memory at address 0x28
+#1  0x0016d87e in cpu_tb_exec (
+    tb_ptr=0xc786fe90 <Address 0xc786fe90 out of bounds>, cpu=0x24450d8)
+    at /mnt/qemu/cpu-exec.c:67
+#2  cpu_arm_exec (env=<optimized out>) at /mnt/qemu/cpu-exec.c:642
+#3  0x00000000 in ?? ()
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1331859 b/results/classifier/gemma3:12b/kernel/1331859
new file mode 100644
index 00000000..9e487786
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1331859
@@ -0,0 +1,16 @@
+
+QEMU kernel panic on Windows with arithmetic syntax error
+
+During attempts to bring-up QEMU 64-bit ARM support I discovered a kernel panics that only occur on Windows but work properly on Linux.
+
+The issue can be reproduced by running the following command line:
+
+$ ./arm-softmmu/qemu-system-arm -M versatilepb -kernel $IMAGES/vmlinuz-3.2.0-4-versatile -initrd $IMAGES/initrd.img-3.2.0-4-versatile -hda $IMAGES/debian_wheezy_armel_standard.qcow2 -append "root=/dev/sda1"
+
+where $IMAGES is the location where the images are downloaded from http://people.debian.org/~aurel32/qemu/armel/.
+
+This was reproduced with both a custom built QEMU as well as the QEMU image installed by http://qemu.weilnetz.de/w32/qemu_w32-setup-20140617.exe.
+
+The same command line runs properly on Linux using a custom built QEMU.
+
+The Windows versions of QEMU do appear to work properly using the arm-test images available on qemu.org.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1340 b/results/classifier/gemma3:12b/kernel/1340
new file mode 100644
index 00000000..9fc2b6a4
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1340
@@ -0,0 +1,67 @@
+
+Static build fail with native aarch64 toolchain (ld failure at linking aarch64_be target)
+Description of problem:
+Do a static build on aarch64, with ArchlinuxARM native toolchain (gcc 12.1.0, binutils 2.38)
+Steps to reproduce:
+Do a static build using the following configs:
+
+```
+./configure \
+      --prefix=/usr \
+      --sysconfdir=/etc \
+      --libexecdir=/usr/lib/qemu \
+      --enable-attr \
+      --enable-linux-user \
+      --enable-tcg \
+      --disable-bpf \
+      --disable-bsd-user \
+      --disable-capstone \
+      --disable-docs \
+      --disable-fdt \
+      --disable-gcrypt \
+      --disable-glusterfs \
+      --disable-gnutls \
+      --disable-gtk \
+      --disable-install-blobs \
+      --disable-kvm \
+      --disable-libiscsi \
+      --disable-libnfs \
+      --disable-libssh \
+      --disable-linux-io-uring \
+      --disable-nettle \
+      --disable-opengl \
+      --disable-qom-cast-debug \
+      --disable-sdl \
+      --disable-system \
+      --disable-tools \
+      --disable-tpm \
+      --disable-vde \
+      --disable-vhost-crypto \
+      --disable-vhost-kernel \
+      --disable-vhost-net \
+      --disable-vhost-user \
+      --disable-vnc \
+      --disable-werror \
+      --disable-xen \
+      --disable-zstd \
+      --static
+```
+
+The build failure looks like this:
+
+```
+[466/2962] Linking target qemu-aarch64_be
+FAILED: qemu-aarch64_be
+c++  -o qemu-aarch64_be libcommon.fa.p/hw_core_cpu-common.c.o libcommon.fa.p/hw_core_machine-smp.c.o libcommon.fa.p/cpus-common.c.o libcommon.fa.p/page-vary-common.c.o libcommon.fa.p/accel_accel-user.c.o libcommon.fa.p/common-user_safe-syscall.S.o libcommon.fa.p/common-user_safe-syscall-error.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_aarch64_signal.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_aarch64_cpu_loop.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_cpu.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_crypto_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_debug_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_gdbstub.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_iwmmxt_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_m_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_mve_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_neon_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_op_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_tlb_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate-m-nocp.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate-mve.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate-neon.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate-vfp.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_vec_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_vfp_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_cpu_tcg.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_kvm-stub.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_cpu64.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_gdbstub64.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_helper-a64.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_mte_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_pauth_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_sve_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_sme_helper.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate-a64.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate-sve.c.o libqemu-aarch64_be-linux-user.fa.p/target_arm_translate-sme.c.o libqemu-aarch64_be-linux-user.fa.p/trace_control-target.c.o libqemu-aarch64_be-linux-user.fa.p/cpu.c.o libqemu-aarch64_be-linux-user.fa.p/disas.c.o libqemu-aarch64_be-linux-user.fa.p/gdbstub.c.o libqemu-aarch64_be-linux-user.fa.p/page-vary.c.o libqemu-aarch64_be-linux-user.fa.p/semihosting_guestfd.c.o libqemu-aarch64_be-linux-user.fa.p/semihosting_syscalls.c.o libqemu-aarch64_be-linux-user.fa.p/semihosting_arm-compat-semi.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_optimize.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_region.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_tcg.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_tcg-common.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_tcg-op.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_tcg-op-gvec.c.o libqemu-aarch64_be-linux-user.fa.p/tcg_tcg-op-vec.c.o libqemu-aarch64_be-linux-user.fa.p/fpu_softfloat.c.o libqemu-aarch64_be-linux-user.fa.p/accel_accel-common.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_tcg-all.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_cpu-exec-common.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_cpu-exec.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_tcg-runtime-gvec.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_tcg-runtime.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_translate-all.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_translator.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_user-exec.c.o libqemu-aarch64_be-linux-user.fa.p/accel_tcg_user-exec-stub.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_elfload.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_exit.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_fd-trans.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_linuxload.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_main.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_mmap.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_signal.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_strace.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_syscall.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_thunk.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_uaccess.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_uname.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_flatload.c.o libqemu-aarch64_be-linux-user.fa.p/linux-user_semihost.c.o libqemu-aarch64_be-linux-user.fa.p/meson-generated_.._aarch64_be-linux-user-gdbstub-xml.c.o -Wl,--as-needed -Wl,--no-undefined -pie -Wl,--whole-archive libhwcore.fa libqom.fa -Wl,--start-group libevent-loop-base.a -Wl,--no-whole-archive -Wl,--warn-common -Wl,-z,relro -Wl,-z,now -static-pie -fstack-protector-strong -march=armv8-a -O2 -pipe -fstack-protector-strong -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -Wp,-D_GLIBCXX_ASSERTIONS -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now libqemuutil.a libhwcore.fa libqom.fa /usr/lib/libz.a -lrt -lm -pthread -lgthread-2.0 -lglib-2.0 -lpcre2-8 -lsysprof-capture-4 -lstdc++ -Wl,--end-group
+/usr/bin/ld: /usr/lib/gcc/aarch64-unknown-linux-gnu/12.1.0/../../../../lib/libglib-2.0.a(gutils.c.o): in function `g_get_user_database_entry':
+(.text+0x324): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
+/usr/bin/ld: (.text+0xf4): warning: Using 'getpwnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
+/usr/bin/ld: (.text+0xe0): warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
+/usr/lib/gcc/aarch64-unknown-linux-gnu/12.1.0/../../../../lib/libc.a(init-first.o): in function `__libc_init_first':
+(.text+0x10): relocation truncated to fit: R_AARCH64_LD64_GOTPAGE_LO15 against symbol `__environ' defined in .bss section in /usr/lib/gcc/aarch64-unknown-linux-gnu/12.1.0/../../../../lib/libc.a(environ.o)
+/usr/bin/ld: (.text+0x10): warning: too many GOT entries for -fpic, please recompile with -fPIC
+collect2: error: ld returned 1 exit status
+distcc[61410] ERROR: compile (null) on localhost failed
+```
+Additional information:
+Full [meson-log.txt](/uploads/05059722cb81b10bd9977a17fd51f048/meson-log.txt) and [config.log](/uploads/1cbd8a5fe5c48c3af83e1cbba6a89ce8/config.log)
diff --git a/results/classifier/gemma3:12b/kernel/1341 b/results/classifier/gemma3:12b/kernel/1341
new file mode 100644
index 00000000..2d1aca31
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1341
@@ -0,0 +1,79 @@
+
+Static build failure with clang (clang 14.0.6)
+Description of problem:
+Static build failure with redefinition of 'iovec'.
+
+The configure looks like this:
+
+```
+  export CC=clang
+  ../$pkgbase-$pkgver/configure \
+      --prefix=/usr \
+      --sysconfdir=/etc \
+      --libexecdir=/usr/lib/qemu \
+      --enable-attr \
+      --enable-linux-user \
+      --enable-tcg \
+      --disable-bpf \
+      --disable-bsd-user \
+      --disable-capstone \
+      --disable-docs \
+      --disable-fdt \
+      --disable-gcrypt \
+      --disable-glusterfs \
+      --disable-gnutls \
+      --disable-gtk \
+      --disable-install-blobs \
+      --disable-kvm \
+      --disable-libiscsi \
+      --disable-libnfs \
+      --disable-libssh \
+      --disable-linux-io-uring \
+      --disable-nettle \
+      --disable-opengl \
+      --disable-qom-cast-debug \
+      --disable-sdl \
+      --disable-system \
+      --disable-tools \
+      --disable-tpm \
+      --disable-vde \
+      --disable-vhost-crypto \
+      --disable-vhost-kernel \
+      --disable-vhost-net \
+      --disable-vhost-user \
+      --disable-vnc \
+      --disable-werror \
+      --disable-xen \
+      --disable-zstd \
+      --static
+```
+
+The compiling failure looks like this:
+```
+FAILED: libqom.fa.p/qom_object.c.o
+clang -Ilibqom.fa.p -I. -I../qemu-7.1.0 -Iqapi -Itrace -Iui/shader -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/sysprof-4 -fcolor-diagnostics -Wall -Winvalid-pch -std=gnu11 -O2 -g -isystem /home/adam/qemu-user-static/src/qemu-7.1.0/linux-headers -isystem linux-headers -iquote . -iquote /home/adam/qemu-user-static/src/qemu-7.1.0 -iquote /home/adam/qemu-user-static/src/qemu-7.1.0/include -iquote /home/adam/qemu-user-static/src/qemu-7.1.0/tcg/aarch64 -pthread -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wno-initializer-overrides -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-string-plus-int -Wno-typedef-redefinition -Wno-tautological-type-limit-compare -Wno-psabi -Wno-missing-braces -march=armv8-a -O2 -pipe -fstack-protector-strong -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fPIE -MD -MQ libqom.fa.p/qom_object.c.o -MF libqom.fa.p/qom_object.c.o.d -o libqom.fa.p/qom_object.c.o -c ../qemu-7.1.0/qom/object.c
+distcc[94580] (dcc_build_somewhere) Warning: failed to distribute, running locally instead
+clang-14: warning: argument unused during compilation: '-fstack-clash-protection' [-Wunused-command-line-argument]
+In file included from ../qemu-7.1.0/qom/object.c:13:
+/home/adam/qemu-user-static/src/qemu-7.1.0/include/qemu/osdep.h:517:8: error: redefinition of 'iovec'
+struct iovec {
+       ^
+/usr/include/bits/types/struct_iovec.h:26:8: note: previous definition is here
+struct iovec
+       ^
+In file included from ../qemu-7.1.0/qom/object.c:13:
+/home/adam/qemu-user-static/src/qemu-7.1.0/include/qemu/osdep.h:524:9: warning: 'IOV_MAX' macro redefined [-Wmacro-redefined]
+#define IOV_MAX 1024
+        ^
+/usr/include/bits/xopen_lim.h:66:10: note: previous definition is here
+# define IOV_MAX __IOV_MAX
+         ^
+1 warning and 1 error generated.
+distcc[94580] ERROR: compile ../qemu-7.1.0/qom/object.c on localhost failed
+ninja: build stopped: subcommand failed.
+```
+Steps to reproduce:
+1. Compile qemu using above configure and use clang as the compiler
+Additional information:
+Full meson log:
+[meson-log.txt](/uploads/a63d609852148140e8fa7210c6912982/meson-log.txt)
diff --git a/results/classifier/gemma3:12b/kernel/1349277 b/results/classifier/gemma3:12b/kernel/1349277
new file mode 100644
index 00000000..86aa055a
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1349277
@@ -0,0 +1,18 @@
+
+AArch64 emulation ignores SPSel=0 when taking (or returning from) an exception at EL1 or greater
+
+The AArch64 emulation ignores SPSel=0 when:
+
+(1) taking an interrupt from an exception level greater than EL0 (e.g., EL1t),
+
+(2) returning from an exception (via ERET) to an exception level greater than EL0 (e.g., EL1t), with SPSR_ELx[SPSel]=0.
+
+The attached patch fixes the problem in my application.
+
+Background:
+
+I'm running a standalone application (toy OS) that is performing preemptive multithreading between threads running at EL1t, with exception handling / context switching occurring at EL1h.  This bug causes the stack pointer to be corrupted in the threads running at EL1t (they end up with a version of the EL1h stack pointer (SP_EL1)).
+
+Occurs in:
+	qemu-2.1.0-rc1 (found in)
+	commit c60a57ff497667780132a3fcdc1500c83af5d5c0 (current master)
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/135 b/results/classifier/gemma3:12b/kernel/135
new file mode 100644
index 00000000..b2381be5
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/135
@@ -0,0 +1,2 @@
+
+Cant compile qemu from source, get error about static declaration of memfd_create following non-static declaration
diff --git a/results/classifier/gemma3:12b/kernel/1351 b/results/classifier/gemma3:12b/kernel/1351
new file mode 100644
index 00000000..0bff6191
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1351
@@ -0,0 +1,6 @@
+
+qemu-system-x86_64  run win7 qcow2 got an exception
+Description of problem:
+when qemu-system-X86-64 run the win7 qcow2,  qemu got an exception
+
+\*\* ERROR:../target/i386/tcg/sysemu/excp_helper.c:517:raise_stage2: code should not be reached Aborted (核心已转储)
diff --git a/results/classifier/gemma3:12b/kernel/1359383 b/results/classifier/gemma3:12b/kernel/1359383
new file mode 100644
index 00000000..0049aba9
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1359383
@@ -0,0 +1,208 @@
+
+kernel panic at smpboot.c:134 when rebooting qemu with multiple cores
+
+Hi all,
+
+I can reproduce this with kernel 3.14 and 3.17rc1. I suspect it is a qemu issue, but I'm not sure. The test case is the following script:
+
+qemu-system-x86_64 -machine accel=kvm -pidfile /tmp/pid$$ -m 512M -smp 8,sockets=8 -kernel vmlinuz -append "init=/sbin/reboot -f console=ttyS0,115200 kgdboc=ttyS2,115200 root=/dev/sda rw" -nographic -serial stdio -drive format=raw,snapshot=on,file=/var/lib/ktest/root 
+
+Note that we pass /sbin/reboot as the init program so it just reboots forever. After a dozen or so iterations, I hit this:
+
+[    0.000000] Initializing cgroup subsys cpuset
+[    0.000000] Initializing cgroup subsys cpu
+[    0.000000] Initializing cgroup subsys cpuacct
+[    0.000000] Linux version 3.17.0-rc1-0-2014.sp (sp@vodka) (gcc version 4.8.2 20140120 (Red Hat 4.8.2-16) (GCC) ) #209 SMP Wed Aug 20 20:17:46 UTC 2014
+[    0.000000] Command line: init=/sbin/reboot -f console=ttyS0,115200 kgdboc=ttyS2,115200 root=/dev/sda rw ktest.priority=9
+[    0.000000] e820: BIOS-provided physical RAM map:
+[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
+[    0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
+[    0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
+[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000001fffcfff] usable
+[    0.000000] BIOS-e820: [mem 0x000000001fffd000-0x000000001fffffff] reserved
+[    0.000000] BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved
+[    0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
+[    0.000000] process: using polling idle threads
+[    0.000000] NX (Execute Disable) protection: active
+[    0.000000] SMBIOS 2.4 present.
+[    0.000000] Hypervisor detected: KVM
+[    0.000000] e820: last_pfn = 0x1fffd max_arch_pfn = 0x400000000
+[    0.000000] PAT not supported by CPU.
+[    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
+[    0.000000] init_memory_mapping: [mem 0x1fc00000-0x1fdfffff]
+[    0.000000] init_memory_mapping: [mem 0x1c000000-0x1fbfffff]
+[    0.000000] init_memory_mapping: [mem 0x00100000-0x1bffffff]
+[    0.000000] init_memory_mapping: [mem 0x1fe00000-0x1fffcfff]
+[    0.000000] ACPI: Early table checksum verification disabled
+[    0.000000] ACPI: RSDP 0x00000000000F0A90 000014 (v00 BOCHS )
+[    0.000000] ACPI: RSDT 0x000000001FFFFC21 000034 (v01 BOCHS  BXPCRSDT 00000001 BXPC 00000001)
+[    0.000000] ACPI: FACP 0x000000001FFFEF40 000074 (v01 BOCHS  BXPCFACP 00000001 BXPC 00000001)                                                                                               
+[    0.000000] ACPI: DSDT 0x000000001FFFDDC0 001180 (v01 BOCHS  BXPCDSDT 00000001 BXPC 00000001)                                                                                               
+[    0.000000] ACPI: FACS 0x000000001FFFDD80 000040                                                                                                                                            
+[    0.000000] ACPI: SSDT 0x000000001FFFEFB4 000B85 (v01 BOCHS  BXPCSSDT 00000001 BXPC 00000001)                                                                                               
+[    0.000000] ACPI: APIC 0x000000001FFFFB39 0000B0 (v01 BOCHS  BXPCAPIC 00000001 BXPC 00000001)                                                                                               
+[    0.000000] ACPI: HPET 0x000000001FFFFBE9 000038 (v01 BOCHS  BXPCHPET 00000001 BXPC 00000001)                                                                                               
+[    0.000000] No NUMA configuration found                                                                                                                                                     
+[    0.000000] Faking a node at [mem 0x0000000000000000-0x000000001fffcfff]                                                                                                                    
+[    0.000000] Initmem setup node 0 [mem 0x00000000-0x1fffcfff]                                                                                                                                
+[    0.000000]   NODE_DATA [mem 0x1fffa000-0x1fffcfff]                                                                                                                                         
+[    0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00                                                                                                                                     
+[    0.000000] kvm-clock: cpu 0, msr 0:1fff9001, primary cpu clock                                                                                                                             
+[    0.000000] Zone ranges:                                                                                                                                                                    
+[    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
+[    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
+[    0.000000]   Normal   empty
+[    0.000000] Movable zone start for each node
+[    0.000000] Early memory node ranges
+[    0.000000]   node   0: [mem 0x00001000-0x0009efff]
+[    0.000000]   node   0: [mem 0x00100000-0x1fffcfff]
+[    0.000000] ACPI: PM-Timer IO Port: 0xb008
+[    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
+[    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
+[    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
+[    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
+[    0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] enabled)
+[    0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] enabled)
+[    0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] enabled)
+[    0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled)
+[    0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
+[    0.000000] ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
+[    0.000000] IOAPIC[0]: apic_id 0, version 17, address 0xfec00000, GSI 0-23
+[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
+[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
+[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
+[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
+[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
+[    0.000000] Using ACPI (MADT) for SMP configuration information
+[    0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
+[    0.000000] smpboot: Allowing 8 CPUs, 0 hotplug CPUs
+[    0.000000] e820: [mem 0x20000000-0xfeffbfff] available for PCI devices
+[    0.000000] Booting paravirtualized kernel on KVM
+[    0.000000] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:8 nr_node_ids:1
+[    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88001fc00000 s80064 r8192 d22336 u262144
+[    0.000000] KVM setup async PF for cpu 0
+[    0.000000] kvm-stealtime: cpu 0, msr 1fc0d000
+[    0.000000] Built 1 zonelists in Node order, mobility grouping on.  Total pages: 128902
+[    0.000000] Policy zone: DMA32
+[    0.000000] Kernel command line: mlx4_core.port_type_array=2,2 intel_idle.max_cstate=0 processor.max_cstate=1 idle=poll init=/sbin/reboot -f console=ttyS0,115200 kgdboc=ttyS2,115200 root=/dev/sda rw ktest.priority=9
+[    0.000000] PID hash table entries: 2048 (order: 2, 16384 bytes)
+[    0.000000] Memory: 497836K/523884K available (6197K kernel code, 845K rwdata, 2312K rodata, 968K init, 2676K bss, 26048K reserved)
+[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
+[    0.000000] Hierarchical RCU implementation.
+[    0.000000]  RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=8.
+[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
+[    0.000000] NR_IRQS:4352 nr_irqs:488 0
+[    0.000000] Console: colour VGA+ 80x25
+[    0.000000] console [ttyS0] enabled
+[    0.000000] tsc: Detected 3491.912 MHz processor
+[    0.008000] Calibrating delay loop (skipped) preset value.. 6983.82 BogoMIPS (lpj=13967648)
+[    0.008000] pid_max: default: 32768 minimum: 301
+[    0.008000] ACPI: Core revision 20140724
+[    0.008000] ACPI: All ACPI Tables successfully acquired
+[    0.008000] Security Framework initialized
+[    0.008000] Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
+[    0.008000] Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
+[    0.008000] Mount-cache hash table entries: 1024 (order: 1, 8192 bytes)
+[    0.008000] Mountpoint-cache hash table entries: 1024 (order: 1, 8192 bytes)
+[    0.008106] Initializing cgroup subsys devices
+[    0.008379] Initializing cgroup subsys freezer
+[    0.008647] Initializing cgroup subsys net_cls
+[    0.008913] Initializing cgroup subsys blkio
+[    0.009169] Initializing cgroup subsys perf_event
+[    0.009486] mce: CPU supports 10 MCE banks
+[    0.009759] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
+[    0.009759] Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0, 1GB 0
+[    0.010597] Freeing SMP alternatives memory: 28K (ffffffff81dc7000 - ffffffff81dce000)
+[    0.013902] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
+[    0.014366] smpboot: CPU0: Intel QEMU Virtual CPU version 2.0.0 (fam: 06, model: 06, stepping: 03)
+[    0.016000] Performance Events: Broken PMU hardware detected, using software events only.
+[    0.016000] Failed to access perfctr msr (MSR c1 is 0)
+[    0.016000] NMI watchdog: disabled (cpu0): hardware events not enabled
+[    0.016000] x86: Booting SMP configuration:
+[    0.016000] .... node  #0, CPUs:      #1
+[    0.008000] kvm-clock: cpu 1, msr 0:1fff9041, secondary cpu clock
+[    0.028010] KVM setup async PF for cpu 1
+[    0.028358]  #2
+[    0.028358] kvm-stealtime: cpu 1, msr 1fc4d000
+[    0.008000] kvm-clock: cpu 2, msr 0:1fff9081, secondary cpu clock
+[    0.044008] KVM setup async PF for cpu 2
+[    0.044506]  #3
+[    0.044507] kvm-stealtime: cpu 2, msr 1fc8d000
+[    0.008000] kvm-clock: cpu 3, msr 0:1fff90c1, secondary cpu clock
+[    0.060011] KVM setup async PF for cpu 3
+[    0.060416]  #4
+[    0.060416] kvm-stealtime: cpu 3, msr 1fccd000
+[    0.008000] kvm-clock: cpu 4, msr 0:1fff9101, secondary cpu clock
+[    0.072010] KVM setup async PF for cpu 4
+[    0.072461]  #5
+[    0.072461] kvm-stealtime: cpu 4, msr 1fd0d000
+[    0.008000] kvm-clock: cpu 5, msr 0:1fff9141, secondary cpu clock
+[    0.088001] KVM setup async PF for cpu 5
+[    0.088001]  #6
+[    0.088001] kvm-stealtime: cpu 5, msr 1fd4d000
+[    0.008000] kvm-clock: cpu 6, msr 0:1fff9181, secondary cpu clock
+[    0.108008] ------------[ cut here ]------------
+[    0.108366] WARNING: CPU: 0 PID: 1 at /src/linux-bcache/kernel/workqueue.c:4473 workqueue_cpu_up_callback+0x36e/0x380()
+[    0.109172] Modules linked in:
+[    0.109419] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.17.0-rc1-0-2014.sp #209
+[    0.112001] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
+[    0.112606]  0000000000000009 ffff88001e927db8 ffffffff81601466 0000000000000000
+[    0.113208]  ffff88001e927df0 ffffffff810b4bb8 ffff88001fd92400 ffff88001fd92730
+[    0.113813]  ffff88001fd92708 0000000000000006 ffff88001ea92540 ffff88001e927e00
+[    0.114422] Call Trace:
+[    0.114616]  [<ffffffff81601466>] dump_stack+0x45/0x56
+[    0.115011]  [<ffffffff810b4bb8>] warn_slowpath_common+0x78/0xa0
+[    0.115474]  [<ffffffff810b4c95>] warn_slowpath_null+0x15/0x20
+[    0.116002]  [<ffffffff810cca2e>] workqueue_cpu_up_callback+0x36e/0x380
+[    0.116507]  [<ffffffff810d0f5c>] notifier_call_chain+0x4c/0x70
+[    0.116962]  [<ffffffff810d1059>] __raw_notifier_call_chain+0x9/0x10
+[    0.117458]  [<ffffffff810b4dee>] cpu_notify+0x1e/0x40
+[    0.117857]  [<ffffffff810b5006>] cpu_up+0x186/0x1b0
+[    0.118249]  [<ffffffff81d06272>] smp_init+0x63/0x7d
+[    0.118633]  [<ffffffff81cea12e>] kernel_init_freeable+0xe9/0x200
+[    0.119114]  [<ffffffff815f99a0>] ? rest_init+0x80/0x80
+[    0.119524]  [<ffffffff815f99a9>] kernel_init+0x9/0xf0
+[    0.120002]  [<ffffffff816077bc>] ret_from_fork+0x7c/0xb0
+[    0.120443]  [<ffffffff815f99a0>] ? rest_init+0x80/0x80
+[    0.120867] ---[ end trace bac34f2af212d79e ]---
+[    0.121255] ------------[ cut here ]------------
+[    0.121243] KVM setup async PF for cpu 6
+[    0.121243] kvm-stealtime: cpu 6, msr 1fd8d000
+[    0.122309] kernel BUG at /src/linux-bcache/kernel/smpboot.c:134!
+[    0.122799] invalid opcode: 0000 [#1] SMP
+[    0.123150] Modules linked in:
+[    0.123406] CPU: 0 PID: 36 Comm: watchdog/6 Tainted: G        W      3.17.0-rc1-0-2014.sp #209
+[    0.124000] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
+[    0.124000] task: ffff88001eb00000 ti: ffff88001eb08000 task.ti: ffff88001eb08000
+[    0.124000] RIP: 0010:[<ffffffff810d390f>]  [<ffffffff810d390f>] smpboot_thread_fn+0x19f/0x1b0
+[    0.124000] RSP: 0000:ffff88001eb0be88  EFLAGS: 00010206
+[    0.124000] RAX: 0000000000000000 RBX: ffff88001eb00000 RCX: 0000000000000000
+[    0.124000] RDX: ffff88001eb0bfd8 RSI: ffff88001eb00000 RDI: 0000000000000006
+[    0.124000] RBP: ffff88001eb0bec8 R08: ffff88001eb08000 R09: ffff88001eb01a89
+[    0.124000] R10: 0000000000000010 R11: 0000000000000001 R12: ffff88001e801930
+[    0.124000] R13: ffffffff81c4b720 R14: ffff88001eb00000 R15: ffff88001eb00000
+[    0.124000] FS:  0000000000000000(0000) GS:ffff88001fc00000(0000) knlGS:0000000000000000
+[    0.124000] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
+[    0.124000] CR2: 00000000ffffffff CR3: 0000000001c14000 CR4: 00000000000006f0
+[    0.124000] Stack:
+[    0.124000]  0000000000000000 ffff88001eb0bea0 ffffffff81603714 ffff88001e90bb00
+[    0.124000]  ffff88001e801930 ffffffff810d3770 0000000000000000 0000000000000000
+[    0.124000]  ffff88001eb0bf48 ffffffff810d00cd 0000000000000001 0000000000000006
+[    0.124000] Call Trace:
+[    0.124000]  [<ffffffff81603714>] ? schedule+0x24/0x70
+[    0.124000]  [<ffffffff810d3770>] ? SyS_setgroups+0x190/0x190
+[    0.124000]  [<ffffffff810d00cd>] kthread+0xcd/0xf0
+[    0.124000]  [<ffffffff810d0000>] ? kthread_create_on_node+0x170/0x170
+[    0.124000]  [<ffffffff816077bc>] ret_from_fork+0x7c/0xb0
+[    0.124000]  [<ffffffff810d0000>] ? kthread_create_on_node+0x170/0x170
+[    0.124000] Code: 89 fa 48 0f a3 11 19 d2 31 f6 85 d2 40 0f 95 c6 ff d0 4c 89 e7 e8 82 16 0f 00 48 83 c4 18 31 c0 5b 41 5c 41 5d 41 5e 41 5f 5d c3 <0f> 0b 0f 0b 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 89 d0 55 48
+[    0.124000] RIP  [<ffffffff810d390f>] smpboot_thread_fn+0x19f/0x1b0
+[    0.124000]  RSP <ffff88001eb0be88>
+[    0.124002] ---[ end trace bac34f2af212d79f ]---
+[    0.124456] Kernel panic - not syncing: Fatal exception
+[    0.128000] Shutting down cpus with NMI
+[    0.128000] ---[ end Kernel panic - not syncing: Fatal exception
+
+Note there's an SMP-related warning coming out of workqueue.c right before the panic.
+
+I have attached the .config I'm using with the kernel.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1361 b/results/classifier/gemma3:12b/kernel/1361
new file mode 100644
index 00000000..4019ff6a
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1361
@@ -0,0 +1,21 @@
+
+ppc64le linux user emulation w/ 64KiB pages seems broken since v5.0.0
+Description of problem:
+[Our (snmalloc's)](https://github.com/microsoft/snmalloc) CI includes running a PowerPC64 little-endian Linux build inside qemu, running with 64KiB pages as, at least, Debian runs them by default.  As reported [over there](https://github.com/microsoft/snmalloc/issues/576), this broke when GitHub's CI runners moved from Ubuntu Focal (20.04) to Jammy (22.04), bringing qemu from v4.2 to v6.2.
+
+The failing test case appears to die of an erroneous `SIGSEGV` `SEGV_MAPERR`:
+```
+--- SIGSEGV {si_signo=SIGSEGV, si_code=1, si_addr=0x0000004001be5000} ---
+```
+despite that address nominally being mapped by the last memory syscall to touch that area
+```
+openat(AT_FDCWD,"/usr/powerpc64le-linux-gnu/lib/libstdc++.so.6",O_RDONLY|O_CLOEXEC) = 4
+[...]
+mmap(0x0000004001bd0000,131072,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_DENYWRITE|MAP_FIXED,4,0x2f0000) = 0x4001bd0000
+```
+
+Bisection reveals that the breakage first occurred with 4dcf078f094d436866ef793aa25c96fba85ac8d0, though I suspect this is merely the commit that exposes some underlying bug rather than being the actual root cause.
+Steps to reproduce:
+Run a ppc64el Linux executable under `qemu-user` with `-p 65536`.
+Additional information:
+Please advise what more would be useful.
diff --git a/results/classifier/gemma3:12b/kernel/1361912 b/results/classifier/gemma3:12b/kernel/1361912
new file mode 100644
index 00000000..c9871715
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1361912
@@ -0,0 +1,10 @@
+
+qemu-mips64 Segmentation fault
+
+When I ran qemu-mips64 for any mips 64 executable , I got this error:
+
+$ ./qemu-mips64  ../lang
+qemu: uncaught target signal 11 (Segmentation fault) - core dumped
+Segmentation fault (core dumped)
+
+Is this a known issue?
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1362635 b/results/classifier/gemma3:12b/kernel/1362635
new file mode 100644
index 00000000..0da1b419
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1362635
@@ -0,0 +1,43 @@
+
+bdrv_read co-routine re-entered recursively
+
+calling bdrv_read in a loop leads to the follwing situation:
+
+bs->drv->bdrv_aio_readv is called, and finally calls bdrv_co_io_em_complete in other thread context.
+there is a possibility of calling bdrv_co_io_em_complete before calling qemu_coroutine_yield in bdrv_co_io_em. And qemu fails with "co-routine re-entered recursively".
+
+static void bdrv_co_io_em_complete(void *opaque, int ret)
+{
+    CoroutineIOCompletion *co = opaque;
+
+    co->ret = ret;
+    qemu_coroutine_enter(co->coroutine, NULL);
+}
+
+static int coroutine_fn bdrv_co_io_em(BlockDriverState *bs, int64_t sector_num,
+                                      int nb_sectors, QEMUIOVector *iov,
+                                      bool is_write)
+{
+    CoroutineIOCompletion co = {
+        .coroutine = qemu_coroutine_self(),
+    };
+    BlockDriverAIOCB *acb;
+
+    if (is_write) {
+        acb = bs->drv->bdrv_aio_writev(bs, sector_num, iov, nb_sectors,
+                                       bdrv_co_io_em_complete, &co);
+    } else {
+        acb = bs->drv->bdrv_aio_readv(bs, sector_num, iov, nb_sectors,
+                                      bdrv_co_io_em_complete, &co);
+    }
+
+    trace_bdrv_co_io_em(bs, sector_num, nb_sectors, is_write, acb);
+    if (!acb) {
+        return -EIO;
+    }
+    qemu_coroutine_yield();
+
+    return co.ret;
+}
+
+is it a bug, or may be I don't understand something?
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1363641 b/results/classifier/gemma3:12b/kernel/1363641
new file mode 100644
index 00000000..4e6c6a68
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1363641
@@ -0,0 +1,15 @@
+
+Build of v2.1.0 fails on armv7l due to undeclared __NR_select
+
+After `make clean` and `git clean -x -f -d` `git checkout v2.1.0 && configure --prefix=/home/user/prefix-qemu-2.1.0 && make` fails due to missing declarations
+
+    CC    qemu-seccomp.o
+    qemu-seccomp.c:28:1: error: '__NR_select' undeclared here (not in a function)
+    qemu-seccomp.c:36:1: error: '__NR_mmap' undeclared here (not in a function)
+    qemu-seccomp.c:57:1: error: '__NR_getrlimit' undeclared here (not in a function)
+    qemu-seccomp.c:96:1: error: '__NR_time' undeclared here (not in a function)
+      GEN   qmp-marshal.c
+    qemu-seccomp.c:186:1: error: '__NR_alarm' undeclared here (not in a function)
+    make: *** [qemu-seccomp.o] Error 1
+
+Same errors for master 8b3030114a449e66c68450acaac4b66f26d91416. `configure`should not succeed for a failing build. `config.log` for v2.1.0 and 8b303011... attached. I'm building on a debian 7.6 chroot on Synology DSM 5.0. `uname -a` says `Linux diskstatation 3.2.40 #4493 SMP Thu Aug 21 21:43:02 CST 2014 armv7l GNU/Linux`.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1383857 b/results/classifier/gemma3:12b/kernel/1383857
new file mode 100644
index 00000000..783332a6
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1383857
@@ -0,0 +1,18 @@
+
+aarch64: virtio disks don't show up in guest (neither blk nor scsi)
+
+kernel-3.18.0-0.rc1.git0.1.rwmj5.fc22.aarch64 (3.18 rc1 + some hardware enablement)
+qemu from git today
+
+When I create a guest with virtio-scsi disks, they don't show up inside the guest.
+Literally after the virtio_mmio.ko and virtio_scsi.ko modules are loaded, there are
+no messages about disks, and of course nothing else works.
+
+Really long command line (generated by libvirt):
+
+HOME=/home/rjones USER=rjones LOGNAME=rjones QEMU_AUDIO_DRV=none TMPDIR=/home/rjones/d/libguestfs/tmp /home/rjones/d/qemu/aarch64-softmmu/qemu-system-aarch64 -name guestfs-oqv29um3jp03kpjf -S -machine virt,accel=tcg,usb=off -cpu cortex-a57 -m 500 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid a5f1a15d-2bc7-46df-9974-1d1f643b2449 -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/home/rjones/.config/libvirt/qemu/lib/guestfs-oqv29um3jp03kpjf.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-reboot -boot strict=on -kernel /home/rjones/d/libguestfs/tmp/.guestfs-1000/appliance.d/kernel -initrd /home/rjones/d/libguestfs/tmp/.guestfs-1000/appliance.d/initrd -append panic=1 console=ttyAMA0 earlyprintk=pl011,0x9000000 ignore_loglevel efi-rtc=noprobe udevtimeout=6000 udev.event-timeout=6000 no_timer_check lpj=500000 acpi=off printk.time=1 cgroup_disable=memory root=/dev/sdb selinux=0 guestfs_verbose=1 TERM=xterm-256color -device virtio-scsi-device,id=scsi0 -device virtio-serial-device,id=virtio-serial0 -usb -drive file=/home/rjones/d/libguestfs/tmp/libguestfs4GxfQ9/scratch.1,if=none,id=drive-scsi0-0-0-0,format=raw,cache=unsafe -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=/home/rjones/d/libguestfs/tmp/libguestfs4GxfQ9/overlay2,if=none,id=drive-scsi0-0-1-0,format=qcow2,cache=unsafe -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=1,lun=0,drive=drive-scsi0-0-1-0,id=scsi0-0-1-0 -serial unix:/home/rjones/d/libguestfs/tmp/libguestfs4GxfQ9/console.sock -chardev socket,id=charchannel0,path=/home/rjones/d/libguestfs/tmp/libguestfs4GxfQ9/guestfsd.sock -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.libguestfs.channel.0 -msg timestamp=on
+
+There are no kernel messages about the disks, they just are not seen.
+
+Worked with kernel 3.16 so I suspect this could be a kernel bug rather than a
+qemu bug, but I've no idea where to report those.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1398 b/results/classifier/gemma3:12b/kernel/1398
new file mode 100644
index 00000000..f300e72d
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1398
@@ -0,0 +1,7 @@
+
+Kernel Fault in primary space mode while using user ASCE emulating s390x with AlmaLinux release 9.1 (Lime Lynx)
+Description of problem:
+Happens twice during startup, however the system keeps running.
+Steps to reproduce:
+1. Install Alma Linux s390x on in KVM on x86_64
+2. Start KVM
diff --git a/results/classifier/gemma3:12b/kernel/1399 b/results/classifier/gemma3:12b/kernel/1399
new file mode 100644
index 00000000..b60e7410
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1399
@@ -0,0 +1,73 @@
+
+Early faults when direct booting large Linux kernel images on x86_64 and aarch64 guests.
+Description of problem:
+When attempting to load a Linux kernel image for direct boot via the `-kernel` command line option, a triple fault occurs shortly after attempting to hand off execution to the kernel if the kernel image is ‘large’ in size (this can be easily reproduced with a custom kernel build by embedding an initramfs in the kernel that includes a few large but mostly incompressible files). I’m not certain of the exact cutoff, but a 75 MB kernel image on x86_64, and a 67 MB kernel image on AArch64 both exhibit the issue, while a 13 MB kernel image on x86_64 does not.
+Steps to reproduce:
+1. Attempt to direct boot an exceptionally large kernel image as an x86_64 or aarch64 guest.
+Additional information:
+I have not yet been able to track down exactly where the initial fault is happening, and am not even certain that it’s in Linux’s early boot code, but the fact that this is reproducible across multiple architectures and is unaffected by things like KASLR and the exact compression algorithm for the guest kernel suggests to me that it’s more likely to be an issue in QEMU’s loader code for direct kernel boot than in the Linux kernel itself.
+
+Running on x86_64, the initial fault appears to be a general protection fault, followed by a double and then triple fault. Output from running QEMU as above with `-d int,guest_error -no-reboot’:
+
+```
+check_exception old: 0xffffffff new 0xd
+     0: v=0d e=0000 i=0 cpl=0 IP=0010:000000000789f7f0 pc=000000000789f7f0 SP=0018:00000000078e6fd8 env->regs[R_EAX]=0000000000000000
+RAX=0000000000000000 RBX=6fb84fe3052f53e2 RCX=00000000fb600000 RDX=00000000078fbed0
+RSI=00000000078f6000 RDI=00000000078e80e0 RBP=00000000078e80e0 RSP=00000000078e6fd8
+R8 =00000000078fb000 R9 =00000000fb600000 R10=000fffffffe00000 R11=0000000000000000
+R12=0000000000000000 R13=0000000000000000 R14=0000000000000000 R15=0000000000000000
+RIP=000000000789f7f0 RFL=00000006 [-----P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
+ES =0000 0000000000000000 00000000 00000000
+CS =0010 0000000000000000 ffffffff 00af9a00 DPL=0 CS64 [-R-]
+SS =0018 0000000000000000 ffffffff 00cf9300 DPL=0 DS   [-WA]
+DS =0018 0000000000000000 ffffffff 00cf9300 DPL=0 DS   [-WA]
+FS =0000 0000000000000000 00000000 00000000
+GS =0000 0000000000000000 00000000 00000000
+LDT=0000 0000000000000000 00000000 00008200 DPL=0 LDT
+TR =0020 0000000000000000 00000fff 00808900 DPL=0 TSS64-avl
+GDT=     00000000078b1030 0000002f
+IDT=     00000000078b1070 000001ff
+CR0=80050033 CR2=6fb84fe3052f53ee CR3=00000000078f6000 CR4=00000020
+DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
+DR6=00000000ffff0ff0 DR7=0000000000000400
+CCS=0000000000000018 CCD=6fb84fe3052f53e2 CCO=LOGICQ
+EFER=0000000000000500
+check_exception old: 0xd new 0xd
+     1: v=08 e=0000 i=0 cpl=0 IP=0010:000000000789f7f0 pc=000000000789f7f0 SP=0018:00000000078e6fd8 env->regs[R_EAX]=0000000000000000
+RAX=0000000000000000 RBX=6fb84fe3052f53e2 RCX=00000000fb600000 RDX=00000000078fbed0
+RSI=00000000078f6000 RDI=00000000078e80e0 RBP=00000000078e80e0 RSP=00000000078e6fd8
+R8 =00000000078fb000 R9 =00000000fb600000 R10=000fffffffe00000 R11=0000000000000000
+R12=0000000000000000 R13=0000000000000000 R14=0000000000000000 R15=0000000000000000
+RIP=000000000789f7f0 RFL=00000006 [-----P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
+ES =0000 0000000000000000 00000000 00000000
+CS =0010 0000000000000000 ffffffff 00af9a00 DPL=0 CS64 [-R-]
+SS =0018 0000000000000000 ffffffff 00cf9300 DPL=0 DS   [-WA]
+DS =0018 0000000000000000 ffffffff 00cf9300 DPL=0 DS   [-WA]
+FS =0000 0000000000000000 00000000 00000000
+GS =0000 0000000000000000 00000000 00000000
+LDT=0000 0000000000000000 00000000 00008200 DPL=0 LDT
+TR =0020 0000000000000000 00000fff 00808900 DPL=0 TSS64-avl
+GDT=     00000000078b1030 0000002f
+IDT=     00000000078b1070 000001ff
+CR0=80050033 CR2=6fb84fe3052f53ee CR3=00000000078f6000 CR4=00000020
+DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
+DR6=00000000ffff0ff0 DR7=0000000000000400
+CCS=0000000000000018 CCD=6fb84fe3052f53e2 CCO=LOGICQ
+EFER=0000000000000500
+check_exception old: 0x8 new 0xd
+```
+
+Running on AArch64, the emulated CPU gets stuck in a loop trying to handle ‘exception 5’, showing the following output when run as above with `-d int, guest_error -no-reboot`, repeated infinitely until the emulator gets killed:
+
+```
+Taking exception 5 [IRQ] on CPU 0
+...from EL1 to EL1
+...with ESR 0x15/0x56000000
+...with ELR 0xffffffef0dee4098
+...to EL1 PC 0xffffffef0d810a80 PSTATE 0x3c5
+Exception return from AArch64 EL1 to AArch64 EL1 PC 0xffffffef0dee4098
+```
+
+I have also attempted to reproduce this on 64-bit little-endian POWER using qemu-system-ppc64 and an equivalent kernel config, and was _not_ able to reproduce it there with a 69 MB kernel image.
+
+I can provide Linux kernel configs for the affected kernels upon request, but am not (currently) able to provide full system images (the project I was working on when I came across this is not yet public).
diff --git a/results/classifier/gemma3:12b/kernel/140 b/results/classifier/gemma3:12b/kernel/140
new file mode 100644
index 00000000..d617b56f
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/140
@@ -0,0 +1,2 @@
+
+linux-user clone() can't handle glibc posix_spawn() (causes locale-gen to assert)
diff --git a/results/classifier/gemma3:12b/kernel/1406016 b/results/classifier/gemma3:12b/kernel/1406016
new file mode 100644
index 00000000..368bacad
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1406016
@@ -0,0 +1,41 @@
+
+qemu-system-arm hangs at start on OS X
+
+Both from release 2.1.2 and built from a recent source, qemu-system-arm seems to hang on a mutex immediately after starting up, never getting to the point of actually booting. 
+
+I've tried qemu-system-mipsel with another image and it worked fine, so this seems to be specific to the ARM runtime. I've tried two different ARM kernels, and I also ran into this with QEMU 2.1.2 release, installed from a bottle using homebrew.
+
+Host: Mac OS X 10.9.5 (Darwin Kernel Version 13.4.0)
+QEMU version: built from HEAD@ab0302ee76
+Build command: ./configure --enable-cocoa --target-list=arm-softmmu,mipsel-softmmu && make
+Run command:
+
+qemu-system-arm -M vexpress-a9 -cpu cortex-a9 -m 256 -sd disk.img -net nic,macaddr=52:54:00:fa:ce:13 -kernel vmlinuz-3.2.0-4-vexpress -initrd initrd.gz -append "root=/dev/ram" -display vnc=localhost:17 -net user,hostfwd=tcp::5022-:22 -append "console=ttyS0"
+
+I also tried this, with a different kernel & root:
+
+qemu-system-arm -kernel zImage -cpu arm1176 -m 256 -M versatilepb -no-reboot -serial stdio -hda rootfs-chromium.ext2 -append "root=/dev/sda"
+
+Thread dump:
+
+(lldb) thread list
+Process 34364 stopped
+* thread #1: tid = 0x135966, 0x00007fff89f4a746 libsystem_kernel.dylib`__psynch_mutexwait + 10, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP
+  thread #2: tid = 0x13598b, 0x00007fff89f4ae6a libsystem_kernel.dylib`__workq_kernreturn + 10
+  thread #3: tid = 0x13598c, 0x00007fff89f4b662 libsystem_kernel.dylib`kevent64 + 10, queue = 'com.apple.libdispatch-manager'
+  thread #7: tid = 0x1359b2, 0x00007fff89f4acc2 libsystem_kernel.dylib`__sigwait + 10
+  thread #9: tid = 0x1359c1, 0x00000001091bc5d9
+  thread #11: tid = 0x1359cc, 0x00007fff89f4a716 libsystem_kernel.dylib`__psynch_cvwait + 10
+  thread #12: tid = 0x1359da, 0x00007fff89f46a1a libsystem_kernel.dylib`mach_msg_trap + 10, name = 'com.apple.audio.IOThread.client'
+
+-------
+* thread #1: tid = 0x135966, 0x00007fff89f4a746 libsystem_kernel.dylib`__psynch_mutexwait + 10, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP
+  * frame #0: 0x00007fff89f4a746 libsystem_kernel.dylib`__psynch_mutexwait + 10
+    frame #1: 0x00007fff8e05f779 libsystem_pthread.dylib`_pthread_mutex_lock + 372
+    frame #2: 0x000000010033e8e9 qemu-system-arm`qemu_mutex_lock(mutex=<unavailable>) + 25 at qemu-thread-posix.c:76
+    frame #3: 0x000000010002d742 qemu-system-arm`qemu_mutex_lock_iothread + 98 at cpus.c:1137
+    frame #4: 0x00000001002c84b5 qemu-system-arm`main_loop_wait [inlined] os_host_main_loop_wait(timeout=<unavailable>) + 191 at main-loop.c:242
+    frame #5: 0x00000001002c83f6 qemu-system-arm`main_loop_wait(nonblocking=<unavailable>) + 278 at main-loop.c:494
+    frame #6: 0x000000010014961a qemu-system-arm`qemu_main [inlined] main_loop + 73 at vl.c:1789
+    frame #7: 0x00000001001495d1 qemu-system-arm`qemu_main(argc=<unavailable>, argv=<unavailable>, envp=<unavailable>) + 17057 at vl.c:4353
+    frame #8: 0x000000010029b45e qemu-system-arm`-[QemuCocoaAppController startEmulationWithArgc:argv:](self=<unavailable>, _cmd=<unavailable>, argc=<unavailable>, argv=<unavailable>) + 30 at cocoa.m:897
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1408152 b/results/classifier/gemma3:12b/kernel/1408152
new file mode 100644
index 00000000..9c25a4b9
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1408152
@@ -0,0 +1,7 @@
+
+latest qemu git doesn't load
+
+commit ab0302ee764fd702465aef6d88612cdff4302809This is with 
+
+qemu-system-x86_64: util/qemu-option.c:387: qemu_opt_get_bool_helper: Assertion `opt->desc && opt->desc->type == QEMU_OPT_BOOL' failed.
+/home/njh/bin/kfreebsd-amd64: line 7: 32549 Aborted                 (core dumped) qemu-system-x86_64 -drive file=kfreebsd-amd64,index=0,media=disk,cache=writeback,aio=native -drive file=/dev/sr0,index=1,media=cdrom -boot c -redir tcp:2232::22 -m 1024 -machine accel=kvm,kernel_irqchip=on -cpu host -net user,hostname=qemu.bandsman.co.uk -net nic,model=e1000 -k en-us
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1416988 b/results/classifier/gemma3:12b/kernel/1416988
new file mode 100644
index 00000000..e263a424
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1416988
@@ -0,0 +1,33 @@
+
+Wrong signal handling in qemu-aarch64.
+
+Running GCC 5.0 testsuite under qemu-aarch64, I noticed that tests connected with stack unwinding fail with:
+
+qemu: uncaught target signal 11 (Segmentation fault) - core dumped
+
+or run into infinite loop.
+
+Here is one example:
+
+$ /home/max/build/gcc-aarch64/gcc/xgcc -B/home/max/build/gcc-aarch64/gcc/ /home/max/src/toolchain/gcc/gcc/testsuite/gcc.dg/cleanup-11.c -fexceptions -fnon-call-exceptions -O2 -lm -o ./cleanup-11.exe
+
+$ qemu-aarch64 -L /home/max/install/aarch64/aarch64-linux/sys-root/ -R 0 -/cleanup-11.exe
+qemu: uncaught target signal 11 (Segmentation fault) - core dumped.
+
+Actually, this caused by ABI incompatibility between Linux Kernel (trunk) and qemu-aarch64. In fact, size of siginfo structure in Linux and target_siginfo structure in qemu-aarch64 differ:
+
+sizeof (struct target_siginfo) = 136  // QEMU
+sizeof (struct siginfo) = 128               // Linux Kernel
+
+
+This caused by wrong TARGET_SI_PAD_SIZE defined in  linux-user/syscall_defs.h:
+
+#define TARGET_SI_PAD_SIZE	((TARGET_SI_MAX_SIZE/sizeof(int)) - 3)
+
+In Kernel respective value is:
+
+#define SI_PAD_SIZE     ((SI_MAX_SIZE - __ARCH_SI_PREAMBLE_SIZE) / sizeof(int))
+.............................................
+#define __ARCH_SI_PREAMBLE_SIZE (4 * sizeof(int))  // for Aarch64
+
+Trivial fix, changing TARGET_SI_PAD_SIZE to right value, is attached.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1428352 b/results/classifier/gemma3:12b/kernel/1428352
new file mode 100644
index 00000000..c4dd6358
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1428352
@@ -0,0 +1,45 @@
+
+SYSRET instruction incorrectly implemented
+
+The Intel architecture manual states that when returning to user mode, the SYSRET instruction will re-load the stack selector (%ss) from the IA32_STAR model specific register using the following logic:
+
+SS.Selector <-- (IA32_STAR[63:48]+8) OR 3; (* RPL forced to 3 *)
+
+Another description of the instruction behavior which shows the same logic in a slightly different form can also be found here:
+
+http://tptp.cc/mirrors/siyobik.info/instruction/SYSRET.html
+
+[...]
+        SS(SEL) = IA32_STAR[63:48] + 8;
+        SS(PL) = 0x3;
+[...]
+
+In other words, the value of the %ss register is supposed to be loaded from  bits 63:48 of the IA32_STAR model-specific register, incremented by 8, and then ORed with 3. ORing in the 3 sets the privilege level to 3 (user). This is done since SYSRET returns to user mode after a system call.
+
+However, helper_sysret() in target-i386/seg_helper.c does not do the "OR 3" step. The code looks like this:
+
+        cpu_x86_load_seg_cache(env, R_SS, selector + 8,
+                               0, 0xffffffff,
+                               DESC_G_MASK | DESC_B_MASK | DESC_P_MASK |
+                               DESC_S_MASK | (3 << DESC_DPL_SHIFT) |
+                               DESC_W_MASK | DESC_A_MASK);
+
+It should look like this:
+
+        cpu_x86_load_seg_cache(env, R_SS, (selector + 8) | 3,
+                               0, 0xffffffff,
+                               DESC_G_MASK | DESC_B_MASK | DESC_P_MASK |
+                               DESC_S_MASK | (3 << DESC_DPL_SHIFT) |
+                               DESC_W_MASK | DESC_A_MASK);
+
+The code does correctly set the privilege level bits for the code selector register (%cs) but not for the stack selector (%ss).
+
+The effect of this is that when SYSRET returns control to the user-mode caller, %ss will be have the privilege level bits cleared. In my case, it went from 0x2b to 0x28. This caused a crash later: when the user-mode code was preempted by an interrupt, and the interrupt handler would do an IRET, a general protection fault would occur because the %ss value being loaded from the exception frame was not valid for user mode. (At least, I think that's what happened.)
+
+This behavior seems inconsistent with real hardware, and also appears to be wrong with respect to the Intel documentation, so I'm pretty confident in calling this a bug. :)
+
+Note that this issue seems to have been around for a long time. I discovered it while using QEMU 2.2.0, but I happened to have the sources for QEMU 0.10.5, and the problem is there too (in os_helper.c). I am using FreeBSD/amd64 9.1-RELEASE as my host system, without KVM.
+
+The fix is fairly simple. I'm attaching a patch which worked for me. Using this fix, the code that I'm testing now behaves the same on the QEMU virtual machine as on real hardware.
+
+- Bill (<email address hidden>)
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1429313 b/results/classifier/gemma3:12b/kernel/1429313
new file mode 100644
index 00000000..3a585306
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1429313
@@ -0,0 +1,10 @@
+
+qemu-user doesn't block target signals on entry to signal hanlder.
+
+Upon entry to a target signal handler the function process_pending_signals in linux-user/signal.c block the appropriate host signals, but signals already received and queued by Qemu are not blocked. If multiple signals arrive in quick succession this results incorrect recursion in the target signal handler.
+
+The attached test case my be run as:
+
+$ (sleep 2 ; echo) | qemu-i386 ./a.out
+.................. Recursion in signal handler!
+qemu: uncaught target signal 6 (Aborted) - core dumped
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1444 b/results/classifier/gemma3:12b/kernel/1444
new file mode 100644
index 00000000..04c51f9d
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1444
@@ -0,0 +1,43 @@
+
+ld.so on aarch64 crashes (SIGSEGV) qemu-aarch64-static to verify attached executable
+Description of problem:
+I'm currently managing an automation to build a linux distribution from nothing.
+The issues is when I try to cross compile gobject-introspection for aarch64 (it is currently working on arm) because the g-ir-compile phase requires a binary verification using ld-linux-aarch64-so-1 --verify GLib-2.0 process used by ldd, that crashes qemu-aarch64-static.
+Original command is: ${SYSROOT}/lib/ld-linux-aarch64-so-1 --verify ${HOME}/builds/gobject-introspection_1.75.4/tmp-introspectnpyrhpje/GLib-2.0.
+I simplified the problem bringing out the ld.so and GLib-2.0 binary to obtain the same result.
+
+This happens with glibc 2.35 and glibc 2.36 on aarch64 built with a gcc-12.2 cross compiler (x86 -> aarch64).
+
+[GLib-2.0](/uploads/47932b18278835fb13ef0de4c34872fa/GLib-2.0)
+
+[ld-linux-aarch64.so.1](/uploads/0ee01949285bea8ccfcebdc88a1d5b33/ld-linux-aarch64.so.1)
+
+I tried to debug the SIGSEGV but it's out completely out of my capacity.
+Steps to reproduce:
+1. Copy the 2 attached files in a directory:
+2. Run: qemu-aarch64-static ./ld-linux-aarch64.so.1 --verify ./GLib-2.0
+3. Result: Segmentation fault.
+Additional information:
+I attach the output of gdb after install qemu debug symbols:
+
+```
+Thread 1 "qemu-aarch64-st" received signal SIGSEGV, Segmentation fault.
+0x0000000000401088 in ?? ()
+(gdb) bt
+#0  0x0000000000401088 in ?? ()
+#1  0x00000000006aa439 in g_malloc0 ()
+#2  0x000000000061bb4b in page_find_alloc (index=index@entry=1024, alloc=alloc@entry=1)
+    at ../accel/tcg/translate-all.c:494
+#3  0x000000000061db12 in page_set_flags (start=start@entry=4194304, end=end@entry=4206592, flags=9, flags@entry=73)
+    at ../accel/tcg/translate-all.c:2288
+#4  0x0000000000629f10 in target_mmap (start=<optimized out>, start@entry=4194304, len=<optimized out>,
+    len@entry=12288, target_prot=target_prot@entry=1, flags=2066, fd=fd@entry=3, offset=offset@entry=0)
+    at ../linux-user/mmap.c:629
+#5  0x0000000000641e1d in do_syscall1 (cpu_env=0x9e8c10, num=222, arg1=4194304, arg2=12288, arg3=1,
+    arg4=<optimized out>, arg5=3, arg6=0, arg8=<optimized out>, arg7=<optimized out>) at ../linux-user/syscall.c:9961
+#6  0x0000000000644c8c in do_syscall (cpu_env=cpu_env@entry=0x9e8c10, num=222, arg1=4194304, arg2=12288, arg3=1,
+    arg4=2066, arg5=3, arg6=0, arg7=0, arg8=0) at ../linux-user/syscall.c:13203
+#7  0x000000000040fca8 in cpu_loop (env=env@entry=0x9e8c10) at ../linux-user/aarch64/cpu_loop.c:93
+#8  0x000000000040267f in main (argc=<optimized out>, argv=0x7fffffffdfc8, envp=<optimized out>)
+    at ../linux-user/main.c:897
+```
diff --git a/results/classifier/gemma3:12b/kernel/1450881 b/results/classifier/gemma3:12b/kernel/1450881
new file mode 100644
index 00000000..de310b33
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1450881
@@ -0,0 +1,26 @@
+
+qemu-system-sparc MUTEX_HELD assert and libC lock errors
+
+Here I am cross-posting a comment I made on Artyom's blog.  Atar responded that he "fixed these issues for some customers".  I hoped that opening a bug to the opensource project might help develop the solution for the public domain.
+
+I now have a mostly-working Solaris 6 emulation, with great thanks to the valuable information in Artyom's blog, brezular.com, and the QEMU/Solaris 4.14 wikibook.
+
+setup detail;
+QEMU (present git snapshot, reports --version 2.2.92)
+-M SS-20, openboot/proprietary prom
+
+# uname -a
+SunOS emu0 5.6 Generic_105181-33 sun4m sparc SUNW,SPARCstation-20
+
+I continue to have a problem, which I have found others posted in blog comments, but have not seen a resolution yet.
+
+# /etc/init.d/init.dmi start
+Run-time error, libC:
+Trying to release a lock that was not acquired in this thread
+(repeat above 1x)
+Abort - core dumped
+
+as well as:
+Assertion failed: MUTEX_HELD(&svc_mutex), file rpc/svc_run.c, line 766
+
+which prints to the console periodically when "dmispd" is running.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1454 b/results/classifier/gemma3:12b/kernel/1454
new file mode 100644
index 00000000..2297cce6
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1454
@@ -0,0 +1,63 @@
+
+QEMU TCG s390x fails an assertion while dispatching an FIXPT_DIVIDE exception on DR when compiled with LTO
+Description of problem:
+When running the attached minimal reproducer, with qemu-system-s390x version 7.2.0 compiled with LTO (`--enable-lto`) with GCC v12.2.1, QEMU fails an assertion and crashes:
+```
+qemu-system-s390x: ../target/s390x/tcg/excp_helper.c:215: do_program_interrupt: Assertion `ilen == 2 || ilen == 4 || ilen == 6' failed.
+Aborted (core dumped)
+```
+Steps to reproduce:
+1. Compile QEMU v7.2.0 for s390x with LTO enabled:
+   ```
+   ../configure --target-list=s390x-softmmu --enable-lto
+   ```
+2. Compile the given reproducer assembler [lpswe-to-pgm.S](/uploads/200fb0e777ddd0ed26f51009e81c26ea/lpswe-to-pgm.S):
+   ```
+   s390x-linux-gnu-gcc -march=z13 -m64 -nostdlib -nostartfiles -static -Wl,-Ttext=0 -Wl,--build-id=none lpswe-to-pgm.S -o lpswe-to-pgm
+   ```
+3. Execute QEMU on the reproducer:
+   ```
+   ./qemu-system-s390x -kernel lpswe-to-pgm
+   ```
+Additional information:
+I have debugged QEMU to try to find the root cause, and I believe I found it, but I'm not sure what the most appropriate way to fix it would be:
+
+QEMU executes the `DR` instruction by executing the `divs32` helper.
+
+When the helper sees that the final division result does not fit in 32 bits, it generates a program interrupt for fixed point divide by calling the `tcg_s390_program_interrupt` function, with the final parameter being the TCG host PC, which is found by calling `GETPC`.
+
+`tcg_s390_program_interrupt` then calls `cpu_restore_state`, and then as long as the host PC is valid, `cpu_restore_state` eventually calls `s390x_restore_state_to_opc` through a long chain of calls, which sets `CPUS390XState::int_pgm_ilen` to a valid value.
+
+Unfortunately when compiling with LTO, the host PC is not valid, which means we don't update `int_pgm_ilen`, resulting in the failed assertion.
+
+The reason the host PC is not valid when compiling with LTO, is that GCC decides to split `helper_divs32` into 2 parts, the actual div logic being the first part, and the call to `GETPC` & `tcg_s390_program_interrupt` being the second part. The way GCC implements it is by turning the second part into a separate function, which the first part calls - see disassembly below. (GCC then re-uses the second part in other similar TCG helpers)
+
+Because we now called the second part before calling `GETPC`, we have a new return address, and `GETPC` returns the address of the first part, instead of the TCG host PC.
+
+```
+000000000022c870 <helper_divs32>:
+  22c870:       48 83 ec 08             sub    rsp,0x8
+  22c874:       85 d2                   test   edx,edx
+  22c876:       74 22                   je     22c89a <helper_divs32+0x2a>
+  22c878:       48 89 f0                mov    rax,rsi
+  22c87b:       48 63 ca                movsxd rcx,edx
+  22c87e:       48 99                   cqo    
+  22c880:       48 f7 f9                idiv   rcx
+  22c883:       4c 63 c0                movsxd r8,eax
+  22c886:       48 89 97 10 03 00 00    mov    QWORD PTR [rdi+0x310],rdx
+  22c88d:       49 39 c0                cmp    r8,rax
+  22c890:       75 17                   jne    22c8a9 <helper_divs32+0x39>
+  22c892:       4c 89 c0                mov    rax,r8
+  22c895:       48 83 c4 08             add    rsp,0x8
+  22c899:       c3                      ret    
+  22c89a:       48 8b 54 24 08          mov    rdx,QWORD PTR [rsp+0x8]
+  22c89f:       be 09 00 00 00          mov    esi,0x9
+  22c8a4:       e8 47 e5 ff ff          call   22adf0 <tcg_s390_program_interrupt>
+  22c8a9:       e8 b2 fe ff ff          call   22c760 <helper_divs32.part.0>
+
+000000000022c760 <helper_divs32.part.0>:
+  22c760:       48 83 ec 08             sub    rsp,0x8
+  22c764:       be 09 00 00 00          mov    esi,0x9
+  22c769:       48 8b 54 24 08          mov    rdx,QWORD PTR [rsp+0x8]
+  22c76e:       e8 7d e6 ff ff          call   22adf0 <tcg_s390_program_interrupt>
+```
diff --git a/results/classifier/gemma3:12b/kernel/1462 b/results/classifier/gemma3:12b/kernel/1462
new file mode 100644
index 00000000..4742f146
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1462
@@ -0,0 +1,15 @@
+
+qemu-system-m68k segfaults on opcode 0x4848
+Description of problem:
+Running an m68k executable with opcode 0x4848 will segfault qemu-system-m68k
+Steps to reproduce:
+1. Boot m68k debian
+2. Compile program (see above for the oops.c source) that executes opcode 0x4848
+3. Run program
+4. QEMU segfaults:
+
+```
+./debian-m68k.sh: line 10:  4420 Segmentation fault      (core dumped) qemu-system-m68k -boot c -M q800 -serial none -serial mon:stdio -m 1000M -net nic,model=dp83932,addr=08:00:07:12:34:89 -net user -append "root=/dev/sda2 rw console=ttyS0 console=tty" -kernel virt/vmlinux-4.16.0-1-m68k -initrd virt/initrd.img-4.16.0-1-m68k -drive file=virt/debian-m68k-deb10.qcow2,format=qcow2 -nographic
+```
+Additional information:
+
diff --git a/results/classifier/gemma3:12b/kernel/1463143 b/results/classifier/gemma3:12b/kernel/1463143
new file mode 100644
index 00000000..32799d27
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1463143
@@ -0,0 +1,51 @@
+
+Kernel Panic on Guest VM
+
+Hi,
+
+I've recently attempted to move a stack to qemu vm's that I have run successfully on both hard metal and ec2.
+
+I'm not sure where to even begin debugging, could someone please point me in the right direction?
+
+
+
+
+  [781785.483343] RIP: 0010:[<ffffffff81511830>]  [<ffffffff81511830>] ata_sff_hsm_move+0x1b0/0x780
+[781785.483345] RSP: 0000:ffff88007fd03dd0  EFLAGS: 00010097
+[781785.483346] RAX: 0000000000000000 RBX: ffff8800374d0000 RCX: 0000000000000050
+[781785.483347] RDX: 0000000000000006 RSI: ffff8800374d0158 RDI: ffff8800374d0000
+[781785.483348] RBP: ffff88007fd03e20 R08: 0000000000000086 R09: ffff88007cc00000
+[781785.483349] R10: 0000000000000011 R11: 000000000000000b R12: ffff8800374d0158
+[781785.483350] R13: 0000000000000000 R14: ffff8800374d0158 R15: ffff8800374d0208
+[781785.483356] FS:  00007f3882e75700(0000) GS:ffff88007fd00000(0000) knlGS:0000000000000000
+[781785.483357] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
+[781785.483358] CR2: 00007f37df39a000 CR3: 000000000b7a5000 CR4: 00000000000006e0
+[781785.483369] Stack:
+[781785.483373]  ffff8800373cb000 ffff88007fd03e60 ffffffff8108d7d2 ffff88007fd03e28
+[781785.483375]  ffff8800374d2140 ffff8800374d0000 ffff8800374d0158 0000000000000000
+[781785.483378]  0000000000000050 0000000000000000 ffff88007fd03e50 ffffffff81511e96
+[781785.483378] Call Trace:
+[781785.483382]  <IRQ> 
+[781785.483396]  [<ffffffff8108d7d2>] ? run_posix_cpu_timers+0x42/0x5c0
+[781785.483400]  [<ffffffff81511e96>] __ata_sff_port_intr+0x96/0x120
+[781785.483403]  [<ffffffff815121ed>] ata_bmdma_port_intr+0x2d/0x120
+[781785.483405]  [<ffffffff81512ba3>] ata_bmdma_interrupt+0x183/0x1e0
+[781785.483414]  [<ffffffff810bf8be>] handle_irq_event_percpu+0x3e/0x1d0
+[781785.483433]  [<ffffffff810bfa8d>] handle_irq_event+0x3d/0x60
+[781785.483437]  [<ffffffff810c2517>] handle_edge_irq+0x77/0x130
+[781785.483455]  [<ffffffff81015cde>] handle_irq+0x1e/0x30
+[781785.483472]  [<ffffffff817312cd>] do_IRQ+0x4d/0xc0
+[781785.483476]  [<ffffffff81726a6d>] common_interrupt+0x6d/0x6d
+[781785.483478]  <EOI> 
+[781785.483480]  [<ffffffff8172efad>] ? system_call_fastpath+0x1a/0x1f
+[781785.483498] Code: f9 ff ff 41 0f b6 46 28 3c 06 0f 84 0b 03 00 00 3c 07 0f 84 e3 02 00 00 3c 05 0f 84 c3 02 00 00 0f 0b 66 0f 1f 84 00 00 00 00 00 <0f> 0b 66 0f 1f 44 00 00 f6 c1 08 0f 84 19 05 00 00 f6 c1 21 0f 
+[781785.483501] RIP  [<ffffffff81511830>] ata_sff_hsm_move+0x1b0/0x780
+[781785.483501]  RSP <ffff88007fd03dd0>
+[781785.484009] ---[ end trace 1b6ef3497a5641b3 ]---
+[781785.484009] Kernel panic - not syncing: Fatal exception in interrupt
+[781785.484009] Shutting down cpus with NMI
+
+
+Thanks for any pointers.
+
+Ryan
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1463172 b/results/classifier/gemma3:12b/kernel/1463172
new file mode 100644
index 00000000..e01ff04a
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1463172
@@ -0,0 +1,4 @@
+
+destination arm board hangs after migration from x86 source
+
+The qemu destination on an arm board hangs after migration from a x86 source. With qemu emulating Arch, the migration works fine while the vm is still in the boot selection screen, but if the machine is booted, then the destination arm board vm hangs indefinitely after migrating from the x86 source. This bug does not occur the other way around, meaning a booted vm originally run on arm board will continue to work after migrating to a x86 destination.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1470170 b/results/classifier/gemma3:12b/kernel/1470170
new file mode 100644
index 00000000..bd241792
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1470170
@@ -0,0 +1,41 @@
+
+Unsupported syscalls 370 and 355
+
+Qemu seems to be missing syscalls 370 and 355 when running qemu usermode arm. These are used by systemd or some similar new package. This can be detected by creating an debian sid armhf with qemu debootstrap. When the system is launched with "systemd-nspawn -bD sid-arm" this happens (newest git as of today):
+
+pawning container sid-arm on /home/jpakkane/qemutest/sid-arm. 
+Press ^] three times within 1s to kill container. 
+Failed to create directory /home/jpakkane/qemutest/sid-arm//sys/fs/selinux: Read-only file system 
+Failed to create directory /home/jpakkane/qemutest/sid-arm//sys/fs/selinux: Read-only file system 
+/etc/localtime is not a symlink, not updating container timezone. 
+qemu: Unsupported syscall: 370 
+qemu: Unsupported syscall: 370 
+qemu: Unsupported syscall: 370 
+qemu: Unsupported syscall: 370 
+qemu: Unsupported syscall: 370 
+qemu: Unsupported syscall: 370 
+qemu: Unsupported syscall: 370 
+qemu: Unsupported syscall: 370 
+qemu: Unsupported syscall: 370 
+qemu: Unsupported syscall: 370 
+qemu: Unsupported syscall: 370 
+qemu: Unsupported syscall: 384 
+qemu: Unsupported syscall: 370 
+qemu: Unsupported syscall: 370 
+qemu: Unsupported syscall: 370 
+qemu: Unsupported syscall: 370 
+qemu: Unsupported syscall: 370 
+qemu: Unsupported syscall: 370 
+qemu: Unsupported syscall: 370 
+qemu: Unsupported syscall: 370 
+qemu: Unsupported syscall: 370 
+systemd 221 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN) 
+Detected virtualization systemd-nspawn. 
+Detected architecture arm. 
+
+Welcome to Debian GNU/Linux stretch/sid! 
+
+Set hostname to <manos>. 
+qemu: Unsupported syscall: 355 
+Failed to allocate manager object: Function not implemented 
+[!!!!!!] Failed to allocate manager object, freezing.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1478 b/results/classifier/gemma3:12b/kernel/1478
new file mode 100644
index 00000000..d80fcbfa
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1478
@@ -0,0 +1,67 @@
+
+Qemu 7.2.0 i386: core2: init crash (glibc)
+Description of problem:
+The toolchain-builder project (a side project of Buildroot to build pre-built toolchains) reported an issue with Qemu 7.2.0 for  x86-core2--glibc--bleeding-edge toolchain, see:
+
+https://gitlab.com/buildroot.org/toolchains-builder/-/jobs/3731683337
+
+Reverting back to Qemu 7.1.0, the system boot correctly with the same system image.
+I reproduced the issue with the current Qemu master (6b433719eabf0abc74cff0cfd5687f0137c4198a)
+
+Here is the boot log obtained with Qemu 7.2.0:
+   ```
+Run /sbin/init as init process
+random: fast init done
+EXT4-fs (vda): warning: mounting unchecked fs, running e2fsck is recommended
+EXT4-fs (vda): re-mounted. Opts: (null). Quota mode: disabled.
+Starting syslogd: OK
+traps: syslogd[52] general protection fault ip:b7e21465 sp:bfe59e6c error:0 in libc.so.6[b7d9b000+123000]
+Starting klogd: OK
+traps: klogd[56] general protection fault ip:b7e94465 sp:bf8f069c error:0 in libc.so.6[b7e0e000+123000]
+Running sysctl: traps: logger[62] general protection fault ip:b7e48b6c sp:bfd7d194 error:0 in libc.so.6[b7e05000+123000]
+Segmentation fault
+traps: logger[64] general protection fault ip:b7dd3b6c sp:bf9b8604 error:0 in libc.so.6[b7d90000+123000]
+Segmentation fault
+
+traps: init[100] general protection fault ip:b7dda465 sp:bfd5f42c error:0 in libc.so.6[b7d54000+123000]
+Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
+CPU: 0 PID: 1 Comm: init Not tainted 5.15.18 #1
+Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.1-0-g3208b098f51a-prebuilt.qemu.org 04/01/2014
+Call Trace:
+ dump_stack_lvl+0x32/0x41
+ dump_stack+0xd/0x10
+ panic+0x90/0x206
+ do_exit.cold+0xa9/0xa9
+ do_group_exit+0x2a/0x90
+ get_signal+0x115/0x7e0
+ arch_do_signal_or_restart+0x90/0x5a0
+ ? put_pid+0xc/0x20
+ ? kernel_clone+0x10b/0x3d0
+ exit_to_user_mode_prepare+0xf8/0x1c0
+ syscall_exit_to_user_mode+0x1b/0x40
+ do_int80_syscall_32+0x41/0x90
+ entry_INT80_32+0xf0/0xf0
+EIP: 0xb7de5d88
+Code: 37 01 00 00 65 ff 15 10 00 00 00 89 d0 5a 5b 5e 5f 5d c3 66 90 66 90 66 90 66 90 66 90 66 90 66 90 90 59 b8 be 00 00 00 cd 80 <51> 3d 01 f0 ff ff 0f 83 06 e9 f6 ff c3 e8 81 a0 06 00 05 9a a0 0e
+EAX: 00000064 EBX: 0059aa1c ECX: 00561f5b EDX: 00000008
+ESI: 0059cc20 EDI: bfd5fa64 EBP: 0059b138 ESP: bfd5fa20
+DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b EFLAGS: 00000246
+Kernel Offset: disabled
+---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---
+   ```
+I did a git bisect on qemu sources up to this commit:
+
+https://gitlab.com/qemu-project/qemu/-/commit/958e1dd1300f37f18b2161dfb4eb806fc8c19b44
+Steps to reproduce:
+Build the Buildroot qemu_x86_defconfig with BR2_x86_core2 target architecture variant added manually
+1. git clone https://gitlab.com/buildroot.org/buildroot.git
+2. git switch --detach c419ef62d84b5be65599452ab84f7ed719bbe470
+3. make qemu_x86_defconfig
+4. make menuconfig (enable BR2_x86_core2)
+5. make
+6. ./output/images/start-qemu.sh
+Additional information:
+System built with gcc options:
+   ```
+i686-buildroot-linux-gnu-gcc.br_real' '--sysroot' 'output/host/i686-buildroot-linux-gnu/sysroot' '-fstack-protector-strong' '-fPIE' '-pie' '-Wl,-z,now' '-Wl,-z,relro'
+   ```
diff --git a/results/classifier/gemma3:12b/kernel/1481 b/results/classifier/gemma3:12b/kernel/1481
new file mode 100644
index 00000000..5eef5280
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1481
@@ -0,0 +1,2 @@
+
+How to create Rootfs for sifive_u machine
diff --git a/results/classifier/gemma3:12b/kernel/1482425 b/results/classifier/gemma3:12b/kernel/1482425
new file mode 100644
index 00000000..f6413fbf
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1482425
@@ -0,0 +1,16 @@
+
+Qemu crashes on Mac (emulation of  x86_64)
+
+I used qemu on MAC OS X Yosemite with the latest qemu version (from git, 6. august 2015, QEMU emulator version 2.3.94, Copyright (c) 2003-2008 Fabrice Bellard)
+
+I configured it with "./configure --enable-vde".
+
+Sometimes when starting an openwrt instance, the following error occurrs in the qemu monitor:
+
+(qemu) qemu:qemu_cpu_kick_thread: No such process
+
+I started qemu this way:
+
+qemu-system-x86_64 -m 128 -serial unix:/tmp/qemu_1.sock,server,nowait -nographic -net nic,macaddr=aa:aa:aa:aa:00:01 -net vde,sock=/tmp/vde_switch_1 -watchdog-action poweroff openwrt-x86-generic-combined-ext4.img
+
+The same works on Linux (Ubuntu 14.04, qemu-2.4.0-rc3).
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1499 b/results/classifier/gemma3:12b/kernel/1499
new file mode 100644
index 00000000..94391899
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1499
@@ -0,0 +1,91 @@
+
+qemu-system-arm doesn't honour CPACR.ASEDIS, D32DIS
+Description of problem:
+We used differential testing to compared the instruction consistency (ARMv7) between QEMU and raspberry pi 2B in system level and some inconsistency in SIMD instruction was detected.
+
+We compiled the kernel with options `-mcpu=cortex-a7 -march=armv7ve -mfloat-abi=hard -mfpu=vfpv4 `. Some SIMD instructions are considered as **undefined** instructions in raspi2b, but run successfully in the QEMU. 
+
+We checked that the CPACR.ASEDIS=1, which disables Advanced SIMD functionality, according to ARMv7-a manual B4.1.40.  The manual says "All instruction encodings identified in the Alphabetical list of instructions on page A8-300 as being Advanced SIMD instructions, but that are not VFPv3 or VFPv4
+instructions, are UNDEFINED when accessed from PL1 and PL0 modes."
+
+Tested instruction samples are shown as follows:
+
+- VMAX_int_T1A1_A 11110010010010110000011010100100 0xf24b06a4
+- VMUL_scalar_A1_A 11110010101001001100100 001000011 0xf2a4c843
+- VADD_int_T1A1_A 11110010000111111010100000001100 0xf21fa80c
+
+...
+
+Some checks of the SIMD instructions may be needed before the execution of the instructions in function ` do_3same` etc. in target/arm/translate-neon.c.
+Steps to reproduce:
+1. Compile a kernel module to run the test instruction in PL1.
+2. Hook a undefined handler in kernel module to catch the undefined instructions. A kernel module template we used to test is as follows
+
+```c
+#include <linux/module.h>
+#include <linux/kernel.h>
+#include <asm/traps.h> 
+
+MODULE_LICENSE("GPL");
+#pragma GCC optimize ("O0")
+// instr is undefined instruction value
+static int undef_instr_handler(struct pt_regs *regs, u32 instr)
+{
+    printk(KERN_INFO "get undefined instruction\n");
+    // Just skip over to the next instruction.
+    regs->ARM_pc += 4;
+    return 0; // All fine!
+}
+
+static struct undef_hook uh = {
+    .instr_mask  = 0x0, // any instruction
+    .instr_val   = 0x0, // any instruction
+    .cpsr_mask = 0x0, // any pstate
+    .cpsr_val  = 0x0, // any pstate
+    .fn          = undef_instr_handler
+};
+int init_module(void) {
+    // Lookup wanted symbols.
+    register_undef_hook(&uh);
+    __asm__ __volatile__("push {R0-R12}");
+    __asm__ __volatile__(
+      ".global inialize_location\n"
+      "inialize_location:\n"
+      "mov r0, %[reg_init]        \n"
+      "mov r1, %[reg_init]        \n"
+      "mov r2, %[reg_init]        \n"
+      "mov r3, %[reg_init]        \n"
+      "mov r4, %[reg_init]        \n"
+      "mov r5, %[reg_init]        \n"
+      "mov r6, %[reg_init]        \n"
+      "mov r7, %[reg_init]        \n"
+      "mov r8, %[reg_init]        \n"
+      "mov r9, %[reg_init]        \n"
+      "mov r10, %[reg_init]       \n"
+      "mov r11, %[reg_init]       \n"
+      "mov r12, %[reg_init]       \n"
+      :
+      : [reg_init] "n"(0)
+    );
+  // =======TODO=======
+  // replace nop with test instruction
+   __asm__ __volatile__(
+      ".global inst_location\n"
+      "inst_location:\n"
+      "nop\n" 
+    );
+    // kgdb_breakpoint();
+    __asm__ __volatile__(
+      ".global finish_location\n"
+      "finish_location:\n"
+    );
+    __asm__ __volatile__("pop {R0-R12}");
+    return 0;
+}
+
+void cleanup_module(void) {
+    unregister_undef_hook(&uh);
+}
+```
+Additional information:
+
diff --git a/results/classifier/gemma3:12b/kernel/1503031 b/results/classifier/gemma3:12b/kernel/1503031
new file mode 100644
index 00000000..988be305
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1503031
@@ -0,0 +1,12 @@
+
+32-to-64-bit call gate unsupported in IA32e mode
+
+In particular, the lcall implementation doesn't support the 64-bit TSS.
+
+helper_lcall_protected (target-i386/seg_helper.c:1884) calls get_ss_esp_from_tss() on a call gate to a lower privilege level, which tries to extract a 32-bit ESP and 16-bit SS from the TSS.  In IA32e mode (64-bit or compatibility mode), this instead grabs the lower 32-bits of the target RSP, and 16 of the upper bits as the SS.  Additionally, several of the subsequent checks are incorrect (even if the correct stack pointer were extracted).
+
+This isn't a problem for interrupts since the interrupts are given their own implementation entirely, that uses get_rsp_from_tss() rather than get_ss_esp_from_tss().
+
+I believe the missing logic is from the branch starting "ELSE (* current TSS is 64-bit *)" in the CALL pseudocode in the Intel manual (page 3-124 of the PDF I have).
+
+Reproduced at master (c0b520dfb8890294a9f8879f4759172900585995), and also as of a qemu built a year ago.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1506 b/results/classifier/gemma3:12b/kernel/1506
new file mode 100644
index 00000000..6f7bb9b1
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1506
@@ -0,0 +1,2 @@
+
+QEMU not support 32-bit stack in unreal/flat/big 32-bit mode
diff --git a/results/classifier/gemma3:12b/kernel/1516408 b/results/classifier/gemma3:12b/kernel/1516408
new file mode 100644
index 00000000..f50ea42e
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1516408
@@ -0,0 +1,32 @@
+
+sh4: Unsupported syscall: 186
+
+Hello!
+
+I'm currently testing qemu as a possibility to set up a buildd for the Debian sh4 port.
+
+I set up qemu and an sh4 chroot as described in the Debian Wiki [1]. This seems to be working mostly fine (besides the fact that qemu segfaults on an amd64 host while it runs fine on an i386 host, I'll file a separate bug report). However, when installing python3.4 in the sh4 chroot, qemu repeatedly printed an error message about an unimplemented syscall: 186:
+
+qemu: Unsupported syscall: 186
+
+From the source code in linux-user/sh4/syscall_nr.h it's apparent that 186 is defined as 
+
+#define TARGET_NR_sigaltstack   186
+
+Looking at the implementation part, it becomes obvious that this syscall is not enabled for sh4:
+
+#if defined(TARGET_I386) || defined(TARGET_ARM) || defined(TARGET_MIPS) || \
+    defined(TARGET_SPARC) || defined(TARGET_PPC) || defined(TARGET_ALPHA) || \
+    defined(TARGET_M68K) || defined(TARGET_S390X) || defined(TARGET_OPENRISC)
+        ret = do_sigaltstack(arg1, arg2, get_sp_from_cpustate((CPUArchState *)cpu_env));
+        break;
+#else
+        goto unimplemented;
+#endif
+
+Is there any particular reason why TARGET_NR_sigaltstack is not enabled on sh4? If not, could you enable it?
+
+Thanks,
+Adrian
+
+> [1] https://wiki.debian.org/QemuUserEmulation
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1518 b/results/classifier/gemma3:12b/kernel/1518
new file mode 100644
index 00000000..05a0ed90
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1518
@@ -0,0 +1,91 @@
+
+qemu tests/unit/test-vmstate crashes in g_tree_foreach
+Description of problem:
+qemu test suite crashes with the latest Fedora Rawhide.
+Downstream issue: https://bugzilla.redhat.com/show_bug.cgi?id=2173639
+Steps to reproduce:
+1. Compile and test qemu from source as normal.
+
+```
+214/658 qemu:unit / test-vmstate                                                  ERROR           0.22s   killed by signal 11 SIGSEGV
+317/658 qemu:qtest+qtest-i386 / qtest-i386/rtl8139-test                           ERROR           0.28s   2 subtests passed
+588/658 qemu:qtest+qtest-x86_64 / qtest-x86_64/rtl8139-test                       ERROR           0.45s   2 subtests passed
+```
+
+The stack trace from the test is:
+
+```
+#0  g_tree_foreach (user_data=0x7fffa23ccbc0, func=0x55a834fe3770 <diff_tree>, 
+    tree=<optimized out>) at ../glib/gtree.c:1132
+#1  g_tree_foreach (tree=<optimized out>, func=0x55a834fe3770 <diff_tree>, 
+    user_data=0x7fffa23ccbc0) at ../glib/gtree.c:1117
+#2  0x000055a834fe382c in compare_trees (tree1=0x55a836723bf0, 
+    tree2=0x55a836723f50, 
+    function=function@entry=0x55a834fe3570 <match_interval_mapping_node>)
+    at ../tests/unit/test-vmstate.c:1085
+#3  0x000055a834fee265 in diff_domain (d2=0x55a836709310, d1=0x55a836708fd0)
+    at ../tests/unit/test-vmstate.c:1093
+#4  test_gtree_load_domain () at ../tests/unit/test-vmstate.c:1138
+#5  0x00007f0eef39d32e in test_case_run (tc=0x55a836724150)
+    at ../glib/gtestutils.c:3108
+#6  g_test_run_suite_internal (suite=suite@entry=0x55a8367056e0, 
+    path=path@entry=0x0) at ../glib/gtestutils.c:3203
+#7  0x00007f0eef39cf03 in g_test_run_suite_internal (
+    suite=suite@entry=0x55a836705090, path=path@entry=0x0)
+    at ../glib/gtestutils.c:3222
+#8  0x00007f0eef39cf03 in g_test_run_suite_internal (
+    suite=suite@entry=0x55a8366ff670, path=path@entry=0x0)
+    at ../glib/gtestutils.c:3222
+#9  0x00007f0eef39cf03 in g_test_run_suite_internal (
+    suite=suite@entry=0x55a836700140, path=path@entry=0x0)
+#10 0x00007f0eef39d8c2 in g_test_run_suite (suite=0x55a836700140)
+    at ../glib/gtestutils.c:3302
+#11 0x00007f0eef397c40 in g_test_run () at ../glib/gtestutils.c:2409
+#12 g_test_run () at ../glib/gtestutils.c:2396
+#13 0x000055a834fe2645 in main (argc=<optimized out>, argv=<optimized out>)
+    at ../tests/unit/test-vmstate.c:1523
+```
+
+This can also be reproduced in gdb using a command similar to:
+
+```
+$ MALLOC_PERTURB_=175 G_TEST_SRCDIR=/home/rjones/d/qemu/tests/unit G_TEST_BUILDDIR=/home/rjones/d/qemu/build/tests/unit gdb --args /home/rjones/d/qemu/build/tests/unit/test-vmstate --tap -k
+...
+(gdb) run
+Thread 1 "test-vmstate" received signal SIGSEGV, Segmentation fault.
+g_tree_foreach (user_data=0x7fffffffd3e0, func=0x555555568770 <diff_tree>, tree=<optimized out>) at ../glib/gtree.c:1132
+1132	      if ((*func) (node->key, node->value, user_data))
+(gdb) bt
+#0  g_tree_foreach (user_data=0x7fffffffd3e0, func=0x555555568770 <diff_tree>, 
+    tree=<optimized out>) at ../glib/gtree.c:1132
+#1  g_tree_foreach (tree=<optimized out>, func=0x555555568770 <diff_tree>, 
+    user_data=0x7fffffffd3e0) at ../glib/gtree.c:1117
+#2  0x000055555556882c in compare_trees (tree1=0x5555555ccdb0, 
+    tree2=0x5555555cd110, 
+    function=function@entry=0x555555568570 <match_interval_mapping_node>)
+    at ../tests/unit/test-vmstate.c:1085
+#3  0x0000555555573265 in diff_domain (d2=0x5555555b3310, d1=0x5555555b2fd0)
+    at ../tests/unit/test-vmstate.c:1093
+#4  test_gtree_load_domain () at ../tests/unit/test-vmstate.c:1138
+#5  0x00007ffff7eb132e in test_case_run (tc=0x5555555cd310)
+    at ../glib/gtestutils.c:3108
+#6  g_test_run_suite_internal (suite=suite@entry=0x5555555af6e0, 
+    path=path@entry=0x0) at ../glib/gtestutils.c:3203
+#7  0x00007ffff7eb0f03 in g_test_run_suite_internal (
+    suite=suite@entry=0x5555555af090, path=path@entry=0x0)
+    at ../glib/gtestutils.c:3222
+#8  0x00007ffff7eb0f03 in g_test_run_suite_internal (
+    suite=suite@entry=0x5555555a9670, path=path@entry=0x0)
+    at ../glib/gtestutils.c:3222
+#9  0x00007ffff7eb0f03 in g_test_run_suite_internal (
+    suite=suite@entry=0x5555555aa140, path=path@entry=0x0)
+    at ../glib/gtestutils.c:3222
+#10 0x00007ffff7eb18c2 in g_test_run_suite (suite=0x5555555aa140)
+    at ../glib/gtestutils.c:3302
+#11 0x00007ffff7eabc40 in g_test_run () at ../glib/gtestutils.c:2409
+#12 g_test_run () at ../glib/gtestutils.c:2396
+#13 0x0000555555567645 in main (argc=<optimized out>, argv=<optimized out>)
+    at ../tests/unit/test-vmstate.c:1523
+```
+
+Unfortunately so much is "optimized out" that it's hard to tell what's going wrong.
diff --git a/results/classifier/gemma3:12b/kernel/1547526 b/results/classifier/gemma3:12b/kernel/1547526
new file mode 100644
index 00000000..84dbdf84
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1547526
@@ -0,0 +1,63 @@
+
+Java program does not execute on SPARC Solaris 8
+
+Hello, 
+
+I am trying to run a java program that never execute. The program uses jre1.1.5 which came with the java program. I don't know what to do to run this application. There are some random messages in command line that can be related to my problem (or not). They are:
+
+	#1. Webstart launcher crashing.
+	Also found here: http://www.openfirmware.info/pipermail/openbios/2011-May/006472.html
+
+	#2. Assertion failed: MUTEX_HELD(&svc_mutex), file rpc/svc_run.c, line 766
+	Which was already reported here: https://bugs.launchpad.net/qemu/+bug/1450881
+
+	#3. Some problems with libthread in Solaris. 
+	I have tried a workaround setting LM_LIBRARY_PATH to use another version of libthread that Solaris 8 has.
+
+I don't know if this is a qemu problem or Solaris problem.
+My java application can be executed in command line or in GUI but I've tried both with no luck. I also have tryed other versions of JRE from 1.1.8 to 1.5 but no luck either.
+
+I appreciate **any information** that can help me to execute the java program!!
+Thank you.
+
+I am using qemu-system-sparc (v2.5.50) with Solaris 8 (solaris-8-hw4-2.04-sparc).
+The host is an Ubuntu 15.10 and I am using the openbios-sparc from Ubuntus ppa as shown bellow:
+
+	openbios-sparc | 1.1+svn1334-1 | http://archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
+
+The command line used to launch qemu is:
+
+	qemu-system-sparc \
+		-M SS-5 \
+		-m 256 \
+		-boot c \
+		-cdrom $(DATA_ISO) \
+		-drive file=root-disk.img,index=0,media=disk,format=raw \
+		-serial stdio \
+		-monitor tcp::4444,server,nowait \
+		-localtime \
+		-net user \
+		-net nic \
+		$(ui)
+
+DATA_ISO is the way I found to send my data to the guest.
+
+The root-disk.img is:
+
+	Disk root-disk.img: 36 GiB, 38654705664 bytes, 75497472 sectors
+	Geometry: 27 heads, 107 sectors/track, 24620 cylinders
+	Units: sectors of 1 * 512 = 512 bytes
+	Sector size (logical/physical): 512 bytes / 512 bytes
+	I/O size (minimum/optimal): 512 bytes / 512 bytes
+	Disklabel type: sun
+
+	Device           Start      End  Sectors   Size Id Type       Flags
+	root-disk.img1       0  2744549  2744550   1.3G  2 SunOS root      
+	root-disk.img2 2744550  3047894   303345 148.1M  3 SunOS swap    u 
+	root-disk.img3       0 71127179 71127180  33.9G  5 Whole disk      
+	root-disk.img8 3047895 71127179 68079285  32.5G  8 SunOS home      
+
+	image: root-disk.img
+	file format: raw
+	virtual size: 36G (38654705664 bytes)
+	disk size: 1.2G
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1551 b/results/classifier/gemma3:12b/kernel/1551
new file mode 100644
index 00000000..8bf7fea2
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1551
@@ -0,0 +1,41 @@
+
+qemu-system-arm: ../accel/tcg/cpu-exec.c:917: cpu_loop_exec_tb: Assertion `icount_enabled()' failed.
+Description of problem:
+When starting the guest, the mentioned assertion is triggered very soon:
+```
+qemu-system-arm: ../accel/tcg/cpu-exec.c:917: cpu_loop_exec_tb: Assertion `icount_enabled()' failed.
+```
+I'm able to successfully boot the same image with QEMU 7.2.0.
+
+The last output from the qemu logging with `-d guest_errors,in_asm,int,pcall,cpu` is
+```
+----------------
+IN:
+0x40209100:  e92d4ff0  push     {r4, r5, r6, r7, r8, sb, sl, fp, lr}
+0x40209104:  e28db020  add      fp, sp, #0x20
+0x40209108:  e24b3f49  sub      r3, fp, #0x124
+0x4020910c:  e24ddf43  sub      sp, sp, #0x10c
+0x40209110:  e1a0e00f  mov      lr, pc
+0x40209114:  e3e0f0ff  mvn      pc, #0xff
+
+R00=4021000c R01=4020a5f8 R02=0000000f R03=40209100
+R04=40210018 R05=40210018 R06=4020c000 R07=40002000
+R08=00000000 R09=00000000 R10=00000000 R11=4020d7fc
+R12=00000000 R13=4020d7f0 R14=4020074c R15=40209100
+PSR=2000011f --C- A sys32
+----------------
+IN:
+0xffffff00:  ee1d0f50  mrc      p15, #0, r0, c13, c0, #2
+
+R00=4021000c R01=4020a5f8 R02=0000000f R03=4020d6c8
+R04=40210018 R05=40210018 R06=4020c000 R07=40002000
+R08=00000000 R09=00000000 R10=00000000 R11=4020d7ec
+R12=00000000 R13=4020d6c0 R14=40209118 R15=ffffff00
+PSR=2000011f --C- A sys32
+```
+
+Please note that the L4Re OS uses `mvn pc, #0xff` to switch from EL1 to EL2 (system call).
+Steps to reproduce:
+1. Boot the attached image with the provided command line to trigger the assertion
+Additional information:
+I will attach the bootstrap image to this ticket.
diff --git a/results/classifier/gemma3:12b/kernel/1552549 b/results/classifier/gemma3:12b/kernel/1552549
new file mode 100644
index 00000000..b4e9edfe
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1552549
@@ -0,0 +1,6 @@
+
+qemu-system-i386 verison 2.5.50 fails at lmsw instruction
+
+I cloned qemu source code from github.com, and compiled it on my Kubuntu 15.10 laptop to run my little OS. When booting my little OS, the virtual machine's screen keep blinking, I guess it's the virtual machine rebooting on and on automatically for some unknown reason, but there is no further information shown on Kubuntu's terminal. I'm pretty sure this problem is not caused by my little OS, because it works just fine in qemu-system-i386 version 2.5.0.
+
+I debugged my OS and find this problem happens when executing instruction "lmsw ax". Is this a bug, can anyone help me out?
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1568 b/results/classifier/gemma3:12b/kernel/1568
new file mode 100644
index 00000000..027dd3a9
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1568
@@ -0,0 +1,40 @@
+
+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/gemma3:12b/kernel/1568589 b/results/classifier/gemma3:12b/kernel/1568589
new file mode 100644
index 00000000..8c15e1bd
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1568589
@@ -0,0 +1,17 @@
+
+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
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1570 b/results/classifier/gemma3:12b/kernel/1570
new file mode 100644
index 00000000..c4463183
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1570
@@ -0,0 +1,64 @@
+
+Incorrect memory handling when booting redox
+Description of problem:
+During the boot of redox, I regularly get one of two errors when reading the HPET at base address `0xfed00000`:
+- Incorrect translation from virtual address `0xffff8000fed00108` to random physical addresses, e.g. `0xfec00108`
+- Invalid read at addr 0x0, size 8, region 'hpet', reason: invalid size (min:4 max:4)
+Steps to reproduce:
+1. Build the server version of the redox OS as per [the instructions](https://doc.redox-os.org/book/ch02-05-building-redox.html).
+2. Run the qemu command line with multiple CPUs. The more CPUs the easier it is to reproduce.
+3. The problem will manifest itself as a divide by zero error. See the corresponding [redox bug report](https://gitlab.redox-os.org/redox-os/kernel/-/issues/116).
+Additional information:
+The best evidence I have is a debug line I added to qemu before [the memory_region_dispatch_read line](https://gitlab.com/qemu-project/qemu/-/blob/master/accel/tcg/cputlb.c#L1375):
+
+```
+if ((mr_offset & 0x1ff) == 0x108)  fprintf(stderr, "cputlb io_readx cpu %d addr=%llx mr_offset=%llx mr=%p mr->addr=%llx\n", current_cpu->cpu_index, addr,  mr_offset, mr, mr->addr);
+r = memory_region_dispatch_read(mr, mr_offset, &val, op, full->attrs);
+```
+
+That logs:
+
+```
+cputlb io_readx cpu 0 addr=ffff8000fed00108 mr_offset=108 mr=0x7fefb60d5720 mr->addr=fec00000
+```
+
+The expected physical address is `0xfed00000` instead of `0xfec00000`.
+
+A more extensive log is this one:
+```
+55027@1680283224.671665:memory_region_ops_read cpu 5 mr 0x7f9950890130 addr 0xfed000f0 value 0x949707cc size 4 name 'hpet'      <- ok
+55027@1680283224.671681:memory_region_ops_read cpu 5 mr 0x7f9950890130 addr 0xfed000f4 value 0x0 size 4 name 'hpet'             <- ok
+tlb_set_page_full: vaddr=0000000000474000 paddr=0x000000000536f000 prot=5 idx=1
+...
+tlb_flush_by_mmuidx_async_work: mmu_idx:0xffff
+tlb_flush_by_mmuidx_async_work: mmu_idx:0xffff
+tlb_flush_by_mmuidx_async_work: mmu_idx:0xffff
+tlb_flush_by_mmuidx_async_work: mmu_idx:0xffff
+...
+55027@1680283224.671951:memory_region_ops_read cpu 5 mr 0x7f9950882930 addr 0xfec00108 value 0x0 size 4 name 'ioapic'           <- wrong
+55027@1680283224.671958:memory_region_ops_read cpu 5 mr 0x7f9950882930 addr 0xfec0010c value 0x0 size 4 name 'ioapic'
+55027@1680283224.671967:memory_region_ops_write cpu 2 mr 0x7f994d808d30 addr 0xcf8 value 0x8000fa80 size 4 name 'pci-conf-idx'
+55027@1680283224.671986:memory_region_ops_read cpu 2 mr 0x7f994d808e40 addr 0xcfc value 0x80a805 size 4 name 'pci-conf-data'
+55027@1680283224.672001:memory_region_ops_read cpu 5 mr 0x7f9950882930 addr 0xfec00000 value 0x0 size 4 name 'ioapic'           <- wrong
+55027@1680283224.672010:memory_region_ops_read cpu 5 mr 0x7f9950882930 addr 0xfec00004 value 0x0 size 4 name 'ioapic'
+```
+
+Some observations
+- ~I seem to be the only one having this issue. Perhaps because I am the only one developing on MacOS. Maybe it's because I'm running an older intel mac.~. I managed to reproduce this on a Asus vivobook running linux
+- The redox OS [reads the HPET](https://gitlab.redox-os.org/redox-os/kernel/-/blob/master/src/arch/x86_64/time.rs#L11) at addresses `0xf4`, `0x108`, `0x00` in that order. If I change the order to `0x00`, `0xf4`, `0x108`, the problem goes away.
+- Even if I work around the problem by changing the order of the reads, the OS still randomly crashes. This could be related, but I can only speculate on that right now.
+- Increasing qemu debug logging tends to push the problem to the 4vs8 size problem instead of the incorrect address one. The more logging, the more difficult it is to reproduce.
+- I tried to bisect the issue and found I could only reproduce it after qemu version 5.2. However, the mac build broke during this process so I could not find the causal commit. Between 5.1 and 5.2 the performance is greatly increased though and I suspect whatever changed there caused the issue.
+- I can't reproduce the problem with -smp 1
+- I have seen qemu segfault occasionally, but I didn't look further into it and I don't know if it's related to this issue.
+- I have attempted to rule out a bug in redox. I am fairly certain nothing strange is going on there, but I can't say for sure.
+- When I trigger the incorrect address bug, I mostly get  a base address of `0xfec00000` which is the IO APIC. However, I do occasionally see other addresses too
+- `info tlb` at the time of the fault shows
+   ```
+   ffff8000fd3e6000: 00000000fd3e6000 X--DA---W
+   ffff8000fd3e7000: 00000000fd3e7000 X--DA---W
+   ffff8000fed00000: 00000000fed00000 X--DAC--W
+   ffff8000fee00000: 00000000fee00000 X--DA---W
+   fffffd8000000000: 0000000001e32000 XG-DA---W
+   fffffd8000001000: 0000000001e36000 XG-DA---W
+   ```
diff --git a/results/classifier/gemma3:12b/kernel/1587535 b/results/classifier/gemma3:12b/kernel/1587535
new file mode 100644
index 00000000..5c52c0aa
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1587535
@@ -0,0 +1,31 @@
+
+Incorrect MAS1_TSIZE_SHIFT in ppce500_spin.c causes incorrectly sized TLB.
+
+When e500 PPC is booted multi-core, the non-boot cores are started via
+the spin table.  ppce500_spin.c:spin_kick() calls
+mmubooke_create_initial_mapping() to allocate a 64MB TLB entry, but
+the created TLB entry is only 256KB.
+
+The root cause is that the function computing the size of the TLB
+entry, namely booke206_page_size_to_tlb assumes MAS1.TSIZE as defined
+by latter PPC cores, specifically n to the power of FOUR * 1KB.  The
+result is then used by mmubooke_create_initial_mapping using
+MAS1_TSIZE_SHIFT, but MAS1_TSIZE_SHIFT is defined assuming TLB entries
+are n to the power of TWO * 1KB.  I.e., a difference of shift=7 or
+shift=8.
+
+Simply changing MAS1_TSIZE_SHIFT from 7 to 8 is not appropriate since
+the macro is used elsewhere.
+
+Removing the ">>1" from:
+
+> static inline hwaddr booke206_page_size_to_tlb(uint64_t size)
+> {
+>     return ctz32(size >> 10) >> 1;
+
+and adding an appropriate comment is what I used as a work around:
+
+> static inline hwaddr booke206_page_size_to_tlb(uint64_t size)
+> {
+>     // resulting size is based on MAS1_TSIZE_SHIFT=7 TLB size.
+>     return ctz32(size >> 10);
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1598029 b/results/classifier/gemma3:12b/kernel/1598029
new file mode 100644
index 00000000..69de96b1
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1598029
@@ -0,0 +1,23 @@
+
+failed to boot a customized kernel if emulating Broadwell/Skylake
+
+Hardware: X86-64, Intel(R) Core(TM) i7-6500U( Skylake)
+OS: Linux Mint 18
+Host Kernel: 4.5.7 + PaX/Grsecurity
+Qemu: QEMU emulator version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.2)
+
+[Reproduction Steps]
+1, Install a Debian 8 in the guest
+2, Install a customized kernel( using same config to Debian 8)
+3, Reboot:
+qemu-system-x86_64 -hda debian8-test.img -boot d  -m 2048 -enable-kvm -usb -usbdevice tablet -net nic -net tap,ifname=tap0,script=no -cpu Broadwell -smp 2
+
+or
+
+qemu-system-x86_64 -hda debian8-test.img -boot d  -m 2048 -enable-kvm -usb -usbdevice tablet -net nic -net tap,ifname=tap0,script=no -cpu host -smp 2
+
+[Actual Result]  
+kernel panic or can't login in the system
+
+[Workaround]
+qemu-system-x86_64 -hda debian8-test.img -boot d  -m 2048 -enable-kvm -usb -usbdevice tablet -net nic -net tap,ifname=tap0,script=no -cpu Haswell -smp 2
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1598612 b/results/classifier/gemma3:12b/kernel/1598612
new file mode 100644
index 00000000..ce8e8f50
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1598612
@@ -0,0 +1,19 @@
+
+Windows for Workgroups 3.11 installer crashes with a general protection fault
+
+I used only disk images from here: http://ia801606.us.archive.org/zipview.php?zip=/22/items/IBM_PC_Compatibles_TOSEC_2012_04_23/IBM_PC_Compatibles_TOSEC_2012_04_23.zip
+
+When I try to install Windows for Workgroups 3.11 on either PC DOS 2000 or MS-DOS 6.22, the installer crashes after entering the graphical part with two dialogs containing:
+
+Application Error
+WINSETUP caused a General Protection Fault in module <unknown>0EDF:7011WINSETUP will close.
+
+Application Error
+WINSETUP caused a General Protection Fault in module USER.EXE at 0001:40B6.
+
+And then:
+Standard Mode: Bad Fault in MS-DOS Extender.
+Fault: 000D Stack Dump: 0000 0000 0070
+Raw fault frame: EC=0000 IP=5EF7 CS=037F FL=3087 SP=FFEE SS=02DF
+
+This happens both with and without KVM. I tested with QEMU from Ubuntu 14.04 and 16.04 and recent GIT (ef8757f1fe8095a256ee617e4dbac69d3b33ae94).
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1605611 b/results/classifier/gemma3:12b/kernel/1605611
new file mode 100644
index 00000000..4ec706c4
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1605611
@@ -0,0 +1,49 @@
+
+memsave returns invalid addr when trying to read a 64 bits address
+
+I am trying to read the first 16 bytes of the System Process on a Windows XP x64 SP2 using the memsave monitor command.
+
+I cloned the latest release of QEMU, v2.6.0, configured it with 
+./configure --target-list=i386-softmmu,x86_64-softmmu --enable-sdl
+and compiled it.
+
+I first tried to use memsave against Windows XP SP3 32 bits.
+This is the procedure i used :
+
+1 - start the VM with :
+./i386-softmmu/qemu-system-i386 --enable-kvm -monitor stdio -hda ~/vm/winxp.qcow2
+and wait for the desktop
+2 - take a physical memory dump with :
+pmemsave 0 134217728 dump.raw
+3 - call rekall on this memory dump to identify running processes :
+rekall -f dump.raw pslist
+_EPROCESS          Name          PID   PPID   Thds    Hnds    Sess  Wow64           Start                     Exit          
+---------- -------------------- ----- ------ ------ -------- ------ ------ ------------------------ ------------------------
+0x80e8fa00 System                   4      0     46      148      - False  -                        -                       
+4 - read the first 16 bytes of the System PROCESS struct :
+memsave 0x80e8fa00 16 system
+5 - check the content with hexdump :
+00000000  03 00 1b 00 00 00 00 00  08 fa e8 80 08 fa e8 80
+you can recognize here the beginning of an EPROCESS struct.
+
+So on a 32 bits Windows XP OS, it works.
+
+But when i tried on Windows XP SP2 64 bits, rekall gave me the following output :
+  _EPROCESS            Name          PID   PPID   Thds    Hnds    Sess  Wow64           Start                     Exit          
+-------------- -------------------- ----- ------ ------ -------- ------ ------ ------------------------ ------------------------
+0xfadffd71d040 System                   4      0     51      398      - False  -                        -                       
+And when i tried to read the memory with memsave :
+memsave 0xfadffd71d040 16 system
+
+I had the following error :
+Invalid addr 0x0000fadffd71d040/size 16 specified
+
+This address is supposed to be valid because I am reading the System EProcess struct, which should not be in the paged pool memory I think.
+Also i disabled the paging file to be sure and the bug is still present.
+
+Furthermore the bug is reproducible on the latest QEMU (01a720125f5e2f0a23d2682b39dead2fcc820066).
+
+Can you confirm that this is a bug ?
+Should i check something ?
+
+Thanks !
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1606 b/results/classifier/gemma3:12b/kernel/1606
new file mode 100644
index 00000000..0934e0aa
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1606
@@ -0,0 +1,30 @@
+
+riscv: fence.i is not functional
+Description of problem:
+The attached user-level test is designed to do the following (in iteration):
+
+  - Thread P0 on CPU0 changes some text/code, while
+
+  - Thread P1 on CPU1 checks/reads the code, fence.i, then executes the same code.
+
+Results (in stdout) indicates that CPU1 has read the new code (1:x5=a009) but executed the old one (1:x7=1) (against the specification).
+Steps to reproduce:
+1. echo 2 > /proc/sys/vm/nr_hugepages
+2. ./CoRF+fence.i
+Additional information:
+Example output:
+```[CoRF+fence.i.c](/uploads/c150ca0910783cc4bfc3886789b64c28/CoRF+fence.i.c)
+Test CoRF+fence.i Allowed
+Histogram (4 states)
+25784  :>1:x5=0xa009; 1:x7=2;
+24207  *>1:x5=0xa009; 1:x7=1;   <--  THIS LINE
+8      :>1:x5=0xa019; 1:x7=1;
+1      :>1:x5=0xa019; 1:x7=2;
+Ok
+Witnesses
+Positive: 24207 Negative 25793
+Condition exists (1:x5=0xa009 /\ 1:x7=1) is  validated
+Observation CoRF+fence.i Sometimes 24207 25793
+Time CoRF+fence.i 0.85
+Hash=
+```
diff --git a/results/classifier/gemma3:12b/kernel/1613817 b/results/classifier/gemma3:12b/kernel/1613817
new file mode 100644
index 00000000..a80d8e11
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1613817
@@ -0,0 +1,57 @@
+
+x86: ret, lret and iret with noncanonical IP saves wrong IP on the exception stack
+
+This test program:
+
+# compile with: gcc -nostartfiles -nostdlib
+_start:         .globl  _start
+                mov     %ss,%eax
+                push    %rax
+                push    %rsp
+                pushf
+                mov     %cs,%eax
+                push    %rax
+                mov     $0x1234567812345678,%rax
+                push    %rax
+//qemu bug: ip=1234567812345678, should be ip=0000000000400abc:
+                iretq
+1:
+                jmp     1b
+
+should segfault on IRET instruction because return address on stack is invalid
+(it is not canonical). And it does, both on native CPU and in qemu.
+But there is a difference: on native CPU, it fails before instruction is executed,
+IOW: saved IP points to the failed IRET:
+
+# strace -i ./bad_ip_in_iret 
+[00007fa609805d57] execve("./bad_ip_in_iret", ["./bad_ip_in_iret"], [/* 54 vars */]) = 0
+[00000000004000e7] --- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL, si_addr=0} ---
+ ^^^^^^^^^^^^^^^^-NOTE THIS
+[????????????????] +++ killed by SIGSEGV (core dumped) +++
+
+
+In qemu, evidently instruction succeeds, and then emulated CPU throws an exception because fetching instructions from non-canonical addresses is not allowed:
+
+/ # strace -i ./bad_ip_in_iret
+[000000000041a790] execve("./bad_ip_in_iret", ["./bad_ip_in_iret"], [/* 5 vars */]) = 0
+[1234567812345678] --- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL, si_addr=0} ---
+ ^^^^^^^^^^^^^^^^-NOTE THIS
+[????????????????] +++ killed by SIGSEGV +++
+Segmentation fault
+
+Thus, the emulation is not the same as real CPU.
+
+This is not specific to IRET, the same happens with "far return" LRET,
+and with ordinary RET instructions as well.
+In qemu:
+
+/ # strace -i ./bad_ip_in_lret
+[000000000041a790] execve("./bad_ip_in_lret", ["./bad_ip_in_lret"], [/* 5 vars */]) = 0
+[1234567812345678] --- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL, si_addr=0} ---
+[????????????????] +++ killed by SIGSEGV +++
+Segmentation fault
+/ # strace -i ./bad_ip_in_ret
+[000000000041a790] execve("./bad_ip_in_ret", ["./bad_ip_in_ret"], [/* 5 vars */]) = 0
+[1234567812345678] --- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL, si_addr=0} ---
+[????????????????] +++ killed by SIGSEGV +++
+Segmentation fault
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1617929 b/results/classifier/gemma3:12b/kernel/1617929
new file mode 100644
index 00000000..88eb1090
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1617929
@@ -0,0 +1,51 @@
+
+qemu hangs in pselect syscall
+
+I'm using git commit d75aa4372f0414c9960534026a562b0302fcff29 (v2.7.0-rc4) configured with;
+    --enable-linux-user \
+    --disable-system \
+    --disable-tools \
+    --disable-guest-agent \
+    --static --disable-linux-aio \
+    --disable-fdt \
+    --without-pixman \
+    --disable-blobs \
+Stable version (v2.6.0) also have the same problem.
+
+In a chroot environment I ran below command-line to compile some things, different sources each time.
+    /usr/bin/qemu-arm -0 /usr/bin/edje_cc /usr/bin/edje_cc -id /home/abuild/rpmbuild/BUILD/org.tizen.browser-1.6.2/services/SimpleUI/images_mob/ -DBROWSER_RESOLUTION_720x1280=1 -DPROFILE_MOBILE=1 /home/abuild/rpmbuild/BUILD/org.tizen.browser-1.6.2/services/SimpleUI/edc/TextPopup_mob.edc /home/abuild/rpmbuild/BUILD/org.tizen.browser-1.6.2/build-tizen/services/SimpleUI/720x1280_TextPopup.edj
+
+Here is back trace with gdb;
+#0  safe_syscall_end () at /usr/src/debug/qemu-2.6.94/linux-user/host/i386/safe-syscall.inc.S:78
+#1  0x60049370 in safe_pselect6 (nfds=10, readfds=0xffa31b5c, writefds=0xffa31bdc, exceptfds=0xffa31c5c, timeout=0x0, sig=0x0)
+    at /usr/src/debug/qemu-2.6.94/linux-user/syscall.c:855
+#2  0x6004b2fe in do_select (n=10, rfd_addr=1082122232, wfd_addr=1082122360, efd_addr=1082122488, target_tv_addr=0)
+    at /usr/src/debug/qemu-2.6.94/linux-user/syscall.c:1386
+#3  0x6005e5ba in do_syscall (cpu_env=0x640d0454, num=142, arg1=10, arg2=1082122232, arg3=1082122360, arg4=1082122488, arg5=0, arg6=1087473216, arg7=0, 
+    arg8=0) at /usr/src/debug/qemu-2.6.94/linux-user/syscall.c:9690
+#4  0x60045def in cpu_loop (env=0x640d0454) at /usr/src/debug/qemu-2.6.94/linux-user/main.c:876
+#5  0x60047640 in main (argc=10, argv=0xffa33c84, envp=0xffa33cb0) at /usr/src/debug/qemu-2.6.94/linux-user/main.c:4817
+
+Attached core file taken from gdb. To see the stack frame, you could try; 
+$ tar -xf reproduced_118_04.tar.bz2; gdb --core core.1823 qemu-arm
+
+And recent strace log for PID 1823(stucked one);
+79965 [  313s] 1823 :0x8e _newselect(10,[9,3,],[],[],NULL)
+79966 [  313s]  ==>[pselect6(0xa)=]
+79967 [  313s]  [pselect6=0x1]<==
+79968 [  313s] 1823 :0x8e _newselect(10,[9,],[],[],NULL)
+79969 [  313s] 1823 :0x8e =>  = 0x00000001 ([9,],[],[],NULL)
+79970 [  313s] 1823 :0xfc epoll_wait(3,1082121456,32,0,1082121456,3)
+79971 [  313s] 1823 :0xfc epoll_wait(3,1082121456,32,0,1082121456,3)
+79972 [  313s] 1823 :0xfc =>  = 0
+79973 [  313s] 1823 :0x3 read(9,0x407fdeec,16)
+79974 [  313s] 1823 :0x3 read(9,0x407fdeec,16)
+79975 [  313s] 1823 :0x3 =>  = 8
+79976 [  313s] 1823 :0x107 clock_gettime(1,1082122120,0,1082829144,1082827588,0)
+79977 [  313s] 1823 :0x107 clock_gettime(1,1082122120,0,1082829144,1082827588,0)
+79978 [  313s] 1823 :0x107 =>  = 0
+79979 [  313s] 1823 :0x8e _newselect(10,[9,3,],[],[],NULL)
+79980 [  313s]  ==>[pselect6(0xa)=]
+
+I'm using 64-bit Ubuntu with kernel release Linux 3.19.0-25-generic #26~14.04.1-Ubuntu.
+Reproducibility is low. One occurrence out of 50+ trials.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1622547 b/results/classifier/gemma3:12b/kernel/1622547
new file mode 100644
index 00000000..7282d6a8
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1622547
@@ -0,0 +1,29 @@
+
+qemu-system-sparc fatal error Trap 0x29 on Solaris 2.6
+
+When trying to install Solaris 2.6 from original CDROM, qemu fail with the following error :
+
+qemu: fatal: Trap 0x29 while interrupts disabled, Error state
+pc: f0041280  npc: f0041284
+%g0-7: 00000000 f0281800 08000000 ffffffff 00000000 f0243b88 00000001 f0244020
+%o0-7: 40400ce2 40400ce2 00000000 404000e2 f0243b88 00000000 f023ffd8 f0057914 
+%l0-7: 40000cc2 f009645c f0096460 00000002 00000209 00000004 00000007 f023ff90 
+%i0-7: 00000042 404000e3 00000000 404000e3 e0000000 f028192a f0240038 f0096448 
+%f00:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%f08:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%f16:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%f24:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
+psr: 40400cc2 (icc: -Z-- SPE: SP-) wim: 00000002
+fsr: 00000000 y: 00000000
+
+The command line was :
+
+qemu-system-sparc -nographic -bios ./openbios-sparc32 -M SS-20 -hda ./36G.disk -m 512 -cdrom Solaris_2.6_Software_05_98.img -boot d -serial telnet:0.0.0.0:3000,server -smp 2,cores=2 -monitor null
+
+It fails with a similar output when using bios ss20_v2.25_rom.
+
+▶ qemu-system-sparc --version
+QEMU emulator version 2.7.0, Copyright (c) 2003-2016 Fabrice Bellard and the QEMU Project developers
+
+▶ uname -a
+Linux xxx 4.7.1-1-ARCH #1 SMP PREEMPT Wed Aug 17 08:13:35 CEST 2016 x86_64 GNU/Linux
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1624896 b/results/classifier/gemma3:12b/kernel/1624896
new file mode 100644
index 00000000..bc465a87
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1624896
@@ -0,0 +1,24 @@
+
+[PPC] SegFault due to Stack Overflow in E500
+
+
+I am getting a Segmentation Fault while simulating a PowerPC e500. I've tried to debug the problem and I've found that it occurs when you have a 0 value decrementer. The function trace is the following:
+
+1) __cpu_ppc_store_decr (ppc.c) is called with value = 0 and raise_excp=booke_decr_cb;
+2) Since value < 3, booke_decr_cb is called;
+3) booke_decr_cb then calls booke_update_irq() and cpu_ppc_store_decr();
+4) cpu_ppc_store_decr calls __cpu_ppc_store_decr
+
+You're stuck on this infinite cycle until your stack overflows eventually.
+
+Command Line:
+qemu-system-ppc -cpu e500v2 -d guest_errors,unimp -m 2048 -M ppce500 -nographic -bios ../cc/share/qem
+u/u-boot.e500 -kernel XKYAPP.exe
+
+Platform where the bug occured: Bash ubuntu on Windows;
+
+Revision where the bug was found: e3571ae30cd26d19efd4554c25e32ef64d6a36b3 (16 Set 2016)
+
+
+
+Thanks!
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1625295 b/results/classifier/gemma3:12b/kernel/1625295
new file mode 100644
index 00000000..4f9597bc
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1625295
@@ -0,0 +1,9 @@
+
+qemu-arm dies with libarmmem inside ld.so.preload
+
+When running raspbian inside qemu,the user has to first comment out the following line from /etc/ld.so.conf:
+
+/usr/lib/arm-linux-gnueabihf/libarmmem.so
+
+
+Will future qemus will be able to work without changine /etc/ld.so.conf ?
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1629 b/results/classifier/gemma3:12b/kernel/1629
new file mode 100644
index 00000000..af911fe4
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1629
@@ -0,0 +1,2 @@
+
+qem-img Heap Buffer Overflow
diff --git a/results/classifier/gemma3:12b/kernel/1645287 b/results/classifier/gemma3:12b/kernel/1645287
new file mode 100644
index 00000000..dcd12061
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1645287
@@ -0,0 +1,19 @@
+
+Option "split" does not available for kernel_irqchip flag in qemu-system-x86_64
+
+On releases prior to Yakkety, the "split" option is not available for kernel_irqchip flag in qemu-system-x86_64.
+
+Yakkety:
+kernel_irqchip=on|off|split controls accelerated irqchip support (default=off)
+
+
+Xenial:
+kernel_irqchip=on|off controls accelerated irqchip support
+
+Trusty:
+kernel_irqchip=on|off controls accelerated irqchip support
+
+Precise:
+kernel_irqchip=on|off controls accelerated irqchip support
+
+It will be great to have this option, as we will need this for some kvm-unit-tests for SRU
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1648 b/results/classifier/gemma3:12b/kernel/1648
new file mode 100644
index 00000000..d9f20785
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1648
@@ -0,0 +1,59 @@
+
+linux-user: incorrect alignment of sigframe::pretcode & rt_sigframe::pretcode cause crash
+Description of problem:
+Corrent Print Result:
+
+sp: cdd3b4e8
+
+SUCCEEDED!
+
+qemu-x86_64 Print Result:
+
+sp: 2804170
+
+qemu: uncaught target signal 11 (Segmentation fault) - core dumped
+
+Segmentation fault
+
+Reason of Bug:
+
+sigframe::pretcode & rt_sigframe::pretcode must align of 16n-sizeof(void*) instead of 16n, Because rsp align of 16n before instruction "call" in caller, After "call", push address of "call" in caller. sp of begin in callee is 16n-sizeof(void*)
+
+For example on x86_64:
+
+reference to "qemu/linux-user/i386/signal.c"
+
+```
+# define TARGET_FPSTATE_FXSAVE_OFFSET 0
+
+struct rt_sigframe {
+    abi_ulong pretcode;
+    struct target_ucontext uc;
+    struct target_siginfo info;
+    struct target_fpstate fpstate QEMU_ALIGNED(16);
+};
+#define TARGET_RT_SIGFRAME_FXSAVE_OFFSET (                                 \
+    offsetof(struct rt_sigframe, fpstate) + TARGET_FPSTATE_FXSAVE_OFFSET)
+```
+
+offsetof(struct rt_sigframe, fpstate) align of 16
+
+TARGET_FPSTATE_FXSAVE_OFFSET is 0
+
+TARGET_RT_SIGFRAME_FXSAVE_OFFSET is 16n, also alignment of fxsave is 64
+
+so address of rt_sigframe::pretcode is 16n instead of 16n - sizeof(void*), It is incorect!
+
+Fix the bug:
+
+```
+struct rt_sigframe {
+    abi_ulong pretcode;
+    struct target_ucontext uc;
+    struct target_siginfo info;
+    abi_ulong unused QEMU_ALIGNED(16);
+    struct target_fpstate fpstate;
+};
+```
+
+offsetof(struct rt_sigframe, fpstate) is 16n+8, so address of rt_sigframe::pretcode is 16n-8 on x86_64.
diff --git a/results/classifier/gemma3:12b/kernel/1650 b/results/classifier/gemma3:12b/kernel/1650
new file mode 100644
index 00000000..fd369bb1
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1650
@@ -0,0 +1,15 @@
+
+Consider doing runtime detection of MAP_FIXED_NOREPLACE
+Description of problem:
+```
+qemu-i386-static: Unable to reserve 0xfffff000 bytes of virtual address space at 0x1000 (Operation not supported) for use as guest address space (check your virtual memory ulimit setting, min_mmap_addr or reserve less using -R option)
+```
+strace says
+```
+ mmap(0x1000, 4294963200, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_NORESERVE|MAP_FIXED_NOREPLACE, -1, 0) = -1 EOPNOTSUPP (Operation not supported)
+```
+Steps to reproduce:
+1. `apt install qemu-i386-static 32subsystem`
+2. `strace qemu-i386-static /opt/32/bin/as`
+Additional information:
+Repeating the strace call in a minimal C program gives the same errno as expected -- the kernel is only 4.4. The problem here is that qemu only does `MAP_FIXED_NOREPLACE` feature detection at build-time via a `#ifndef` and even that behavior is poorly documented. Maybe do something at runtime?
diff --git a/results/classifier/gemma3:12b/kernel/1652 b/results/classifier/gemma3:12b/kernel/1652
new file mode 100644
index 00000000..d19750e4
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1652
@@ -0,0 +1,33 @@
+
+make check failed about qemu@master on debian10_aarch64
+Description of problem:
+make check failed about qemu@master on debian10_aarch64
+Steps to reproduce:
+1../configure
+2.make -j16
+3.make -j16 check
+Additional information:
+error:
+>>> QTEST_QEMU_STORAGE_DAEMON_BINARY=./storage-daemon/qemu-storage-daemon QTEST_QEMU_IMG=./qemu-img G_TEST_DBUS_DAEMON=/home/stage/root/spack-stage-qemu-master-d6wsqaf6ydt7c6frhxqd3nyqhh72vz7v/spack-src/tests/dbus-vmstate-daemon.sh MALLOC_PERTURB_=105 QTEST_QEMU_BINARY=./qemu-system-aarch64 /home/stage/root/spack-stage-qemu-master-d6wsqaf6ydt7c6frhxqd3nyqhh72vz7v/spack-src/build/tests/qtest/migration-test --tap -k
+――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― ✀  ―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
+stderr:
+Broken pipe
+../tests/qtest/libqtest.c:184: kill_qemu() tried to terminate QEMU process but encountered exit status 1 (expected 0)
+
+
+TAP parsing error: Too few tests run (expected 18, got 0)
+(test program exited with status code -6)
+――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
+
+190/627 qemu:qtest+qtest-aarch64 / qtest-aarch64/arm-cpu-features                          ERROR           0.34s   killed by signal 6 SIGABRT
+>>> QTEST_QEMU_STORAGE_DAEMON_BINARY=./storage-daemon/qemu-storage-daemon QTEST_QEMU_IMG=./qemu-img G_TEST_DBUS_DAEMON=/home/stage/root/spack-stage-qemu-master-d6wsqaf6ydt7c6frhxqd3nyqhh72vz7v/spack-src/tests/dbus-vmstate-daemon.sh MALLOC_PERTURB_=115 QTEST_QEMU_BINARY=./qemu-system-aarch64 /home/stage/root/spack-stage-qemu-master-d6wsqaf6ydt7c6frhxqd3nyqhh72vz7v/spack-src/build/tests/qtest/arm-cpu-features --tap -k
+――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― ✀  ―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
+stderr:
+qemu-system-aarch64: Failed to retrieve host CPU features
+Broken pipe
+../tests/qtest/libqtest.c:184: kill_qemu() tried to terminate QEMU process but encountered exit status 1 (expected 0)
+
+
+TAP parsing error: Too few tests run (expected 5, got 1)
+(test program exited with status code -6)
+――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
diff --git a/results/classifier/gemma3:12b/kernel/1654 b/results/classifier/gemma3:12b/kernel/1654
new file mode 100644
index 00000000..77d43a00
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1654
@@ -0,0 +1,82 @@
+
+Memory out of bounds access vulnerability when guest accesses Block Limits information of SCSI devices
+Description of problem:
+When a guest uses a Linux kernel version 5.19 or higher and uses an scsi device, there will be a memory access violation, which can be clearly seen when ASAN is turned on.
+
+**reason：**
+Linux kernel 5.19 merge commit：
+
+https://github.com/torvalds/linux/commit/c92a6b5d63359dd6d2ce6ea88ecd8e31dd769f6b
+
+The Linux kernel will first issue a header request to obtain the VPD length before obtaining the VPD information. The BUF for obtaining the VPD length is less than 8 bytes. However, QEMU regards the header for obtaining the VPD length as obtaining all VPD information, and a memory access violation occurs when writing information to BUF.
+
+The specific memory out of bounds information is as follows:
+==12430==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
+
+==12430==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 
+0x7fffebc1d000; bottom 0x7f61115ee000; size: 0x009eda62f000 (682268749824)
+
+False positive error reports may follow
+
+==12430==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60200024d858 at pc 0x55767513791c bp 0x7f6111fcddc0 sp 0x7f6111fcddb0
+
+WRITE of size 4 at 0x60200024d858 thread T0
+
+    #0 0x55767513791b in stl_he_p /root/hci/qemu/qemu-5.0.0/include/qemu/bswap.h:357
+
+    #1 0x55767513791b in stl_be_p /root/hci/qemu/qemu-5.0.0/include/qemu/bswap.h:464
+
+    #2 0x55767513791b in scsi_handle_inquiry_reply hw/scsi/scsi-generic.c:173
+
+    #3 0x55767513791b in scsi_read_complete hw/scsi/scsi-generic.c:318
+
+    #4 0x55767545d7c6 in blk_aio_complete block/block-backend.c:1425
+
+    #5 0x557675544d79 in coroutine_trampoline util/coroutine-ucontext.c:115
+
+    #6 0x7f611b9f14df  (/lib/x86_64-linux-gnu/libc.so.6+0x5b4df)
+
+0x60200024d858 is located 4 bytes to the right of 4-byte region [0x60200024d850,0x60200024d854)
+
+allocated by thread T0 here:
+
+    #0 0x557674a987f2 in malloc (/sf/bin/qemu-system-x86_64+0x7827f2)
+
+    #1 0x7f6120141d41 in g_malloc (/usr/lib/libglib256-2.0.so.0+0x61d41)
+
+    #2 0x557675137bb4 in scsi_send_command hw/scsi/scsi-generic.c:459
+
+    #3 0x55767513e902 in scsi_req_enqueue hw/scsi/scsi-bus.c:836
+
+    #4 0x557674c5f26e in virtio_scsi_handle_cmd_req_submit /root/hci/qemu/qemu-5.0.0/hw/scsi/virtio-scsi.c:589
+
+    #5 0x557674c5f26e in virtio_scsi_handle_cmd_vq /root/hci/qemu/qemu-5.0.0/hw/scsi/virtio-scsi.c:634
+
+    #6 0x557674c61089 in virtio_scsi_data_plane_handle_cmd /root/hci/qemu/qemu-5.0.0/hw/scsi/virtio-scsi-dataplane.c:60
+
+    #7 0x557674c9a520 in virtio_queue_notify_aio_vq /root/hci/qemu/qemu-5.0.0/hw/virtio/virtio.c:2338
+
+    #8 0x55767552c7c4 in aio_dispatch_handler util/aio-posix.c:328
+
+SUMMARY: AddressSanitizer: heap-buffer-overflow /root/hci/qemu/qemu-5.0.0/include/qemu/bswap.h:357 stl_he_p
+Steps to reproduce:
+1. QEMU Enable ASAN
+2. Use a guest with a Linux kernel version greater than 5.19 and mount an scsi physical device
+3. Upon startup, memory out of bounds access can be detected
+Additional information:
+At present, I have made some simple modifications, but I am not sure if this is the best solution and can serve as a reference.
+
+Make a judgment on buflen, ignore the header information issued by the Linux kernel, and write the VPD information when issuing the actual instruction to obtain VPD information.
+
+hw/scsi/scsi-generic.c:scsi_handle_inquiry_reply
+
+```
+if (r->buflen >= 12) {
+    stl_be_p(&r->buf[8], max_transfer);
+}
+if (r->buflen >= 16){
+    /* Also take care of the opt xfer len. */
+    stl_be_p(&r->buf[12],
+        MIN_NON_ZERO(max_transfer, ldl_be_p(&r->buf[12])));
+}
+```
diff --git a/results/classifier/gemma3:12b/kernel/1657538 b/results/classifier/gemma3:12b/kernel/1657538
new file mode 100644
index 00000000..93cc8a17
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1657538
@@ -0,0 +1,31 @@
+
+qemu 2.7.x 2.8 softmmu dont work on BE machine 
+
+Build on Be machine qemu 2.7.1 and 2.8 in pure softmmu (tgc) dont work on big endian hardware .
+tested with ppc-softmmu,i386-softmmu,arm-softmmu same result:
+
+with :
+ ./qemu-system-i386 
+Gtk-Message: Failed to load module "overlay-scrollbar"
+qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a0000
+This usually means one of the following happened:
+
+(1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine)
+(2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end
+(3) Your guest kernel has a bug and crashed by jumping off into nowhere
+
+This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine.
+If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point.
+
+Execution cannot continue; stopping here.
+
+
+I try to add the -L option with ../pc-bios/bios.bin 
+and have the same result.
+
+note the ppc-softmmu and ppc64-softmmu work in kvm mode only emulated mode have issue.
+
+
+tested on my hardware a  Qriq P5040 and G5 4x970MP with Ubuntu Mate 16.10 
+thanks
+Luigi
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1658 b/results/classifier/gemma3:12b/kernel/1658
new file mode 100644
index 00000000..64b04622
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1658
@@ -0,0 +1,61 @@
+
+Zephyr TF-M IPC example triggers failed assertion !arm_feature(env, ARM_FEATURE_M) on recent Qemu
+Description of problem:
+I can't run the TrustedFirmware-M IPC example in the Zephyr repo with recent Qemu (in particular v8.0.0).
+
+By bisecting, I got the last commit OK : v7.2.0-351-gfaa1451e7b
+
+```
+$ qemu-system-arm -M mps2-an521 -device loader,file=tfm_merged.hex -serial stdio
+[INF] Beginning TF-M provisioning
+[WRN] TFM_DUMMY_PROVISIONING is not suitable for production! This device is NOT SECURE
+[Sec Thread] Secure image initializing!
+Booting TF-M 8209cb2ed
+Creating an empty ITS flash layout.
+Creating an empty PS flash layout.
+[INF][Crypto] Provisioning entropy seed... complete.
+*** Booting Zephyr OS build zephyr-v3.3.0-4041-g7ba5ecf451ef ***
+TF-M IPC on mps2_an521_ns
+The version of the PSA Framework API is 257.
+The PSA Crypto service minor version is 1.
+Generating 256 bytes of random data:
+71 03 DD 50 8E E5 00 C7 E0 61 7B EB 77 15 E9 38 
+E9 A8 7D 0C 51 23 76 9F C3 61 E9 8B 8A 67 BD 14 
+73 A3 2C 6E E5 8C E3 19 53 6B 50 55 A8 A7 F4 7B 
+56 03 60 AA 48 B6 DF 04 33 56 BE 84 43 FA 4E AC 
+D7 6E 2E 2E 1D 7E 46 69 D5 9B B0 42 5C 54 E4 09 
+73 9E 4F 55 F8 3E 05 9E A3 DE 46 D3 E4 02 B0 9C 
+F3 21 9F 20 85 74 34 07 19 79 07 B8 02 B5 0E 90 
+74 21 BE B5 09 4C D7 20 D8 43 F7 72 23 1C F0 3E 
+77 7B D3 70 29 72 69 D3 7F 1F 61 16 12 73 D5 89 
+C5 8B D1 A3 7B 4B FD F5 11 C2 B1 9A C0 A5 F9 7B 
+16 3D 98 17 66 FE E9 F4 FE 37 76 62 E0 E6 83 99 
+69 26 41 CD FF 0C 44 AC F9 F4 91 B8 CA 63 5E 1D 
+B9 C4 38 D6 0C 11 19 1B 94 BE C9 4F EC 2E 5A 05 
+3F 72 5F 41 44 3C 91 39 AC 2D 50 75 DF FD D3 11 
+39 F2 43 18 D7 69 B0 A3 99 0C C0 6E 83 84 1A A8 
+B0 37 6C 8E 32 B2 8E 4F AA 12 97 09 09 87 D3 FD 
+qemu-system-arm: terminating on signal 2
+```
+
+But after 452c67a427, for example v8.0.0-918-g6972ef1440, I get :
+
+```
+$ qemu-system-arm -M mps2-an521 -device loader,file=tfm_merged.hex -serial stdio
+[INF] Beginning TF-M provisioning
+[WRN] TFM_DUMMY_PROVISIONING is not suitable for production! This device is NOT SECURE
+[Sec Thread] Secure image initializing!
+Booting TF-M 8209cb2ed
+Creating an empty ITS flash layout.
+Creating an empty PS flash layout.
+[INF][Crypto] Provisioning entropy seed... complete.
+*** Booting Zephyr OS build zephyr-v3.3.0-4041-g7ba5ecf451ef ***
+TF-M IPC on mps2_an521_ns
+qemu-system-arm: ../target/arm/cpu.h:2396: arm_is_secure_below_el3: Assertion `!arm_feature(env, ARM_FEATURE_M)' failed.
+Aborted
+```
+Steps to reproduce:
+1. Build the Zephyr tfm_merged.hex file from Zephyr 7ba5ecf451 https://github.com/zephyrproject-rtos/zephyr/commit/7ba5ecf451ef29f96b30dbe5f0e54c1865839093 : ``west -v build -p -b mps2_an521_ns ./samples/tfm_integration/tfm_ipc``
+2. Build qemu-system-arm and run : ``qemu-system-arm -M mps2-an521 -device loader,file=tfm_merged.hex -serial stdio``
+Additional information:
+More info to build Zephyr TF-M IPC example on the official repo https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/tfm_integration/tfm_ipc
diff --git a/results/classifier/gemma3:12b/kernel/1658120 b/results/classifier/gemma3:12b/kernel/1658120
new file mode 100644
index 00000000..4f75339e
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1658120
@@ -0,0 +1,26 @@
+
+building with gcc-aarch64-linux-gnu
+
+Hi, while trying to build qemu v2.8.0 with gcc-aarch64-linux-gnu cross-compiler I'm getting the following :
+
+
+In file included from /usr/include/x86_64-linux-gnu/sys/syscall.h:31:0,
+                 from /root/qemu/util/compatfd.c:21:
+/root/qemu/util/compatfd.c: In function 'qemu_signalfd':
+/root/qemu/util/compatfd.c:103:19: error: '__NR_signalfd' undeclared (first use in this function)
+     ret = syscall(SYS_signalfd, -1, mask, _NSIG / 8);
+                   ^
+/root/qemu/util/compatfd.c:103:19: note: each undeclared identifier is reported only once for each function it appears in
+/root/qemu/rules.mak:59: recipe for target 'util/compatfd.o' failed
+make: *** [util/compatfd.o] Error 1
+
+
+I had configured it with :
+
+../configure --target-list=x86_64-linux-user --static --cpu=aarch64
+
+And I'm on :
+
+Linux ubuntu-512mb-fra1-01 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
+
+Thanks
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1662600 b/results/classifier/gemma3:12b/kernel/1662600
new file mode 100644
index 00000000..b3c9bb87
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1662600
@@ -0,0 +1,29 @@
+
+error while building from source on Ubuntu 16.04
+
+I'm trying to build Qemu from source (from git) as specified here: http://www.qemu-project.org/download/#source
+
+Here is the git commit hash for the source: 7d2c6c95511e42dffe2b263275e09957723d0ff4
+
+During the 'make' step, I get the following error:
+
+migration/rdma.c: In function ‘qemu_rdma_dump_id’:
+migration/rdma.c:749:21: error: ‘struct ibv_port_attr’ has no member named ‘link_layer’
+migration/rdma.c:750:22: error: ‘struct ibv_port_attr’ has no member named ‘link_layer’
+migration/rdma.c:750:37: error: ‘IBV_LINK_LAYER_INFINIBAND’ undeclared (first use in this function)
+migration/rdma.c:750:37: note: each undeclared identifier is reported only once for each function it appears in
+migration/rdma.c:751:24: error: ‘struct ibv_port_attr’ has no member named ‘link_layer’
+migration/rdma.c:751:39: error: ‘IBV_LINK_LAYER_ETHERNET’ undeclared (first use in this function)
+migration/rdma.c: In function ‘qemu_rdma_broken_ipv6_kernel’:
+migration/rdma.c:850:26: error: ‘struct ibv_port_attr’ has no member named ‘link_layer’
+migration/rdma.c:850:41: error: ‘IBV_LINK_LAYER_INFINIBAND’ undeclared (first use in this function)
+migration/rdma.c:852:33: error: ‘struct ibv_port_attr’ has no member named ‘link_layer’
+migration/rdma.c:852:48: error: ‘IBV_LINK_LAYER_ETHERNET’ undeclared (first use in this function)
+migration/rdma.c:891:18: error: ‘struct ibv_port_attr’ has no member named ‘link_layer’
+make: *** [migration/rdma.o] Error 1
+
+I searched around a bit, my problem seems related to this: https://patchwork.kernel.org/patch/992952/
+
+That issue makes me think my libibverbs may be out of date, but I checked and I have libibverbs-dev installed.  Is that the correct version?
+
+FYI, I installed libibverbs-dev as suggested here: http://wiki.qemu-project.org/index.php/Hosts/Linux#Recommended_additional_packages
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1667401 b/results/classifier/gemma3:12b/kernel/1667401
new file mode 100644
index 00000000..d2ecbb7c
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1667401
@@ -0,0 +1,68 @@
+
+qemu-ppc segfaults(SIGSEGV) on pthread_create
+
+qemu-ppc running on x86-64 hardware leads to a segfault when running the
+attached program (test.c). It simply creates a pthread, joins it and exits.
+
+It was compiled as follows on a Debian testing system:
+> powerpc-linux-gnuspe-gcc-6 -static -Wall -g -o test -pthread test.c
+
+Sample execution (expected output is "Hello - World!"):
+> qemu-ppc -cpu e500 ./test
+[...output...]
+Hello - qemu-ppc: /build/qemu-_M2UL5/qemu-2.8+dfsg/translate-all.c:175: tb_lock: Assertion `!have_tb_lock' failed.
+qemu-ppc: /build/qemu-_M2UL5/qemu-2.8+dfsg/translate-all.c:175: tb_lock: Assertion `!have_tb_lock' failed.
+[1]    25747 segmentation fault  qemu-ppc -cpu e500 test
+[...end output...]
+
+The same behavior is observed when running on a PPC 604:
+
+> powerpc-linux-gnu-gcc -Wall -g -o test -pthread test.c
+> qemu-ppc ./test
+[... as above ...]
+
+Version information:
+powerpc-linux-gnu-gcc -v => gcc version 6.3.0 20170124 (Debian 6.3.0-5)
+qemu-ppc -version => qemu-ppc version 2.8.0(Debian 1:2.8+dfsg-2)
+
+The same experiment was conducted again using qemu from the git repository (commit: 796b288f7be875045670f963ce99991b3c8e96ac):
+~/tools/qemu/build/ppc-linux-user/qemu-ppc -version => qemu-ppc version 2.8.50 (v2.8.0-1417-g796b288f7b-dirty)
+[...output...]
+Hello - qemu-ppc: [...redacted...]/tools/qemu/translate-all.c:175: tb_lock: Assertion `!have_tb_lock' failed.
+qemu-ppc: [...redacted...]/tools/qemu/translate-all.c:175: tb_lock: Assertion `!have_tb_lock' failed.
+[1]    25996 segmentation fault  ~/tools/qemu/build/ppc-linux-user/qemu-ppc -cpu e500 test
+[...end output...]
+
+
+Executing with -strace option yields a surprising entry (see second clone() syscall below):
+[...]
+26007 clone(CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID,child_stack=0xf67fde60,parent_tidptr=0xf67fe368,tls=0xf68057d0,child_tidptr=0xf67fe368) = 26009
+26007 clone(0,child_stack=0xf67fde60,parent_tidptr=0xf67fe368,tls=0xf68057d0,child_tidptr=0xf67fe368) = -1 errno=22 (Invalid argument)
+
+
+test.c works just fine if the pthread_create & pthread_join calls are removed
+(i.e. when compiled with -DNO_PTHREAD_CREATE).
+
+At first glance, the issue seems specific to PPC because compiling and running
+for x86_64 using qemu-x86_64 works fine.
+
+
+Additional info:
+> lddtree =qemu-ppc
+qemu-ppc => /usr/bin/qemu-ppc (interpreter => /lib64/ld-linux-x86-64.so.2)
+    libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0
+        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2
+            ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2
+    libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0
+        libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3
+    librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1
+    libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6
+    libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
+    libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
+    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6
+
+> /lib/x86_64-linux-gnu/libc.so.6
+GNU C Library (Debian GLIBC 2.24-9) stable release version 2.24, by Roland McGrath et al.
+
+> uname -a
+Linux [...redacted...] 4.9.0-1-amd64 #1 SMP Debian 4.9.6-3 (2017-01-28) x86_64 GNU/Linux
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1668041 b/results/classifier/gemma3:12b/kernel/1668041
new file mode 100644
index 00000000..cced05ba
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1668041
@@ -0,0 +1,11 @@
+
+x86 Floating point exceptions - incorrect support?
+
+It seems that qemu does not correctly emulate the x86 support for optionally causing a floating-point exception (#FP) when, for example, dividing by zero. Reports such as:
+
+https://github.com/cloudius-systems/osv/issues/855
+http://stackoverflow.com/questions/15134189/qemu-div-by-zero-mxcsr-register
+
+suggest that setting the exception mask in the fpu cw or mxcsr (e.g., using a function like feenableexcept() in the guest OS) does not generate floating point exceptions on divide by zero. The problem only happens on pure QEMU - when a QEMU/KVM combination is used, the actual hardware does the floating point work, and does throw the exception on divide by zero if so requested.
+
+Looking at the qemu (2.8.0) source code, it seems to me it really lacks support for generating fpu exceptions: For example, helper_fdiv() in target-i386/fpu_helper.c, when it notices the divisor is zero, seems to set the divide-by-zero exception bit, but doesn't seem to check whether it needs to trigger an exception (when the right bits on the x87 or SSE control words are enabled).
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1670170 b/results/classifier/gemma3:12b/kernel/1670170
new file mode 100644
index 00000000..1db4c703
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1670170
@@ -0,0 +1,39 @@
+
+`qemu-system-sparc64 -M Niagara` Aborted (core dumped)
+
+> qemu-system-sparc64 -M Niagara
+qemu: fatal: Trap 0x0064 while trap level (6) >= MAXTL (6), Error state
+pc: 0000000000004c80  npc: 0000000000004c84
+%g0-3: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%g4-7: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%o0-3: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 
+%o4-7: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 
+%l0-3: 0000000007f00000 000001ff00000000 000001fff0080000 0000000000000000 
+%l4-7: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 
+%i0-3: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 
+%i4-7: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 
+%f00:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%f08:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%f16:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%f24:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%f32:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%f40:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%f48:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%f56:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
+pstate: 00000414 ccr: 44 (icc: -Z-- xcc: -Z--) asi: 00 tl: 6 pil: 0
+cansave: 6 canrestore: 0 otherwin: 0 wstate: 0 cleanwin: 6 cwp: 7
+fsr: 0000000000000000 y: 0000000000000000 fprs: 0000000000000000
+
+Aborted (core dumped)
+
+> qemu-system-sparc64 -M help
+Supported machines are:
+Niagara              Sun4v platform, Niagara
+none                 empty machine
+sun4u                Sun4u platform (default)
+sun4v                Sun4v platform
+
+> qemu-system-sparc64 -version
+QEMU emulator version 2.8.0(Virtualization:Staging / SLE_12_SP2)
+
+from https://build.opensuse.org/package/show/Virtualization:Staging/qemu on openSUSE Leap 42.2.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1675 b/results/classifier/gemma3:12b/kernel/1675
new file mode 100644
index 00000000..0d2214c1
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1675
@@ -0,0 +1,2 @@
+
+virtual machines still randomly crashing on kernel 6.1.30
diff --git a/results/classifier/gemma3:12b/kernel/1677247 b/results/classifier/gemma3:12b/kernel/1677247
new file mode 100644
index 00000000..aefd4f58
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1677247
@@ -0,0 +1,13 @@
+
+QEMU e500 kvm no video and kernel crashing in virtios modules
+
+Hi,
+i been attached the log of my issue on Qoriq e5500
+when i start qemu-system-ppc64  -cpu e5500 -M ppce500 --enable-kvm -device virtio-gpu-pci  --nodefaults -display gtk and so and so . i have crashes in virtio modules in the VM and continue traces on the host machine.
+If is needed more for investigating ask freely .
+
+Note: i use my selfmade kernel this machine dont have a distro kenels and official kernels.
+
+
+Ciao 
+Luigi
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1682093 b/results/classifier/gemma3:12b/kernel/1682093
new file mode 100644
index 00000000..9b633464
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1682093
@@ -0,0 +1,16 @@
+
+aarch64-softmmu "bad ram pointer" crash
+
+I am developing a piece of software called SimBench which is a benchmarking system for full system simulators. I am currently porting this to aarch64, using QEMU as a test platform. 
+
+I have encountered a 'bad ram pointer' crash. I've attempted to build a minimum test case, but I haven't managed to replicate the behaviour in isolation, so I've created a branch of my project which exhibits the crash: https://bitbucket.org/Awesomeclaw/simbench/get/qemu-bug.tar.gz
+
+The package can be compiled using:
+
+make
+
+and then run using:
+
+qemu-system-aarch64  -M virt -m 512 -cpu cortex-a57 -kernel out/armv8/virt/simbench -nographic
+
+I have replicated the issue in both qemu 2.8.1 and in 2.9.0-rc3, on Fedora 23. Please let me know if you need any more information or any logs/core dumps/etc.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1689367 b/results/classifier/gemma3:12b/kernel/1689367
new file mode 100644
index 00000000..f65f8b11
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1689367
@@ -0,0 +1,27 @@
+
+In qemu chroot, repeating "qemu: Unsupported syscall: 384" messages.  sys_getrandom ?
+
+On exec of an armv7 qemu chroot on my local x86_64 desktop, launched via
+
+	/usr/sbin/qemu-binfmt-conf.sh
+
+from
+
+	qemu-linux-user-2.9.0-374.1.x86_64
+
+on the host, inside the chroot any compile activity is laced with repetitions of
+
+	qemu: Unsupported syscall: 384
+
+messages.
+
+This wasn't always the case -- but, TBH, it's been ~ 6 months since I used this env, and there have been scads of usual pkg updates in the interim.  These messages appear to be non-fatal, with no particular effect at all; at least not so far ...
+
+From a chat in #IRC,
+
+	[10:05] davidgiluk clever/pgnd: I see it as getrandom
+	[10:05] davidgiluk pgnd: https://fedora.juszkiewicz.com.pl/syscalls.html   sort it on the ARM table and you can easily see it
+	[10:05] clever arch/arm/tools/syscall.tbl:384  common  getrandom               sys_getrandom
+	[10:06] davidgiluk pgnd: my *guess* is that something is calling getrandom, getting told it's not implemented and then falling back to using /dev/urandom
+	[10:10] pgnd davidgiluk: If that *is* the case, is it to be considered a problem, or just informational?
+	[10:12] davidgiluk pgnd: As long as it's falling back probably informational; but someone should probably go and wire up sys_getrandom at some point
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1696 b/results/classifier/gemma3:12b/kernel/1696
new file mode 100644
index 00000000..5085e946
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1696
@@ -0,0 +1,40 @@
+
+Linux kernel hangs rarely when booting on the latest qemu
+Description of problem:
+(Downstream bug: https://bugzilla.redhat.com/show_bug.cgi?id=2213346)
+
+In Fedora we have noticed that the latest Linux kernel (rarely) hangs when booting
+on the latest qemu.  It hangs after printing:
+
+```
+[    0.070120] x86/cpu: User Mode Instruction Prevention (UMIP) activated
+[    0.070120] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
+[    0.070120] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
+[    0.070120] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
+[    0.070120] Spectre V2 : Mitigation: Retpolines
+[    0.070120] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
+[    0.070120] Spectre V2 : Spectre v2 / SpectreRSB : Filling RSB on VMEXIT
+[    0.070120] Spectre V2 : Enabling Speculation Barrier for firmware calls
+[    0.070120] RETBleed: Mitigation: untrained return thunk
+[    0.070120] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
+[    0.070120] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl
+[    0.070120] Freeing SMP alternatives memory: 48K
+```
+
+The next line which would be printed (if it didn't hang) is:
+
+```
+[    0.070794] smpboot: CPU0: AMD Ryzen 9 3900X 12-Core Processor (family: 0x17, model: 0x71, stepping: 0x0)
+```
+
+We've seen this hang on both AMD and Intel.  It probably happens one in every 300 boots.
+Steps to reproduce:
+By far the easiest way to reproduce this is to just run guestfish in a loop:
+
+```
+$ while guestfish -a /dev/null -v run >& /tmp/log; do echo -n . ; done 
+```
+Additional information:
+The full qemu command is rather long but you can find it in this log file:
+
+https://bugzilla-attachments.redhat.com/attachment.cgi?id=1969620
diff --git a/results/classifier/gemma3:12b/kernel/1699277 b/results/classifier/gemma3:12b/kernel/1699277
new file mode 100644
index 00000000..0f3728dd
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1699277
@@ -0,0 +1,115 @@
+
+qemu-system-s390x: asserts while booting Debian Stretch installer
+
+QEMU 2.9.0 (Arch Linux) asserts when I try to install Debian Stretch.
+
+Steps to reproduce:
+
+wget http://ftp.debian.org/debian/dists/stretch/main/installer-s390x/current/images/generic/initrd.debian
+wget http://ftp.debian.org/debian/dists/stretch/main/installer-s390x/current/images/generic/kernel.debian
+qemu-img create -f qcow2 hda.qcow2 80G
+qemu-system-s390x -kernel kernel.debian -initrd initrd.debian -nographic -drive file=hda.qcow2
+
+Output:
+
+[    0.051915] Linux version 4.9.0-3-s390x (<email address hidden>) (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.30-2 (2017-06-12)
+[    0.053000] setup: Linux is running under KVM in 64-bit mode
+[    0.053780] setup: Max memory size: 128MB
+[    0.067239] Write protected kernel read-only data: 8848k
+[    0.082461] Zone ranges:
+[    0.083717]   DMA      [mem 0x0000000000000000-0x000000007fffffff]
+[    0.084163]   Normal   empty
+[    0.084185] Movable zone start for each node
+[    0.084223] Early memory node ranges
+[    0.084306]   node   0: [mem 0x0000000000000000-0x0000000007ffffff]
+[    0.084468] Initmem setup node 0 [mem 0x0000000000000000-0x0000000007ffffff]
+[    0.087697] percpu: Embedded 19 pages/cpu @0000000007f87000 s40704 r8192 d28928 u77824
+[    0.088991] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32256
+[    0.089108] Kernel command line: 
+[    0.096684] PID hash table entries: 512 (order: 0, 4096 bytes)
+[    0.096853] Dentry cache hash table entries: 16384 (order: 5, 131072 bytes)
+[    0.097041] Inode-cache hash table entries: 8192 (order: 4, 65536 bytes)
+[    0.102453] Memory: 105164K/131072K available (6060K kernel code, 802K rwdata, 2784K rodata, 508K init, 648K bss, 25908K reserved, 0K cma-reserved)
+[    0.109112] Hierarchical RCU implementation.
+[    0.109134] 	Build-time adjustment of leaf fanout to 64.
+[    0.109155] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=2.
+[    0.109194] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=2
+[    0.122047] NR_IRQS:3 nr_irqs:3 3
+[    0.124317] clocksource: tod: mask: 0xffffffffffffffff max_cycles: 0x3b0a9be803b0a9, max_idle_ns: 1805497147909793 ns
+[    0.138366] console [ttyS1] enabled
+[    0.139126] pid_max: default: 32768 minimum: 301
+[    0.143164] Security Framework initialized
+[    0.143215] Yama: disabled by default; enable with sysctl kernel.yama.*
+[    0.143955] AppArmor: AppArmor disabled by boot time parameter
+[    0.144489] Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
+[    0.144538] Mountpoint-cache hash table entries: 512 (order: 0, 4096 bytes)
+[    0.156937] ftrace: allocating 19165 entries in 75 pages
+[    0.408921] cpu: 1 configured CPUs, 0 standby CPUs
+[    0.433942] Brought up 1 CPUs
+[    0.451811] devtmpfs: initialized
+[    0.467021] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
+[    0.467549] futex hash table entries: 512 (order: 5, 131072 bytes)
+[    0.476626] NET: Registered protocol family 16
+[    0.482575] The s390-virtio transport is deprecated. Please switch to a modern host providing virtio-ccw.
+[    0.693017] VFS: Disk quotas dquot_6.6.0
+[    0.693296] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
+[    0.695029] hugetlbfs: disabling because there are no supported hugepage sizes
+[    0.703040] NET: Registered protocol family 2
+[    0.709803] TCP established hash table entries: 1024 (order: 1, 8192 bytes)
+[    0.710003] TCP bind hash table entries: 1024 (order: 2, 16384 bytes)
+[    0.710134] TCP: Hash tables configured (established 1024 bind 1024)
+[    0.710879] UDP hash table entries: 256 (order: 1, 8192 bytes)
+[    0.711005] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
+[    0.712409] NET: Registered protocol family 1
+[    0.717432] Unpacking initramfs...
+[    1.308935] random: fast init done
+[    1.597369] Freeing initrd memory: 10152K (0000000000f90000 - 000000000197a000)
+[    1.600200] hypfs: The hardware system does not support hypfs
+[    1.601718] hypfs: Initialization of hypfs failed with rc=-61
+[    1.605317] audit: initializing netlink subsys (disabled)
+[    1.606211] audit: type=2000 audit(1497977949.601:1): initialized
+[    1.611137] workingset: timestamp_bits=46 max_order=15 bucket_order=0
+[    1.612066] zbud: loaded
+[    1.642108] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
+[    1.643111] io scheduler noop registered
+[    1.643160] io scheduler deadline registered
+[    1.643383] io scheduler cfq registered (default)
+[    1.644143] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
+[    1.644221] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
+[    1.645626] hvc_iucv: The z/VM IUCV HVC device driver cannot be used without z/VM
+[    1.647547] mousedev: PS/2 mouse device common for all mice
+[    1.649359] ledtrig-cpu: registered to indicate activity on CPUs
+[    1.649884] cio: Channel measurement facility initialized using format extended (mode autodetected)
+[    1.657228] NET: Registered protocol family 10
+[    1.663924] mip6: Mobile IPv6
+[    1.664068] NET: Registered protocol family 17
+[    1.664195] mpls_gso: MPLS GSO support
+[    1.667936] registered taskstats version 1
+[    1.669547] zswap: loaded using pool lzo/zbud
+[    1.674474] ima: No TPM chip found, activating TPM-bypass!
+[    1.739953] Freeing unused kernel memory: 508K (0000000000a6f000 - 0000000000aee000)
+[    1.740381] Write protected read-only-after-init data: 4k
+**
+ERROR:/build/qemu/src/qemu-2.9.0/translate-common.c:34:tcg_handle_interrupt: assertion failed: (qemu_mutex_iothread_locked())
+[1]    13880 abort (core dumped)  qemu-system-s390x -kernel kernel.debian -initrd initrd.debian -nographic 
+
+Trace:
+#0  0x00007ffff10fb670 in raise () at /usr/lib/libc.so.6
+#1  0x00007ffff10fcd00 in abort () at /usr/lib/libc.so.6
+#2  0x00007ffff35dfc9d in g_assertion_message () at /usr/lib/libglib-2.0.so.0
+#3  0x00007ffff35dfd2a in g_assertion_message_expr () at /usr/lib/libglib-2.0.so.0
+#4  0x00005555556abb84 in  ()
+#5  0x000055555572ab73 in css_adapter_interrupt ()
+#6  0x000055555571be68 in virtio_notify ()
+#7  0x00005555556f84ce in  ()
+#8  0x00005555556f9afd in  ()
+#9  0x00005555556fa78f in virtio_blk_handle_vq ()
+#10 0x000055555571b7f1 in virtio_queue_notify ()
+#11 0x000055555572ceb7 in  ()
+#12 0x0000555555726f86 in s390_virtio_hypercall ()
+#13 0x0000555555752c85 in helper_diag ()
+#14 0x00007fffe46664bf in code_gen_buffer ()
+#15 0x00005555556ab2f5 in cpu_exec ()
+#16 0x00005555556ce08d in  ()
+#17 0x00007ffff1474297 in start_thread () at /usr/lib/libpthread.so.0
+#18 0x00007ffff11b525f in clone () at /usr/lib/libc.so.6
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1700 b/results/classifier/gemma3:12b/kernel/1700
new file mode 100644
index 00000000..1d5930a2
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1700
@@ -0,0 +1,2 @@
+
+TriCore:  helper_ret() is not correctly restoring PSW
diff --git a/results/classifier/gemma3:12b/kernel/1701798 b/results/classifier/gemma3:12b/kernel/1701798
new file mode 100644
index 00000000..00d5c72c
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1701798
@@ -0,0 +1,161 @@
+
+dynamically linked binaries crash for big-endian targets
+
+On the targets
+  hppa
+  m68k
+  mips
+  mips64
+  powerpc
+  powerpc64
+  s390x
+  sparc64
+dynamically linked binaries crash, but statically linked binaries work.
+On the targets
+  aarch64
+  alpha
+  armhf
+  powerpc64le
+  sh4
+both dynamically linked and statically linked binaries work.
+
+How to reproduce:
+
+1) On Ubuntu 16.04, install the packages
+g++-5-aarch64-linux-gnu
+g++-5-alpha-linux-gnu
+g++-5-arm-linux-gnueabihf
+g++-5-hppa-linux-gnu
+g++-5-m68k-linux-gnu
+g++-5-mips-linux-gnu
+g++-5-mips64-linux-gnuabi64
+g++-5-powerpc-linux-gnu
+g++-5-powerpc64-linux-gnu
+g++-5-powerpc64le-linux-gnu
+g++-5-s390x-linux-gnu
+g++-5-sh4-linux-gnu
+g++-5-sparc64-linux-gnu
+
+2) Install qemu 2.9.0 from source (for m68k, use the 2.7.0-m68k
+code from https://github.com/vivier/qemu-m68k.git):
+$ ../configure --prefix=/home/bruno/inst-qemu/2.9.0 --target-list=aarch64-softmmu,alpha-softmmu,arm-softmmu,i386-softmmu,m68k-softmmu,mips-softmmu,mipsel-softmmu,mips64-softmmu,mips64el-softmmu,ppc-softmmu,ppc64-softmmu,s390x-softmmu,sh4-softmmu,sparc-softmmu,sparc64-softmmu,x86_64-softmmu,aarch64-linux-user,alpha-linux-user,arm-linux-user,hppa-linux-user,m68k-linux-user,mips-linux-user,mipsel-linux-user,mips64-linux-user,mips64el-linux-user,ppc-linux-user,ppc64-linux-user,ppc64le-linux-user,s390x-linux-user,sh4-linux-user,sparc-linux-user,sparc64-linux-user --disable-strip --disable-werror --enable-gtk --enable-vnc
+$ make
+$ make install
+
+3) Cross-compile the programs:
+
+$ aarch64-linux-gnu-gcc-5 -O hello.c -o hello.aarch64
+$ alpha-linux-gnu-gcc-5 -O hello.c -o hello.alpha
+$ arm-linux-gnueabihf-gcc-5 -O hello.c -o hello.armhf
+$ hppa-linux-gnu-gcc-5 -O hello.c -o hello.hppa
+$ m68k-linux-gnu-gcc-5 -O hello.c -o hello.m68k
+$ mips-linux-gnu-gcc-5 -O hello.c -o hello.mips
+$ mips64-linux-gnuabi64-gcc-5 -O hello.c -o hello.mips64
+$ powerpc-linux-gnu-gcc-5 -O hello.c -o hello.powerpc
+$ powerpc64-linux-gnu-gcc-5 -O hello.c -o hello.powerpc64
+$ powerpc64le-linux-gnu-gcc-5 -O hello.c -o hello.powerpc64le
+$ s390x-linux-gnu-gcc-5 -O hello.c -o hello.s390x
+$ sh4-linux-gnu-gcc-5 -O hello.c -o hello.sh4
+$ sparc64-linux-gnu-gcc-5 -O hello.c -o hello.sparc64
+
+4) Run the programs:
+
+* aarch64 works:
+$ QEMU_LD_PREFIX=/usr/aarch64-linux-gnu ~/inst-qemu/2.9.0/bin/qemu-aarch64 hello.aarch64
+Hello world
+
+* alpha works:
+$ QEMU_LD_PREFIX=/usr/alpha-linux-gnu ~/inst-qemu/2.9.0/bin/qemu-alpha hello.alpha 
+Hello world
+
+* armhf works:
+$ QEMU_LD_PREFIX=/usr/arm-linux-gnueabihf ~/inst-qemu/2.9.0/bin/qemu-arm hello.armhf
+Hello world
+
+* powerpc64le works:
+$ QEMU_LD_PREFIX=/usr/powerpc64le-linux-gnu ~/inst-qemu/2.9.0/bin/qemu-ppc64le hello.powerpc64le
+Hello world
+
+* sh4 works:
+$ QEMU_LD_PREFIX=/usr/sh4-linux-gnu ~/inst-qemu/2.9.0/bin/qemu-sh4 hello.sh4
+Hello world
+
+* ===== sparc64 does not work:
+$ QEMU_LD_PREFIX=/usr/sparc64-linux-gnu ~/inst-qemu/2.9.0/bin/qemu-sparc64 hello.sparc64
+Segmentation fault (core dumped)
+
+When I copy the file to a machine with `uname -srm` = "Linux 4.5.0-2-sparc64 sparc64",
+it works:
+$ ./hello.sparc64
+Hello world
+
+When I copy the file and its execution environment /usr/sparc64-linux-gnu to the
+same machine and run the binary in a chroot environment:
+# /bin/hello.sparc64 
+Hello world
+
+* ===== mips does not work:
+$ QEMU_LD_PREFIX=/usr/mips-linux-gnu ~/inst-qemu/2.9.0/bin/qemu-mips hello.mips
+qemu: uncaught target signal 11 (Segmentation fault) - core dumped
+
+When I copy the file to a machine with `uname -srm` = "Linux 3.16.0-4-4kc-malta mips",
+it works:
+$ ./hello.mips
+Hello world
+
+When I copy the file and its execution environment /usr/mips-linux-gnu to the
+same machine and run the binary in a chroot environment:
+# /bin/hello.mips 
+Hello world
+
+* ===== mips64 does not work:
+$ QEMU_LD_PREFIX=/usr/mips64-linux-gnuabi64 ~/inst-qemu/2.9.0/bin/qemu-mips64 hello.mips64
+qemu: uncaught target signal 11 (Segmentation fault) - core dumped
+
+When I copy the file to a machine with `uname -srm` = "Linux 3.16.0-4-5kc-malta mips64",
+it works:
+$ ./hello.mips64
+Hello world
+
+* ===== powerpc does not work:
+$ QEMU_LD_PREFIX=/usr/powerpc-linux-gnu ~/inst-qemu/2.9.0/bin/qemu-ppc hello.powerpc
+qemu: uncaught target signal 11 (Segmentation fault) - core dumped
+
+When I copy the file to a machine with `uname -srm` = "Linux 3.17.2-200.fc20.ppc64p7 ppc64",
+it works:
+$ ./hello.powerpc
+Hello world
+
+* ===== powerpc64 does not work:
+$ QEMU_LD_PREFIX=/usr/powerpc64-linux-gnu ~/inst-qemu/2.9.0/bin/qemu-ppc64 hello.powerpc64
+qemu: uncaught target signal 11 (Segmentation fault) - core dumped
+
+When I copy the file to a machine with `uname -srm` = "Linux 3.17.2-200.fc20.ppc64p7 ppc64",
+it works:
+$ ./hello.powerpc64
+Hello world
+
+* ===== s390x does not work:
+$ QEMU_LD_PREFIX=/usr/s390x-linux-gnu ~/inst-qemu/2.9.0/bin/qemu-s390x hello.s390x
+<hangs>
+$ QEMU_LD_PREFIX=/usr/s390x-linux-gnu ~/inst-qemu/2.8.1/bin/qemu-s390x hello.s390x
+qemu-s390x: /media/develdata/devel/build/qemu-2.8.1/translate-all.c:175: tb_lock: Assertion `!have_tb_lock' failed.
+Segmentation fault (core dumped)
+
+When I copy the file to a machine with `uname -srm` = "Linux 3.16.0-4-s390x s390x",
+it works:
+$ ./hello.s390x
+Hello world
+
+* ===== hppa does not work:
+$ QEMU_LD_PREFIX=/usr/hppa-linux-gnu ~/inst-qemu/2.9.0/bin/qemu-hppa hello.hppa
+Segmentation fault (core dumped)
+
+* ===== m68k does not work:
+$ QEMU_LD_PREFIX=/usr/m68k-linux-gnu QEMU_CPU=m68020 ~/inst-qemu/2.9.0/bin/qemu-m68k hello.m68k
+qemu: uncaught target signal 4 (Illegal instruction) - core dumped
+$ QEMU_LD_PREFIX=/usr/m68k-linux-gnu QEMU_CPU=m68020 ~/inst-qemu/2.7.0-m68k/bin/qemu-m68k hello.m68k
+qemu: uncaught target signal 11 (Segmentation fault) - core dumped
+
+
+The set of targets where it does not work is exactly the big-endian targets.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1705118 b/results/classifier/gemma3:12b/kernel/1705118
new file mode 100644
index 00000000..c66bc6ac
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1705118
@@ -0,0 +1,57 @@
+
+qemu user mode: rt signals not implemented for sparc guests
+
+The documentation
+<https://qemu.weilnetz.de/doc/qemu-doc.html#Features> says that
+qemu in user mode supports POSIX signal handling.
+
+Catching SIGSEGV according to POSIX, however, does not work on
+  ppc, ppc64, ppc64le, s390x, sparc64.
+It does work, however, on
+  aarch64, alpha, arm, hppa, m68k, mips, mips64, sh4.
+
+How to reproduce:
+The attached program runs fine (exits with code 0) on
+  - real hardware Linux/PowerPC64 (in 32-bit and 64-bit mode),
+  - real hardware Linux/PowerPC64LE,
+  - qemu-system-s390x emulated Linux/s390x,
+  - real hardware Linux/SPARC64.
+$ gcc -O -Wall testsigsegv.c; ./a.out; echo $?
+0
+
+For ppc:
+$ powerpc-linux-gnu-gcc-5 -O -Wall -static testsigsegv.c -o testsigsegv-ppc
+$ ~/inst-qemu/2.9.0/bin/qemu-ppc testsigsegv-ppc
+$ echo $?
+3
+
+For ppc64:
+$ powerpc64-linux-gnu-gcc-5 -O -Wall -static testsigsegv.c -o testsigsegv-ppc64
+$ ~/inst-qemu/2.9.0/bin/qemu-ppc64 testsigsegv-ppc64
+$ echo $?
+3
+
+For ppc64le:
+$ powerpc64le-linux-gnu-gcc-5 -O -Wall -static testsigsegv.c -o testsigsegv-ppc64le
+$ ~/inst-qemu/2.9.0/bin/qemu-ppc64le testsigsegv-ppc64le
+$ echo $?
+3
+
+For s390x:
+$ s390x-linux-gnu-gcc-5 -O -Wall -static testsigsegv.c -o testsigsegv-s390x
+$ ~/inst-qemu/2.9.0/bin/qemu-s390x testsigsegv-s390x
+$ echo $?
+3
+$ s390x-linux-gnu-gcc-5 -O -Wall -static testsigsegv.c -DAVOID_LINUX_S390X_COMPAT -o testsigsegv-s390x-a
+$ ~/inst-qemu/2.9.0/bin/qemu-s390x testsigsegv-s390x-a
+$ echo $?
+0
+So, the test fails here because the Linux/s390x kernel omits the least
+significant 12 bits of the fault address in the 'si_addr' field. But
+qemu-s390x is not compatible with the Linux/s390x behaviour: it puts
+the complete fault address in the 'si_addr' field.
+
+For sparc64:
+$ sparc64-linux-gnu-gcc-5 -O -Wall -static testsigsegv.c -o testsigsegv-sparc64
+$ ~/inst-qemu/2.9.0/bin/qemu-sparc64 testsigsegv-sparc64
+Segmentation fault (core dumped)
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1707 b/results/classifier/gemma3:12b/kernel/1707
new file mode 100644
index 00000000..d3a5ee08
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1707
@@ -0,0 +1,24 @@
+
+linux-user  qemu-x86_64  can't exec a binary  on aarch64 or Loongarch.
+Description of problem:
+on master branch,  we build an simply hello.c with x86_cross gcc.
+then. run './build/qemu-x86_64 hello', no output.
+Steps to reproduce:
+1. build  an hello.c with x86_64 cross.  use --static.
+2. build qemu-x86_64 on aarch64 or LoongArch host.
+3. run './build/qemu-x86_64 hello'
+Additional information:
+[strace.txt](/uploads/5362e0e9b04ad9a582470faf4a9fcedb/strace.txt)
+ 
+
+
+ [hello](/uploads/12d9277fa4e853286414f575010a37ac/hello)
+
+ 
+The following commit causes this problem．
+
+commit 86f04735ac2088d5c069c3d1712212ec7428c562
+Author: Helge Deller <deller@gmx.de>
+Date:   Sun Dec 25 09:23:19 2022 +0100
+
+    linux-user: Fix brk() to release pages
diff --git a/results/classifier/gemma3:12b/kernel/172 b/results/classifier/gemma3:12b/kernel/172
new file mode 100644
index 00000000..7d7255e6
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/172
@@ -0,0 +1,2 @@
+
+qemu seems to lack support for pid namespace.
diff --git a/results/classifier/gemma3:12b/kernel/1728256 b/results/classifier/gemma3:12b/kernel/1728256
new file mode 100644
index 00000000..16b7d89e
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1728256
@@ -0,0 +1,11 @@
+
+Memory corruption in Windows 10 guest / amd64
+
+I have a Win 10 Pro x64 guest inside a qemu/kvm running on an Arch x86_64 host. The VM has a physical GPU passed through, as well as the physical USB controllers, as well as a dedicated SSD attached via SATA; you can find the complete libvirt xml here: https://pastebin.com/U1ZAXBNg
+I built qemu from source using the qemu-minimal-git AUR package; you can find the build script here: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=qemu-minimal-git (if you aren't familiar with Arch, this is essentially a bash script where build() and package() are run to build the files, and then install them into the $pkgdir to later tar them up.)
+
+Starting with qemu v2.10.0, Windows crashes randomly with a bluescreen about CRITICAL_STRUCTURE_CORRUPTION. I also tested the git heads f90ea7ba7c, 861cd431c9 and e822e81e35, before I went back to v2.9.0, which is running stable for over 50 hours right now.
+
+During my tests I found that locking the memory pages alleviates the problem somewhat, but never completely avoids it. However, with the crashes occuring randomly, that could as well be false conclusions; I had crashes within minutes after boot with that too.
+
+I will now start `git bisect`ing; if you have any other suggestions on what I could try or possible patches feel free to leave them with me.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1728448 b/results/classifier/gemma3:12b/kernel/1728448
new file mode 100644
index 00000000..69eb2949
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1728448
@@ -0,0 +1,15 @@
+
+qemu-system-arm segmentation fault with cpu cortex-m*
+
+I try to run an emulation with qemu-system-arm under a cpu cortex-m3 but any execution under the processor result by a segmentation fault. 
+
+My command is : qemu-system-arm -m 256 -M versatilepb -cpu cortex-m3 -kernel ~/qemu/wheezy/vmlinuz-3.2.0-4-versatile -initrd ~/qemu/wheezy/initrd.img-3.2.0-4-versatile -hda ~/qemu/wheezy/hda.img -append 'root=/dev/sda1'
+
+If a lauch the emulation without specifying a cpu equivalent to cortex-m*, the vm opens up well and works but I absolutely need to run it under cortex-m3.
+
+
+Do you have any idea why I have this problem only with this type of processor ?
+
+I also try with other boards different from versatilepb but I have the same result.
+
+I am under ubuntu 17 64bits during my test.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1729623 b/results/classifier/gemma3:12b/kernel/1729623
new file mode 100644
index 00000000..9929bd60
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1729623
@@ -0,0 +1,49 @@
+
+test-aio-multithread fails with 'Co-routine re-entered recursively'
+
+git head is at fa73e146250181852c0915aa65df8d54d35485fa
+
+configure with the following
+
+./configure --enable-attr --enable-bsd-user --enable-cap-ng\
+ --enable-coroutine-pool  --enable-crypto-afalg --enable-curl\
+ --enable-curses --enable-debug --enable-debug-info\
+ --enable-debug-tcg      --enable-fdt      --enable-gcrypt \
+ --enable-gnutls      --enable-gprof      --enable-gtk  \
+ --enable-guest-agent      --enable-kvm      --enable-libiscsi \
+ --enable-libssh2      --enable-linux-aio      --enable-linux-user \
+ --enable-live-block-migration      --enable-modules   \
+ --enable-numa      --enable-pie      --enable-profiler \
+ --enable-qom-cast-debug      --enable-rbd      --enable-replication  \
+ --enable-seccomp      --enable-smartcard      --enable-stack-protector \
+ --enable-system      --enable-tcg      --enable-tcg-interpreter  \
+ --enable-tools      --enable-tpm      --enable-trace-backend=ftrace \
+ --enable-user      --enable-vhost-net      --enable-vhost-scsi  \
+ --enable-vhost-user      --enable-vhost-vsock      --enable-virtfs  \ 
+ --enable-vnc      --enable-tpm      --enable-vnc-png   \
+ --enable-vnc-sasl      --enable-werror      --enable-xfsctl \
+ --enable-gcov --enable-debug-stack-usage
+
+make -j 32
+
+make test-aio-multithread V=1
+
+...
+File '/home/nasastry/qemu/include/qapi/qmp/qobject.h'
+No executable lines
+
+MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} gtester -k --verbose -m=quick tests/test-aio-multithread
+TEST: tests/test-aio-multithread... (pid=86877)
+  /aio/multi/lifecycle:                                                OK
+  /aio/multi/schedule:                                                 Co-routine re-entered recursively
+FAIL
+GTester: last random seed: R02S681209ce87fc22715b41223212d9f6f0
+(pid=86891)
+  /aio/multi/mutex/contended:                                          OK
+  /aio/multi/mutex/handoff:                                            OK
+  /aio/multi/mutex/mcs:                                                OK
+  /aio/multi/mutex/pthread:                                            OK
+FAIL: tests/test-aio-multithread
+make: *** [check-tests/test-aio-multithread] Error 1
+
+Full log will be attached.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1733720 b/results/classifier/gemma3:12b/kernel/1733720
new file mode 100644
index 00000000..1b9faada
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1733720
@@ -0,0 +1,56 @@
+
+raspi2 with multiple CPU's #1
+
+Greetings,
+
+I am running a small program for raspi2 (from http://wiki.osdev.org/ARM_RaspberryPi_Tutorial_C).
+
+This code writes "Hello World", but the output ir repeated 4 times.
+
+My thought was that this is emulating a 4 cpu core system.
+
+However, when I check the MPIDR registed for CPU number, it always returns 1.
+
+I git cloned github.com/qemu/qemu.git, made & installed on Acer ARM CB5-311 under Crouton/ubuntu.
+
+
+./qemu.sh 
+1111
+
+Linux:armv7l: ~/Downloads/RaspiTest/BareBones >>> uname -a
+Linux localhost 3.10.18 #1 SMP Mon Nov 13 16:34:10 PST 2017 armv7l armv7l armv7l GNU/Linux
+
+Linux:armv7l: ~/Downloads/RaspiTest/BareBones >>> qemu-system-arm --version
+QEMU emulator version 2.10.91 (v2.11.0-rc1-dirty)
+Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers
+
+=====
+static inline uint32_t read_mpdir(void)
+{
+  uint32_t id;
+  
+  asm volatile("mrc p15, 0, %[id], c0, c0, 0 @ read MIDR\n\t"
+	       : [id] "=r" (id));
+  return id;
+}
+======
+void kernel_main(uint32_t r0, uint32_t r1, uint32_t atags)
+{
+	// Declare as unused
+	(void) r0;
+	(void) r1;
+	(void) atags;
+
+	uint32_t cpu_id;
+
+	cpu_id = read_mpdir() & 0x03;
+
+	uart_putc( "01234"[cpu_id] ); /* output is "1111" */
+
+	if (cpu_id == 0) { /* code never executes 8^( */ }
+
+====== qemu.sh
+qemu-system-arm -m 256 -M raspi2 -no-reboot -serial stdio  -kernel myos.elf
+
+Thanks much,
+-KenD
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1734792 b/results/classifier/gemma3:12b/kernel/1734792
new file mode 100644
index 00000000..ac9dfd9f
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1734792
@@ -0,0 +1,8 @@
+
+linux-user mode does not support memfd_create syscall
+
+qemu-x86_66 GIT HEAD fails on a userspace application that requires memfd_create with:
+
+"qemu: Unsupported syscall: 319".
+
+memfd_create support needs to be implemented in QEMU.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1735082 b/results/classifier/gemma3:12b/kernel/1735082
new file mode 100644
index 00000000..97b0910e
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1735082
@@ -0,0 +1,23 @@
+
+NVME pass through in th eguest VM
+
+Hi Qemu Team 
+
+i am new in qemu and trying for nvme pass through ..
+for that i used  below git repo for nvme 
+
+https://github.com/famz/qemu/tree/nvme
+
+and trying to launch the VM by below qemu command ..
+
+/usr/local/bin/qemu-system-x86_64 -name sl7.0  -m 1024 -object memory-backend-file,id=mem,size=1G,mem-path=/dev/hugepages,share=on -nographic -no-user-config -nodefaults -serial mon:telnet:localhost:7704,server,nowait -monitor mon:telnet:localhost:8804,server,nowait -numa node,memdev=mem -drive file=/home/qemu/qcows,format=qcow2,if=none,id=disk -device ide-hd,drive=disk,bootindex=0 -drive file=nvme://0000:d8:00.0,if=none,id=drive0 -device virtio-blk,drive=drive0,id=virtio0 --enable-kvm
+
+i am getting kernel panic and not proceed further..please help 
+
+PS:-  our guest VM version is 
+
+Scientific Linux 7.0 (Nitrogen)
+Kernel 3.10.0-123.el7.x86_64 on an x86_64
+
+Regards
+Nitin
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1737444 b/results/classifier/gemma3:12b/kernel/1737444
new file mode 100644
index 00000000..96f026d3
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1737444
@@ -0,0 +1,94 @@
+
+gccgo setcontext conftest crashes qemu-sh4
+
+While testing gccgo on sh4 to add SH platform definitions to libgo, I discovered that the following conftest program which is part of the libgo configure script crashes on qemu-sh4:
+
+(sid-sh4-sbuild)root@z6:/# cat setcontext.c
+#include <pthread.h>                                                                                                                                                                                                                                                           
+#include <stdlib.h>                                                                                                                                                                                                                                                            
+#include <ucontext.h>                                                                                                                                                                                                                                                          
+#include <unistd.h>                                                                                                                                                                                                                                                            
+
+__thread int tls;
+
+static char stack[10 * 1024 * 1024];
+static ucontext_t c;
+
+/* Called via makecontext/setcontext.  */
+
+static void
+cfn (void)
+{
+  exit (tls);
+}
+
+/* Called via pthread_create.  */
+
+static void *
+tfn (void *dummy)
+{
+  /* The thread should still see this value after calling
+     setcontext.  */
+  tls = 0;
+
+  setcontext (&c);
+
+  /* The call to setcontext should not return.  */
+  abort ();
+}
+
+int
+main ()
+{
+  pthread_t tid;
+
+  /* The thread should not see this value.  */
+  tls = 1;
+
+  if (getcontext (&c) < 0)
+    abort ();
+
+  c.uc_stack.ss_sp = stack;
+#ifdef MAKECONTEXT_STACK_TOP                                                                                                                                                                                                                                                   
+  c.uc_stack.ss_sp += sizeof stack;
+#endif                                                                                                                                                                                                                                                                         
+  c.uc_stack.ss_flags = 0;
+  c.uc_stack.ss_size = sizeof stack;
+  c.uc_link = NULL;
+  makecontext (&c, cfn, 0);
+
+  if (pthread_create (&tid, NULL, tfn, NULL) != 0)
+    abort ();
+
+  if (pthread_join (tid, NULL) != 0)
+    abort ();
+
+  /* The thread should have called exit.  */
+  abort ();
+}
+
+(sid-sh4-sbuild)root@z6:/# gcc -o setcontext -lpthread setcontext.c
+(sid-sh4-sbuild)root@z6:/# ./setcontext 
+Unhandled trap: 0x180
+pc=0x7f69235e sr=0x00000000 pr=0x00400710 fpscr=0x00080000
+spc=0x00000000 ssr=0x00000000 gbr=0x7f658478 vbr=0x00000000
+sgr=0x00000000 dbr=0x00000000 delayed_pc=0x7f692320 fpul=0x00000000
+r0=0x00e11158 r1=0x00000000 r2=0x00000001 r3=0x7ffff2e0
+r4=0x00e11068 r5=0x7ffff314 r6=0x7ffff31c r7=0x00000000
+r8=0x004007b0 r9=0x00000000 r10=0x00000000 r11=0x00000000
+r12=0x7f79ac54 r13=0x00000000 r14=0x7ffff288 r15=0x7ffff288
+r16=0x00000000 r17=0x00000000 r18=0x00000000 r19=0x00000000
+r20=0x00000000 r21=0x00000000 r22=0x00000000 r23=0x00000000
+(sid-sh4-sbuild)root@z6:/#
+
+The same code works fine on my Renesas SH7785LCR evaluation board:
+
+root@tirpitz:~> uname -a
+Linux tirpitz 3.16.7-ckt7 #8 PREEMPT Fri Oct 21 18:47:41 CEST 2016 sh4a GNU/Linux
+root@tirpitz:~> gcc -o setcontext setcontext.c  -lpthread
+root@tirpitz:~> ./setcontext 
+root@tirpitz:~> echo $?
+0
+root@tirpitz:~>
+
+Due to this bug, it is not possible to compile gcc-7 with the Go frontend enabled on qemu-sh4.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1738 b/results/classifier/gemma3:12b/kernel/1738
new file mode 100644
index 00000000..9b506f0c
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1738
@@ -0,0 +1,150 @@
+
+qemu-system-x86_64 crash during kernel PCI init with large number of busses
+Description of problem:
+When booting a Linux kernel under qemu-system-x86_64 (tcg) using a large number of PCI busses (25+), qemu crashes with an invalid memory access during kernel PCI init phase. Failure rate is not 100%; some kernel boots do succeed, but the failure rate increases as the number of pci busses increases. Note that no initrd is needed; crash happens before kernel even gets to the point of trying to mount root.
+Steps to reproduce:
+Launch qemu using command line above along with 4.19.x kernel image (have not tested 5.x). It may take a few tries but within about 20 boot attempts, qemu will crash at least once.
+Additional information:
+Final kernel logs before crash:
+```
+...
+[    1.413615] ACPI: Added _OSI(Module Device)
+[    1.413947] ACPI: Added _OSI(Processor Device)
+[    1.414262] ACPI: Added _OSI(3.0 _SCP Extensions)
+[    1.414421] ACPI: Added _OSI(Processor Aggregator Device)
+[    1.414922] ACPI: Added _OSI(Linux-Dell-Video)
+[    1.415445] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
+[    1.444489] ACPI: 1 ACPI AML tables successfully acquired and loaded
+[    1.468218] ACPI: Interpreter enabled
+[    1.469897] ACPI: (supports S0 S3 S4 S5)
+[    1.470200] ACPI: Using IOAPIC for interrupt routing
+[    1.471811] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and repog
+[    1.474421] ACPI: Enabled 2 GPEs in block 00 to 3F
+[    1.536854] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
+[    1.537996] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
+[    1.540988] acpi PNP0A08:00: _OSC: platform does not support [LTR]
+[    1.542232] acpi PNP0A08:00: _OSC: OS now controls [PME AER PCIeCapability]
+[    1.546310] PCI host bridge to bus 0000:00
+[    1.546650] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
+[    1.547471] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
+[    1.548039] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
+[    1.548421] pci_bus 0000:00: root bus resource [mem 0x80000000-0xafffffff window]
+[    1.549086] pci_bus 0000:00: root bus resource [mem 0xc0000000-0xfebfffff window]
+[    1.549945] pci_bus 0000:00: root bus resource [mem 0x280000000-0xa7fffffff window]
+[    1.550994] pci_bus 0000:00: root bus resource [bus 00-ff]
+<...crash...>
+```
+
+QEMU backtrace:
+```
+$ gdb build/qemu-system-x86_64 core.3475232
+<...>
+Reading symbols from build/qemu-system-x86_64...
+[New LWP 3475243]
+[New LWP 3475244]
+[New LWP 3475241]
+[New LWP 3475238]
+[New LWP 3475245]
+[New LWP 3475239]
+[New LWP 3475246]
+[New LWP 3475240]
+[New LWP 3475232]
+[New LWP 3475242]
+[New LWP 3475236]
+[New LWP 3475247]
+[Thread debugging using libthread_db enabled]
+Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
+Core was generated by `build/qemu-system-x86_64 -m 8192 -smp cpus=10,threads=2 -nographic -machine q35'.
+Program terminated with signal SIGSEGV, Segmentation fault.
+#0  0x0000556065897e0e in memory_region_dispatch_write (mr=mr@entry=0x0, addr=addr@entry=768, data=data@entry=253, 
+    op=op@entry=MO_32, attrs=...) at ../softmmu/memory.c:1497
+1497	    if (mr->alias) {
+[Current thread is 1 (Thread 0x7fe2e951d640 (LWP 3475243))]
+(gdb) bt full
+#0  0x0000556065897e0e in memory_region_dispatch_write
+    (mr=mr@entry=0x0, addr=addr@entry=768, data=data@entry=253, op=op@entry=MO_32, attrs=...) at ../softmmu/memory.c:1497
+        size = <optimized out>
+#1  0x00005560659112c2 in io_writex
+    (env=env@entry=0x556066bbd5d0, full=0x7fe08401ec70, mmu_idx=mmu_idx@entry=2, val=val@entry=253, addr=addr@entry=18446744073699050240, retaddr=retaddr@entry=140611404753775, op=MO_32) at ../accel/tcg/cputlb.c:1430
+        _iothread_lock_auto = 0x1
+        cpu = 0x556066bbb1e0
+        mr_offset = 768
+        section = 0x7fe078d7d570
+        mr = 0x0
+        r = <optimized out>
+#2  0x0000556065915f14 in store_helper
+    (op=MO_32, retaddr=140611404753775, oi=<optimized out>, val=<optimized out>, addr=18446744073699050240, env=0x556066bbd5d0)
+    at ../accel/tcg/cputlb.c:2454
+        full = <optimized out>
+        need_swap = false
+        a_bits = <optimized out>
+        mmu_idx = 2
+        tlb_addr = <optimized out>
+        haddr = <optimized out>
+        size = 4
+        index = <optimized out>
+        entry = 0x7fe08401bc40
+#3  full_le_stl_mmu (env=0x556066bbd5d0, addr=18446744073699050240, val=253, oi=<optimized out>, retaddr=140611404753775)
+    at ../accel/tcg/cputlb.c:2542
+#4  0x00007fe2a4d4eb6f in code_gen_buffer ()
+#5  0x00005560659065bb in cpu_tb_exec
+    (cpu=cpu@entry=0x556066bbb1e0, itb=itb@entry=0x7fe2a4d4e9c0 <code_gen_buffer+13953427>, tb_exit=tb_exit@entry=0x7fe2e951c758)
+    at ../accel/tcg/cpu-exec.c:460
+        env = 0x556066bbd5d0
+        ret = <optimized out>
+        last_tb = <optimized out>
+        tb_ptr = 0x7fe2a4d4ea80 <code_gen_buffer+13953619>
+        __PRETTY_FUNCTION__ = "cpu_tb_exec"
+#6  0x0000556065906ab6 in cpu_loop_exec_tb
+    (tb_exit=0x7fe2e951c758, last_tb=<synthetic pointer>, pc=<optimized out>, tb=0x7fe2a4d4e9c0 <code_gen_buffer+13953427>, cpu=0x556066bbb1e0) at ../accel/tcg/cpu-exec.c:893
+        insns_left = <optimized out>
+        __PRETTY_FUNCTION__ = "cpu_loop_exec_tb"
+        tb = 0x7fe2a4d4e9c0 <code_gen_buffer+13953427>
+        flags = <optimized out>
+        cflags = 4280811520
+        cs_base = <optimized out>
+        pc = <optimized out>
+        last_tb = <optimized out>
+        tb_exit = 0
+--Type <RET> for more, q to quit, c to continue without paging--
+        ret = <optimized out>
+#7  cpu_exec_loop (cpu=cpu@entry=0x556066bbb1e0, sc=sc@entry=0x7fe2e951c7f0) at ../accel/tcg/cpu-exec.c:1013
+        tb = 0x7fe2a4d4e9c0 <code_gen_buffer+13953427>
+        flags = <optimized out>
+        cflags = 4280811520
+        cs_base = <optimized out>
+        pc = <optimized out>
+        last_tb = <optimized out>
+        tb_exit = 0
+        ret = <optimized out>
+#8  0x0000556065907311 in cpu_exec_setjmp (cpu=cpu@entry=0x556066bbb1e0, sc=sc@entry=0x7fe2e951c7f0) at ../accel/tcg/cpu-exec.c:1043
+        __func__ = "cpu_exec_setjmp"
+#9  0x00005560659079f0 in cpu_exec (cpu=cpu@entry=0x556066bbb1e0) at ../accel/tcg/cpu-exec.c:1069
+        ret = <optimized out>
+        sc = {diff_clk = 0, last_cpu_icount = 0, realtime_clock = 0}
+#10 0x000055606592a854 in tcg_cpus_exec (cpu=cpu@entry=0x556066bbb1e0) at ../accel/tcg/tcg-accel-ops.c:81
+        ret = <optimized out>
+        __PRETTY_FUNCTION__ = "tcg_cpus_exec"
+#11 0x000055606592a9a7 in mttcg_cpu_thread_fn (arg=arg@entry=0x556066bbb1e0) at ../accel/tcg/tcg-accel-ops-mttcg.c:95
+        r = <optimized out>
+
+                  force_rcu = {notifier = {notify = 0x55606592aac0 <mttcg_force_rcu>, node = {le_next = 0x0, le_prev = 0x7fe2e951d4a0}}, cpu = 0x556066bbb1e0}
+        cpu = 0x556066bbb1e0
+        __PRETTY_FUNCTION__ = "mttcg_cpu_thread_fn"
+        __func__ = "mttcg_cpu_thread_fn"
+#12 0x0000556065aa2e91 in qemu_thread_start (args=<optimized out>) at ../util/qemu-thread-posix.c:541
+
+                    __cancel_buf = {__cancel_jmp_buf = {{__cancel_jmp_buf = {140612553791040, -3809744250012005023, 93872529245600, 25, 140612607756368, 140729970282144, -7051494707616903839, -3809738403745854111}, __mask_was_saved = 0}}, __pad = {0x7fe2e951c970, 0x0, 0x0, 0x0}}
+        __cancel_routine = 0x556065aa2ee0 <qemu_thread_atexit_notify>
+        __not_first_call = <optimized out>
+        start_routine = 0x55606592a8a0 <mttcg_cpu_thread_fn>
+        arg = 0x556066bbb1e0
+        r = <optimized out>
+#13 0x00007fe2ec894b43 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442
+        ret = <optimized out>
+        pd = <optimized out>
+
+                      unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140729970281792, 7053160723592154465, 140612553791040, 25, 140612607756368, 140729970282144, -7051494707570766495, -7051505217351676575}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
+        not_first_call = <optimized out>
+#14 0x00007fe2ec926a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
+```
diff --git a/results/classifier/gemma3:12b/kernel/1738202 b/results/classifier/gemma3:12b/kernel/1738202
new file mode 100644
index 00000000..14f7d7f1
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1738202
@@ -0,0 +1,32 @@
+
+qemu 2.11 segfaults on elf file that worked with qemu2.7
+
+running on cygwin in Windows 7
+
+QEMU 2.10.93 segfaults:
+$ /opt/qemu2.11/qemu-system-arm -M integratorcp -cpu cortex-m4 -semihosting -nographic -monitor null -serial null -no-reboot -kernel MFWso_Cycle_f1uP2_CUNIT_0.elf
+Segmentation fault
+
+where QEMU 2.7.0 worked:
+$ /opt/qemu2.7/qemu-system-arm -M integratorcp -cpu cortex-m4 -semihosting -nographic -monitor null -serial null -no-reboot -kernel MFWso_Cycle_f1uP2_CUNIT_0.elf
+------------ CUnit_MFWso_Cycle_f1 ------------
+
+
+     CUnit - A Unit testing framework for C - Version 2.1-0
+     http://cunit.sourceforge.net/
+
+
+Suite: Suite_MFWso_Cycle_f1
+  Test: MFWso_Cycle_f1() ... passed
+  Test: MFWso_GetPhysicalStateData() ... passed
+  Test: MFWso_GetOutputData() ... passed
+  Test: MFWso_GetSafeChannelOK() ... passed
+
+--Run Summary: Type      Total     Ran  Passed  Failed
+               suites        1       1     n/a       0
+               tests         4       4       4       0
+               asserts      54      54      54       0
+
+----------------------------------------
+
+Omitting the -cpu parameter results (for both versions) to hang of qemu (no output, no end, full cpu load).
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1738434 b/results/classifier/gemma3:12b/kernel/1738434
new file mode 100644
index 00000000..843a55b4
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1738434
@@ -0,0 +1,29 @@
+
+CALL FWORD PTR [ESP] handled incorrectly
+
+To keep the story short, this 32-bit code crashes on 64-bit Windows whereas it works fine on real system and VMware:
+
+    push 33h
+    push offset _far_call
+    call fword ptr[esp]
+    jmp _ret
+_far_call:
+    retf
+_ret:
+
+32-bit code running under WoW64 on 64-bit Windows has the ability to switch to the 64-bit mode via so called "Heaven's gate". In order to do that you have to make a far call/jmp by 0x33 selector how the code snippet above shows. QEMU throws an access violation exception whereas the code snippet runs with no problems on real CPU and VMware. By the way, this code works fine under QEMU, I hope it gives you a hint where to look:
+
+    push 23h
+    push offset _far_call
+    call fword ptr[esp]
+    jmp _ret
+_far_call:
+    retf
+_ret:
+
+0x23 is a default 32-bit selector for 32-bit processes running under WoW64.
+
+Environment:
+QEMU: 2.10.93, command line: qemu-system-x86_64.exe -m 2G -snapshot -cdrom full_path_to_iso fullP_path_to_img
+Guest OS: Windows 7 x64 SP1 build 7601 or Windows 10 version 1709 build 16299.19
+Host OS: Windows 10 x64 version 1703 build 15063.786
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1738691 b/results/classifier/gemma3:12b/kernel/1738691
new file mode 100644
index 00000000..93deefc1
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1738691
@@ -0,0 +1,207 @@
+
+Guest kernel crashes with kvm_pr on POWER8
+
+When attempting to use the kvm_pr module with QEMU 2.10 on a POWER8 host, Debian and Ubuntu guests hang and show crashes.
+
+Host kernel is 4.14.  Issue is observed with host kernels 4.9 and 4.13 as well; no other host kernels were tested.
+
+Is this the correct place to report a kvm_pr bug?
+
+Output from Ubuntu 17.10 guest:
+
+Quiescing Open Firmware ...
+Booting Linux via __start() @ 0x0000000002000000 ...
+[    0.000000] Page sizes from device-tree:
+[    0.000000] base_shift=12: shift=12, sllp=0x0000, avpnm=0x00000000, tlbiel=1, penc=0
+[    0.000000] base_shift=16: shift=16, sllp=0x0110, avpnm=0x00000000, tlbiel=1, penc=1
+[    0.000000] base_shift=24: shift=24, sllp=0x0100, avpnm=0x00000001, tlbiel=0, penc=0
+[    0.000000] Using 1TB segments
+[    0.000000] Initializing hash mmu with SLB
+[    0.000000] Linux version 4.13.0-16-generic (buildd@bos01-ppc64el-029) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:37:02 UTC 2017 (Ubuntu 4.13.0-16.19-generic 4.13.4)
+[    0.000000] Found initrd at 0xc000000003b00000:0xc0000000048cf68b
+[    0.000000] Using pSeries machine description
+[    0.000000] bootconsole [udbg0] enabled
+[    0.000000] Partition configured for 2 cpus.
+[    0.000000] CPU maps initialized for 1 thread per core
+ -> smp_release_cpus()
+spinning_secondaries = 1
+ <- smp_release_cpus()
+[    0.000000] -----------------------------------------------------
+[    0.000000] ppc64_pft_size    = 0x19
+[    0.000000] phys_mem_size     = 0x100000000
+[    0.000000] dcache_bsize      = 0x80
+[    0.000000] icache_bsize      = 0x80
+[    0.000000] cpu_features      = 0x077c7a6c18500249
+[    0.000000]   possible        = 0x5fffffff18500649
+[    0.000000]   always          = 0x0000000018100040
+[    0.000000] cpu_user_features = 0xdc0065c2 0xae000000
+[    0.000000] mmu_features      = 0x7c006001
+[    0.000000] firmware_features = 0x00000000415a445f
+[    0.000000] htab_hash_mask    = 0x3ffff
+[    0.000000] -----------------------------------------------------
+[    0.000000] numa:   NODE_DATA [mem 0xfffd7c80-0xfffe3fff]
+[    0.000000] PCI host bridge /pci@800000020000000  ranges:
+[    0.000000]   IO 0x0000200000000000..0x000020000000ffff -> 0x0000000000000000
+[    0.000000]  MEM 0x0000200080000000..0x00002000ffffffff -> 0x0000000080000000
+[    0.000000]  MEM 0x0000210000000000..0x000021ffffffffff -> 0x0000210000000000
+[    0.000000] PPC64 nvram contains 65536 bytes
+[    0.000000] Zone ranges:
+[    0.000000]   DMA      [mem 0x0000000000000000-0x00000000ffffffff]
+[    0.000000]   DMA32    empty
+[    0.000000]   Normal   empty
+[    0.000000]   Device   empty
+[    0.000000] Movable zone start for each node
+[    0.000000] Early memory node ranges
+[    0.000000]   node   0: [mem 0x0000000000000000-0x00000000ffffffff]
+[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x00000000ffffffff]
+[    0.000000] percpu: Embedded 4 pages/cpu @c0000000ffe00000 s162840 r0 d99304 u524288
+[    0.000000] Built 1 zonelists in Node order, mobility grouping on.  Total pages: 65472
+[    0.000000] Policy zone: DMA
+[    0.000000] Kernel command line: BOOT_IMAGE=/install/vmlinux file=/cdrom/preseed/ubuntu-server.seed no_timer_check printk.time=1 ---
+[    0.000000] PID hash table entries: 4096 (order: -1, 32768 bytes)
+[    0.000000] Memory: 4070016K/4194304K available (12800K kernel code, 2048K rwdata, 3456K rodata, 4608K init, 3021K bss, 124288K reserved, 0K cma-reserved)
+[    0.000000] random: get_random_u64 called from cache_random_seq_create+0x80/0x180 with crng_init=0
+[    0.000000] SLUB: HWalign=128, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
+[    0.000000] ftrace: allocating 33631 entries in 13 pages
+[    0.000000] Hierarchical RCU implementation.
+[    0.000000]  RCU restricting CPUs from NR_CPUS=2048 to nr_cpu_ids=2.
+[    0.000000]  Tasks RCU enabled.
+[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
+[    0.000000] NR_IRQS: 512, nr_irqs: 512, preallocated irqs: 16
+[    0.000006] clocksource: timebase: mask: 0xffffffffffffffff max_cycles: 0x761537d007, max_idle_ns: 440795202126 ns
+[    0.000696] clocksource: timebase mult[1f40000] shift[24] registered
+[    0.001189] Console: colour dummy device 80x25
+[    0.001500] console [hvc0] enabled
+[    0.001500] console [hvc0] enabled
+[    0.001751] bootconsole [udbg0] disabled
+[    0.001751] bootconsole [udbg0] disabled
+[    0.002142] pid_max: default: 32768 minimum: 301
+[    0.002358] Security Framework initialized
+[    0.002377] Yama: becoming mindful.
+[    0.002466] AppArmor: AppArmor initialized
+[    0.007008] Dentry cache hash table entries: 524288 (order: 6, 4194304 bytes)
+[    0.009037] Inode-cache hash table entries: 262144 (order: 5, 2097152 bytes)
+[    0.009144] Mount-cache hash table entries: 8192 (order: 0, 65536 bytes)
+[    0.009282] Mountpoint-cache hash table entries: 8192 (order: 0, 65536 bytes)
+[    0.011066] EEH: pSeries platform initialized
+[    0.011137] POWER8 performance monitor hardware support registered
+[    0.011231] Hierarchical SRCU implementation.
+[    0.012560] smp: Bringing up secondary CPUs ...
+[    0.014620] smp: Brought up 1 node, 2 CPUs
+[    0.014669] numa: Node 0 CPUs: 0-1
+[    0.017357] devtmpfs: initialized
+[    0.020796] evm: security.selinux
+[    0.020816] evm: security.SMACK64
+[    0.020832] evm: security.SMACK64EXEC
+[    0.020849] evm: security.SMACK64TRANSMUTE
+[    0.020865] evm: security.SMACK64MMAP
+[    0.020882] evm: security.ima
+[    0.020898] evm: security.capability
+[    0.021384] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
+[    0.021428] futex hash table entries: 512 (order: 0, 65536 bytes)
+[    0.022217] NET: Registered protocol family 16
+[    0.023456] EEH: No capable adapters found
+[    0.068790] KVM: Live patching for a fast VM worked
+[    0.069504] cpuidle: using governor ladder
+[    0.069606] cpuidle: using governor menu
+[    0.070109] pstore: using zlib compression
+[    0.070162] pstore: Registered nvram as persistent store backend
+Linux ppc64le
+#19-Ubuntu SMP W[    0.073385] PCI: Probing PCI hardware
+[    0.073595] PCI host bridge to bus 0000:00
+[    0.073650] pci_bus 0000:00: root bus resource [io  0x10000-0x1ffff] (bus address [0x0000-0xffff])
+[    0.073722] pci_bus 0000:00: root bus resource [mem 0x200080000000-0x2000ffffffff] (bus address [0x80000000-0xffffffff])
+[    0.073827] pci_bus 0000:00: root bus resource [mem 0x210000000000-0x21ffffffffff]
+[    0.073913] pci_bus 0000:00: root bus resource [bus 00-ff]
+[    0.081145] IOMMU table initialized, virtual merging enabled
+[    0.081231] iommu: Adding device 0000:00:00.0 to group 0
+[    0.083493] HugeTLB registered 16.0 MiB page size, pre-allocated 0 pages
+[    0.085216] SCSI subsystem initialized
+[    0.085722] vgaarb: loaded
+[    0.085885] usbcore: registered new interface driver usbfs
+[    0.085961] usbcore: registered new interface driver hub
+[    0.086096] usbcore: registered new device driver usb
+[    0.086175] pps_core: LinuxPPS API ver. 1 registered
+[    0.086217] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <email address hidden>
+[    0.086316] PTP clock support registered
+[    0.086629] EDAC MC: Ver: 3.0.0
+[    0.087455] NetLabel: Initializing
+[    0.087509] NetLabel:  domain hash size = 128
+[    0.087550] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
+[    0.087676] NetLabel:  unlabeled traffic allowed by default
+[    0.088226] clocksource: Switched to clocksource timebase
+[    0.109127] VFS: Disk quotas dquot_6.6.0
+[    0.109244] VFS: Dquot-cache hash table entries: 8192 (order 0, 65536 bytes)
+[    0.109543] AppArmor: AppArmor Filesystem Enabled
+[    0.121635] NET: Registered protocol family 2
+[    0.122074] TCP established hash table entries: 32768 (order: 2, 262144 bytes)
+[    0.122584] TCP bind hash table entries: 32768 (order: 3, 524288 bytes)
+[    0.123346] TCP: Hash tables configured (established 32768 bind 32768)
+[    0.123472] UDP hash table entries: 2048 (order: 0, 65536 bytes)
+[    0.123692] UDP-Lite hash table entries: 2048 (order: 0, 65536 bytes)
+[    0.123937] NET: Registered protocol family 1
+[    0.124257] Unpacking initramfs...
+[    0.467838] Freeing initrd memory: 14080K
+[    0.472109] audit: initializing netlink subsys (disabled)
+[    0.472949] audit: type=2000 audit(1513569522.428:1): state=initialized audit_enabled=0 res=1
+[    0.473972] Initialise system trusted keyrings
+[    0.474068] Key type blacklist registered
+[    0.474308] workingset: timestamp_bits=38 max_order=16 bucket_order=0
+[    0.476124] zbud: loaded
+[    0.477006] squashfs: version 4.0 (2009/01/31) Phillip Lougher
+[    0.477456] fuse init (API version 7.26)
+[    0.478394] random: fast init done
+[    0.483013] Key type asymmetric registered
+[    0.483040] Asymmetric key parser 'x509' registered
+[    0.483150] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
+[    0.483363] io scheduler noop registered
+[    0.483383] io scheduler deadline registered
+[    0.483450] io scheduler cfq registered (default)
+[    0.484056] virtio-pci 0000:00:00.0: enabling device (0100 -> 0103)
+[    0.485519] virtio-pci 0000:00:00.0: ibm,query-pe-dma-windows(2026) 0 8000000 20000000 returned 0
+[    0.485916] virtio-pci 0000:00:00.0: ibm,create-pe-dma-window(2027) 0 8000000 20000000 10 20 returned 0 (liobn = 0x80000001 starting addr = 8000000 0)
+[    0.501557] virtio-pci 0000:00:00.0: Using 64-bit direct DMA at offset 800000000000000
+[    0.503803] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
+[    0.507398] Linux agpgart interface v0.103
+[    0.511296] loop: module loaded
+[    0.511671] libphy: Fixed MDIO Bus: probed
+[    0.511698] tun: Universal TUN/TAP device driver, 1.6
+[    0.511860] PPP generic driver version 2.4.2
+[    0.512086] VFIO - User Level meta-driver version: 0.3
+[    0.512309] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
+[    0.512367] ehci-pci: EHCI PCI platform driver
+[    0.512420] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
+[    0.512457] ohci-pci: OHCI PCI platform driver
+[    0.512501] uhci_hcd: USB Universal Host Controller Interface driver
+[    0.512814] mousedev: PS/2 mouse device common for all mice
+[    0.513152] rtc-generic rtc-generic: rtc core: registered rtc-generic as rtc0
+[    0.513200] i2c /dev entries driver
+[    0.513320] device-mapper: uevent: version 1.0.3
+[    0.513482] device-mapper: ioctl: 4.36.0-ioctl (2017-06-09) initialised: <email address hidden>
+[    0.513710] ledtrig-cpu: registered to indicate activity on CPUs
+[    0.514095] NET: Registered protocol family 10
+[    0.526547] modprobe[89]: unhandled signal 11 at 0000000000000008 nip 000073724fd9645c lr 000073724fd855c0 code 30001
+[    0.528919] modprobe[90]: unhandled signal 11 at 00000000001e4250 nip 000076c0ae90e0f8 lr 000076c0ae90e6a4 code 30001
+[    0.529819] Segment Routing with IPv6
+[    0.529874] NET: Registered protocol family 17
+[    0.529922] Key type dns_resolver registered
+[    0.530832] registered taskstats version 1
+[    0.530902] Loading compiled-in X.509 certificates
+[    0.531719] modprobe[93]: unhandled signal 11 at 0000000000000008 nip 0000741ba74e645c lr 0000741ba74d55c0 code 30001
+[    0.532899] modprobe[94]: unhandled signal 11 at 0000000000000008 nip 0000764dd97f645c lr 0000764dd97e55c0 code 30001
+[    0.534414] Loaded X.509 cert 'Build time autogenerated kernel key: bc297e5938e0456833a4c0c157e5483b77785cf1'
+[    0.534505] zswap: loaded using pool lzo/zbud
+[    0.535375] modprobe[97]: unhandled signal 11 at 0000000000000008 nip 00007e85a34b645c lr 00007e85a34a55c0 code 30001
+[    0.536618] modprobe[98]: unhandled signal 11 at 0000000000000008 nip 0000713d7724645c lr 0000713d772355c0 code 30001
+[    0.537392] Key type big_key registered
+[    0.537418] Key type trusted registered
+[    0.545589] Key type encrypted registered
+[    0.545642] AppArmor: AppArmor sha1 policy hashing enabled
+[    0.545689] ima: No TPM chip found, activating TPM-bypass! (rc=-19)
+[    0.545799] evm: HMAC attrs: 0x1
+[    0.551224] rtc-generic rtc-generic: setting system clock to 2017-12-18 03:58:43 UTC (1513569523)
+[    0.552107] Unable to open file: /etc/keys/x509_ima.der (-2)
+[    0.552109] Unable to open file: /etc/keys/x509_evm.der (-2)
+[    0.591193] Freeing unused kernel memory: 4608K
+[    0.591643] This architecture does not have kernel memory protection.
+<hang>
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1738767 b/results/classifier/gemma3:12b/kernel/1738767
new file mode 100644
index 00000000..32589a43
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1738767
@@ -0,0 +1,13 @@
+
+Cannot build QEMU on RHEL6 because of MAP_HUGETLB
+
+Hello,
+I've just downloaded qemu-2.11.0 sources and I wanted to build QEMU on RHEL6 x86_64, for various targets, amonst which arm-linux-user.
+
+The build fails because /usr/include/bits/mman.h does not define MAP_HUGETLB.
+
+I think it is needed since commit 541e16904.
+
+I'm not sure if RHEL6 is still supported by QEMU? If so, can you fix this problem?
+
+Thanks
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1739371 b/results/classifier/gemma3:12b/kernel/1739371
new file mode 100644
index 00000000..6e0b5bea
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1739371
@@ -0,0 +1,72 @@
+
+qemu-system-arm snapshot loadvm core dumped
+
+Ubuntu Qemu is crashing trying to restore saved snapshot in qemu-system-arm.
+I've tried different guests kernels, but I wasn't lucky with any of them.
+
+The guest vm boots and I can use it normally. The issue is when I save the snapshot using "savevm Base0", "quit" and then I restore that snapshot using "-loadvm Base0" from the cmd line.
+
+The only difference I've noticed is tweaking the guest memory:
+* With -m 512 or 1024 it crashes as you can see below.
+* With -m 2048 it doesn't crash, it restores the vm and I can see the screen as it was, but the OS is halted. And it's not just the keyboard. I've tried saving the snapshot while it's booting with lot of lines being printed on screen and after restoring it, the OS is frozen.
+
+I also tried limiting the guest kernel memory using the mem parameter (mem=2048M) and disabling the kernel address space randomization (nokaslr) with the same results.
+
+OS: Ubuntu 16.04.3 LTS (xenial)
+
+$ qemu-system-arm --version
+QEMU emulator version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.16), Copyright (c) 2003-2008 Fabrice Bellard
+
+$ qemu-system-arm -kernel kernel/vmlinuz-4.10.0-42-generic -initrd kernel/initrd.img-4.10.0-42-generic -M vexpress-a15 -m 512 -append 'root=/dev/mmcblk0 rootwait console=tty0' -sd vexpress-4G.qcow2 -dtb device-tree/vexpress-v2p-ca15-tc1.dtb  -loadvm Base0
+pulseaudio: set_sink_input_volume() failed
+pulseaudio: Reason: Invalid argument
+pulseaudio: set_sink_input_mute() failed
+pulseaudio: Reason: Invalid argument
+qemu: fatal: Trying to execute code outside RAM or ROM at 0xc0321568
+
+R00=00000001 R01=00000000 R02=00000000 R03=c0321560
+R04=c1500000 R05=c150529c R06=c1505234 R07=c14384d0
+R08=00000000 R09=00000000 R10=c1501f50 R11=c1501f3c
+R12=c1501f40 R13=c1501f30 R14=c030a184 R15=c0321568
+PSR=60070093 -ZC- A S svc32
+s00=6374652f s01=636f6c2f d00=636f6c2f6374652f
+s02=7273752f s03=6962732f d01=6962732f7273752f
+s04=6e612f6e s05=6f726361 d02=6f7263616e612f6e
+s06=7c7c206e s07=63202820 d03=632028207c7c206e
+s08=202f2064 s09=72202626 d04=72202626202f2064
+s10=702d6e75 s11=73747261 d05=73747261702d6e75
+s12=722d2d20 s13=726f7065 d06=726f7065722d2d20
+s14=652f2074 s15=632f6374 d07=632f6374652f2074
+s16=00000000 s17=00000000 d08=0000000000000000
+s18=00000000 s19=00000000 d09=0000000000000000
+s20=00000000 s21=00000000 d10=0000000000000000
+s22=00000000 s23=00000000 d11=0000000000000000
+s24=00000000 s25=00000000 d12=0000000000000000
+s26=00000000 s27=00000000 d13=0000000000000000
+s28=00000000 s29=00000000 d14=0000000000000000
+s30=00000000 s31=00000000 d15=0000000000000000
+s32=00000000 s33=00000000 d16=0000000000000000
+s34=00000000 s35=00000000 d17=0000000000000000
+s36=00000000 s37=00000000 d18=0000000000000000
+s38=00000000 s39=00000000 d19=0000000000000000
+s40=00000000 s41=00000000 d20=0000000000000000
+s42=00000000 s43=00000000 d21=0000000000000000
+s44=00000000 s45=00000000 d22=0000000000000000
+s46=00000000 s47=00000000 d23=0000000000000000
+s48=00000000 s49=00000000 d24=0000000000000000
+s50=00000000 s51=00000000 d25=0000000000000000
+s52=00000000 s53=00000000 d26=0000000000000000
+s54=00000000 s55=00000000 d27=0000000000000000
+s56=00000000 s57=00000000 d28=0000000000000000
+s58=00000000 s59=00000000 d29=0000000000000000
+s60=00000000 s61=00000000 d30=0000000000000000
+s62=00000000 s63=00000000 d31=0000000000000000
+FPSCR: 00000000
+Aborted (core dumped)
+
+As I said above, the same happens when -m 1024 is used.
+
+I have a different issue when I use the qemu git master version, but I'm submiting a different ticket for that.
+
+Cheers,
+Gus
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1740 b/results/classifier/gemma3:12b/kernel/1740
new file mode 100644
index 00000000..3a8bab91
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1740
@@ -0,0 +1,74 @@
+
+QEMU Abort in Cortex-M Exception raising
+Description of problem:
+When an exception should be raised in a ARM Cortex-M board QEMU aborts.
+
+```
+$ qemu-system-arm --version
+QEMU emulator version 8.0.2
+
+$ qemu-system-arm -M stm32vldiscovery -device loader,file=/tmp/raw-hardfault.hex -d in_asm,exec,int
+[...]
+Trace 0: 0x7f2aa8000680 [00800400/00000110/00000110/ff200000]
+----------------
+IN:
+0x00000140:  f64b 6eef  movw     lr, #0xbeef
+0x00000144:  f6cd 6ead  movt     lr, #0xdead
+0x00000148:  4770       bx       lr
+
+Linking TBs 0x7f2aa8000680 index 0 -> 0x7f2aa80007c0
+Trace 0: 0x7f2aa80007c0 [00800400/00000140/00000110/ff200000]
+qemu-system-arm: ../qemu-8.0.2/target/arm/cpu.h:2396: arm_is_secure_below_el3: Assertion `!arm_feature(env, ARM_FEATURE_M)' failed.
+```
+
+Expected behavior:
+```
+$ qemu-system-arm --version
+QEMU emulator version 7.1.0
+
+$ qemu-system-arm -M stm32vldiscovery -device loader,file=raw-hardfault.hex -d in_asm,exec,int
+[...]
+Trace 0: 0x7fb488000680 [00800400/00000110/00000110/ff000000]
+----------------
+IN:
+0x00000140:  f64b 6eef  movw     lr, #0xbeef
+0x00000144:  f6cd 6ead  movt     lr, #0xdead
+0x00000148:  4770       bx       lr
+
+Linking TBs 0x7fb488000680 [00000110] index 0 -> 0x7fb488000780 [00000140]
+Trace 0: 0x7fb488000780 [00800400/00000140/00000110/ff000000]
+Taking exception 3 [Prefetch Abort] on CPU 0
+...at fault address 0xdeadbeee
+...with CFSR.IACCVIOL
+...BusFault with BFSR.STKERR
+...taking pending nonsecure exception 3
+...loading from element 3 of non-secure vector table at 0xc
+...loaded new PC 0x0
+```
+Steps to reproduce:
+1. Run any Cortex-M firmware that raises an exception. (minimal example attached)
+Additional information:
+- Minimal Reproducer:
+[raw-hardfault.hex](/uploads/113889116675b608e05748280d1db354/raw-hardfault.hex)
+- Assert introduced in fcc7404eff24b4c8b322fb27ca5ae7f3113129c3.
+- Stacktrace:
+```
+#4  0x00007ffff6a483d6 in __assert_fail () from /usr/lib/libc.so.6
+#5  0x00007ffff73afe67 in arm_is_secure_below_el3 (env=0x55555712f9b0) at target/arm/cpu.h:2396
+#6  0x00007ffff73afedd in arm_is_el2_enabled (env=0x55555712f9b0) at target/arm/cpu.h:2448
+#7  0x00007ffff73afcd4 in arm_el_is_aa64 (env=0x55555712f9b0, el=0x1) at target/arm/cpu.h:2509
+#8  0x00007ffff73af68f in compute_fsr_fsc (env=0x55555712f9b0, fi=0x7fffffff7098, target_el=0x1, mmu_idx=0x1, ret_fsc=0x7fffffff6fe0)
+    at target/arm/tcg/tlb_helper.c:71
+#9  0x00007ffff73af483 in arm_deliver_fault (cpu=0x55555712d250, addr=0xdeadbeee, access_type=MMU_INST_FETCH, mmu_idx=0x1, fi=0x7fffffff7098)
+    at target/arm/tcg/tlb_helper.c:114
+#10 0x00007ffff73afa4c in arm_cpu_tlb_fill (cs=0x55555712d250, address=0xdeadbeee, size=0x1, access_type=MMU_INST_FETCH, mmu_idx=0x1, probe=0x0, retaddr=0x0)
+    at target/arm/tcg/tlb_helper.c:242
+#11 0x00007ffff74a3a1e in probe_access_internal (env=0x55555712f9b0, addr=0xdeadbeee, fault_size=0x1, access_type=MMU_INST_FETCH, mmu_idx=0x1, nonfault=0x0, phost=0x7fffffff71c8,
+    pfull=0x7fffffff71d0, retaddr=0x0) at accel/tcg/cputlb.c:1555
+#12 0x00007ffff74a4085 in get_page_addr_code_hostp (env=0x55555712f9b0, addr=0xdeadbeee, hostp=0x0) at accel/tcg/cputlb.c:1694
+#13 0x00007ffff7490c0f in get_page_addr_code (env=0x55555712f9b0, addr=0xdeadbeee) at include/exec/exec-all.h:748
+#14 0x00007ffff7490b2a in tb_htable_lookup (cpu=0x55555712d250, pc=0xdeadbeee, cs_base=0x800408, flags=0x110, cflags=0xff200200) at accel/tcg/cpu-exec.c:233
+#15 0x00007ffff748f719 in tb_lookup (cpu=0x55555712d250, pc=0xdeadbeee, cs_base=0x800408, flags=0x110, cflags=0xff200200) at accel/tcg/cpu-exec.c:270
+#16 0x00007ffff748f463 in helper_lookup_tb_ptr (env=0x55555712f9b0) at accel/tcg/cpu-exec.c:425
+#17 0x00007fff6800091c in code_gen_buffer ()
+```
diff --git a/results/classifier/gemma3:12b/kernel/1740887 b/results/classifier/gemma3:12b/kernel/1740887
new file mode 100644
index 00000000..5a37f744
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1740887
@@ -0,0 +1,17 @@
+
+qemu-system-arm & qemu-system-aarch64 for windows crash at start
+
+In Windows 7 64 bit (both 32 & 64 bit QEMU emulator version 2.11.0 (v2.11.0-11693-g21057c841e-dirty)).
+
+With arguments:
+
+qemu-system-arm.exe -M raspi2
+
+It crashes and reports:
+
+ERROR:/home/stefan/src/qemu/repo.or.cz/qemu/ar7/qom/object.c:176:type_get_parent: assertion failed: (type->parent_type != NULL)
+
+Same goes for qemu-system-aarch64.exe or with -M raspi argument.
+
+Have a nice day,
+f.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1741 b/results/classifier/gemma3:12b/kernel/1741
new file mode 100644
index 00000000..c49a21c6
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1741
@@ -0,0 +1,2 @@
+
+95059f9c313a7fbd7f22e4cdc1977c0393addc7b breaks some 32bit architectures in linux-user on amd64
diff --git a/results/classifier/gemma3:12b/kernel/1741718 b/results/classifier/gemma3:12b/kernel/1741718
new file mode 100644
index 00000000..1ab491a8
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1741718
@@ -0,0 +1,87 @@
+
+qemu-system-sparc64: "panic[cpu0]/thread=180e000: lgrp_traverse: No memory blocks found" with tribblix-sparc-0m16.iso
+
+qemu-system-sparc64 Niagara VM running Tribblix crashes with "panic[cpu0]/thread=180e000: lgrp_traverse: No memory blocks found" on QEMU 2.11.0. Happens also with 1 GB, 4 GB, and 8 GB of RAM.
+
+$ qemu-system-sparc64 -nographic -M niagara -L /home/newman/Downloads/OpenSPARCT1_Arch.1.5/S10image/ -drive if=pflash,readonly=on,file=/home/newman/Downloads/tribblix-sparc-0m16.iso -m 2048
+cpu Probing I/O buses
+
+
+Sun Fire T2000, No Keyboard
+Copyright 2005 Sun Microsystems, Inc.  All rights reserved.
+OpenBoot 4.20.0, 256 MB memory available, Serial #1122867.
+[mo23723 obp4.20.0 #0]
+Ethernet address 0:80:3:de:ad:3, Host ID: 80112233.
+
+
+
+ok boot
+Boot device: vdisk  File and args: 
+hsfs-file-system 
+Loading: /platform/sun4v/boot_archive
+ramdisk-root ufs-file-system 
+Loading: /platform/sun4v/kernel/sparcv9/unix
+\
+panic[cpu0]/thread=180e000: lgrp_traverse: No memory blocks found
+
+Warning - stack not written to the dumpbuf
+000000000180b710 unix:lgrp_traverse+120 (fff32000, 10d5f30, 2000, 7efefeff, 81010100, ff00)
+  %l0-3: 0000000001876c00 ffffffffffffffff 00000000010d6c00 0000000000000000
+  %l4-7: 800000008f000740 800000008fc54750 00000000f0254cc4 00000000010dedd0
+000000000180b800 unix:plat_lgrp_init+14 (4, 180e000, 4, 0, 180b950, 1)
+  %l0-3: 00000000fff32000 00000000fff340e0 00000000fff34590 00000000010d5f28
+  %l4-7: 0000000000000016 0000000000000000 0000000000000016 0000000000000011
+000000000180b8b0 unix:lgrp_plat_init+74 (0, 0, 0, 180ba08, 180ba00, 91)
+  %l0-3: 0000000000002000 00000000fff34000 0000000001874c00 0000000001874c00
+  %l4-7: 0000000000000000 0000000001874c00 000000000180b950 00000000010de048
+000000000180b960 unix:lgrp_init+4 (0, 2000, 70002000, 0, 180c0e8, 0)
+  %l0-3: 000000000180e380 000000000183c678 000000000180ba08 00000000010d4f90
+  %l4-7: 00000000010d4fa0 00000000010d1c00 0000000000004000 0000000080001070
+000000000180ba10 unix:mlsetup+2f4 (180bb80, 180bec0, 0, 0, f025496c, 0)
+  %l0-3: 00000000018ee000 0000000070002000 0000000070002000 000000000180bad0
+  %l4-7: 000000000190c4d8 00000001001f56e0 0000000000000000 0000000080001070
+
+
+ERROR: Last Trap: Level 14 Interrupt
+[Exception handlers interrupted, please file a bug]
+[type 'resume' to attempt a normal recovery]
+
+
+Without "if=pflash" VM hangs:
+
+$ qemu-system-sparc64 -nographic -M niagara -L /home/newman/Downloads/OpenSPARCT1_Arch.1.5/S10image/ -drive readonly=on,file=/home/newman/Downloads/tribblix-sparc-0m16.iso -m 4096
+cpu Probing I/O buses
+
+
+Sun Fire T2000, No Keyboard
+Copyright 2005 Sun Microsystems, Inc.  All rights reserved.
+OpenBoot 4.20.0, 256 MB memory available, Serial #1122867.
+[mo23723 obp4.20.0 #0]
+Ethernet address 0:80:3:de:ad:3, Host ID: 80112233.
+
+
+
+ok boot
+Boot device: vdisk  File and args: 
+qemu: fatal: Trap 0x0032 while trap level (6) >= MAXTL (6), Error state
+pc: 000000000040f01c  npc: 000000000040f020
+%g0-3: 0000000000000000 0000000000000000 0000000000000000 0000009700000280
+%g4-7: 0000000000001000 0000000000000000 0000000000000000 0000000000000000
+%o0-3: 0000000000000000 000000008ffd6000 0000000000008000 0000000000000000 
+%o4-7: 0000000000000000 00000000000000f0 00000000fff55701 00000000f020d78c 
+%l0-3: 000000000002fd10 7ffffffffffffffe 8000000000000000 0000000000000000 
+%l4-7: 000000000000000b 800000008fffa750 00000000f026fbf0 00000000f022a0d8 
+%i0-3: 0000000080000000 0000000010000000 0000000000000000 0000000000000000 
+%i4-7: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 
+%f00:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%f08:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%f16:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%f24:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%f32:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%f40:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%f48:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%f56:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
+pstate: 00000014 ccr: 11 (icc: ---C xcc: ---C) asi: 20 tl: 6 pil: d gl: 6
+tbr: 00000000f0200000 hpstate: 0000000000000004 htba: 0000000000400000
+cansave: 6 canrestore: 0 otherwin: 0 wstate: 0 cleanwin: 7 cwp: 0
+fsr: 0000000000000000 y: 0000000000000000 fprs: 0000000000000004
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1742 b/results/classifier/gemma3:12b/kernel/1742
new file mode 100644
index 00000000..dc6c2383
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1742
@@ -0,0 +1,96 @@
+
+Arm64 kernel run with qemu-system-aarch64 crashes handling program using SVE and Streaming SVE modes
+Description of problem:
+The userspace program shown, which switches between SVE/SME states, crashes the kernel on task switch when running under qemu-system-aarch64. This does not reproduce on an Arm Fast Model, but I can't be sure that that is not a timing difference.
+
+The kernel appears to have no space allocated to save SVE state for this process, but also believes that it should save the state, where it then faults.
+Steps to reproduce:
+1. Compile the following program:
+```
+#include <sys/prctl.h>
+
+int main() {
+  asm volatile("msr  s0_3_c4_c7_3, xzr" /*smstart*/);
+  prctl(PR_SVE_SET_VL, 8 * 4);
+  asm volatile("msr  s0_3_c4_c7_3, xzr" /*smstart*/);
+  while (1) {} // Wait to be preempted?
+  return 0;
+}
+```
+With:
+```
+$ aarch64-unknown-linux-gnu-gcc main.c -o main.o -g -O3 -march=armv8.6-a+sve
+```
+Compiler version does not matter I don't think, but in case:
+```
+$ aarch64-unknown-linux-gnu-gcc --version
+aarch64-unknown-linux-gnu-gcc (crosstool-NG 1.25.0.85_61c4cca) 10.4.0
+```
+It is a 10.4.0 built with CrossToolNG.
+
+2. Boot Linux and run the program in the emulated environment. I've found looping it to be more consistent:
+```
+$ while true; do ./main.o; done
+```
+Though sometimes it will crash after only one run.
+Additional information:
+Here is the output from the kernel:
+```
+$ /mnt/virt_root/sme_crash/main.o
+[  190.813392] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
+[  190.818912] Mem abort info:
+[  190.819255]   ESR = 0x0000000096000046
+[  190.819727]   EC = 0x25: DABT (current EL), IL = 32 bits
+[  190.820391]   SET = 0, FnV = 0
+[  190.820757]   EA = 0, S1PTW = 0
+[  190.821145]   FSC = 0x06: level 2 translation fault
+[  190.821635] Data abort info:
+[  190.821978]   ISV = 0, ISS = 0x00000046, ISS2 = 0x00000000
+[  190.822490]   CM = 0, WnR = 1, TnD = 0, TagAccess = 0
+[  190.822991]   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
+[  190.823645] user pgtable: 4k pages, 48-bit VAs, pgdp=00000000475f1000
+[  190.824269] [0000000000000000] pgd=0800000047645003, p4d=0800000047645003, pud=0800000047641003, pmd=0000000000000000
+[  190.826225] Internal error: Oops: 0000000096000046 [#1] PREEMPT SMP
+[  190.826996] Modules linked in:
+[  190.827748] CPU: 0 PID: 198 Comm: main.o Not tainted 6.4.0-01761-g6aeadf7896bf #1
+[  190.828638] Hardware name: linux,dummy-virt (DT)
+[  190.829304] pstate: 234000c5 (nzCv daIF +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
+[  190.830115] pc : sve_save_state+0x4/0xf0
+[  190.831378] lr : fpsimd_save+0x184/0x1f0
+[  190.831848] sp : ffff80008047bc70
+[  190.832223] x29: ffff80008047bc70 x28: ffff0000036c49c0 x27: 0000000000000000
+[  190.833182] x26: ffff0000036c4f58 x25: ffff0000036c49c0 x24: ffff0000036c5868
+[  190.834045] x23: 0000000000000020 x22: ffff24441ea31000 x21: 0000000000000001
+[  190.834894] x20: ffff00003fdc50b0 x19: ffffdbbc213940b0 x18: 0000000000000000
+[  190.835759] x17: ffff24441ea31000 x16: ffff800080000000 x15: 0000000000000000
+[  190.836593] x14: 000000000000026c x13: 0000000000000001 x12: 0000000000000020
+[  190.837436] x11: 0000000000000000 x10: 0000000000000001 x9 : 0000000000000800
+[  190.838323] x8 : ffff00003fdcffc0 x7 : ffff00003fdcff40 x6 : 0000000002da9c8c
+[  190.839149] x5 : 0000000000000001 x4 : 0000000000000000 x3 : 0000000000000000
+[  190.839976] x2 : 0000000000000001 x1 : ffff0000036c56a0 x0 : 0000000000000440
+[  190.840936] Call trace:
+[  190.841406]  sve_save_state+0x4/0xf0
+[  190.841993]  fpsimd_thread_switch+0x24/0xd4
+[  190.842572]  __switch_to+0x20/0x1d4
+[  190.843043]  __schedule+0x2a0/0xa7c
+[  190.843488]  schedule+0x5c/0xc4
+[  190.843912]  do_notify_resume+0x1a4/0x474
+[  190.844410]  el0_interrupt+0xc4/0xd4
+[  190.844855]  __el0_irq_handler_common+0x18/0x24
+[  190.845350]  el0t_64_irq_handler+0x10/0x1c
+[  190.845824]  el0t_64_irq+0x190/0x194
+[  190.846661] Code: 54000040 d51b4408 d65f03c0 d503245f (e5bb5800)
+[  190.847545] ---[ end trace 0000000000000000 ]---
+[  190.848125] note: main.o[198] exited with irqs disabled
+```
+
+I have looked the kernel functions in the backtrace and it seems to be loading memory fine, so it's not obviously a code generation problem. The pointer loaded prior to the crash is definitely a nullptr.
+
+Removing any of the lines (`while (1) {}` aside) from the example seems to avoid the issue but again, could be timing.
+
+An important point here is that the kernel syscall ABI states that streaming mode will be exited on
+a syscall. I have observed that this does happen as expected. This is why the test case does a syscall, then immediately goes back to streaming mode. And it is perhaps where the confusion starts.
+
+I have confirmed that SME is supported by the emulated CPU and other SME programs do run correctly.
+
+I initially thought this was to do with having many cores, but it reproduces on a single core also.
diff --git a/results/classifier/gemma3:12b/kernel/1750229 b/results/classifier/gemma3:12b/kernel/1750229
new file mode 100644
index 00000000..829d65db
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1750229
@@ -0,0 +1,104 @@
+
+virtio-blk-pci regression: softlock in guest kernel at module loading
+
+Hello,
+
+I am running qemu from master git branch on x86_64 host with kernel is 4.4.114. I've found that commit
+
+    9a4c0e220d8a "hw/virtio-pci: fix virtio behaviour"
+
+introduces an regression with the following command:
+
+    qemu-system-x86_64 -enable-kvm -nodefaults -no-reboot -nographic -vga none -runas qemu -kernel .build.kernel.kvm -initrd .build.initrd.kvm -append 'panic=1 softlockup_panic=1 no-kvmclock nmi_watchdog=0 console=ttyS0 root=/dev/disk/by-id/virtio-0' -m 2048 -drive file=./root,format=raw,if=none,id=disk,serial=0,cache=unsafe -device virtio-blk-pci,drive=disk -serial stdio -smp 2
+
+Starting from this commit to master the following happens with a wide variety of guest kernels (4.4 to 4.15):
+
+[   62.428107] BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=-20 stuck for 59s!
+[   62.437426] Showing busy workqueues and worker pools:
+[   62.443117] workqueue events: flags=0x0
+[   62.447512]   pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256
+[   62.448161]     pending: check_corruption
+[   62.458570] workqueue kblockd: flags=0x18
+[   62.463082]   pwq 1: cpus=0 node=0 flags=0x0 nice=-20 active=3/256
+[   62.463082]     in-flight: 4:blk_mq_run_work_fn
+[   62.463082]     pending: blk_mq_run_work_fn, blk_mq_timeout_work
+[   62.474831] pool 1: cpus=0 node=0 flags=0x0 nice=-20 hung=59s workers=2 idle: 214
+[   62.492121] INFO: rcu_preempt detected stalls on CPUs/tasks:
+[   62.492121]  Tasks blocked on level-0 rcu_node (CPUs 0-1): P4
+[   62.492121]  (detected by 0, t=15002 jiffies, g=-130, c=-131, q=32)
+[   62.492121] kworker/0:0H    R  running task        0     4      2 0x80000000
+[   62.492121] Workqueue: kblockd blk_mq_run_work_fn
+[   62.492121] Call Trace:
+[   62.492121]  <IRQ>
+[   62.492121]  sched_show_task+0xdf/0x100
+[   62.492121]  rcu_print_detail_task_stall_rnp+0x48/0x69
+[   62.492121]  rcu_check_callbacks+0x93d/0x9d0
+[   62.492121]  ? tick_sched_do_timer+0x40/0x40
+[   62.492121]  update_process_times+0x28/0x50
+[   62.492121]  tick_sched_handle+0x22/0x70
+[   62.492121]  tick_sched_timer+0x34/0x70
+[   62.492121]  __hrtimer_run_queues+0xcc/0x250
+[   62.492121]  hrtimer_interrupt+0xab/0x1f0
+[   62.492121]  smp_apic_timer_interrupt+0x62/0x150
+[   62.492121]  apic_timer_interrupt+0xa2/0xb0
+[   62.492121]  </IRQ>
+[   62.492121] RIP: 0010:iowrite16+0x1d/0x30
+[   62.492121] RSP: 0018:ffffa477c034fcc8 EFLAGS: 00010292 ORIG_RAX: ffffffffffffff11
+[   62.492121] RAX: ffffffffa24fbdb0 RBX: ffff92a1f8f82000 RCX: 0000000000000001
+[   62.492121] RDX: ffffa477c0371000 RSI: ffffa477c0371000 RDI: 0000000000000000
+[   62.492121] RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000001080020
+[   62.492121] R10: ffffdc7cc1e4fc00 R11: 0000000000000000 R12: 0000000000000000
+[   62.492121] R13: 0000000000000000 R14: ffff92a1f93f0000 R15: ffff92a1f8e1aa80
+[   62.492121]  ? vp_synchronize_vectors+0x60/0x60
+[   62.492121]  vp_notify+0x12/0x20
+[   62.492121]  virtqueue_notify+0x18/0x30
+[   62.492121]  virtio_queue_rq+0x2f5/0x300 [virtio_blk]
+[   62.492121]  blk_mq_dispatch_rq_list+0x7e/0x4a0
+[   62.492121]  blk_mq_do_dispatch_sched+0x4a/0xd0
+[   62.492121]  blk_mq_sched_dispatch_requests+0x106/0x170
+[   62.492121]  __blk_mq_run_hw_queue+0x80/0x90
+[   62.492121]  process_one_work+0x1e3/0x420
+[   62.492121]  worker_thread+0x2b/0x3d0
+[   62.492121]  ? process_one_work+0x420/0x420
+[   62.492121]  kthread+0x113/0x130
+[   62.492121]  ? kthread_create_worker_on_cpu+0x50/0x50
+[   62.492121]  ret_from_fork+0x3a/0x50
+[   62.492121] kworker/0:0H    R  running task        0     4      2 0x80000000
+[   62.492121] Workqueue: kblockd blk_mq_run_work_fn
+[   62.492121] Call Trace:
+[   62.492121]  <IRQ>
+[   62.492121]  sched_show_task+0xdf/0x100
+[   62.492121]  rcu_print_detail_task_stall_rnp+0x48/0x69
+[   62.492121]  rcu_check_callbacks+0x972/0x9d0
+[   62.492121]  ? tick_sched_do_timer+0x40/0x40
+[   62.492121]  update_process_times+0x28/0x50
+[   62.492121]  tick_sched_handle+0x22/0x70
+[   62.492121]  tick_sched_timer+0x34/0x70
+[   62.492121]  __hrtimer_run_queues+0xcc/0x250
+[   62.492121]  hrtimer_interrupt+0xab/0x1f0
+[   62.492121]  smp_apic_timer_interrupt+0x62/0x150
+[   62.492121]  apic_timer_interrupt+0xa2/0xb0
+[   62.492121]  </IRQ>
+[   62.492121] RIP: 0010:iowrite16+0x1d/0x30
+[   62.492121] RSP: 0018:ffffa477c034fcc8 EFLAGS: 00010292 ORIG_RAX: ffffffffffffff11
+[   62.492121] RAX: ffffffffa24fbdb0 RBX: ffff92a1f8f82000 RCX: 0000000000000001
+[   62.492121] RDX: ffffa477c0371000 RSI: ffffa477c0371000 RDI: 0000000000000000
+[   62.492121] RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000001080020
+[   62.492121] R10: ffffdc7cc1e4fc00 R11: 0000000000000000 R12: 0000000000000000
+[   62.492121] R13: 0000000000000000 R14: ffff92a1f93f0000 R15: ffff92a1f8e1aa80
+[   62.492121]  ? vp_synchronize_vectors+0x60/0x60
+[   62.492121]  vp_notify+0x12/0x20
+[   62.492121]  virtqueue_notify+0x18/0x30
+[   62.492121]  virtio_queue_rq+0x2f5/0x300 [virtio_blk]
+[   62.492121]  blk_mq_dispatch_rq_list+0x7e/0x4a0
+[   62.492121]  blk_mq_do_dispatch_sched+0x4a/0xd0
+[   62.492121]  blk_mq_sched_dispatch_requests+0x106/0x170
+[   62.492121]  __blk_mq_run_hw_queue+0x80/0x90
+[   62.492121]  process_one_work+0x1e3/0x420
+[   62.492121]  worker_thread+0x2b/0x3d0
+[   62.492121]  ? process_one_work+0x420/0x420
+[   62.492121]  kthread+0x113/0x130
+[   62.492121]  ? kthread_create_worker_on_cpu+0x50/0x50
+[   62.492121]  ret_from_fork+0x3a/0x50
+
+Another important thing is that the commit works well on other hardware with the same setup (same host kernel, same qemu command line and host kernel binaries). How could I try to find the issue reason?
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1754372 b/results/classifier/gemma3:12b/kernel/1754372
new file mode 100644
index 00000000..86fd39c3
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1754372
@@ -0,0 +1,10 @@
+
+Set MIPS MSA in ELF Auxiliary Vectors
+
+The MIPS MSA feature is currently not set in the ELF auxiliary vector.
+
+That is, querying the AT_HWCAP key of the ELF auxiliary vectors for a MIPS CPU that has the MSA feature should return a value that has the second bit [0] set.
+
+From [0], `HWCAP_MIPS_MSA` is defined to `1 << 1`.
+
+[0]: https://github.com/torvalds/linux/blob/master/arch/mips/include/uapi/asm/hwcap.h
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1756 b/results/classifier/gemma3:12b/kernel/1756
new file mode 100644
index 00000000..5ed106bb
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1756
@@ -0,0 +1,44 @@
+
+qemu8-user on Linux: SIGSEGV because brk(NULL) does not exist
+Description of problem:
+On Linux, the return value of the system call brk(NULL) need not point to a page that exists.
+If so, then qemu8-user will generate SIGSEGV at the next call to brk() with a higher value,
+because qemu8 believes that it should maintain contiguous .bss with bytes of value 0.
+Thus qemu8-user so calls `memset(g2h_untagged(target_brk), 0, brk_page - target_brk);
+in do_brk() at ../linux-user/syscall.c:867, and this generates SIGSEGV at
+the non-existent page that covers brk(NULL).
+
+Instead, the safest thing to do is nothing at all.
+Linux deliberately returns a random value for brk(NULL), subject to the conditions
+that the value be at least as large as the maximum over all PT_LOAD of (.p_vaddr + .p_memsz),
+and "somewhat near" that maximum.  The purpose of randomness is to use variability
+to interfere with effectiveness of malware, and to expose application coding errors
+regarding brk() and sbrk().  If qemu-user wants to preserve contiguous .bss,
+then qemu-user should call memset() only if the first page of the range exists.
+(As explained in the next paragraph, "contiguous .bss" is a murky concept.)
+
+Linux itself is partly to blame, because it computes the maximum (.p_vaddr + .p_memsz)
+over all the PT_LOAD of the most recent execve().  The most recent execve() seen by
+Linux might have no relationship to the state of the address space at the time of
+_either_ call to brk().  The app can do arbitrary mmap, munmap, mprotect at any time.
+In particular, the run-time de-compressor of UPX does exactly that for a compressed
+main program.  The maximum computed by Linux is for the compressed program,
+which has a different layout than the de-compressed program.
+
+There is a Linux system call prctl(PR_SET_MM_BRK, new_value) which sets a value
+for "the brk", but that syscall tries to validate the new_value based on
+the most recent execve().  Once again, that has no relationship to the current
+layout of the address space produced by the UPX de-compressor.
+Steps to reproduce:
+1. build qemu8-x86_64 from
+```
+commit fcb237e64f9d026c03d635579c7b288d0008a6e5 (HEAD -> master, origin/master, origin/HEAD)
+Merge: 2ff49e96ac c00aac6f14
+Date:   Mon Jul 10 09:17:06 2023 +0100
+```
+2. run `build/qemu-x86_64 -strace upx-4.0.2-amd64_linux/upx --version` where the upx
+is from https://github.com/upx/upx/releases/download/v4.0.2/upx-4.0.2-amd64_linux.tar.xz
+3. output ends with
+```
+372621 close(3) = 0
+372621 munmap(0x0000004000803000,3055) = 0
diff --git a/results/classifier/gemma3:12b/kernel/1756080 b/results/classifier/gemma3:12b/kernel/1756080
new file mode 100644
index 00000000..822a072c
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1756080
@@ -0,0 +1,4 @@
+
+QEMU does not provide non-Linux kernels with ATAGS structure on ARM targets
+
+This would be a useful feature. Many kernels, particularly hobbyist kernels, have support for ATAGS.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1757363 b/results/classifier/gemma3:12b/kernel/1757363
new file mode 100644
index 00000000..3e8b9121
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1757363
@@ -0,0 +1,34 @@
+
+infinite loop due to improper deal with "eret" on mips32
+
+1.qemu 2.9.1 release on the official web build with tcg
+2.cmd: qemu-system-mips -kernel kernelfile
+3. host: ubuntu 16.04.1 with linux kernel 4.6.2 x86_64
+   guest: mips bigendian 32bit (tplink firmware)
+
+
+detail:
+
+static inline void exception_return(CPUMIPSState *env)
+{
+    debug_pre_eret(env);
+    if (env->CP0_Status & (1 << CP0St_ERL)) {
+        set_pc(env, env->CP0_ErrorEPC);
+        env->CP0_Status &= ~(1 << CP0St_ERL);
+    } else {
+        set_pc(env, env->CP0_EPC);
+        env->CP0_Status &= ~(1 << CP0St_EXL);====================> ISSUE????
+    }
+    compute_hflags(env);
+    debug_post_eret(env);
+}
+
+void helper_eret(CPUMIPSState *env)
+{
+    exception_return(env);
+    env->lladdr = 1;
+}
+
+
+In the Issue Line, there is no check CP0_Status whether int is disabled (should not enter int routine),
+that result in the cpu can not jump out the int routine.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1760 b/results/classifier/gemma3:12b/kernel/1760
new file mode 100644
index 00000000..d1e452a2
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1760
@@ -0,0 +1,54 @@
+
+qemu8-i386 gets wrong arguments for 32-bit old mmap syscall (_NR_mmap = 90)
+Description of problem:
+qemu8-i386 does not decode syscall arguments correctly for system call _NR_mmap = 90 on i386.
+```
+$ strace ./oldmmap
+execve("./oldmmap", ["./oldmmap"], 0x7fff46ba6d40 /* 61 vars */) = 0
+[ Process PID=405233 runs in 32 bit mode. ]
+mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xf7fa7000
+exit(5)                                 = ?
++++ exited with 5 +++
+
+$ build/qemu-i386 -strace ./oldmmap
+405254 mmap(0x40800058,0,PROT_NONE,0,0,0) = 0x3fffb000
+405254 exit(5)
+```
+Steps to reproduce:
+1. gcc -m32 -o oldmmap -nostartfiles -nostdlib oldmmap.S  # build 32-bit executable
+2. strace ./oldmmap  # run under strace
+3. build/qemu-i386 -strace ./oldmmap  # run under "qemu-i386 -strace"
+4. Notice that qemu-i386 did not report the same arguments to the _NR_map syscall as /usr/bin/strace did.
+Additional information:
+```
+$ cat oldmmap.S
+MAP_FIXED=     0x10
+MAP_PRIVATE=   0x02
+MAP_ANONYMOUS= 0x20
+
+PROT_READ=      1
+PROT_WRITE=     2
+PROT_EXEC=      4
+
+_NR_exit = 1
+_NR_mmap = 90  // oldmmap: %ebx -> array of 6 arguments
+
+    .globl _start
+_start:
+    push $0  // offset
+    push $-1  // fd
+    push $MAP_PRIVATE|MAP_ANONYMOUS  // flags
+    push $PROT_READ|PROT_WRITE  // protection
+    push $2<<12  // length
+    push $0  // addr (kernel chooses)
+    mov %esp,%ebx
+    mov $_NR_mmap,%eax
+    int $0x80
+    nop
+
+    mov $5,%ebx
+    mov $_NR_exit,%eax
+    int $0x80
+    hlt
+$ 
+```
diff --git a/results/classifier/gemma3:12b/kernel/1761027 b/results/classifier/gemma3:12b/kernel/1761027
new file mode 100644
index 00000000..ef5a2ccf
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1761027
@@ -0,0 +1,14 @@
+
+Unexpected error: "AioContext polling is not implemented on Windows"
+
+When run it this error happens:
+Unexpected error in aio_context_set_poll_params() at /home/stefan/src/qemu/repo.or.cz/qemu/ar7/util/aio-win32.c:413:
+C:\Program Files\qemu\qemu-system-x86_64.exe: AioContext polling is not implemented on Windows
+
+This application has requested the Runtime to terminate it in an unusual way.
+Please contact the application's support team for more information.
+
+
+
+System:
+Windows 10 x64
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1765 b/results/classifier/gemma3:12b/kernel/1765
new file mode 100644
index 00000000..8f885c59
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1765
@@ -0,0 +1,96 @@
+
+Linux kernel fails to boot on powernv machines with nvme device on s390x hosts
+Description of problem:
+When running a powernv guest with nvme device on a s390x host, the guest linux kernel fails to boot with the following panic:
+
+```
+nvme nvme0: pci function 0002:01:00.0
+nvme 0002:01:00.0: enabling device (0100 -> 0102)
+nvme nvme0: 1/0/0 default/read/poll queues
+nvme nvme0: invalid id 0 completed on queue 0
+nvme nvme0: invalid id 0 completed on queue 0
+nvme nvme0: invalid id 0 completed on queue 0
+nvme nvme0: invalid id 0 completed on queue 0
+nvme nvme0: invalid id 0 completed on queue 0
+nvme nvme0: invalid id 0 completed on queue 0
+nvme nvme0: invalid id 0 completed on queue 0
+nvme nvme0: invalid id 0 completed on queue 0
+nvme nvme0: invalid id 0 completed on queue 0
+nvme nvme0: invalid id 0 completed on queue 0
+nvme nvme0: invalid id 0 completed on queue 0
+nvme nvme0: invalid id 0 completed on queue 0
+nvme nvme0: invalid id 0 completed on queue 0
+nvme nvme0: invalid id 0 completed on queue 0
+nvme nvme0: invalid id 0 completed on queue 0
+nvme nvme0: invalid id 0 completed on queue 0
+nvme nvme0: invalid id 0 completed on queue 0
+nvme nvme0: invalid id 0 completed on queue 0
+nvme nvme0: invalid id 0 completed on queue 0
+nvme nvme0: invalid id 0 completed on queue 0
+nvme nvme0: invalid id 0 completed on queue 0
+nvme nvme0: invalid id 0 completed on queue 0
+nvme nvme0: invalid id 0 completed on queue 0
+nvme nvme0: invalid id 0 completed on queue 0
+nvme nvme0: invalid id 0 completed on queue 0
+BUG: Kernel NULL pointer dereference on read at 0x00000008
+Faulting instruction address: 0xc0000000000c02ec
+Oops: Kernel access of bad area, sig: 11 [#1]
+LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV
+Modules linked in: nvme powernv_flash(+) rtc_opal ibmpowernv mtd nvme_core
+CPU: 0 PID: 100 Comm: pb-console Not tainted 5.10.50-openpower1 #2
+NIP:  c0000000000c02ec LR: c00000000050d5dc CTR: c00000000024a2d0
+REGS: c00000003ffdfa00 TRAP: 0300   Not tainted  (5.10.50-openpower1)
+MSR:  9000000000009033 <SF,HV,EE,ME,IR,DR,RI,LE>  CR: 24000402  XER: 20000000
+CFAR: c00000000000f3c0 DAR: 0000000000000008 DSISR: 40000000 IRQMASK: 1 
+GPR00: c0000000000ba058 c00000003ffdfc90 c00000000180db00 0000000000000008 
+GPR04: 000000000000000a 0000000000000000 c000000002740210 c00000000274e218 
+GPR08: c00000000183be00 0000000080000000 0000000000000000 c0080000003ba798 
+GPR12: c00000000024a2d0 c000000001a30000 0000000000000000 0000000000000100 
+GPR16: 0000000000000004 0000000000000020 0000000000000100 c00000000bbe8080 
+GPR20: 0000000000000028 c000000001830100 0000000000000001 0000000000000000 
+GPR24: c000000001831a00 c000000001410c00 00000000ffff9097 0000000000400040 
+GPR28: 000000000000000a 000000000000000a 0000000000000008 0000000000000000 
+NIP [c0000000000c02ec] __arch_spin_trylock+0x4/0x24
+LR [c00000000050d5dc] _raw_spin_lock_irqsave+0x2c/0x78
+Call Trace:
+[c00000003ffdfc90] [c00000003ffdfcc0] 0xc00000003ffdfcc0 (unreliable)
+[c00000003ffdfcd0] [c0000000000ba058] complete+0x24/0x64
+[c00000003ffdfd10] [c00000000024a2f8] blk_end_sync_rq+0x28/0x3c
+[c00000003ffdfd30] [c00000000024f44c] __blk_mq_end_request+0x134/0x160
+[c00000003ffdfd70] [c0080000003b481c] nvme_complete_rq+0xcc/0x13c [nvme_core]
+[c00000003ffdfda0] [c0080000000a1078] nvme_pci_complete_rq+0x78/0x108 [nvme]
+[c00000003ffdfdd0] [c00000000024de38] blk_done_softirq+0xc0/0xd0
+[c00000003ffdfe30] [c00000000050da20] __do_softirq+0x238/0x28c
+[c00000003ffdff20] [c0000000000875d4] __irq_exit_rcu+0x80/0xc8
+[c00000003ffdff50] [c000000000087844] irq_exit+0x18/0x30
+[c00000003ffdff70] [c000000000011c4c] __do_irq+0x80/0xa0
+[c00000003ffdff90] [c00000000001d7a4] call_do_irq+0x14/0x24
+[c00000000bff3960] [c000000000011d20] do_IRQ+0xb4/0xbc
+[c00000000bff39f0] [c000000000008fac] hardware_interrupt_common_virt+0x1ac/0x1b0
+--- interrupt: 500 at arch_local_irq_restore+0xac/0xe8
+    LR = __raw_spin_unlock_irq+0x34/0x40
+[c00000000bff3cf0] [0000000000000000] 0x0 (unreliable)
+[c00000000bff3d20] [c0000000000a8344] __raw_spin_unlock_irq+0x34/0x40
+[c00000000bff3d50] [c0000000000a84b0] finish_task_switch+0x160/0x228
+[c00000000bff3df0] [c0000000000aa3d0] schedule_tail+0x20/0x8c
+[c00000000bff3e20] [c00000000000cb50] ret_from_fork+0x4/0x54
+Instruction dump:
+a14d0b7a 7da96b78 2f8a0000 419e0010 39400000 b14d0b7a 7c0004ac a1490b78 
+394affff b1490b78 4e800020 812d0000 <7d401829> 2c0a0000 40c20010 7d20192d 
+---[ end trace 6b7a11c45e4fc465 ]---
+
+Kernel panic - not syncing: Fatal exception
+Rebooting in 30 seconds..
+```
+
+The issue has been noticed while running the avocado tests on a s390x host:
+
+```
+make check-venv
+./tests/venv/bin/avocado run tests/avocado/boot_linux_console.py:BootLinuxConsole.test_ppc_powernv8
+```
+
+But they can also be reproduced manually:
+Steps to reproduce:
+1. wget https://github.com/open-power/op-build/releases/download/v2.7/zImage.epapr
+2. ./qemu-system-ppc64 -nographic -M powernv8 -kernel zImage.epapr -append "console=tty0 console=hvc0" -device pcie-pci-bridge,id=bridge1,bus=pcie.1,addr=0x0 -device nvme,bus=pcie.2,addr=0x0,serial=1234
diff --git a/results/classifier/gemma3:12b/kernel/1767146 b/results/classifier/gemma3:12b/kernel/1767146
new file mode 100644
index 00000000..fa13485f
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1767146
@@ -0,0 +1,36 @@
+
+No ACPI-table found, option -M 1.6 not found either
+
+Currently writing a small kernel, when trying to detect memory blocks that contain ACPI information, no such block is found. When ran in Oracle Virtualbox, code runs flawlessly.
+
+Code that is detecting the ACPI-Info (with a bit of debug-output):
+
+```
+multiboot_memory_map32_t* map = (multiboot_memory_map32_t*)mmap;
+for (uint32_t i = 0; i < size; i++) {
+	Termutils::cout << map[i].type << "type of block  ";
+        if (mmap[i].type == MULTIBOOT_MEMORY_ACPI_RECLAIMABLE) {
+		Termutils::cout << "WE ARE INSIDE\n";
+		fadt = (FADT*)(map[i].base_addr_low);
+		//break;
+	}
+	if (i % 9 == 0) {
+		Termutils::cout << "\n";
+	}
+}
+```
+
+
+command qemu is run with:
+
+qemu-img create build/objects/test 500M
+qemu-system-i386 -hda $(APP_DIR)/clinl.iso -hdb ./build/objects/test
+
+
+The iso-image is (zipped) included as attachment.
+
+
+qemu-system-i386 --version:
+
+QEMU emulator version 2.10.1(qemu-2.10.1-3.fc27)
+Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1767200 b/results/classifier/gemma3:12b/kernel/1767200
new file mode 100644
index 00000000..04a7e8e2
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1767200
@@ -0,0 +1,10 @@
+
+Kernel Panic Unable to mount root fs on unknown-block(31,3)
+
+Using the latest qemu:
+qemu-system-arm.exe -kernel C:\Users\a\Downloads\kernel-qemu-4.4.34-jessie -cpu arm1176 -m 256 -machine versatilepb -cdrom C:\Users\a\Downloads\picore-9.0.3.img
+
+Gives error:
+Kernel Panic Unable to mount root fs on unknown-block(31,3)
+
+I have tried different ARMv6 ARMv7 images/kernels with the same result.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1768 b/results/classifier/gemma3:12b/kernel/1768
new file mode 100644
index 00000000..3eac013e
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1768
@@ -0,0 +1,33 @@
+
+Could not allocate more than ~2GB with qemu-user
+Description of problem:
+On qemu-user, failed to allocate more than about 2GB on 32bit platform supporting up to 4GB (arm, ppc, etc.)
+Steps to reproduce:
+1. Try to allocate more than 2GB [e.g. for(i=0;i<64;i++) if(malloc(64*1024*1024)==NULL) perror("Failed to allocate 64MB");]
+2. Only 1 64MB chunck is allocated in the upper 2GB memory space
+3. Failed to allocate after about 2GB.
+Additional information:
+The problem is in **pageflags_find** and **pageflags_next** functions (found in _accel/tcg/user-exec.c_) 3rd parameters, that should be **target_ulong** instead of incorrect _target_long_ (the parameter will be converted signed extended to uint64_t).
+The testing program is the following:
+```
+#include <stdio.h>
+#include <stdlib.h>
+
+int main(int argc,char *argv[]) {
+  unsigned int a;
+  unsigned int i;
+  char *al;
+  unsigned int sss=1U*1024*1024*64;
+  for(a=0;a<128;a++) {
+    al=malloc(sss);
+    if(al!=NULL) {
+      printf("ALLOC OK %u (%08lX)!\n",sss*(a+1),al);
+    }
+    else {
+      printf("Cannot alloc %d\n",(a+1)*sss);
+      perror("Cannot alloc");
+      exit(1);
+    }
+  }
+}
+```
diff --git a/results/classifier/gemma3:12b/kernel/1770 b/results/classifier/gemma3:12b/kernel/1770
new file mode 100644
index 00000000..893c0780
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1770
@@ -0,0 +1,23 @@
+
+Wrong unpacked structure for epoll_event on qemu-or1k (openrisc)
+Description of problem:
+When using cmake automoc, the process will infinite loop waiting for epoll_events.
+Steps to reproduce:
+1. Try to compile cmake with qt5 support
+2. The build process will freeze when "Automatic MOC" is invoked
+Additional information:
+The problem is that or1k has a "packed" epoll_event structure, so it should be also packed in target_epoll_event structure.
+Following the (very trivial) patch:
+```
+--- qemu-20230327/linux-user/syscall_defs.h.orig	2023-03-27 15:41:42.000000000 +0200
++++ qemu-20230327/linux-user/syscall_defs.h	2023-06-30 17:29:39.034322213 +0200
+@@ -2714,7 +2709,7 @@ 
+ #define FUTEX_CMD_MASK          ~(FUTEX_PRIVATE_FLAG | FUTEX_CLOCK_REALTIME)
+ 
+ #ifdef CONFIG_EPOLL
+-#if defined(TARGET_X86_64)
++#if defined(TARGET_X86_64) || defined(TARGET_OPENRISC)
+ #define TARGET_EPOLL_PACKED QEMU_PACKED
+ #else
+ #define TARGET_EPOLL_PACKED
+```
diff --git a/results/classifier/gemma3:12b/kernel/1772166 b/results/classifier/gemma3:12b/kernel/1772166
new file mode 100644
index 00000000..5b9a800c
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1772166
@@ -0,0 +1,13 @@
+
+qemu 2.4.1: dereferencing pointer to incomplete type ‘struct ucontext’
+
+Trying to compile qemu release 2.4.1
+
+Getting compile error 
+
+user-exec.c: In function ‘cpu_resume_from_signal’:
+user-exec.c:72:37: error: dereferencing pointer to incomplete type ‘struct ucontext’
+         sigprocmask(SIG_SETMASK, &uc->uc_sigmask, NULL);
+                                     ^~
+user-exec.c: In function ‘cpu_arm_signal_handler’:
+user-exec.c:214:41: error: dereferencing pointer to incomplete type ‘struct ucontext’
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1774 b/results/classifier/gemma3:12b/kernel/1774
new file mode 100644
index 00000000..7d72a453
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1774
@@ -0,0 +1,24 @@
+
+8.1-rc0 failure to build with capstone 5.0
+Description of problem:
+Use >=capstone-5.0 dependency, try to build qemu, get this error:
+```
+/opt/homebrew/Cellar/capstone/5.0/include/capstone/tricore.h:561:3: error:
+redefinition of 'tricore_feature' as different kind of symbol
+} tricore_feature;
+  ^
+../target/tricore/cpu.h:261:19: note: previous definition is here
+static inline int tricore_feature(CPUTriCoreState *env, int feature)
+                  ^
+1 error generated.
+```
+
+The fix is trivial and it was already mentioned in the mailing list but wasn't fixed for rc0, so I figured it might have been forgotten about.
+
+https://lore.kernel.org/qemu-devel/CA+PgxXVxVKpT0SZ3N+Fc1YvXCiwkkbqm0FmLKqLTbgcDpYCNgg@mail.gmail.com/
+
+If you meet any other problem with capstone (e.g. some regression), please don't hesitate to report it mainstream.
+
+There are plans to make a new patch release soon with fixes for some most annoying bugs since the 5.0 release: https://github.com/capstone-engine/capstone/issues/2081
+
+https://github.com/capstone-engine/capstone/releases
diff --git a/results/classifier/gemma3:12b/kernel/1775555 b/results/classifier/gemma3:12b/kernel/1775555
new file mode 100644
index 00000000..30e187c3
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1775555
@@ -0,0 +1,371 @@
+
+guest migration 100% cpu freeze bug
+
+# Investigate migration cpu hog(100%) bug
+
+I have some issues when migrating from qemu 2.6.2 to qemu 2.11.1.
+The hypervisors are running kernel 4.9.92 on debian stretch with libvirt v4.0.0.
+Linux, libvirt and qemu are all custom compiled.
+
+I migrated around 21.000 vms from qemu 2.6.2 to qemu 2.11.1 and every once in a while a vm is stuck at 100% cpu after the migration from 2.6.2 to 2.11.1. This happend with about 50-60 vms so far.
+
+I attached gdb to a vcpu thread of one stuck vm, and a bt showed the following info:
+#0  0x00007f4f19949dd7 in ioctl () at ../sysdeps/unix/syscall-template.S:84
+#1  0x0000557c9edede47 in kvm_vcpu_ioctl (cpu=cpu@entry=0x557ca1058840, type=type@entry=0xae80) at /home/dbosschieter/src/qemu-pkg/src/accel/kvm/kvm-all.c:2050
+#2  0x0000557c9ededfb6 in kvm_cpu_exec (cpu=cpu@entry=0x557ca1058840) at /home/dbosschieter/src/qemu-pkg/src/accel/kvm/kvm-all.c:1887
+#3  0x0000557c9edcab44 in qemu_kvm_cpu_thread_fn (arg=0x557ca1058840) at /home/dbosschieter/src/qemu-pkg/src/cpus.c:1128
+#4  0x00007f4f19c0f494 in start_thread (arg=0x7f4f053f3700) at pthread_create.c:333
+#5  0x00007f4f19951acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97
+
+The ioctl call is a ioctl(18, KVM_RUN and it looks like it is looping inside the vm itself.
+
+I saved the state of the VM (with `virsh save`) after I found it was hanging on its vcpu threads. Then I restored this vm on a test environment running the same kernel, QEMU and libvirt version). After the restore the VM still was haning at 100% cpu usage on all the vcpus.
+I tried to use the perf kvm guest option to trace the guest vm with a copy of the kernel, modules and kallsyms files from inside the guest vm and I got the following trace:
+
+$ perf kvm --guest --guestkallsyms=kallsyms --guestmodules=modules record -g -p 14471 -o perf.data
+$ perf kvm --guest --guestkallsyms=kallsyms --guestmodules=modules report -i perf.data --stdio > analyze
+
+# To display the perf.data header info, please use --header/--header-only options.
+#
+#
+# Total Lost Samples: 0
+#
+# Samples: 105K of event 'cycles'
+# Event count (approx.): 67588147605
+#
+# Children      Self  Command  Shared Object            Symbol                                      Parent symbol
+# ........  ........  .......  .......................  ..........................................  .............
+#
+    28.79%    28.79%  :16028   [guest.kernel.kallsyms]  [g] fuse_get_root_inode                     [other]
+    23.48%    23.48%  :16030   [guest.kernel.kallsyms]  [g] ftrace_raw_output_hrtimer_init          [other]
+     7.32%     7.32%  :16029   [guest.kernel.kallsyms]  [g] do_sysfs_unregistration                 [other]
+     4.82%     4.82%  :16029   [guest.kernel.kallsyms]  [g] posix_cpu_clock_get                     [other]
+     4.20%     4.20%  :16030   [guest.kernel.kallsyms]  [g] ftrace_raw_output_timer_expire_entry    [other]
+     3.87%     3.87%  :16029   [guest.kernel.kallsyms]  [g] kvm_init_debugfs                        [other]
+     3.66%     3.66%  :16029   [guest.kernel.kallsyms]  [g] fat_msg                                 [other]
+     3.11%     3.11%  :16029   [guest.kernel.kallsyms]  [g] match_token                             [other]
+     3.07%     3.07%  :16029   [guest.kernel.kallsyms]  [g] load_balance                            [other]
+     1.87%     1.87%  :16029   [guest.kernel.kallsyms]  [g] kvm_pv_guest_cpu_reboot                 [other]
+     1.69%     1.69%  :16031   [guest.kernel.kallsyms]  [g] kvm_init_debugfs                        [other]
+     1.59%     1.59%  :16029   [guest.kernel.kallsyms]  [g] sys_kcmp                                [other]
+     1.19%     1.19%  :16031   [guest.kernel.kallsyms]  [g] save_paranoid                           [other]
+     0.82%     0.82%  :16031   [guest.kernel.kallsyms]  [g] kvm_pv_guest_cpu_reboot                 [other]
+     0.69%     0.69%  :16031   [guest.kernel.kallsyms]  [g] kvm_cpu_notify                          [other]
+     0.54%     0.54%  :16031   [guest.kernel.kallsyms]  [g] rcu_process_callbacks                   [other]
+     0.46%     0.46%  :16030   [guest.kernel.kallsyms]  [g] ftrace_raw_output_hrtimer_start         [other]
+     0.43%     0.43%  :16031   [guest.kernel.kallsyms]  [g] tg_set_cfs_bandwidth                    [other]
+     0.42%     0.42%  :16030   [guest.kernel.kallsyms]  [g] ftrace_raw_output_hrtimer_expire_entry  [other]
+     0.37%     0.37%  :16029   [guest.kernel.kallsyms]  [g] amd_get_mmconfig_range                  [other]
+     0.35%     0.35%  :16031   [guest.kernel.kallsyms]  [g] sys_kcmp                                [other]
+     0.35%     0.35%  :16031   [guest.kernel.kallsyms]  [g] console_unlock                          [other]
+     0.34%     0.34%  :16029   [guest.kernel.kallsyms]  [g] __fat_fs_error                          [other]
+     0.31%     0.31%  :16031   [guest.kernel.kallsyms]  [g] do_sysfs_unregistration                 [other]
+     0.24%     0.24%  :16031   [guest.kernel.kallsyms]  [g] paravirt_write_msr                      [other]
+     0.24%     0.24%  :16029   [guest.kernel.kallsyms]  [g] parse_no_kvmclock                       [other]
+     0.24%     0.24%  :16029   [guest.kernel.kallsyms]  [g] kvm_save_sched_clock_state              [other]
+     0.21%     0.21%  :16030   [guest.kernel.kallsyms]  [g] ptrace_request                          [other]
+     0.20%     0.20%  :16031   [guest.kernel.kallsyms]  [g] print_stack_trace                       [other]
+     0.20%     0.20%  :16031   [guest.kernel.kallsyms]  [g] build_sched_domains                     [other]
+     0.20%     0.20%  :16031   [guest.kernel.kallsyms]  [g] __synchronize_srcu                      [other]
+     0.17%     0.17%  :16031   [guest.kernel.kallsyms]  [g] do_cpu_nanosleep                        [other]
+     0.16%     0.16%  :16031   [guest.kernel.kallsyms]  [g] amd_get_mmconfig_range                  [other]
+     0.16%     0.16%  :16031   [guest.kernel.kallsyms]  [g] irq_node_proc_show                      [other]
+     0.15%     0.15%  :16031   [guest.kernel.kallsyms]  [g] __srcu_read_lock                        [other]
+     0.15%     0.15%  :16031   [guest.kernel.kallsyms]  [g] posix_cpu_nsleep_restart                [other]
+     0.11%     0.11%  :16031   [guest.kernel.kallsyms]  [g] parse_no_kvmclock                       [other]
+     0.11%     0.11%  :16031   [guest.kernel.kallsyms]  [g] __irq_domain_add                        [other]
+     0.11%     0.11%  :16031   [guest.kernel.kallsyms]  [g] print_tickdevice.isra.4                 [other]
+     0.10%     0.10%  :16031   [guest.kernel.kallsyms]  [g] kvm_save_sched_clock_state              [other]
+     0.09%     0.09%  :16031   [guest.kernel.kallsyms]  [g] sysfs_unbind_tick_dev                   [other]
+     0.09%     0.09%  :16029   [guest.kernel.kallsyms]  [g] __sched_setscheduler                    [other]
+     0.09%     0.09%  :16031   [guest.kernel.kallsyms]  [g] process_srcu                            [other]
+     0.08%     0.08%  :16031   [guest.kernel.kallsyms]  [g] avc_compute_av                          [other]
+     0.08%     0.08%  :16031   [guest.kernel.kallsyms]  [g] arch_remove_reservations                [other]
+     0.08%     0.08%  :16031   [guest.kernel.kallsyms]  [g] __switch_to_xtra                        [other]
+     0.08%     0.08%  :16031   [guest.kernel.kallsyms]  [g] __create_irqs                           [other]
+     0.08%     0.08%  :16031   [guest.kernel.kallsyms]  [g] ftrace_raw_output_irq_handler_exit      [other]
+     0.07%     0.07%  :16031   [guest.kernel.kallsyms]  [g] posix_clock_read                        [other]
+     0.07%     0.07%  :16031   [guest.kernel.kallsyms]  [g] posix_clock_poll                        [other]
+     0.07%     0.07%  :16031   [guest.kernel.kallsyms]  [g] native_cpu_up                           [other]
+     0.06%     0.06%  :16031   [guest.kernel.kallsyms]  [g] do_nmi                                  [other]
+     0.06%     0.06%  :16031   [guest.kernel.kallsyms]  [g] rcu_try_advance_all_cbs                 [other]
+     0.06%     0.06%  :16031   [guest.kernel.kallsyms]  [g] fat_msg                                 [other]
+     0.05%     0.05%  :16031   [guest.kernel.kallsyms]  [g] check_tsc_warp                          [other]
+     0.04%     0.04%  :16031   [guest.kernel.kallsyms]  [g] tick_handle_oneshot_broadcast           [other]
+     0.03%     0.03%  :16031   [guest.kernel.kallsyms]  [g] set_cpu_itimer                          [other]
+     0.02%     0.02%  :16031   [guest.kernel.kallsyms]  [g] arp_ignore                              [other]
+     0.02%     0.02%  :16031   [guest.kernel.kallsyms]  [g] store_powersave_bias_gov_sys            [other]
+     0.02%     0.02%  :16031   [guest.kernel.kallsyms]  [g] cleanup_srcu_struct                     [other]
+     0.02%     0.02%  :16031   [guest.kernel.kallsyms]  [g] create_prof_cpu_mask                    [other]
+     0.02%     0.02%  :16031   [guest.kernel.kallsyms]  [g] alarm_timer_nsleep                      [other]
+     0.02%     0.02%  :16031   [guest.kernel.kallsyms]  [g] time_cpufreq_notifier                   [other]
+     0.02%     0.02%  :16030   [guest.kernel.kallsyms]  [g] ftrace_raw_output_itimer_state          [other]
+     0.02%     0.02%  :16031   [guest.kernel.kallsyms]  [g] tick_check_new_device                   [other]
+     0.02%     0.02%  :16031   [guest.kernel.kallsyms]  [g] init_timer_key                          [other]
+     0.02%     0.02%  :16031   [guest.kernel.kallsyms]  [g] tick_setup_device                       [other]
+     0.02%     0.02%  :16031   [guest.kernel.kallsyms]  [g] clockevents_register_device             [other]
+     0.02%     0.02%  :16031   [guest.kernel.kallsyms]  [g] __srcu_read_unlock                      [other]
+     0.02%     0.02%  :16031   [guest.kernel.kallsyms]  [g] hpet_rtc_interrupt                      [other]
+     0.02%     0.02%  :16031   [guest.kernel.kallsyms]  [g] init_srcu_struct                        [other]
+     0.02%     0.02%  :16031   [guest.kernel.kallsyms]  [g] irq_spurious_proc_show                  [other]
+     0.02%     0.02%  :16031   [guest.kernel.kallsyms]  [g] rcu_jiffies_till_stall_check            [other]
+     0.02%     0.02%  :16031   [guest.kernel.kallsyms]  [g] ksoftirqd_should_run                    [other]
+     0.01%     0.01%  :16031   [guest.kernel.kallsyms]  [g] ftrace_raw_output_irq_handler_entry     [other]
+     0.01%     0.01%  :16031   [guest.kernel.kallsyms]  [g] avc_denied.isra.0                       [other]
+     0.01%     0.01%  :16031   [guest.kernel.kallsyms]  [g] __fat_fs_error                          [other]
+     0.01%     0.01%  :16031   [guest.kernel.kallsyms]  [g] wakeme_after_rcu                        [other]
+     0.01%     0.01%  :16031   [guest.kernel.kallsyms]  [g] prof_cpu_mask_proc_write                [other]
+     0.01%     0.01%  :16031   [guest.kernel.kallsyms]  [g] srcu_barrier                            [other]
+     0.01%     0.01%  :16031   [guest.kernel.kallsyms]  [g] tick_get_device                         [other]
+     0.01%     0.01%  :16031   [guest.kernel.kallsyms]  [g] irq_domain_add_simple                   [other]
+     0.01%     0.01%  :16031   [guest.kernel.kallsyms]  [g] synchronize_srcu_expedited              [other]
+     0.01%     0.01%  :16031   [guest.kernel.kallsyms]  [g] sysfs_show_current_tick_dev             [other]
+     0.01%     0.01%  :16031   [guest.kernel.kallsyms]  [g] tick_is_oneshot_available               [other]
+     0.01%     0.01%  :16031   [guest.kernel.kallsyms]  [g] tick_check_replacement                  [other]
+     0.01%     0.01%  :16031   [guest.kernel.kallsyms]  [g] clockevents_notify                      [other]
+     0.01%     0.01%  :16031   [guest.kernel.kallsyms]  [g] show_stack                              [other]
+     0.01%     0.01%  :16031   [guest.kernel.kallsyms]  [g] debug_kfree                             [other]
+     0.01%     0.01%  :16031   [guest.kernel.kallsyms]  [g] tick_do_broadcast.constprop.6           [other]
+     0.01%     0.01%  :16031   [guest.kernel.kallsyms]  [g] sock_rps_save_rxhash.isra.28.part.29    [other]
+     0.00%     0.00%  :16031   [guest.kernel.kallsyms]  [g] store_ignore_nice_load.isra.3           [other]
+     0.00%     0.00%  :16031   [guest.kernel.kallsyms]  [g] perf_trace_itimer_expire                [other]
+     0.00%     0.00%  :16031   [guest.kernel.kallsyms]  [g] hrtick_start                            [other]
+     0.00%     0.00%  :16031   [guest.kernel.kallsyms]  [g] parse_probe_arg                         [other]
+     0.00%     0.00%  :16031   [guest.kernel.kallsyms]  [g] wakeup_softirqd                         [other]
+     0.00%     0.00%  :16031   [guest.kernel.kallsyms]  [g] tick_install_replacement                [other]
+     0.00%     0.00%  :16031   [guest.kernel.kallsyms]  [g] detach_if_pending                       [other]
+     0.00%     0.00%  :16031   [guest.kernel.kallsyms]  [g] default_affinity_show                   [other]
+     0.00%     0.00%  :16031   [guest.kernel.kallsyms]  [g] tick_do_periodic_broadcast              [other]
+     0.00%     0.00%  :16031   [guest.kernel.kallsyms]  [g] ftrace_raw_output_softirq               [other]
+     0.00%     0.00%  :16031   [guest.kernel.kallsyms]  [g] tasklet_kill                            [other]
+     0.00%     0.00%  :16031   [guest.kernel.kallsyms]  [g] update_rq_clock                         [other]
+     0.00%     0.00%  :16031   [guest.kernel.kallsyms]  [g] tasklet_init                            [other]
+     0.00%     0.00%  :16031   [guest.kernel.kallsyms]  [g] arch_local_irq_enable                   [other]
+     0.00%     0.00%  :16031   [guest.kernel.kallsyms]  [g] irq_affinity_proc_show                  [other]
+     0.00%     0.00%  :16031   [guest.kernel.kallsyms]  [g] store_sampling_down_factor.isra.4       [other]
+     0.00%     0.00%  :16031   [guest.kernel.kallsyms]  [g] amd_get_subcaches                       [other]
+
+Also tried a `virsh restore` with the `--bypass-cache` option and ran a perf trace. Noticable is the different trace. See output below:
+
+# perf trace without filesystem cache:
+# To display the perf.data header info, please use --header/--header-only options.
+#
+#
+# Total Lost Samples: 0
+#
+# Samples: 1M of event 'cycles'
+# Event count (approx.): 798928823821
+#
+# Children      Self  Command  Shared Object            Symbol
+# ........  ........  .......  .......................  ..........................................
+#
+    25.32%    25.32%  :34335   [guest.kernel.kallsyms]  [g] ftrace_raw_output_hrtimer_init
+     9.55%     9.55%  :34334   [guest.kernel.kallsyms]  [g] do_sysfs_unregistration
+     5.83%     5.83%  :34335   [guest.kernel.kallsyms]  [g] ftrace_raw_output_timer_expire_entry
+     5.60%     5.60%  :34334   [guest.kernel.kallsyms]  [g] posix_cpu_clock_get
+     4.37%     4.37%  :34334   [guest.kernel.kallsyms]  [g] kvm_init_debugfs
+     4.30%     4.30%  :34334   [guest.kernel.kallsyms]  [g] fat_msg
+     3.63%     3.63%  :34334   [guest.kernel.kallsyms]  [g] match_token
+     3.44%     3.44%  :34334   [guest.kernel.kallsyms]  [g] load_balance
+     3.28%     3.28%  :34333   [guest.kernel.kallsyms]  [g] save_paranoid
+     2.25%     2.25%  :34334   [guest.kernel.kallsyms]  [g] kvm_pv_guest_cpu_reboot
+     2.19%     2.19%  :34335   [guest.kernel.kallsyms]  [g] ftrace_raw_output_hrtimer_expire_entry
+     1.89%     1.89%  :34334   [guest.kernel.kallsyms]  [g] sys_kcmp
+     1.73%     1.73%  :34336   [guest.kernel.kallsyms]  [g] kvm_init_debugfs
+     1.58%     1.58%  :34335   [guest.kernel.kallsyms]  [g] ftrace_raw_output_hrtimer_start
+     1.26%     1.26%  :34336   [guest.kernel.kallsyms]  [g] save_paranoid
+     1.09%     1.09%  :34333   [guest.kernel.kallsyms]  [g] kvm_init_debugfs
+     1.01%     1.01%  :34333   [unknown]                [u] 0x0000000000434c1b
+     0.94%     0.94%  :34336   [guest.kernel.kallsyms]  [g] tg_set_cfs_bandwidth
+     0.88%     0.88%  :34333   [guest.kernel.kallsyms]  [g] avc_denied.isra.0
+     0.87%     0.87%  :34336   [guest.kernel.kallsyms]  [g] kvm_pv_guest_cpu_reboot
+     0.73%     0.73%  :34333   [guest.kernel.kallsyms]  [g] kvm_pv_guest_cpu_reboot
+     0.68%     0.68%  :34336   [guest.kernel.kallsyms]  [g] kvm_cpu_notify
+     0.65%     0.65%  :34336   [guest.kernel.kallsyms]  [g] rcu_process_callbacks
+     0.57%     0.57%  :34333   [guest.kernel.kallsyms]  [g] paravirt_write_msr
+     0.56%     0.56%  :34333   [guest.kernel.kallsyms]  [g] avc_compute_av
+     0.40%     0.40%  :34334   [guest.kernel.kallsyms]  [g] __fat_fs_error
+     0.39%     0.39%  :34334   [guest.kernel.kallsyms]  [g] amd_get_mmconfig_range
+     0.39%     0.39%  :34335   [guest.kernel.kallsyms]  [g] ptrace_request
+     0.38%     0.38%  :34336   [guest.kernel.kallsyms]  [g] sys_kcmp
+     0.34%     0.34%  :34333   [guest.kernel.kallsyms]  [g] posix_cpu_nsleep_restart
+     0.32%     0.32%  :34336   [guest.kernel.kallsyms]  [g] do_sysfs_unregistration
+     0.31%     0.31%  :34336   [guest.kernel.kallsyms]  [g] console_unlock
+     0.30%     0.30%  :34334   [guest.kernel.kallsyms]  [g] kvm_save_sched_clock_state
+     0.29%     0.29%  :34334   [guest.kernel.kallsyms]  [g] parse_no_kvmclock
+     0.27%     0.27%  :34333   [guest.kernel.kallsyms]  [g] do_sysfs_unregistration
+     0.27%     0.27%  :34333   [guest.kernel.kallsyms]  [g] check_tsc_warp
+     0.26%     0.26%  :34333   [guest.kernel.kallsyms]  [g] ksoftirqd_should_run
+     0.26%     0.26%  :34336   [guest.kernel.kallsyms]  [g] paravirt_write_msr
+     0.26%     0.26%  :34333   [guest.kernel.kallsyms]  [g] amd_get_mmconfig_range
+     0.25%     0.25%  :34333   [guest.kernel.kallsyms]  [g] sys_kcmp
+     0.22%     0.22%  :34336   [guest.kernel.kallsyms]  [g] build_sched_domains
+     0.22%     0.22%  :34333   [guest.kernel.kallsyms]  [g] do_cpu_nanosleep
+     0.22%     0.22%  :34333   [guest.kernel.kallsyms]  [g] print_stack_trace
+     0.21%     0.21%  :34336   [guest.kernel.kallsyms]  [g] irq_node_proc_show
+     0.19%     0.19%  :34336   [guest.kernel.kallsyms]  [g] print_stack_trace
+     0.19%     0.19%  :34336   [guest.kernel.kallsyms]  [g] __srcu_read_lock
+     0.18%     0.18%  :34336   [guest.kernel.kallsyms]  [g] __synchronize_srcu
+     0.17%     0.17%  :34333   [guest.kernel.kallsyms]  [g] __create_irqs
+     0.17%     0.17%  :34336   [guest.kernel.kallsyms]  [g] do_cpu_nanosleep
+     0.17%     0.17%  :34336   [guest.kernel.kallsyms]  [g] amd_get_mmconfig_range
+     0.15%     0.15%  :34336   [guest.kernel.kallsyms]  [g] posix_cpu_nsleep_restart
+     0.14%     0.14%  :34333   [guest.kernel.kallsyms]  [g] rcu_process_callbacks
+     0.14%     0.14%  :34333   [guest.kernel.kallsyms]  [g] rcu_try_advance_all_cbs
+     0.13%     0.13%  :34336   [guest.kernel.kallsyms]  [g] parse_no_kvmclock
+     0.11%     0.11%  :34333   [guest.kernel.kallsyms]  [g] tasklet_init
+     0.11%     0.11%  :34336   [guest.kernel.kallsyms]  [g] process_srcu
+     0.11%     0.11%  :34336   [guest.kernel.kallsyms]  [g] kvm_save_sched_clock_state
+     0.11%     0.11%  :34333   [guest.kernel.kallsyms]  [g] sysfs_unbind_tick_dev
+     0.10%     0.10%  :34336   [guest.kernel.kallsyms]  [g] __switch_to_xtra
+     0.10%     0.10%  :34334   [guest.kernel.kallsyms]  [g] __sched_setscheduler
+     0.10%     0.10%  :34333   [guest.kernel.kallsyms]  [g] print_tickdevice.isra.4
+     0.10%     0.10%  :34336   [guest.kernel.kallsyms]  [g] sysfs_unbind_tick_dev
+     0.10%     0.10%  :34336   [guest.kernel.kallsyms]  [g] print_tickdevice.isra.4
+     0.10%     0.10%  :34336   [guest.kernel.kallsyms]  [g] posix_clock_read
+     0.09%     0.09%  :34333   [guest.kernel.kallsyms]  [g] parse_no_kvmclock
+     0.09%     0.09%  :34333   [guest.kernel.kallsyms]  [g] posix_clock_poll
+     0.09%     0.09%  :34336   [guest.kernel.kallsyms]  [g] __irq_domain_add
+     0.09%     0.09%  :34336   [guest.kernel.kallsyms]  [g] avc_compute_av
+     0.09%     0.09%  :34333   [guest.kernel.kallsyms]  [g] posix_clock_read
+     0.09%     0.09%  :34333   [guest.kernel.kallsyms]  [g] hpet_rtc_interrupt
+     0.09%     0.09%  :34336   [guest.kernel.kallsyms]  [g] __create_irqs
+     0.08%     0.08%  :34336   [guest.kernel.kallsyms]  [g] posix_clock_poll
+     0.08%     0.08%  :34336   [guest.kernel.kallsyms]  [g] rcu_try_advance_all_cbs
+     0.07%     0.07%  :34336   [guest.kernel.kallsyms]  [g] ftrace_raw_output_irq_handler_exit
+     0.07%     0.07%  :34336   [guest.kernel.kallsyms]  [g] arch_remove_reservations
+     0.07%     0.07%  :34333   [guest.kernel.kallsyms]  [g] native_cpu_up
+     0.07%     0.07%  :34336   [guest.kernel.kallsyms]  [g] native_cpu_up
+     0.07%     0.07%  :34336   [guest.kernel.kallsyms]  [g] check_tsc_warp
+     0.07%     0.07%  :34333   [guest.kernel.kallsyms]  [g] kvm_save_sched_clock_state
+     0.07%     0.07%  :34333   [guest.kernel.kallsyms]  [g] do_nmi
+     0.06%     0.06%  :34336   [guest.kernel.kallsyms]  [g] do_nmi
+     0.06%     0.06%  :34335   [guest.kernel.kallsyms]  [g] ftrace_raw_output_itimer_state
+     0.05%     0.05%  :34336   [guest.kernel.kallsyms]  [g] fat_msg
+     0.04%     0.04%  :34336   [guest.kernel.kallsyms]  [g] store_powersave_bias_gov_sys
+     0.04%     0.04%  :34336   [guest.kernel.kallsyms]  [g] tick_handle_oneshot_broadcast
+     0.04%     0.04%  :34336   [guest.kernel.kallsyms]  [g] set_cpu_itimer
+     0.04%     0.04%  :34336   [guest.kernel.kallsyms]  [g] cleanup_srcu_struct
+     0.03%     0.03%  :34336   [guest.kernel.kallsyms]  [g] __srcu_read_unlock
+     0.03%     0.03%  :34336   [guest.kernel.kallsyms]  [g] time_cpufreq_notifier
+     0.02%     0.02%  :34336   [guest.kernel.kallsyms]  [g] irq_spurious_proc_show
+     0.02%     0.02%  :34336   [guest.kernel.kallsyms]  [g] alarm_timer_nsleep
+     0.02%     0.02%  :34336   [guest.kernel.kallsyms]  [g] ksoftirqd_should_run
+     0.02%     0.02%  :34333   [guest.kernel.kallsyms]  [g] tg_set_cfs_bandwidth
+     0.02%     0.02%  :34333   [guest.kernel.kallsyms]  [g] create_prof_cpu_mask
+     0.02%     0.02%  :34336   [guest.kernel.kallsyms]  [g] create_prof_cpu_mask
+     0.02%     0.02%  :34333   [guest.kernel.kallsyms]  [g] fat_msg
+     0.02%     0.02%  :34336   [guest.kernel.kallsyms]  [g] tick_check_new_device
+     0.02%     0.02%  :34333   [guest.kernel.kallsyms]  [g] __switch_to_xtra
+     0.02%     0.02%  :34336   [guest.kernel.kallsyms]  [g] tick_setup_device
+     0.02%     0.02%  :34336   [guest.kernel.kallsyms]  [g] init_timer_key
+     0.02%     0.02%  :34336   [guest.kernel.kallsyms]  [g] rcu_jiffies_till_stall_check
+     0.02%     0.02%  :34333   [guest.kernel.kallsyms]  [g] ftrace_raw_output_irq_handler_exit
+     0.02%     0.02%  :34336   [guest.kernel.kallsyms]  [g] arp_ignore
+     0.02%     0.02%  :34336   [guest.kernel.kallsyms]  [g] clockevents_register_device
+     0.02%     0.02%  :34336   [guest.kernel.kallsyms]  [g] hpet_rtc_interrupt
+     0.02%     0.02%  :34336   [guest.kernel.kallsyms]  [g] init_srcu_struct
+     0.01%     0.01%  :34333   [guest.kernel.kallsyms]  [g] irq_node_proc_show
+     0.01%     0.01%  :34336   [guest.kernel.kallsyms]  [g] __fat_fs_error
+     0.01%     0.01%  :34336   [guest.kernel.kallsyms]  [g] tick_check_replacement
+     0.01%     0.01%  :34336   [guest.kernel.kallsyms]  [g] avc_denied.isra.0
+     0.01%     0.01%  :34336   [guest.kernel.kallsyms]  [g] tick_get_device
+     0.01%     0.01%  :34336   [guest.kernel.kallsyms]  [g] irq_affinity_proc_show
+     0.01%     0.01%  :34336   [guest.kernel.kallsyms]  [g] sysfs_show_current_tick_dev
+     0.01%     0.01%  :34333   [guest.kernel.kallsyms]  [g] __fat_fs_error
+     0.01%     0.01%  :34336   [guest.kernel.kallsyms]  [g] ftrace_raw_output_irq_handler_entry
+     0.01%     0.01%  :34336   [guest.kernel.kallsyms]  [g] tick_is_oneshot_available
+     0.01%     0.01%  :34336   [guest.kernel.kallsyms]  [g] irq_domain_add_simple
+     0.01%     0.01%  :34333   [guest.kernel.kallsyms]  [g] irq_spurious_proc_show
+     0.01%     0.01%  :34336   [guest.kernel.kallsyms]  [g] tick_do_broadcast.constprop.6
+     0.01%     0.01%  :34336   [guest.kernel.kallsyms]  [g] sock_rps_save_rxhash.isra.28.part.29
+     0.01%     0.01%  :34336   [guest.kernel.kallsyms]  [g] prof_cpu_mask_proc_write
+     0.01%     0.01%  :34336   [guest.kernel.kallsyms]  [g] perf_trace_itimer_expire
+     0.01%     0.01%  :34336   [guest.kernel.kallsyms]  [g] srcu_barrier
+     0.01%     0.01%  :34336   [guest.kernel.kallsyms]  [g] store_ignore_nice_load.isra.3
+     0.01%     0.01%  :34336   [guest.kernel.kallsyms]  [g] wakeme_after_rcu
+     0.01%     0.01%  :34333   [guest.kernel.kallsyms]  [g] ftrace_raw_output_irq_handler_entry
+     0.01%     0.01%  :34333   [guest.kernel.kallsyms]  [g] ftrace_raw_output_softirq
+     0.01%     0.01%  :34336   [guest.kernel.kallsyms]  [g] debug_kfree
+     0.01%     0.01%  :34336   [guest.kernel.kallsyms]  [g] clockevents_notify
+     0.01%     0.01%  :34336   [guest.kernel.kallsyms]  [g] parse_probe_arg
+     0.00%     0.00%  :34336   [guest.kernel.kallsyms]  [g] hrtick_start
+     0.00%     0.00%  :34336   [guest.kernel.kallsyms]  [g] detach_if_pending
+     0.00%     0.00%  :34336   [guest.kernel.kallsyms]  [g] tasklet_init
+     0.00%     0.00%  :34336   [guest.kernel.kallsyms]  [g] show_stack
+     0.00%     0.00%  :34336   [guest.kernel.kallsyms]  [g] wakeup_softirqd
+     0.00%     0.00%  :34336   [guest.kernel.kallsyms]  [g] arch_local_irq_enable
+     0.00%     0.00%  :34336   [guest.kernel.kallsyms]  [g] tasklet_kill
+     0.00%     0.00%  :34336   [guest.kernel.kallsyms]  [g] default_affinity_show
+     0.00%     0.00%  :34336   [guest.kernel.kallsyms]  [g] ftrace_raw_output_softirq
+     0.00%     0.00%  :34336   [guest.kernel.kallsyms]  [g] store_sampling_down_factor.isra.4
+     0.00%     0.00%  :34336   [guest.kernel.kallsyms]  [g] synchronize_srcu_expedited
+     0.00%     0.00%  :34336   [guest.kernel.kallsyms]  [g] update_rq_clock
+     0.00%     0.00%  :34336   [guest.kernel.kallsyms]  [g] tick_do_periodic_broadcast
+     0.00%     0.00%  :34336   [guest.kernel.kallsyms]  [g] tick_install_replacement
+     0.00%     0.00%  :34336   [guest.kernel.kallsyms]  [g] amd_get_subcaches
+     0.00%     0.00%  :34334   [guest.kernel.kallsyms]  [g] amd_get_subcaches
+     0.00%     0.00%  :34336   [guest.kernel.kallsyms]  [g] tick_handle_periodic
+     0.00%     0.00%  :34336   [guest.kernel.kallsyms]  [g] __page_cache_alloc
+
+I am not sure how correct the symbol mapping of perf is, so I don't know if this is usable at all.
+
+I have dumped info registers with the `qemu-monitor-command` command after the  migration problematic VM and this gave the following output:
+
+RAX=0000000000001975 RBX=ffff8802342fc000 RCX=000000000000beac RDX=000000000000beaa
+RSI=000000000000beac RDI=ffff8802342fc000 RBP=ffff880233d3fb18 RSP=ffff880233d3fb18
+R8 =0000000000000286 R9 =ffff8800a71eee40 R10=ffff8800a71eeed4 R11=000000000000000a
+R12=ffff8802342fc000 R13=ffffffff81cdf010 R14=ffff880233d3fb58 R15=ffff88003672b200
+RIP=ffffffff817360b7 RFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0
+ES =0000 0000000000000000 000fffff 00000000
+CS =0010 0000000000000000 ffffffff 00a09b00 DPL=0 CS64 [-RA]
+SS =0018 0000000000000000 ffffffff 00c09300 DPL=0 DS   [-WA]
+DS =0000 0000000000000000 000fffff 00000000
+FS =0000 0000000000000000 000fffff 00000000
+GS =0000 ffff88023fc00000 000fffff 00000000
+LDT=0000 0000000000000000 000fffff 00000000
+TR =0040 ffff88023fc04440 00002087 00008b00 DPL=0 TSS64-busy
+GDT=     ffff88023fc0c000 0000007f
+IDT=     ffffffffff576000 00000fff
+CR0=8005003b CR2=0000000000408950 CR3=0000000232098000 CR4=00000670
+DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
+DR6=00000000ffff0ff0 DR7=0000000000000400
+EFER=0000000000000d01
+FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00001fa0
+FPR0=0000000000000000 0000 FPR1=0000000000000000 0000
+FPR2=0000000000000000 0000 FPR3=0000000000000000 0000
+FPR4=0000000000000000 0000 FPR5=0000000000000000 0000
+FPR6=0000000000000000 0000 FPR7=0000000000000000 0000
+XMM00=ffffffffff0000ff0000000000000000 XMM01=0000010101000000ffffffffffffffff
+XMM02=00007fe302de17006776615f64616f6c XMM03=00000000000000000000000000000000
+XMM04=00000000000000000000000000000000 XMM05=00000000000000000000000000ff0000
+XMM06=5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b XMM07=20202020202020202020202020202020
+XMM08=00000000000000000000000000000000 XMM09=00000000000000000000000000000000
+XMM10=00000000000000000000000000000000 XMM11=00000000000000000000000000000000
+XMM12=00ff000000ff0000000000000000ff00 XMM13=00000000000000000000000000000000
+XMM14=00000000000000000000000000000000 XMM15=00000000000000000000000000000000
+
+And I looped this for a minute to check were the RIP is changing to:
+136 RIP=0000000000434c1b
+173 RIP=ffffffff8105144a
+  2 RIP=ffffffff810521ff
+  1 RIP=ffffffff81070816
+
+
+I tried to reproduce this with some manual actions prior to migrating between qemu 2.6.2 and 2.11.1 on our testing environment using similar hardware (56 core model name: Intel(R) Xeon(R) Gold 6126 CPU @ 2.60GHz)
+And I was not able to reproduce this, i tried the following:
+- restore without filesystem caches (see new perf traces below)
+- create vm with same kernel as stuck vm
+- restore paused detach net device and virtio block device (detach doesn't work)
+- try to do a lot of network and disk io while migrating
+- ecrypt fs actions during migration
+- migrate 4000 times between 2.6.2 -> 2.11 using loop
+- add extra timer calls inside guest for migrate loop (done using cyclictest)
+- try with guest kernel 3.13.0-145-generic, same kernel vm was running with this issue
+- try host clock/timer calls on 2.11.1 host prior and during migration bound on first cpu core (cyclictest -a 0 -c 1 -d 200 -H -l 1 -t 2)
+
+I asked the vm owner what he is doing on his vm, and he told me that he is using 80% of his mem around 14G of the 16G, the vm is running a tomcat 7 server and a libreoffice deamon the vm has a load of 1.0 and runs Ubuntu 14.04 with kernel 3.13.0-145.
+
+The other vms were running centos 6, centos 7, debian 7, debian 8, ubuntu 13.10, ubuntu 14.04, ubuntu 12.04 the majority of these vms are running linux kernel 3.*.
+
+The thing is I am actually out of ideas for reproducing this, and I am not sure how to pinpoint this issue, I would like some help and possible some extra tips on debugging.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1776 b/results/classifier/gemma3:12b/kernel/1776
new file mode 100644
index 00000000..4a236cd3
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1776
@@ -0,0 +1,2 @@
+
+qemu-armel SEGFAULTs when trying to map a commpage on armel
diff --git a/results/classifier/gemma3:12b/kernel/1778473 b/results/classifier/gemma3:12b/kernel/1778473
new file mode 100644
index 00000000..fc998693
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1778473
@@ -0,0 +1,133 @@
+
+[Crash] qemu-system-x86_64: mov_ss_trap_64 PANIC: double fault, error_code: 0x0
+
+Kselftest test case mov_ss_trap_64 is causing kernel panic on
+qemu-system-x86_64 and PASS on real x86_64 hardware.
+
+qemu-system-x86_64 version is 2.12.0
+host architecture: amd64
+
+Test failed on recent stable rc kernel,
+4.17.3-rc1, 4.16.18-rc1 and 4.14.52-rc1.
+
+
+Test code snippet,
+main() {
+<>
+      printf("[RUN]\tMOV SS; CS CS INT3\n");
+      asm volatile ("mov %[ss], %%ss; .byte 0x2e, 0x2e; int3" :: [ss] "m" (ss));
+<>
+}
+
+Kerel crash log,
+# cd /opt/kselftests/mainline/x86
+# ./mov_ss_trap_64
+	SS = 0x2b, &SS = 0x0x604188
+	Set up a watchpoint
+	DR0 = 604188, DR1 = 400a19, DR7 = 7000a
+[RUN]	Read from watched memory (should get SIGTRAP)
+	Got SIGTRAP with RIP=4008ea, EFLAGS.RF=0
+[RUN]	MOV SS; INT3
+	Got SIGTRAP with RIP=4008fb, EFLAGS.RF=0
+[RUN]	MOV SS; INT 3
+	Got SIGTRAP with RIP=40090d, EFLAGS.RF=0
+[RUN]	M[   20.305426] PANIC: double fault, error_code: 0x0
+OV SS; CS CS INT3
+	Got SIGTRAP with RIP=400920,[   20.308317] CPU: 3 PID: 2471 Comm: mov_ss_trap_64 Not tainted 4.17.3-rc1 #1
+ EFLAGS.RF=0
+[RUN]	MOV SS; CSx14 INT3
+[   20.311664] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1 04/01/2014
+[   20.314738] RIP: 0010:error_entry+0x32/0x100
+[   20.316198] RSP: 0000:fffffe0000086000 EFLAGS: 00010046
+[   20.317911] RAX: 0000000092400a87 RBX: 0000000000000000 RCX: 0000000000000000
+[   20.320168] RDX: 0000000000000000 RSI: ffffffff92400f18 RDI: ffffffff92401146
+[   20.322405] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
+[   20.324320] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
+[   20.326073] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
+[   20.327869] FS:  00007f3174aefe80(0000) GS:ffff9f447fd80000(0000) knlGS:0000000000000000
+[   20.329850] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
+[   20.331343] CR2: fffffe0000085ff8 CR3: 0000000136d2e000 CR4: 00000000000006e0
+[   20.333150] DR0: 0000000000604188 DR1: 0000000000400a19 DR2: 0000000000000000
+[   20.334893] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 000000000007060a
+[   20.336649] Call Trace:
+[   20.337523]  <ENTRY_TRAMPOLINE>
+[   20.338507]  ? native_iret+0x7/0x7
+[   20.339611]  ? page_fault+0x8/0x30
+[   20.340693]  ? error_entry+0x86/0x100
+[   20.341871]  ? trace_hardirqs_off_caller+0x7/0xa0
+[   20.343212]  ? trace_hardirqs_off_thunk+0x1a/0x1c
+[   20.344554]  ? native_iret+0x7/0x7
+[   20.345647]  ? page_fault+0x8/0x30
+[   20.346716]  ? error_entry+0x86/0x100
+[   20.347853]  ? page_fault+0x8/0x30
+[   20.348920]  ? ist_enter+0x6/0xa0
+[   20.349961]  ? do_int3+0x34/0x120
+[   20.351095]  ? int3+0x14/0x20
+[   20.352047]  </ENTRY_TRAMPOLINE>
+[   20.353060] Code: 48 89 7c 24 08 52 31 d2 51 31 c9 50 41 50 45 31 c0 41 51 45 31 c9 41 52 45 31 d2 41 53 45 31 db 53 31 db 55 31 ed 41 54 45 31 e4 <41> 55 45 31 ed 41 56 45 31 f6 41 57 45 31 ff 56 48 8d 6c 24 09 
+[   20.357895] Kernel panic - not syncing: Machine halted.
+[   20.359385] CPU: 3 PID: 2471 Comm: mov_ss_trap_64 Not tainted 4.17.3-rc1 #1
+[   20.361271] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1 04/01/2014
+[   20.363513] Call Trace:
+[   20.364367]  <#DF>
+[   20.365109]  dump_stack+0x68/0x95
+[   20.366131]  panic+0xe3/0x22a
+[   20.367207]  df_debug+0x2d/0x30
+[   20.368254]  do_double_fault+0x9f/0x120
+[   20.369387]  double_fault+0x23/0x30
+[   20.370444] RIP: 0010:error_entry+0x32/0x100
+[   20.371791] RSP: 0000:fffffe0000086000 EFLAGS: 00010046
+[   20.373246] RAX: 0000000092400a87 RBX: 0000000000000000 RCX: 0000000000000000
+[   20.375250] RDX: 0000000000000000 RSI: ffffffff92400f18 RDI: ffffffff92401146
+[   20.377103] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
+[   20.378958] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
+[   20.380808] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
+[   20.382744]  ? page_fault+0x8/0x30
+[   20.383925]  ? error_entry+0x86/0x100
+[   20.385037]  </#DF>
+[   20.385793]  <ENTRY_TRAMPOLINE>
+[   20.386774]  ? native_iret+0x7/0x7
+[   20.387839]  ? page_fault+0x8/0x30
+[   20.388901]  ? error_entry+0x86/0x100
+[   20.389997]  ? trace_hardirqs_off_caller+0x7/0xa0
+[   20.391464]  ? trace_hardirqs_off_thunk+0x1a/0x1c
+[   20.392850]  ? native_iret+0x7/0x7
+[   20.393886]  ? page_fault+0x8/0x30
+[   20.394984]  ? error_entry+0x86/0x100
+[   20.396092]  ? page_fault+0x8/0x30
+[   20.397145]  ? ist_enter+0x6/0xa0
+[   20.398167]  ? do_int3+0x34/0x120
+[   20.399213]  ? int3+0x14/0x20
+[   20.400226]  </ENTRY_TRAMPOLINE>
+[   20.401574] Kernel Offset: 0x10800000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
+[   20.404788] ---[ end Kernel panic - not syncing: Machine halted. ]---
+
+Full crash log can be found at,
+https://lkft.validation.linaro.org/scheduler/job/303760
+
+Download this image.
+http://snapshots.linaro.org/openembedded/lkft/morty/intel-core2-32/rpb/linux-stable-rc-4.17/7/rpb-console-image-intel-core2-32-20180624171508-7.hddimg.xz 
+
+Boot command:
+qemu-system-x86_64
+ -cpu host
+ -enable-kvm
+ -nographic
+ -net nic,model=virtio,macaddr=DE:AD:BE:EF:66:01
+ -net tap -m 1024
+ -monitor none
+ -drive format=raw,file=rpb-console-image-intel-core2-32-20180624171508-7.hddimg,if=virtio
+ -m 4096
+ -smp 4
+ -drive format=qcow2,file=/lava-guest.qcow2,media=disk,if=virtio
+
+
+After successfull boot,
+login as root
+
+Run the in-built test,
+cd /opt/kselftests/mainline/x86
+./mov_ss_trap_64
+
+Test case link,
+https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/tree/tools/testing/selftests/x86/mov_ss_trap.c?h=linux-4.17.y
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1779017 b/results/classifier/gemma3:12b/kernel/1779017
new file mode 100644
index 00000000..9fadf1a3
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1779017
@@ -0,0 +1,44 @@
+
+qemu-system-arm: crashes raspian kernels with divide-by-zero
+
+While trying to boot a arm kernel for a raspi2 machine (kernel7-4.9.41-stretch.img in my case, but applies to other versions, too) the kernel crash with a division by zero. The output on the sreial console is:
+[   10.022377] [<8011d344>] (__warn) from [<8011d42c>] (warn_slowpath_null+0x30/0x38)
+[   10.024726] [<8011d42c>] (warn_slowpath_null) from [<804da378>] (uart_get_baud_rate+0xf8/0x160)
+
+...
+
+[   10.094933] Hardware name: BCM2835
+[   10.101507] [<8010fb3c>] (unwind_backtrace) from [<8010c058>] (show_stack+0x20/0x24)
+[   10.105413] [<8010c058>] (show_stack) from [<80455f84>] (dump_stack+0xd4/0x118)
+[   10.140268] [<80455f84>] (dump_stack) from [<8010bed4>] (__div0+0x24/0x28)
+[   10.143065] [<8010bed4>] (__div0) from [<8045498c>] (Ldiv0+0x8/0x14)
+[   10.145553] [<8045498c>] (Ldiv0) from [<804e5538>] (pl011_set_termios+0x9c/0x37c)
+[   10.148017] [<804e5538>] (pl011_set_termios) from [<804da954>] (uart_change_speed+0x40/0xfc)
+[   10.185887] [<804da954>] (uart_change_speed) from [<804ddedc>] (uart_startup.part.3+0xa4/0x13c)
+[   10.222187] [<804ddedc>] (uart_startup.part.3) from [<804ddfcc>] (uart_port_activate+0x58/0x64)
+[   10.226014] [<804ddfcc>] (uart_port_activate) from [<804c93b8>] (tty_port_open+0xa0/0xe0)
+[   10.228398] [<804c93b8>] (tty_port_open) from [<804dce64>] (uart_open+0x40/0x48)
+[   10.264254] [<804dce64>] (uart_open) from [<804c1d70>] (tty_open+0xc0/0x678)
+[   10.266697] [<804c1d70>] (tty_open) from [<802753f0>] (chrdev_open+0xe0/0x1a0)
+[   10.269049] [<802753f0>] (chrdev_open) from [<8026d964>] (do_dentry_open+0x1f4/0x314)
+[   10.271620] [<8026d964>] (do_dentry_open) from [<8026ec00>] (vfs_open+0x60/0x8c)
+[   10.275245] [<8026ec00>] (vfs_open) from [<8027f39c>] (path_openat+0x2bc/0x1040)
+[   10.312827] [<8027f39c>] (path_openat) from [<80281040>] (do_filp_open+0x70/0xd4)
+[   10.317860] [<80281040>] (do_filp_open) from [<8026efd8>] (do_sys_open+0x120/0x1d0)
+[   10.320370] [<8026efd8>] (do_sys_open) from [<8026f0b4>] (SyS_open+0x2c/0x30)
+[   10.357033] [<8026f0b4>] (SyS_open) from [<801080c0>] (ret_fast_syscall+0x0/0x1c)
+
+Tracking that down in the linux kernel source, it looks like somehow uart_get_baud_rate() returns 0.
+
+The same kernel could be booted without problem with qemu version 2.11.
+Trying to bisecting the issue revealed commit @d9f8bbd8eb4e95db97cf02bd03af86a3d606f4f1 as the culprit.
+
+Commandline to run was:
+qemu-system-arm -M raspi2 \
+	-kernel "$KERNEL" \
+	-m 1024 \
+	-d guest_errors,unimp \
+	-dtb bcm2709-rpi-2-b.dtb \
+	-drive file="$IMG,if=sd,format=raw"
+
+Distribution is SuSE tumbleweed (x86_64, kernel 4.17.2), but same problem also happens with a freshly compiled qemu from git repository.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1780814 b/results/classifier/gemma3:12b/kernel/1780814
new file mode 100644
index 00000000..dbc46bbb
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1780814
@@ -0,0 +1,34 @@
+
+lib/raid6/neon4.c:118:1: internal compiler error
+
+I am facing below issue when i am trying to cross compile kernel for raspberry pi 3.
+please give solution .
+
+
+Below is log
+
+
+
+CHK     include/config/kernel.release
+  CHK     include/generated/uapi/linux/version.h
+  CHK     include/generated/utsrelease.h
+  CHK     include/generated/bounds.h
+  CHK     include/generated/timeconst.h
+  CHK     include/generated/asm-offsets.h
+  CALL    scripts/checksyscalls.sh
+  CHK     scripts/mod/devicetable-offsets.h
+  CHK     include/generated/compile.h
+  CHK     kernel/config_data.h
+  CC [M]  lib/raid6/neon4.o
+lib/raid6/neon4.c: In function ‘raid6_neon4_gen_syndrome_real’:
+lib/raid6/neon4.c:118:1: internal compiler error: in dwarf2out_frame_debug_adjust_cfa, at dwarf2cfi.c:1078
+ }
+ ^
+Please submit a full bug report,
+with preprocessed source if appropriate.
+See <https://bugs.launchpad.net/gcc-linaro> for instructions.
+scripts/Makefile.build:328: recipe for target 'lib/raid6/neon4.o' failed
+make[2]: *** [lib/raid6/neon4.o] Error 1
+scripts/Makefile.build:587: recipe for target 'lib/raid6' failed
+make[1]: *** [lib/raid6] Error 2
+Makefile:1034: recipe for target 'lib' failed
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1783437 b/results/classifier/gemma3:12b/kernel/1783437
new file mode 100644
index 00000000..ddac9378
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1783437
@@ -0,0 +1,10 @@
+
+read-modify-write page faults error code has write bit unset
+
+Consider the attached C file, which does a read-modify-write of the form `add [mem], reg`, where `mem` points to a non-present page. In the resulting page fault, the W/R bit is not set, while real hardware does set this bit.
+
+% gcc -m32 qemu-bug1.c&& ./a.out && qemu-i386 ./a.out
+page fault: addr=0x70000000 err=0x6
+page fault: addr=0x70000000 err=0x4
+
+Tested on the qemu-3.0.0-rc1 release.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1785203 b/results/classifier/gemma3:12b/kernel/1785203
new file mode 100644
index 00000000..aae9a15c
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1785203
@@ -0,0 +1,44 @@
+
+accel/tcg/translate-all.c:2511: page_check_range: Assertion `start < ((target_ulong)1 << L1_MAP_ADDR_SPACE_BITS)' failed.
+
+qemu-riscv64 version 2.12.93 crashes when mincore() is called with invalid pointer with the following message:
+
+qemu-riscv64: /opt/qemu/accel/tcg/translate-all.c:2511: page_check_range: Assertion `start < ((target_ulong)1 << L1_MAP_ADDR_SPACE_BITS)' failed.
+qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x600014ef
+
+Testcase:
+
+#include <sys/mman.h>
+
+int main (void)
+{
+  unsigned char v;
+  return mincore ((void *) 0x00000010000000000, 1, &v);
+}
+
+Backtrace:
+
+#0  raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
+#1  0x000000006000140a in abort () at abort.c:79
+#2  0x00000000600012ec in __assert_fail_base (
+    fmt=0x6024eae8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", 
+    assertion=0x601b9758 "start < ((target_ulong)1 << L1_MAP_ADDR_SPACE_BITS)", 
+    file=0x601b9658 "/opt/qemu/accel/tcg/translate-all.c", line=2511, 
+    function=0x601b9810 <__PRETTY_FUNCTION__.23867> "page_check_range") at assert.c:92
+#3  0x000000006010e10e in __assert_fail (
+    assertion=assertion@entry=0x601b9758 "start < ((target_ulong)1 << L1_MAP_ADDR_SPACE_BITS)", file=file@entry=0x601b9658 "/opt/qemu/accel/tcg/translate-all.c", line=line@entry=2511, 
+    function=function@entry=0x601b9810 <__PRETTY_FUNCTION__.23867> "page_check_range")
+    at assert.c:101
+#4  0x000000006003e916 in page_check_range (start=start@entry=1099511627776, len=len@entry=1, 
+    flags=flags@entry=1) at /opt/qemu/accel/tcg/translate-all.c:2511
+#5  0x0000000060057717 in access_ok (size=1, addr=1099511627776, type=0)
+    at /opt/qemu/linux-user/qemu.h:567
+#6  lock_user (copy=0, len=1, guest_addr=1099511627776, type=0)
+    at /opt/qemu/linux-user/qemu.h:567
+#7  do_syscall (cpu_env=cpu_env@entry=0x622fca28, num=232, arg1=1099511627776, arg2=1, 
+    arg3=274886298751, arg4=0, arg5=274886298808, arg6=66518, arg7=0, arg8=0)
+    at /opt/qemu/linux-user/syscall.c:11635
+#8  0x0000000060066c5c in cpu_loop (env=env@entry=0x622fca28)
+    at /opt/qemu/linux-user/riscv/cpu_loop.c:55
+#9  0x0000000060002156 in main (argc=<optimized out>, argv=0x7fffffffed68, 
+    envp=<optimized out>) at /opt/qemu/linux-user/main.c:819
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1786343 b/results/classifier/gemma3:12b/kernel/1786343
new file mode 100644
index 00000000..29dffe10
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1786343
@@ -0,0 +1,37 @@
+
+QEMU v3.0.0-rc4 configure fails with --enable-mpath on CentOS 7.5
+
+QEMU v3.0.0-rc4 configure fails with --enable-mpath on CentOS 7.5.
+
+After commit b3f1c8c413bc83e4a2cc7a63e4eddf9fe6449052 "qemu-pr-helper: use new
+libmultipath API", QEMU started using new libmultipath API, which is not
+available on CentOS 7.5.  Reverting this commit, configure passes.
+
+Steps to reproduce (fails on x86_64 and ppc64le architectures):
+
+  $ git clone git://git.qemu.org/qemu.git
+  $ mkdir -p qemu/build && cd qemu/build
+  $ ../configure --enable-mpath
+  ERROR: Multipath requires libmpathpersist devel
+
+  $ rpm -qa | grep device-mapper | sort
+  device-mapper-1.02.146-4.el7.ppc64le
+  device-mapper-devel-1.02.146-4.el7.ppc64le
+  device-mapper-libs-1.02.146-4.el7.ppc64le
+  device-mapper-multipath-0.4.9-119.el7.ppc64le
+  device-mapper-multipath-devel-0.4.9-119.el7.ppc64le
+  device-mapper-multipath-libs-0.4.9-119.el7.ppc64le
+
+Snippet from config.log:
+
+  funcs: do_compiler do_cc compile_prog main
+  lines: 92 125 3580 0
+  cc -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -m64 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wendif-labels -Wno-missing-include-dirs -Wempty-body -Wnested-externs -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wold-style-declaration -Wold-style-definition -Wtype-limits -fstack-protector-strong -Wno-missing-braces -I/usr/include/p11-kit-1 -I/usr/include/libpng15 -o config-temp/qemu-conf.exe config-temp/qemu-conf.c -m64 -g -ludev -lmultipath -lmpathpersist
+  config-temp/qemu-conf.c: In function ‘main’:
+  config-temp/qemu-conf.c:15:5: error: too few arguments to function ‘mpath_lib_init’
+       multipath_conf = mpath_lib_init();
+       ^
+  In file included from config-temp/qemu-conf.c:2:0:
+  /usr/include/mpath_persist.h:179:12: note: declared here
+   extern int mpath_lib_init (struct udev *udev);
+              ^
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1788582 b/results/classifier/gemma3:12b/kernel/1788582
new file mode 100644
index 00000000..57dbecec
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1788582
@@ -0,0 +1,68 @@
+
+Race condition during shutdown
+
+I ran into a bug when I started several VMs in parallel using
+libvirt. The VMs are using only a kernel and a initrd (which includes a
+minimal OS). The guest OS itself does a 'poweroff -f' as soon as the
+login prompt shows up. So the expectaction is that the VMs will start,
+the shutdown will be initiated, and the QEMU processes will then
+end. But instead some of the QEMU processes get stuck in ppoll().
+
+A bisect showed that the first bad commit was
+0f12264e7a41458179ad10276a7c33c72024861a ("block: Allow graph changes in
+bdrv_drain_all_begin/end sections").
+
+I've already tried the current master (13b7b188501d419a7d63c016e00065bcc693b7d4) 
+since the problem might be related
+to the commit a1405acddeb0af6625dd9c30e8277b08e0885bd3 ("aio: Do
+aio_notify_accept only during blocking aio_poll"). But the bug is still
+there. I’ve reproduced the bug on x86_64 and on s390x.
+
+The backtrace of a hanging QEMU process:
+
+(gdb) bt
+#0  0x00007f5d0e251b36 in ppoll () from target:/lib64/libc.so.6
+#1  0x0000560191052014 in qemu_poll_ns (fds=0x560193b23d60, nfds=5, timeout=55774838936000) at /home/user/git/qemu/util/qemu-timer.c:334
+#2  0x00005601910531fa in os_host_main_loop_wait (timeout=55774838936000) at /home/user/git/qemu/util/main-loop.c:233
+#3  0x0000560191053119 in main_loop_wait (nonblocking=0) at /home/user/git/qemu/util/main-loop.c:497
+#4  0x0000560190baf454 in main_loop () at /home/user/git/qemu/vl.c:1866
+#5  0x0000560190baa552 in main (argc=71, argv=0x7ffde10e41c8, envp=0x7ffde10e4408) at /home/user/git/qemu/vl.c:4644
+
+The used domain definition is:
+
+<domain type='kvm'>
+  <name>test</name>
+  <memory unit='KiB'>716800</memory>
+  <vcpu placement='static'>2</vcpu>
+  <iothreads>8</iothreads>
+  <os>
+    <type arch='x86_64' machine='pc-i440fx-3.0'>hvm</type>
+    <kernel>/var/lib/libvirt/images/vmlinuz-4.14.13-200.fc26.x86_64</kernel>
+    <initrd>/var/lib/libvirt/images/test-image-qemux86_64+modules-4.14.13-200.fc26.x86_64.cpio.gz</initrd>
+    <cmdline>console=hvc0 STARTUP=shutdown.sh</cmdline>
+    <boot dev='hd'/>
+  </os>
+  <features>
+    <acpi/>
+  </features>
+  <clock offset='utc'/>
+  <on_poweroff>destroy</on_poweroff>
+  <on_reboot>restart</on_reboot>
+  <on_crash>preserve</on_crash>
+  <devices>
+    <emulator>/usr/local/qemu/master/bin/qemu-system-x86_64</emulator>
+    <controller type='usb' index='0' model='piix3-uhci'>
+      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
+    </controller>
+    <controller type='pci' index='0' model='pci-root'/>
+    <controller type='virtio-serial' index='0'>
+      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
+    </controller>
+    <console type='pty'>
+      <target type='virtio' port='0'/>
+    </console>
+    <input type='mouse' bus='ps2'/>
+    <input type='keyboard' bus='ps2'/>
+    <memballoon model='none'/>
+  </devices>
+</domain>
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1791796 b/results/classifier/gemma3:12b/kernel/1791796
new file mode 100644
index 00000000..eb16483a
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1791796
@@ -0,0 +1,124 @@
+
+unimplemented thread syscalls in nios2 user-mode emulation
+
+This bug is reported against the 3.0 release.
+
+I noticed that the GCC test gcc.dg/torture/tls/tls-test.c is failing when run in user-mode qemu for nios2 target.  The problem appears to be that the thread-related syscalls are unimplemented in qemu.  Here is output from running with -strace:
+
+22484 brk(NULL) = 0x00005000
+22484 uname(0x7fffef5a) = 0
+22484 faccessat(AT_FDCWD,"/etc/ld.so.preload",R_OK,0x5) = -1 errno=2 (No such file or directory)
+22484 openat(AT_FDCWD,"/scratch/sandra/nios2-linux-trunk3/obj/test-2018.11-999999-nios2-linux-gnu/host-x86_64-linux-gnu/sourceryg++-2018.11/nios2-linux-gnu/libc/./lib/./tls/libm.so.6",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 errno=2 (No such file or directory)
+22484 fstatat64(AT_FDCWD,"/scratch/sandra/nios2-linux-trunk3/obj/test-2018.11-999999-nios2-linux-gnu/host-x86_64-linux-gnu/sourceryg++-2018.11/nios2-linux-gnu/libc/./lib/./tls",0x7fffe870,0) = -1 errno=2 (No such file or directory)
+22484 openat(AT_FDCWD,"/scratch/sandra/nios2-linux-trunk3/obj/test-2018.11-999999-nios2-linux-gnu/host-x86_64-linux-gnu/sourceryg++-2018.11/nios2-linux-gnu/libc/./lib/./libm.so.6",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 3
+22484 read(3,0x7fffe954,512) = 512
+22484 fstat64(3,0x7fffe870) = 0
+22484 mmap2(NULL,803596,PROT_EXEC|PROT_READ,MAP_PRIVATE|MAP_DENYWRITE,3,0) = 0x7f716000
+22484 mmap2(0x7f7d8000,12288,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_DENYWRITE|MAP_FIXED,3,0xc1) = 0x7f7d8000
+22484 close(3) = 0
+22484 openat(AT_FDCWD,"/scratch/sandra/nios2-linux-trunk3/obj/test-2018.11-999999-nios2-linux-gnu/host-x86_64-linux-gnu/sourceryg++-2018.11/nios2-linux-gnu/libc/./lib/./libpthread.so.0",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 3
+22484 read(3,0x7fffe948,512) = 512
+22484 mmap2(NULL,8192,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANONYMOUS,-1,0) = 0x7f714000
+22484 fstat64(3,0x7fffe864) = 0
+22484 mmap2(NULL,120700,PROT_EXEC|PROT_READ,MAP_PRIVATE|MAP_DENYWRITE,3,0) = 0x7f6f6000
+22484 mprotect(0x7f70e000,4096,PROT_NONE) = 0
+22484 mmap2(0x7f70f000,12288,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_DENYWRITE|MAP_FIXED,3,0x18) = 0x7f70f000
+22484 mmap2(0x7f712000,6012,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANONYMOUS|MAP_FIXED,-1,0) = 0x7f712000
+22484 close(3) = 0
+22484 openat(AT_FDCWD,"/scratch/sandra/nios2-linux-trunk3/obj/test-2018.11-999999-nios2-linux-gnu/host-x86_64-linux-gnu/sourceryg++-2018.11/nios2-linux-gnu/libc/./lib/./libc.so.6",O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 3
+22484 read(3,0x7fffe93c,512) = 512
+22484 fstat64(3,0x7fffe858) = 0
+22484 mmap2(NULL,1491048,PROT_EXEC|PROT_READ,MAP_PRIVATE|MAP_DENYWRITE,3,0) = 0x7f589000
+22484 mmap2(0x7f6de000,86016,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_DENYWRITE|MAP_FIXED,3,0x154) = 0x7f6de000
+22484 mmap2(0x7f6f3000,8296,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANONYMOUS|MAP_FIXED,-1,0) = 0x7f6f3000
+22484 close(3) = 0
+22484 mprotect(0x7f6de000,65536,PROT_READ) = 0
+22484 mprotect(0x7f70f000,8192,PROT_READ) = 0
+22484 mprotect(0x7f7d8000,4096,PROT_READ) = 0
+22484 mprotect(0x00003000,4096,PROT_READ) = 0
+22484 mprotect(0x7f7fc000,4096,PROT_READ) = 0
+22484 set_tid_address(2138131700,2147480980,2147480988,2147480988,87148,47) = 22484
+22484 set_robust_list(2138131708,12,2147480988,0,87148,47) = -1 errno=38 (Function not implemented)
+22484 rt_sigaction(32,0x7ffff36c,NULL) = 0
+22484 rt_sigaction(33,0x7ffff36c,NULL) = -1 errno=22 (Invalid argument)
+22484 rt_sigprocmask(SIG_UNBLOCK,0x7ffff4a8,NULL) = 0
+22484 getrlimit(3,2147480732,3,0,62512,47) = 0
+22484 mmap2(NULL,8392704,PROT_NONE,MAP_PRIVATE|MAP_ANONYMOUS|0x20000,-1,0) = 0x7ed88000
+22484 mprotect(0x7ed89000,8388608,PROT_READ|PROT_WRITE) = 0
+22484 brk(NULL) = 0x00005000
+22484 brk(0x00026000) = 0x00026000
+22484 clone(CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID,child_stack=0x7f588018,parent_tidptr=0x7f5884fc,tls=0x7f58f928,child_tidptr=0x7f5884fc) = 22503
+22484 io_setup(4001536,2136506392,2136507644,2136507644,2136537384,4100) = -1 errno=38 (Function not implemented)
+22484 futex(0x7f5884fc,FUTEX_WAIT,22503,NULL,NULL,0)22484 set_robust_list(2136507652,12,0,4100,2136508076,4100) = -1 errno=38 (Function not implemented)
+22484 madvise(2128117760,8372224,4,2136507672,528660,4100) = 0
+22484 exit(0)
+ = 0
+22484 fstat64(1,0x7fffef48) = 0
+22484 write(1,0x51e8,42)FAIL: a= 10, thr_a = 10 Addr = 0x7f715120
+ = 42
+22484 exit_group(1)
+sandra@build2-trusty-cs:/scratch/sandra/nios2-linux-trunk3$ 
+22484 mmap2(NULL,1491048,PROT_EXEC|PROT_READ,MAP_PRIVATE|MAP_DENYWRITE,3,0) = 0x7f589000
+22484 mmap2(0x7f6de000,86016,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_DENYWRITE|MAP_FIXED,3,0x154) = 0x7f6de000
+22484 mmap2(0x7f6f3000,8296,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANONYMOUS|MAP_FIXED,-1,0) = 0x7f6f3000
+22484 close(3) = 0
+22484 mprotect(0x7f6de000,65536,PROT_READ) = 0
+22484 mprotect(0x7f70f000,8192,PROT_READ) = 0
+22484 mprotect(0x7f7d8000,4096,PROT_READ) = 0
+22484 mprotect(0x00003000,4096,PROT_READ) = 0
+22484 mprotect(0x7f7fc000,4096,PROT_READ) = 0
+22484 set_tid_address(2138131700,2147480980,2147480988,2147480988,87148,47) = 22484
+22484 set_robust_list(2138131708,12,2147480988,0,87148,47) = -1 errno=38 (Function not implemented)
+22484 rt_sigaction(32,0x7ffff36c,NULL) = 0
+22484 rt_sigaction(33,0x7ffff36c,NULL) = -1 errno=22 (Invalid argument)
+22484 rt_sigprocmask(SIG_UNBLOCK,0x7ffff4a8,NULL) = 0
+22484 getrlimit(3,2147480732,3,0,62512,47) = 0
+22484 mmap2(NULL,8392704,PROT_NONE,MAP_PRIVATE|MAP_ANONYMOUS|0x20000,-1,0) = 0x7ed88000
+22484 mprotect(0x7ed89000,8388608,PROT_READ|PROT_WRITE) = 0
+22484 brk(NULL) = 0x00005000
+22484 brk(0x00026000) = 0x00026000
+22484 clone(CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID,child_stack=0x7f588018,parent_tidptr=0x7f5884fc,tls=0x7f58f928,child_tidptr=0x7f5884fc) = 22503
+22484 io_setup(4001536,2136506392,2136507644,2136507644,2136537384,4100) = -1 errno=38 (Function not implemented)
+22484 futex(0x7f5884fc,FUTEX_WAIT,22503,NULL,NULL,0)22484 set_robust_list(2136507652,12,0,4100,2136508076,4100) = -1 errno=38 (Function not implemented)
+22484 madvise(2128117760,8372224,4,2136507672,528660,4100) = 0
+22484 exit(0)
+ = 0
+22484 fstat64(1,0x7fffef48) = 0
+22484 write(1,0x51e8,42)FAIL: a= 10, thr_a = 10 Addr = 0x7f715120
+ = 42
+22484 exit_group(1)
+sandra@build2-trusty-cs:/scratch/sandra/nios2-linux-trunk3$ 
+22484 mmap2(NULL,1491048,PROT_EXEC|PROT_READ,MAP_PRIVATE|MAP_DENYWRITE,3,0) = 0x7f589000
+22484 mmap2(0x7f6de000,86016,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_DENYWRITE|MAP_FIXED,3,0x154) = 0x7f6de000
+22484 mmap2(0x7f6f3000,8296,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANONYMOUS|MAP_FIXED,-1,0) = 0x7f6f3000
+22484 close(3) = 0
+22484 mprotect(0x7f6de000,65536,PROT_READ) = 0
+22484 mprotect(0x7f70f000,8192,PROT_READ) = 0
+22484 mprotect(0x7f7d8000,4096,PROT_READ) = 0
+22484 mprotect(0x00003000,4096,PROT_READ) = 0
+22484 mprotect(0x7f7fc000,4096,PROT_READ) = 0
+22484 set_tid_address(2138131700,2147480980,2147480988,2147480988,87148,47) = 22484
+22484 set_robust_list(2138131708,12,2147480988,0,87148,47) = -1 errno=38 (Function not implemented)
+22484 rt_sigaction(32,0x7ffff36c,NULL) = 0
+22484 rt_sigaction(33,0x7ffff36c,NULL) = -1 errno=22 (Invalid argument)
+22484 rt_sigprocmask(SIG_UNBLOCK,0x7ffff4a8,NULL) = 0
+22484 getrlimit(3,2147480732,3,0,62512,47) = 0
+22484 mmap2(NULL,8392704,PROT_NONE,MAP_PRIVATE|MAP_ANONYMOUS|0x20000,-1,0) = 0x7ed88000
+22484 mprotect(0x7ed89000,8388608,PROT_READ|PROT_WRITE) = 0
+22484 brk(NULL) = 0x00005000
+22484 brk(0x00026000) = 0x00026000
+22484 clone(CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID,child_stack=0x7f588018,parent_tidptr=0x7f5884fc,tls=0x7f58f928,child_tidptr=0x7f5884fc) = 22503
+22484 io_setup(4001536,2136506392,2136507644,2136507644,2136537384,4100) = -1 errno=38 (Function not implemented)
+22484 futex(0x7f5884fc,FUTEX_WAIT,22503,NULL,NULL,0)22484 set_robust_list(2136507652,12,0,4100,2136508076,4100) = -1 errno=38 (Function not implemented)
+22484 madvise(2128117760,8372224,4,2136507672,528660,4100) = 0
+22484 exit(0)
+ = 0
+22484 fstat64(1,0x7fffef48) = 0
+22484 write(1,0x51e8,42)FAIL: a= 10, thr_a = 10 Addr = 0x7f715120
+ = 42
+22484 exit_group(1)
+
+Note that set_robust_list and clone are reported as unimplemented.
+
+I've reported the problems with the signal syscalls separately here.
+https://bugs.launchpad.net/qemu/+bug/1791763
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1793183 b/results/classifier/gemma3:12b/kernel/1793183
new file mode 100644
index 00000000..7316e75f
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1793183
@@ -0,0 +1,24 @@
+
+apt source --compile qemu-system-x86 fails on last ubuntu 18.04.1
+
+Error log:
+
+/tmp/qemu-2.10+dfsg/util/memfd.c:40:12: error: static declaration of ‘memfd_create’ follows non-static declaration
+ static int memfd_create(const char *name, unsigned int flags)
+            ^~~~~~~~~~~~
+In file included from /usr/include/x86_64-linux-gnu/bits/mman-linux.h:115:0,
+                 from /usr/include/x86_64-linux-gnu/bits/mman.h:45,
+                 from /usr/include/x86_64-linux-gnu/sys/mman.h:41,
+                 from /tmp/qemu-2.10+dfsg/include/sysemu/os-posix.h:29,
+                 from /tmp/qemu-2.10+dfsg/include/qemu/osdep.h:104,
+                 from /tmp/qemu-2.10+dfsg/util/memfd.c:28:
+/usr/include/x86_64-linux-gnu/bits/mman-shared.h:46:5: note: previous declaration of ‘memfd_create’ was here
+ int memfd_create (const char *__name, unsigned int __flags) __THROW;
+     ^~~~~~~~~~~~
+/tmp/qemu-2.10+dfsg/rules.mak:66: recipe for target 'util/memfd.o' failed
+make[1]: *** [util/memfd.o] Error 1
+make[1]: *** Waiting for unfinished jobs....
+make[1]: Leaving directory '/tmp/qemu-2.10+dfsg/qemu-build'
+debian/rules:121: recipe for target 'build-stamp' failed
+make: *** [build-stamp] Error 2
+dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1794950 b/results/classifier/gemma3:12b/kernel/1794950
new file mode 100644
index 00000000..86376be3
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1794950
@@ -0,0 +1,84 @@
+
+qemu hangs when guest is using linux kernel 4.16+
+
+I have been using qemu on daily basis 5+ years in order to do btrfs development and testing and it always worked perfectly, until I upgraded the linux kernel of the guests to 4.16. With 4.16+ kernels, when running all the fstests (previously called xfstests), the qemu process hangs (console unresponsive, can't ping or ssh the guest anymore, etc) and stays in a state Sl+ according to 'ps'.
+
+This happens on two different physical machines, one running openSUSE tumbleweed (which I don't access at the moment to check kernel version) and another running xubuntu (tried kernels 4.15.0-32-generic and vanilla 4.18.0). Using any kernel from 4.16 to 4.19-rc5 in the guests (they use different debian versions) makes qemu hang running the fstests suite (after about 30 to 40 minutes, either at test generic/299 or test generic/451).
+
+I tried different qemu versions, 2.11.2, 2.12.1 and 3.0.0, and it happens with all of them (all built from the sources available at https://www.qemu.org/download/#source).
+
+I built 3.0.0 with debug enabled, using the following parameters for 'configure':
+
+--prefix=/home/fdmanana/qemu-3.0.0 --enable-tools --enable-linux-aio --enable-kvm --enable-vnc --enable-vnc-png --enable-debug --extra-cflags="-O0 -g3 -fno-omit-frame-pointer"
+
+And captured a coredump of the qemu process, available at:
+
+https://www.dropbox.com/s/d1tlsimahykwhla/core_dump_debug.tar.xz?dl=0
+
+the stack traces of all threads, for a quick look:
+
+https://friendpaste.com/zqkz2pD0WgSdeSKITHPDf
+
+qemu is being invoked with the following script:
+
+#!/bin/bash -x
+
+sudo modprobe tun
+sudo modprobe kvm
+sudo modprobe kvm-intel
+
+sudo tunctl -t tap5 -u fdmanana
+sudo ifconfig tap5 up
+sudo brctl addif br0 tap5
+
+sudo umount /mnt/tmp5
+sudo mkdir -p /mnt/tmp5
+sudo mount -t tmpfs -o size=14G tmpfs /mnt/tmp5
+for ((i = 2; i <= 7; i++)); do
+        sudo qemu-img create -f qcow2 /mnt/tmp5/disk$i 13G
+done
+sudo chown fdmanana /mnt/tmp5/disk*
+
+qemu-system-x86_64 -m 4G \
+        -device virtio-scsi-pci \
+        -boot c \
+\
+        -drive if=none,file=debian5.qcow2,cache=none,aio=native,cache.direct=on,format=qcow2,id=drive0,discard=on \
+        -device scsi-hd,drive=drive0,bus=scsi.0 \
+\
+        -drive if=none,file=/mnt/tmp5/disk2,cache=writeback,format=qcow2,id=drive1,discard=on \
+        -device scsi-hd,drive=drive1,bus=scsi.0 \
+\
+        -drive if=none,file=/mnt/tmp5/disk3,cache=writeback,format=qcow2,id=drive2,discard=on \
+        -device scsi-hd,drive=drive2,bus=scsi.0 \
+\
+        -drive if=none,file=/mnt/tmp5/disk4,cache=writeback,format=qcow2,id=drive3,discard=on \
+        -device scsi-hd,drive=drive3,bus=scsi.0 \
+\
+        -drive if=none,file=/mnt/tmp5/disk5,cache=writeback,format=qcow2,id=drive4,discard=on \
+        -device scsi-hd,drive=drive4,bus=scsi.0 \
+\
+        -drive if=none,file=/mnt/tmp5/disk6,cache=writeback,format=qcow2,id=drive5,discard=on \
+        -device scsi-hd,drive=drive5,bus=scsi.0 \
+\
+        -drive if=none,file=/mnt/tmp5/disk7,cache=writeback,format=qcow2,id=drive6,discard=on \
+        -device scsi-hd,drive=drive6,bus=scsi.0 \
+\
+        -drive if=none,file=disk8,cache=writeback,aio=native,cache.direct=on,format=qcow2,id=drive7,discard=on \
+        -device scsi-hd,drive=drive7,bus=scsi.0 \
+\
+        -drive if=none,file=disk9,cache=writeback,aio=native,cache.direct=on,format=qcow2,id=drive8,discard=on \
+        -device scsi-hd,drive=drive8,bus=scsi.0 \
+\
+        -drive if=none,file=disk10,cache=writeback,aio=native,cache.direct=on,format=qcow2,id=drive9,discard=on \
+        -device scsi-hd,drive=drive9,bus=scsi.0 \
+\
+        -net nic,macaddr=52:54:00:12:34:fa -net tap,ifname=tap5,script=no,downscript=no \
+        -rtc base=localtime -enable-kvm -machine accel=kvm -smp 4 -cpu host \
+        -k pt -serial tcp:127.0.0.1:9997 -display vnc=:5
+
+
+
+Is there anything else I can provided to help debug this?
+
+Thanks.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1796520 b/results/classifier/gemma3:12b/kernel/1796520
new file mode 100644
index 00000000..97d23c2e
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1796520
@@ -0,0 +1,37 @@
+
+autogen crashes on qemu-sh4-user after 61dedf2af7
+
+Running "autogen --help" crashes on qemu-sh4-user with:
+
+(sid-sh4-sbuild)root@nofan:/# autogen --help
+Unhandled trap: 0x180
+pc=0xf64dd2de sr=0x00000000 pr=0xf63b9c74 fpscr=0x00080000
+spc=0x00000000 ssr=0x00000000 gbr=0xf61102a8 vbr=0x00000000
+sgr=0x00000000 dbr=0x00000000 delayed_pc=0xf64dd2a0 fpul=0x00000003
+r0=0xf6fc1320 r1=0x00000000 r2=0xffff5dc4 r3=0xf67bfb50
+r4=0xf6fc1230 r5=0xf6fc141c r6=0x000003ff r7=0x00000000
+r8=0x00000004 r9=0xf63e20bc r10=0xf6fc141c r11=0xf63e28f0
+r12=0xf63e2258 r13=0xf63eae1c r14=0x00000804 r15=0xf6fc1220
+r16=0x00000000 r17=0x00000000 r18=0x00000000 r19=0x00000000
+r20=0x00000000 r21=0x00000000 r22=0x00000000 r23=0x00000000
+(sid-sh4-sbuild)root@nofan:/#
+
+Bi-secting found this commit to be the culprit:
+
+61dedf2af79fb5866dc7a0f972093682f2185e17 is the first bad commit
+commit 61dedf2af79fb5866dc7a0f972093682f2185e17
+Author: Richard Henderson <email address hidden>
+Date:   Tue Jul 18 10:02:50 2017 -1000
+
+    target/sh4: Add missing FPSCR.PR == 0 checks
+    
+    Both frchg and fschg require PR == 0, otherwise undefined_operation.
+    
+    Reviewed-by: Aurelien Jarno <email address hidden>
+    Signed-off-by: Richard Henderson <email address hidden>
+    Message-Id: <email address hidden>
+    Signed-off-by: Aurelien Jarno <email address hidden>
+
+:040000 040000 980d79b69ae712f23a1e4c56983e97a843153b4a 1024c109f506c7ad57367c63bc8bbbc8a7a36cd7 M      target
+
+Reverting 61dedf2af79fb5866dc7a0f972093682f2185e17 fixes the problem for me.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1804678 b/results/classifier/gemma3:12b/kernel/1804678
new file mode 100644
index 00000000..01d404b9
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1804678
@@ -0,0 +1,56 @@
+
+qemu-3.1.0-rc0: mips emulation hangs when executing invalid instructions
+
+QEMU version:
+-------------
+
+qemu-3.1.0-rc0 compiled from sources (earlier versions also affected)
+
+Summary:
+--------
+
+QEMU MIPS system emulation hangs when trying to execute the following invalid instructions:
+
+71c5a9bf       sdbbp 0x716a6
+2c4745aa       sltiu a3, v0, 0x45aa
+f47539fb       sdc1 f21, 0x39fb(v1)
+5fa5e284       invalid
+
+qemu-system-mips falls under an infinite loop condition and it needs to be ended.
+
+The issue has been reproduced in Ubuntu x64 host running Debian MIPS 32-bits guest with the following command line:
+
+qemu-system-mips -M malta -kernel vmlinux-3.2.0-4-4kc-malta -hda debian_wheezy_mips_standard.qcow2 -append "root=/dev/sda1 console=tty0"
+
+It can also be reproduced using mips-linux-user, in which case throws the following exception:
+
+qemu-mips mips_loop_static.elf
+qemu: unhandled CPU exception 0x10 - aborting
+pc=0x004a9da0 HI=0x00000003 LO=0x00000002 ds 00e2 004a9da0 0
+GPR00: r0 00000000 at fffffff8 v0 004a9da0 v1 004ad000
+GPR04: a0 00000001 a1 7fffefc4 a2 7fffefcc a3 00000000
+GPR08: t0 004ab854 t1 0ffffffe t2 81010100 t3 2f2f2f2f
+GPR12: t4 7ffff1ad t5 004ab090 t6 004ab06c t7 004ab07c
+GPR16: s0 00000000 s1 452ac505 s2 00400db4 s3 00400d38
+GPR20: s4 00000000 s5 00000000 s6 00000000 s7 00000000
+GPR24: t8 004ab0a8 t9 004a9da0 k0 00000000 k1 00000000
+GPR28: gp 004b25a0 sp 7fffeec0 s8 7fffeec0 ra 0040041c
+CP0 Status  0x24000010 Cause   0x00000000 EPC    0x00000000
+    Config0 0x80008482 Config1 0x9e190c8f LLAddr 0xffffffffffffffff
+    Config2 0x80000000 Config3 0x00000000
+    Config4 0x00000000 Config5 0x00000000
+qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x602dbad8
+
+Testcase:
+---------
+
+C program to reproduce the problem:
+
+unsigned char code[] = "\x71\xC5\xA9\xBF\x2C\x47\x45\xAA\xF4\x75\x39\xFB\x5F\xA5\xE2\x84";
+main()
+{
+  int (*ret)() = (int(*)())code;
+  ret();
+}
+
+Also, find a statically compiled ELF attached.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1808 b/results/classifier/gemma3:12b/kernel/1808
new file mode 100644
index 00000000..9f4cce43
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1808
@@ -0,0 +1,72 @@
+
+qemu-system-i386: Crash in tcg_handle_interrupt on fpu_raise_exception call
+Description of problem:
+While I was messing with an old Linux system, QEMU crashed as I tried to run `make test` on a package:
+```
+ERROR:../accel/tcg/tcg-accel-ops.c:83:tcg_handle_interrupt: assertion failed: (qemu_mutex_iothread_locked())
+Bail out! ERROR:../accel/tcg/tcg-accel-ops.c:83:tcg_handle_interrupt: assertion failed: (qemu_mutex_iothread_locked())
+```
+Running QEMU straight from the master branch (c167c80) didn't help either. The backtrace is as follows:
+```
+(gdb) bt
+#0  0x00007ffff55ac26c in  () at /usr/lib/libc.so.6
+#1  0x00007ffff555ca08 in raise () at /usr/lib/libc.so.6
+#2  0x00007ffff5545538 in abort () at /usr/lib/libc.so.6
+#3  0x00007ffff6bae05e in g_assertion_message
+    (domain=domain@entry=0x0, file=file@entry=0x555555f90a98 "../accel/tcg/tcg-accel-ops.c", line=line@entry=83, func=func@entry=0x55555607a130 <__func__.3> "tcg_handle_interrupt", message=message@entry=0x7fff9c15ee10 "assertion failed: (qemu_mutex_iothread_locked())") at ../glib/glib/gtestutils.c:3450
+#4  0x00007ffff6c0ef40 in g_assertion_message_expr
+    (domain=domain@entry=0x0, file=file@entry=0x555555f90a98 "../accel/tcg/tcg-accel-ops.c", line=line@entry=83, func=func@entry=0x55555607a130 <__func__.3> "tcg_handle_interrupt", expr=expr@entry=0x555555f79cf8 "qemu_mutex_iothread_locked()") at ../glib/glib/gtestutils.c:3476
+#5  0x0000555555c97369 in tcg_handle_interrupt (cpu=0x555557434cb0, mask=2) at ../accel/tcg/tcg-accel-ops.c:83
+#6  tcg_handle_interrupt (cpu=0x555557434cb0, mask=2) at ../accel/tcg/tcg-accel-ops.c:81
+#7  0x0000555555b4d58b in pic_irq_request (opaque=<optimized out>, irq=<optimized out>, level=1) at ../hw/i386/x86.c:555
+#8  0x0000555555b4f218 in gsi_handler (opaque=0x5555579423d0, n=13, level=1) at ../hw/i386/x86.c:611
+#9  0x00007fffa42bde14 in code_gen_buffer ()
+#10 0x0000555555c724bb in cpu_tb_exec (cpu=cpu@entry=0x555557434cb0, itb=<optimized out>, tb_exit=tb_exit@entry=0x7fffe9bfd658) at ../accel/tcg/cpu-exec.c:457
+#11 0x0000555555c7298e in cpu_loop_exec_tb (tb_exit=0x7fffe9bfd658, last_tb=<synthetic pointer>, pc=3221283547, tb=<optimized out>, cpu=<optimized out>) at ../accel/tcg/cpu-exec.c:919
+#12 cpu_exec_loop (cpu=cpu@entry=0x555557434cb0, sc=sc@entry=0x7fffe9bfd6f0) at ../accel/tcg/cpu-exec.c:1040
+#13 0x0000555555c731dd in cpu_exec_setjmp (cpu=cpu@entry=0x555557434cb0, sc=sc@entry=0x7fffe9bfd6f0) at ../accel/tcg/cpu-exec.c:1057
+#14 0x0000555555c73810 in cpu_exec (cpu=cpu@entry=0x555557434cb0) at ../accel/tcg/cpu-exec.c:1083
+#15 0x0000555555c974ff in tcg_cpus_exec (cpu=cpu@entry=0x555557434cb0) at ../accel/tcg/tcg-accel-ops.c:75
+#16 0x0000555555c97657 in mttcg_cpu_thread_fn (arg=arg@entry=0x555557434cb0) at ../accel/tcg/tcg-accel-ops-mttcg.c:95
+#17 0x0000555555e283e8 in qemu_thread_start (args=0x5555574935f0) at ../util/qemu-thread-posix.c:541
+#18 0x00007ffff55aa44b in  () at /usr/lib/libc.so.6
+#19 0x00007ffff562de40 in  () at /usr/lib/libc.so.6
+```
+
+After further testing, it seems related to inftest.awk. However, the crash doesn't occur right after I run the file, but only when I do specific operations afterwards.
+
+With `-accel kvm`
+```
+> gawk -f test/inftest.awk
+(output trimmed)
+1e+305 1e+302
+1e+308 1e+305
+gawk: test/inftest.awk:3: fatal: floating point exception
+> echo Test # No crash
+Test
+> cat test/inftest.awk # No crash
+```
+
+With `-accel tcg`
+```
+> gawk -f test/inftest.awk
+(output trimmed)
+1e+308 1e+305
+Infinity 1e+308
+Infinity Infinity
+loop terminated
+> echo Test # No crash
+Test
+> cat test/inftest.awk # QEMU crash
+```
+Steps to reproduce:
+1. Start the VM
+2. Press any key except for enter to go through the SVGA prompt
+3. Enter `root` to login. No password is required
+4. Run `cd /usr/src2/gawk-2.14`
+5. Run `gawk -f test/inftest.awk`
+6. Run certain commands that interact with the kernel (ex. `ls`, `cat test/inftest.awk`, `whoami`)
+7. Observe the crash
+Additional information:
+[00000-bootFloppy.raw](/uploads/379f6b601132980af4ea721fe77dbae4/00000-bootFloppy.raw)
+[artifact.qcow2](/uploads/d721a35bc55e764e17087e8bc1a7531e/artifact.qcow2)
diff --git a/results/classifier/gemma3:12b/kernel/1811 b/results/classifier/gemma3:12b/kernel/1811
new file mode 100644
index 00000000..9252b50f
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1811
@@ -0,0 +1,37 @@
+
+ppc serial appears to have a maximum ratio of output to input, hides output and only writes it on subsequent input(?!)
+Description of problem:
+When pasting in large chunks of text, the echo is partial, but completes with subsequent writes (and is drained when the writes are small). Sorry this is really stupid, see video.
+
+(also, when booting, the console stops at
+```
+Building dt strings...
+Building dt structure...
+Device tree strings 0x00000000062c0000 -> 0x00000000062c0b90
+Device tree struct  0x00000000062d0000 -> 0x00000000062e0000
+Quiescing Open Firmware ...
+Booting Linux via __start() @ 0x0000000002000000 ...
+Linux ppc64le
+#1 SMP Debian 6.
+```
+and then continues with more messages from just after the dot:
+```
+Linux ppc64le
+#1 SMP Debian 6.[   15.683156] vio vio: uevent: failed to send synthetic uevent: -19
+vio: Failed to write 'add' to '/sys/devices/vio/uevent', ignoring: No such device
+/dev/vda2: clean, 17371/987360 files, 345018/3942144 blocks
+```
+)
+Steps to reproduce:
+1. `cat > /dev/null`
+2. paste in a couple solid lines
+3. observe that the echo completed mid-line
+4. paste in a couple more solid lines
+5. observe that the echo includes the end of the first few lines, and the start of the second set
+6. ^D
+7. observe that with every key input into the shell, you get a few bytes back, and those bytes are the tail-end of the second set of lines
+8. when the echo buffer is drained, it's drained
+Additional information:
+Demo video: https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1041707;filename=2023-07-21+17-59-25.mp4;msg=5
+
+Downstream bug: https://bugs.debian.org/1041707
diff --git a/results/classifier/gemma3:12b/kernel/1811244 b/results/classifier/gemma3:12b/kernel/1811244
new file mode 100644
index 00000000..1af7d965
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1811244
@@ -0,0 +1,41 @@
+
+qemu 3.1/i386 crashes/guest hangs when MTTCG is enabled
+
+When MTTCG is enabled, QEMU 3.1.0 sometimes crashes when running the following command line:
+
+qemu-system-i386 -kernel /home/jermar/Kernkonzept/software/l4/.build-i386/bin/x86_gen/bootstrap -append bootstrap -initrd "/home/jermar/work/software/l4/fiasco/.build-i386/fiasco -serial_esc,/home/jermar/Kernkonzept/software/l4/.build-i386/bin/x86_gen/l4f/sigma0 ,/home/jermar/Kernkonzept/software/l4/.build-i386/bin/x86_gen/l4f/moe rom/ahci.cfg,/home/jermar/Kernkonzept/software/l4/.build-i386/bin/x86_gen/l4f/ned ,test_env.lua ,/home/jermar/Kernkonzept/software/l4/pkg/ahci-driver/examples/md5sum/ahci.cfg ,/home/jermar/Kernkonzept/software/l4/.build-i386/bin/x86_gen/l4f/l4re ,/home/jermar/Kernkonzept/software/l4/pkg/ahci-driver/examples/md5sum/ahci.io ,/home/jermar/Kernkonzept/software/l4/.build-i386/bin/x86_gen/l4f/io ,/home/jermar/Kernkonzept/software/l4/.build-i386/bin/x86_gen/l4f/ahci-drv ,/home/jermar/Kernkonzept/software/l4/.build-i386/bin/x86_gen/l4f/ahci-md5-sync" -smp 4 -accel tcg,thread=multi -device ahci,id=ahci0 -drive if=none,file=/home/jermar/Kernkonzept/software/l4/.build-i386/pkg/ahci-driver/test/examples/test_ahci.img,format=raw,id=drive-sata0-0-0 -device ide-drive,bus=ahci0.0,drive=drive-sata0-0-0,id=sata0-0-0 -serial stdio -nographic -monitor none
+
+The host is x86_64.
+
+The stack at the time of the crash (core dump and debug binary linked below[1]):
+
+Core was generated by `qemu-system-i386 -kernel /home/jermar/Kernkonzept/software/l4/.build-i386/bin/x'.
+Program terminated with signal SIGSEGV, Segmentation fault.
+#0  io_writex (env=env@entry=0x565355ca0140, iotlbentry=iotlbentry@entry=0x565355ca9120, mmu_idx=2, val=val@entry=0, addr=addr@entry=3938451632, retaddr=retaddr@entry=140487132809203, recheck=false, size=4)
+    at /home/jermar/software/HelenOS/helenos.git/contrib/qemu/qemu-3.1.0/accel/tcg/cputlb.c:791
+791	    if (mr->global_locking && !qemu_mutex_iothread_locked()) {
+[Current thread is 1 (Thread 0x7fc5af7fe700 (LWP 3625719))]
+Missing separate debuginfos, use: dnf debuginfo-install SDL2-2.0.9-1.fc29.x86_64 at-spi2-atk-2.30.0-1.fc29.x86_64 at-spi2-core-2.30.0-2.fc29.x86_64 atk-2.30.0-1.fc29.x86_64 bzip2-libs-1.0.6-28.fc29.x86_64 cairo4
+(gdb) bt
+#0  0x0000565354f5f365 in io_writex
+    (env=env@entry=0x565355ca0140, iotlbentry=iotlbentry@entry=0x565355ca9120, mmu_idx=2, val=val@entry=0, addr=addr@entry=3938451632, retaddr=retaddr@entry=140487132809203, recheck=false, size=4)
+    at /home/jermar/software/HelenOS/helenos.git/contrib/qemu/qemu-3.1.0/accel/tcg/cputlb.c:791
+#1  0x0000565354f621b2 in io_writel (recheck=<optimized out>, retaddr=140487132809203, addr=3938451632, val=0, index=0, mmu_idx=2, env=0x565355ca0140)
+    at /home/jermar/software/HelenOS/helenos.git/contrib/qemu/qemu-3.1.0/accel/tcg/softmmu_template.h:310
+#2  0x0000565354f621b2 in helper_le_stl_mmu (env=0x565355ca0140, addr=<optimized out>, val=0, oi=34, retaddr=140487132809203)
+    at /home/jermar/software/HelenOS/helenos.git/contrib/qemu/qemu-3.1.0/accel/tcg/softmmu_template.h:310
+#3  0x00007fc5b5a587f3 in code_gen_buffer ()
+#4  0x0000565354f75fd0 in cpu_tb_exec (itb=<optimized out>, cpu=0x7fc5b5a5aa40 <code_gen_buffer+12266006>) at /home/jermar/software/HelenOS/helenos.git/contrib/qemu/qemu-3.1.0/accel/tcg/cpu-exec.c:171
+#5  0x0000565354f75fd0 in cpu_loop_exec_tb (tb_exit=<synthetic pointer>, last_tb=<synthetic pointer>, tb=<optimized out>, cpu=0x7fc5b5a5aa40 <code_gen_buffer+12266006>)
+    at /home/jermar/software/HelenOS/helenos.git/contrib/qemu/qemu-3.1.0/accel/tcg/cpu-exec.c:615
+#6  0x0000565354f75fd0 in cpu_exec (cpu=cpu@entry=0x565355c97e90) at /home/jermar/software/HelenOS/helenos.git/contrib/qemu/qemu-3.1.0/accel/tcg/cpu-exec.c:725
+#7  0x0000565354f33b1f in tcg_cpu_exec (cpu=0x565355c97e90) at /home/jermar/software/HelenOS/helenos.git/contrib/qemu/qemu-3.1.0/cpus.c:1429
+#8  0x0000565354f35e83 in qemu_tcg_cpu_thread_fn (arg=0x565355c97e90) at /home/jermar/software/HelenOS/helenos.git/contrib/qemu/qemu-3.1.0/cpus.c:1733
+#9  0x0000565354f35e83 in qemu_tcg_cpu_thread_fn (arg=arg@entry=0x565355c97e90) at /home/jermar/software/HelenOS/helenos.git/contrib/qemu/qemu-3.1.0/cpus.c:1707
+#10 0x00005653552ec5da in qemu_thread_start (args=<optimized out>) at util/qemu-thread-posix.c:498
+#11 0x00007fc5b858a58e in start_thread () at /lib64/libpthread.so.0
+#12 0x00007fc5b84b96a3 in clone () at /lib64/libc.so.6
+
+Another symptom that occurs more often than this crash is that the guest hangs while waiting for another CPU to complete a cross-CPU call. Disabling MTTCG makes both symptoms go away.
+
+[1] Core file + debug binary: http://jermar.eu/ref/qemu-mttcg-core.tar.xz
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1813045 b/results/classifier/gemma3:12b/kernel/1813045
new file mode 100644
index 00000000..b265cdc5
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1813045
@@ -0,0 +1,17 @@
+
+qemu-ga fsfreeze crashes the kernel
+
+We use mainly Cloudlinux, Debian and Centos.
+We experienced many crashes on our qemu instances based on Cloudlinux during a snapshot.
+The issue is not related to CloudLinux directly, but to Qemu agent, which does not freeze the file system(s) correctly. What is actually happening:
+
+When VM backup is invoked, Qemu agent freezes the file systems, so no single change will be made during the backup. But Qemu agent does not respect the loop* devices in freezing order (we have checked its sources), which leads to the next situation: 
+1) freeze loopback fs
+              ---> send async reqs to loopback thread
+2) freeze main fs
+3) loopback thread wakes up and trying to write data to the main fs, which is still frozen, and this finally leads to the hung task and kernel crash. 
+
+I believe this is the culprit: 
+
+/dev/loop0 /tmp ext3 rw,nosuid,noexec,relatime,data=ordered 0 0
+/dev/loop0 /var/tmp ext3 rw,nosuid,noexec,relatime,data=ordered 0 0
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1813201 b/results/classifier/gemma3:12b/kernel/1813201
new file mode 100644
index 00000000..41ad6d1b
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1813201
@@ -0,0 +1,56 @@
+
+QEMU TCG i386 / x86_64 system emulation crash when executing int instruction
+
+QEMU version:
+-------------
+
+qemu from git, master branch commit d058a37a6e8daa8d71a6f2b613eb415b69363755
+
+Release versions are also affected.
+
+Summary:
+--------
+
+QEMU i386 and x86_64 system emulation crash when executing the following "int" instruction:
+
+cd08  int 8
+
+This generates a kernel NULL pointer dereference error in Linux, and a BSOD error in Windows.
+
+No special permissions are required to execute the instruction, any unprivileged user can execute it.
+
+This issue has been reproduced in QEMU running in TCG mode. KVM is not affected.
+
+Kernel panic log:
+
+[  111.091138] BUG: unable to handle kernel NULL pointer dereference at 00000014
+[  111.092145] IP: [<ce0513ad>] doublefault_fn+0xd/0x130
+[  111.092145] *pdpt = 0000000000000000 *pde = f000ff53f000ff53 [  111.092145] 
+[  111.092145] Oops: 0000 [#1] SMP
+[  111.092145] Modules linked in: kvm_amd bochs_drm ppdev ttm drm_kms_helper drm kvm irqbypass evdev pcspkr serio_raw sg parport_pc parport button ip_tables x_tables autofs4 ext4 crc16 jbd2 crc32c_generic fscrypto ecb xts lrw gf128mul ablk_helper cryptd aes_i586 mbcache sr_mod sd_mod cdrom ata_generic ata_piix libata psmouse e1000 scsi_mod i2c_piix4 floppy
+[  111.092145] CPU: 0 PID: 409 Comm: int8.elf Not tainted 4.9.0-8-686-pae #1 Debian 4.9.130-2
+[  111.092145] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org 04/01/2014
+[  111.092145] task: f6c88a80 task.stack: f6e52000
+[  111.092145] EIP: 0060:[<ce0513ad>] EFLAGS: 00004086 CPU: 0
+[  111.092145] EIP is at doublefault_fn+0xd/0x130
+[  111.092145] EAX: 00000000 EBX: 00000000 ECX: 00000000 EDX: 00000000
+[  111.092145] ESI: 00000000 EDI: 00000000 EBP: ce8f13fc ESP: ce8f13d4
+[  111.092145]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
+[  111.092145] CR0: 8005003b CR2: 00000014 CR3: 0e8e1000 CR4: 000006f0
+[  111.092145] Stack:
+[  111.092145]  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
+[  111.092145]  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
+[  111.092145]  00000000 00000000 00000000 00000000 fed00000 ce474ad0 00000000 00017d78
+[  111.092145] Call Trace:
+[  111.092145] Code: 86 fd ff eb a3 89 f6 8d bc 27 00 00 00 00 55 89 e5 3e 8d 74 26 00 5d e9 e2 79 fd ff 66 90 55 89 e5 56 53 83 ec 20 3e 8d 74 26 00 <65> a1 14 00 00 00 89 45 f4 31 c0 31 c0 c7 45 f0 00 00 00 00 66
+[  111.092145] EIP: [<ce0513ad>] [  111.092145] doublefault_fn+0xd/0x130
+[  111.092145]  SS:ESP 0068:ce8f13d4
+[  111.092145] CR2: 0000000000000014
+[  111.092145] ---[ end trace 8afa7884b76cafc1 ]---
+
+Testcase:
+---------
+
+void main() {
+        asm("int $0x8");
+}
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1813398 b/results/classifier/gemma3:12b/kernel/1813398
new file mode 100644
index 00000000..8398fedc
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1813398
@@ -0,0 +1,42 @@
+
+qemu user calls malloc after fork in multi-threaded process
+
+qemu user may hang in malloc on a musl based system because
+it calls malloc after fork (in a pthread_atfork handler)
+in the child process.
+
+this is undefined behaviour since the parent process is
+multi-threaded and only as-safe functions may be called
+in the child then. (if malloc/free is called concurrently
+with fork the malloc state will be corrupted in the child,
+it works on glibc because glibc takes the malloc locks
+before the fork syscall, but that breaks the as-safety of
+fork and thus non-conforming to posix)
+
+discussed at
+https://www.openwall.com/lists/musl/2019/01/26/1
+
+the bug is hard to reproduce (requires the call_rcu thread
+to call free concurrently with do_fork in the main thread),
+this one is observed with qemu-arm 3.1.0 running on x86_64
+executing an arm busybox sh:
+
+(gdb) bt
+#0  malloc (n=<optimized out>, n@entry=9) at src/malloc/malloc.c:306
+#1  0x0000000060184ad3 in g_malloc (n_bytes=n_bytes@entry=9) at gmem.c:99
+#2  0x000000006018bcab in g_strdup (str=<optimized out>, str@entry=0x60200abf "call_rcu") at gstrfuncs.c:363
+#3  0x000000006016e31d in qemu_thread_create (thread=thread@entry=0x7ffe367d1870, name=name@entry=0x60200abf "call_rcu", 
+    start_routine=start_routine@entry=0x60174c00 <call_rcu_thread>, arg=arg@entry=0x0, mode=mode@entry=1)
+    at /home/pmos/build/src/qemu-3.1.0/util/qemu-thread-posix.c:526
+#4  0x0000000060174b99 in rcu_init_complete () at /home/pmos/build/src/qemu-3.1.0/util/rcu.c:327
+#5  0x00000000601c4fac in __fork_handler (who=1) at src/thread/pthread_atfork.c:26
+#6  0x00000000601be8db in fork () at src/process/fork.c:33
+#7  0x000000006009d191 in do_fork (env=0x627aaed0, flags=flags@entry=17, newsp=newsp@entry=0, parent_tidptr=parent_tidptr@entry=0, 
+    newtls=newtls@entry=0, child_tidptr=child_tidptr@entry=0) at /home/pmos/build/src/qemu-3.1.0/linux-user/syscall.c:5528
+#8  0x00000000600af894 in do_syscall1 (cpu_env=cpu_env@entry=0x627aaed0, num=num@entry=2, arg1=arg1@entry=0, arg2=arg2@entry=-8700192, 
+    arg3=<optimized out>, arg4=8, arg5=1015744, arg6=-74144, arg7=0, arg8=0) at /home/pmos/build/src/qemu-3.1.0/linux-user/syscall.c:7042
+#9  0x00000000600a835c in do_syscall (cpu_env=cpu_env@entry=0x627aaed0, num=2, arg1=0, arg2=-8700192, arg3=<optimized out>, 
+    arg4=<optimized out>, arg5=1015744, arg6=-74144, arg7=0, arg8=0) at /home/pmos/build/src/qemu-3.1.0/linux-user/syscall.c:11533
+#10 0x00000000600c265f in cpu_loop (env=env@entry=0x627aaed0) at /home/pmos/build/src/qemu-3.1.0/linux-user/arm/cpu_loop.c:360
+#11 0x00000000600417a2 in main (argc=<optimized out>, argv=0x7ffe367d57b8, envp=<optimized out>)
+    at /home/pmos/build/src/qemu-3.1.0/linux-user/main.c:819
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1824344 b/results/classifier/gemma3:12b/kernel/1824344
new file mode 100644
index 00000000..438a32dd
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1824344
@@ -0,0 +1,46 @@
+
+x86: retf or iret pagefault sets wrong error code
+
+With a x86_64 or i386 guest, non-KVM, when trying to execute a
+"iret/iretq/retf" instruction in userspace with invalid stack pointer
+(under a protected mode OS, like Linux), wrong bits are set in the
+pushed error code; bit 2 is not set, indicating the error comes from
+kernel space.
+
+If the guest OS is using this flag to decide whether this was a kernel
+or user page fault, it will mistakenly decide a kernel has irrecoverably
+faulted, possibly causing guest OS panic.
+
+
+How to reproduce the problem a guest (non-KVM) Linux:
+Note, on recent Linux kernel version, this needs a CPU with SMAP support
+(eg. -cpu max)
+
+$ cat tst.c
+int main()
+{
+__asm__ volatile (
+"mov $0,%esp\n"
+"retf"
+);
+return 0;
+}
+
+$ gcc tst.c
+$ ./a.out
+Killed
+
+
+"dmesg" shows the kernel has in fact triggered a "BUG: unable to handle
+kernel NULL pointer dereference...", but it has "recovered" by killing
+the faulting process (see attached screenshot).
+
+
+Using self-compiled qemu from git:
+commit 532cc6da74ec25b5ba6893b5757c977d54582949 (HEAD -> master, tag: v4.0.0-rc3, origin/master, origin/HEAD)
+Author: Peter Maydell <email address hidden>
+Date:   Wed Apr 10 15:38:59 2019 +0100
+
+    Update version for v4.0.0-rc3 release
+    
+    Signed-off-by: Peter Maydell <email address hidden>
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1824768 b/results/classifier/gemma3:12b/kernel/1824768
new file mode 100644
index 00000000..e4129af2
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1824768
@@ -0,0 +1,29 @@
+
+Qemu ARMv7 TCG MultiThreading for i386 guest doesn't work
+
+Using any Linux image (in this case Alpine Linux iso) and want to use all cores of my Raspberry with --accel,thread=multi. I know there is a probably still problem with memory ordering of the host but I have also seen some very old commits which could potentially help with it.
+
+But anyway, with version qemu-i386 version 3.1.0 (Debian 1:3.1+dfsg-7)
+I can see OpenRC starting up services and then the kernel crash.
+
+With version QEMU emulator version 3.1.93 (v4.0.0-rc3-dirty)
+The whole machine crash with this error: 
+Illegal instruction
+
+
+Using command:
+./qemu-system-i386 -cdrom alpine.iso --accel tcg,thread=multi
+
+Full Console Output:
+qemu-system-i386: warning: Guest expects a stronger memory ordering than the host provides
+This may cause strange/hard to debug errors
+Illegal instruction
+
+
+Kernel:
+Linux raspberrypi 4.14.98-v7+ #1200 SMP Tue Feb 12 20:27:48 GMT 2019 armv7l GNU/Linux
+
+CPU:
+ARMv7 Processor rev 5 (v7l)
+Features: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm 
+4 cores
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1824778 b/results/classifier/gemma3:12b/kernel/1824778
new file mode 100644
index 00000000..aa50d5d8
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1824778
@@ -0,0 +1,9 @@
+
+PowerPC64: tlbivax does not work for addresses above 4G
+
+The tlbivax instruction in QEMU does not work for address above 4G. The reason behind this is a simple 32bit trunction of an address.
+Changing the argument ea from uint32_t to target_ulong for the function booke206_invalidate_ea_tlb() in target/ppc/mmu_helper.c solves the issue.
+
+I did not reproduce this using Linux so I have no public example for reproducing it. However it's a pretty straight forward change.
+
+Issue can be seen in all version of QEMU.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1826 b/results/classifier/gemma3:12b/kernel/1826
new file mode 100644
index 00000000..dac49f63
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1826
@@ -0,0 +1,30 @@
+
+Segfault in memory_region_dispatch_write()
+Description of problem:
+Several possible outcomes
+- Kernel freeze and rcu lockup messages.
+- segfault
+ 
+For segfault, using gdb.
+```
+in memory_region_dispatch_write (mr=mr@entry=0x130013001300013, addr=addr@entry=176, data=dat@entry=0, op=op@entry=M0_42, attrs=...) at ../../softwmmu/memory.c:1515
+1515     if (mr->alias) {
+
+in memory_region_dispatch_write(  .. as above...)
+in io_writex(env=env@entry=0x555556a84320, full=full@entry=0x7ffda010f630, mmu_idx=mmu_idx@entry=0, val=0, addr=addr@entry=18446744073699049648, retaddr=retaddr@entry=140736023420498, op=MO_32) at ../../accel/tcg/cputlb.c:1448
+in do_st_mmio_leN (env=env@entry=0x555556a84320, full=full@entry=0x7ffda010f630, val_le=<optmized out>, val_le@entry=0, addr=addr@entry=18446744073699049648, size=size@entry=4, mmu_idx=mmu_idx@entry=0, ra=140736023420498) at ../../accel/tcg/cputlb.c:2755
+in do_st_4 (ra=<optmized_out>, memop=<optimized out> mmu_idx=0, val=0, p=0x7ffff529c140, env=0x555556a84320) at ../../accel/tcg/cputbl.c:2921
+do_st4_mmu (env=0x555556a84320, addr=<optimized out> val=<optmized out>, oi=<otpmized out> ra=140736023420498) at ../../accel/tcg/cputlb.c:3006
+in code_gen_buffer()
+in cpu_tb_exec(..) //getting lazy on typing as seems unlikely anything useful beyond here.
+in cpu_loop_exec_tb()
+cpu_exec_loop
+in cpu_exec_setjmp()
+in cpu_exec()
+in tcg_cpus_exec()
+```
+Steps to reproduce:
+1. Boot.
+2. Use gdb to grab back trace after segfault.
+Additional information:
+Seems to segfault mid way through PCI enumeration in the kernel.  Which device seems to vary between runs.
diff --git a/results/classifier/gemma3:12b/kernel/1828429 b/results/classifier/gemma3:12b/kernel/1828429
new file mode 100644
index 00000000..3a936ee0
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1828429
@@ -0,0 +1,16 @@
+
+qemu-system-aarch64 crashes with assertion failed while running GCC 9 test suite
+
+I am using QEMU 4.0.0 on an x86_64 Linux 4.19.0 host, the guest is an Aarch64 linux 5.0.0 system. The same issue occurred on QEMU 3.1.0.
+
+While running the GCC 9.1 test suite on the guest system, QEMU crashes with:
+
+qemu-system-aarch64: [...]/qemu-4.0.0/tcg/tcg.c:3952: tcg_gen_code: Assertion `s->gen_insn_end_off[num_insns] == off' failed.
+
+I am able to reproduce the issue reliably, which is encouraging. The full QEMU command line is:
+
+qemu-system-aarch64 -kernel kernel-5.0.0cbl1 -append "root=/dev/vda1 ro init=/sbin/init console=ttyAMA0" -name guest=cbl -drive file=cbl.qcow2,index=0,media=disk,format=qcow2 -drive file=swap.qcow2,index=1,media=disk,format=qcow2 -machine virt -cpu cortex-a57 -smp 4,sockets=1,cores=2,threads=2 -m size=8192 -netdev tap,id=network0,ifname=tapcbl2,script=no,downscript=no -device virtio-net-device,netdev=network0,mac=aa:bb:cc:dd:ee:02 -nographic
+
+The specific GCC test that causes QEMU to crash is vldX.c run from advsimd-intrinsics.exp; I can reproduce via "make check-gcc RUNTESTFLAGS=advsimd-intrinsics.exp=vldX.c"
+
+If there is anything I can do to further triage the issue, or gain more insight into what is going on, please let me know! I am eager to help however I can.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1829459 b/results/classifier/gemma3:12b/kernel/1829459
new file mode 100644
index 00000000..9c46fd31
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1829459
@@ -0,0 +1,36 @@
+
+qemu seems to lack support for pid namespace.
+
+# Version
+
+qemu-4.0.0
+
+# commands used to launch qemu-aarch64 in user mode.
+
+printf '%s\n' ':qemu-aarch64:M::\x7fELF\x02\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\xb7\x00:\xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff:/usr/bin/qemu-aarch64:'"${QEMU_BINFMT_FLAGS}" >/proc/sys/fs/binfmt_misc/register
+
+> sudo cp /usr/bin/qemu-aarch64 $RPI/usr/bin
+> sudo chroot $RPI /bin/ksh -l
+
+# host
+
+Gentoo Linux amd64
+
+# Guest
+
+Gentoo Linux aarch64
+
+# The problem that I have
+
+"emerge" program fails due to the error, "qemu: qemu_thread_create: Invalid argument".
+"emerge" is Gentoo's package manager that compiles and installs packages.
+
+# How to reproduce the issue
+
+Execute
+
+unshare --pid -- echo hello world
+
+or
+
+python -c "import portage.process; portage.process.spawn(['echo', 'hello', 'world'], unshare_pid=True)"
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1829498 b/results/classifier/gemma3:12b/kernel/1829498
new file mode 100644
index 00000000..579d9214
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1829498
@@ -0,0 +1,18 @@
+
+window 8 stuck during boot on Qemu 
+
+Description of problem:
+I've got windows 8 image(64 bit), installed on Qemu(x86-64_softmmu) and then i'm trying to boot/shutdown it in the same Qemu configuration. Windows 8 has feature - when you click "Shutdown" in UI, windows 8 doesn't actually power off, it goes to "Suspend to disc" ACPI state. After shutdown, i'm trying to boot it again, but it stucks during boot.
+
+I've discovered, that it hangs when windows 8 writes to AHCI's command register, AHCI triggers irq, but windows 8 sends EOI, don't accessing AHCI register,so irq line stills in high state, and irq will be injected again and again, while windows will send EOI on each AHCI interrupt. Strange thing is that it happens only on TCG mode or 
+with option "kernel-irqchip=off/split", with "kernel-irqchip=on" everything works ok(windows 8 accesses AHCI register and line goes to low state).
+
+Version-Release number of selected component (if applicable):
+Qemu revision: d8276573da58e8ce78dab8c46dd660efd664bcb7
+
+
+Steps to Reproduce:
+1. Install Windows 8 on QEMU(qemu command line: "-enable-kvm -m 1G -hda <image>  -serial stdio  -cpu core2duo -machine q35,kernel-irqchip=off"
+2. Click shutdown in UI.
+3. Try to boot again(it will stuck)
+4. Kill Qemu and boot again, it will boot, now go to 2) :)
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1830031 b/results/classifier/gemma3:12b/kernel/1830031
new file mode 100644
index 00000000..d4a79bb8
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1830031
@@ -0,0 +1,82 @@
+
+fatal error: float32nan on QEmu 3.1
+
+Docker throws float32nan errors when running alpine container on a CentOS 7.6 ppc64le Distro VM, when using Fedora 30 Host qemu 3.1. I Compiled qemu 2.11.2 on the Fedora 30 and using this qemu-system-ppc64 we don't see the error. Even using qemu 3.1 and machine 2.11 we still get the same issue. 
+
+Nothing changed on the OS level on the two runs. just the qemu-system-ppc64 used to run the virtual machine. 
+
+ Docker on CentOS 7: docker.ppc64le 2:1.13.1-96
+
+Running with qemu 2.11.2 behavior and machine 2.11:
+[root@machine ~]# /usr/local/bin/qemu-system-ppc64 -version
+QEMU emulator version 2.11.2(qemu-2.11.2-5.fc30)
+Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers
+
+[root@powericp ~]# docker run -i -t alpine /bin/sh
+/ # exit
+[root@powericp ~]# uname -a
+Linux powericp 3.10.0-957.12.2.el7.ppc64le #1 SMP Tue May 14 22:24:22 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux
+[root@powericp ~]# docker version
+Client:
+ Version:         1.13.1
+ API version:     1.26
+ Package version: docker-1.13.1-96.gitb2f74b2.el7.centos.ppc64le
+ Go version:      go1.10.3
+ Git commit:      b2f74b2/1.13.1
+ Built:           Wed May  1 15:05:41 2019
+ OS/Arch:         linux/ppc64le
+…
+[root@powericp ~]# lscpu
+Architecture:          ppc64le
+Byte Order:            Little Endian
+CPU(s):                16
+On-line CPU(s) list:   0-15
+Thread(s) per core:    1
+Core(s) per socket:    1
+Socket(s):             16
+NUMA node(s):          1
+Model:                 2.0 (pvr 004e 1200)
+Model name:            POWER8 (architected), altivec supported
+Hypervisor vendor:     KVM
+Virtualization type:   para
+L1d cache:             32K
+L1i cache:             32K
+NUMA node0 CPU(s):     0-15
+#################################################################################################
+#Running with qemu3.1
+#################################################################################################
+[root@machine ~]# qemu-system-ppc64 -version
+QEMU emulator version 3.1.0 (qemu-3.1.0-8.fc30)
+Copyright (c) 2003-2018 Fabrice Bellard and the QEMU Project developers
+[root@powericp ~]# docker run -i -t alpine /bin/sh
+/usr/bin/docker-current: Error response from daemon: oci runtime error: error running hook: exit status 4, stdout: , stderr: fatal error: float32nan
+runtime: panic before malloc heap initialized
+
+runtime stack:
+fatal error: gentraceback before goexitPC initialization
+runtime: panic before malloc heap initialized
+panic during panic
+
+runtime stack:
+fatal error: gentraceback before goexitPC initialization
+runtime: panic before malloc heap initialized
+stack trace unavailable.
+[root@powericp ~]# lscpu
+Architecture:          ppc64le
+Byte Order:            Little Endian
+CPU(s):                16
+On-line CPU(s) list:   0-15
+Thread(s) per core:    1
+Core(s) per socket:    1
+Socket(s):             16
+NUMA node(s):          1
+Model:                 2.0 (pvr 004e 1200)
+Model name:            POWER8 (architected), altivec supported
+Hypervisor vendor:     KVM
+Virtualization type:   para
+L1d cache:             32K
+L1i cache:             32K
+NUMA node0 CPU(s):     0-15
+
+
+strace attached.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1831545 b/results/classifier/gemma3:12b/kernel/1831545
new file mode 100644
index 00000000..1dfada3e
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1831545
@@ -0,0 +1,22 @@
+
+"accel/tcg: demacro cputlb" break qemu-system-x86_64 on 32-bit x86 host
+
+As described in https://lists.gnu.org/archive/html/qemu-devel//2019-05/msg07362.html I run into TCG regression in qemu-git.
+
+Unfortunately, fix from bug https://bugs.launchpad.net/qemu/+bug/1830872 seems to be nonn-effective for my case.
+
+For reproduction (on 32-bit x86 host, in my case Slackware with gcc 5.5.0):
+
+./configure --target-list=x86_64-softmmu --disable-werror --enable-debug-tcg
+
+make (-j5 in my case)
+
+try to boot any 64-bit kernel:
+
+x86_64-softmmu/qemu-system-x86_64 -kernel /boot/bzImage-4.12.0-x64 -accel tcg
+
+result is - qemu appear to hang right after "Booting the kernel" line. Decompression (xz) was ok.
+
+Tested with qemu-git commit  e2a58ff493a2e00db3e963c1839c5374500110f2 
+
+32-bit OS can be booted fine, and -enable-kvm also allow 64 bit kernel/os to boot.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1833661 b/results/classifier/gemma3:12b/kernel/1833661
new file mode 100644
index 00000000..cd583dcd
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1833661
@@ -0,0 +1,20 @@
+
+Linux kernel oops on Malta board while accessing pflash
+
+commit 33d609990621dea6c7d056c86f707b8811320ac1
+
+While running tests/acceptance/linux_ssh_mips_malta.py, the big-endian tests fail:
+
+  physmap-flash.0: Found 1 x32 devices at 0x0 in 32-bit bank. Manufacturer ID 0x000000 Chip ID 0x000000
+  Intel/Sharp Extended Query Table at 0x0031
+  Using buffer write method
+  Searching for RedBoot partition table in physmap-flash.0 at offset 0x1003f0000
+  Creating 3 MTD partitions on "physmap-flash.0":
+  0x000000000000-0x000000100000 : "YAMON"
+  0x000000100000-0x0000003e0000 : "User FS"
+  0x0000003e0000-0x000000400000 : "Board Config"
+  CPU 0 Unable to handle kernel paging request at virtual address 00000014
+
+The 64-bit test fails with:
+
+  CPU 0 Unable to handle kernel paging request at virtual address 0000000000000028
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1837347 b/results/classifier/gemma3:12b/kernel/1837347
new file mode 100644
index 00000000..37e9aadd
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1837347
@@ -0,0 +1,35 @@
+
+guest userspace process core dump after raspi2 kernel boot
+
+Host info:
+==========
+x86-64, Ubuntu 18.04, QEMU 4.0.0 (downloaded tarball from main site)
+
+Guest info:
+===========
+ARM7l, Raspbian OS off the main raspberry pi site
+
+QEMU command:
+=============
+qemu-system-arm -M raspi2 -kernel bootpart/kernel7.img -dtb bootpart/bcm2709-rpi-2-b.dtb -drive file=2019-07-10-raspbian-buster.img,format=raw,if=sd -append "rw earlyprintk console=ttyAMA0,115200 fsck.repair=yes rootwait memtest=1 loglevel=8 dwc_otg.lpm_enable=0 root=/dev/mmcblk0p2" -serial stdio
+
+kernel7.img and bcm2709-rpi-2-b.dtb were obtained by the following commands:
+
+guestfish --ro -a 2019-07-10-raspbian-buster.img -m /dev/sda1
+><fs> copy-out / bootpart/
+><fs> quit
+
+Output:
+=======
+
+https://pastebin.com/fL1eXhV0
+
+References:
+===========
+https://translatedcode.wordpress.com/2016/11/03/installing-debian-on-qemus-32-bit-arm-virt-board/
+https://translatedcode.wordpress.com/2018/04/25/debian-on-qemus-raspberry-pi-3-model/
+
+
+The core dump error can occur at both times, before logging in and after logging in, in this case I have given the output after logging in to show the initial processes running.
+
+Also please let me know if I using any kernel flags incorrectly
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1838 b/results/classifier/gemma3:12b/kernel/1838
new file mode 100644
index 00000000..6fbe1081
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1838
@@ -0,0 +1,2 @@
+
+Win9x on qemu 8.0.3 - Impossible to launch a win32 app
diff --git a/results/classifier/gemma3:12b/kernel/1839807 b/results/classifier/gemma3:12b/kernel/1839807
new file mode 100644
index 00000000..70fe83c6
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1839807
@@ -0,0 +1,49 @@
+
+Snapshots freeze guest Sabrelite IMX.6 board
+
+Hello,
+
+I'm trying to take and restore  a snapshot with the whole system state of the Sabrelite IMX.6 board running on QEMU with commands savevm/loadvm.
+It seems that I am able to take a snapshot but loading the snapshot fails.
+
+For comparison I checked out snapshots on 32bit ARM Virt with Debian as well as on the Versatilepb board with a bare metal application and it works fine.
+The problem occurs only with that one particular board.
+
+My environment is:
+Ubuntu 18.04
+QEMU 3.0.1 (I see the same issue in QEMU 4.0.0 as well)
+The kernel and device tree used for the board was 5.1.14 version from kernel.org
+
+The file system was build from imx_v6_v7_defconfig config in buildroot as and sd card image.
+
+Problem:
+
+Loading snapshot stops the whole machine and it's impossible to resume it.
+
+Steps to reproduce problem:
+
+1.      I converted the sdcard.img built from the buildroot to qcow2 using command qemu-img convert -f raw -O qcow2 sdcard.img sdcard.qcow2, since the raw doesn't support snapshots.
+
+2.      I start QEMU with a command
+./arm-softmmu/qemu-system-arm -m 512 -M sabrelite -kernel zImage -append "rootfstype=ext4 root=/dev/mmcblk2p2 rw rootwait" -rtc base=localtime,clock=vm -dtb imx6dl-sabresd.dtb -drive file=sdcard.qcow2,index=2,format=qcow2,id=mycard -device sd-card,drive=mycard -nographic -net nic -net user
+
+3.      I run a simple program which print characters to the console in the background and add some files in user directory, to differ from original image.
+
+4.      I switch to QEMU monitor, and type “savevm <name>”.
+When I type “info snapshots”, the snapshot is listed.
+So I assume it was saved correctly.
+
+5.      Then I switch back to Linux console from monitor, remove the added files and stop the background printing process.
+
+6.      I switch back to monitor and I'm trying now to load the snapshot by “loadvm <name>” command. 
+
+That’s where the problem occurs. QEMU stops and I can't switch back from monitor to Linux.
+Typing “cont” doesn’t help.
+It seems like the simulation has freezed. CPU usage on my Laptop machine equals 100% until I exit QEMU.
+
+
+What’s interesting when I exit the QEMU and then start it again the Linux boots and after it reaches the command prompt I can see the files which were removed after saving the snapshot.
+
+It looks like loading the snapshots works for restoring disk space but it fails for restoring the running processes.
+
+Due to the answer on QEMU mailing list (https://lists.nongnu.org/archive/html/qemu-discuss/2019-08/msg00016.html) it is QEMUs bug.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1840777 b/results/classifier/gemma3:12b/kernel/1840777
new file mode 100644
index 00000000..bebc1249
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1840777
@@ -0,0 +1,58 @@
+
+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
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1840920 b/results/classifier/gemma3:12b/kernel/1840920
new file mode 100644
index 00000000..bbe4ea72
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1840920
@@ -0,0 +1,11 @@
+
+changelog 4.1 krenel typo
+
+The changelog for 4.1 subsection Arm has a typo (krenel --> kernel)
+https://wiki.qemu.org/ChangeLog/4.1#Arm
+
+At the following line:
+The i.mx7 PCI controller emulation has been improved so it can boot current Linux krenels 
+
+it should be:
+The i.mx7 PCI controller emulation has been improved so it can boot current Linux kernels
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1841592 b/results/classifier/gemma3:12b/kernel/1841592
new file mode 100644
index 00000000..c3c8c0bc
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1841592
@@ -0,0 +1,10 @@
+
+ppc: softfloat float implementation issues
+
+Per bug #1841491, Richard Henderson (rth) said:
+> The float test failure is part of a larger problem for target/powerpc in which all float 
+> routines are implemented incorrectly. They are all implemented as double operations with
+> rounding to float as a second step. Which not only produces incorrect exceptions, as in
+> this case, but incorrect > numerical results from the double rounding.
+> 
+> This should probably be split to a separate bug...
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1842 b/results/classifier/gemma3:12b/kernel/1842
new file mode 100644
index 00000000..3b4a482f
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1842
@@ -0,0 +1,16 @@
+
+keyutils meson regression in 8.1.0
+Description of problem:
+keyutils is no longer found by meson during the build.
+
+commit 0db0fbb5cf8955d4f7a4a82bde32cfd93bd042ea appears to be buggy:
+```
+$ grep KEYUTILS config-host.h
+#undef CONFIG_KEYUTILS
+```
+Steps to reproduce:
+1. Have keyutils installed
+2. Build QEMU 8.1.0
+3. Note that keyutils is no longer linked into the build
+
+Thanks
diff --git a/results/classifier/gemma3:12b/kernel/1844597 b/results/classifier/gemma3:12b/kernel/1844597
new file mode 100644
index 00000000..0c34a592
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1844597
@@ -0,0 +1,89 @@
+
+fc1120a7f5f2d4b601003205c598077d3eb11ad2 causes a kernel panic in vfp_init on a clang built kernel
+
+Commit 4cdabee7d6d2 ("ARM: configs: aspeed_g5: Enable AST2600") [1] in the Linux kernel enabled CONFIG_VFP. When building this config with Clang, the resulting kernel does not boot after commit fc1120a7f5 ("target/arm: Implement NSACR gating of floating point") [2] (present since the 4.1.0 release).
+
+The QEMU command:
+
+qemu-system-arm -m 512m \
+                -machine romulus-bmc \
+                -no-reboot \
+                -dtb out/arch/arm/boot/dts/aspeed-bmc-opp-romulus.dtb \
+                -initrd rootfs.cpio \
+                -display none \
+                -serial mon:stdio \
+                -kernel ${KBF}/arch/arm/boot/zImage
+
+If it is needed, the rootfs we are using is provided at a link below [3].
+
+Debugging with QEMU reveals that the kernel panics in vfp_init, specifically at the line:
+
+vfpsid = fmrx(FPSID);
+
+in arch/arm/vfp/vfpmodule.c because of an illegal instruction:
+
+[    0.058685] VFP support v0.3: 
+[    0.059159] Internal error: Oops - undefined instruction: 0 [#1] SMP ARM
+[    0.059525] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.3.0-next-20190918-dirty #1
+[    0.059547] Hardware name: Generic DT based system
+[    0.059702] PC is at vfp_init+0x50/0x1f4
+[    0.059721] LR is at vfp_init+0x4c/0x1f4
+[    0.059738] pc : [<80b0383c>]    lr : [<80b03838>]    psr: 60000153
+[    0.059756] sp : 9e497ec0  ip : 00000020  fp : 9e497ed8
+[    0.059773] r10: 00000000  r9 : ffffe000  r8 : 80c06048
+[    0.059792] r7 : 00000000  r6 : 80c0caac  r5 : 80c6c418  r4 : 80b037ec
+[    0.059811] r3 : 00000000  r2 : 339aa372  r1 : 00000000  r0 : 00000012
+[    0.059859] Flags: nZCv  IRQs on  FIQs off  Mode SVC_32  ISA ARM  Segment none
+[    0.059883] Control: 00c5387d  Table: 80004008  DAC: 00000051
+[    0.059997] Process swapper/0 (pid: 1, stack limit = 0x(ptrval))
+[    0.060048] Stack: (0x9e497ec0 to 0x9e498000)
+[    0.060205] 7ec0: 80b037ec 80b6bf0c 80b037ec ffffffff 00000000 00000000 9e497f48 80b01100
+[    0.060310] 7ee0: 00000000 9eeff9e0 80a85734 809eb9be 00000000 8014b7f4 9eeff9e0 80a85734
+[    0.060408] 7f00: 9e497f48 8014b7f4 000000a4 00000001 00000001 00000000 80b0133c 9e497f38
+[    0.060509] 7f20: 00000000 9eeff9d5 339aa372 80b6be80 80b6bf0c 00000000 00000000 00000000
+[    0.060606] 7f40: 00000000 00000000 9e497f70 80b01864 00000001 00000001 00000000 80b0133c
+[    0.060703] 7f60: 00000001 8085d268 00000000 00000000 9e497f80 80b01758 00000000 00000000
+[    0.060800] 7f80: 9e497f90 80b015e4 00000000 8085d268 9e497fa8 8085d27c 00000000 8085d268
+[    0.060897] 7fa0: 00000000 00000000 00000000 801010e8 00000000 00000000 00000000 00000000
+[    0.060993] 7fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
+[    0.061090] 7fe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000
+[    0.061625] [<80b0383c>] (vfp_init) from [<80b01100>] (do_one_initcall+0xa8/0x1e0)
+[    0.061722] [<80b01100>] (do_one_initcall) from [<80b01864>] (do_initcall_level+0xfc/0x12c)
+[    0.061742] [<80b01864>] (do_initcall_level) from [<80b01758>] (do_basic_setup+0x2c/0x3c)
+[    0.061759] [<80b01758>] (do_basic_setup) from [<80b015e4>] (kernel_init_freeable+0x68/0x104)
+[    0.061777] [<80b015e4>] (kernel_init_freeable) from [<8085d27c>] (kernel_init+0x14/0x26c)
+[    0.061798] [<8085d27c>] (kernel_init) from [<801010e8>] (ret_from_fork+0x14/0x2c)
+[    0.061835] Exception stack(0x9e497fb0 to 0x9e497ff8)
+[    0.061896] 7fa0:                                     00000000 00000000 00000000 00000000
+[    0.061998] 7fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
+[    0.062080] 7fe0: 00000000 00000000 00000000 00000000 00000013 00000000
+[    0.062263] Code: e5860000 e59f0174 ebd9d8fc e59f5170 (eef04a10) 
+[    0.062679] ---[ end trace 2d338c91e4e74562 ]---
+
+Before fc1120a7f5:
+
+[    0.069418] VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
+
+Should you need to reproduce this locally:
+
+* clang 9.0.0 or later is needed to build this config. If you do not have easy access to such a build, we have a clang build script available [4] that can help with this:
+
+% ./build-llvm.py --branch llvmorg-9.0.0-rc6 \
+                  --build-stage1-only \
+                  --projects clang \
+                  --targets ARM
+
+* Because of an unrelated build issue, linux-next needs to be used (or the singular patch that resolves it needs to be cherry-picked on top of 4cdabee7d6d2 [5]). The kernel make command used:
+
+% make -j$(nproc) -s \
+       ARCH=arm \
+       CC=clang \
+       CROSS_COMPILE=arm-linux-gnueabi- \
+       O=out \
+       distclean aspeed_g5_defconfig all
+
+[1]: https://git.kernel.org/linus/4cdabee7d6d2e439fea726a101e448c4ca6837f4
+[2]: https://git.qemu.org/?p=qemu.git;a=commit;h=fc1120a7f5f2d4b601003205c598077d3eb11ad2
+[3]: https://github.com/ClangBuiltLinux/continuous-integration/blob/800d84bf8c55ee04c50ed4c78144a96d889a91c5/images/arm/rootfs.cpio
+[4]: https://github.com/ClangBuiltLinux/tc-build
+[5]: http://git.armlinux.org.uk/cgit/linux-arm.git/commit/?id=7b3948597372e5a6b314208ac320362c204b7f0f
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1844635 b/results/classifier/gemma3:12b/kernel/1844635
new file mode 100644
index 00000000..d5e9f971
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1844635
@@ -0,0 +1,45 @@
+
+qemu bug where load linux kernel
+
+i found a qemu bug ,when the qemu start and parse the kernel file .
+
+This vulnerability can be exploited.
+
+thanks
+
+/****
+
+
+(gdb) set args -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -m 2048  -smp 2 -cpu host -machine kernel_irqchip=split -kernel poc1
+(gdb) r
+Starting program: /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -m 2048  -smp 2 -cpu host -machine kernel_irqchip=split -kernel ./poc/poc1
+[Thread debugging using libthread_db enabled]
+Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
+[New Thread 0x7fffe9a03700 (LWP 30066)]
+[New Thread 0x7fffe9202700 (LWP 30068)]
+[New Thread 0x7fffe8a01700 (LWP 30069)]
+
+Thread 1 "qemu-system-x86" received signal SIGSEGV, Segmentation fault.
+__memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:249
+249	../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S: No such file or directory.
+(gdb) bt
+#0  0x00007ffff2390b1f in __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:249
+#1  0x00005555559ebdcf in rom_copy ()
+#2  0x00005555558dd1b3 in load_multiboot ()
+#3  0x00005555558de1c3 in  ()
+#4  0x00005555558e19d1 in pc_memory_init ()
+#5  0x00005555558e4ee3 in  ()
+#6  0x00005555559e8500 in machine_run_board_init ()
+#7  0x0000555555834959 in main ()
+(gdb) c
+Continuing.
+Couldn't get registers: No such process.
+Couldn't get registers: No such process.
+(gdb) [Thread 0x7fffe8a01700 (LWP 30069) exited]
+[Thread 0x7fffe9202700 (LWP 30068) exited]
+[Thread 0x7fffe9a03700 (LWP 30066) exited]
+
+Program terminated with signal SIGSEGV, Segmentation fault.
+The program no longer exists.
+
+***/
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1846816 b/results/classifier/gemma3:12b/kernel/1846816
new file mode 100644
index 00000000..db9383d9
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1846816
@@ -0,0 +1,120 @@
+
+Booting error on AIX 6.1 "Illegal Trap Instruction Interrupt in Kernel""
+
+# ls -ltr
+total 8750584
+-rw-rw-r--  1 linux linux 4274997248 Oct  4 18:33 AIX.vol1.iso
+-rw-rw-r--  1 linux linux 4293888000 Oct  4 18:45 AIX.vol2.iso
+-rw-rw-r--  1 linux linux  391485440 Oct  4 18:50 AIX.vol3.iso
+-rw-r--r--  1 root  root      204608 Oct  4 19:00 AIX61.img
+
+# qemu-system-ppc64 -cpu POWER8,compat=power7 -machine pseries -m 8192 -serial mon:stdio \
+> -drive file=/qemu/BST/AIX61.img,if=none,id=drive-virtio-disk0 \
+> -device virtio-scsi-pci,id=scsi -device scsi-hd,drive=drive-virtio-disk0 \
+> -cdrom /qemu/BST/AIX.vol1.iso \
+> -prom-env boot-command='boot cdrom: -s verbose'
+
+
+VNC server running on ::1:5900
+qemu-system-ppc64: warning: TCG doesn't support requested feature, cap-ibs=workaround
+
+
+SLOF **********************************************************************
+QEMU Starting
+ Build Date = Jul  3 2019 12:26:14
+ FW Version = git-ba1ab360eebe6338
+ 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
+          8200000000000000 CD-ROM   : "QEMU     QEMU CD-ROM      2.5+"
+Populating /pci@800000020000000
+                     00 0000 (D) : 1234 1111    qemu vga
+                     00 0800 (D) : 1033 0194    serial bus [ usb-xhci ]
+                     00 1000 (D) : 1af4 1004    virtio [ scsi ]
+Populating /pci@800000020000000/scsi@2
+       SCSI: Looking for devices
+          100000000000000 DISK     : "QEMU     QEMU HARDDISK    2.5+"
+Installing QEMU fb
+
+
+
+Scanning USB
+  XHCI: Initializing
+    USB Keyboard
+    USB mouse
+No console specified using screen & keyboard
+
+  Welcome to Open Firmware
+
+  Copyright (c) 2004, 2017 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: -s verbose from: /vdevice/v-scsi@71000003/disk@8200000000000000: ...   Successfully loaded
+qemu-system-ppc64: Couldn't negotiate a suitable PVR during CAS
+AIX
+StarLED{814}
+
+AIX Version 6.1
+exec(/etc/init){1,0}
+
+INIT: EXECUTING /sbin/rc.boot 1
+exec(/usr/bin/sh,-c,/sbin/rc.boot 1){1114146,1}
+exec(/sbin/rc.boot,/sbin/rc.boot,1){1114146,1}
++ PHASE=1
++ + bootinfo -p
+exec(/usr/sbin/bootinfo,-p){1179684,1114146}
+PLATFORM=chrp
++ [ ! -x /usr/lib/boot/bin/bootinfo_chrp ]
++ [ 1 -eq 1 ]
++ 1> /usr/lib/libc.a
++ init -c unlink /usr/lib/boot/bin/!(*_chrp)
+exec(/etc/init,-c,unlink /usr/lib/boot/bin/!(*_chrp)){1179686,1114146}
++ chramfs -t
+exec(/usr/sbin/chramfs,-t){1179688,1114146}
++ init -c unlink /usr/sbin/chramfs
++ 1> /dev/null
+exec(/etc/init,-c,unlink /usr/sbin/chramfs){1179690,1114146}
++ + bootinfo -t
+exec(/usr/sbin/bootinfo,-t){1179692,1114146}
+BOOTYPE=3
++ [ 0 -ne 0 ]
++ [ -z 3 ]
++ unset pdev_to_ldev undolt native_netboot_cfg
++ unset disknet_odm_init config_ATM
++ /usr/lib/methods/showled 0x510 DEV CFG 1 START
+exec(/usr/lib/methods/showled,0x510,DEV CFG 1 START){1179694,1114146}
++ cfgmgr -f -v
+exec(/usr/sbin/cfgmgr,-f,-v){1179696,1114146}
+cfgmgr is running in phase 1
+----------------
+Time: 0 LEDS: 0x538
+Invoking top level program -- "/etc/methods/defsys"
+exec(/bin/sh,-c,/etc/methods/defsys ){1245222,1179696}
+exec(/etc/methods/defsys){1245222,1179696}
+exec(/bin/sh,-c,/usr/lib/methods/define_rspc -n -c sys -s node -t chrp){1310760,1245222}
+exec(/usr/lib/methods/define_rspc,-n,-c,sys,-s,node,-t,chrp){1310760,1245222}
+Time: 0 LEDS: 0x539
+Return code = 0
+***** stdout *****
+sys0
+
+*** no stderr ****
+----------------
+Attempting to configure device 'sys0'
+Time: 0 LEDS: 0x811
+Invoking /usr/lib/methods/cfgsys_chrp -1 -l sys0
+exec(/bin/sh,-c,/usr/lib/methods/cfgsys_chrp -1 -l sys0){1245224,1179696}
+Number of running methods: 1
+exec(/usr/lib/methods/cfgsys_chrp,-1,-l,sys0){1245224,1179696}
+LED{A20}
+Illegal Trap Instruction Interrupt in Kernel
+04151A74      tweqi    r0,0                r0=0
+KDB(0)>
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1849894 b/results/classifier/gemma3:12b/kernel/1849894
new file mode 100644
index 00000000..9b2d7770
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1849894
@@ -0,0 +1,45 @@
+
+hw/scsi/scsi-disk.c line 2554 allocation overflow
+
+When compiling qemu from git master (at commit 03bf012e523ecdf047ac56b2057950247256064d ) on Linux amd64, with gcc-9 9.2.1 , and using `-march=native -flto`, during linking of most target binaries, compiler does detect an issue with allocation in scsi_disk_new_request_dump and aborts compilation.
+
+
+make[1]: Entering directory '/home/user/qemu/slirp'
+make[1]: Nothing to be done for 'all'.
+make[1]: Leaving directory '/home/user/qemu/slirp'
+nm: stats64.o: no symbols
+  LINK    aarch64-softmmu/qemu-system-aarch64
+In function ‘scsi_disk_new_request_dump’,
+    inlined from ‘scsi_new_request’ at hw/scsi/scsi-disk.c:2580:9,
+    inlined from ‘scsi_new_request’ at hw/scsi/scsi-disk.c:2564:21:
+hw/scsi/scsi-disk.c:2554:19: error: argument 1 value ‘18446744073709551612’ exceeds maximum object size 9223372036854775807 [-Werror=alloc-size-larger-than=]
+hw/scsi/scsi-disk.c: In function ‘scsi_new_request’:
+/usr/include/glib-2.0/glib/gmem.h:78:10: note: in a call to allocation function ‘g_malloc’ declared here
+   78 | gpointer g_malloc         (gsize  n_bytes) G_GNUC_MALLOC G_GNUC_ALLOC_SIZE(1);
+      |          ^
+lto1: all warnings being treated as errors
+lto-wrapper: fatal error: c++ returned 1 exit status
+compilation terminated.
+/usr/bin/ld: error: lto-wrapper failed
+collect2: error: ld returned 1 exit status
+
+
+
+same happens for most other targets: alpha-softmmu/qemu-system-alpha arm-softmmu/qemu-system-arm hppa-softmmu/qemu-system-hppa i386-softmmu/qemu-system-i386 lm32-softmmu/qemu-system-lm32 mips-softmmu/qemu-system-mips mips64-softmmu/qemu-system-mips64 mips64el-softmmu/qemu-system-mips64el mipsel-softmmu/qemu-system-mipsel ppc-softmmu/qemu-system-ppc ppc64-softmmu/qemu-system-ppc64 riscv32-softmmu/qemu-system-riscv32 riscv64-softmmu/qemu-system-riscv64 s390x-softmmu/qemu-system-s390x sh4-softmmu/qemu-system-sh4 sh4eb-softmmu/qemu-system-sh4eb sparc-softmmu/qemu-system-sparc sparc64-softmmu/qemu-system-sparc64 x86_64-softmmu/qemu-system-x86_64 xtensa-softmmu/qemu-system-xtensa xtensaeb-softmmu/qemu-system-xtensaeb
+
+Notice -softmmu being a common factor here.
+
+
+
+The size of the allocation for the temporary buffer for dumping using snprintf is determined based on the size of the buffer via call to scsi_cdb_length. I believe the heavy inlining and constant propagation makes scsi_cdb_length return -1, so len = -1. Then allocation size is 5*len + 1, or -4. Which overflows to 2^64 - 4 or so.
+
+The case of len==-1 from scsi_cdb_length happens if the (buf[0] >> 5) is not 0, 1, 2, 4 or 5.
+
+However, I can't find out how gcc figures out that buf[0] is not one of these variables. To me looking at this function, compiler should not know anything about buf[0].
+
+I tried following the chain of calls back, including devirtualize alloc_req, and I found scsi_device_alloc_req calling these alloc_req callbacks, but it is itself called from scsi_req_new, which is called in  get_scsi_requests , just after buf is filled from QEMUFile using qemu_get_buffer, which ultimately goes even further into read paths, which there might be many AFAIK.
+
+
+
+
+glib2 version 2.62.1-1
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1850 b/results/classifier/gemma3:12b/kernel/1850
new file mode 100644
index 00000000..a87d1b37
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1850
@@ -0,0 +1,30 @@
+
+AARCH64 Illegal Instruction (CurrentEL)
+Description of problem:
+While emulating Aarch64 in QEMU, whenever the instruction `CurrentEL` is executed,
+QEMU crashes with the following message.
+
+`qemu: uncaught target signal 4 (Illegal instruction) - core dumped
+Illegal instruction (core dumped)`
+
+I've tried both QEMU user space translation (qemu-aarch64-static) and QEMU emulation (qemu-system-aarch64),
+and both fail with the above message.
+
+C Code to reproduce bug, courtesy of https://github.com/cirosantilli/linux-kernel-module-cheat/blob/35684b1b7e0a04a68987056cb15abd97e3d2f0cc/baremetal/arch/aarch64/el.c
+```
+#include <stdio.h>
+#include <inttypes.h>
+
+int main(void) {
+        register uint64_t x0 __asm__ ("x0");
+	__asm__ ("mrs x0, CurrentEL;" : : : "%x0");
+	printf("%" PRIu64 "\n", x0 >> 2);
+	return 0;
+}
+```
+Steps to reproduce:
+1. Copy C code above into file.
+2. Compile code `gcc ./main.c --static`
+3. Execute elf bin `./a.out`
+Additional information:
+
diff --git a/results/classifier/gemma3:12b/kernel/1850378 b/results/classifier/gemma3:12b/kernel/1850378
new file mode 100644
index 00000000..7090b12e
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1850378
@@ -0,0 +1,19 @@
+
+RISC-V unreliable IPIs
+
+I am working on a project with custom inter processor interrupts (IPIs) on the RISC-V virt machine.
+After upgrading from version 3.1.0 to 4.1.0 which fixes a related issue (https://github.com/riscv/riscv-qemu/issues/132) I am able to use the CPU hotplug feature.
+
+However, if I try to use IPIs for communication between two cores, the wfi instruction behaves strangely. Either it does not return, or it returns on timer interrupts, even though they are disabled. The code, I use on one core to wait for an interrupt is the following.
+
+	csr_clear(sie, SIE_SEIE | SIE_STIE);
+	do {
+		wait_for_interrupt();
+		sipval = csr_read(sip);
+		sieval = csr_read(sie);
+		scauseval = csr_read(scause) & 0xFF;
+	/* only break if wfi returns for an software interrupt */
+	} while ((sipval & sieval) == 0 && scauseval != 1);
+	csr_set(sie, SIE_SEIE | SIE_STIE);
+
+Since the resulting sequence does not seem to be deterministic, my guess is, that it has something to do with the communication of qemu's threads for the different cores.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1851939 b/results/classifier/gemma3:12b/kernel/1851939
new file mode 100644
index 00000000..f5e29bc1
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1851939
@@ -0,0 +1,17 @@
+
+RISC-V mstatus TSR bit not correctly implemented
+
+Hi,
+
+since qemu 4.1.0 the TSR bit in mstatus register is supported. But it does not allow for executing sret in m-mode.
+
+From the RISC-V specifications:
+"When TSR=1, attempts to execute SRET while executing in S-mode will raise an illegal instruction
+exception. When TSR=0, this operation is permitted in S-mode."
+
+This means an exception should only be raised when executing in S-mode, but not in M-mode, hence you should change the condition in helper_sret (target/riscv/op_helper.c) from:
+     if (env->priv_ver >= PRIV_VERSION_1_10_0 &&
+          get_field(env->mstatus, MSTATUS_TSR))
+to:
+     if (env->priv_ver >= PRIV_VERSION_1_10_0 &&
+          get_field(env->mstatus, MSTATUS_TSR) && !(env->priv >= PRV_M))
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1852115 b/results/classifier/gemma3:12b/kernel/1852115
new file mode 100644
index 00000000..363b3776
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1852115
@@ -0,0 +1,45 @@
+
+qemu --static user build fails with fedora rawhide glibc-2.30.9000
+
+Building qemu latest git 654efcb511d on fedora rawhide fails with this configure line:
+
+./configure \
+	--static \
+	--disable-system \
+	--enable-linux-user \
+	--disable-werror \
+	--disable-tools \
+	--disable-capstone
+
+make fails with:
+
+/usr/bin/ld: linux-user/syscall.o: in function `do_syscall1':
+/root/qemu.git/linux-user/syscall.c:7769: undefined reference to `stime'
+collect2: error: ld returned 1 exit status
+
+Seems related to this glibc change: https://sourceware.org/git/?p=glibc.git;a=commit;h=12cbde1dae6fa4a9a792b64564c7e0debf7544cc
+
+...
+
++* The obsolete function stime is no longer available to newly linked
++  binaries and it has been removed from <time.h> header.  This function
++  has been deprecated in favor of clock_settime.
++
+
+# rpm -q glibc
+glibc-2.30.9000-17.fc32.x86_64
+
+
+FWIW there's some other messages but I don't think they are fatal:
+
+/usr/bin/ld: /usr/lib/gcc/x86_64-redhat-linux/9/../../../../lib64/libglib-2.0.a(gutils.c.o): in function `g_get_user_database_entry':
+(.text+0x267): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
+/usr/bin/ld: (.text+0xe0): warning: Using 'getpwnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
+/usr/bin/ld: (.text+0x11e): warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
+
+
+Also, --disable-capstone is required to avoid this error, but it is pre-existing, not sure if it's a bug, if so I can file a separate one:
+
+  LINK    aarch64-linux-user/qemu-aarch64
+/usr/bin/ld: cannot find -lcapstone
+collect2: error: ld returned 1 exit status
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1852781 b/results/classifier/gemma3:12b/kernel/1852781
new file mode 100644
index 00000000..c737b3b0
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1852781
@@ -0,0 +1,33 @@
+
+qemu s390x on focal - applications breaking
+
+Running qemu-system-s390x (1:4.0+dfsg-0ubuntu10) on an x86-64 Focal host with an upgrade of a Eoan s390x VM to a Focal s390x is triggering random breakage, for example:
+
+sudo apt-get update && sudo apt-get dist-upgrade
+
+...
+...
+
+Unpacking debianutils (4.9) over (4.8.6.3) ...
+Setting up debianutils (4.9) ...
+Use of uninitialized value $ARGV[0] in string ne at /usr/sbin/update-mime line 43.
+(Reading database ... 83640 files and directories currently installed.)
+Preparing to unpack .../bash_5.0-5ubuntu1_s390x.deb ...
+Unpacking bash (5.0-5ubuntu1) over (5.0-4ubuntu1) ...
+Setting up bash (5.0-5ubuntu1) ...
+[12124.788618] User process fault: interruption code 0007 ilc:3 in bash[2aa3d780000+149000]
+dpkg: error processing package bash (--configure):
+ installed bash package post-installation script subprocess was killed by signal (Floating point exception), core du
+mped
+Errors were encountered while processing:
+ bash
+E: Sub-process /usr/bin/dpkg returned an error code (1)
+
+And now bash is completely broken:
+
+cking@eoan-s390x:~$ bash
+[12676.204389] User process fault: interruption code 0007 ilc:3 in bash[2aa14780000+149000]
+
+Floating point exception (core dumped)
+
+The upgrade works OK on a s390x, so I'm assuming it's something to do with the qemu emulation.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1853781 b/results/classifier/gemma3:12b/kernel/1853781
new file mode 100644
index 00000000..4014069f
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1853781
@@ -0,0 +1,37 @@
+
+Baremetal kernel built from assembly runs multiple times
+
+QEMU version: 4.1.0.
+
+Full command used to launch: qemu-system-arm -machine raspi2 -kernel main
+
+(Technically, the first term of the command is actually "~/Applications/QEMU/qemu-4.1.0/build/arm-softmmu/qemu-system-arm", but I shortened it for readability.)
+
+Host information: Running debian 9.9 on a 64-bit x86 processor (Intel i5-2520M).
+
+Guest information: No operating system. I'm providing my own kernel, which I assembled from a 60-line ARM assembly program using arm-none-eabi-as and then linked with arm-none-eabi-ld, both version 2.28-5+9+b3.
+
+Additional details: To view the screen output of the program, I am using vncviewer version 6.19.1115 (r42122). All of the above software packages were installed as debian packages using apt, except for QEMU, which I built from source after downloading from the official website.
+
+.
+
+The issue here is that I have written a program in assembly and it isn't doing what I expect it to when I emulate it. Here's a summary of the code:
+
+1) Read a number from zero-initialized memory.
+
+2) Add one to the number and write it back.
+
+3) Use the number to determine a screen location to write to.
+
+4) Use the number to determine what color to write.
+
+5) Write 4000 half-words to the screen starting at that offset and using that color. This should result in a stripe across the whole screen that's about 6 pixels tall.
+
+The expected behavior is that *one* stripe should appear on the screen in a single color. However, the actual behavior is that up to *four* stripes appear, each in a different color. Furthermore, if I comment out the line that writes the incremented counter back to memory, then only one stripe will appear.
+
+I will also note that the Raspberry Pi 2, which is the system I'm emulating, has four cores. What I suspect is going on here is that my code is being loaded onto all four cores of the emulated machine. I couldn't find anything about this anywhere in the documentation, and it strikes me as bug.
+
+I have attached the assmebly code that I'm using, as well as a short makefile. Since I can only add one attachment to this report, I've combined the two into a single text file and labeled each. After separating the two into two files, you will need to change the first line of the makefile to point to your installation of qemu-system-arm v4.1.0. After that, type "make run" to run the program.
+
+Thanks in advance,
+Evan Rysdam
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1858461 b/results/classifier/gemma3:12b/kernel/1858461
new file mode 100644
index 00000000..0a7e41c5
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1858461
@@ -0,0 +1,24 @@
+
+Please refactor linux-user/mips/cpu_loop.c
+
+Hello. I am working with qemu on test images. I've added a new syscall (436) to qemu but received ENOSYS from mips application.
+
+Please open "linux-user/mips/cpu_loop.c". I've added at the end of "mips_syscall_args" the following:
+
+```
+MIPS_SYS(sys_getdents64_x32, 3)
+```
+
+But
+
+```
+syscall_num = env->active_tc.gpr[2] - 4000;
+if (syscall_num >= sizeof(mips_syscall_args)) {
+  ret = -TARGET_ENOSYS;
+```
+
+returns -TARGET_ENOSYS
+
+We can see that "linux-user/mips/cpu_loop.c" differs a lot from "linux-user/arm/cpu_loop.c". Arm has it's own "ARM_NR_BASE" and etc.
+
+Can you please refactor mips cpu loop in the same way as arm? Thank you.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1859021 b/results/classifier/gemma3:12b/kernel/1859021
new file mode 100644
index 00000000..3d7c0538
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1859021
@@ -0,0 +1,33 @@
+
+qemu-system-aarch64 (tcg):  cval + voff overflow not handled, causes qemu to hang
+
+The Armv8 architecture reference manual states that for any timer set (e.g. CNTP* and CNTV*), the condition for such timer to generate an interrupt (if enabled & unmasked) is:
+
+CVAL <= CNT(P/V)CT
+
+Although this is arguably sloppy coding, I have seen code that is therefore assuming it can set CVAL to a very high value (e.g. UINT64_MAX) and leave the interrupt enabled in CTL, and never get the interrupt.
+
+On latest master commit as the time of writing, there is an integer overflow in target/arm/helper.c gt_recalc_timer affecting the virtual timer when the interrupt is enabled in CTL:
+
+    /* Next transition is when we hit cval */
+    nexttick = gt->cval + offset;
+
+When this overflow happens, I notice that qemu is no longer responsive and that I have to SIGKILL the process:
+    - qemu takes nearly all the cpu time of the cores it is running on (e.g. 50% cpu usage if running on half the cores) and is completely unresponsive
+    - no guest interrupt (reported via -d int) is generated
+
+Here the minimal code example to reproduce the issue:
+
+    mov     x0, #1
+    msr     cntvoff_el2, x0
+    mov     x0, #-1
+    msr     cntv_cval_el0, x0
+    mov     x0, #1
+    msr     cntv_ctl_el0, x0 // interrupt generation enabled, not masked; qemu will start to hang here
+
+Options used:
+-nographic -machine virt,virtualization=on,gic-version=2,accel=tcg -cpu cortex-a57
+-smp 4 -m 1024 -kernel whatever.elf -d unimp,guest_errors,int -semihosting-config enable,target=native
+-serial mon:stdio
+
+Version used: 4.2
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1859920 b/results/classifier/gemma3:12b/kernel/1859920
new file mode 100644
index 00000000..dc5feea5
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1859920
@@ -0,0 +1,50 @@
+
+daemoniz not working on MacOS
+
+OS: MacOS Catalina 10.15.2
+Qemu install via brew: brew install qemu
+
+qemu-system-x86_64 -version
+QEMU emulator version 4.2.50 (v4.2.0-13-g084a398bf8-dirty)
+Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers
+
+---
+
+Start Ubuntu Desktop 18.04 client as follow:
+
+IMG_CD=$HOME/Downloads/iso/ubuntu-18.04.3-desktop-amd64.iso
+IMG_FILE=$HOME/code/vm/qemu/u64d01.qcow2
+MAC_ADDR=xx:xx:xx:xx:xx:xx
+
+qemu-system-x86_64 \
+-no-user-config -nodefaults \
+-show-cursor \
+-name u64d01 \
+-M q35,accel=hvf,usb=off,vmport=off \
+-cpu host -smp 4 -m 2048 \
+-overcommit mem-lock=off \
+-overcommit cpu-pm=off \
+-rtc base=utc,clock=host \
+\
+-device virtio-tablet-pci \
+-device virtio-vga \
+\
+-device virtio-blk-pci,drive=ssd1 \
+-drive id=ssd1,file=$IMG_FILE,if=none,format=qcow2 \
+\
+-device virtio-net-pci,netdev=nic1,mac=$MAC_ADDR \
+-netdev user,id=nic1,ipv4=on,ipv6=on,hostname=u64d01,hostfwd=tcp::2222-:22 \
+\
+-device ich9-intel-hda,id=snd,msi=on \
+-device hda-output,id=snd-codec0,bus=snd.0,cad=0,audiodev=snd0 \
+-audiodev coreaudio,id=snd0,out.buffer-count=10000 \
+\
+-daemonize
+
+Give following error:
+
+objc[3432]: +[NSNumber initialize] may have been in progress in another thread when fork() was called.
+objc[3432]: +[NSNumber initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.
+
+
+I checked "ps -ef|grep qemu" before and after the command, there was no qemu process running.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1861 b/results/classifier/gemma3:12b/kernel/1861
new file mode 100644
index 00000000..220583d5
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1861
@@ -0,0 +1,30 @@
+
+qemu 8.1.0 fails to build with ppc64l and musl libc
+Description of problem:
+qemu 8.1.0 fails to build on alpine linux ppc64le:
+
+```
+ninja: job failed: gcc -m64 -mlittle-endian -Ilibqemuutil.a.p -I. -I.. -Iqapi -Itrace -Iui/shader -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -fdiagnostics-color=auto -Wall -Winvalid-pch -std=gnu11 -O2 -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wundef -Wwrite-strings -Wmissing-prototypes -Wstrict-prototypes -Wredundant-decls -Wold-style-declaration -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wimplicit-fallthrough=2 -Wmissing-format-attribute -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -isystem /home/ncopa/aports/community/qemu/src/qemu-8.1.0/linux-headers -isystem linux-headers -iquote . -iquote /home/ncopa/aports/community/qemu/src/qemu-8.1.0 -iquote /home/ncopa/aports/community/qemu/src/qemu-8.1.0/include -iquote /home/ncopa/aports/community/qemu/src/qemu-8.1.0/host/include/ppc64 -iquote /home/ncopa/aports/community/qemu/src/qemu-8.1.0/host/include/generic -iquote /home/ncopa/aports/community/qemu/src/qemu-8.1.0/tcg/ppc -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fno-strict-aliasing -fno-common -fwrapv -Os -fstack-clash-protection -Wformat -Werror=format-security -O2 -fPIE -pthread -MD -MQ libqemuutil.a.p/util_cpuinfo-ppc.c.o -MF libqemuutil.a.p/util_cpuinfo-ppc.c.o.d -o libqemuutil.a.p/util_cpuinfo-ppc.c.o -c ../util/cpuinfo-ppc.c
+../util/cpuinfo-ppc.c: In function 'cpuinfo_init':
+../util/cpuinfo-ppc.c:33:18: error: 'PPC_FEATURE2_ARCH_3_1' undeclared (first use in this function); did you mean 'PPC_FEATURE2_ARCH_3_00'?
+   33 |     if (hwcap2 & PPC_FEATURE2_ARCH_3_1) {
+      |                  ^~~~~~~~~~~~~~~~~~~~~
+      |                  PPC_FEATURE2_ARCH_3_00
+../util/cpuinfo-ppc.c:33:18: note: each undeclared identifier is reported only once for each function it appears in
+../util/cpuinfo-ppc.c:43:18: error: 'PPC_FEATURE2_HAS_ISEL' undeclared (first use in this function); did you mean 'PPC_FEATURE_HAS_VSX'?
+   43 |     if (hwcap2 & PPC_FEATURE2_HAS_ISEL) {
+      |                  ^~~~~~~~~~~~~~~~~~~~~
+      |                  PPC_FEATURE_HAS_VSX
+../util/cpuinfo-ppc.c:56:26: error: 'PPC_FEATURE2_HAS_VEC_CRYPTO' undeclared (first use in this function); did you mean 'PPC_FEATURE2_VEC_CRYPTO'?
+   56 |             if (hwcap2 & PPC_FEATURE2_HAS_VEC_CRYPTO) {
+      |                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~
+      |                          PPC_FEATURE2_VEC_CRYPTO
+ninja: subcommand failed
+make: *** [Makefile:162: run-ninja] Error 1
+```
+Steps to reproduce:
+Build qemu 8.1.0 on alpine linux ppc64le.
+Additional information:
+Likely introduced by 623d7e3551a6fc5693c06ea938c60fe281b52e27
+
+Explicit `#include <asm/cputable.h>` fixes the `PPC_FEATURE2_ARCH_3_1` case but not the other two.
diff --git a/results/classifier/gemma3:12b/kernel/1861394 b/results/classifier/gemma3:12b/kernel/1861394
new file mode 100644
index 00000000..b2cfa350
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1861394
@@ -0,0 +1,15 @@
+
+qemu-system-riscv64 hangs after poweroff linux command
+
+QEMU Version : v4.2.0-773-g43d1455-dirty (commit 43d1455cf84283466e5c22a217db5ef4b8197b14)
+
+Command: qemu-system-riscv64 -machine virt -kernel ./bbl -nographic -initrd rootfs.cpio.gz -append "root=/dev/ram console=ttyS0"
+
+Host:LSB Version:    :core-4.1-amd64:core-4.1-noarch
+Distributor ID: CentOS
+Description:    CentOS Linux release 7.7.1908 (Core)
+Release:        7.7.1908
+Codename:       Core
+
+
+Problem: after boot, when type poweroff -f it hangs (not quitting). I have tested this for x86_64, and aarch64 and it works fine. The problem appears only for risv64(of those mentioned). Last time i have checked it worked also for riscv64 and it was on the d0f90e1423b4f412adc620eee93e8bfef8af4117 commit
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1861551 b/results/classifier/gemma3:12b/kernel/1861551
new file mode 100644
index 00000000..e81c8593
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1861551
@@ -0,0 +1,52 @@
+
+Errors while compiling source
+
+OS type: Mac OS X 10.11.6
+List of errors:
+qemu-io-cmds.c:837:5: warning: implicit declaration of function 'clock_gettime' is invalid in C99 [-Wimplicit-function-declaration]
+    clock_gettime(CLOCK_MONOTONIC, &t1);
+    ^
+qemu-io-cmds.c:837:19: error: use of undeclared identifier 'CLOCK_MONOTONIC'
+    clock_gettime(CLOCK_MONOTONIC, &t1);
+                  ^
+qemu-io-cmds.c:843:19: error: use of undeclared identifier 'CLOCK_MONOTONIC'
+    clock_gettime(CLOCK_MONOTONIC, &t2);
+                  ^
+qemu-io-cmds.c:970:19: error: use of undeclared identifier 'CLOCK_MONOTONIC'
+    clock_gettime(CLOCK_MONOTONIC, &t1);
+                  ^
+qemu-io-cmds.c:972:19: error: use of undeclared identifier 'CLOCK_MONOTONIC'
+    clock_gettime(CLOCK_MONOTONIC, &t2);
+                  ^
+qemu-io-cmds.c:1184:19: error: use of undeclared identifier 'CLOCK_MONOTONIC'
+    clock_gettime(CLOCK_MONOTONIC, &t1);
+                  ^
+qemu-io-cmds.c:1194:19: error: use of undeclared identifier 'CLOCK_MONOTONIC'
+    clock_gettime(CLOCK_MONOTONIC, &t2);
+                  ^
+qemu-io-cmds.c:1306:19: error: use of undeclared identifier 'CLOCK_MONOTONIC'
+    clock_gettime(CLOCK_MONOTONIC, &t1);
+                  ^
+qemu-io-cmds.c:1308:19: error: use of undeclared identifier 'CLOCK_MONOTONIC'
+    clock_gettime(CLOCK_MONOTONIC, &t2);
+                  ^
+qemu-io-cmds.c:1351:19: error: use of undeclared identifier 'CLOCK_MONOTONIC'
+    clock_gettime(CLOCK_MONOTONIC, &t2);
+                  ^
+qemu-io-cmds.c:1383:19: error: use of undeclared identifier 'CLOCK_MONOTONIC'
+    clock_gettime(CLOCK_MONOTONIC, &t2);
+                  ^
+qemu-io-cmds.c:1518:19: error: use of undeclared identifier 'CLOCK_MONOTONIC'
+    clock_gettime(CLOCK_MONOTONIC, &ctx->t1);
+                  ^
+qemu-io-cmds.c:1663:23: error: use of undeclared identifier 'CLOCK_MONOTONIC'
+        clock_gettime(CLOCK_MONOTONIC, &ctx->t1);
+                      ^
+qemu-io-cmds.c:1885:19: error: use of undeclared identifier 'CLOCK_MONOTONIC'
+    clock_gettime(CLOCK_MONOTONIC, &t1);
+                  ^
+qemu-io-cmds.c:1887:19: error: use of undeclared identifier 'CLOCK_MONOTONIC'
+    clock_gettime(CLOCK_MONOTONIC, &t2);
+                  ^
+1 warning and 14 errors generated.
+make: *** [qemu-io-cmds.o] Error 1
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1861653 b/results/classifier/gemma3:12b/kernel/1861653
new file mode 100644
index 00000000..ae419b01
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1861653
@@ -0,0 +1,37 @@
+
+CPU of qemu-system-aarch64 always stuck
+
+I started qemu with these arguments:
+ qemu-system-aarch64 -M virt-2.9 -cpu cortex-a72 -smp cores=8,threads=1,sockets=1 -m 2G -device nec-usb-xhci -device usb-kbd -device usb-tablet -pflash /sdcard/QEMU_EFI.img -pflash /sdcard/QEMU_VARS.img -device virtio-blk-device,drive=Ubuntu -drive if=none,id=Ubuntu,file=Ubuntu.vhd -nographic -net user -net nic,model=rtl8139 -kernel linux -initrd initrd.gz
+The setup program of Ubuntu devel aarch64 ran normally.But after several hours,the CPUs emulated by qemu-system-aarch64 went wrong.
+Here are the messages displayed on the tty
+[15842.164745] watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ksoftirqd/0:9]                                                                         [15930.163589] watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ksoftirqd/0:9]
+[16110.163540] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [ksoftirqd/0:9] 
+[16290.162801] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [ksoftirqd/0:9]
+[16470.163927] watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ksoftirqd/0:9] 
+[16650.163246] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [ksoftirqd/0:9] 
+[16830.163216] watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ksoftirqd/0:9] 
+[17010.164504] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [ksoftirqd/0:9]
+
+Then I tried CentOS 7.1908 aarch64 with almost the same arguments.
+After several hours,it went wrong too.
+[17480 . 201 1 58] rcu : (3 ticks this GP) idle=362/0/0x3 softirq=61631 /61 631 fqs=10077
+[17480 . 204889] (detected by 3 , t=24007 jiffies , g=218453 , q=5285) [1 7480 . 21 7986] Task dump for CPU 7 :
+[17480.222379] swapper/7R running task	0 
+0  0x0000002a [17480.229073] Call trace :
+[1 7480.241518]	switch t0+0x104/0x1 f8
+[17480.249839]	Ox7fffffffffffffff
+[17660.232314] rcu : INFO: rcu sched detected stalls on CPUs/ tasks :
+[17660.233580] rcu : (3 ticks this GP) idle=362/0/0x3 softirq=61631 /61 631 fqs=17770
+[17660.235837] (detected by 3,t=42012 jiffies , g=218453 , q=7039) 
+[17660 . 237955] Task dump for CPU 7 :
+[17660.238900] swapper/ 7  R running task  0   0
+[17660.242967] Call trace :
+[17660.246192]	switch t0+0x104/0x1 f8
+[17660.253215]	Ox7fffffffffffffff
+
+Obviously qemu-system-aarch64 caused these bugs.
+
+qemu version: 4.x(I have tested version 4.0 & 4.1.0 & 4.2.0)
+host architecture: aarch64(Qualcomm Snapdragon series)
+host system:Ubuntu devel 20.04& Debian 10(I have tested on many devices)
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1862986 b/results/classifier/gemma3:12b/kernel/1862986
new file mode 100644
index 00000000..990b9e05
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1862986
@@ -0,0 +1,65 @@
+
+qemu-s390x segfaults
+
+All tested versions (2.11 and 4.2) qemu-s390x crashes with a segfault when run on an aarch64 odroid Ubuntu.
+
+Steps to reproduce:
+
+root@odroid:~/workspace/bitcoin-core# /usr/local/bin/qemu-s390x "/root/workspace/bitcoin-core/build/bitcoin-s390x-linux-gnu/src/test/test_bitcoin_orig"
+Segmentation fault (core dumped)
+root@odroid:~/workspace/bitcoin-core# /usr/local/bin/qemu-s390x --version
+qemu-s390x version 4.2.0
+Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers
+root@odroid:~/workspace/bitcoin-core# /usr/bin/qemu-s390x "/root/workspace/bitcoin-core/build/bitcoin-s390x-linux-gnu/src/test/test_bitcoin_orig"
+Segmentation fault (core dumped)
+root@odroid:~/workspace/bitcoin-core# /usr/bin/qemu-s390x --version
+qemu-s390x version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.22)
+Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers
+
+
+qemu-arm does work on the same machine:
+
+root@odroid:~/workspace/bitcoin-core# /usr/bin/qemu-arm bitcoin-0.19.0.1-armhf/bin/test_bitcoin -t amount_tests
+Running 4 test cases...
+
+*** No errors detected
+root@odroid:~/workspace/bitcoin-core# /usr/local/bin/qemu-arm bitcoin-0.19.0.1-armhf/bin/test_bitcoin -t amount_tests
+Running 4 test cases...
+
+*** No errors detected
+
+
+What kind of debug information would be helpful for this issue report?
+
+
+GDB for the self-compiled latest release is not particularly helpful:
+
+(gdb) run
+Starting program: /usr/local/bin/qemu-s390x /root/workspace/bitcoin-core/build/bitcoin-s390x-linux-gnu/src/test/test_bitcoin_orig
+[Thread debugging using libthread_db enabled]
+Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
+[New Thread 0x7fb7a2a140 (LWP 28264)]
+
+Thread 1 "qemu-s390x" received signal SIGSEGV, Segmentation fault.
+0x000000555596b218 in __bss_start__ ()
+(gdb) bt
+#0  0x000000555596b218 in __bss_start__ ()
+#1  0x00000055556120a8 in ?? ()
+#2  0x00000055579904b0 in ?? ()
+Backtrace stopped: previous frame inner to this frame (corrupt stack?)
+
+A bit more information is available in the version shipped by Ubuntu:
+
+(gdb) run
+Starting program: /usr/bin/qemu-s390x /root/workspace/bitcoin-core/build/bitcoin-s390x-linux-gnu/src/test/test_bitcoin_orig
+[Thread debugging using libthread_db enabled]
+Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
+[New Thread 0x7fb7a01180 (LWP 28271)]
+
+Thread 1 "qemu-s390x" received signal SIGSEGV, Segmentation fault.
+0x0000005555738f98 in code_gen_buffer ()
+(gdb) bt
+#0  0x0000005555738f98 in code_gen_buffer ()
+#1  0x00000055555e96c8 in cpu_exec ()
+#2  0x00000055555ee430 in cpu_loop ()
+#3  0x00000055555c3328 in main ()
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1863508 b/results/classifier/gemma3:12b/kernel/1863508
new file mode 100644
index 00000000..72e9609d
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1863508
@@ -0,0 +1,26 @@
+
+qemu-system-arm stops with SIGSEGV in helper_gvec_eq16
+
+Segmentation fault when trying to start FreeBSD-arm system with qemu-system-arm (version 4.1.1 on Fedora 31)
+
+Commandline:
+gdb -q --args /bin/qemu-system-arm \
+ -name FreeBSD12,debug-threads=on \
+ -m 1536 -machine virt -smp 2 \
+ -M virt,highmem=off -serial mon:stdio -monitor telnet::45452,server,nowait \
+ -machine virt,accel=tcg,usb=off,dump-guest-core=off,gic-version=2 \
+ -overcommit mem-lock=off -no-reboot -device virtio-rng-device \
+ -bios u-boot-qemu.bin \
+ -drive file=FreeBSD-12.1-RELEASE-arm-armv7-CUBIEBOARD2.img,if=none,id=drive0,format=raw \
+ -device ich9-ahci,id=ahci -device ide-drive,drive=drive0,bus=ahci.0 
+
+Results:
+....
+Mounting local filesystems:.
+
+Thread 4 "CPU 1/TCG" received signal SIGSEGV, Segmentation fault.
+[Switching to Thread 0x7fffcedfe700 (LWP 53608)]
+0x00005555558d9332 in helper_gvec_eq16 (d=0x5555566748d8, a=0x5555566748e0, b=0x5555566748d0, desc=0) at /usr/src/debug/qemu-4.1.1-1.fc31.x86_64/accel/tcg/tcg-runtime-gvec.c:948
+948     DO_CMP2(16)
+
+Tested different versions of qemu. qemu-3.0.1 worked, but qemu-3.1.1 failed with the same error.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1864 b/results/classifier/gemma3:12b/kernel/1864
new file mode 100644
index 00000000..804fbd68
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1864
@@ -0,0 +1,22 @@
+
+x86 VM with TCG and SMP fails to start on 8.1.0
+Description of problem:
+I'm running Colima on MacOS to run Docker. After upgrading qemu to 8.1.0 my x86_64 VM fails to start. If I downgrade qemu to 8.0.4 everything runs normally. Relevant logs:
+
+```
+[   60.976187] rcu: 	0-...!: (0 ticks this GP) idle=0d58/0/0x0 softirq=44/44 fqs=0 (false positive?)
+[   60.979262] 	(detected by 1, t=6005 jiffies, g=-1171, q=1981 ncpus=2)
+[   60.982317] Sending NMI from CPU 1 to CPUs 0:
+[   11.583693] NMI backtrace for cpu 0 skipped: idling at native_safe_halt+0xb/0x10
+[   11.583693] INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 2.006 msecs
+[   60.982317] rcu: rcu_preempt kthread timer wakeup didn't happen for 6004 jiffies! g-1171 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402
+[   60.982317] rcu: 	Possible timer handling issue on cpu=0 timer-softirq=15
+[   60.982317] rcu: rcu_preempt kthread starved for 6005 jiffies! g-1171 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=0
+[   60.982317] rcu: 	Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior.
+[   60.982317] rcu: RCU grace-period kthread stack dump:
+[   60.982317] task:rcu_preempt     state:I stack:0     pid:15    ppid:2      flags:0x00004000
+```
+
+[serial.log](/uploads/1039eceff37133504eb93401df1db137/serial.log)
+Steps to reproduce:
+1. `colima start --arch x86_64`
diff --git a/results/classifier/gemma3:12b/kernel/1865 b/results/classifier/gemma3:12b/kernel/1865
new file mode 100644
index 00000000..bd7d439c
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1865
@@ -0,0 +1,25 @@
+
+ERROR:../target/s390x/tcg/cc_helper.c:128:cc_calc_addu: assertion failed: (carry_out <= 1)
+Description of problem:
+Installation progresses OK, but QEMU asserts during post-installation setup tasks:
+
+Performing post-installation setup tasks
+**
+ERROR:../target/s390x/tcg/cc_helper.c:128:cc_calc_addu: assertion failed: (carry_out <= 1)
+Bail out! ERROR:../target/s390x/tcg/cc_helper.c:128:cc_calc_addu: assertion failed: (carry_out <= 1)
+./install.sh: line 25: 158224 Aborted                 (core dumped) $QEMU/qemu-system-s390x -M s390-ccw-virtio -smp 1 -m 4G 
+-nographic -display none -serial mon:stdio -device virtio-scsi -drive file=$ISO,format=raw,if=none,id=c1 -device scsi-cd,dri
+ve=c1 -hda $DISK -kernel $KERNEL -initrd $INITRD -net nic,model=virtio,netdev=net1 -netdev user,id=net1 -D debug.log
+Steps to reproduce:
+1. Download ClefOS 7.7 ISO from [sinenomine](https://download.sinenomine.net/clefos)
+2. Download Fedora 27 ISO and extract kernel.img and initrd.img, for boot purposes
+3. Boot ClefOS ISO using Fedora kernel/initrd
+4. Go through a minimal install, observe crash during post-installation setup tasks
+Additional information:
+See script log and install.sh attached. [install-and-output.zip](/uploads/87eb8484344402ea9c68784f89ea3339/install-and-output.zip)
+
+I have tried QEMU 7.2.5 and 8.1 on my Fedora 38 AMD host.
+
+My goal is to create RHEL7, SLES12, Ubuntu20 (or compatible) VMs for s390x software builds.
+So far only Ubuntu20 has been successful.
+RHEL7 fails due to kernel issues described in QEMU issue 906, so I'm trying ClefOS (CentOS for z) based on a procedure [here](https://www.linuxquestions.org/questions/linux-server-73/install-clefos-7-5-an-open-source-version-of-rhel-7-5-s390x-using-qemu-4175658710/)
diff --git a/results/classifier/gemma3:12b/kernel/1865160 b/results/classifier/gemma3:12b/kernel/1865160
new file mode 100644
index 00000000..5eae9c38
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1865160
@@ -0,0 +1,48 @@
+
+Unpredictable behaviour resulting in User process faults
+
+An example of the behaviour can be reproduced when using NPM, whereby running the command multiple times will result in a variety of error conditions causing the command to fail:
+
+Example of failure:
+
+Segmentation fault.] / rollbackFailedOptional: verb npm-session 1a805a5e0ff7b8f5
+
+[ 3144.216869] User process fault: interruption code 0038 ilc:3 
+[ 3144.216981] Failing address: 66616c7365000000 TEID: 66616c7365000800
+[ 3144.217009] Fault in primary space mode while using user ASCE.
+[ 3144.217055] AS:00000000ed28c1c7 R3:0000000000000024 
+
+Feb 28 14:32:08 qemus390x kernel: [ 3144.216869] User process fault: interruption code 0038 ilc:3 
+Feb 28 14:32:08 qemus390x kernel: [ 3144.216981] Failing address: 66616c7365000000 TEID: 66616c7365000800
+Feb 28 14:32:08 qemus390x kernel: [ 3144.217009] Fault in primary space mode while using user ASCE.
+Feb 28 14:32:08 qemus390x kernel: [ 3144.217055] AS:00000000ed28c1c7 R3:0000000000000024 
+Feb 28 14:32:08 qemus390x kernel: [ 3144.217217] CPU: 2 PID: 1018 Comm: npm Not tainted 4.15.0-88-generic #88-Ubuntu
+Feb 28 14:32:08 qemus390x kernel: [ 3144.217234] Hardware name: QEMU 2964 QEMU (KVM/Linux)
+Feb 28 14:32:08 qemus390x kernel: [ 3144.217257] User PSW : 00000000185db982 00000000c1d5a1a1
+Feb 28 14:32:08 qemus390x kernel: [ 3144.217290]            R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 RI:0 EA:3
+Feb 28 14:32:08 qemus390x kernel: [ 3144.217322] User GPRS: 000002aa03705200 0000006a16d73ac1 0000003da4b829f1 0000000000000000
+Feb 28 14:32:08 qemus390x kernel: [ 3144.217343]            0000003da4b82a08 0000003da4b82a08 000002aa036a92ec 0000000000000000
+Feb 28 14:32:08 qemus390x kernel: [ 3144.217364]            0000003da4b829f1 000003ffdb8f7e50 0000003da4b82a08 000003ffdb8f7d88
+Feb 28 14:32:08 qemus390x kernel: [ 3144.217385]            66616c7365000000 000002aa036a05b0 000002aa015bcfb2 000003ffdb8f7d88
+Feb 28 14:32:08 qemus390x kernel: [ 3144.217512] User Code:#0000006a16d73b00: c0f4000000df	brcl	15,0000006a16d73cbe
+Feb 28 14:32:08 qemus390x kernel: [ 3144.217512]           >0000006a16d73b06: a7290000		lghi	%r2,0
+Feb 28 14:32:08 qemus390x kernel: [ 3144.217512]            0000006a16d73b0a: 07fe		bcr	15,%r14
+Feb 28 14:32:08 qemus390x kernel: [ 3144.217512]            0000006a16d73b0c: c02f000001f3	llilf	%r2,499
+Feb 28 14:32:08 qemus390x kernel: [ 3144.217512]            0000006a16d73b12: e3d0dff8ff71	lay	%r13,-8(%r13)
+Feb 28 14:32:08 qemus390x kernel: [ 3144.217512]            0000006a16d73b18: e320d0000024	stg	%r2,0(%r13)
+Feb 28 14:32:08 qemus390x kernel: [ 3144.217512]            0000006a16d73b1e: c028000002aa	iihf	%r2,682
+Feb 28 14:32:08 qemus390x kernel: [ 3144.217724] Last Breaking-Event-Address:
+Feb 28 14:32:08 qemus390x kernel: [ 3144.217759]  [<000002aa015bcfae>] 0x2aa015bcfae
+
+
+
+
+QEMU emulator version 4.2.0
+Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers
+
+QEMU Command:
+
+sudo qemu-system-s390x -smp cpus=5 -machine s390-ccw-virtio -cpu max,zpci=on -serial telnet::4441,server -display none -m 4096 -net nic -net tap  -drive file=ubuntu.root,if=none,id=drive-virtio-disk0,format=raw,cache=none -device virtio-blk-ccw,devno=fe.0.0003,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=100,scsi=off -drive file=ubuntu.home,if=none,id=drive-virtio-disk1,format=raw,cache=none -device virtio-blk-ccw,devno=fe.0.0002,drive=drive-virtio-disk1,id=virtio-disk1,bootindex=1,scsi=off -drive file=ubuntu.swap,if=none,id=drive-virtio-disk4,format=raw,cache=none -device virtio-blk-ccw,devno=fe.0.0005,drive=drive-virtio-disk4,id=virtio-disk4,bootindex=101,scsi=off
+
+
+Ubuntu 18.04.4 LTS qemus390x ttysclp0
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1866892 b/results/classifier/gemma3:12b/kernel/1866892
new file mode 100644
index 00000000..ef21b412
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1866892
@@ -0,0 +1,80 @@
+
+guest OS catches a page  fault bug when running dotnet
+
+The linux guest OS catches a page fault bug when running the dotnet application.
+
+host = metal = x86_64
+host OS = ubuntu 19.10
+qemu emulation, without KVM, with "tiny code generator" tcg; no plugins; built from head/master
+guest emulation = x86_64
+guest OS = ubuntu 19.10
+guest app = dotnet, running any program
+
+qemu sha=7bc4d1980f95387c4cc921d7a066217ff4e42b70 (head/master Mar 10, 2020)
+
+qemu invocation is:
+
+qemu/build/x86_64-softmmu/qemu-system-x86_64 \
+  -m size=4096 \
+  -smp cpus=1 \
+  -machine type=pc-i440fx-5.0,accel=tcg \
+  -cpu Skylake-Server-v1 \
+  -nographic \
+  -bios OVMF-pure-efi.fd \
+  -drive if=none,id=hd0,file=ubuntu-19.10-server-cloudimg-amd64.img \
+  -device virtio-blk,drive=hd0 \
+  -drive if=none,id=cloud,file=linux_cloud_config.img \
+  -device virtio-blk,drive=cloud \
+  -netdev user,id=user0,hostfwd=tcp::2223-:22 \
+  -device virtio-net,netdev=user0
+
+
+Here's the guest kernel console output:
+
+
+[ 2834.005449] BUG: unable to handle page fault for address: 00007fffffffc2c0
+[ 2834.009895] #PF: supervisor read access in user mode
+[ 2834.013872] #PF: error_code(0x0001) - permissions violation
+[ 2834.018025] IDT: 0xfffffe0000000000 (limit=0xfff) GDT: 0xfffffe0000001000 (limit=0x7f)
+[ 2834.022242] LDTR: NULL
+[ 2834.026306] TR: 0x40 -- base=0xfffffe0000003000 limit=0x206f
+[ 2834.030395] PGD 80000000360d0067 P4D 80000000360d0067 PUD 36105067 PMD 36193067 PTE 8000000076d8e867
+[ 2834.038672] Oops: 0001 [#4] SMP PTI
+[ 2834.042707] CPU: 0 PID: 13537 Comm: dotnet Tainted: G      D           5.3.0-29-generic #31-Ubuntu
+[ 2834.050591] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 0.0.0 02/06/2015
+[ 2834.054785] RIP: 0033:0x1555547eaeda
+[ 2834.059017] Code: d0 00 00 00 4c 8b a7 d8 00 00 00 4c 8b af e0 00 00 00 4c 8b b7 e8 00 00 00 4c 8b bf f0 00 00 00 48 8b bf b0 00 00 00 9d 74 02 <48> cf 48 8d 64 24 30 5d c3 90 cc c3 66 90 55 4c 8b a7 d8 00 00 00
+[ 2834.072103] RSP: 002b:00007fffffffc2c0 EFLAGS: 00000202
+[ 2834.076507] RAX: 0000000000000000 RBX: 00001554b401af38 RCX: 0000000000000001
+[ 2834.080832] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00007fffffffcfb0
+[ 2834.085010] RBP: 00007fffffffd730 R08: 0000000000000000 R09: 00007fffffffd1b0
+[ 2834.089184] R10: 0000155555331dd5 R11: 00001555553ad8d0 R12: 0000000000000002
+[ 2834.093350] R13: 0000000000000001 R14: 0000000000000001 R15: 00001554b401d388
+[ 2834.097309] FS:  0000155554fa5740 GS:  0000000000000000
+[ 2834.101131] Modules linked in: isofs nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ppdev input_leds serio_raw parport_pc parport sch_fq_codel ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd glue_helper virtio_net psmouse net_failover failover virtio_blk floppy
+[ 2834.122539] CR2: 00007fffffffc2c0
+[ 2834.126867] ---[ end trace dfae51f1d9432708 ]---
+[ 2834.131239] RIP: 0033:0x14d793262eda
+[ 2834.135715] Code: Bad RIP value.
+[ 2834.140243] RSP: 002b:00007ffddb4e2980 EFLAGS: 00000202
+[ 2834.144615] RAX: 0000000000000000 RBX: 000014d6f402acb8 RCX: 0000000000000002
+[ 2834.148943] RDX: 0000000001cd6950 RSI: 0000000000000000 RDI: 00007ffddb4e3670
+[ 2834.153335] RBP: 00007ffddb4e3df0 R08: 0000000000000001 R09: 00007ffddb4e3870
+[ 2834.157774] R10: 000014d793da9dd5 R11: 000014d793e258d0 R12: 0000000000000002
+[ 2834.162132] R13: 0000000000000001 R14: 0000000000000001 R15: 000014d6f402d040
+[ 2834.166239] FS:  0000155554fa5740(0000) GS:ffff97213ba00000(0000) knlGS:0000000000000000
+[ 2834.170529] CS:  0033 DS: 0000 ES: 0000 CR0: 0000000080050033
+[ 2834.174751] CR2: 000014d793262eb0 CR3: 0000000036130000 CR4: 00000000007406f0
+[ 2834.178892] PKRU: 55555554
+
+I run the application from a shell with `ulimit -s unlimited` (unlimited stack to size).
+
+The application creates a number of threads, and those threads make a lot of calls to sigaltstack() and mprotect(); see the relevant source for dotnet here https://github.com/dotnet/runtime/blob/15ec69e47b4dc56098e6058a11ccb6ae4d5d4fa1/src/coreclr/src/pal/src/thread/thread.cpp#L2467
+
+using strace -f on the app shows that no alt stacks come anywhere near the failing address; all alt stacks are in the heap, as expected.  None of the mmap/mprotect/munmap syscalls were given arguments in the high memory 0x7fffffff0000 and up.
+
+gdb (with default signal stop/print/pass semantics) does not report any signals prior to the kernel bug being tripped, so I doubt the alternate signal stack is actually used.
+
+When I run the same dotnet binary on the host (eg, on "bare metal"), the host kernel seems happy and dotnet runs as expected.
+
+I have not tried different qemu or guest or host O/S.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1871005 b/results/classifier/gemma3:12b/kernel/1871005
new file mode 100644
index 00000000..81b8a24a
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1871005
@@ -0,0 +1,18 @@
+
+build fails on CLOCK_MONOTONIC
+
+Moc OS X.11.6 El Capitan
+
+build fails on this 
+
+/Users/alba/Downloads/qemu-5.0.0-rc1/include/qemu/timer.h:843:9: warning: 
+      implicit declaration of function 'clock_gettime' is invalid in C99
+      [-Wimplicit-function-declaration]
+        clock_gettime(CLOCK_MONOTONIC, &ts);
+        ^
+/Users/alba/Downloads/qemu-5.0.0-rc1/include/qemu/timer.h:843:23: error: use of
+      undeclared identifier 'CLOCK_MONOTONIC'
+        clock_gettime(CLOCK_MONOTONIC, &ts);
+                      ^
+1 warning and 1 error generated.
+make: *** [trace/control.o] Error 1
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1871842 b/results/classifier/gemma3:12b/kernel/1871842
new file mode 100644
index 00000000..043af99e
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1871842
@@ -0,0 +1,52 @@
+
+AMD CPUID leaf 0x8000'0008 reported number of cores  inconsistent with ACPI.MADT
+
+Setup:
+CPU: AMD EPYC-v2 or host's EPYC cpu
+Linux 64-bit fedora host; Kernel version 5.5.15-200.fc31
+qemu version: self build
+git-head: f3bac27cc1e303e1860cc55b9b6889ba39dee587
+config: Configured with: '../configure' '--target-list=x86_64-softmmu,mips64el-softmmu,mips64-softmmu,mipsel-softmmu,mips-softmmu,i386-softmmu,aarch64-softmmu,arm-softmmu' '--prefix=/opt/qemu-master'
+
+Cmdline: 
+qemu-system-x86_64 -kernel /home/peppelt/code/l4/internal/.build-x86_64/bin/amd64_gen/bootstrap -append "" -initrd "./fiasco/.build-x86_64/fiasco , ... " -serial stdio -nographic -monitor none -nographic -monitor none -cpu EPYC-v2 -m 4G -smp 4 
+
+Issue:
+We are developing an microkernel operating system called L4Re. We recently got an AMD EPYC server for testing and we couldn't execute SMP tests of our system when running Linux + qemu + VM w/ L4Re.
+In fact, the kernel did not recognize any APs at all. On AMD CPUs the kernel checks for the number of cores reported in CPUID leaf 0x8000_0008.ECX[NC] or [ApicIdSize].  [0][1]
+
+The physical machine reports for leaf 0x8000_0008:  EAX: 0x3030 EBX: 0x18cf757 ECX: 0x703f EDX: 0x1000
+The lower four bits of ECX are the [NC] field and all set.
+
+When querying inside qemu with -enable-kvm -cpu host -smp 4 (basically as replacement and addition to the above cmdline) the CPUID leaf shows: EAX: 0x3024, EBX: 0x1001000, ECX: 0x0, EDX: 0x0
+Note, ECX is zero. Indicating that this is no SMP capabale CPU.
+
+I'm debugging it using my local machine and the QEMU provided EPYC-v2 CPU model and it is reproducible there as well and reports:  EAX: 0x3028, EBX: 0x0, ECX: 0x0, EDX: 0x0
+
+I checked other AMD based CPU models (phenom, opteron_g3/g5) and they behave the same. [2] shows the CPUID 0x8000'0008 handling in the QEMU source.
+I believe that behavior here is wrong as ECX[NC] should report the number of cores per processor, as stated in the AMD manual [2] p.584. In my understanding -smp 4 should then lead to ECX[NC] = 0x3.
+
+The following table shows my findings with the -smp option:
+Option | Qemu guest observed ECX value
+-smp 4 | 0x0
+-smp 4,cores=4  | 0x3
+-smp 4,cores=2,thread=2 | 0x3
+-smp 4,cores=4,threads=2 | QEMU boot error: topology false.
+
+Now, I'm asking myself how the terminology of the AMD manual maps to QEMU's -smp option.
+Obviously, nr_cores and nr_threads correspond to the cores and threads options on the cmdline and cores * threads <= 4 (in this example), but what corresponds the X in -smp X to?
+
+Querying 0x8000'0008 on the physical processor results in different reports than quering QEMU's model as does it with -enable-kvm -cpu host.
+
+Furthermore, the ACPI.MADT shows 4 local APICs to be present while the CPU leave reports a single core processor.
+
+This leads me to the conclusion that CPUID 0x8000'0008.ECX reports the wrong number.
+
+
+Please let me know, if you need more information from my side.
+
+
+[0] https://github.com/kernkonzept/fiasco/blob/522ccc5f29ab120213cf02d71328e2b879cbbd19/src/kern/ia32/kernel_thread-ia32.cpp#L109
+[1] https://github.com/kernkonzept/fiasco/blob/522ccc5f29ab120213cf02d71328e2b879cbbd19/src/kern/ia32/cpu-ia32.cpp#L1120
+[2] https://github.com/qemu/qemu/blob/f2a8261110c32c4dccd84e774d8dd7a0524e00fb/target/i386/cpu.c#L5835
+[3] https://www.amd.com/system/files/TechDocs/24594.pdf
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1872644 b/results/classifier/gemma3:12b/kernel/1872644
new file mode 100644
index 00000000..a82ab16b
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1872644
@@ -0,0 +1,37 @@
+
+MacOS host qemu-system-x86_64 -cpu host not working
+
+MacOS: 10.15.4
+uname -a: Linux door 4.15.0-96-generic #97-Ubuntu SMP Wed Apr 1 03:25:46 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
+
+I am using qemu on mac host, with ubuntu client.
+
+I used to have "-cpu host" in my qemu command as follow:-
+
+qemu-system-x86_64 \
+-no-user-config \
+-nodefaults \
+-name u64d01 \
+-show-cursor \
+-M q35,accel=hvf,usb=off,vmport=off \
+-cpu host \
+-m 8192M \
+-smp 4 \
+-rtc base=utc,clock=host \
+-device virtio-blk-pci,drive=ssd1 \
+-drive id=ssd1,file=/Users/js/code/vm/qemu/u64d01.qcow2,if=none,format=qcow2 \
+-device virtio-net-pci,netdev=nic1,mac=52:54:98:76:54:33 \
+-netdev user,id=nic1,ipv4=on,ipv6=on,hostname=u64d01,hostfwd=tcp::2222-:22 \
+-device virtio-tablet-pci \
+-device virtio-vga \
+-device ich9-intel-hda,id=snd,msi=on \
+-device hda-output,id=snd-codec0,bus=snd.0,cad=0,audiodev=snd0 \
+-audiodev coreaudio,id=snd0
+
+Base on log of one of the vm, it was definitely working on 2020-01-17(base on journal inside vm), with qemu 4.2.0, which I installed with brew.
+
+The only way to make it work is to remove "-cpu host".
+
+Already tried with 4.1.1, 4.2 and 5.0rc2. Same result.
+
+To reproduce, try above with a Ubuntu 18.04 installation cd. Client will crash during kernel loading.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1875702 b/results/classifier/gemma3:12b/kernel/1875702
new file mode 100644
index 00000000..b29ee7b0
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1875702
@@ -0,0 +1,8 @@
+
+madvise reports success, but doesn't implement WIPEONFORK.
+
+The implementation of madvise (linux-user/syscall.c:11331, tag v5.0.0-rc4) always returns zero (i.e. success). However, an application requesting (at least) MADV_WIPEONFORK may need to know whether the call was actually successful. If not (because the kernel doesn't support WIPEONFORK) then it will need to take other measures to provide fork-safety (such as drawing entropy from the kernel in every case). But, if the application believes that WIPEONFORK is supported (because madvise returned zero), but it actually isn't (as in qemu), then it may forego those protections on the assumption that WIPEONFORK will provide fork-safety.
+
+Roughly, the comment in qemu that says "This is a hint, so ignoring and returning success is ok." is no longer accurate in the presence of MADV_WIPEONFORK.
+
+(This is not purely academic: BoringSSL is planning on acting in this way. We found the qemu behaviour in pre-release testing and are planning on making an madvise call with advice=-1 first to test whether unknown advice values actually produce EINVAL.)
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1876568 b/results/classifier/gemma3:12b/kernel/1876568
new file mode 100644
index 00000000..452a2634
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1876568
@@ -0,0 +1,18 @@
+
+"semtimedop" implementation missing in qemu?
+
+I was trying to do an ARMv6 cross compile with qemu-user-static when I ran into this:
+
+https://travis-ci.com/github/VDR4Arch/vdr4arch/jobs/326884620#L1596
+
+I was close to giving up when I found the following:
+
+https://github.com/osrf/multiarch-docker-image-generation/issues/36
+
+Most important comment may be this one:
+
+https://github.com/osrf/multiarch-docker-image-generation/issues/36#issuecomment-610626796
+
+> The "correct" way to fix this does seem to be to implement semtimedop in qemu.
+
+I don't know how much involved the people, discussing there, are in the qemu development but I thought it may be a good idea to bring this to your attention. If this is already fixed (I haven't found any bug about "semtimedop"), then please just close this one and tell me in which version the fix will be included.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1877706 b/results/classifier/gemma3:12b/kernel/1877706
new file mode 100644
index 00000000..f651f7ac
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1877706
@@ -0,0 +1,25 @@
+
+ [Feature request] qemu does not support for Octeon MIPS64 on X86
+
+Description of problem:
+
+I use mips64-octeon-linux-gnu-gcc cross toolchain on X86,and generate binary file.
+
+> mips64-octeon-linux-gnu-gcc hello.c -static
+> file a.out
+> a.out: ELF 32-bit MSB executable, MIPS, N32 MIPS64 rel2 version 1 (SYSV), statically linked, for GNU/Linux 2.4.0, not stripped
+
+I execute it with mips64-linux-user mode in qemu, it is invalid.
+
+> ./qemu-5.0.0/mips64-linux-user/qemu-mips64 a.out
+> a.out: Invalid ELF image for this architecture
+
+when I choose mips-linux-user mode, it regards as illegal instruction.
+
+> ./qemu-5.0.0/mips-linux-user/qemu-mips a.out
+> qemu: uncaught target signal 4 (Illegal instruction) - core dumped
+> Illegal instruction (core dumped)
+
+I would like to know, is this due to my problem or does qemu not support Octeon MIPS64 on X86?
+
+if qemu has supported Octeon MIPS64 on X86, how can I emulate it.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1878 b/results/classifier/gemma3:12b/kernel/1878
new file mode 100644
index 00000000..eefe1adb
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1878
@@ -0,0 +1,30 @@
+
+QEMU doesn't implement ARMv4/v5 legacy SCTLR.U==0 load-and-rotate unaligned access handling
+Description of problem:
+**ldr r7, \[r0, r1\]** works differently on real device and QEMU. Probably all **ldr Rd, \[Rs\]** commands works wrongly in QEMU with Raspberry Pi emulation.
+Steps to reproduce:
+1. Launch the attached software **kernel_qemu.img** in QEMU.
+2. Launch the attached software **kerenel.img** on real Raspberry Pi 1B+.
+3. Look at the r7. It contains different data.
+Additional information:
+**kernel_qemu.img** and **kerenel.img** are the same program. It just compiled with different origins - 0x8000 for real device and 0x10000 for QEMU. But code inside the program works at the same addresses.
+
+r0 = 0x183a4
+
+r1 = 0x817
+
+**\[r0, r1\]** points to byte 0x42 in memory with such data:
+
+**0x80 0x15 0x22 \[0x42\] 0x03 0x21 0x87**
+
+After **ldr r7, \[r0, r1\]** execution real device puts to r7: **0x22158042**
+
+After **ldr r7, \[r0, r1\]** execution QEMU puts to r7: **0x87210342**
+
+QEMU:
+
+![QEMU.png](/uploads/51ecbf1689d36f969cb482f2613ccb58/QEMU.png)
+
+Real Raspberry Pi 1B+: ![real.jpg](/uploads/2a9cc3f4bc33d7f254c549e5086070a7/real.jpg)
+
+[kernel_qemu.img](/uploads/ae6a7490660569d5fe56adc9f4dde85d/kernel_qemu.img) [kernel.img](/uploads/48c94a66370c1fe8720fe89603c45c7b/kernel.img)
diff --git a/results/classifier/gemma3:12b/kernel/1878413 b/results/classifier/gemma3:12b/kernel/1878413
new file mode 100644
index 00000000..18f37282
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1878413
@@ -0,0 +1,16 @@
+
+/proc/sys/fs/binfmt_misc/ empty even though binfmt_misc is loaded
+
+_apksigner_ uses binfmt to execute via _jarwrapper_, since it is a JAR.  We have a test suite that relies on _apksigner_ working.  It was running fine in Ubuntu/bionic.  Since it was pegged to LTS, it got upgraded to Ubuntu/focal and it stopped working.  This is likely because /proc/sys/fs/binfmt_misc/ is totally empty.  The "binfmt_misc" kernel module shows as loaded:
+
+$ grep binfmt /proc/modules
+binfmt_misc 20480 1 - Live 0xffffffffc0452000
+
+This relies on binfmt support in gitlab.com's CI runner setup, based on Docker.  binfmt works in containers there, for example on Ubuntu/bionic:
+https://gitlab.com/fdroid/fdroidserver/-/jobs/516857857
+
+Something in Ubuntu/focal broke this when running focal in the container on the same Docker host runners:
+https://gitlab.com/fdroid/fdroidserver/-/jobs/547148092
+
+Debian's ci.debian.net lxc runners also have a similar problem, it might be related:
+https://salsa.debian.org/ci-team/debian-ci-config/-/issues/1
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1878501 b/results/classifier/gemma3:12b/kernel/1878501
new file mode 100644
index 00000000..c73fecc5
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1878501
@@ -0,0 +1,32 @@
+
+qemu-i386 does not define AT_SYSINFO
+
+qemu-i386 does not define the AT_SYSINFO auxval when running i386 Linux binaries.
+
+On most libcs, this is properly handled, but this is mandatory for the i686 Bionic (Android) libc or it will segfault.
+
+This is due to a blind assumption that getauxval(AT_SYSINFO) will return a valid function pointer:
+
+The code varies from version to version, but it looks like this:
+
+void *__libc_sysinfo;
+// mangled as _Z19__libc_init_sysinfov
+void __libc_init_sysinfo() {
+  bool dummy;
+  // __bionic_getauxval = getauxval
+  __libc_sysinfo = reinterpret_cast<void *>(__bionic_getauxval(AT_SYSINFO, dummy));
+}
+
+A simple way to reproduce is to compile a basic C program against the NDK:
+
+int main(void) { return 0; }
+
+$ i686-linux-android-clang -static empty.c -o empty
+$ qemu-i386 -cpu max ./empty
+qemu: uncaught target signal 11 (Segmentation fault) - core dumped
+Segmentation fault
+
+The place where it segfaults is misleading: It will, at least on the current NDK, crash on __set_thread_area, this is due to it calling a function pointer to __libc_sysinfo returned by __kernel_syscall.
+
+QEMU 4.1.1 (aarch64)
+Pixel 2 XL via Termux
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1878628 b/results/classifier/gemma3:12b/kernel/1878628
new file mode 100644
index 00000000..36a72aea
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1878628
@@ -0,0 +1,9 @@
+
+linux-user/mmap build failure using Clang 10
+
+When building with Clang 10 on Fedora 32, we get:
+
+    CC      linux-user/mmap.o
+  linux-user/mmap.c:720:49: error: result of comparison 'unsigned long' > 18446744073709551615 is always false [-Werror,-Wtautological-type-limit-compare]
+          if ((unsigned long)host_addr + new_size > (abi_ulong)-1) {
+              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~~~~~~~~~~~~~
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1881506 b/results/classifier/gemma3:12b/kernel/1881506
new file mode 100644
index 00000000..2c71872c
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1881506
@@ -0,0 +1,6 @@
+
+TCG doesn't support a lot of features that should be supported
+
+This is quite odd, and I'm not sure about how to get around it. I'm writing an OS in Rust and require APIC support. When I boot my kernel with qemu-system-x86_64, however, it dumps out a [lot] of warnings; it claims that TCG doesn't support FMA, X2APIC, AVX, F16C, AVX2, RDSEED, SHA-NI, FXSR-OPT, misalignsse, 3dnowprefetch, osvw, topoext, perfctr-core, clzero, xsaveerptr, ibpb, nrip-save, xsavec, and xsaves, but prints these warnings over 80 times before finally doing what I told it to do. Running QEMU 5.0.0 (unknown commit hash), as follows:
+qemu-system-x86_64 -drive format=raw,file=target\x86_64-kernel-none\debug\bootimage-kernel.bin -serial stdio -no-reboot -hdb disk.img -s -m 4G -usb -rtc base=utc,clock=host -cpu EPYC-v3,+acpi,+apic,+rdrand,+rdseed,+sse,+sse2,+sse4.1,+sse4.2,+sse4a,+ssse3,+syscall,+x2apic -smp cpus=8 -soundhw all
+I would run using HAXM, but my kernel requires RDRAND, and QEMU does not, to my knowledge, automatically support RDRAND (and I don't know how to enable it).
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1882123 b/results/classifier/gemma3:12b/kernel/1882123
new file mode 100644
index 00000000..0f4ff6b8
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1882123
@@ -0,0 +1,59 @@
+
+ARM cpu emulation regression on QEMU 4.2.0
+
+[*] Summary
+
+Latest QEMU has an ARM CPU emulation regression.
+Regression is reproducible by building any C# project with .NET Core SDK 3.1.300 on Debian 10 armhf.
+
+Affected releases: QEMU 4.2.0, 5.0.0
+Not affected releases: QEMU 4.1.0, QEMU 4.1.1
+
+
+[*] Detail
+
+qemu-system-arm fails to run .NET Core SDK 3.1 on Debian 10 armhf.
+
+I occasionally test my C# projects on the virtual armhf/arm64 system emulated by QEMU.
+MSBuild, a build engine of the .NET Core SDK, crashes on QEMU 4.2.0 or later.
+The crash only happens when MSBuild tries to do any JIT compiling (dotnet build / dotnet test).
+
+I attached MSBuild crash logs. MSBuild always crashes with SEHException, which means it tried to call C binary from .NET binary.
+
+The issue affects QEMU 4.2.0 and 5.0.0.
+QEMU 4.1.0, 4.1.1, and real Raspberry Pi 2 machine is not affected by this issue, and .NET Core SDK works completely fine.
+Thus, I think an ARM CPU regression happened between QEMU 4.1.1 ~ QEMU 4.2.0.
+
+
+[*] Environment
+
+[Host OS]
+Distribution: Linux Mint 19.3 amd64
+CPU: AMD Ryzen 5 3600
+Kernel: Ubuntu 5.3.0-51-generic
+
+[QEMU Arguments]
+qemu-system-arm \
+    -smp 3 -M virt -m 4096 \
+    -kernel vmlinuz-4.19.0-9-armmp-lpae \
+    -initrd initrd.img-4.19.0-9-armmp-lpae \
+    -append "root=/dev/vda2" \
+    -drive if=none,file=debian_arm.qcow2,format=qcow2,id=hd \
+    -device virtio-blk-device,drive=hd \
+    -netdev user,id=mynet,hostfwd=tcp::<PORT>-:22 \
+    -device virtio-net-device,netdev=mynet \
+    -device virtio-rng-device\
+
+[QEMU Guest OS]
+Distribution: Debian 10 Buster armhf
+Kernel: Debian 4.19.0-9-armmp-lpae
+.NET Core SDK: 3.1.300
+
+[Raspberry Pi 2]
+Distribution: Raspberry Pi OS Buster armhf (20200527)
+
+[Tested C# Projects]
+This is a list of C# projects I have tested on QEMU and RPI2. 
+- https://github.com/ied206/Joveler.DynLoader
+- https://github.com/ied206/Joveler.Compression
+- https://github.com/ied206/ManagedWimLib
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1886155 b/results/classifier/gemma3:12b/kernel/1886155
new file mode 100644
index 00000000..6937485c
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1886155
@@ -0,0 +1,56 @@
+
+error: argument 2 of ‘__atomic_load’ discards ‘const’ qualifier
+
+GCC 11 reports the following errors:
+
+[  125s] In file included from /home/abuild/rpmbuild/BUILD/qemu-5.0.0/include/qemu/seqlock.h:17,
+[  125s]                  from /home/abuild/rpmbuild/BUILD/qemu-5.0.0/include/qemu/qht.h:10,
+[  125s]                  from /home/abuild/rpmbuild/BUILD/qemu-5.0.0/util/qht.c:69:
+[  125s] /home/abuild/rpmbuild/BUILD/qemu-5.0.0/util/qht.c: In function 'qht_do_lookup':
+[  125s] /home/abuild/rpmbuild/BUILD/qemu-5.0.0/include/qemu/atomic.h:153:5: error: argument 2 of '__atomic_load' discards 'const' qualifier [-Werror=incompatible-pointer-types]
+[  125s]   153 |     __atomic_load(ptr, valptr, __ATOMIC_RELAXED);       \
+[  125s]       |     ^~~~~~~~~~~~~
+[  125s] /home/abuild/rpmbuild/BUILD/qemu-5.0.0/include/qemu/atomic.h:161:5: note: in expansion of macro 'atomic_rcu_read__nocheck'
+[  125s]   161 |     atomic_rcu_read__nocheck(ptr, &_val);             \
+[  125s]       |     ^~~~~~~~~~~~~~~~~~~~~~~~
+[  125s] /home/abuild/rpmbuild/BUILD/qemu-5.0.0/util/qht.c:499:27: note: in expansion of macro 'atomic_rcu_read'
+[  125s]   499 |                 void *p = atomic_rcu_read(&b->pointers[i]);
+[  125s]       |                           ^~~~~~~~~~~~~~~
+[  125s] /home/abuild/rpmbuild/BUILD/qemu-5.0.0/include/qemu/atomic.h:153:5: error: argument 2 of '__atomic_load' discards 'const' qualifier [-Werror=incompatible-pointer-types]
+[  125s]   153 |     __atomic_load(ptr, valptr, __ATOMIC_RELAXED);       \
+[  125s]       |     ^~~~~~~~~~~~~
+[  125s] /home/abuild/rpmbuild/BUILD/qemu-5.0.0/include/qemu/atomic.h:161:5: note: in expansion of macro 'atomic_rcu_read__nocheck'
+[  125s]   161 |     atomic_rcu_read__nocheck(ptr, &_val);             \
+[  125s]       |     ^~~~~~~~~~~~~~~~~~~~~~~~
+[  125s] /home/abuild/rpmbuild/BUILD/qemu-5.0.0/util/qht.c:506:13: note: in expansion of macro 'atomic_rcu_read'
+[  125s]   506 |         b = atomic_rcu_read(&b->next);
+[  125s]       |             ^~~~~~~~~~~~~~~
+[  125s] /home/abuild/rpmbuild/BUILD/qemu-5.0.0/util/qht.c: In function 'qht_lookup_custom':
+[  125s] /home/abuild/rpmbuild/BUILD/qemu-5.0.0/include/qemu/atomic.h:153:5: error: argument 2 of '__atomic_load' discards 'const' qualifier [-Werror=incompatible-pointer-types]
+[  125s]   153 |     __atomic_load(ptr, valptr, __ATOMIC_RELAXED);       \
+[  125s]       |     ^~~~~~~~~~~~~
+[  125s] /home/abuild/rpmbuild/BUILD/qemu-5.0.0/include/qemu/atomic.h:161:5: note: in expansion of macro 'atomic_rcu_read__nocheck'
+[  125s]   161 |     atomic_rcu_read__nocheck(ptr, &_val);             \
+[  125s]       |     ^~~~~~~~~~~~~~~~~~~~~~~~
+[  125s] /home/abuild/rpmbuild/BUILD/qemu-5.0.0/util/qht.c:534:11: note: in expansion of macro 'atomic_rcu_read'
+[  125s]   534 |     map = atomic_rcu_read(&ht->map);
+[  125s]       |           ^~~~~~~~~~~~~~~
+[  125s] /home/abuild/rpmbuild/BUILD/qemu-5.0.0/util/qht.c: In function 'qht_statistics_init':
+[  125s] /home/abuild/rpmbuild/BUILD/qemu-5.0.0/include/qemu/atomic.h:153:5: error: argument 2 of '__atomic_load' discards 'const' qualifier [-Werror=incompatible-pointer-types]
+[  125s]   153 |     __atomic_load(ptr, valptr, __ATOMIC_RELAXED);       \
+[  125s]       |     ^~~~~~~~~~~~~
+[  125s] /home/abuild/rpmbuild/BUILD/qemu-5.0.0/include/qemu/atomic.h:161:5: note: in expansion of macro 'atomic_rcu_read__nocheck'
+[  125s]   161 |     atomic_rcu_read__nocheck(ptr, &_val);             \
+[  125s]       |     ^~~~~~~~~~~~~~~~~~~~~~~~
+[  125s] /home/abuild/rpmbuild/BUILD/qemu-5.0.0/util/qht.c:907:11: note: in expansion of macro 'atomic_rcu_read'
+[  125s]   907 |     map = atomic_rcu_read(&ht->map);
+[  125s]       |           ^~~~~~~~~~~~~~~
+[  125s] /home/abuild/rpmbuild/BUILD/qemu-5.0.0/include/qemu/atomic.h:153:5: error: argument 2 of '__atomic_load' discards 'const' qualifier [-Werror=incompatible-pointer-types]
+[  125s]   153 |     __atomic_load(ptr, valptr, __ATOMIC_RELAXED);       \
+[  125s]       |     ^~~~~~~~~~~~~
+[  125s] /home/abuild/rpmbuild/BUILD/qemu-5.0.0/include/qemu/atomic.h:161:5: note: in expansion of macro 'atomic_rcu_read__nocheck'
+[  125s]   161 |     atomic_rcu_read__nocheck(ptr, &_val);             \
+[  125s]       |     ^~~~~~~~~~~~~~~~~~~~~~~~
+[  125s] /home/abuild/rpmbuild/BUILD/qemu-5.0.0/util/qht.c:941:21: note: in expansion of macro 'atomic_rcu_read'
+[  125s]   941 |                 b = atomic_rcu_read(&b->next);
+[  125s]       |                     ^~~~~~~~~~~~~~~
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1887854 b/results/classifier/gemma3:12b/kernel/1887854
new file mode 100644
index 00000000..dbe0da7a
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1887854
@@ -0,0 +1,24 @@
+
+Spurious Data Abort on qemu-system-aarch64
+
+When running RTEMS test psxndbm01.exe built for AArch64-ilp32 (this code is not yet publically available), the test generates a spurious data abort (the MMU and alignment checks should be disabled according to bits 1, 0 of SCTLR_EL1). The abort information is as follows:
+Taking exception 4 [Data Abort]
+...from EL1 to EL1
+...with ESR 0x25/0x96000010
+...with FAR 0x104010ca28
+...with ELR 0x400195d8
+...to EL1 PC 0x40018200 PSTATE 0x3c5
+
+The ESR indicates that a synchronous external abort has occurred.
+ESR EC field: 0b100101
+
+From the ARMv8 technical manual: Data Abort taken without a change in Exception level. Used for MMU faults generated by data accesses, alignment faults other than those caused by Stack Pointer misalignment, and synchronous External aborts, including synchronous parity or ECC errors. Not used for debug related exceptions.
+
+ESR ISS field: 0b10000
+
+From the ARMv8 technical manual: Synchronous External abort, not on translation table walk or hardware update of translation table.
+
+The following command line is used to invoke qemu:
+qemu-system-aarch64 -machine virt -cpu cortex-a53 -m 256M -no-reboot -nographic -serial mon:stdio -kernel build/aarch64/a53_ilp32_qemu/testsuites/psxtests/psxndbm01.exe -D qemu.log -d in_asm,int,cpu_reset,unimp,guest_errors
+
+This occurs on Qemu 3.1.0 as distributed via Debian and on Qemu 4.1 as built by the RTEMS source builder (4.1+minor patches).
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1888431 b/results/classifier/gemma3:12b/kernel/1888431
new file mode 100644
index 00000000..0e64e13e
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1888431
@@ -0,0 +1,53 @@
+
+v5.1.0-rc1 build fails on Mac OS X 10.11.6 
+
+Hi all, 
+
+build of tag v5.1.0-rc1 fails on Mac OS X 10.11.6 (El Capitan) with the following error:
+
+git clone https://git.qemu.org/git/qemu.git
+    <output elided, but all OK>
+cd qemu
+git submodule init
+    <output elided, but all OK>
+git submodule update --recursive
+    <output elided, but all OK>
+./configure
+    <output elided, but all OK>
+make
+    <output elided, but all OK up until fail>
+
+  CC      trace/control.o
+In file included from trace/control.c:29:
+In file included from /Users/rtb/src/qemu/include/monitor/monitor.h:4:
+In file included from /Users/rtb/src/qemu/include/block/block.h:4:
+In file included from /Users/rtb/src/qemu/include/block/aio.h:23:
+/Users/rtb/src/qemu/include/qemu/timer.h:843:9: warning: implicit declaration of function 'clock_gettime' is invalid in C99
+      [-Wimplicit-function-declaration]
+        clock_gettime(CLOCK_MONOTONIC, &ts);
+        ^
+/Users/rtb/src/qemu/include/qemu/timer.h:843:23: error: use of undeclared identifier 'CLOCK_MONOTONIC'
+        clock_gettime(CLOCK_MONOTONIC, &ts);
+                      ^
+1 warning and 1 error generated.
+make: *** [trace/control.o] Error 1
+
+
+rtb:qemu rtb$ git log -n1
+commit c8004fe6bbfc0d9c2e7b942c418a85efb3ac4b00 (HEAD -> master, tag: v5.1.0-rc1, origin/master, origin/HEAD)
+Author: Peter Maydell <email address hidden>
+Date:   Tue Jul 21 20:28:59 2020 +0100
+
+    Update version for v5.1.0-rc1 release
+    
+    Signed-off-by: Peter Maydell <email address hidden>
+rtb:qemu rtb$ 
+
+
+Please find the full output of all the commands (from git clone of the repo, to the make) in the attached file "buildfail.txt".
+
+Thank you!
+
+Best regards, 
+
+Robert Ball
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1894361 b/results/classifier/gemma3:12b/kernel/1894361
new file mode 100644
index 00000000..085c19b1
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1894361
@@ -0,0 +1,6 @@
+
+linux-user: syscall.c lacks pselect6_time64
+
+in commit 50efc69586388a975c1ebd90cb8cc8e4a7328bc4 legacy pselect6 definition
+for riscv32 was removed in favour of pselect6_time64, but pselect6_time64 is
+not available in syscall.c, thus leaving riscv32 without pselect syscall.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1895053 b/results/classifier/gemma3:12b/kernel/1895053
new file mode 100644
index 00000000..0243f917
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1895053
@@ -0,0 +1,35 @@
+
+Cannot nspawn raspbian 10 [FAILED] Failed to start Journal Service.
+
+Hi, I'm using nspawn and asked the question @systemd-devel. They redirected me to you, guessing that nspawn calls a syscall or ioctl qemu isnt aware of and can't implement properly?
+They were like: "Sorry, that's not my department." ^^
+
+Maybe you can reproduce the issue or help me investigating whats wrong or put the ball right back into their court? :D
+
+From:	"chiasa.men" <email address hidden>
+To:	<email address hidden>
+Date:	09.09.20 14:20
+(cf. https://github.com/systemd/systemd/issues/16975)
+
+Testscript:
+wget https://downloads.raspberrypi.org/raspios_lite_armhf_latest -o r.zip
+unzip r.zip
+LOOP=$(losetup --show -Pf *raspios-buster-armhf-lite.img)
+mount ${LOOP}p2 /mnt
+mount ${LOOP}p1 /mnt/boot
+systemd-nspawn --bind /usr/bin/qemu-arm-static --boot --directory=/mnt -- systemd.log_level=debug
+
+
+Output:
+see attachment
+
+System:
+uname -a
+Linux MArch 5.8.7-arch1-1 #1 SMP PREEMPT Sat, 05 Sep 2020 12:31:32 +0000 
+x86_64 GNU/Linux
+
+systemd-nspawn --version 
+systemd 246 (246.4-1-arch)
++PAM +AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP 
++GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN 
++PCRE2 default-hierarchy=hybrid
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1895080 b/results/classifier/gemma3:12b/kernel/1895080
new file mode 100644
index 00000000..51efea60
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1895080
@@ -0,0 +1,37 @@
+
+pgb_reserved_va: Assertion `addr == test' failed
+
+This problem occurs on CentOS-7.5 (64-bit) with qemu-5.1.0, qemu head (commit 9435a8b3dd35f1f926f1b9127e8a906217a5518a) for riscv32-linux-user.
+
+Firstly, compile fails:
+Compiling C object libqemu-riscv32-linux-user.fa.p/linux-user_strace.c.o
+../qemu.git/linux-user/strace.c:1210:18: error: ‘FALLOC_FL_KEEP_SIZE’ undeclared here (not in a function)
+     FLAG_GENERIC(FALLOC_FL_KEEP_SIZE),
+
+I have to add below include to linux-user/strace.c
+diff --git a/linux-user/strace.c b/linux-user/strace.c
+index 11fea14fba..22e51d4a8a 100644
+--- a/linux-user/strace.c
++++ b/linux-user/strace.c
+@@ -7,6 +7,7 @@
+ #include <sys/mount.h>
+ #include <arpa/inet.h>
+ #include <netinet/tcp.h>
++#include <linux/falloc.h>
+ #include <linux/if_packet.h>
+ #include <linux/netlink.h>
+ #include <sched.h>
+
+Then trying qemu-riscv32 with a simple ELF, I get:
+linux-user/elfload.c:2341: pgb_reserved_va: Assertion `addr == test' failed.
+
+strace shows that:
+mmap(0x1000, 4294963200, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_NORESERVE, -1, 0) = 0x10000
+write(2, "qemu-riscv32: ../qemu.git/linux-"..., 103qemu-riscv32: ../qemu.git/linux-user/elfload.c:2341: pgb_reserved_va: Assertion `addr == test' failed.
+) = 103
+
+The source code is in the function pgb_reserved_va (linux-user/elfload.c). I think mmap cannot guarantee that the returned pointer (test) equals to the parameter of addr. So is this a bug to assert (addr == test)?
+
+Attached configure script and test ELF file.
+
+Thanks.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1897194 b/results/classifier/gemma3:12b/kernel/1897194
new file mode 100644
index 00000000..e9d30d54
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1897194
@@ -0,0 +1,12 @@
+
+Test failure in test-crypto-secret.c
+
+When running qemu test suite I'm seeing a test failure:
+
+ERROR:../qemu/tests/test-crypto-secret.c:144:test_secret_keyring_good: assertion failed: (key >= 0)
+
+Host is Arch Linux running in the standard Arch build environment (essentially an nspawn container).
+
+I first noticed this at release of 5.1.0 but it's still there on current trunk. For 5.1.0 I was able to sidestep the issue by building with `--disable-keyring' but this no longer works (I think due to 9866a33cbb7046891dec3dcc9ca2015828673afe)
+
+Any clues on what might be the cause? Not sure how to debug.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1898954 b/results/classifier/gemma3:12b/kernel/1898954
new file mode 100644
index 00000000..b95dfb21
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1898954
@@ -0,0 +1,28 @@
+
+x86 f1 opcode hangs qemu
+
+I have qemu installed and running in linux and windows
+in linux i execute the following simple code in real mode of cpu in my vm
+90 nop
+90 nop
+90 nop
+f1         ;this should conjure up my interrupt handler from ivt int 1
+--------- end of code ----
+it works properly in vbox,qemu linux,and even in my boot loder
+on a real platform
+   it doeas not work fine in windows 10 (32 bit efi) based qemu
+---
+all of the below was retyped there may be typo
+so onwards to the flawed software 
+********** for qemu-system-x86_64.exe **********
+info version 
+4.2.0v4.2.0.11797-g2890edc853-dirty
+********** for qemu-system-i386.exe **********
+info version 
+4.2.0v4.2.0.11797-g2890edc853-dirty
+***********************************************
+my startup code is
+"d:\programs\qemu\qemu-system-x86_64.exe" -m 16M -boot a -fda "d:\floppy.img" -cpu Nehalem -machine pc
+---
+also same flaw if i change above section to
+"d:\programs\qemu\qemu-system-i386.exe"
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1899082 b/results/classifier/gemma3:12b/kernel/1899082
new file mode 100644
index 00000000..85136efe
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1899082
@@ -0,0 +1,35 @@
+
+ReplayKernel.test_x86_64_pc fails intermittently
+
+Even though this acceptance test is already skipped on GitLab CI, the intermittent failures can be seen on other environments too.
+
+The record phase works fine, but during the replay phase fail to finish booting the kernel (until the expected place):
+
+16:34:47 DEBUG| [    0.034498] Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0, 1GB 0
+16:34:47 DEBUG| [    0.034790] Spectre V2 : Spectre mitigation: LFENCE not serializing, switching to generic retpoline
+16:34:47 DEBUG| [    0.035093] Spectre V2 : Mitigation: Full generic retpoline
+16:34:47 DEBUG| [    0.035347] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
+16:34:47 DEBUG| [    0.035667]
+16:36:02 ERROR| 
+16:36:02 ERROR| Reproduced traceback from: /home/cleber/src/avocado/avocado/avocado/core/test.py:767
+16:36:02 ERROR| Traceback (most recent call last):
+16:36:02 ERROR|   File "/var/lib/users/cleber/build/qemu/tests/acceptance/replay_kernel.py", line 92, in test_x86_64_pc
+16:36:02 ERROR|     self.run_rr(kernel_path, kernel_command_line, console_pattern, shift=5)
+16:36:02 ERROR|   File "/var/lib/users/cleber/build/qemu/tests/acceptance/replay_kernel.py", line 73, in run_rr
+16:36:02 ERROR|     False, shift, args, replay_path)
+16:36:02 ERROR|   File "/var/lib/users/cleber/build/qemu/tests/acceptance/replay_kernel.py", line 55, in run_vm
+16:36:02 ERROR|     self.wait_for_console_pattern(console_pattern, vm)
+16:36:02 ERROR|   File "/var/lib/users/cleber/build/qemu/tests/acceptance/boot_linux_console.py", line 53, in wait_for_console_pattern
+16:36:02 ERROR|     vm=vm)
+16:36:02 ERROR|   File "/var/lib/users/cleber/build/qemu/tests/acceptance/avocado_qemu/__init__.py", line 130, in wait_for_console_pattern
+16:36:02 ERROR|     _console_interaction(test, success_message, failure_message, None, vm=vm)
+16:36:02 ERROR|   File "/var/lib/users/cleber/build/qemu/tests/acceptance/avocado_qemu/__init__.py", line 82, in _console_interaction
+16:36:02 ERROR|     msg = console.readline().strip()
+16:36:02 ERROR|   File "/usr/lib64/python3.7/socket.py", line 575, in readinto
+16:36:02 ERROR|     def readinto(self, b):
+16:36:02 ERROR|   File "/home/cleber/src/avocado/avocado/avocado/plugins/runner.py", line 77, in sigterm_handler
+16:36:02 ERROR|     raise RuntimeError("Test interrupted by SIGTERM")
+16:36:02 ERROR| RuntimeError: Test interrupted by SIGTERM
+16:36:02 ERROR| 
+
+On my workstation, I can replicate the failure roughly once every 50 runs.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1900 b/results/classifier/gemma3:12b/kernel/1900
new file mode 100644
index 00000000..a5625f66
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1900
@@ -0,0 +1,2 @@
+
+8.1.0-r1: segfault at get_zones_wp() at ../block/file-posix.c:1337
diff --git a/results/classifier/gemma3:12b/kernel/1902267 b/results/classifier/gemma3:12b/kernel/1902267
new file mode 100644
index 00000000..adc58e9a
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1902267
@@ -0,0 +1,32 @@
+
+CPU not support 32-bit stack in 32-bit unreal mode
+
+QEMU version 5.0.0 supports 32-bit and 16-bit unreal mode. Great!
+Unfortunately, QEMU does not support 32-bit stack in unreal 32-bit mode.
+After the INT instruction, the stack is switched to 16-bit, which should not be the case. 
+At BOCHS, my code works 100%. At QEMU not works.
+
+Sample code to find out:
+
+use32
+cli
+mov ax,cs
+shl eax,16
+mov ax,NewInt80h
+mov [IDT32+4*80h],eax
+mov edx,esp
+mov esp,0x10000
+int 80h
+NewInt80h:
+xchg esp,edx
+cmp edx,0x10000-6
+jnz IsStack16Bit
+
+Stack selector loaded from GDT:
+GDT:
+real32_GDT            
+dq 0
+dw 0xFFFF,0x0000,9A00h,0xCF     ; 32-bit code descriptor
+dw 0xFFFF,0x0000,9200h,0x8F     ;   4 GB data descriptor
+dw 0xFFFF,0x0000,9A00h,0x00     ; 16-bit code descriptor
+dw 0xFFFF,0x0000,9200h,0xCF     ; 32-bit data descriptor stack
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1904464 b/results/classifier/gemma3:12b/kernel/1904464
new file mode 100644
index 00000000..1ae0eeef
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1904464
@@ -0,0 +1,18 @@
+
+Build fails with 64 bits time_t
+
+time element is deprecated on new input_event structure in kernel's
+input.h [1]
+
+This will avoid the following build failure:
+
+hw/input/virtio-input-host.c: In function 'virtio_input_host_handle_status':
+hw/input/virtio-input-host.c:198:28: error: 'struct input_event' has no member named 'time'
+  198 |     if (gettimeofday(&evdev.time, NULL)) {
+      |                            ^
+
+Fixes:
+ - http://autobuild.buildroot.org/results/a538167e288c14208d557cd45446df86d3d599d5
+ - http://autobuild.buildroot.org/results/efd4474fb4b6c0ce0ab3838ce130429c51e43bbb
+
+[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=152194fe9c3f
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1906156 b/results/classifier/gemma3:12b/kernel/1906156
new file mode 100644
index 00000000..1c1fbef9
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1906156
@@ -0,0 +1,16 @@
+
+Host OS Reboot Required, for Guest kext to Load (Fully)
+
+Hi,
+
+Finding this one a bit odd, but I am loading a driver (kext) in a macOS guest ... and it works, on the first VM (domain) startup after a full / clean host OS boot (or reboot). However, if I even reboot the guest OS, then the driver load fails => can be "corrected" by a full host OS reboot (which seems very extreme).
+
+Is this a known issue, and/or is there a workaround?
+
+FYI, running,
+QEMU emulator version 5.0.0 (Debian 1:5.0-5ubuntu9.1)
+Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers
+
+This is for a macOS guest, on a Linux host.
+
+Thanks!
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1907 b/results/classifier/gemma3:12b/kernel/1907
new file mode 100644
index 00000000..25ee92bd
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1907
@@ -0,0 +1,58 @@
+
+QEMU LoongArch regression after merging LASX changes
+Description of problem:
+After enabling LASX in qemu (@gaosong), booting Gentoo Linux with latest glibc master (w/ LSX & LASX optimized libc routines) will fail in systemd:
+
+```
+[   10.350207] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000085
+[   10.350557] CPU: 5 PID: 1 Comm: systemd Not tainted 6.5.2-gentoo #2
+[   10.350655] Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015
+[   10.350961] Stack : 0072617764726148 0000000000000000 9000000000223440 90000001000e4000
+[   10.351181]         90000001000e7990 90000001000e7998 0000000000000000 90000001000e7ad8
+[   10.351294]         90000001000e7ad0 90000001000e7ad0 90000001000e7900 0000000000000001
+[   10.351406]         0000000000000001 90000001000e7998 ec94a2e1446052e6 9000000100438140
+[   10.351519]         0000000000000001 0000000000000003 0000000000000000 0000000000000030
+[   10.351630]         0000000000000000 00000000000559bf 00000000056e0000 0000000000000004
+[   10.351745]         0000000000000000 0000000000000000 900000000162b438 900000000177e000
+[   10.351856]         00000000400004d8 0000000000000001 0000000000000018 90000001000e7c84
+[   10.351968]         0000000000020000 0000000000000000 9000000000223458 00007ffff0341af0
+[   10.352081]         00000000000000b0 0000000000000004 0000000000000000 0000000000071c1c
+[   10.352196]         ...
+[   10.352277] Call Trace:
+[   10.352482] [<9000000000223458>] show_stack+0x5c/0x180
+[   10.353518] [<9000000001178d4c>] dump_stack_lvl+0x60/0x88
+[   10.353592] [<900000000115cd7c>] panic+0x13c/0x308
+[   10.353670] [<900000000024244c>] do_exit+0x860/0x868
+[   10.353735] [<900000000024261c>] do_group_exit+0x34/0x94
+[   10.353803] [<9000000000250514>] get_signal+0x75c/0x804
+[   10.353869] [<90000000002254c4>] arch_do_signal_or_restart+0x74/0xae0
+[   10.353944] [<90000000002c738c>] exit_to_user_mode_loop.isra.0+0x90/0x10c
+[   10.354041] [<9000000001179ff0>] irqentry_exit_to_user_mode+0x1c/0x28
+[   10.354119] [<90000000011792f8>] do_bp+0xcc/0x2ac
+[   10.354222] [<90000001005a1924>] 0x90000001005a1924
+[   10.354522] [<00007ffff0341af0>] 0x7ffff0341af0
+```
+
+Full log:
+
+[stderr](/uploads/61b9870ae2441c9a25f44791c67889b8/stderr)
+
+Instruction trace `-d in_asm,out_asm,op` (very large):
+
+[log.tar.zstd](https://cloud.tsinghua.edu.cn/f/a83eac6d44694ede8cb1/?dl=1)
+
+I also tried to boot LoongArchLinux whose glibc does not have LSX/LASX optimized C routines, and it can boot without problems. If I chroot from LoongArchLinux into Gentoo Linux, running `emerge` command will SIGSEGV.
+
+If I disable LASX in CPUCFG2, the problem is gone:
+
+```cpp
+//     data = FIELD_DP32(data, CPUCFG2, LASX, 1),
+```
+
+I guess the bug is related to LASX assemblies in [glibc](https://github.com/bminor/glibc/tree/master/sysdeps/loongarch/lp64/multiarch).
+Steps to reproduce:
+1. Launch qemu
+2. Wait for systemd to be killed
+3. Collect logs
+Additional information:
+
diff --git a/results/classifier/gemma3:12b/kernel/1907137 b/results/classifier/gemma3:12b/kernel/1907137
new file mode 100644
index 00000000..f9a17107
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1907137
@@ -0,0 +1,37 @@
+
+LDTR not properly emulated when MTE tag checks enabled at EL0
+
+I am trying to boot Android (just the non-GUI parts for now) under QEMU with MTE enabled. This can be done by following the instructions here to build the fvp-eng target with MTE support:
+
+https://cs.android.com/android/platform/superproject/+/master:device/generic/goldfish/fvpbase/
+
+and launching QEMU with the following command:
+
+qemu-system-aarch64 -kernel $ANDROID_PRODUCT_OUT/kernel -initrd $ANDROID_PRODUCT_OUT/combined-ramdisk.img -machine virt,mte=on -cpu max -drive driver=raw,file=$ANDROID_PRODUCT_OUT/system-qemu.img,if=none,id=system -device virtio-blk-device,drive=system -append "console=ttyAMA0 earlyprintk=ttyAMA0 androidboot.hardware=fvpbase androidboot.boot_devices=a003e00.virtio_mmio loglevel=9 printk.devkmsg=on buildvariant=eng" -m 512 -nographic -no-reboot
+
+If I do this then QEMU crashes like so:
+
+**
+ERROR:../target/arm/mte_helper.c:558:mte_check_fail: code should not be reached
+Bail out! ERROR:../target/arm/mte_helper.c:558:mte_check_fail: code should not be reached
+
+The error is caused by an MTE tag check fault from an LDTR instruction in __arch_copy_from_user. At this point TCF=0 and TCF0=2.
+
+I have this patch that gets me past the error but it is unclear whether this is the correct fix since there may be other confusion between TCF and TCF0 elsewhere.
+
+diff --git a/target/arm/mte_helper.c b/target/arm/mte_helper.c
+index 153bd1e9df..aa5db4eac4 100644
+--- a/target/arm/mte_helper.c
++++ b/target/arm/mte_helper.c
+@@ -552,10 +552,8 @@ static void mte_check_fail(CPUARMState *env, uint32_t desc,
+     case 0:
+         /*
+          * Tag check fail does not affect the PE.
+-         * We eliminate this case by not setting MTE_ACTIVE
+-         * in tb_flags, so that we never make this runtime call.
+          */
+-        g_assert_not_reached();
++        break;
+ 
+     case 2:
+         /* Tag check fail causes asynchronous flag set.  */
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1907427 b/results/classifier/gemma3:12b/kernel/1907427
new file mode 100644
index 00000000..e3960b63
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1907427
@@ -0,0 +1,13 @@
+
+Build on sparc64 fails with "undefined reference to `fdt_check_full'"
+
+Trying to build QEMU on sparc64 fails with:
+
+[4648/8435] c++  -o qemu-system-ppc64 qemu-system-ppc64.p/softmmu_main.c.o libcommon.fa.p/ui_vnc-auth-sasl.c.o libcommon.fa.p/migration_colo-failover.c.o libcommon.fa.p/hw_input_vhost-user-input.c.o libcommon.fa.p/replay_replay-random.c.o libcommon.fa.p/hw_9pfs_codir.c.o libcommon.fa.p/hw_display_edid-region.c.o libcommon.fa.p/hw_net_vhost_net.c.o libcommon.fa.p/hw_isa_i82378.c.o libcommon.fa.p/backends_rng-egd.c.o libcommon.fa.p/hw_usb_core.c.o libcommon.fa.p/hw_pci-bridge_i82801b11.c.o libcommon.fa.p/net_tap.c.o libcommon.fa.p/hw_ipack_ipack.c.o libcommon.fa.p/hw_scsi_mptconfig.c.o libcommon.fa.p/hw_usb_libhw.c.o libcommon.fa.p/hw_display_sm501.c.o libcommon.fa.p/hw_net_rocker_rocker_world.c.o libcommon.fa.p/fsdev_qemu-fsdev.c.o libcommon.fa.p/backends_tpm_tpm_util.c.o libcommon.fa.p/net_tap-linux.c.o libcommon.fa.p/hw_net_rocker_rocker_fp.c.o libcommon.fa.p/hw_usb_dev-uas.c.o libcommon.fa.p/hw_net_fsl_etsec_miim.c.o libcommon.fa.p/net_queue.c.o libcommon.fa.p/hw_isa_isa-superio.c.o libcommon.fa.p/migration_global_state.c.o libcommon.fa.p/backends_rng-random.c.o libcommon.fa.p/hw_ipmi_ipmi_bmc_extern.c.o libcommon.fa.p/migration_postcopy-ram.c.o libcommon.fa.p/hw_scsi_megasas.c.o libcommon.fa.p/hw_acpi_acpi-stub.c.o libcommon.fa.p/hw_nvram_mac_nvram.c.o libcommon.fa.p/hw_net_pcnet-pci.c.o libcommon.fa.p/cpus-common.c.o libcommon.fa.p/hw_core_qdev-properties-system.c.o libcommon.fa.p/migration_colo.c.o libcommon.fa.p/ui_spice-module.c.o libcommon.fa.p/hw_usb_hcd-ehci-pci.c.o libcommon.fa.p/migration_exec.c.o libcommon.fa.p/hw_input_adb-kbd.c.o libcommon.fa.p/hw_timer_xilinx_timer.c.o libcommon.fa.p/hw_cpu_core.c.o libcommon.fa.p/chardev_msmouse.c.o libcommon.fa.p/migration_socket.c.o libcommon.fa.p/hw_9pfs_9p-synth.c.o libcommon.fa.p/backends_dbus-vmstate.c.o libcommon.fa.p/net_colo-compare.c.o libcommon.fa.p/hw_misc_macio_cuda.c.o libcommon.fa.p/hw_audio_intel-hda.c.o libcommon.fa.p/audio_audio_legacy.c.o
+(...)
+libio.fa libchardev.fa -Wl,--no-whole-archive -Wl,--warn-common -Wl,-z,relro -Wl,-z,now -m64 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,--as-needed -fstack-protector-strong libmigration.fa -Wl,--start-group libqemuutil.a contrib/libvhost-user/libvhost-user.a libqmp.fa libhwcore.fa libblockdev.fa libblock.fa libcrypto.fa libauthz.fa libqom.fa libio.fa libchardev.fa @block.syms @qemu.syms /usr/lib/gcc/sparc64-linux-gnu/10/../../../sparc64-linux-gnu/libfdt.so /usr/lib/sparc64-linux-gnu/libcapstone.so -lepoxy -lgbm /usr/lib/sparc64-linux-gnu/libpixman-1.so /usr/lib/sparc64-linux-gnu/libz.so /usr/lib/sparc64-linux-gnu/libslirp.so /usr/lib/sparc64-linux-gnu/libglib-2.0.so -lrdmacm -libverbs -libumad -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 /usr/lib/gcc/sparc64-linux-gnu/10/../../../sparc64-linux-gnu/libsasl2.so @block.syms -lusb-1.0 /lib/sparc64-linux-gnu/libudev.so /usr/lib/sparc64-linux-gnu/libpng16.so -lvdeplug /usr/lib/sparc64-linux-gnu/libjpeg.so -pthread -luring -lgnutls -lutil -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lm -Wl,--export-dynamic -lgmodule-2.0 -lglib-2.0 -laio -luring -lgnutls -lnettle -lstdc++ -Wl,--end-group
+/usr/bin/ld: libqemu-ppc64-softmmu.fa.p/hw_ppc_spapr_hcall.c.o: in function `h_update_dt':
+./b/qemu/../../hw/ppc/spapr_hcall.c:1966: undefined reference to `fdt_check_full'
+collect2: error: ld returned 1 exit status
+
+Full build log available at: https://buildd.debian.org/status/fetch.php?pkg=qemu&arch=sparc64&ver=1%3A5.2%2Bdfsg-1&stamp=1607502300&raw=0
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1909823 b/results/classifier/gemma3:12b/kernel/1909823
new file mode 100644
index 00000000..93d753b0
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1909823
@@ -0,0 +1,8 @@
+
+RDPMC check on PCE is backwards
+
+At [this line](https://github.com/qemu/qemu/blob/75ee62ac606bfc9eb59310b9446df3434bf6e8c2/target/i386/tcg/misc_helper.c#L225) the check on CR4_PCE_MASK is backwards: it's raising an exception if the flag is set (and CPL != 0) rather than if the flag is clear.
+
+It's low priority at the moment because the instruction isn't implemented, so you get an illegal opcode exception when expecting a GPF, or vice versa, but it's a time bomb for if it is ever implemented.
+
+The Intel docs also indicate that CR0.PE influences the protection; I don't know if that's already reflected in env->hflags & HF_CPL_MASK.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1910505 b/results/classifier/gemma3:12b/kernel/1910505
new file mode 100644
index 00000000..381a4f8f
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1910505
@@ -0,0 +1,68 @@
+
+atomic failure linking with --enable-sanitizers on 32-bit Linux hosts
+
+As of commit 50536341b47, using --enable-sanitizers on 32-bit Linux host:
+- displays various warnings
+- fails linking
+
+Using Ubuntu 18.04 (release 20201211.1) and Clang10 on i386:
+
+[139/675] Compiling C object softmmu.fa.p/softmmu_icount.c.o
+In file included from ../softmmu/icount.c:31:
+In file included from include/exec/exec-all.h:23:
+In file included from ../target/mips/cpu.h:4:
+In file included from ../target/mips/cpu-qom.h:23:
+In file included from include/hw/core/cpu.h:23:
+In file included from include/hw/qdev-core.h:5:
+In file included from include/qemu/bitmap.h:16:
+In file included from include/qemu/bitops.h:17:
+include/qemu/atomic.h:463:12: warning: misaligned atomic operation may
+incur significant performance penalty [-Watomic-alignment]
+    return qatomic_read__nocheck(ptr);
+           ^
+include/qemu/atomic.h:129:5: note: expanded from macro
+'qatomic_read__nocheck'
+    __atomic_load_n(ptr, __ATOMIC_RELAXED)
+    ^
+include/qemu/atomic.h:473:5: warning: misaligned atomic operation may
+incur significant performance penalty [-Watomic-alignment]
+    qatomic_set__nocheck(ptr, val);
+    ^
+include/qemu/atomic.h:138:5: note: expanded from macro
+'qatomic_set__nocheck'
+    __atomic_store_n(ptr, i, __ATOMIC_RELAXED)
+    ^
+2 warnings generated.
+[...]
+
+[850/2216] Linking target tests/test-hbitmap
+FAILED: tests/test-hbitmap
+clang  -o tests/test-hbitmap tests/test-hbitmap.p/test-hbitmap.c.o
+tests/test-hbitmap.p/iothread.c.o -Wl,--as-needed -Wl,--no-undefined
+-pie -Wl,--whole-archive libblock.fa libcrypto.fa libauthz.fa libqom.fa
+libio.fa -Wl,--no-whole-archive -Wl,--warn-common -fsanitize=undefined
+-fsanitize=address -Wl,-z,relro -Wl,-z,now -m32 -ggdb
+-fstack-protector-strong -Wl,--start-group libqemuutil.a
+subprojects/libvhost-user/libvhost-user-glib.a
+subprojects/libvhost-user/libvhost-user.a libblock.fa libcrypto.fa
+libauthz.fa libqom.fa libio.fa @block.syms -lgio-2.0 -lgobject-2.0
+-lglib-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -pthread -lutil -lgnutls
+-lm -lgthread-2.0 -lglib-2.0 /usr/lib/i386-linux-gnu/libglib-2.0.so
+-liscsi -lgthread-2.0 -lglib-2.0 -laio -lcurl
+/usr/lib/i386-linux-gnu/libz.so -lrbd -lrados -lnettle -lgnutls
+-Wl,--end-group
+libblock.fa(block_io.c.o): In function `stat64_max':
+include/qemu/stats64.h:58: undefined reference to `__atomic_load_8'
+include/qemu/stats64.h:60: undefined reference to
+`__atomic_compare_exchange_8'
+libblock.fa(block_qapi.c.o): In function `stat64_get':
+include/qemu/stats64.h:40: undefined reference to `__atomic_load_8'
+libqemuutil.a(util_qsp.c.o): In function `qatomic_set_u64':
+include/qemu/atomic.h:478: undefined reference to `__atomic_store_8'
+libqemuutil.a(util_qsp.c.o): In function `qatomic_read_u64':
+include/qemu/atomic.h:468: undefined reference to `__atomic_load_8'
+clang: error: linker command failed with exit code 1 (use -v to see
+invocation)
+
+Issue previously reported on the list here:
+https://<email address hidden>/msg770128.html
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1911 b/results/classifier/gemma3:12b/kernel/1911
new file mode 100644
index 00000000..6094f3f8
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1911
@@ -0,0 +1,41 @@
+
+abnormal segfaults inside qemu-system-riscv64
+Description of problem:
+3 tests of Cockatrice segfaults in qemu-system-riscv64 emulator. This is similar to a regression of qemu-riscv64-static I reported: #1908.
+But for qemu-system-riscv64, it doesn't looks like a recent regression because qemu 7.2.1 also fails.
+Steps to reproduce:
+To save the time on reproducing this bug, [I uploaded the zstd compressed qcow2 image to google drive](https://drive.google.com/file/d/1-2Wtmq4MlGvTLjmQ7P5vAvNlWg8--jjT/view?usp=sharing). It contains the whole environment, cockatrice source code and built tests.
+
+The password of the root user is `archriscv`.
+
+1. Setup Arch Linux riscv environment: https://github.com/CoelacanthusHex/archriscv-scriptlet https://github.com/felixonmars/archriscv-packages/wiki/Setup-Arch-Linux-RISC-V-using-qemu-system
+2. Start it(with the commandline above, in the boot menu, choose `2:      Linux linux (fallback initramfs)`) and building cockatrice with tests in it. 
+3. Run tests (/root/Cockatrice/build/tests/loading_from_clipboard/loading_from_clipboard_test, /root/Cockatrice/build/tests/carddatabase/filter_string_test, /root/Cockatrice/build/tests/carddatabase/carddatabase_test)
+4. The tests segfault, which is unexpected.
+Additional information:
+The tests segfault at exactly the same instruction as in #1908:
+
+```
+┌──────────────────────────────────────────────────────────────────────────────┐
+│  > 0x7ffff2cba928  lhu     a2,1248(a2)                                       │
+│    0x7ffff2cba92c  and     a0,a0,127                                         │
+│    0x7ffff2cba930  sll     a2,a2,0x7                                         │
+│    0x7ffff2cba934  add     a0,a0,a2                                          │
+│    0x7ffff2cba938  lui     t2,0xf8000                                        │
+│    0x7ffff2cba93c  lui     a2,0xf5de2                                        │
+│    0x7ffff2cba940  add     a2,a2,-1824                                       │
+│    0x7ffff2cba944  sll     t2,t2,0x14                                        │
+│    0x7ffff2cba948  xor     a2,a2,t2                                          │
+│    0x7ffff2cba94c  sll     t2,a0,0x1                                         │
+│    0x7ffff2cba950  add     a2,a2,t2                                          │
+│    0x7ffff2cba954  lhu     a2,0(a2)                                          │
+│    0x7ffff2cba958  sll     a0,a2,0x3                                         │
+└──────────────────────────────────────────────────────────────────────────────┘
+multi-thre Thread 0x7ffff2cbe0 In:                     L??   PC: 0x7ffff2cba928
+(gdb) bt
+#0  0x00007ffff2cba928 in  ()
+```
+
+It might suggest that 2d708164e0475064e0e2167bd73e8570e22df1e0 is not the true cause of #1908 and this bug shares the same underlying cause with #1908.
+
+Commit 2d708164e0475064e0e2167bd73e8570e22df1e0 LGTM, although it seems that it is copied from the loongarch one and the author forgot to update [the file header](https://gitlab.com/qemu-project/qemu/-/blob/2d708164e0475064e0e2167bd73e8570e22df1e0/linux-user/riscv/target_mman.h#L1-6).
diff --git a/results/classifier/gemma3:12b/kernel/1913315 b/results/classifier/gemma3:12b/kernel/1913315
new file mode 100644
index 00000000..ad69a077
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1913315
@@ -0,0 +1,49 @@
+
+qemu-system-x86_64 crash: in memory_region_access_valid+0x13
+
+Recently we started to get intermittent qemu crashes. There is catchsegv report:
+
+```
++ qemu-system-x86_64 -m 77766M -smp 8 -nodefaults -nographic -no-reboot -fsdev local,id=root,path=/,security_model=none,multidevs=remap -device virtio-9p-pci,fsdev=root,mount_tag=/dev/root -device virtio-rng-pci -serial mon:stdio -kernel /usr/src/tmp/kernel-image-rt-buildroot/boot/vmlinuz-4.19.165-rt-alt1.rt70 -initrd /usr/src/tmp/initramfs-4.19.165-rt-alt1.rt70.img -bios bios.bin -append 'console=ttyS0 mitigations=off nokaslr quiet panic=-1 no_timer_check'
+*** signal 11
+Register dump:
+
+ RAX: 0000000000000000   RBX: 0000034000000340   RCX: 0000000000000001
+ RDX: 0000000000000004   RSI: 0000000000000300   RDI: 0000034000000340
+ RBP: 0000000000000300   R8 : 0000000000000000   R9 : 0000034000000340
+ R10: 0000000000000370   R11: 0000000000000002   R12: 0000000000000004
+ R13: 0000000000000004   R14: 000055b473fef5e0   R15: 0000000000000002
+ RSP: 00007fd7edffae90
+
+ RIP: 000055b4717ef653   EFLAGS: 00010206
+
+ CS: 0033   FS: 0000   GS: 0000
+
+ Trap: 0000000e   Error: 00000004   OldMask: 7ffbfa77   CR2: 00000388
+
+ FPUCW: 0000037f   FPUSW: 00000000   TAG: 00000000
+ RIP: 00000000   RDP: 00000000
+
+ ST(0) 0000 0000000000000000   ST(1) 0000 0000000000000000
+ ST(2) 0000 0000000000000000   ST(3) 0000 0000000000000000
+ ST(4) 0000 0000000000000000   ST(5) 0000 0000000000000000
+ ST(6) 0000 0000000000000000   ST(7) 0000 0000000000000000
+ mxcsr: 1fa0
+ XMM0:  00000000000000000000000000000000 XMM1:  00000000000000000000000000000000
+ XMM2:  00000000000000000000000000000000 XMM3:  00000000000000000000000000000000
+ XMM4:  00000000000000000000000000000000 XMM5:  00000000000000000000000000000000
+ XMM6:  00000000000000000000000000000000 XMM7:  00000000000000000000000000000000
+ XMM8:  00000000000000000000000000000000 XMM9:  00000000000000000000000000000000
+ XMM10: 00000000000000000000000000000000 XMM11: 00000000000000000000000000000000
+ XMM12: 00000000000000000000000000000000 XMM13: 00000000000000000000000000000000
+ XMM14: 00000000000000000000000000000000 XMM15: 00000000000000000000000000000000
+
+Backtrace:
+qemu-system-x86_64(memory_region_access_valid+0x13)[0x55b4717ef653]
+qemu-system-x86_64(memory_region_dispatch_write+0x48)[0x55b4717ef8c8]
+qemu-system-x86_64(+0x69fdfc)[0x55b471851dfc]
+qemu-system-x86_64(helper_le_stl_mmu+0x2c5)[0x55b471858995]
+[0x7feaed070925]
+
+```
+QEMU release 5.2.0.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1915 b/results/classifier/gemma3:12b/kernel/1915
new file mode 100644
index 00000000..c6b2e893
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1915
@@ -0,0 +1,12 @@
+
+whpx causes a blue screen on guest windows
+Description of problem:
+i wanted to install windows 7 with qemu, but qunad i tried i got a blue screen . Then I downgraded to version 5.0.2 and it worked perfectly, I also tried with windows 10 and it didn't boot.
+
+![image](/uploads/3b69a76f8b23ae49652b010b1ae31d83/image.png)
+Steps to reproduce:
+1. install windows 7 iso
+2. run the setup 
+3. and the bsod..
+Additional information:
+I tried it with qemu 5.0.2 and it worked perfectly.
diff --git a/results/classifier/gemma3:12b/kernel/1915682 b/results/classifier/gemma3:12b/kernel/1915682
new file mode 100644
index 00000000..4dac0203
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1915682
@@ -0,0 +1,99 @@
+
+i386-linux-user wine exception regression tests fail
+
+When trying to run wine (latest devel from git) regression tests for ntdll in a statically linked qemu-i386 (commit 392b9a74b9b621c52d05e37bc6f41f1bbab5c6f8) on arm32 (raspberry pi 4) in a debian buster chroot, the exception tests fail at the first test with an infinite exception loop.
+
+WINEDEBUG=+seh wine wine/dlls/ntdll/tests/ntdll_test.exe exception
+
+
+Working x86_64 system running 32-bit code
+
+0024:warn:seh:dispatch_exception EXCEPTION_ACCESS_VIOLATION exception (code=c0000005) raised
+0024:trace:seh:dispatch_exception  eax=00000000 ebx=7ffc2000 ecx=004e0ef4 edx=003c0004 esi=003c0000 edi=00000000
+0024:trace:seh:dispatch_exception  ebp=0085fa08 esp=0085f9ac cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010246
+0024:trace:seh:call_vectored_handlers calling handler at 7B00B460 code=c0000005 flags=0
+0024:trace:seh:call_vectored_handlers handler at 7B00B460 returned 0
+0024:trace:seh:call_stack_handlers calling handler at 004178B0 code=c0000005 flags=0
+0024:trace:seh:call_stack_handlers handler at 004178B0 returned 0
+0024:trace:seh:dispatch_exception  call_stack_handlers continuing
+0024:trace:seh:NtGetContextThread 0xfffffffe: dr0=42424240 dr1=00000000 dr2=126bb070 dr3=0badbad0 dr6=00000000 dr7=ffff0115
+
+
+Non-working qemu
+
+0024:warn:seh:dispatch_exception EXCEPTION_ACCESS_VIOLATION exception (code=c0000005) raised
+0024:trace:seh:dispatch_exception  eax=00000000 ebx=3ffe2000 ecx=004e0ef4 edx=003c0004 esi=003c0000 edi=00000000
+0024:trace:seh:dispatch_exception  ebp=0085fa08 esp=0085f9ac cs=0023 ds=002b es=002b fs=003b gs=0033 flags=00000246
+0024:trace:seh:call_vectored_handlers calling handler at 7B00B460 code=c0000005 flags=0
+0024:trace:seh:call_vectored_handlers handler at 7B00B460 returned 0
+0024:trace:seh:call_stack_handlers calling handler at 004178B0 code=c0000005 flags=0
+0024:trace:seh:call_stack_handlers handler at 004178B0 returned 0
+0024:trace:seh:dispatch_exception  call_stack_handlers continuing
+0024:trace:seh:dispatch_exception  call_stack_handlers ret status = 0
+0024:trace:seh:dispatch_exception code=0 flags=1 addr=7BC2389C ip=7bc2389c tid=0024
+
+The non-working verion is never managing to set the CPU context using NtContinue/SetContextThread back to the correct running thread stack and IP. It executes as if the context restore just returns to the function that called NtContinue() (dispatch_exception(), not the function that raised the exception or one of its parent exception handlers).
+
+It looks like NtSetContextThread(), specifically the asm function set_full_cpu_context() is being handled incorrectly.
+
+wine code below. note interesting use of iret with no previous interrupt call. The exception handler is called with a jmp.
+
+/***********************************************************************
+ *           set_full_cpu_context
+ *
+ * Set the new CPU context.
+ */
+extern void set_full_cpu_context( const CONTEXT *context );
+__ASM_GLOBAL_FUNC( set_full_cpu_context,
+                   "movl $0,%fs:0x1f8\n\t"     /* x86_thread_data()->syscall_frame = NULL */
+                   "movl 4(%esp),%ecx\n\t"
+                   "movw 0x8c(%ecx),%gs\n\t"  /* SegGs */
+                   "movw 0x90(%ecx),%fs\n\t"  /* SegFs */
+                   "movw 0x94(%ecx),%es\n\t"  /* SegEs */
+                   "movl 0x9c(%ecx),%edi\n\t" /* Edi */
+                   "movl 0xa0(%ecx),%esi\n\t" /* Esi */
+                   "movl 0xa4(%ecx),%ebx\n\t" /* Ebx */
+                   "movl 0xb4(%ecx),%ebp\n\t" /* Ebp */
+                   "movw %ss,%ax\n\t"
+                   "cmpw 0xc8(%ecx),%ax\n\t"  /* SegSs */
+                   "jne 1f\n\t"
+                   /* As soon as we have switched stacks the context structure could
+                    * be invalid (when signal handlers are executed for example). Copy
+                    * values on the target stack before changing ESP. */
+                   "movl 0xc4(%ecx),%eax\n\t" /* Esp */
+                   "leal -4*4(%eax),%eax\n\t"
+                   "movl 0xc0(%ecx),%edx\n\t" /* EFlags */
+                   ".byte 0x36\n\t"
+                   "movl %edx,3*4(%eax)\n\t"
+                   "movl 0xbc(%ecx),%edx\n\t" /* SegCs */
+                   ".byte 0x36\n\t"
+                   "movl %edx,2*4(%eax)\n\t"
+                   "movl 0xb8(%ecx),%edx\n\t" /* Eip */
+                   ".byte 0x36\n\t"
+                   "movl %edx,1*4(%eax)\n\t"
+                   "movl 0xb0(%ecx),%edx\n\t" /* Eax */
+                   ".byte 0x36\n\t"
+                   "movl %edx,0*4(%eax)\n\t"
+                   "pushl 0x98(%ecx)\n\t"     /* SegDs */
+                   "movl 0xa8(%ecx),%edx\n\t" /* Edx */
+                   "movl 0xac(%ecx),%ecx\n\t" /* Ecx */
+                   "popl %ds\n\t"
+                   "movl %eax,%esp\n\t"
+                   "popl %eax\n\t"
+                   "iret\n"
+                   /* Restore the context when the stack segment changes. We can't use
+                    * the same code as above because we do not know if the stack segment
+                    * is 16 or 32 bit, and 'movl' will throw an exception when we try to
+                    * access memory above the limit. */
+                   "1:\n\t"
+                   "movl 0xa8(%ecx),%edx\n\t" /* Edx */
+                   "movl 0xb0(%ecx),%eax\n\t" /* Eax */
+                   "movw 0xc8(%ecx),%ss\n\t"  /* SegSs */
+                   "movl 0xc4(%ecx),%esp\n\t" /* Esp */
+                   "pushl 0xc0(%ecx)\n\t"     /* EFlags */
+                   "pushl 0xbc(%ecx)\n\t"     /* SegCs */
+                   "pushl 0xb8(%ecx)\n\t"     /* Eip */
+                   "pushl 0x98(%ecx)\n\t"     /* SegDs */
+                   "movl 0xac(%ecx),%ecx\n\t" /* Ecx */
+                   "popl %ds\n\t"
+                   "iret" )
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1917184 b/results/classifier/gemma3:12b/kernel/1917184
new file mode 100644
index 00000000..375c971f
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1917184
@@ -0,0 +1,6 @@
+
+qemu-user vm86() segfaults handling interrupt with ss:sp in same page as cs:ip
+
+When using qemu-i386 to run a program that uses vm86(), if the vm86 code calls an interrupt while cs:ip and ss:sp both point within the same page, do_int tries to write to the page while it is not writable, causing a segfault.
+
+qemu version 5.2.0, x86-64 host.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1917542 b/results/classifier/gemma3:12b/kernel/1917542
new file mode 100644
index 00000000..9d2ca450
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1917542
@@ -0,0 +1,139 @@
+
+qemu-img crash on M1 Mac
+
+1. Symptom
+$ qemu-img create -f qcow2 disk.qcow2 10G
+[1] 72373 killed qemu-img create -f qcow2 disk.qcow2 10G
+
+2. System environment
+CPU: Apple M1
+OS: Big Sur 11.2.2
+qemu:  stable 5.2.0 (Binary installed by homebrew)
+
+3. Kernel logs
+$ sudo log show --predicate ‘eventMessage LIKE “qemu”’ --debug
+ntID Dirty: 1 Event: com.apple.stability.crash {“appVersion”:"???",“exceptionType”:1,“logwritten”:1,“process”:“qemu-img”,“responsibleApp”:“iTerm2”,“timestamp”:1614666875993238}
+2021-03-02 15:36:52.728210+0900 0xfb308 Default 0x0 0 0 kernel: CODE SIGNING: cs_invalid_page(0x102930000): p=72373[qemu-img] final status 0x23000200, denying page sending SIGKILL
+2021-03-02 15:36:52.728222+0900 0xfb308 Default 0x0 0 0 kernel: CODE SIGNING: process 72373[qemu-img]: rejecting invalid page at address 0x102930000 from offset 0x0 in file “/opt/homebrew/Cellar/libssh/0.9.5_1/lib/libssh.4.8.6.dylib” (cs_mtime:1614297740.413435328 == mtime:1614297740.413435328) (signed:1 validated:1 tainted:1 nx:0 wpmapped:0 dirty:0 depth:0)
+2021-03-02 15:36:52.728477+0900 0xfab09 Default 0x0 919 0 ReportCrash: Parsing corpse data for process qemu-img [pid 72373]
+2021-03-02 15:36:52.884736+0900 0xfab09 Default 0x0 919 0 ReportCrash: (CrashReporterSupport) Saved crash report for qemu-img[72373] version 0 to qemu-img_2021-03-02-153652_.crash
+
+4. Crash logs
+$ sudo cat /Users//Library/Logs/DiagnosticReports/qemu-img_2021-03-02-153652_.crash
+Process: qemu-img [72373]
+Path: /opt/homebrew/*/qemu-img
+Identifier: qemu-img
+Version: 0
+Code Type: ARM-64 (Native)
+Parent Process: zsh [67484]
+Responsible: iTerm2 [556]
+User ID: 501
+
+Date/Time: 2021-03-02 15:36:52.710 +0900
+OS Version: macOS 11.2.2 (20D80)
+Report Version: 12
+Anonymous UUID: AF87D5F0-2BED-EB72-1DC8-26F63A24DA7C
+
+Sleep/Wake UUID: 3862EA39-132E-42BD-A4BB-5A36F36607F1
+
+Time Awake Since Boot: 89000 seconds
+Time Since Wake: 520 seconds
+
+System Integrity Protection: enabled
+
+Crashed Thread: 0
+
+Exception Type: EXC_BAD_ACCESS (Code Signature Invalid)
+Exception Codes: 0x0000000000000032, 0x0000000102930000
+Exception Note: EXC_CORPSE_NOTIFY
+
+Termination Reason: Namespace CODESIGNING, Code 0x2
+
+kernel messages:
+
+VM Regions Near 0x102930000:
+__LINKEDIT 102908000-102930000 [ 160K] r–/r-- SM=COW /opt/homebrew/*
+→ mapped file 102930000-102934000 [ 16K] r–/r-x SM=PRV Object_id=fc8cc3db
+__TEXT 1029bc000-102a38000 [ 496K] r-x/r-x SM=COW /usr/lib/dyld
+
+Application Specific Information:
+dyld: launch, loading dependent libraries
+/opt/homebrew/opt/libssh/lib/libssh.4.dylib
+
+Thread 0 Crashed:
+0 dyld 0x0000000102a18780 bcmp + 16
+1 dyld 0x00000001029d9408 ImageLoaderMachO::validateFirstPages(linkedit_data_command const*, int, unsigned char const*, unsigned long, long long, ImageLoader::LinkContext const&) + 136
+2 dyld 0x00000001029e03b8 ImageLoaderMachOCompressed::instantiateFromFile(char const*, int, unsigned char const*, unsigned long, unsigned long long, unsigned long long, stat const&, unsigned int, unsigned int, linkedit_data_command const*, encryption_info_command const*, ImageLoader::LinkContext const&) + 268
+3 dyld 0x00000001029d7ffc ImageLoaderMachO::instantiateFromFile(char const*, int, unsigned char const*, unsigned long, unsigned long long, unsigned long long, stat const&, ImageLoader::LinkContext const&) + 172
+4 dyld 0x00000001029c0290 dyld::loadPhase6(int, stat const&, char const*, dyld::LoadContext const&) + 668
+5 dyld 0x00000001029c8dd8 dyld::loadPhase5(char const*, char const*, dyld::LoadContext const&, unsigned int&, std::__1::vector<char const*, std::__1::allocator<char const*> >) + 1328
+6 dyld 0x00000001029c8824 dyld::loadPhase4(char const, char const*, dyld::LoadContext const&, unsigned int&, std::__1::vector<char const*, std::__1::allocator<char const*> >) + 208
+7 dyld 0x00000001029c8530 dyld::loadPhase3(char const, char const*, dyld::LoadContext const&, unsigned int&, std::__1::vector<char const*, std::__1::allocator<char const*> >) + 1100
+8 dyld 0x00000001029c7cf0 dyld::loadPhase1(char const, char const*, dyld::LoadContext const&, unsigned int&, std::__1::vector<char const*, std::__1::allocator<char const*> >) + 212
+9 dyld 0x00000001029bfe0c dyld::loadPhase0(char const, char const*, dyld::LoadContext const&, unsigned int&, std::__1::vector<char const*, std::__1::allocator<char const*> >) + 468
+10 dyld 0x00000001029bf9b0 dyld::load(char const, dyld::LoadContext const&, unsigned int&) + 196
+11 dyld 0x00000001029c977c dyld::libraryLocator(char const*, bool, char const*, ImageLoader::RPathChain const*, unsigned int&) + 56
+12 dyld 0x00000001029d39d4 ImageLoader::recursiveLoadLibraries(ImageLoader::LinkContext const&, bool, ImageLoader::RPathChain const&, char const*) + 344
+13 dyld 0x00000001029d21ac ImageLoader::link(ImageLoader::LinkContext const&, bool, bool, bool, ImageLoader::RPathChain const&, char const*) + 160
+14 dyld 0x00000001029c25f4 dyld::link(ImageLoader*, bool, bool, ImageLoader::RPathChain const&, unsigned int) + 328
+15 dyld 0x00000001029c4928 dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*) + 6764
+16 dyld 0x00000001029bd258 dyldbootstrap::start(dyld3::MachOLoaded const*, int, char const**, dyld3::MachOLoaded const*, unsigned long*) + 476
+17 dyld 0x00000001029bd038 _dyld_start + 56
+
+Thread 0 crashed with ARM Thread State (64-bit):
+x0: 0x0000000102930000 x1: 0x000000016d6297c0 x2: 0x0000000000000850 x3: 0x0000000000040001
+x4: 0x0000000000000003 x5: 0x0000000000000000 x6: 0x0000000102a40280 x7: 0x0000000000000000
+x8: 0x0000000000000000 x9: 0x000000016d629ea8 x10: 0x0000000000000001 x11: 0x0001803000000000
+x12: 0x0000000000000032 x13: 0x0004000000000000 x14: 0x0000000000062530 x15: 0x000000016d629e28
+x16: 0x00000000000000c5 x17: 0x0000000000000000 x18: 0x0000000000000000 x19: 0x0000000102a45cc0
+x20: 0x0000000000000860 x21: 0x000000016d6297c0 x22: 0x0000000102930000 x23: 0x0000000000000003
+x24: 0x000000016d62a010 x25: 0x000000016d6318d8 x26: 0x00000001027cc970 x27: 0x000000016d6297c0
+x28: 0x0000000000000004 fp: 0x000000016d6291c0 lr: 0x00000001029d9408
+sp: 0x000000016d629180 pc: 0x0000000102a18780 cpsr: 0x20000000
+far: 0x0000000102930000 esr: 0x92000007
+
+Binary Images:
+0x1027cc000 - 0x1028ebfff +qemu-img (0) /opt/homebrew//qemu-img
+0x1029bc000 - 0x102a37fff dyld (832.7.3) <4AB185B3-DC20-3C03-A193-67C0E6C589D7> /usr/lib/dyld
+0x102ac0000 - 0x102bbffff +libglib-2.0.0.dylib (0) /opt/homebrew//libglib-2.0.0.dylib
+0x102bf4000 - 0x102d1bfff +libgnutls.30.dylib (0) <74A67886-3907-3E35-B0A3-8A5798F97283> /opt/homebrew/*/libgnutls.30.dylib
+0x191db9000 - 0x192262fff com.apple.CoreFoundation (6.9 - 1774.101) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
+0x1944af000 - 0x194579fff com.apple.framework.IOKit (2.0.2 - 1845.81.1) <516911DA-18D7-3D17-8646-BBF7C75CD070> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
+0x19b3b6000 - 0x19b3b7fff libSystem.B.dylib (1292.60.1) /usr/lib/libSystem.B.dylib
+0x19b635000 - 0x19b639fff libpam.2.dylib (28.40.1) /usr/lib/libpam.2.dylib
+
+External Modification Summary:
+Calls made by other processes targeting this process:
+task_for_pid: 0
+thread_create: 0
+thread_set_state: 0
+Calls made by this process:
+task_for_pid: 0
+thread_create: 0
+thread_set_state: 0
+Calls made by all processes on this machine:
+task_for_pid: 81731
+thread_create: 0
+thread_set_state: 8
+
+VM Region Summary:
+ReadOnly portion of Libraries: Total=489.5M resident=0K(0%) swapped_out_or_unallocated=489.5M(100%)
+Writable regions: Total=8400K written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=8400K(100%)
+
+                            VIRTUAL   REGION
+REGION TYPE SIZE COUNT (non-coalesced)
+=========== ======= =======
+STACK GUARD 56.0M 1
+Stack 8176K 1
+__AUTH 7K 2
+__AUTH_CONST 926K 4
+__DATA 371K 10
+__DATA_CONST 2209K 7
+__DATA_DIRTY 32K 2
+__LINKEDIT 480.3M 6
+__OBJC_CONST 28K 2
+__TEXT 9472K 8
+__UNICODE 588K 1
+mapped file 16K 1
+=========== ======= =======
+TOTAL 557.6M 45
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1920602 b/results/classifier/gemma3:12b/kernel/1920602
new file mode 100644
index 00000000..8073ffc5
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1920602
@@ -0,0 +1,20 @@
+
+QEMU crash after a QuickBASIC program integer overflow
+
+A trivial program compiler with QuickBASIC 4.5 with integer overflow will crash QEMU when ran under MS-DOS 5.0 or FreeDOS 1.2:
+
+C:\KILLER>type killer.bas                                                       
+A% = VAL("99999"):PRINT A%                                                      
+                                                                                
+C:\KILLER>killer.exe                                                            
+**                                                                              
+  ERROR:../qemu-5.2.0/accel/tcg/tcg-cpus.c:541:tcg_handle_interrupt: assertion failed: (qemu_mutex_iothread_locked())                                           
+Aborted
+
+QEMU version v5.2, compiler for ARM, and started with command line:
+
+qemu-system-i386 -curses -cpu 486 -m 1 -drive dos.img
+
+The same test under Ubuntu QEMU and KVM/x86_64 (QEMU emulator version 4.2.1 (Debian 1:4.2-3ubuntu6.14)) will just silently hang the QEMU. On DOSBOX, the machine does not die and program outputs the value -31073.
+
+The EXE to reproduce the issue is attached.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1921 b/results/classifier/gemma3:12b/kernel/1921
new file mode 100644
index 00000000..5797f4a1
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1921
@@ -0,0 +1,31 @@
+
+qemu-system-x86_64 segfaults in iotlb_to_section() on riscv64
+Description of problem:
+QEMU segfaults when booting up the Arch Linux x86_64 installation ISO. The ISO could be downloaded from https://geo.mirror.pkgbuild.com/iso/2023.09.01/archlinux-2023.09.01-x86_64.iso or any other Arch Linux mirrors.
+
+The crash often happens after "Probing EDD...". It's more reliably reproducible with higher `-smp` numbers, and may hang with "rcu_preempt detected stalls" without the -smp option.
+Additional information:
+I have reproduced the same issues with different RISC-V hardware, including SG2042 and TH1520.
+
+Errors:
+```
+qemu-system-x86_64: ../qemu-8.1.1/softmmu/physmem.c:2419: iotlb_to_section: Assertion `section_index < d->map.sections_nb' failed.
+```
+
+Backtrace:
+```
+#0  0x0000003fa74f0ece in __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
+#1  0x0000003fa74f0f0e in __pthread_kill_internal (signo=6, threadid=<optimized out>) at pthread_kill.c:78
+#2  0x0000003fa74ba912 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
+#3  0x0000003fa74aa164 in __GI_abort () at abort.c:79
+#4  0x0000003fa74b54a4 in __assert_fail_base
+    (fmt=0x3fa7594c10 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x2ae1de0458 "section_index < d->map.sections_nb", file=file@entry=0x2ae1ddf980 "../qemu-8.1.1/softmmu/physmem.c", line=line@entry=2419, function=function@entry=0x2ae1f05f20 <__PRETTY_FUNCTION__.11> "iotlb_to_section") at assert.c:92
+#5  0x0000003fa74b54f8 in __assert_fail (assertion=0x2ae1de0458 "section_index < d->map.sections_nb", file=0x2ae1ddf980 "../qemu-8.1.1/softmmu/physmem.c", line=2419, function=0x2ae1f05f20 <__PRETTY_FUNCTION__.11> "iotlb_to_section") at assert.c:101
+#6  0x0000002ae1b69788 in iotlb_to_section () at ../qemu-8.1.1/softmmu/physmem.c:2419
+#7  0x0000002ae1b9d774 in io_writex () at ../qemu-8.1.1/accel/tcg/cputlb.c:1432
+#8  0x0000002ae1b9d924 in do_st_mmio_leN () at ../qemu-8.1.1/accel/tcg/cputlb.c:2755
+#9  0x0000002ae1ba127c in do_st_4 () at ../qemu-8.1.1/accel/tcg/cputlb.c:2921
+#10 do_st4_mmu () at ../qemu-8.1.1/accel/tcg/cputlb.c:3006
+#11 0x0000003f600dd7ec in code_gen_buffer ()
+#12 0x5f085e2755518600 in  ()
+```
diff --git a/results/classifier/gemma3:12b/kernel/1921138 b/results/classifier/gemma3:12b/kernel/1921138
new file mode 100644
index 00000000..51c6a1f3
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1921138
@@ -0,0 +1,14 @@
+
+tcg.c:3329: tcg fatal error
+
+I am currently building my own kernel with bootloader and qemu crashed after I have set an IDT in protected mode and then create a invalid opcode exception with the opcode 0xff.
+
+My code is here: https://github.com/Luis-Hebendanz/svm_kernel/blob/qemu_crash/svm_kernel/external/bootloader/src/main.rs#L80
+
+Build instructions are here: https://github.com/Luis-Hebendanz/svm_kernel/tree/qemu_crash
+
+A precompiled binary is here: https://cloud.gchq.icu/s/LcjoDWRW2CbxJ5i
+
+I executed the following command: qemu-system-x86_64 -smp cores=4 -cdrom target/x86_64-os/debug/bootimage-svm_kernel.iso -serial stdio -display none -m 4G
+
+I am running QEMU emulator version 5.1.0
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1921664 b/results/classifier/gemma3:12b/kernel/1921664
new file mode 100644
index 00000000..3794916d
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1921664
@@ -0,0 +1,93 @@
+
+QEMU coroutines fail with LTO on non-x86_64 architectures
+
+I regularly run a RISC-V (RV64GC) QEMU VM, but an update a few days ago broke it.  Now when I launch it, it hits an assertion:
+
+                                                                                  
+OpenSBI v0.6                                                                      
+   ____                    _____ ____ _____                             
+  / __ \                  / ____|  _ \_   _|                                      
+ | |  | |_ __   ___ _ __ | (___ | |_) || |                                        
+ | |  | | '_ \ / _ \ '_ \ \___ \|  _ < | |                                                                                                                           
+ | |__| | |_) |  __/ | | |____) | |_) || |_                                                                                                                          
+  \____/| .__/ \___|_| |_|_____/|____/_____|                                      
+        | |                                                                                                                                                          
+        |_|                                                                       
+                                                                                  
+...
+Found /boot/extlinux/extlinux.conf                                                                                                                                   
+Retrieving file: /boot/extlinux/extlinux.conf                                                                                                                        
+618 bytes read in 2 ms (301.8 KiB/s)                                              
+RISC-V Qemu Boot Options                                                          
+1:      Linux kernel-5.5.0-dirty         
+2:      Linux kernel-5.5.0-dirty (recovery mode)                            
+Enter choice: 1:        Linux kernel-5.5.0-dirty                                  
+Retrieving file: /boot/initrd.img-5.5.0-dirty                                                                                                                        
+qemu-system-riscv64: ../../block/aio_task.c:64: aio_task_pool_wait_one: Assertion `qemu_coroutine_self() == pool->main_co' failed.                                   
+./run.sh: line 31:  1604 Aborted                 (core dumped) qemu-system-riscv64 -machine virt -nographic -smp 8 -m 8G -bios fw_payload.bin -device virtio-blk-devi
+ce,drive=hd0 -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-device,rng=rng0 -drive file=riscv64-UbuntuFocal-qemu.qcow2,format=qcow2,id=hd0 -devi
+ce virtio-net-device,netdev=usernet -netdev user,id=usernet,$ports                
+
+Interestingly this doesn't happen on the AMD64 version of Ubuntu 21.04 (fully updated).
+
+
+Think you have everything already, but just in case:
+
+$ lsb_release -rd
+Description:    Ubuntu Hirsute Hippo (development branch)
+Release:        21.04
+
+$ uname -a
+Linux minimacvm 5.11.0-11-generic #12-Ubuntu SMP Mon Mar 1 19:27:36 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
+(note this is a VM running on macOS/M1)
+
+$ apt-cache policy qemu
+qemu:
+  Installed: 1:5.2+dfsg-9ubuntu1
+  Candidate: 1:5.2+dfsg-9ubuntu1
+  Version table:
+ *** 1:5.2+dfsg-9ubuntu1 500
+        500 http://ports.ubuntu.com/ubuntu-ports hirsute/universe arm64 Packages
+        100 /var/lib/dpkg/status
+
+ProblemType: Bug
+DistroRelease: Ubuntu 21.04
+Package: qemu 1:5.2+dfsg-9ubuntu1
+ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
+Uname: Linux 5.11.0-11-generic aarch64
+ApportVersion: 2.20.11-0ubuntu61
+Architecture: arm64
+CasperMD5CheckResult: unknown
+CurrentDmesg:
+ Error: command ['pkexec', 'dmesg'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
+ Error executing command as another user: Not authorized
+ 
+ This incident has been reported.
+Date: Mon Mar 29 02:33:25 2021
+Dependencies:
+ 
+KvmCmdLine: COMMAND         STAT  EUID  RUID     PID    PPID %CPU COMMAND
+Lspci-vt:
+ -[0000:00]-+-00.0  Apple Inc. Device f020
+            +-01.0  Red Hat, Inc. Virtio network device
+            +-05.0  Red Hat, Inc. Virtio console
+            +-06.0  Red Hat, Inc. Virtio block device
+            \-07.0  Red Hat, Inc. Virtio RNG
+Lsusb: Error: command ['lsusb'] failed with exit code 1:
+Lsusb-t:
+ 
+Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
+ProcEnviron:
+ TERM=screen
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=<set>
+ LANG=C.UTF-8
+ SHELL=/bin/bash
+ProcKernelCmdLine: console=hvc0 root=/dev/vda
+SourcePackage: qemu
+UpgradeStatus: Upgraded to hirsute on 2020-12-30 (88 days ago)
+acpidump:
+ Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
+ Error executing command as another user: Not authorized
+ 
+ This incident has been reported.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1921948 b/results/classifier/gemma3:12b/kernel/1921948
new file mode 100644
index 00000000..2746deb9
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1921948
@@ -0,0 +1,39 @@
+
+MTE tags not checked properly for unaligned accesses at EL1
+
+For kernel memory accesses that span across two memory granules, QEMU's MTE implementation only checks the tag of the first granule but not of the second one.
+
+To reproduce this, build the Linux kernel with CONFIG_KASAN_HW_TAGS enabled, apply the patch below, and boot the kernel:
+
+diff --git a/sound/last.c b/sound/last.c
+index f0bb98780e70..04745cb30b74 100644
+--- a/sound/last.c
++++ b/sound/last.c
+@@ -5,12 +5,18 @@
+  */
+ 
+ #include <linux/init.h>
++#include <linux/slab.h>
+ #include <sound/core.h>
+ 
+ static int __init alsa_sound_last_init(void)
+ {
+        struct snd_card *card;
+        int idx, ok = 0;
++
++       char *ptr = kmalloc(128, GFP_KERNEL);
++       pr_err("KASAN report should follow:\n");
++       *(volatile unsigned long *)(ptr + 124);
++       kfree(ptr);
+        
+        printk(KERN_INFO "ALSA device list:\n");
+        for (idx = 0; idx < SNDRV_CARDS; idx++) {
+
+KASAN tags the 128 allocated bytes with the same tag as the returned pointer. The memory granule that follows the 128 allocated bytes has a different tag (with 1/15 probability).
+
+Expected result: a tag fault is detected and a KASAN report is printed when accessing bytes [124, 130).
+Observed result: no tag fault is detected and no KASAN report is printed.
+
+Here are the flags that I use to run QEMU if they matter:
+
+qemu-system-aarch64 -s -machine virt,mte=on -cpu max -m 2G -smp 2 -net user,host=10.0.2.10,hostfwd=tcp:127.0.0.1:10021-:22 -net nic -nographic -kernel ./Image -append "console=ttyAMA0 root=/dev/vda earlyprintk=serial" -drive file=./fs.img,format=raw,if=virtio -no-shutdown -no-reboot
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1922 b/results/classifier/gemma3:12b/kernel/1922
new file mode 100644
index 00000000..ca2aa9b3
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1922
@@ -0,0 +1,21 @@
+
+loongson3-virt machine fails to bring up secondary CPUs
+Description of problem:
+When booting Debian netboot on `loongson3-virt` machine with SMP, cores other than number 0 fail to come up.  Boot without SMP is successful.
+
+I provided the details of the first combination I tested, but I have also tested on an x86_64 host, as well as with Debian 11 (kernel `5.10.0-22-loongson-3`) on both hosts, with the same results.
+Steps to reproduce:
+1.  `wget https://ftp.debian.org/debian/dists/bookworm/main/installer-mips64el/current/images/loongson-3/netboot/vmlinuz-6.1.0-10-loongson-3`
+2.  `wget https://ftp.debian.org/debian/dists/bookworm/main/installer-mips64el/current/images/loongson-3/netboot/initrd.gz`
+3.  `qemu-system-mips64el -M loongson3-virt -kernel vmlinuz-6.1.0-10-loongson-3 -initrd initrd.gz -append "console=ttyS0" -serial stdio -smp 2`
+Additional information:
+Boot is successful when removing `-smp 2` from command line.  With it present, the following error is in `dmesg` (extends to all other CPUs when a larger SMP value is passed):
+```
+[    2.248229] rcu: Hierarchical SRCU implementation.
+[    2.248446] rcu:     Max phase no-delay instances is 1000.
+[    2.647997] smp: Bringing up secondary CPUs ...
+[    2.749706] Booting CPU#1...
+[    7.093229] CPU1: failed to start
+[    7.096508] smp: Brought up 1 node, 1 CPU
+```
+The boot eventually stalls after this.
diff --git a/results/classifier/gemma3:12b/kernel/1922617 b/results/classifier/gemma3:12b/kernel/1922617
new file mode 100644
index 00000000..c3236f36
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1922617
@@ -0,0 +1,121 @@
+
+qemu-aarch64-static "Illegal instruction" with debootstrap
+
+This is reproducible against QEMU master. I apologize for the long reproduction steps, I tried to distill it down as much as possible.
+
+System info:
+
+# qemu-aarch64-static --version
+qemu-aarch64 version 5.2.91 (v6.0.0-rc1-68-gee82c086ba)
+Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers
+
+# cat /etc/os-release
+PRETTY_NAME="Debian GNU/Linux 10 (buster)"
+NAME="Debian GNU/Linux"
+VERSION_ID="10"
+VERSION="10 (buster)"
+VERSION_CODENAME=buster
+ID=debian
+HOME_URL="https://www.debian.org/"
+SUPPORT_URL="https://www.debian.org/support"
+BUG_REPORT_URL="https://bugs.debian.org/"
+
+# head -n 26 /proc/cpuinfo
+processor       : 0
+vendor_id       : GenuineIntel
+cpu family      : 6
+model           : 85
+model name      : Intel(R) Xeon(R) Gold 5218 CPU @ 2.30GHz
+stepping        : 7
+microcode       : 0x5002f01
+cpu MHz         : 1000.716
+cache size      : 22528 KB
+physical id     : 0
+siblings        : 32
+core id         : 0
+cpu cores       : 16
+apicid          : 0
+initial apicid  : 0
+fpu             : yes
+fpu_exception   : yes
+cpuid level     : 22
+wp              : yes
+flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 invpcid_single intel_ppin ssbd mba ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm mpx rdt_a avx512f avx512dq rdseed adx smap clflushopt clwb intel_pt avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts pku ospke avx512_vnni md_clear flush_l1d arch_capabilities
+bugs            : spectre_v1 spectre_v2 spec_store_bypass swapgs taa itlb_multihit
+bogomips        : 4600.00
+clflush size    : 64
+cache_alignment : 64
+address sizes   : 46 bits physical, 48 bits virtual
+power management:
+
+My reproduction steps:
+
+# apt-get install --no-install-recommends -y \
+    build-essential \
+    ca-certificates \
+    debootstrap \
+    git \
+    libglib2.0-dev \
+    libpixman-1-dev \
+    ninja-build \
+    pkg-config \
+    python3 \
+    zstd
+
+# git clone https://github.com/qemu/qemu
+
+# mkdir qemu/build
+
+# cd qemu/build
+
+# ../configure \
+    --enable-debug \
+    --enable-linux-user \
+    --disable-bsd-user \
+    --disable-werror \
+    --disable-system \
+    --disable-tools \
+    --disable-docs \
+    --disable-gtk \
+    --disable-gnutls \
+    --disable-nettle \
+    --disable-gcrypt \
+    --disable-glusterfs \
+    --disable-libnfs \
+    --disable-libiscsi \
+    --disable-vnc \
+    --disable-kvm \
+    --disable-libssh \
+    --disable-libxml2 \
+    --disable-vde \
+    --disable-sdl \
+    --disable-opengl \
+    --disable-xen \
+    --disable-fdt \
+    --disable-vhost-net \
+    --disable-vhost-crypto \
+    --disable-vhost-user \
+    --disable-vhost-vsock \
+    --disable-vhost-scsi \
+    --disable-tpm \
+    --disable-qom-cast-debug \
+    --disable-capstone \
+    --disable-zstd \
+    --disable-linux-io-uring \
+    --static \
+    --target-list-exclude=hexagon-linux-user
+
+# ninja qemu-aarch64
+
+# install -Dm755 qemu-aarch64 /usr/local/bin/qemu-aarch64-static
+
+# cat <<'EOF' >/proc/sys/fs/binfmt_misc/register
+:qemu-aarch64:M::\x7fELF\x02\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\xb7:\xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff:/usr/local/bin/qemu-aarch64-static:CF
+EOF
+
+# debootstrap --arch arm64 --foreign buster debian-rootfs
+
+# chroot debian-rootfs /debootstrap/debootstrap --second-stage
+Illegal instruction
+
+This prevents me from building an arm64 Debian image on x86_64. If I am doing something wrong, please let me know. The binary has been uploaded for your convenience.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1922887 b/results/classifier/gemma3:12b/kernel/1922887
new file mode 100644
index 00000000..d459d45c
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1922887
@@ -0,0 +1,31 @@
+
+STR in Thumb 32 decode problem
+
+Hi 
+
+It seems that QEMU does not have a proper check on the STR instruction in Thumb32 mode.
+
+Specifically, the machine code is 0xf84f0ddd, which is 0b1111 1000 0100 1111 0000 1101 1101 1101. 
+This is an STR (immediate, Thumb) instruction with a T4 encoding scheme.
+
+The symbols is 
+
+Rn = 1111
+Rt = 0000
+P = 1
+U = 0
+W = 1
+
+The decode ASL is below:
+
+if P == ‘1’ && U == ‘1’ && W == ‘0’ then SEE STRT;
+if Rn == ‘1101’ && P == ‘1’ && U == ‘0’ && W == ‘1’ && imm8 == ‘00000100’ then SEE PUSH;
+if Rn == ‘1111’ || (P == ‘0’ && W == ‘0’) then UNDEFINED;
+t = UInt(Rt); n = UInt(Rn); imm32 = ZeroExtend(imm8, 32);
+index = (P == ‘1’); add = (U == ‘1’); wback = (W == ‘1’);
+if t == 15 || (wback && n == t) then UNPREDICTABLE;
+
+When Rn == 1111, it should be an undefined instruction, which should raise SEGILL signal. However, it seems that QEMU does not check this constraint, which should be a bug. Many thanks
+
+Regards
+Muhui
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1923197 b/results/classifier/gemma3:12b/kernel/1923197
new file mode 100644
index 00000000..fe17cbdf
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1923197
@@ -0,0 +1,38 @@
+
+RISC-V priviledged instruction error
+
+Hello when performing an MRET with MPP set to something else than 0b11 in MSTATUS, 'Invalid Instruction' exception will be triggered. The problem appeared in code after version 5.2.0.
+
+<pre>
+  # setup interrupt handling for monitor mode
+  la t0, entry_loop
+  la t1, entry_trap
+  li t2, 0x888
+  li t3, 0x1880 # MPP in MSTATUS selects to which mode to return & MPIE selects if to enable interrupts after MRET
+  csrw mepc, t0
+  csrw mtvec, t1
+  csrs mie, t2
+  csrs mstatus, t3
+
+  # if supervisor mode not supported, then loop forever
+  csrr t0, misa
+  li t1, 0x40000
+  and t2, t1, t0
+  beqz t2, 1f
+
+  # setup interrupt i& exception delegation for supervisor mode
+  li t0, 0xc0000000 # 3 GiB (entry address of supervisor)
+  li t1, 0x1000
+  #li t2, 0x300 # bit 8 & 9 is for ecall from user & supervisor mode
+  #li t3, 0x222
+  csrw mepc, t0
+  csrc mstatus, t1
+  #csrs medeleg, t2
+  #csrs mideleg, t3
+
+  # pass mhartid as first parameter to supervisor
+  csrr a0, mhartid
+
+1:
+  mret
+</pre>
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1926044 b/results/classifier/gemma3:12b/kernel/1926044
new file mode 100644
index 00000000..3797c8ac
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1926044
@@ -0,0 +1,31 @@
+
+QEMU-user doesn't report HWCAP2_MTE
+
+Reproducible on ffa090bc56e73e287a63261e70ac02c0970be61a
+
+Host Debian 5.10.24 x86_64 GNU
+
+Configured with "configure --disable-system --enable-linux-user --static"
+
+This one works and prints "OK" as expected:
+clang tests/tcg/aarch64/mte-3.c -target aarch64-linux-gnu  -fsanitize=memtag -march=armv8+memtag
+qemu-aarch64 --cpu max -L /usr/aarch64-linux-gnu ./a.out && echo OK
+
+
+This one fails and print "0":
+cat mytest.c
+#include <stdio.h>
+#include <sys/auxv.h>
+
+#ifndef HWCAP2_MTE
+#define HWCAP2_MTE (1 << 18)
+#endif
+
+int main(int ac, char **av)
+{
+    printf("%d\n", (int)(getauxval(AT_HWCAP2) & HWCAP2_MTE));
+}
+
+
+clang mytest.c -target aarch64-linux-gnu  -fsanitize=memtag -march=armv8+memtag
+qemu-aarch64 --cpu max -L /usr/aarch64-linux-gnu ./a.out
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1926521 b/results/classifier/gemma3:12b/kernel/1926521
new file mode 100644
index 00000000..46055098
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1926521
@@ -0,0 +1,63 @@
+
+QEMU-user ignores MADV_DONTNEED
+
+There is comment int the code "This is a hint, so ignoring and returning success is ok"
+https://github.com/qemu/qemu/blob/b1cffefa1b163bce9aebc3416f562c1d3886eeaa/linux-user/syscall.c#L11941
+
+But it seems incorrect with the current state of Linux
+
+"man madvise" or https://man7.org/linux/man-pages/man2/madvise.2.html
+says the following:
+>>  These advice values do not influence the semantics
+>>       of the application (except in the case of MADV_DONTNEED)
+
+>> After a successful MADV_DONTNEED operation, the semantics
+>> of memory access in the specified region are changed:
+>> subsequent accesses of pages in the range will succeed,
+>> but will result in either repopulating the memory contents
+>> from the up-to-date contents of the underlying mapped file
+>> (for shared file mappings, shared anonymous mappings, and
+>> shmem-based techniques such as System V shared memory
+>> segments) or zero-fill-on-demand pages for anonymous
+>> private mappings.
+
+Some applications use this behavior clear memory and it
+would be nice to be able to run them on QEMU without
+workarounds.
+
+Reproducer on "Debian 5.10.24 x86_64 GNU/Linux" as a host.
+
+
+```
+#include "assert.h"
+#include "stdio.h"
+#include <sys/mman.h>
+#include <errno.h>
+
+int main() {
+  char *P = (char *)mmap(0, 4096, PROT_READ | PROT_WRITE,
+                         MAP_PRIVATE | MAP_ANONYMOUS, -1, 0);
+  assert(P);
+  *P = 'A';
+  while (madvise(P, 4096, MADV_DONTNEED) == -1 && errno == EAGAIN) {
+  }
+  assert(*P == 0);
+
+  printf("OK\n");
+}
+
+/*
+gcc /tmp/madvice.c -o /tmp/madvice
+
+qemu-x86_64 /tmp/madvice
+madvice: /tmp/madvice.c:13: main: Assertion `*P == 0' failed.
+qemu: uncaught target signal 6 (Aborted) - core dumped
+Aborted
+
+/tmp/madvice
+OK
+
+
+*/
+
+```
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1926759 b/results/classifier/gemma3:12b/kernel/1926759
new file mode 100644
index 00000000..41acba9e
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1926759
@@ -0,0 +1,19 @@
+
+WFI instruction results in unhandled CPU exception
+
+Hi 
+
+I refer to the WFI instruction. The bytecode is 0xe320f003. After the execution, qemu exit with the following  crash log.
+
+qemu: unhandled CPU exception 0x10001 - aborting
+R00=00000001 R01=40800b34 R02=40800b3c R03=000102ec
+R04=00010a28 R05=00010158 R06=00087460 R07=00010158
+R08=00000000 R09=00000000 R10=00085b7c R11=408009f4
+R12=40800a08 R13=408009f0 R14=0001057c R15=000102f8
+PSR=60000010 -ZC- A usr32
+qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x7f5c21d0fa12
+
+WFI aims to enter a low-power state and wait for interrupt. The raised exception seems not a right behavior. I can provide a testcase if you needed. Many thanks.
+
+Regards
+Muhui
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1926996 b/results/classifier/gemma3:12b/kernel/1926996
new file mode 100644
index 00000000..bd28b323
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1926996
@@ -0,0 +1,21 @@
+
+qemu-user clone syscall fails
+
+qemu-user fails to emulate clone() (https://linux.die.net/man/2/clone).  The architecture doesn't seem to matter, tho I've mostly been testing aarch64.
+
+Attached is clone_test.c that demonstrates the problem.  Running it natively looks like this:
+$ bin/clone_test
+The variable was 9
+clone returned 4177: 0 Success
+The variable is now 42
+
+
+However, running it via qemu looks like:
+$ qemu-aarch64-static --version
+qemu-aarch64 version 5.2.0 (v5.2.0)
+Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers
+
+$ qemu-aarch64-static ./clone_test
+The variable was 9
+clone returned -1: 22 Invalid argument
+The variable is now 9
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1927 b/results/classifier/gemma3:12b/kernel/1927
new file mode 100644
index 00000000..3bf1c5ac
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1927
@@ -0,0 +1,525 @@
+
+SPARC64 pci-bridge kernel panic
+Description of problem:
+Kernel panics when a PCI bridge is added.
+I wanted to install a number of PCI devices, but never got enough slots from the default PCI bus (pciB, pciA is not open at all).
+So, I added a PCI bridge, but the kernel panics during boot:
+```
+OpenBIOS for Sparc64
+Cannot manage 'PCI-to-PCI bridge' PCI device type 'pci':
+ 1b36 1 (6 4 0)
+Cannot manage 'misc communication device' PCI device type '<NULL>':
+ 1af4 1003 (7 80 0)
+Cannot manage 'undefined' PCI device type '<NULL>':
+ 1af4 1005 (0 ff 0)
+Cannot manage 'undefined' PCI device type '<NULL>':
+ 1af4 1009 (0 2 0)
+Cannot manage 'SCSI bus controller' PCI device type 'scsi':
+ 1af4 1004 (1 0 0)
+Configuration device id QEMU version 1 machine id 0
+kernel phys 404000 virt 40004000 size 0x11f9290
+kernel cmdline root=/dev/sda rw log_buf_len=8M mitigations=off ktest.dir=/repos/janpieter/ktest ktest.env=/tmp/build-test-kernel-YOUlNpfwIz/env crashkernel=128M console=earlyprom0 loglevel=15 irqpoll kasan.fault=panic
+CPUs: 1 x SUNW,UltraSPARC-IIi
+UUID: 00000000-0000-0000-0000-000000000000
+Welcome to OpenBIOS v1.1 built on Mar 7 2023 22:22
+  Type 'help' for detailed information
+[sparc64] Kernel already loaded
+
+PROMLIB: Sun IEEE Boot Prom 'OBP 3.10.24 1999/01/01 01:01'
+PROMLIB: Root node compatible: sun4u
+Linux version 6.5.0-ktest-02812-g4d2faeb4fb58 (janpieter@linuxserver) (sparc64-linux-gnu-gcc (Gentoo 11.3.0 p4) 11.3.0, GNU ld (Gentoo 2.41 p2) 2.41.0) #10 SMP Mon Oct  9 15:55:57 CEST 2023
+printk: bootconsole [earlyprom0] enabled
+ARCH: SUN4U
+Ethernet address: 52:54:00:12:34:57
+MM: PAGE_OFFSET is 0xfffff80000000000 (max_phys_bits == 40)
+MM: VMALLOC [0x0000000100000000 --> 0x0000060000000000]
+MM: VMEMMAP [0x0000060000000000 --> 0x00000c0000000000]
+Kernel: Using 5 locked TLB entries for main kernel image.
+Remapping the kernel... 
+done.
+OF stdout device is: /pci@1fe,0/pci@1,1/ebus@1/su
+PROM: Built device tree with 66340 bytes of memory.
+Top of RAM: 0x7fe80000, Total RAM: 0x7fe80000
+Memory hole size: 0MB
+Allocated 16384 bytes for kernel page tables.
+Zone ranges:
+  Normal   [mem 0x0000000000000000-0x000000007fe7ffff]
+Movable zone start for each node
+Early memory node ranges
+  node   0: [mem 0x0000000000000000-0x000000007fe7ffff]
+Initmem setup node 0 [mem 0x0000000000000000-0x000000007fe7ffff]
+On node 0, zone Normal: 192 pages in unavailable ranges
+Booting Linux...
+CPU CAPS: [flush,stbar,swap,muldiv,v9,mul32,div32,v8plus]
+CPU CAPS: [vis]
+percpu: Embedded 16 pages/cpu s93992 r8192 d28888 u4194304
+pcpu-alloc: s93992 r8192 d28888 u4194304 alloc=1*4194304
+pcpu-alloc: [0] 0 
+Kernel command line: root=/dev/sda rw log_buf_len=8M mitigations=off ktest.dir=/repos/janpieter/ktest ktest.env=/tmp/build-test-kernel-YOUlNpfwIz/env crashkernel=128M console=earlyprom0 loglevel=15 irqpoll kasan.fault=panic
+Misrouted IRQ fixup and polling support enabled
+This may significantly impact system performance
+Unknown kernel command line parameters "crashkernel=128M", will be passed to user space.
+printk: log_buf_len: 8388608 bytes
+printk: early log buf free: 128952(98%)
+Dentry cache hash table entries: 262144 (order: 8, 2097152 bytes, linear)
+Inode-cache hash table entries: 131072 (order: 7, 1048576 bytes, linear)
+Sorting __ex_table...
+Built 1 zonelists, mobility grouping on.  Total pages: 259905
+mem auto-init: stack:off, heap alloc:off, heap free:off
+Memory: 2020416K/2095616K available (6609K kernel code, 7566K rwdata, 1640K rodata, 560K init, 1980K bss, 75200K reserved, 0K cma-reserved)
+SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
+ftrace: allocating 21433 entries in 42 pages
+ftrace: allocated 42 pages with 3 groups
+trace event string verifier disabled
+rcu: Hierarchical RCU implementation.
+rcu:    RCU event tracing is enabled.
+rcu:    RCU restricting CPUs from NR_CPUS=4096 to nr_cpu_ids=1.
+        Rude variant of Tasks RCU enabled.
+rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
+rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
+NR_IRQS: 2048, nr_irqs: 2048, preallocated irqs: 1
+rcu: srcu_init: Setting srcu_struct sizes based on contention.
+clocksource: tick: mask: 0xffffffffffffffff max_cycles: 0x171024e7e0, max_idle_ns: 440795205315 ns
+clocksource: mult[a000000] shift[24]
+clockevent: mult[1999999a] shift[32]
+Console: colour dummy device 80x25
+Calibrating delay using timer specific routine.. 201.35 BogoMIPS (lpj=402700)
+pid_max: default: 32768 minimum: 301
+Mount-cache hash table entries: 4096 (order: 2, 32768 bytes, linear)
+Mountpoint-cache hash table entries: 4096 (order: 2, 32768 bytes, linear)
+RCU Tasks Rude: Setting shift to 0 and lim to 1 rcu_task_cb_adjust=1.
+rcu: Hierarchical SRCU implementation.
+rcu:    Max phase no-delay instances is 1000.
+smp: Bringing up secondary CPUs ...
+smp: Brought up 1 node, 1 CPU
+devtmpfs: initialized
+device: 'platform': device_add
+bus: 'platform': registered
+bus: 'cpu': registered
+device: 'cpu': device_add
+bus: 'container': registered
+device: 'container': device_add
+Performance events: No support for PMU type 'ultra12'
+bus: 'workqueue': registered
+device: 'workqueue': device_add
+clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
+futex hash table entries: 256 (order: 1, 16384 bytes, linear)
+bus: 'virtio': registered
+NET: Registered PF_NETLINK/PF_ROUTE protocol family
+device: 'root': device_add
+bus: 'platform': add device root
+device: 'ffe1c220': device_add
+bus: 'platform': add device ffe1c220
+device: 'ffe1c348': device_add
+bus: 'platform': add device ffe1c348
+device: 'ffe26eb0': device_add
+bus: 'platform': add device ffe26eb0
+device: 'ffe1c600': device_add
+bus: 'platform': add device ffe1c600
+device: 'ffe1c6e0': device_add
+bus: 'platform': add device ffe1c6e0
+device: 'ffe1c820': device_add
+bus: 'platform': add device ffe1c820
+device: 'ffe1c948': device_add
+bus: 'platform': add device ffe1c948
+device: 'ffe26978': device_add
+bus: 'platform': add device ffe26978
+device: 'ffe289d0': device_add
+bus: 'platform': add device ffe289d0
+device: 'ffe28c20': device_add
+bus: 'platform': add device ffe28c20
+device: 'ffe2d168': device_add
+bus: 'platform': add device ffe2d168
+device: 'ffe2d780': device_add
+bus: 'platform': add device ffe2d780
+device: 'ffe2dd10': device_add
+bus: 'platform': add device ffe2dd10
+device: 'ffe2e2a8': device_add
+bus: 'platform': add device ffe2e2a8
+device: 'ffe2ba78': device_add
+bus: 'platform': add device ffe2ba78
+device: 'ffe2bbd8': device_add
+bus: 'platform': add device ffe2bbd8
+device: 'ffe2e478': device_add
+bus: 'platform': add device ffe2e478
+device: 'ffe2ef68': device_add
+bus: 'platform': add device ffe2ef68
+device: 'ffe2f8d0': device_add
+bus: 'platform': add device ffe2f8d0
+device: 'ffe302d0': device_add
+bus: 'platform': add device ffe302d0
+device: 'ffe30448': device_add
+bus: 'platform': add device ffe30448
+device: 'ffe305f0': device_add
+bus: 'platform': add device ffe305f0
+device: 'ffe30b40': device_add
+bus: 'platform': add device ffe30b40
+device: 'ffe30ea8': device_add
+bus: 'platform': add device ffe30ea8
+device: 'ffe310e8': device_add
+bus: 'platform': add device ffe310e8
+device: 'ffe31470': device_add
+bus: 'platform': add device ffe31470
+device: 'ffe31990': device_add
+bus: 'platform': add device ffe31990
+device: 'ffe31e50': device_add
+bus: 'platform': add device ffe31e50
+device: 'ffe323e8': device_add
+bus: 'platform': add device ffe323e8
+device: 'ffe32c80': device_add
+bus: 'platform': add device ffe32c80
+device: 'ffe332b8': device_add
+bus: 'platform': add device ffe332b8
+device: 'ffe33a68': device_add
+bus: 'platform': add device ffe33a68
+device: 'ffe33f58': device_add
+bus: 'platform': add device ffe33f58
+device: 'ffe34448': device_add
+bus: 'platform': add device ffe34448
+device: 'ffe34940': device_add
+bus: 'platform': add device ffe34940
+device: 'ffe34f58': device_add
+bus: 'platform': add device ffe34f58
+device class 'bdi': registering
+device class 'pci_bus': registering
+bus: 'pci': registered
+bus: 'pci_express': registered
+device class 'tty': registering
+device class 'vtconsole': registering
+device: 'vtcon0': device_add
+bus: 'serial': registered
+device class 'iommu': registering
+device class 'devlink': registering
+device class 'dma': registering
+bus: 'serial-base': registered
+bus: 'serial-base': add driver ctrl
+bus: 'serial-base': add driver port
+device: 'cpu0': device_add
+bus: 'cpu': add device cpu0
+bus: 'platform': add driver psycho
+bus: 'platform': add driver sabre
+bus: 'platform': __driver_probe_device: matched device ffe2e478 with driver sabre
+bus: 'platform': really_probe: probing driver sabre with device ffe2e478
+pci@1f,0: PCI IO [io  0x1fe02000000-0x1fe02ffffff] offset 1fe02000000
+pci@1f,0: PCI MEM [mem 0x1ff00000000-0x1ffefffffff] offset 1ff00000000
+pci@1f,0: SABRE PCI Bus Module ver[0:0]
+PCI: Scanning PBM /pci@1f,0
+device: 'pci0000:00': device_add
+device: '0000:00': device_add
+sabre ffe2e478: PCI host bridge to bus 0000:00
+pci_bus 0000:00: root bus resource [io  0x1fe02000000-0x1fe02ffffff] (bus address [0x0000-0xffffff])
+pci_bus 0000:00: root bus resource [mem 0x1ff00000000-0x1ffefffffff] (bus address [0x00000000-0xefffffff])
+pci_bus 0000:00: root bus resource [bus 00-03]
+pci 0000:00:01.1: [108e:5000] type 01 class 0x060400
+device: '0000:00:01.1': device_add
+bus: 'pci': add device 0000:00:01.1
+pci_bus 0000:01: extended config space not accessible
+device: '0000:01': device_add
+pci 0000:01:01.0: [108e:1000] type 00 class 0x068000
+pci 0000:01:01.0: reg 0x10: [mem 0x1ff20000000-0x1ff20ffffff]
+pci 0000:01:01.0: reg 0x14: [io  0x1fe02000000-0x1fe02007fff]
+device: '0000:01:01.0': device_add
+bus: 'pci': add device 0000:01:01.0
+pci 0000:01:03.0: enabling bus mastering
+pci 0000:01:03.0: [1095:0646] type 00 class 0x01018f
+pci 0000:01:03.0: reg 0x10: [io  0x1fe02008000-0x1fe02008007]
+pci 0000:01:03.0: reg 0x14: [io  0x1fe02008080-0x1fe02008083]
+pci 0000:01:03.0: reg 0x18: [io  0x1fe02008100-0x1fe02008107]
+pci 0000:01:03.0: reg 0x1c: [io  0x1fe02008180-0x1fe02008183]
+pci 0000:01:03.0: reg 0x20: [io  0x1fe02008200-0x1fe0200820f]
+device: '0000:01:03.0': device_add
+bus: 'pci': add device 0000:01:03.0
+pci 0000:00:01.0: [108e:5000] type 01 class 0x060400
+device: '0000:00:01.0': device_add
+bus: 'pci': add device 0000:00:01.0
+pci_bus 0000:02: extended config space not accessible
+device: '0000:02': device_add
+pci 0000:02:00.0: [1af4:1000] type 00 class 0x020000
+pci 0000:02:00.0: reg 0x10: [io  0x1fe02800000-0x1fe0280001f]
+pci 0000:02:00.0: reg 0x20: [mem 0x1ff60000000-0x1ff60003fff 64bit pref]
+device: '0000:02:00.0': device_add
+bus: 'pci': add device 0000:02:00.0
+pci 0000:02:01.0: [1b36:0001] type 00 class 0x060400
+pci 0000:02:01.0: reg 0x10: [mem 0x1ff60080000-0x1ff600800ff 64bit]
+device: '0000:02:01.0': device_add
+bus: 'pci': add device 0000:02:01.0
+pci 0000:02:02.0: [1af4:1004] type 00 class 0x010000
+pci 0000:02:02.0: reg 0x10: [io  0x1fe02802000-0x1fe0280203f]
+pci 0000:02:02.0: reg 0x20: [mem 0x1ff60200000-0x1ff60203fff 64bit pref]
+device: '0000:02:02.0': device_add
+bus: 'pci': add device 0000:02:02.0
+driver: 'sabre': driver_bound: bound to device 'ffe2e478'
+bus: 'platform': really_probe: bound device ffe2e478 to driver sabre
+bus: 'platform': add driver schizo
+bus: 'platform': add driver pci_sun4v
+bus: 'platform': add driver fire
+device: 'writeback': device_add
+bus: 'workqueue': add device writeback
+device class 'block': registering
+device class 'misc': registering
+iommu: Default domain type: Passthrough
+device class 'scsi_host': registering
+bus: 'scsi': registered
+device class 'scsi_device': registering
+SCSI subsystem initialized
+device class 'input': registering
+device class 'rtc': registering
+device class 'pps': registering
+pps_core: LinuxPPS API ver. 1 registered
+pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
+device class 'ptp': registering
+PTP clock support registered
+device class 'net': registering
+device: 'lo': device_add
+bus: 'platform': add driver rtc
+bus: 'platform': add driver mostek
+bus: 'platform': __driver_probe_device: matched device ffe302d0 with driver mostek
+bus: 'platform': really_probe: probing driver mostek with device ffe302d0
+/pci@1f,0/pci@1,1/ebus@1/eeprom@14,2000: Mostek regs at 0x1fe02002000
+Registering platform device 'rtc-m48t59.0'. Parent at platform
+device: 'rtc-m48t59.0': device_add
+bus: 'platform': add device rtc-m48t59.0
+driver: 'mostek': driver_bound: bound to device 'ffe302d0'
+bus: 'platform': really_probe: bound device ffe302d0 to driver mostek
+bus: 'platform': add driver bq4802
+bus: 'platform': add driver fhc
+bus: 'platform': add driver clock_board
+bus: 'platform': add driver auxio
+clocksource: Switched to clocksource tick
+device class 'mem': registering
+device: 'null': device_add
+device: 'zero': device_add
+device: 'full': device_add
+device: 'random': device_add
+device: 'urandom': device_add
+device: 'kmsg': device_add
+device: 'tty': device_add
+device: 'console': device_add
+device: 'tty0': device_add
+device class 'vc': registering
+device: 'vcs': device_add
+device: 'vcsu': device_add
+device: 'vcsa': device_add
+device: 'vcs1': device_add
+device: 'vcsu1': device_add
+device: 'vcsa1': device_add
+device: 'tty1': device_add
+device: 'tty2': device_add
+device: 'tty3': device_add
+device: 'tty4': device_add
+device: 'tty5': device_add
+device: 'tty6': device_add
+device: 'tty7': device_add
+device: 'tty8': device_add
+device: 'tty9': device_add
+device: 'tty10': device_add
+device: 'tty11': device_add
+device: 'tty12': device_add
+device: 'tty13': device_add
+device: 'tty14': device_add
+device: 'tty15': device_add
+device: 'tty16': device_add
+device: 'tty17': device_add
+device: 'tty18': device_add
+device: 'tty19': device_add
+device: 'tty20': device_add
+device: 'tty21': device_add
+device: 'tty22': device_add
+device: 'tty23': device_add
+device: 'tty24': device_add
+device: 'tty25': device_add
+device: 'tty26': device_add
+device: 'tty27': device_add
+device: 'tty28': device_add
+device: 'tty29': device_add
+device: 'tty30': device_add
+device: 'tty31': device_add
+device: 'tty32': device_add
+device: 'tty33': device_add
+device: 'tty34': device_add
+device: 'tty35': device_add
+device: 'tty36': device_add
+device: 'tty37': device_add
+device: 'tty38': device_add
+device: 'tty39': device_add
+device: 'tty40': device_add
+device: 'tty41': device_add
+device: 'tty42': device_add
+device: 'tty43': device_add
+device: 'tty44': device_add
+device: 'tty45': device_add
+device: 'tty46': device_add
+device: 'tty47': device_add
+device: 'tty48': device_add
+device: 'tty49': device_add
+device: 'tty50': device_add
+device: 'tty51': device_add
+device: 'tty52': device_add
+device: 'tty53': device_add
+device: 'tty54': device_add
+device: 'tty55': device_add
+device: 'tty56': device_add
+device: 'tty57': device_add
+device: 'tty58': device_add
+device: 'tty59': device_add
+device: 'tty60': device_add
+device: 'tty61': device_add
+device: 'tty62': device_add
+device: 'tty63': device_add
+device: 'hw_random': device_add
+NET: Registered PF_INET protocol family
+IP idents hash table entries: 32768 (order: 5, 262144 bytes, linear)
+tcp_listen_portaddr_hash hash table entries: 1024 (order: 1, 16384 bytes, linear)
+Table-perturb hash table entries: 65536 (order: 5, 262144 bytes, linear)
+TCP established hash table entries: 16384 (order: 4, 131072 bytes, linear)
+TCP bind hash table entries: 16384 (order: 6, 524288 bytes, linear)
+TCP: Hash tables configured (established 16384 bind 16384)
+UDP hash table entries: 1024 (order: 2, 32768 bytes, linear)
+UDP-Lite hash table entries: 1024 (order: 2, 32768 bytes, linear)
+NET: Registered PF_UNIX/PF_LOCAL protocol family
+PCI: CLS 0 bytes, default 64
+bus: 'platform': add driver power
+bus: 'platform': __driver_probe_device: matched device ffe30448 with driver power
+bus: 'platform': really_probe: probing driver power with device ffe30448
+power: Control reg at 1fe02007240
+driver: 'power': driver_bound: bound to device 'ffe30448'
+bus: 'platform': really_probe: bound device ffe30448 to driver power
+device: 'mdesc': device_add
+bus: 'clocksource': registered
+device: 'clocksource': device_add
+device: 'clocksource0': device_add
+bus: 'clocksource': add device clocksource0
+bus: 'platform': add driver alarmtimer
+bus: 'clockevents': registered
+device: 'clockevents': device_add
+device: 'clockevent0': device_add
+bus: 'clockevents': add device clockevent0
+bus: 'event_source': registered
+device: 'uprobe': device_add
+bus: 'event_source': add device uprobe
+device: 'kprobe': device_add
+bus: 'event_source': add device kprobe
+device: 'tracepoint': device_add
+bus: 'event_source': add device tracepoint
+device: 'software': device_add
+bus: 'event_source': add device software
+workingset: timestamp_bits=62 max_order=18 bucket_order=0
+9p: Installing v9fs 9p2000 file system support
+device class 'bsg': registering
+Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
+bus: 'platform': add driver simple-pm-bus
+bus: 'pci_express': add driver pciehp
+pciehp: pcie_port_service_register = 0
+bus: 'pci': add driver pcieport
+bus: 'pci': __driver_probe_device: matched device 0000:00:01.1 with driver pcieport
+bus: 'pci': really_probe: probing driver pcieport with device 0000:00:01.1
+pcieport 0000:00:01.1: runtime IRQ mapping not provided by arch
+pcieport: probe of 0000:00:01.1 rejects match -19
+bus: 'pci': __driver_probe_device: matched device 0000:00:01.0 with driver pcieport
+bus: 'pci': really_probe: probing driver pcieport with device 0000:00:01.0
+pcieport 0000:00:01.0: runtime IRQ mapping not provided by arch
+pcieport: probe of 0000:00:01.0 rejects match -19
+bus: 'pci': __driver_probe_device: matched device 0000:02:01.0 with driver pcieport
+bus: 'pci': really_probe: probing driver pcieport with device 0000:02:01.0
+pcieport 0000:02:01.0: runtime IRQ mapping not provided by arch
+pcieport: probe of 0000:02:01.0 rejects match -19
+bus: 'pci': add driver shpchp
+bus: 'pci': __driver_probe_device: matched device 0000:00:01.1 with driver shpchp
+bus: 'pci': really_probe: probing driver shpchp with device 0000:00:01.1
+shpchp 0000:00:01.1: runtime IRQ mapping not provided by arch
+shpchp: probe of 0000:00:01.1 rejects match -19
+bus: 'pci': __driver_probe_device: matched device 0000:00:01.0 with driver shpchp
+bus: 'pci': really_probe: probing driver shpchp with device 0000:00:01.0
+shpchp 0000:00:01.0: runtime IRQ mapping not provided by arch
+shpchp: probe of 0000:00:01.0 rejects match -19
+bus: 'pci': __driver_probe_device: matched device 0000:02:01.0 with driver shpchp
+bus: 'pci': really_probe: probing driver shpchp with device 0000:02:01.0
+shpchp 0000:02:01.0: runtime IRQ mapping not provided by arch
+shpchp 0000:02:01.0: HPC vendor_id 1b36 device_id 1 ss_vid 0 ss_did 0
+shpchp 0000:02:01.0: Can't get msi for the hotplug controller
+shpchp 0000:02:01.0: Use INTx for the hotplug controller
+Unable to handle kernel NULL pointer dereference
+tsk->{mm,active_mm}->context = 0000000000000000
+tsk->{mm,active_mm}->pgd = fffff80000402000
+              \|/ ____ \|/
+              "@'/ .. \`@"
+              /_| \__/ |_\
+                 \__U_/
+swapper/0(1): Oops [#1]
+CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.5.0-ktest-02812-g4d2faeb4fb58 #10
+TSTATE: 0000004411001601 TPC: 00000000007e5f98 TNPC: 00000000007e5fbc Y: 00000000    Not tainted
+TPC: <shpc_init+0x638/0x900>
+g0: fffff8000228ca18 g1: 0000000000000000 g2: 0000000000001f00 g3: 0000000000000000
+g4: fffff80002148000 g5: fffff8007e410000 g6: fffff800021a4000 g7: 0000000000000001
+o0: 0000000000000000 o1: 00000000007e4da0 o2: 0000000000000000 o3: 0000000000000000
+o4: 0000000000b9b950 o5: 0000000000000000 sp: fffff800021a6b01 ret_pc: 00000000007e607c
+RPC: <shpc_init+0x71c/0x900>
+l0: 00000000015ef800 l1: 00000000ff1f7fff l2: 0000000000b78440 l3: 0000000000b9c6b0
+l4: 000000000000001f l5: 000000007f000000 l6: fffff80002553280 l7: fffff800022f7680
+i0: fffff8000254ea00 i1: fffff800021f6000 i2: 00000000015ef800 i3: 0000000000000000
+i4: 0000000000b9b800 i5: 0000000000000000 i6: fffff800021a6bc1 i7: 00000000007e29f0
+I7: <shpc_probe+0x70/0x3a0>
+Call Trace:
+[<00000000007e29f0>] shpc_probe+0x70/0x3a0
+[<00000000007c5bf8>] pci_device_probe+0x78/0x100
+[<0000000000a6b70c>] really_probe+0x16c/0x41c
+[<0000000000a6ba68>] __driver_probe_device.part.0+0xac/0xc0
+[<0000000000846b28>] driver_probe_device+0x88/0x120
+[<0000000000846d64>] __driver_attach+0x84/0x1c0
+[<0000000000844bb4>] bus_for_each_dev+0x54/0xc0
+[<000000000084659c>] driver_attach+0x1c/0x40
+[<0000000000845e24>] bus_add_driver+0xe4/0x1e0
+[<0000000000847cfc>] driver_register+0x7c/0x140
+[<00000000007c5028>] __pci_register_driver+0x48/0x60
+[<0000000001398e64>] shpcd_init+0x18/0x68
+[<0000000000427c90>] do_one_initcall+0x30/0x240
+[<000000000137eea4>] kernel_init_freeable+0x1d4/0x22c
+[<0000000000a6d824>] kernel_init+0x1c/0x138
+[<00000000004060c8>] ret_from_fork+0x1c/0x2c
+Disabling lock debugging due to kernel taint
+Caller[00000000007e29f0]: shpc_probe+0x70/0x3a0
+Caller[00000000007c5bf8]: pci_device_probe+0x78/0x100
+Caller[0000000000a6b70c]: really_probe+0x16c/0x41c
+Caller[0000000000a6ba68]: __driver_probe_device.part.0+0xac/0xc0
+Caller[0000000000846b28]: driver_probe_device+0x88/0x120
+Caller[0000000000846d64]: __driver_attach+0x84/0x1c0
+Caller[0000000000844bb4]: bus_for_each_dev+0x54/0xc0
+Caller[000000000084659c]: driver_attach+0x1c/0x40
+Caller[0000000000845e24]: bus_add_driver+0xe4/0x1e0
+Caller[0000000000847cfc]: driver_register+0x7c/0x140
+Caller[00000000007c5028]: __pci_register_driver+0x48/0x60
+Caller[0000000001398e64]: shpcd_init+0x18/0x68
+Caller[0000000000427c90]: do_one_initcall+0x30/0x240
+Caller[000000000137eea4]: kernel_init_freeable+0x1d4/0x22c
+Caller[0000000000a6d824]: kernel_init+0x1c/0x138
+Caller[00000000004060c8]: ret_from_fork+0x1c/0x2c
+Caller[0000000000000000]: 0x0
+Instruction DUMP:
+ c20c2219 
+ 80a06000 
+ 0240000a 
+<d628e0da>
+ d25e2048 
+ 15002e71 
+ 11002de1 
+ 960ae0ff 
+ 9412a3a0 
+
+Kernel panic - not syncing: Fatal exception
+Press Stop-A (L1-A) from sun keyboard or send break
+twice on console to return to the boot prom
+---[ end Kernel panic - not syncing: Fatal exception ]---
+qemu-system-sparc64: terminating on signal 2
+
+```
+Steps to reproduce:
+1. compile a sparc64 kernel (config file included)
+2. add a config where a pci-bridge is installed in slot 1,2 or 3 (virtio-slot-pci takes the first slot)
+3. create a empty file using fallocate
+Additional information:
+attached: tar.xz file:
+- linux arch/sparc64/boot/image (uncompressed) as vmlinuz
+- linux .config file as config
+- linux modules in the lib directory
+
+[sparckernelinfo.tar.xz](/uploads/55f1475c5c811cd56d1374386e8f9e6e/sparckernelinfo.tar.xz)
diff --git a/results/classifier/gemma3:12b/kernel/1929 b/results/classifier/gemma3:12b/kernel/1929
new file mode 100644
index 00000000..5632fc42
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1929
@@ -0,0 +1,22 @@
+
+regression: 7.0.0 breaks registering process subreaper on Apple silicon
+Description of problem:
+When running any container on the QEMU virtual guest that is using a utility like `tini` which is trying to register itself as a process subreaper I get an error message like this:
+
+```
+[FATAL tini (1)] PR_SET_CHILD_SUBREAPER is unavailable on this platform. Are you using Linux >= 3.4?
+```
+
+The issue has been observed by multiple people on Apple silicon Macs, e.g. in these issues:
+https://github.com/docker/for-mac/issues/6620#issuecomment-1694380189
+https://github.com/GoogleCloudPlatform/spark-on-k8s-operator/issues/1735
+Steps to reproduce:
+1. Install QEMU 7.0.0+ on an Apple silicon MAC
+2. Run a virtual guest
+3. Try to register a process subreaper, e.g. like `tini -s` does
+Additional information:
+the issue was introduced in QEMU 7.0.0 with this commit:
+https://gitlab.com/qemu-project/qemu/-/commit/220717a6f46a99031a5b1af964bbf4dec1310440
+
+tini readme talking about process subreaping:
+https://github.com/krallin/tini#subreaping
diff --git a/results/classifier/gemma3:12b/kernel/1939179 b/results/classifier/gemma3:12b/kernel/1939179
new file mode 100644
index 00000000..31905b27
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1939179
@@ -0,0 +1,22 @@
+
+qemu-ga fsfreeze crashes the kernel
+
+Hello,
+
+Still required your attention, duplicate from:
+https://bugs.launchpad.net/bugs/1807073
+https://bugs.launchpad.net/bugs/1813045
+
+We use mainly Cloudlinux, Debian and Centos.
+We experienced many crashes on our qemu instances based on Cloudlinux during a snapshot.
+The issue is not related to CloudLinux directly, but to Qemu agent, which does not freeze the file system(s) correctly. What is actually happening:
+
+When VM backup is invoked, Qemu agent freezes the file systems, so no single change will be made during the backup. But Qemu agent does not respect the loop* devices in freezing order (we have checked its sources), which leads to the next situation:
+1) freeze loopback fs
+              ---> send async reqs to loopback thread
+2) freeze main fs
+3) loopback thread wakes up and trying to write data to the main fs, which is still frozen, and this finally leads to the hung task and kernel crash.
+
+Moreover, a lot of Proxmox users are complaining about the issue as well:
+https://forum.proxmox.com/threads/error-vm-100-qmp-command-guest-fsfreeze-thaw-failed-got-timeout.68082/
+https://forum.proxmox.com/threads/problem-with-fsfreeze-freeze-and-qemu-guest-agent.65707/
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1945540 b/results/classifier/gemma3:12b/kernel/1945540
new file mode 100644
index 00000000..f4b788fd
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1945540
@@ -0,0 +1,64 @@
+
+Java crashes on s390x VM with SIGILL/ILL_PRVOPC at '__kernel_getcpu+0x8'
+
+Host environment
+
+- Operating system: Ubuntu 20.04.3 LTS Desktop
+- OS/kernel version: Linux tower 5.11.0-37-generic #41~20.04.2-Ubuntu
+    SMP Fri Sep 24 09:06:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
+- Architecture: amd64
+- QEMU flavor: qemu-system-s390x
+- QEMU version: QEMU emulator version 4.2.1 (Debian 1:4.2-3ubuntu6.17)
+- QEMU command line: See attached file 'command-line.txt'
+
+Emulated/Virtualized environment
+
+- Operating system: Ubuntu 20.04.3 LTS Server
+- OS/kernel version: Linux s390x-focal 5.4.0-88-generic #99-Ubuntu
+    SMP Thu Sep 23 17:27:44 UTC 2021 s390x s390x s390x GNU/Linux
+- Architecture: s390x
+
+Description of problem
+
+Java crashes as shown below:
+
+$ java --version
+#
+# A fatal error has been detected by the Java Runtime Environment:
+#
+#  SIGILL (0x4) at pc=0x000003ff9f5fe6f4, pid=6789, tid=6818
+#
+# JRE version:  (17.0+35) (build )
+# Java VM: OpenJDK 64-Bit Server VM (17+35-snap, mixed mode, sharing,
+# tiered, compressed oops, compressed class ptrs, g1 gc, linux-s390x)
+# Problematic frame:
+# C  [linux-vdso64.so.1+0x6f8]  __kernel_getcpu+0x8
+#
+# Core dump will be written. Default location: core.6789 (may not
+# exist)
+#
+# An error report file with more information is saved as:
+# /home/ubuntu/src/hs_err_pid6789.log
+#
+#
+Aborted (core dumped)
+
+Steps to reproduce
+
+Run any Java program to reproduce the problem.
+
+Because the 'openjdk' packages in Ubuntu run the 'java' command during installation, they hit the same error and fail to install. As an alternative, you can install the OpenJDK Snap package for the 's390x' architecture as follows:
+
+  $ sudo snap install openjdk
+
+The OpenJDK Snap package has been tested to work on a real IBM/S390 8561 system, namely the IBM LinuxONE III LT1 at Marist College:
+
+  Marist College Installs World’s First IBM LinuxONE III™
+  https://www.marist.edu/-/marist-first-linuxone-iii
+
+Additional information
+
+See the following attached files:
+
+command-line.txt - the command-line used to start the virtual machine
+hs_err_pid6789.log - the log file resulting from 'java --version'
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/1950 b/results/classifier/gemma3:12b/kernel/1950
new file mode 100644
index 00000000..4762d0dc
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1950
@@ -0,0 +1,10 @@
+
+[AARCH64] GP bit (BTI) lost during two stages translation
+Description of problem:
+I noticed that the BTI faults were not reported.
+That's because the GP (guarded page) information is lost during the two stages translation in get_phys_addr_twostage().
+The "guarded" information is correctly retrieved by the first call to get_phys_addr_nogpc() but overwritten by the the second call to get_phys_addr_nogpc().
+The call to combine_cacheattrs() copies cacheattrs1.guarded but this field is never modified.
+
+The attached patch fixes the issue for me.
+[get_phys_addr_twostage_bti_gp_bit_lost_master.patch](/uploads/2fbe8090f92c43a63e39ee66ab2daf47/get_phys_addr_twostage_bti_gp_bit_lost_master.patch)
diff --git a/results/classifier/gemma3:12b/kernel/1952 b/results/classifier/gemma3:12b/kernel/1952
new file mode 100644
index 00000000..b9cd9059
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1952
@@ -0,0 +1,97 @@
+
+elf-linux-user: segfault caused by invalid loaddr extracted by the ELF loader
+Description of problem:
+Emulating ELF binaries as emitted by Zig may lead to segfault in QEMU, which typically looks like this
+
+```
+$ qemu-x86_64 simple
+fish: Job 1, 'qemu-x86_64 simple' terminated by signal SIGSEGV (Address boundary error)
+```
+Steps to reproduce:
+1. Obtain latest Zig nightly
+2. Compile simple static C program using Zig's ELF linker:
+
+```
+$ echo "int main() { return 0 };" > simple.c
+$ zig build-exe simple.c -lc -target x86_64-linux-musl -fno-lld --image-base 0x1000000
+$ qemu-x86_64 simple
+fish: Job 1, 'qemu-x86_64 simple' terminated by signal SIGSEGV (Address boundary error)
+```
+Additional information:
+Note that running `simple` directly it's correctly mmaped and executed by the kernel:
+
+```
+$ ./simple
+$ echo $status
+0
+``` 
+
+The reason this happens is because of an assumption QEMU's ELF loader makes on the virtual addresses and offsets of `PT_LOAD` segments, namely:
+
+```
+vaddr2 - vaddr1 >= off2 - off1
+```
+
+Typically, to the best of my knowledge, this is conformed to by the linkers in the large, but it is not required at all. Here's a one-line tweak to QEMU's loader that fixes the segfault:
+
+```diff
+diff --git a/linux-user/elfload.c b/linux-user/elfload.c
+index f21e2e0c3d..eabb4fed03 100644
+--- a/linux-user/elfload.c
++++ b/linux-user/elfload.c
+@@ -3211,7 +3211,7 @@ static void load_elf_image(const char *image_name, int image_fd,
+     for (i = 0; i < ehdr->e_phnum; ++i) {
+         struct elf_phdr *eppnt = phdr + i;
+         if (eppnt->p_type == PT_LOAD) {
+-            abi_ulong a = eppnt->p_vaddr - eppnt->p_offset;
++            abi_ulong a = eppnt->p_vaddr & ~(eppnt->p_align - 1);
+             if (a < loaddr) {
+                 loaddr = a;
+             }
+```
+
+The reason why this breaks for ELF binaries emitted by Zig is that while virtual addresses are allocated sequentially or pre-allocated, file offsets are allocated on a best-effort basis wherever there is enough space in the file to fit a given section/segment so that we can move the contents in file while preserving the allocated virtual addresses on a whim. To provide a more concrete example, here's the load segment layout for `simple` as emitted by Zig:
+
+```
+$ readelf -l simple
+
+Elf file type is EXEC (Executable file)
+Entry point 0x1002000
+There are 7 program headers, starting at offset 64
+
+Program Headers:
+  Type           Offset             VirtAddr           PhysAddr
+                 FileSiz            MemSiz              Flags  Align
+  PHDR           0x0000000000000040 0x0000000001000040 0x0000000001000040
+                 0x0000000000000188 0x0000000000000188  R      0x8
+  LOAD           0x0000000000000000 0x0000000001000000 0x0000000001000000
+                 0x00000000000001c8 0x00000000000001c8  R      0x1000
+  LOAD           0x0000000000021000 0x0000000001001000 0x0000000001001000
+                 0x0000000000000078 0x0000000000000078  R      0x1000
+  LOAD           0x0000000000022000 0x0000000001002000 0x0000000001002000
+                 0x000000000000065a 0x000000000000065a  R E    0x1000
+  LOAD           0x0000000000023000 0x0000000001003000 0x0000000001003000
+                 0x0000000000000060 0x0000000000000278  RW     0x1000
+  GNU_EH_FRAME   0x0000000000021064 0x0000000001001064 0x0000000001001064
+                 0x0000000000000014 0x0000000000000014  R      0x4
+  GNU_STACK      0x0000000000000000 0x0000000000000000 0x0000000000000000
+                 0x0000000000000000 0x0000000000000000  RW     0x1
+
+ Section to Segment mapping:
+  Segment Sections...
+   00
+   01
+   02     .rodata.str1.1 .rodata .eh_frame .eh_frame_hdr
+   03     .text .init .fini
+   04     .data .got .bss
+   05     .eh_frame_hdr
+   06
+```
+
+As you can see, initially `loaddr := 0x1000000 - 0x0 = 0x1000000`. However, upon iterating over the second load segment, we already get
+
+```
+a := 0x1001000 - 0x21000 = 0xfe000
+```
+
+and since `a < loaddr`, we incorrectly set `loaddr := 0xfe000`.
diff --git a/results/classifier/gemma3:12b/kernel/1967 b/results/classifier/gemma3:12b/kernel/1967
new file mode 100644
index 00000000..ddc6a069
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1967
@@ -0,0 +1,2 @@
+
+Guest SIGRTMIN remapped incorrectly
diff --git a/results/classifier/gemma3:12b/kernel/1977 b/results/classifier/gemma3:12b/kernel/1977
new file mode 100644
index 00000000..36a9974c
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1977
@@ -0,0 +1,31 @@
+
+MSYS2 build fails with link errors on Window 10  22H2
+Description of problem:
+Linking target tests/plugin/libbb.dll fails with undefined references in below attached output
+Steps to reproduce:
+1. Open MSYS2 build environment on Windows 10
+2. mkdir build && cd build && ../configure --prefix=/home/Admin --enable-sdl --enable-gtk --target-list=arm-softmmu
+3. make -j4
+Additional information:
+[2300/2631] Linking target tests/plugin/libbb.dll
+FAILED: tests/plugin/libbb.dll
+"cc" "-m64" "-mcx16"  -o tests/plugin/libbb.dll plugins/qemu_plugin_api.lib tests/plugin/libbb.dll.p/bb.c.obj tests/plugin/libbb.dll.p/.._.._contrib_plugins_win32_linker.c.obj "-Wl,--allow-shlib-undefined" "-shared" "-Wl,--start-group" "-Wl,--out-implib=tests/plugin/libbb.dll.a" "-fstack-protector-strong" "-Wl,--no-seh" "-Wl,--nxcompat" "-Wl,--dynamicbase" "-Wl,--high-entropy-va" "-Wl,--warn-common" "C:/msys64/ucrt64/lib/libglib-2.0.dll.a" "C:/msys64/ucrt64/lib/libintl.dll.a" "C:/msys64/ucrt64/lib/libgmodule-2.0.dll.a" "-lkernel32" "-luser32" "-lgdi32" "-lwinspool" "-lshell32" "-lole32" "-loleaut32" "-luuid" "-lcomdlg32" "-ladvapi32" "-Wl,--end-group"
+C:/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: tests/plugin/libbb.dll.p/bb.c.obj: in function `vcpu_tb_trans':
+C:\msys64\home\Admin\qemu\build/../tests/plugin/bb.c:84:(.text+0x4f): undefined reference to `__imp_qemu_plugin_tb_n_insns'
+C:/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: C:\msys64\home\Admin\qemu\build/../tests/plugin/bb.c:87:(.text+0x62): undefined reference to `__imp_qemu_plugin_register_vcpu_tb_exec_inline'
+C:/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: C:\msys64\home\Admin\qemu\build/../tests/plugin/bb.c:93:(.text+0xba): undefined reference to `__imp_qemu_plugin_register_vcpu_tb_exec_cb'
+C:/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: tests/plugin/libbb.dll.p/bb.c.obj: in function `plugin_exit':
+C:\msys64\home\Admin\qemu\build/../tests/plugin/bb.c:55:(.text+0x1cb): undefined reference to `__imp_qemu_plugin_outs'
+C:/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: C:\msys64\home\Admin\qemu\build/../tests/plugin/bb.c:55:(.text+0x204): undefined reference to `__imp_qemu_plugin_outs'
+C:/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: tests/plugin/libbb.dll.p/bb.c.obj: in function `vcpu_idle':
+C:\msys64\home\Admin\qemu\build/../tests/plugin/bb.c:66:(.text+0x299): undefined reference to `__imp_qemu_plugin_outs'
+C:/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: tests/plugin/libbb.dll.p/bb.c.obj: in function `qemu_plugin_install':
+C:\msys64\home\Admin\qemu\build/../tests/plugin/bb.c:114:(.text+0x2e8): undefined reference to `__imp_qemu_plugin_bool_parse'
+C:/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: C:\msys64\home\Admin\qemu\build/../tests/plugin/bb.c:141:(.text+0x3d5): undefined reference to `__imp_qemu_plugin_register_vcpu_tb_trans_cb'
+C:/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: C:\msys64\home\Admin\qemu\build/../tests/plugin/bb.c:142:(.text+0x3ea): undefined reference to `__imp_qemu_plugin_register_atexit_cb'
+C:/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: C:\msys64\home\Admin\qemu\build/../tests/plugin/bb.c:138:(.text+0x420): undefined reference to `__imp_qemu_plugin_register_vcpu_idle_cb'
+collect2.exe: error: ld returned 1 exit status
+[2301/2631] Compiling C object tests/plugin/libempty.dll.p/.._.._contrib_plugins_win32_linker.c.obj
+[2302/2631] Compiling C object tests/libtestqapi.a.p/meson-generated_.._test-qapi-visit.c.obj
+[2303/2631] Compiling C object tests/plugin/libinsn.dll.p/.._.._contrib_plugins_win32_linker.c.obj
+ninja: build stopped: subcommand failed.
diff --git a/results/classifier/gemma3:12b/kernel/1983 b/results/classifier/gemma3:12b/kernel/1983
new file mode 100644
index 00000000..3c4e5690
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1983
@@ -0,0 +1,31 @@
+
+Guest boot displays "virtio: device uses modern interface but does not have VIRTIO_F_VERSION_1" and then happens Call Trace
+Description of problem:
+Guest boot displays "FATAL: Module scsi_wait_scan not found", and then happens Call Trace.
+
+```
+Call Trace:
+ dump_stack+0x4f/0x66
+ panic+0xa2/0x258
+ do_exit+0x858/0xab0
+ do_group_exit+0x2f/0x90
+ ? do_page_fault+0x18c/0x4c0
+ sys_exit_group+0x11/0x20
+ do_fast_syscall_32+0x8b/0x1c2
+ entry_SYSENTER_32+0xa5/0xf8
+EIP: 0xb7fcec71
+Code: 89 01 31 c0 89 51 04 89 71 08 89 79 0c eb 03 83 c8 ff 83 c4 28 5b 5e 5f 5d c3 8b 1c 24 c3 90 90 90 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d 76 00 58 b8 77 00 00 00 cd 80 90 8d 76
+EAX: ffffffda EBX: 00000001 ECX: 034c4745 EDX: 00000000
+ESI: 00000000 EDI: 00000000 EBP: bff7db18 ESP: bff7da3c
+DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b EFLAGS: 00000246
+Kernel Offset: 0x16c00000 from 0xc0400000 (relocation range: 0xc0000000-0xf75fdfff)
+```
+Steps to reproduce:
+1.Create guest by using the command
+   ```
+   ./qemu-system-x86_64 -accel kvm -m 4096 -smp 4 -cpu host  -drive file=test-img.qcow2,format=qcow2,if=none,id=virtio-disk0 -device virtio-blk-pci,drive=virtio-disk0,bootindex=0 -monitor pty -daemonize -vnc :32137 -device virtio-net-pci,netdev=nic0,mac=00:c2:58:38:8e:f0 -netdev tap,id=nic0,br=virbr0,helper=/usr/local/libexec/qemu-bridge-helper,vhost=on
+   ```
+Additional information:
+Suspected to be a QEMU regression issue, the first bad commit id: 14f5a7bae4cb5ca45a03e16b5bb0c5d766fd51b7.
+
+Latest successful version commit id: cea3ea670fe265421131aad90c36fbb87bc4d206
diff --git a/results/classifier/gemma3:12b/kernel/1985 b/results/classifier/gemma3:12b/kernel/1985
new file mode 100644
index 00000000..80c2024d
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1985
@@ -0,0 +1,2 @@
+
+Possible infinite loop in target/arm/sme_helper.c: helper_sme_fmopa_h
diff --git a/results/classifier/gemma3:12b/kernel/1990 b/results/classifier/gemma3:12b/kernel/1990
new file mode 100644
index 00000000..60fdafa7
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1990
@@ -0,0 +1,20 @@
+
+qemu ASSERT [ArmCpuDxe] DefaultExceptionHandler.c:333 on Mac M3
+Description of problem:
+I am installing Podman 4.7.2 and `podman-machine` uses `qemu-system-aarch64` to boot up an embedded coreos image to run containers.
+With the new Apple M3 hardware, I am experiencing a QEMU assertion failure almost all of the time.
+
+![image](/uploads/372b9ae2dfaa2d70e704a0f30b1964f1/image.png)
+
+`ASSERT [ArmCpuDxe] /home/kraxel/projects/qemu/roms/edk2/ArmPkg/Library/DefaultExceptionHandlerLib/AArch64/DefaultExceptionHandler.c(333): ((BOOLEAN)(0==1))`
+
+I have been unable to get the full crash output - I didn't figure out how to resize the console any larger, and I tried a couple different ways to hook the console up to qemu stdout without any success. (since the kernel command line parameters are not passed in, but instead the image uses a bootloader)
+
+I believe this is the same issue I experience, but with a better capture of the crash:
+https://github.com/lima-vm/lima/issues/1996
+Steps to reproduce:
+1. Use Mac M3 (Max in my case)
+2. Install Podman
+3. Run `podman-machine init`
+4. Run `podman-machine start --log-level=debug`
+5. Crash (almost certainly)
diff --git a/results/classifier/gemma3:12b/kernel/2000 b/results/classifier/gemma3:12b/kernel/2000
new file mode 100644
index 00000000..fddbd9f2
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2000
@@ -0,0 +1,46 @@
+
+m68k: error "fatal: Unimplemented control register write 0x0 = 0x1"
+Description of problem:
+An attempt to run the NetBSD m68k kernel under QEMU crashes.
+The error message is:
+```
+qemu: fatal: Unimplemented control register write 0x0 = 0x1
+```
+Steps to reproduce:
+1. ```wget http://cdn.netbsd.org/pub/NetBSD/iso/9.3/NetBSD-9.3-mac68k.iso```
+2. Pull kernel out of the installation CD:
+```
+sudo mount -r -t iso9660 -o loop /home/bruno/vms/os-install-media/NetBSD-9.3-mac68k.iso /mnt
+cp /mnt/mac68k/binary/kernel/netbsd-GENERIC.gz .
+sudo umount /mnt
+chmod u+w netbsd-GENERIC.gz
+gunzip netbsd-GENERIC.gz
+```
+3. ```qemu-img create -f qcow2 netbsd93.qcow2 10G```
+4. ```qemu-system-m68k -m 256 -drive file=netbsd93.qcow2,format=qcow2,index=0 -nographic -kernel netbsd-GENERIC -cdrom NetBSD-9.3-mac68k.iso```
+
+It crashes like this:
+```
+qemu: fatal: Unimplemented control register write 0x0 = 0x1
+
+D0 = 00000001   A0 = 00000000   F0 = 7fff ffffffffffffffff  (         nan)
+D1 = 00000000   A1 = 00000000   F1 = 7fff ffffffffffffffff  (         nan)
+D2 = 00000000   A2 = 00000000   F2 = 7fff ffffffffffffffff  (         nan)
+D3 = 00000000   A3 = 00000000   F3 = 7fff ffffffffffffffff  (         nan)
+D4 = 00000000   A4 = 00000000   F4 = 7fff ffffffffffffffff  (         nan)
+D5 = 00000000   A5 = 00000000   F5 = 7fff ffffffffffffffff  (         nan)
+D6 = 00000000   A6 = 00000000   F6 = 7fff ffffffffffffffff  (         nan)
+D7 = 00000000   A7 = 00330346   F7 = 7fff ffffffffffffffff  (         nan)
+PC = 00002e14   SR = 2700 T:0 I:7 SI -----
+FPSR = 00000000 ----
+                                FPCR =     0000 X RN
+  A7(MSP) = 00000000 ->A7(USP) = 00330346   A7(ISP) = 00000000
+VBR = 0x00000000
+SFC = 0 DFC 0
+SSW 00000000 TCR 00000000 URP 00000000 SRP 00000000
+DTTR0/1: 00000000/00000000 ITTR0/1: 00000000/00000000
+MMUSR 00000000, fault at 00000000
+Aborted (core dumped)
+```
+Additional information:
+
diff --git a/results/classifier/gemma3:12b/kernel/2005 b/results/classifier/gemma3:12b/kernel/2005
new file mode 100644
index 00000000..cba3e4df
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2005
@@ -0,0 +1,30 @@
+
+qemu-system-aarch64: ../target/arm/helper.c:6757: sve_vqm1_for_el_sm: Assertion `sm' failed.
+Description of problem:
+Qemu crashes when sve is completely disabled for CPU model "max" (`-cpu max,sve=off`). Using any CPU model which does not include SVE, or using only e.g. SVE128 (`-cpu max,sve128=on`) works fine.\
+\
+`#0  0x00007f94b8291dec in __pthread_kill_implementation () at /lib64/libc.so.6 `\
+`#1  0x00007f94b823f0c6 in raise () at /lib64/libc.so.6 `\
+`#2  0x00007f94b82268d7 in abort () at /lib64/libc.so.6 `\
+`#3  0x00007f94b82267eb in _nl_load_domain.cold () at /lib64/libc.so.6 `\
+`#4  0x00007f94b8237016 in  () at /lib64/libc.so.6 `\
+`#5  0x000055d6794aa698 in sve_vqm1_for_el_sm (env=env@entry=0x55d67c6ff9b0, el=el@entry=1, sm=false) at ../target/arm/helper.c:6757 `\
+`#6  0x000055d6794afc29 in sve_vqm1_for_el (el=1, env=0x55d67c6ff9b0) at ../target/arm/helper.c:6763 `\
+`#7  smcr_write (env=0x55d67c6ff9b0, ri=0x55d67c78f600, value=<optimized out>) at ../target/arm/helper.c:6887 `\
+`#8  0x00007f9469bad101 in code_gen_buffer () `\
+`#9  0x000055d67977dc19 in cpu_tb_exec (cpu=cpu@entry=0x55d67c6fd1f0, itb=<optimized out>, tb_exit=tb_exit@entry=0x7f94acdcc4c4) at ../accel/tcg/cpu-exec.c:457 `\
+`#10 0x000055d67977e59f in cpu_loop_exec_tb (tb_exit=0x7f94acdcc4c4, last_tb=<synthetic pointer>, pc=<optimized out>, tb=<optimized out>, cpu=<optimized out>) at ../accel/tcg/cpu-exec.c:919 `\
+`#11 cpu_exec_loop (cpu=cpu@entry=0x55d67c6fd1f0, sc=sc@entry=0x7f94acdcc570) at ../accel/tcg/cpu-exec.c:1040 `\
+`#12 0x000055d67977ee7d in cpu_exec_setjmp (cpu=0x55d67c6fd1f0, sc=0x7f94acdcc570) at ../accel/tcg/cpu-exec.c:1057 `\
+`#13 0x000055d679787c3d in cpu_exec (cpu=0x55d67c6fd1f0) at ../accel/tcg/cpu-exec.c:1083 `\
+`#14 0x000055d6797a1d52 in tcg_cpus_exec (cpu=0x55d67c6fd1f0) at ../accel/tcg/tcg-accel-ops.c:75 `\
+`#15 mttcg_cpu_thread_fn (arg=arg@entry=0x55d67c6fd1f0) at ../accel/tcg/tcg-accel-ops-mttcg.c:95 `\
+`#16 0x000055d679938698 in qemu_thread_start (args=0x55d67c7a1500) at ../util/qemu-thread-posix.c:541 `\
+`#17 0x00007f94b828ff44 in start_thread () at /lib64/libc.so.6 `\
+`#18 0x00007f94b8318314 in clone () at /lib64/``libc.so``.6`\
+ \
+This happens when the system is booting, i.e. grub has just finished, loaded kernel and initrd, and the kernel has just began to run, i.e. early in the kernel startup.
+Steps to reproduce:
+1. 
+2. 
+3.
diff --git a/results/classifier/gemma3:12b/kernel/2013 b/results/classifier/gemma3:12b/kernel/2013
new file mode 100644
index 00000000..30c0230e
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2013
@@ -0,0 +1,79 @@
+
+The avocado test replay_kernel.py:ReplayKernelNormal.test_mips64el_malta is unreliable
+Description of problem:
+This test keeps hanging on CI
+Steps to reproduce:
+Run the test on GitLab's CI infrastructure and it will hang on replay. Examples: https://gitlab.com/stsquad/qemu/-/jobs/5664260736
+Additional information:
+Excerpt from log:
+
+```
+18:02:49 DEBUG| Transitioning from 'Runstate.CONNECTING' to 'Runstate.RUNNING'.
+18:02:49 DEBUG| Opening console file
+18:02:49 DEBUG| Opening console socket
+18:02:49 DEBUG| [    0.000000] Initializing cgroup subsys cpuset
+18:02:49 DEBUG| [    0.000000] Initializing cgroup subsys cpu
+18:02:49 DEBUG| [    0.000000] Linux version 2.6.32-5-5kc-malta (Debian 2.6.32-48) (ben@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Fri Feb 15 21:38:11 UTC 2013
+18:02:49 DEBUG| [    0.000000]
+18:02:49 DEBUG| [    0.000000] LINUX started...
+18:02:49 DEBUG| [    0.000000] bootconsole [early0] enabled
+18:02:49 DEBUG| [    0.000000] CPU revision is: 000182a0 (MIPS 20Kc)
+18:02:49 DEBUG| [    0.000000] FPU revision is: 000f8200
+18:02:49 DEBUG| [    0.000000] Checking for the multiply/shift bug... no.
+18:02:49 DEBUG| [    0.000000] Checking for the daddiu bug... no.
+18:02:49 DEBUG| [    0.000000] Determined physical RAM map:
+18:02:49 DEBUG| [    0.000000]  memory: 0000000000001000 @ 0000000000000000 (reserved)
+18:02:49 DEBUG| [    0.000000]  memory: 00000000000ef000 @ 0000000000001000 (ROM data)
+18:02:49 DEBUG| [    0.000000]  memory: 0000000000659000 @ 00000000000f0000 (reserved)
+18:02:49 DEBUG| [    0.000000]  memory: 00000000078b7000 @ 0000000000749000 (usable)
+18:02:49 DEBUG| [    0.000000] Wasting 104440 bytes for tracking 1865 unused pages
+18:02:49 DEBUG| [    0.000000] Initrd not found or empty - disabling initrd
+18:02:49 DEBUG| [    0.000000] Zone PFN ranges:
+18:02:49 DEBUG| [    0.000000]   DMA      0x00000000 -> 0x00001000
+18:02:49 DEBUG| [    0.000000]   Normal   0x00001000 -> 0x00008000
+18:02:49 DEBUG| [    0.000000] Movable zone start PFN for each node
+18:02:49 DEBUG| [    0.000000] early_node_map[1] active PFN ranges
+18:02:49 DEBUG| [    0.000000]     0: 0x00000000 -> 0x00008000
+18:02:49 DEBUG| [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32320
+18:02:49 DEBUG| [    0.000000] Kernel command line: printk.time=1 panic=-1 console=ttyS0
+18:02:49 DEBUG| Shutting down VM appliance; timeout=30
+18:02:49 DEBUG| Attempting graceful termination
+18:02:49 DEBUG| Closing console file
+18:02:49 DEBUG| Closing console socket
+18:02:49 DEBUG| Politely asking QEMU to terminate
+...
+
+18:02:49 DEBUG| Transitioning from 'Runstate.CONNECTING' to 'Runstate.RUNNING'.
+18:02:49 DEBUG| Opening console file
+18:02:49 DEBUG| Opening console socket
+18:02:49 DEBUG| [    0.000000] Initializing cgroup subsys cpuset
+18:02:49 DEBUG| [    0.000000] Initializing cgroup subsys cpu
+18:02:49 DEBUG| [    0.000000] Linux version 2.6.32-5-5kc-malta (Debian 2.6.32-48) (ben@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Fri Feb 15 21:38:11 UTC 2013
+18:02:49 DEBUG| [    0.000000]
+18:02:49 DEBUG| [    0.000000] LINUX started...
+18:02:49 DEBUG| [    0.000000] bootconsole [early0] enabled
+18:02:49 DEBUG| [    0.000000] CPU revision is: 000182a0 (MIPS 20Kc)
+18:02:49 DEBUG| [    0.000000] FPU revision is: 000f8200
+18:02:49 DEBUG| [    0.000000] Checking for the multiply/shift bug... no.
+18:02:49 DEBUG| [    0.000000] Checking for the daddiu bug... no.
+18:02:49 DEBUG| [    0.000000] Determined physical RAM map:
+18:02:49 DEBUG| [    0.000000]  memory: 0000000000001000 @ 0000000000000000 (reserved)
+18:02:49 DEBUG| [    0.000000]  memory: 00000000000ef000 @ 0000000000001000 (ROM data)
+18:02:49 DEBUG| [    0.000000]  memory: 0000000000659000 @ 00000000000f0000 (reserved)
+18:02:49 DEBUG| [    0.000000]  m
+18:04:48 ERROR| 
+18:04:48 ERROR| Reproduced traceback from: /builds/stsquad/qemu/build/pyvenv/lib/python3.10/site-packages/avocado/core/test.py:770
+18:04:48 ERROR| Traceback (most recent call last):
+18:04:48 ERROR|   File "/builds/stsquad/qemu/build/tests/avocado/replay_kernel.py", line 147, in test_mips64el_malta
+18:04:48 ERROR|     self.run_rr(kernel_path, kernel_command_line, console_pattern, shift=5)
+18:04:48 ERROR|   File "/builds/stsquad/qemu/build/tests/avocado/replay_kernel.py", line 78, in run_rr
+18:04:48 ERROR|     t2 = self.run_vm(kernel_path, kernel_command_line, console_pattern,
+18:04:48 ERROR|   File "/builds/stsquad/qemu/build/tests/avocado/replay_kernel.py", line 61, in run_vm
+18:04:48 ERROR|     self.wait_for_console_pattern(console_pattern, vm)
+18:04:48 ERROR|   File "/builds/stsquad/qemu/build/tests/avocado/boot_linux_console.py", line 52, in wait_for_console_pattern
+18:04:48 ERROR|     wait_for_console_pattern(self, success_message,
+18:04:48 ERROR|   File "/builds/stsquad/qemu/build/tests/avocado/avocado_qemu/__init__.py", line 199, in wait_for_console_pattern
+18:04:48 ERROR|     _console_interaction(test, success_message, failure_message, None, vm=vm)
+18:04:48 ERROR|   File "/builds/stsquad/qemu/build/tests/avocado/avocado_qemu/__init__.py", line 148, in _console_interaction
+18:04:48 ERROR|     msg = console.readline().decode().strip()
+```
diff --git a/results/classifier/gemma3:12b/kernel/2040 b/results/classifier/gemma3:12b/kernel/2040
new file mode 100644
index 00000000..2d061cdb
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2040
@@ -0,0 +1,25 @@
+
+x86 TCG incorrectly truncates physical addresses to 32 bits when PAE is enabled
+Description of problem:
+Originally observed as 32-bit Windows failing to boot on systems with RAM above 4G when using TCG (but working fine under KVM).  Windows kernel debugger showed the kernel allocating a block of memory but somehow failing to create a page table mapping for it.
+
+Bisection in QEMU produced the first bad commit as 4a1e9d4 ("target/i386: Use atomic operations for pte updates"), which changed the PTE accessing code from using e.g. `x86_ldq_phys()` to using `probe_access_full()` and `ldq_p()`.
+
+Further deconstruction of the changes in this commit found that at some point during the boot, the value obtained from `ldq_p()` was completely different to the value obtained from `x86_ldq_phys()`.  Debugging revealed that the underlying host addresses used by each method were exactly 4G apart, with the new method (`ldq_p()`) accessing a host location 4G below the correct address.
+
+Inspection of the code revealed one place where addresses are truncated to 32 bits, which would cause this 4G offset: in `get_physical_address()` we have the code:
+
+```
+    if (!(env->hflags & HF_LMA_MASK)) {
+        /* Without long mode we can only address 32bits in real mode */
+        out->paddr = (uint32_t)out->paddr;
+    }
+```
+
+This looks wrong, since PAE allows for physical addresses above 4G to be accessed without long mode.  (This is the whole point of PAE.)
+
+A quick experiment shows that commenting out the above block of code fixes the symptom and allows Windows 10 to boot with RAM above 4G.
+
+I suspect that the test should be checking for PAE being enabled rather than long mode being enabled.  (Enabling PAE is part of setting up the CPU for long mode, so it is impossible to be in long mode without PAE already enabled.)
+Steps to reproduce:
+Run the command given above.
diff --git a/results/classifier/gemma3:12b/kernel/2064 b/results/classifier/gemma3:12b/kernel/2064
new file mode 100644
index 00000000..a277056f
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2064
@@ -0,0 +1,13 @@
+
+QEMU v8.2.0-rc4 and above will not take SMI
+Description of problem:
+Starting from v8.2.0-rc4, the x86 QEMU system will take SMI from an incorrect starting address. Without any firmware relocation, sending an SMI will move the RIP to 0x8000, instead of the traditional 0x38000. This caused the existing UEFI drivers not functional during SMI relocation step.
+
+After some investigation, the issue was caused by this commit: https://github.com/qemu/qemu/commit/b5e0d5d22fbffc3d8f7d3e86d7a2d05a1a974e27. There seems to be 2 issues with this change:
+
+1. This code section https://github.com/qemu/qemu/blob/7425b6277f12e82952cede1f531bfc689bf77fb1/target/i386/tcg/translate.c#L568C1-L572C6 was updated from calculating `cpu_eip` based on `s->pc` to `s->base.pc_next`. This will cause undetermined behavior.
+2. This code section https://github.com/qemu/qemu/blob/7425b6277f12e82952cede1f531bfc689bf77fb1/target/i386/tcg/translate.c#L2848C1-L2869C67 added the routine of updating `new_pc`, which is later used `tcg_gen_addi_tl`. This will cause the `new_pc` to be populated with undesirable value and thus cause faulting behaviors.
+Steps to reproduce:
+1. Launch once booting UEFI firmware, and the system will get stuck at the SMM base relocation logic.
+Additional information:
+I verified that after fixing the 2 issues mentioned above, the SMI can be correctly invoked at desired location.
diff --git a/results/classifier/gemma3:12b/kernel/2078 b/results/classifier/gemma3:12b/kernel/2078
new file mode 100644
index 00000000..5734ade0
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2078
@@ -0,0 +1,35 @@
+
+Qemu crashes with SIGFPE on certain trapping arithmetic operations on m68k target
+Description of problem:
+I recently ported NetBSD to the Qemu m68k "virt" platform, and this was discovered when running NetBSD's automated tests.  Certain arithmetic operation that will trap in the guest will crash Qemu.  First case encountered is below.
+Steps to reproduce:
+1. Compile and run the following program in the m68k guest:
+
+```
+virt68k:thorpej 3$ cat crash-qemu.c                                            
+#include <limits.h>
+#include <stdlib.h>
+
+int divisor = -1;
+
+int
+main(int argc, char *argv[])
+{
+
+	if (argc > 1)
+		divisor = atoi(argv[1]);
+
+	return INT_MIN / divisor;
+}
+virt68k:thorpej 4$ 
+```
+
+Another minimal case would be:
+
+```
+move.l #-2147483648,%d0
+move.l #-1,%d1
+divsl.l %d1,%d1:%d0
+```
+Additional information:
+
diff --git a/results/classifier/gemma3:12b/kernel/2078790 b/results/classifier/gemma3:12b/kernel/2078790
new file mode 100644
index 00000000..50d40e2d
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2078790
@@ -0,0 +1,12 @@
+
+jammy qemu x86 int3: 0000 [#1] SMP NOPTI 
+
+jammy:linux-lowlatency-hwe-6.8 6.8.0-44.44.1~22.04.1 qemu-x86 QEMU Standard PC (i440FX + PIIX, 1996)
+
+
+Recently (2024.08.05), I have been seeing this issue with ADT:systemd:upstream-1/2 test in which kernel panics/prints a stack. I have seen this with jammy:linux-lowlatency-hwe-6.8 and jammy:linux-ibm-6.8. Stack trace is different everytime because kernel receives an interrupt, drop what it is doing, and crash when handling the interrupt.
+
+I think this is an issue with qemu and not kernel. For jammy, we are using qemu 6.2 and there are some fixes related to x86 interrupt handling in 8.x (https://<email address hidden>/T/). I propose we create a launchpad bug and trace the issue. If I am correct, we shouldn't see this in noble. And we should occasionally see this in 5.15 jammy kernels (and more frequently with lowlantecy kernels).
+
+
+Meanwhile see comments below for some stack traces;
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/2079 b/results/classifier/gemma3:12b/kernel/2079
new file mode 100644
index 00000000..3c84fcad
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2079
@@ -0,0 +1,2 @@
+
+flaky test: tcg tests, cross-i686-tci runner, "run-memory" test
diff --git a/results/classifier/gemma3:12b/kernel/2113 b/results/classifier/gemma3:12b/kernel/2113
new file mode 100644
index 00000000..e84f18af
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2113
@@ -0,0 +1,2 @@
+
+x64-freebsd-13-build CI job fails with "/usr/local/lib/libtasn1.so: undefined reference to strverscmp@FBSD_1.7"
diff --git a/results/classifier/gemma3:12b/kernel/212 b/results/classifier/gemma3:12b/kernel/212
new file mode 100644
index 00000000..388e948d
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/212
@@ -0,0 +1,2 @@
+
+ppc64 TCG application crashes
diff --git a/results/classifier/gemma3:12b/kernel/2122 b/results/classifier/gemma3:12b/kernel/2122
new file mode 100644
index 00000000..306af058
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2122
@@ -0,0 +1,8 @@
+
+qemu-user-static segfault running ldconfig on host x86_64 with client arm64
+Description of problem:
+qemu segfault
+Steps to reproduce:
+1. download ubuntu jammy arm64 rootfs (I assume any will do)
+2. mount it (with /proc from host so apt is happy)
+3. execute an apt uninstall that triggers libc-bin processing
diff --git a/results/classifier/gemma3:12b/kernel/2133 b/results/classifier/gemma3:12b/kernel/2133
new file mode 100644
index 00000000..bc8d7096
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2133
@@ -0,0 +1,56 @@
+
+Debian sparc64 works on hardware, segfaults in qemu
+Description of problem:
+
+Steps to reproduce:
+1. Start the installer normally (boot cdrom), use guided all disk partition, change ext4 to btrfs for /
+2. Installer always segfaults at the same place while installing base system step:
+
+```
+Jan 28 09:17:48 debootstrap: Setting up mawk (1.3.4.20200120-3.1) ...
+Jan 28 09:17:49 debootstrap: update-alternatives:
+Jan 28 09:17:49 debootstrap: using /usr/bin/mawk to provide /usr/bin/awk (awk) i
+n auto mode
+Jan 28 09:17:49 debootstrap:
+Jan 28 09:17:54 debootstrap: Selecting previously unselected package debconf.
+Jan 28 09:17:54 debootstrap: (Reading database ... 1459 files and directories cu
+rrently installed.)
+Jan 28 09:17:54 debootstrap: Preparing to unpack .../debconf_1.5.82_all.deb ...
+Jan 28 09:17:54 debootstrap: Unpacking debconf (1.5.82) ...
+Jan 28 09:17:55 kernel: [ 2994.426867] dpkg-deb[12709]: segfault at ffffffffffff
+ffff ip fffff80100a1c3ec (rpc 0000000000000030) sp fffff80102402041 error 1 in l
+iblzma.so.5.4.1[fffff80100a00000+2a000]
+Jan 28 09:17:55 debootstrap: dpkg-deb: error: <decompress> subprocess was killed
+ by signal (Segmentation fault)
+Jan 28 09:17:56 debootstrap: dpkg: error processing archive /var/cache/apt/archi
+ves/debconf_1.5.82_all.deb (--install):
+Jan 28 09:17:56 debootstrap:  dpkg-deb --fsys-tarfile subprocess returned error
+exit status 2
+Jan 28 09:17:57 debootstrap: Errors were encountered while processing:
+Jan 28 09:17:57 debootstrap:  /var/cache/apt/archives/debconf_1.5.82_all.deb
+Jan 28 09:18:10 base-installer: error: exiting on error base-installer/debootstr
+
+
+cd /target/var/cache/apt/archives
+# ar x debconf_1.5.82_all.deb
+/target/var/cache/apt/archives # unxz data.tar.xz
+/target/var/cache/apt/archives # unxz control.tar.xz
+```
+another try, to ext2 fs:
+```
+Jan 28 10:31:16 debootstrap: Preparing to unpack .../dpkg_1.21.21_sparc64.deb ..
+.
+Jan 28 10:31:16 debootstrap: Unpacking dpkg (1.21.21) over (1.21.21) ...
+Jan 28 10:31:23 kernel: [ 7402.528016] dpkg-deb[20720]: segfault at 7240015 ip f
+ffff8010091def4 (rpc 000000006e17c498) sp fffff80103124041 error 1 in liblzma.so
+.5.4.1[fffff80100900000+2a000]
+Jan 28 10:31:23 debootstrap: dpkg-deb: error: <decompress> subprocess was killed
+ by signal (Segmentation fault)
+Jan 28 10:31:24 debootstrap: dpkg: error processing archive /var/cache/apt/archi
+ves/dpkg_1.21.21_sparc64.deb (--install):
+Jan 28 10:31:24 debootstrap:  cannot copy extracted data for './usr/share/doc/dp
+kg/changelog.gz' to '/usr/share/doc/dpkg/changelog.gz.dpkg-new': unexpected end
+of file or stream
+```
+Additional information:
+All times i've tried under Ubuntu qemu or latest build for Windows it segfaults unpacking package, and i believe it's a misleading error message, since very same ISO installs normally on Sun Fire T1000 machine (sun4v). I've tried also booting FreeBSD-12.4-RELEASE-sparc64-disc1.iso which dies shortly after booting the kernel, but i am more interested in Debian, since it was verified to work on a real hardware. BTW i was able to unpack specified file with "ar x" within installer.
diff --git a/results/classifier/gemma3:12b/kernel/2146 b/results/classifier/gemma3:12b/kernel/2146
new file mode 100644
index 00000000..9b1d15b1
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2146
@@ -0,0 +1,115 @@
+
+qemu-system-aarch64 Segfaults
+Description of problem:
+Never finishes the script below always segfaults after a few hours
+in seemingly random functions.
+Steps to reproduce:
+This is what i did with qemu version 8.2.1
+inside test directory:
+1. wget https://download.qemu.org/qemu-8.2.1.tar.xz
+2. tar xvJf qemu-8.2.1.tar.xz
+3. cd qemu-8.2.1
+4. ./configure --target-list="aarch64-linux-user, aarch64-softmmu" --enable-slirp (crashes with and without --enable-debug)
+5. make -j$(nproc)
+6. ln -sf "$PWD/build/qemu-system-aarch64" "../qemu-system-aarch64"
+7. cd ..
+
+Now the VM
+1. wget -O installer-linux https://deb.debian.org/debian/dists/bookworm/main/installer-arm64/current/images/netboot/debian-installer/arm64/linux
+2. wget -O installer-initrd.gz https://deb.debian.org/debian/dists/bookworm/main/installer-arm64/current/images/netboot/debian-installer/arm64/initrd.gz
+3. qemu-img create -f qcow2 hda.qcow2 15G
+4. ./qemu-system-aarch64 -M virt -m 6G -cpu cortex-a72 \
+      -kernel installer-linux \
+      -initrd installer-initrd.gz \
+      -drive if=none,file=hda.qcow2,format=qcow2,id=hd \
+      -device virtio-blk-pci,drive=hd \
+      -netdev user,id=mynet \
+      -device virtio-net-pci,netdev=mynet \
+      -nographic -no-reboot \
+      -accel tcg,thread=multi \
+      -smp 8
+5. Install minimal debian inside the VM
+6. sudo virt-copy-out -a hda.qcow2 /boot/vmlinuz-6.1.0-17-arm64 /boot/initrd.img-6.1.0-17-arm64 .
+7. ./qemu-system-aarch64 -M virt -m 6G -cpu cortex-a72 \
+      -kernel vmlinuz-6.1.0-17-arm64 \
+      -initrd initrd.img-6.1.0-17-arm64 \
+      -append 'root=/dev/vda2' \
+      -drive if=none,file=hda.qcow2,format=qcow2,id=hd \
+      -device virtio-blk-pci,drive=hd \
+      -netdev user,id=mynet,hostfwd=tcp::10022-:22 \
+      -device virtio-net-pci,netdev=mynet \
+      -nographic \
+      -accel tcg,thread=multi \
+      -smp 8
+8. Now run this script inside some directory inside the VM(you might need to install gcc first)
+
+#!/bin/bash
+
+wget --no-clobber https://sourceware.org/pub/binutils/releases/binutils-2.41.tar.xz   
+wget --no-clobber https://ftp.gnu.org/gnu/mpfr/mpfr-4.2.0.tar.xz   
+wget --no-clobber https://ftp.gnu.org/gnu/gmp/gmp-6.3.0.tar.xz    
+wget --no-clobber https://ftp.gnu.org/gnu/mpc/mpc-1.3.1.tar.gz    
+wget --no-clobber https://ftp.gnu.org/gnu/gcc/gcc-13.2.0/gcc-13.2.0.tar.xz   
+
+BUG_TARGET="$(uname -m)-bug-linux-gnu"
+
+tar -xf binutils-2.41.tar.xz   
+cd binutils-2.41   
+mkdir -vp build   
+cd build   
+../configure --prefix=$PWD        \
+             --with-sysroot=$PWD  \
+             --target=$BUG_TARGET \
+             --disable-nls        \
+             --enable-gprofng=no  \
+             --disable-werror     \
+             --disable-gdb
+make --jobs $(nproc)   
+cd ../..   
+rm -rf binutils   
+
+tar -xf gcc-13.2.0.tar.xz   
+cd gcc-13.2.0   
+tar -xf ../mpfr-4.2.0.tar.xz   
+tar -xf ../gmp-6.3.0.tar.xz   
+tar -xf ../mpc-1.3.1.tar.gz   
+mv mpfr-4.2.0 mpfr   
+mv gmp-6.3.0 gmp   
+mv mpc-1.3.1 mpc   
+mkdir -vp build   
+cd build   
+../configure --prefix=$PWD             \
+             --with-sysroot=$PWD       \
+             --target=$BUG_TARGET      \
+             --with-glibc-version=2.38 \
+             --with-newlib             \
+             --without-headers         \
+             --enable-default-pie      \
+             --enable-default-ssp      \
+             --disable-nls             \
+             --disable-shared          \
+             --disable-multilib        \
+             --disable-threads         \
+             --disable-libatomic       \
+             --disable-libgomp         \
+             --disable-libquadmath     \
+             --disable-libssp          \
+             --disable-libvtv          \
+             --disable-libstdcxx       \
+             --enable-languages=c,c++
+make --jobs $(nproc)   
+cd ../..   
+rm -rf gcc
+Additional information:
+I tried all the versions listed above, 6.2 usually segfaults in binutils while the other two run further.
+
+Example:
+```
+Program terminated with signal SIGSEGV, Segmentation fault.
+#0  0x000055555615dd37 in tlb_index (cpu=<Cannot access memory at address 0x7fffefffe1c8>,
+    mmu_idx=<Cannot access memory at address 0x7fffefffe1c0>,
+    addr=<Cannot access memory at address 0x7fffefffe1b8>)
+    at qemu-8.2.1/include/exec/cpu_ldst.h:367
+367	    uintptr_t size_mask = cpu->neg.tlb.f[mmu_idx].mask >> CPU_TLB_ENTRY_BITS;
+[Current thread is 1 (LWP 857562)]
+```
diff --git a/results/classifier/gemma3:12b/kernel/2148 b/results/classifier/gemma3:12b/kernel/2148
new file mode 100644
index 00000000..35e00829
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2148
@@ -0,0 +1,10 @@
+
+vdso.so is required to build vdso.so since 8.2.0
+Description of problem:
+Removing binaries from the "source" distribution makes it unable to compile. It used to work in 8.1.4.
+Steps to reproduce:
+1. remove **/vdso.so
+2. configure, build
+3. `../linux-user/i386/meson.build:7:20: ERROR: File vdso.so does not exist.`
+Additional information:
+Build log in my Gentoo harness: [build.log](/uploads/da1933173b39dd6e5f9f90de09adc3a1/build.log)
diff --git a/results/classifier/gemma3:12b/kernel/215 b/results/classifier/gemma3:12b/kernel/215
new file mode 100644
index 00000000..a0437373
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/215
@@ -0,0 +1,2 @@
+
+x86 Floating point exceptions - incorrect support?
diff --git a/results/classifier/gemma3:12b/kernel/2150 b/results/classifier/gemma3:12b/kernel/2150
new file mode 100644
index 00000000..ac59b307
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2150
@@ -0,0 +1,14 @@
+
+ERROR:tcg/optimize.c:580:do_constant_folding_2: code should not be reached
+Description of problem:
+After booting Windows 10 or 11 (ARM) QEMU suddenly quits with:
+
+ERROR:tcg/optimize.c:580:do_constant_folding_2: code should not be reached
+
+It seems like it is missing an OPCODE in that function?
+Steps to reproduce:
+1. Boot Windows
+2. QEMU quits
+3.
+Additional information:
+
diff --git a/results/classifier/gemma3:12b/kernel/2155 b/results/classifier/gemma3:12b/kernel/2155
new file mode 100644
index 00000000..a091752a
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2155
@@ -0,0 +1,24 @@
+
+LoadVM assert on ARM_FEATURE_M for Cortex M3
+Description of problem:
+This appears to be a similar issue to https://gitlab.com/qemu-project/qemu/-/issues/1775 and https://gitlab.com/qemu-project/qemu/-/issues/1658
+
+When running `loadvm`  qemu aborts with this error:
+
+"qemu/target/arm/helper.c:12383: arm_security_space_below_el3: Assertion `!arm_feature(env, ARM_FEATURE_M)' failed."
+
+I've traced the error to `pmu_counter_enabled` in `qemu\target\arm\helper.c:1172`   
+ [uint64_t mdcr_el2 = arm_mdcr_el2_eff(env)](https://gitlab.com/qemu-project/qemu/-/blob/v8.2.0/target/arm/helper.c?ref_type=tags#L1172)  (link is to 8.2.0 release tag)
+
+
+The issue is caused by attempting to get the MDCR_EL2 register  prior to checking if the CPU has ARM_FEATURE_PMU support. 
+
+A simple fix seems to be to check for `ARM_PMU_ENABLED` and returning early if it is not enabled.
+Steps to reproduce:
+1. Start emulation and connect monitor
+2. savevm <snapshot-name>
+3. Loadvm <snapshot-name>
+Additional information:
+See screenshot for stack trace
+
+![armCortexM3LoadVMStackTrace](/uploads/fcfd927f4d373922715c8787dbb9cc26/armCortexM3LoadVMStackTrace.png)
diff --git a/results/classifier/gemma3:12b/kernel/2156 b/results/classifier/gemma3:12b/kernel/2156
new file mode 100644
index 00000000..c2979d64
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2156
@@ -0,0 +1,16 @@
+
+Userland QEMU segfaults when emulating itself thrice
+Description of problem:
+See title. 
+```
+$ qemu-x86_64-static qemu-x86_64-static qemu-x86_64-static /bin/true
+qemu-x86_64-static: QEMU internal SIGSEGV {code=ACCERR, addr=0x7f9ae80001a0}
+[1]    15705 segmentation fault (core dumped)  qemu-x86_64-static qemu-x86_64-static qemu-x86_64-static /bin/true
+```
+Steps to reproduce:
+1. Execute command above
+Additional information:
+Coredump (~322MB uncompressed)
+[qemu_qemu-x86_64-static_20240208-123447_15705.core.xz](/uploads/a6723aaf956dfd1efc434303e62c25e2/qemu_qemu-x86_64-static_20240208-123447_15705.core.xz)
+
+SHA1: 31c2b06a61f63dca5199b64b767aa2fdeefbeec6
diff --git a/results/classifier/gemma3:12b/kernel/216 b/results/classifier/gemma3:12b/kernel/216
new file mode 100644
index 00000000..86f6a31d
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/216
@@ -0,0 +1,2 @@
+
+qemu-system-sparc64 with tribblix-sparc-0m16.iso ends with "panic - kernel: no nucleus hblk8 to allocate"
diff --git a/results/classifier/gemma3:12b/kernel/2165 b/results/classifier/gemma3:12b/kernel/2165
new file mode 100644
index 00000000..c0bf978b
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2165
@@ -0,0 +1,69 @@
+
+m68k: 68000 strict alignment requirements not emulated correctly
+Description of problem:
+Unaligned accesses should cause an address error on the 68000 but apparently currently don't.
+Steps to reproduce:
+1. Create a 68000 based QEMU machine to port u-boot/linux
+2. Get u-boot/linux working perfectly on your QEMU machine
+3. Copy kernel over to your real 68000 hardware
+4. Notice that the kernel doesn't work
+5. Spend a day adding inline assembly all over the kernel to work out where the real hardware is locking up
+6. Find that the issue is probably memmove() being called with an unaligned src pointer:
+
+C level..
+
+```
+Breakpoint 1, memmove (n=215, src=0x2059df <printk_shared_pbufs+215>, dest=0x2059ee <printk_shared_pbufs+230>) at ../arch/m68k/lib/memmove.c:152
+152                             *--sdest = *--ssrc;
+(gdb) bt
+#0  memmove (n=215, src=0x2059df <printk_shared_pbufs+215>, dest=0x2059ee <printk_shared_pbufs+230>) at ../arch/m68k/lib/memmove.c:152
+#1  memmove (dest=<optimized out>, src=<optimized out>, n=<optimized out>) at ../arch/m68k/lib/memmove.c:10
+#2  0x000265b6 in record_print_text (r=<optimized out>, syslog=<optimized out>, time=<optimized out>) at ../kernel/printk/printk.c:1472
+#3  0x00027be6 in printk_get_next_message (pmsg=<optimized out>, seq=<optimized out>, is_extended=<optimized out>, may_suppress=<optimized out>) at ../kernel/printk/printk.c:2952
+#4  0x00027e5a in console_emit_next_record (cookie=0, handover=0x1d9e37, con=0x1edf14 <early_con>) at ../kernel/printk/printk.c:3019
+#5  console_flush_all (do_cond_resched=false, next_seq=0x1d9e38, handover=0x1d9e37) at ../kernel/printk/printk.c:3118
+#6  0x00027fc8 in console_unlock () at ../kernel/printk/printk.c:3187
+#7  0x00028a04 in vprintk_emit (facility=0, level=<optimized out>, dev_info=0x0, fmt=0x1bd051 "\0016printk: %s%sconsole [%s%d] enabled\n", args=0x1d9e98) at ../kernel/printk/printk.c:2359
+#8  0x00028a26 in vprintk_default (fmt=0x1bd051 "\0016printk: %s%sconsole [%s%d] enabled\n", args=0x1d9e98) at ../kernel/printk/printk.c:2374
+#9  0x00028c22 in vprintk (fmt=0x1bd051 "\0016printk: %s%sconsole [%s%d] enabled\n", args=0x1d9e98) at ../kernel/printk/printk_safe.c:45
+#10 0x0019d016 in _printk (fmt=0x1bd051 "\0016printk: %s%sconsole [%s%d] enabled\n") at ../kernel/printk/printk.c:2384
+#11 0x0002857e in register_console (newcon=<optimized out>) at ../kernel/printk/printk.c:3693
+#12 0x001fbf1e in register_earlycon (match=<optimized out>, buf=0x0) at ../drivers/tty/serial/earlycon.c:161
+#13 setup_earlycon (buf=<optimized out>) at ../drivers/tty/serial/earlycon.c:212
+#14 0x001fbf72 in param_setup_earlycon (buf=0x2009e9 <tmp_cmdline+9> "mc68ez328,0xfffff900") at ../drivers/tty/serial/earlycon.c:244
+#15 0x001f1102 in do_early_param (param=0x2009e0 <tmp_cmdline> "earlycon", val=0x2009e9 <tmp_cmdline+9> "mc68ez328,0xfffff900", unused=0x1b96c6 "early options", arg=0x0)
+    at ../init/main.c:744
+#16 0x00017eac in parse_one (handle_unknown=<optimized out>, arg=<optimized out>, max_level=<optimized out>, min_level=<optimized out>, num_params=<optimized out>, params=<optimized out>, 
+    doing=0x1b96c6 "early options", val=0x2009e9 <tmp_cmdline+9> "mc68ez328,0xfffff900", param=0x2009e0 <tmp_cmdline> "earlycon") at ../kernel/params.c:154
+#17 parse_args (doing=<optimized out>, args=0x2009fe <tmp_cmdline+30> "console=ttyDB0 root=/dev/mmcblk0p2 rootfstype=squashfs rootwait", params=<optimized out>, num=<optimized out>, 
+    min_level=<optimized out>, max_level=<optimized out>, arg=<optimized out>, unknown=<optimized out>) at ../kernel/params.c:189
+#18 0x001f13ea in parse_early_options (cmdline=0x2009e0 <tmp_cmdline> "earlycon") at ../init/main.c:754
+#19 0x001f1420 in parse_early_param () at ../init/main.c:769
+#20 0x001f1570 in start_kernel () at ../init/main.c:908
+#21 0x000004b8 in _clear_bss () at ../arch/m68k/dt/head.S:95
+#22 0x00000000 in ?? ()
+```
+
+Asm level:
+
+```
+152                             *--sdest = *--ssrc;
+   0x0019bed8 <+324>:   movel %a1,%d2
+   0x0019beda <+326>:   subql #2,%d2
+   0x0019bedc <+328>:   movel %a2,%d1
+   0x0019bede <+330>:   subql #2,%d1
+=> 0x0019bee0 <+332>:   movew %a1@(-2),%a2@(-2)
+```
+
+This is a word store so needs to be aligned but a1 isn't aligned so we should get an address error:
+
+```
+(gdb) print/x $a1
+$3 = 0x2059df
+(gdb) print/x $a2
+$4 = 0x2059ee
+```
+
+
+7. Check QEMU source code to work out why it doesn't crash the cpu at the same place.
+8. Notice it doesn't seem to check the alignment.
diff --git a/results/classifier/gemma3:12b/kernel/2168 b/results/classifier/gemma3:12b/kernel/2168
new file mode 100644
index 00000000..0a27e95d
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2168
@@ -0,0 +1,33 @@
+
+qemu-x86_64: segfault when running grep on arm64 host
+Description of problem:
+An internal segmentation fault occurs when attempting to run `grep` in a Gentoo stage3 chroot
+Steps to reproduce:
+1. Unpack an x86_64 chroot environment (easiest way is using one of Gentoo's stage3s from https://get.gentoo.org)
+2. Run `qemu-x86_64 -L /path/to/x86_64/chroot /path/to/x86_64/chroot/bin/grep`
+Additional information:
+It seems this only occurs in 8.x.x, 7.x.x does not have this segfault.
+
+Output:
+```
+# qemu-x86_64 -L /bugs/grep-sandbox /bugs/grep-sandbox/bin/grep
+qemu-x86_64: QEMU internal SIGSEGV {code=MAPERR, addr=0x20}
+Segmentation fault
+```
+
+GDB bt:
+```
+(gdb) bt
+#0  open_self_maps_2 (opaque=0xffffffffd0b0, guest_start=18446744073699065856, guest_end=<optimized out>, flags=12) at ../linux-user/syscall.c:8089
+#1  0x000000000048539c in walk_memory_regions (priv=priv@entry=0xffffffffd0b0, fn=fn@entry=0x4a13e4 <open_self_maps_2>) at ../accel/tcg/user-exec.c:176
+#2  0x00000000004a20bc in open_self_maps_1 (smaps=false, fd=3, env=<optimized out>) at ../linux-user/syscall.c:8112
+#3  open_self_maps (cpu_env=<optimized out>, fd=3) at ../linux-user/syscall.c:8122
+#4  0x00000000004aaa00 in do_guest_openat (cpu_env=cpu_env@entry=0x862050, dirfd=dirfd@entry=-100, fname=fname@entry=0x5555555776f1 "/proc/self/maps", flags=0, mode=mode@entry=0, safe=safe@entry=true)
+    at ../linux-user/syscall.c:8381
+#5  0x00000000004b0cc4 in do_syscall1 (cpu_env=cpu_env@entry=0x862050, num=num@entry=257, arg1=arg1@entry=4294967196, arg2=arg2@entry=93824992376561, arg3=arg3@entry=0, arg4=arg4@entry=0,
+    arg5=arg5@entry=93824992373306, arg6=arg6@entry=0, arg8=0, arg7=0) at ../linux-user/syscall.c:9075
+#6  0x00000000004b2770 in do_syscall (cpu_env=cpu_env@entry=0x862050, num=257, arg1=4294967196, arg2=93824992376561, arg3=0, arg4=0, arg5=93824992373306, arg6=0, arg7=arg7@entry=0, arg8=arg8@entry=0)
+    at ../linux-user/syscall.c:13658
+#7  0x0000000000404fdc in cpu_loop (env=env@entry=0x862050) at ../linux-user/x86_64/../i386/cpu_loop.c:242
+#8  0x0000000000400d7c in main (argc=4, argv=0xffffffffed48, envp=<optimized out>) at ../linux-user/main.c:1014
+```
diff --git a/results/classifier/gemma3:12b/kernel/2170 b/results/classifier/gemma3:12b/kernel/2170
new file mode 100644
index 00000000..0bd02c8a
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2170
@@ -0,0 +1,45 @@
+
+qemu-x86_64 crashes when the application calls pthread_getattr_np()
+Description of problem:
+QEMU user emulation crashes with this program:
+```
+#define _GNU_SOURCE
+#include <stdio.h>
+#include <pthread.h>
+
+int main()
+{
+        pthread_attr_t attr;
+        int error = pthread_getattr_np(pthread_self(), &attr);
+
+        printf("%d\n", error);
+        return 0;
+}
+```
+Steps to reproduce:
+1. Compile the program above
+2. Run QEMU
+Additional information:
+QEMU crashes with:
+```
+qemu-x86_64: QEMU internal SIGSEGV {code=MAPERR, addr=0x20}
+Segmentation fault (core dumped)
+
+```
+
+In gdb I get this backtrace:
+```
+#0  0x0000555555627d6d in open_self_maps_2 (opaque=0x7fffffffc020, guest_start=18446744073699065856, guest_end=<optimized out>, flags=12) at ../linux-user/syscall.c:8089
+#1  0x000055555560ce67 in walk_memory_regions (priv=priv@entry=0x7fffffffc020, fn=fn@entry=0x555555627d30 <open_self_maps_2>) at ../accel/tcg/user-exec.c:176
+#2  0x0000555555628b3a in open_self_maps_1 (smaps=<optimized out>, fd=<optimized out>, env=<optimized out>) at ../linux-user/syscall.c:8112
+#3  open_self_maps (cpu_env=<optimized out>, fd=3) at ../linux-user/syscall.c:8122
+#4  0x0000555555631e24 in do_guest_openat (cpu_env=cpu_env@entry=0x55555583ae20, dirfd=dirfd@entry=-100, fname=fname@entry=0x2aaaab496eb4 "/proc/self/maps", flags=524288, mode=mode@entry=0, safe=safe@entry=true) at ../linux-user/syscall.c:8381
+#5  0x0000555555638f71 in do_syscall1 (cpu_env=cpu_env@entry=0x55555583ae20, num=num@entry=257, arg1=arg1@entry=4294967196, arg2=arg2@entry=46912506523316, arg3=arg3@entry=524288, arg4=arg4@entry=0, arg5=<optimized out>, arg6=<optimized out>, arg8=0, arg7=0) at ../linux-user/syscall.c:9075
+#6  0x000055555563b659 in do_syscall (cpu_env=cpu_env@entry=0x55555583ae20, num=257, arg1=4294967196, arg2=46912506523316, arg3=524288, arg4=0, arg5=8, arg6=1, arg7=0, arg8=0) at ../linux-user/syscall.c:13658
+#7  0x000055555558db19 in cpu_loop (env=env@entry=0x55555583ae20) at ../linux-user/x86_64/../i386/cpu_loop.c:242
+#8  0x00005555555898d8 in main (argc=<optimized out>, argv=0x7fffffffdd38, envp=<optimized out>) at ../linux-user/main.c:1012
+
+```
+
+This bug was introduced in the rewrite of `open_self_maps` in 7b7a3366e142d3baeb3fd1d3660a50e7956c19eb.
+The current master (5767815218efd3cbfd409505ed824d5f356044ae) is still affected.
diff --git a/results/classifier/gemma3:12b/kernel/2198 b/results/classifier/gemma3:12b/kernel/2198
new file mode 100644
index 00000000..74d82555
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2198
@@ -0,0 +1,26 @@
+
+Unable to run OS/2 Warp4.52
+Description of problem:
+Operating system crashes upon boot.
+Steps to reproduce:
+1. Install OS/2 Warp4
+2. Apply Fixpack15
+3. Try to boot the system
+Additional information:
+This is a very old bug that seems to render a whole family of Operating Systems (OS/2 Warp4 and eComStation) unusable under Qemu.
+Warp4 works, in the sense that it does install and run, but just until it is updated to 4.52 (which is necessary to get a useable guest)
+
+I found traces of its existence as far as:
+https://bugs.launchpad.net/qemu/+bug/1743441
+https://lists.gnu.org/archive/html/qemu-devel/2019-02/msg02337.html
+
+And i found the issue brieffly commented at https://www.os2world.com/forum/index.php?topic=2346.0
+I quote: 
+ 
+'Regarding QEMU/KVM, OS/2 runs in QEMU mostly fine. Except the trap in os2lvm.dmd and non-working netbeui.os2 and
+tcpbeui.os2. The problem with os2lvm.dmd is because QEMU closely follows the intel spec, which is incorrect. The spec says
+that 16-bit SGDT instruction behaves the same like in i286 processor. But it's not true, it behaves like i386 instruction. So, QEMU
+emulates SGDT 16-bit instruction incorrectly. OS2LVM.DMD uses 16-bit SGDT instruction and it hits the problem.'
+
+After a brief discussion on the Warp4 group at groups.io where I was told that this is indeed a Qemu bug, I thought someone has 
+to report on that.
diff --git a/results/classifier/gemma3:12b/kernel/2206 b/results/classifier/gemma3:12b/kernel/2206
new file mode 100644
index 00000000..5371d217
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2206
@@ -0,0 +1,11 @@
+
+PAGE_FAULT_IN_NONPAGED_AREA in Windows 7 x64.
+Description of problem:
+When trying to install Windows 7, it always crashes with PAGE_FAULT_IN_NONPAGED_AREA. This also impacts Windows 8.1, but crashes when it tries to start up the installation disc.
+Steps to reproduce:
+1. Create A VM with the Windows 7 installation disc inside the cdrom.
+2. Go through the installation
+3. At some point, it will pull a blue screen with a PAGE_FAULT_IN_NONPAGED_AREA. (around expanding windows files or completing installation)
+Additional information:
+It looks like this bsod is relating to some non-canonical (illegal) virtual address being referenced. (It's just my guess based on the stop code)
+![image](/uploads/910a863461a99713ff8566e5c2212ce2/image.png)
diff --git a/results/classifier/gemma3:12b/kernel/2219 b/results/classifier/gemma3:12b/kernel/2219
new file mode 100644
index 00000000..7264b6ae
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2219
@@ -0,0 +1,2 @@
+
+Core dump instead of error when starting on nohz_full system with enable-membarrier
diff --git a/results/classifier/gemma3:12b/kernel/2259 b/results/classifier/gemma3:12b/kernel/2259
new file mode 100644
index 00000000..82d315c4
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2259
@@ -0,0 +1,15 @@
+
+The cause code of a trap changes when qemu is nested in another qemu
+Description of problem:
+I am studying the feasibility of doing some practical work on RISCV plates. Since I don't have these boards yet, I'm emulating it with qemu. The practice in turn consists of launching with qemu a very small operating system with two tasks that make a series of system calls.
+
+When I run this practice on my host it works correctly, but when I run it on an Ubuntu emulated in riscv with qemu, the cause code for the trap changes (the first bit of the code).
+
+The demo can be found in this repository: https://github.com/Sft570/qemu-bug-report
+Steps to reproduce:
+1. Clone the repository on the host and run the demo with "make qemu"
+2. Emulate with qemu ubuntu in riscv, clone the repository and run the demo with "make qemu".
+
+The error displayed shows the change of the cause code bit. You can analyze its behavior in the trap.c file in the src folder.
+Additional information:
+
diff --git a/results/classifier/gemma3:12b/kernel/2264 b/results/classifier/gemma3:12b/kernel/2264
new file mode 100644
index 00000000..1fdb151e
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2264
@@ -0,0 +1,58 @@
+
+tests fail in staging-7.2 after "fix direction of "32-bit MMU" patch
+Description of problem:
+Running the tests with current staging-7.2 sources after compiling, it results in failing some tests after introduction of the following patches:
+
+- [target/i386: introduce function to query MMU indices](https://gitlab.com/qemu-project/qemu/-/commit/6332f3c12f7fc6c01fae1eaa59d661fef280f499)
+
+- [target/i386: use separate MMU indexes for 32-bit accesses](https://gitlab.com/qemu-project/qemu/-/commit/6b9875b03c81351c5f0268f571e011cf5f2fd9d2)
+
+- [target/i386: fix direction of "32-bit MMU" test](https://gitlab.com/qemu-project/qemu/-/commit/64e5fffe523daee23b06f3fd0f31721b137901b5)
+
+- [target/i386: Revert monitor_puts() in do_inject_x86_mce()](https://gitlab.com/qemu-project/qemu/-/commit/1d024cdc49a9ebc4d51142d2c33668bba1d31c89)
+
+in particular is the fix:
+
+- [target/i386: fix direction of "32-bit MMU" test](https://gitlab.com/qemu-project/qemu/-/commit/64e5fffe523daee23b06f3fd0f31721b137901b5)
+
+that causes the tests failing (removing such fix, tests passes). The failing tests are:
+
+```
+Summary of Failures:
+
+ 92/689 qemu:qtest+qtest-i386 / qtest-i386/boot-serial-test                       ERROR           0.10s   killed by signal 6 SIGABRT
+127/689 qemu:qtest+qtest-x86_64 / qtest-x86_64/boot-serial-test                   ERROR           0.12s   killed by signal 6 SIGABRT
+ 48/689 qemu:qtest+qtest-i386 / qtest-i386/bios-tables-test                       ERROR          40.95s   killed by signal 6 SIGABRT
+ 71/689 qemu:qtest+qtest-x86_64 / qtest-x86_64/bios-tables-test                   ERROR          40.45s   killed by signal 6 SIGABRT
+```
+
+In particular we have:
+
+```
+ 92/689 qemu:qtest+qtest-i386 / qtest-i386/boot-serial-test                       ERROR           0.10s   killed by signal 6 SIGABRT
+――――――――――――――――――――――――――――――――――――― ✀  ―――――――――――――――――――――――――――――――――――――
+stderr:
+Broken pipe
+../tests/qtest/libqtest.c:188: kill_qemu() detected QEMU death from signal 11 (Segmentation fault) (core dumped)
+
+(test program exited with status code -6)
+――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
+```
+
+and
+
+
+```
+127/689 qemu:qtest+qtest-x86_64 / qtest-x86_64/boot-serial-test                   ERROR           0.12s   killed by signal 6 SIGABRT
+――――――――――――――――――――――――――――――――――――― ✀  ―――――――――――――――――――――――――――――――――――――
+stderr:
+Broken pipe
+../tests/qtest/libqtest.c:188: kill_qemu() detected QEMU death from signal 11 (Segmentation fault) (core dumped)
+
+(test program exited with status code -6)
+
+TAP parsing error: Too few tests run (expected 2, got 0)
+――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
+```
+
+and so on.
diff --git a/results/classifier/gemma3:12b/kernel/2276 b/results/classifier/gemma3:12b/kernel/2276
new file mode 100644
index 00000000..c80e7128
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2276
@@ -0,0 +1,43 @@
+
+qemu crash for  suspend and resume vm while backup disk of vm
+Description of problem:
+![image](/uploads/40e41df2dab7e0d3dacb6c07c1bf42b1/image.png)
+Steps to reproduce:
+1. virsh create vm2.xml
+2. virsh backup-begin domid
+3. virsh suspend domid
+4. sleep 1 && virsh resume domid
+
+qemu crash
+Additional information:
+static int blk_do_set_aio_context(BlockBackend *blk, AioContext *new_context,
+                                  bool update_root_node, Error **errp)
+{
+    BlockDriverState *bs = blk_bs(blk);
+    ThrottleGroupMember *tgm = &blk->public.throttle_group_member;
+    int ret;
+
+    if (bs) {
+        bdrv_ref(bs);
+
+        if (update_root_node) {
+            ret = bdrv_child_try_set_aio_context(bs, new_context, blk->root,
+                                                 errp);
+            if (ret < 0) {
+                bdrv_unref(bs);
+                return ret;
+            }
+        }
+        if (tgm->throttle_state) {
+         _   ****bdrv_drained_begin(bs);----- bs->aio_context->lock lock count is 0,so unlock failed**_
+            throttle_group_detach_aio_context(tgm);
+            throttle_group_attach_aio_context(tgm, new_context);
+            bdrv_drained_end(bs);
+        }
+
+        bdrv_unref(bs);
+    }
+
+    blk->ctx = new_context;
+    return 0;
+}
diff --git a/results/classifier/gemma3:12b/kernel/2281 b/results/classifier/gemma3:12b/kernel/2281
new file mode 100644
index 00000000..493189a5
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2281
@@ -0,0 +1,8 @@
+
+[bugfix incl.] Solaris Debuggers Panic OS with "Nonparity Synchronous Error"
+Description of problem:
+General use of a debugger (mdb, adb, gdb), such as single-stepping, causing a breakpoint to trigger, and/or simply running a program will cause a kernel panic of "Nonparity Synchronous Error" on many versions of Solaris / SunOS.
+
+This a well reported issue.
+
+#
diff --git a/results/classifier/gemma3:12b/kernel/2284 b/results/classifier/gemma3:12b/kernel/2284
new file mode 100644
index 00000000..7986ac71
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2284
@@ -0,0 +1,2 @@
+
+sunxi avocado tests: kernel no longer available on armbian
diff --git a/results/classifier/gemma3:12b/kernel/2286 b/results/classifier/gemma3:12b/kernel/2286
new file mode 100644
index 00000000..9b0bef27
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2286
@@ -0,0 +1,2 @@
+
+QEMU RISC-V TCG: amo insn fault does not throw AMO fault
diff --git a/results/classifier/gemma3:12b/kernel/2300 b/results/classifier/gemma3:12b/kernel/2300
new file mode 100644
index 00000000..98fe30ad
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2300
@@ -0,0 +1,2 @@
+
+Unintialized variable in double_cpdo.c
diff --git a/results/classifier/gemma3:12b/kernel/2304 b/results/classifier/gemma3:12b/kernel/2304
new file mode 100644
index 00000000..2fd96a21
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2304
@@ -0,0 +1,39 @@
+
+Disabling SVE via `-cpu max,sve=off` leaves SVE2 advertised by `getauxval`
+Description of problem:
+The documentation on https://qemu-project.gitlab.io/qemu/system/arm/cpu-features.html suggests that it should be possible to disable SVE support by passing `-cpu max,sve=off` on the command line, however this appears to only disable the SVE support advertised in the return value from `getauxval(AT_HWCAP)`. In particular it leaves SVE2 reported as enabled. This leaves the feature set advertised by `getauxval` in an inconsistent state since SVE is mandatory if SVE2 is available.
+
+This may also affect other feature dependencies for example FEAT_SVE_BITPerm also requiring SVE2 to be available, I've not checked exhaustively.
+
+For example, given the following code:
+
+    #include <sys/auxv.h>
+    #include <stdio.h>
+
+    int main() {
+      unsigned long hwcap = getauxval(AT_HWCAP);
+      unsigned long hwcap2 = getauxval(AT_HWCAP2);
+
+      if (hwcap & HWCAP_SVE) {
+        printf("have sve!\n");
+      } else {
+        printf("don't have sve!\n");
+      }
+      if (hwcap2 & HWCAP2_SVE2) {
+        printf("have sve2!\n");
+      } else {
+        printf("don't have sve2!\n");
+      }
+    }
+
+We can observe the following:
+
+    $ aarch64-linux-gnu-gcc test.c -static
+    $ ../qemu-aarch64 -cpu max ./a.out
+    have sve!
+    have sve2!
+    $ ../qemu-aarch64 -cpu max,sve=off ./a.out
+    don't have sve!
+    have sve2!
+
+I don't believe that there is a `-cpu ...,sve2=off` option, so I would expect that disabling SVE also prevents SVE2 from being advertised as available.
diff --git a/results/classifier/gemma3:12b/kernel/2316 b/results/classifier/gemma3:12b/kernel/2316
new file mode 100644
index 00000000..006d1b1d
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2316
@@ -0,0 +1,37 @@
+
+aarch64 virt cortex-a53 libc printf (with argument) hello world strange behavior
+Description of problem:
+My hello world get lost after
+
+`0x0000000040000370 <+48>:    str     q0, [sp, #80]`
+
+in 
+
+```
+   0x1f8:       udf     #0
+   0x1fc:       udf     #0
+=> 0x200:       udf     #0
+   0x204:       udf     #0
+   0x208:       udf     #0
+   0x20c:       udf     #0
+   0x210:       udf     #0
+   0x214:       udf     #0
+```
+
+By bisecting, I got the last commit OK : v8.2.0-2033-g49fa457ca5
+
+```
+$ qemu-system-aarch64 -M virt,secure=on,gic-version=3 -cpu cortex-a53 -kernel aarch64-none-elf-a.elf -serial stdio -display none
+printf with an integer : 42
+```
+
+But after v8.2.0-2034-g59754f85ed https://gitlab.com/qemu-project/qemu/-/commit/59754f85ed35cbd5f4bf2663ca2136c78d5b2413 (for example with latest v9.0.0-265-gfd87be1dad), it doesn't work anymore.
+Steps to reproduce:
+1. Build qemu-system-aarch64 with ``./configure --prefix=$PREFIX --target-list=aarch64-softmmu --disable-user --disable-linux-user --disable-bsd-user --enable-kvm --enable-tcg --disable-gnutls --disable-nettle --disable-gtk --disable-iconv --disable-curses --disable-curl --disable-vnc --disable-vnc-jpeg --disable-attr --disable-libusb --disable-opengl --disable-tpm --disable-bzip2 && make -j$(nproc) && make install``
+
+2. Run my hello world : ``qemu-system-aarch64 -M virt,secure=on,gic-version=3 -cpu cortex-a53 -kernel aarch64-none-elf-a.elf -serial stdio -display none``
+Additional information:
+I provide here the hello world (elf + map). Of course the problem might be that it (qemu and/or hello world) was not built correctly and that everything was working by chance before v8.2.0-2033-g49fa457ca5
+[aarch64-none-elf-a.elf](/uploads/daf7f37aec260c56d4be5fd90554dce3/aarch64-none-elf-a.elf)
+[aarch64-none-elf-a.map](/uploads/5564cee13a214e7eb8d6d4bf79f09682/aarch64-none-elf-a.map)
+Depending on the investigation, I can provide what's needed to rebuild it.
diff --git a/results/classifier/gemma3:12b/kernel/2319 b/results/classifier/gemma3:12b/kernel/2319
new file mode 100644
index 00000000..a2700a1c
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2319
@@ -0,0 +1,18 @@
+
+SPARC32-bit SDIV of negative divisor gives wrong result
+Description of problem:
+SDIV of negative divisor gives wrong result because of typo in helper_sdiv(). This is true for QEMU 9.0.0 and earlier.
+
+Place -1 in the Y register and -128 in another reg, then -120 in another register and do SDIV into a result register, instead of the proper value of 1 for the result, the incorrect value of 0 is produced.
+
+There is a typo in target/sparc/helper.c that causes the divisor to be consider unsigned, this patch fixes it:
+
+\*\*\* helper.c.ori Tue Apr 23 16:23:45 2024 --- helper.c Mon Apr 29 20:14:07 2024
+
+---
+
+\*\*\* 121,127 \*\*\*\* return (uint32_t)(b32 \< 0 ? INT32_MAX : INT32_MIN) | (-1ull \<\< 32); }
+
+! a64 /= b; r = a64; if (unlikely(r != a64)) { return (uint32_t)(a64 \< 0 ? INT32_MIN : INT32_MAX) | (-1ull \<\< 32); --- 121,127 ---- return (uint32_t)(b32 \< 0 ? INT32_MAX : INT32_MIN) | (-1ull \<\< 32); }
+
+! a64 /= b32; r = a64; if (unlikely(r != a64)) { return (uint32_t)(a64 \< 0 ? INT32_MIN : INT32_MAX) | (-1ull \<\< 32);
diff --git a/results/classifier/gemma3:12b/kernel/2326 b/results/classifier/gemma3:12b/kernel/2326
new file mode 100644
index 00000000..bcbfe7c3
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2326
@@ -0,0 +1,25 @@
+
+qemu-system-arm regression with Qemu 9.0.0
+Description of problem:
+Bootup of the userland crashes:
+```
+[    1.713693] Run /init as init process
+[    2.372470] Alignment trap: not handling instruction f8530b04 at [<0001225a>]
+[    2.391053] 8<--- cut here ---
+[    2.392942] Unhandled fault: alignment exception (0x001) at 0x00035335
+[    2.397042] [00035335] *pgd=6066b831, *pte=6030734f, *ppte=6030783f
+```
+Steps to reproduce:
+wget https://debug.openadk.org/vexpress-v2p-ca9.dtb
+
+wget https://debug.openadk.org/qemu-arm-vexpress-a9-initramfspiggyback-kernel
+
+qemu-system-arm -M vexpress-a9 -nographic -cpu cortex-a9 -net user -net nic,model=lan9118 -dtb vexpress-v2p-ca9.dtb -kernel qemu-arm-vexpress-a9-initramfspiggyback-kernel -qmp tcp:127.0.0.1:4444,server,nowait -no-reboot
+Additional information:
+It works fine for ARM instruction set, but not for Thumb2.
+
+Git bisect showed following commit as the problematic one:<br>
+From 59754f85ed35cbd5f4bf2663ca2136c78d5b2413 Mon Sep 17 00:00:00 2001<br>
+From: Richard Henderson <richard.henderson@linaro.org><br>
+Date: Fri, 1 Mar 2024 10:41:09 -1000<br>
+Subject: [PATCH] target/arm: Do memory type alignment check when translation disabled<br>
diff --git a/results/classifier/gemma3:12b/kernel/2360 b/results/classifier/gemma3:12b/kernel/2360
new file mode 100644
index 00000000..40a5de2a
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2360
@@ -0,0 +1,31 @@
+
+qemu-system-m68k: double mmu fault
+Description of problem:
+Shutting down Mac OS 7.5.3 after boot from CD image results in a double MMU fault.
+qemu: fatal: DOUBLE MMU FAULT
+
+D0 = 00000008   A0 = 22152a78   F0 = 7fff ffffffffffffffff  (         nan)\
+D1 = 40810000   A1 = 0000c190   F1 = 7fff ffffffffffffffff  (         nan)\
+D2 = 00010490   A2 = 000207a0   F2 = 7fff ffffffffffffffff  (         nan)\
+D3 = 0002befe   A3 = a88879d0   F3 = 7fff ffffffffffffffff  (         nan)\
+D4 = db6d0000   A4 = 00041a86   F4 = 7fff ffffffffffffffff  (         nan)\
+D5 = 00000000   A5 = 39ec4080   F5 = 7fff ffffffffffffffff  (         nan)\
+D6 = 00000001   A6 = 00053178   F6 = 7fff ffffffffffffffff  (         nan)\
+D7 = 07b6d258   A7 = 00000004   F7 = 7fff ffffffffffffffff  (         nan)\
+
+PC = 97f87008   SR = 2210 T:0 I:2 SI X---- \
+FPSR = 00000000 ---- \
+FPCR =     0000 X RN \
+A7(MSP) = 00000000   A7(USP) = 00000000 ->A7(ISP) = 00000004 \
+VBR = 0x00000000 \
+SFC = 0 DFC 5 \
+SSW 00000505 TCR 0000c000 URP 00000000 SRP 07fffa00 \
+DTTR0/1: f900c060/807fc040 ITTR0/1: f900c060/807fc040 \
+MMUSR 00000000, fault at fffffffc \
+Steps to reproduce:
+1. Boot from CD image
+2. Choose Shut down from the Special menu
+Additional information:
+Reproducing requires a quadra 800 rom file.\
+A CD image (f.e. SYSTEM_7-5-3-RETAIL.ISO) can be obtained here: https://macintoshgarden.org/apps/macintosh-os-755 \
+Also see here: https://gitlab.com/qemu-project/qemu/-/issues/2249
diff --git a/results/classifier/gemma3:12b/kernel/2382 b/results/classifier/gemma3:12b/kernel/2382
new file mode 100644
index 00000000..40437ecd
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2382
@@ -0,0 +1,15 @@
+
+QEMU occurs an Error when testing my DIY UEFI aarch64 kernel:Synchronous Exception at 0x00000000E46CCEAC
+Description of problem:
+Shows Synchronous Exception at 0x00000000E46CCEAC and the program halts.
+Steps to reproduce:
+1.Download the UEFIPascalOS on github.
+2.run the bash buildaarch64.sh to build the kernel iso.
+3.Go through the installer guide and enter the kernel.
+4.Enter the account's name and password and press enter,now you can got an error that shows Synchronous Exception at 0x00000000E46CCEAC
+Additional information:
+(no logs,stack traces was shown for the error because logs and stack traces are not exists.)
+screenshots:
+![ScreenShot.png](/uploads/981efb0cfe6149872487b55b9beb504d/QQ截图20240605203550.png)
+If I create two accounts,it will halt on sentence "Welcome to TYDQ System!" and give me  Synchronous Exception at other numbers.
+If I change the memory in virt-machine,the Synchronous Exception showing number will be changed.
diff --git a/results/classifier/gemma3:12b/kernel/2384 b/results/classifier/gemma3:12b/kernel/2384
new file mode 100644
index 00000000..a9ae4822
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2384
@@ -0,0 +1,27 @@
+
+Crash on QEMU 7.2.11 with imx6ul arm cpu cortex-a7 when trying to mount rootfs
+Description of problem:
+trying to run qemu 7.2.11 for NXP mcimx6ul-evk machine, We get a kernel panic trying to mount the rootfs.
+...
+[    7.401206]   No soundcards found.
+[    7.500010] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
+[    7.504607] VFS: Mounted root (vfat filesystem) on device 179:1.
+[    7.511987] devtmpfs: error mounting -2
+[    7.612562] Freeing unused kernel image (initmem) memory: 1024K
+[    7.638370] Run /sbin/init as init process
+[    7.638829]   with arguments:
+[    7.639016]     /sbin/init
+[    7.639247]     earlyprintk
+[    7.639429]     noresume
+...
+[    7.657347] Kernel panic - not syncing: No working init found.
+
+The full log is attached.[qemu_imx6ul_kernel_panic_info.txt](/uploads/c4075a3de7894c18050bf53c32bb18a7/qemu_imx6ul_kernel_panic_info.txt)
+Steps to reproduce:
+1. download and build qemu 7.2.11
+2. download LF_v6.1.55-2.2.1_images_IMX6UL7D.zip from NXP containing kernel, dtb, rootfs, ...etc binaries 
+3. To use diskimage as ‘sd’ card , we need to shrink .wic image we got from NXP to fit in 4GB : 
+./qemu-img resize --shrink imx-image-full.wic 4G
+4. invoke the command to run qemu described above.
+Additional information:
+Any help would be appreciated, if it's not the right forum please advise, thank you.
diff --git a/results/classifier/gemma3:12b/kernel/2389 b/results/classifier/gemma3:12b/kernel/2389
new file mode 100644
index 00000000..3db32c4b
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2389
@@ -0,0 +1,35 @@
+
+Mutex initialization assertion failure due to incompatibility with macOS setrlimit() syscall
+Description of problem:
+Running the command with with any set of arguments instantly crashes with the following error message:
+
+```
+Assertion failed: (mutex->initialized), function qemu_mutex_lock_impl, file ../util/qemu-thread-posix.c, line 92.
+zsh: abort      ./qemu-system-x86_64
+```
+Steps to reproduce:
+As per instructions for building from scratch:
+
+1. `mkdir build && cd build`
+2. `../configure --prefix=$PWD/.. --audio-drv-list=sdl --disable-cocoa --enable-sdl --enable-sdl-image`
+3. `make && make install`
+4. `cd ../bin`
+5. `./qemu-system-x86_64`
+Additional information:
+The issue is coming from the `os_setup_limits()` function in `os-posix.c`. As it turns out, the `setrlimit()` syscall behaves subtly different on macOS than on Linux systems, and the macOS man pages explicitly forbade the code on line 273.
+
+Line 273 from `os-posix.c`:
+
+```
+nofile.rlim_cur = nofile.rlim_max;
+```
+
+macOS `setrlimit()` man page:
+
+```
+COMPATIBILITY
+     setrlimit() now returns with errno set to EINVAL in places that historically succeeded.  It no longer accepts "rlim_cur = RLIM_INFINITY" for
+     RLIM_NOFILE.  Use "rlim_cur = min(OPEN_MAX, rlim_max)".
+```
+
+The man page thankfully gives us the [patch](/uploads/e7c8c6e3b5620c3b1ee34e89661097f3/qemu.patch)
diff --git a/results/classifier/gemma3:12b/kernel/2396 b/results/classifier/gemma3:12b/kernel/2396
new file mode 100644
index 00000000..6acdf660
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2396
@@ -0,0 +1,2 @@
+
+Exception in interrupt handling after upgrading from 8.0 to 9.0
diff --git a/results/classifier/gemma3:12b/kernel/2434 b/results/classifier/gemma3:12b/kernel/2434
new file mode 100644
index 00000000..11b5ac40
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2434
@@ -0,0 +1,30 @@
+
+qemu fails to build tests/unit/test-nested-aio-poll with errors about writing <N> bytes into a region of size <M> overflows the destination
+Description of problem:
+Fails to compile from source with:
+```
+[2/2] Linking target tests/unit/test-nested-aio-poll
+FAILED: tests/unit/test-nested-aio-poll 
+cc -m64  -o tests/unit/test-nested-aio-poll libevent-loop-base.a.p/event-loop-base.c.o libqom.a.p/qom_container.c.o libqom.a.p/qom_object.c.o libqom.a.p/qom_object_interfaces.c.o libqom.a.p/qom_qom-qobject.c.o libblock.a.p/block.c.o libblock.a.p/blockjob.c.o libblock.a.p/job.c.o libblock.a.p/qemu-io-cmds.c.o libblock.a.p/replication.c.o libblock.a.p/nbd_client.c.o libblock.a.p/nbd_client-connection.c.o libblock.a.p/nbd_common.c.o libblock.a.p/scsi_utils.c.o libblock.a.p/scsi_pr-manager.c.o libblock.a.p/scsi_pr-manager-helper.c.o libblock.a.p/block_accounting.c.o libblock.a.p/block_aio_task.c.o libblock.a.p/block_amend.c.o libblock.a.p/block_backup.c.o libblock.a.p/block_blkdebug.c.o libblock.a.p/block_blklogwrites.c.o libblock.a.p/block_blkverify.c.o libblock.a.p/block_block-backend.c.o libblock.a.p/block_block-copy.c.o libblock.a.p/block_commit.c.o libblock.a.p/block_copy-before-write.c.o libblock.a.p/block_copy-on-read.c.o libblock.a.p/block_create.c.o libblock.a.p/block_crypto.c.o libblock.a.p/block_dirty-bitmap.c.o libblock.a.p/block_filter-compress.c.o libblock.a.p/block_graph-lock.c.o libblock.a.p/block_io.c.o libblock.a.p/block_mirror.c.o libblock.a.p/block_nbd.c.o libblock.a.p/block_null.c.o libblock.a.p/block_preallocate.c.o libblock.a.p/block_progress_meter.c.o libblock.a.p/block_qapi.c.o libblock.a.p/block_qcow2.c.o libblock.a.p/block_qcow2-bitmap.c.o libblock.a.p/block_qcow2-cache.c.o libblock.a.p/block_qcow2-cluster.c.o libblock.a.p/block_qcow2-refcount.c.o libblock.a.p/block_qcow2-snapshot.c.o libblock.a.p/block_qcow2-threads.c.o libblock.a.p/block_quorum.c.o libblock.a.p/block_raw-format.c.o libblock.a.p/block_reqlist.c.o libblock.a.p/block_snapshot.c.o libblock.a.p/block_snapshot-access.c.o libblock.a.p/block_throttle.c.o libblock.a.p/block_throttle-groups.c.o libblock.a.p/block_write-threshold.c.o libblock.a.p/block_qcow.c.o libblock.a.p/block_vdi.c.o libblock.a.p/block_vhdx-endian.c.o libblock.a.p/block_vhdx-log.c.o libblock.a.p/block_vhdx.c.o libblock.a.p/block_vmdk.c.o libblock.a.p/block_vpc.c.o libblock.a.p/block_cloop.c.o libblock.a.p/block_bochs.c.o libblock.a.p/block_vvfat.c.o libblock.a.p/block_dmg.c.o libblock.a.p/block_qed-check.c.o libblock.a.p/block_qed-cluster.c.o libblock.a.p/block_qed-l2-cache.c.o libblock.a.p/block_qed-table.c.o libblock.a.p/block_qed.c.o libblock.a.p/block_parallels.c.o libblock.a.p/block_parallels-ext.c.o libblock.a.p/block_file-posix.c.o libblock.a.p/block_iscsi-opts.c.o libblock.a.p/block_nvme.c.o libblock.a.p/block_replication.c.o libblock.a.p/block_linux-aio.c.o libblock.a.p/block_io_uring.c.o libblock.a.p/block_stream.c.o libblock.a.p/block_monitor_bitmap-qmp-cmds.c.o libblock.a.p/block_blkio.c.o libblock.a.p/block_curl.c.o libblock.a.p/block_gluster.c.o libblock.a.p/block_iscsi.c.o libblock.a.p/block_nfs.c.o libblock.a.p/block_ssh.c.o libblock.a.p/block_dmg-bz2.c.o libblock.a.p/meson-generated_.._block_block-gen.c.o libcrypto.a.p/crypto_afsplit.c.o libcrypto.a.p/crypto_akcipher.c.o libcrypto.a.p/crypto_block-luks.c.o libcrypto.a.p/crypto_block-qcow.c.o libcrypto.a.p/crypto_block.c.o libcrypto.a.p/crypto_cipher.c.o libcrypto.a.p/crypto_der.c.o libcrypto.a.p/crypto_hash.c.o libcrypto.a.p/crypto_hmac.c.o libcrypto.a.p/crypto_ivgen-essiv.c.o libcrypto.a.p/crypto_ivgen-plain.c.o libcrypto.a.p/crypto_ivgen-plain64.c.o libcrypto.a.p/crypto_ivgen.c.o libcrypto.a.p/crypto_pbkdf.c.o libcrypto.a.p/crypto_secret_common.c.o libcrypto.a.p/crypto_secret.c.o libcrypto.a.p/crypto_tlscreds.c.o libcrypto.a.p/crypto_tlscredsanon.c.o libcrypto.a.p/crypto_tlscredspsk.c.o libcrypto.a.p/crypto_tlscredsx509.c.o libcrypto.a.p/crypto_tlssession.c.o libcrypto.a.p/crypto_rsakey.c.o libcrypto.a.p/crypto_hash-gnutls.c.o libcrypto.a.p/crypto_hmac-gnutls.c.o libcrypto.a.p/crypto_pbkdf-gnutls.c.o libcrypto.a.p/crypto_secret_keyring.c.o libauthz.a.p/authz_base.c.o libauthz.a.p/authz_list.c.o libauthz.a.p/authz_listfile.c.o libauthz.a.p/authz_simple.c.o libauthz.a.p/authz_pamacct.c.o libio.a.p/io_channel-buffer.c.o libio.a.p/io_channel-command.c.o libio.a.p/io_channel-file.c.o libio.a.p/io_channel-null.c.o libio.a.p/io_channel-socket.c.o libio.a.p/io_channel-tls.c.o libio.a.p/io_channel-util.c.o libio.a.p/io_channel-watch.c.o libio.a.p/io_channel-websock.c.o libio.a.p/io_channel.c.o libio.a.p/io_dns-resolver.c.o libio.a.p/io_net-listener.c.o libio.a.p/io_task.c.o tests/unit/test-nested-aio-poll.p/test-nested-aio-poll.c.o tests/unit/test-nested-aio-poll.p/iothread.c.o -Werror -flto -Wl,--as-needed -Wl,--no-undefined -Wl,-O1 -pie -Wl,-z,relro -Wl,-z,now -march=native -fno-omit-frame-pointer -Wl,-rpath,/usr/lib64/iscsi -Wl,-rpath-link,/usr/lib64/iscsi -Wl,--start-group libqemuutil.a subprojects/libvhost-user/libvhost-user-glib.a subprojects/libvhost-user/libvhost-user.a /usr/lib64/libzstd.so /usr/lib64/libz.so /usr/lib64/iscsi/libiscsi.so -laio /usr/lib64/liburing.so -lblkio /usr/lib64/libcurl.so /usr/lib64/libacl.so /usr/lib64/libgfapi.so /usr/lib64/libglusterfs.so /usr/lib64/libgfrpc.so /usr/lib64/libgfxdr.so /usr/lib64/libuuid.so /usr/lib64/libnfs.so /usr/lib64/libssh.so /usr/lib64/libglib-2.0.so /usr/lib64/libgmodule-2.0.so -pthread -lbz2 /usr/lib64/libgnutls.so -lpam -lnuma /usr/lib64/libgio-2.0.so /usr/lib64/libgobject-2.0.so -lm -Wl,--end-group
+In function ‘aio_notify’,
+    inlined from ‘aio_bh_enqueue’ at ../util/async.c:96:5,
+    inlined from ‘aio_bh_schedule_oneshot_full’ at ../util/async.c:139:5,
+    inlined from ‘aio_wait_kick.part.0’ at ../util/aio-wait.c:54:9:
+../util/async.c:494:5: error: ‘__atomic_store_1’ writing 1 byte into a region of size 0 overflows the destination [-Werror=stringop-overflow=]
+  494 |     qatomic_set(&ctx->notified, true);
+      |     ^
+In function ‘aio_wait_kick.part.0’:
+lto1: note: destination object is likely at address zero
+In function ‘aio_notify’,
+    inlined from ‘aio_bh_enqueue’ at ../util/async.c:96:5,
+    inlined from ‘aio_bh_schedule_oneshot_full’ at ../util/async.c:139:5,
+    inlined from ‘aio_wait_kick.part.0’ at ../util/aio-wait.c:54:9:
+../util/async.c:501:9: error: ‘__atomic_load_4’ writing 4 bytes into a region of size 0 overflows the destination [-Werror=stringop-overflow=]
+  501 |     if (qatomic_read(&ctx->notify_me)) {
+      |         ^
+In function ‘aio_wait_kick.part.0’:
+lto1: note: destination object is likely at address zero
+lto1: all warnings being treated as errors
+```
+Steps to reproduce:
+1. Build qemu from source, probably with LTO enabled and recent GCC.
diff --git a/results/classifier/gemma3:12b/kernel/2446 b/results/classifier/gemma3:12b/kernel/2446
new file mode 100644
index 00000000..fa64bd69
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2446
@@ -0,0 +1,61 @@
+
+linux-user: Qemu doesn't support `set_robust_list` used by glibc robust mutex implementation
+Description of problem:
+It seems that syscall set_robust_list is not implemented on Qemu for any Linux platform: [link]( https://github.com/qemu/qemu/blob/master/linux-user/syscall.c#L12811)
+Steps to reproduce:
+1.  Use below toy program `set_robust_list.c` and compile it without optimizations like:
+```
+    gcc -Wall -W -Wextra -std=gnu17 -pedantic set_robust_list.c -o set_robust_list
+```
+
+```
+#include <stdio.h>
+#include <stdlib.h>
+#include <errno.h>
+#include <sys/syscall.h>
+#include <sys/types.h>
+#include <unistd.h>
+#include <linux/futex.h>
+#include <syscall.h>
+
+int main(void)
+{
+#ifdef __NR_set_robust_list
+    struct robust_list_head head;
+    size_t len = sizeof(struct robust_list_head);
+
+    // This call to set_robust_list function should fail
+    int err = syscall(__NR_set_robust_list, &head, -1);
+    if (err < 0)
+        perror("1st set_robust_list error");
+    else
+        puts("1st set_robust_list OK");
+
+    // This call to set_robust_list function should be sucessful
+    err = syscall(__NR_set_robust_list, &head, len);
+    if (err < 0)
+        perror("2nd set_robust_list error");
+    else
+        puts("2nd set_robust_list OK");
+#else
+    puts("No set_robust_list support");
+#endif
+    exit(0);
+}
+```
+
+2. Run program on Qemu and compare output with output from x64 build. In my case it looks like:
+```
+root@AMDC4705:/runtime/set_robust_list# ./set_robust_list
+1st set_robust_list error: Invalid argument
+2nd set_robust_list OK
+root@AMDC4705:/runtime/set_robust_list# ./set_robust_list-riscv
+1st set_robust_list error: Function not implemented
+2nd set_robust_list error: Function not implemented
+```
+Additional information:
+Working `set_robust_list` on Linux is quite important in context of named robust mutexes. In NPTL `set_robust_list` is used internally at ld.so initialization time to perform following check: [link](https://github.com/bminor/glibc/blob/master/sysdeps/nptl/dl-tls_init_tp.c#L96)
+
+When syscall fails, later `pthread_mutex_init` (with `PTHREAD_MUTEX_ROBUST` + `PTHREAD_PROCESS_SHARED` attributes) end up with `ENOTSUP` error [link](https://github.com/bminor/glibc/blob/master/nptl/pthread_mutex_init.c#L99).
+
+In dotnet we use robust mutexes for process synchronization purpose. Although there are other available techniques like named semaphores or file locks, robust mutexes are better locking option in case of unexpected process death.
diff --git a/results/classifier/gemma3:12b/kernel/246 b/results/classifier/gemma3:12b/kernel/246
new file mode 100644
index 00000000..388fff1e
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/246
@@ -0,0 +1,2 @@
+
+Build fails with 64 bits time_t
diff --git a/results/classifier/gemma3:12b/kernel/2466 b/results/classifier/gemma3:12b/kernel/2466
new file mode 100644
index 00000000..226b9f5f
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2466
@@ -0,0 +1,25 @@
+
+I'm not sure. But I Think I could cause the err(include/qemu/queue.h).
+Description of problem:
+At file "include/qemu/queue.h", Maybe I Think QTAILQ_REMOVE could cause a Error.
+
+```
+#define QTAILQ_REMOVE(head, elm, field) do {                            \
+       if (((elm)->field.tqe_next) != NULL)                            \
+           (elm)->field.tqe_next->field.tqe_circ.tql_prev =            \
+               (elm)->field.tqe_circ.tql_prev;                         \
+       else                                                            \
+           (head)->tqh_circ.tql_prev = (elm)->field.tqe_circ.tql_prev; \
+       (elm)->field.tqe_circ.tql_prev->tql_next = (elm)->field.tqe_next; \
+       (elm)->field.tqe_circ.tql_prev = NULL;                          \
+       (elm)->field.tqe_circ.tql_next = NULL;                          \
+       (elm)->field.tqe_next = NULL;                                   \
+} while (/*CONSTCOND*/0)
+```
+If the length of the que is one, line 7 cause a segmentation fault.
+Steps to reproduce:
+1. Create a Que with QTAILQ_INIT
+2. Add one element to que.
+3. Remove the element with QTAILQ_REMOVE
+Additional information:
+queue.h file is located at "inclue/qemu/queue.h"
diff --git a/results/classifier/gemma3:12b/kernel/2473 b/results/classifier/gemma3:12b/kernel/2473
new file mode 100644
index 00000000..53153a46
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2473
@@ -0,0 +1,4 @@
+
+qemu-system-aarch64: Stop execution on unhandled exceptions
+Additional information:
+
diff --git a/results/classifier/gemma3:12b/kernel/2481 b/results/classifier/gemma3:12b/kernel/2481
new file mode 100644
index 00000000..c9218524
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2481
@@ -0,0 +1,2 @@
+
+Possible dereference of NULL
diff --git a/results/classifier/gemma3:12b/kernel/249 b/results/classifier/gemma3:12b/kernel/249
new file mode 100644
index 00000000..1bb7154f
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/249
@@ -0,0 +1,2 @@
+
+guest OS catches a page  fault bug when running dotnet
diff --git a/results/classifier/gemma3:12b/kernel/2511 b/results/classifier/gemma3:12b/kernel/2511
new file mode 100644
index 00000000..bcb8aba4
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2511
@@ -0,0 +1,33 @@
+
+Regression 9.1.0rc2: target/i386/tcg/access.c:18: access_prepare_mmu: Assertion '...' failed.
+Description of problem:
+Executing QEMU command line crashes with 
+   ```
+qemu-system-x86_64: ../target/i386/tcg/access.c:18: access_prepare_mmu: Assertion `size > 0 && size <= TARGET_PAGE_SIZE' failed.
+   ```
+Steps to reproduce:
+1. Download https://www.qemu-advent-calendar.org/2020/download/day07.tar.gz
+2. Execute with QEMU command line
+Additional information:
+git bisect finishes with:
+   ```
+8b131065080af3cf2dda04e4e190c5a74fec2f31 is the first bad commit
+commit 8b131065080af3cf2dda04e4e190c5a74fec2f31
+Author: Paolo Bonzini <pbonzini@redhat.com>
+Date:   Tue Jun 18 09:13:49 2024 +0200
+
+    target/i386/tcg: use X86Access for TSS access
+    
+    This takes care of probing the vaddr range in advance, and is also faster
+    because it avoids repeated TLB lookups.  It also matches the Intel manual
+    better, as it says "Checks that the current (old) TSS, new TSS, and all
+    segment descriptors used in the task switch are paged into system memory";
+    note however that it's not clear how the processor checks for segment
+    descriptors, and this check is not included in the AMD manual.
+    
+    Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
+    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
+
+ target/i386/tcg/seg_helper.c | 110 +++++++++++++++++++++++--------------------
+ 1 file changed, 58 insertions(+), 52 deletions(-)
+   ```
diff --git a/results/classifier/gemma3:12b/kernel/2523 b/results/classifier/gemma3:12b/kernel/2523
new file mode 100644
index 00000000..672a4980
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2523
@@ -0,0 +1,21 @@
+
+[9.0.2] PPC: snapshot replay freeze on PowerPC
+Description of problem:
+Qemu 9.0.2 cannot replay snapshots on PowerPC e500mc (Book-E) architecture. When I try to do this, the program freezes.
+Steps to reproduce:
+1. Run bare metal example from the attachment with the first command-line to create snapshot. Then end it using ctrl+c.
+2. Run bare metal example from the attachment with the second command-line to replay snapshot. Running will freeze, use ctrl+c.
+Additional information:
+e500mc example that prints Hello World: [ppc-e500.zip](/uploads/ef9ce53abc3f17490d4894c041956038/ppc-e500.zip)
+
+Log output:
+```
+% qemu-system-ppc -cpu e500  -M ppce500 -kernel hello.elf -display none -serial stdio -icount 1,rr=record,rrfile=main.bin,rrsnapshot=init -drive file=empty.qcow2,if=none,id=rr
+Hello world
+qemu-system-ppc: terminating on signal 2
+% qemu-system-ppc -cpu e500  -M ppce500 -kernel hello.elf -display none -serial stdio -icount 1,rr=replay,rrfile=main.bin,rrsnapshot=init -drive file=empty.qcow2,if=none,id=rr
+qemu-system-ppc: terminating on signal 2
+qemu-system-ppc: Playback shouldn't have to iowait (insn total 0/68 left, event 4 is EVENT_INSTRUCTION)
+zsh: IOT instruction (core dumped)  qemu-system-ppc -cpu e500 -M ppce500 -kernel hello.elf -display none -serial
+```
+`Playback shouldn't have to iowait` error caused by 1f881ea4a444ef36a8b6907b0b82be4b3af253a2 commit, see https://gitlab.com/qemu-project/qemu/-/issues/2524
diff --git a/results/classifier/gemma3:12b/kernel/2525 b/results/classifier/gemma3:12b/kernel/2525
new file mode 100644
index 00000000..6817a6e5
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2525
@@ -0,0 +1,2 @@
+
+bFLT triggers accel/tcg/user-exec.c:505: page_set_flags: Assertion `have_mmap_lock()' failed.
diff --git a/results/classifier/gemma3:12b/kernel/2526 b/results/classifier/gemma3:12b/kernel/2526
new file mode 100644
index 00000000..59aea734
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2526
@@ -0,0 +1,40 @@
+
+qemu-system-aarch64: Build of system emulators with --static failed on aarch64 Ubuntu 22.04 for tests/unit/test-bitcnt
+Description of problem:
+Build Qemu got error:
+```
+[1107/2870] Compiling C object tcg/libtcg_system.fa.p/perf.c.o
+[1108/2870] Linking target tests/unit/test-bitcnt
+FAILED: tests/unit/test-bitcnt
+cc  -o tests/unit/test-bitcnt tests/unit/test-bitcnt.p/test-bitcnt.c.o -Wl,--as-needed -Wl,--no-undefined -pie -Wl,--whole-archive libevent-loop-base.fa libqom.fa -Wl,--no-whole-archive -static-pie -fstack-protector-strong -Wl,-z,relro -Wl,-z,now -Wl,--start-group libqemuutil.a subprojects/libvhost-user/libvhost-user-glib.a subprojects/libvhost-user/libvhost-user.a libevent-loop-base.fa libqom.fa /usr/lib/aarch64-linux-gnu/libgio-2.0.a /usr/lib/aarch64-linux-gnu/libgmodule-2.0.a -pthread /usr/lib/aarch64-linux-gnu/libz.a -ldl /usr/lib/aarch64-linux-gnu/libblkid.a /usr/lib/aarch64-linux-gnu/libselinux.a /usr/lib/aarch64-linux-gnu/libsepol.a /usr/lib/aarch64-linux-gnu/libpcre2-8.a /usr/lib/aarch64-linux-gnu/libgobject-2.0.a /usr/lib/aarch64-linux-gnu/libffi.a /usr/lib/aarch64-linux-gnu/libglib-2.0.a -lm /usr/lib/aarch64-linux-gnu/libpcre.a -lmount -lmount -Wl,--end-group
+/usr/bin/ld: cannot find -lmount: No such file or directory
+/usr/bin/ld: cannot find -lmount: No such file or directory
+collect2: error: ld returned 1 exit status
+[1109/2870] Linking target tests/unit/test-qapi-util
+FAILED: tests/unit/test-qapi-util
+cc  -o tests/unit/test-qapi-util tests/unit/test-qapi-util.p/test-qapi-util.c.o -Wl,--as-needed -Wl,--no-undefined -pie -Wl,--whole-archive libevent-loop-base.fa libqom.fa -Wl,--no-whole-archive -static-pie -fstack-protector-strong -Wl,-z,relro -Wl,-z,now -Wl,--start-group libqemuutil.a subprojects/libvhost-user/libvhost-user-glib.a subprojects/libvhost-user/libvhost-user.a libevent-loop-base.fa libqom.fa /usr/lib/aarch64-linux-gnu/libgio-2.0.a /usr/lib/aarch64-linux-gnu/libgmodule-2.0.a -pthread /usr/lib/aarch64-linux-gnu/libz.a -ldl /usr/lib/aarch64-linux-gnu/libblkid.a /usr/lib/aarch64-linux-gnu/libselinux.a /usr/lib/aarch64-linux-gnu/libsepol.a /usr/lib/aarch64-linux-gnu/libpcre2-8.a /usr/lib/aarch64-linux-gnu/libgobject-2.0.a /usr/lib/aarch64-linux-gnu/libffi.a /usr/lib/aarch64-linux-gnu/libglib-2.0.a -lm /usr/lib/aarch64-linux-gnu/libpcre.a -lmount -lmount -Wl,--end-group
+/usr/bin/ld: cannot find -lmount: No such file or directory
+/usr/bin/ld: cannot find -lmount: No such file or directory
+collect2: error: ld returned 1 exit status
+[1110/2870] Linking target tests/unit/check-qom-interface
+FAILED: tests/unit/check-qom-interface
+cc  -o tests/unit/check-qom-interface tests/unit/check-qom-interface.p/check-qom-interface.c.o -Wl,--as-needed -Wl,--no-undefined -pie -Wl,--whole-archive libevent-loop-base.fa libqom.fa -Wl,--no-whole-archive -static-pie -fstack-protector-strong -Wl,-z,relro -Wl,-z,now -Wl,--start-group libqemuutil.a subprojects/libvhost-user/libvhost-user-glib.a subprojects/libvhost-user/libvhost-user.a libevent-loop-base.fa libqom.fa /usr/lib/aarch64-linux-gnu/libgio-2.0.a /usr/lib/aarch64-linux-gnu/libgmodule-2.0.a -pthread /usr/lib/aarch64-linux-gnu/libz.a -ldl /usr/lib/aarch64-linux-gnu/libblkid.a /usr/lib/aarch64-linux-gnu/libselinux.a /usr/lib/aarch64-linux-gnu/libsepol.a /usr/lib/aarch64-linux-gnu/libpcre2-8.a /usr/lib/aarch64-linux-gnu/libgobject-2.0.a /usr/lib/aarch64-linux-gnu/libffi.a /usr/lib/aarch64-linux-gnu/libglib-2.0.a -lm /usr/lib/aarch64-linux-gnu/libpcre.a -lmount -lmount -Wl,--end-group
+/usr/bin/ld: cannot find -lmount: No such file or directory
+/usr/bin/ld: cannot find -lmount: No such file or directory
+collect2: error: ld returned 1 exit status
+```
+After install libmount-dev, this error is still there.
+If we just run:
+```
+./configure --target-list=aarch64-softmmu --enable-kvm
+make -16
+```
+This works well.
+Steps to reproduce:
+```
+1. ./configure --target-list=aarch64-softmmu --enable-kvm --disable-brlapi --disable-docs --disable-curses --disable-gtk --disable-opengl --disable-sdl --disable-spice --disable-vte --disable-vnc --disable-vnc-jpeg --disable-png --disable-vnc-sasl --disable-auth-pam --disable-glusterfs --disable-libiscsi --disable-libnfs --disable-libssh --disable-bzip2 --disable-lzo --disable-snappy --disable-slirp --disable-libusb --disable-usb-redir --static --disable-qom-cast-debug --disable-libudev --disable-curl --disable-rdma --disable-tools --enable-virtfs --disable-bsd-user --disable-linux-user --disable-sparse --disable-vde --disable-nettle --disable-xen --disable-linux-aio --disable-capstone --disable-virglrenderer --disable-replication --disable-smartcard --disable-guest-agent --disable-guest-agent-msi --disable-vvfat --disable-vdi --disable-qed --disable-qcow1 --disable-bochs --disable-cloop --disable-dmg --disable-parallels --disable-colo-proxy --disable-debug-graph-lock --disable-hexagon-idef-parser --disable-libdw --disable-pipewire --disable-pixman --disable-relocatable --disable-rutabaga-gfx --disable-vmdk --disable-avx512bw --disable-vpc --disable-vhdx --disable-hv-balloon
+
+2.make -j16
+```
+Additional information:
+
diff --git a/results/classifier/gemma3:12b/kernel/2542 b/results/classifier/gemma3:12b/kernel/2542
new file mode 100644
index 00000000..57a69ae2
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2542
@@ -0,0 +1,2 @@
+
+qemu-system-arm failure with picolibc tests since 59754f85ed35cbd5f4bf2663ca2136c78d5b2413
diff --git a/results/classifier/gemma3:12b/kernel/2552 b/results/classifier/gemma3:12b/kernel/2552
new file mode 100644
index 00000000..cc547f3d
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2552
@@ -0,0 +1,73 @@
+
+system libfdt said to be too old (1.5.1 min required) but 1.7.1 is installed.
+Description of problem:
+<--
+I am running an update build of the latest qemu version 9.0.2 to update it from 8.1.2 in the IPFire firewall distribution.
+The build command being run was
+
+`
+./configure \
+	--prefix=/usr \
+	--sysconfdir=/etc \
+	--localstatedir=/var \
+	--enable-kvm \
+	--disable-attr \
+	--target-list="$(TARGETS)" \
+	--extra-cflags="$(CFLAGS)" \
+	--enable-spice \
+	--enable-usb-redir \
+	--enable-seccomp \
+	--disable-docs \
+	--disable-sdl \
+	--enable-slirp 
+`
+
+and where $TARGETS is
+
+`	x86_64-linux-user \
+	aarch64-linux-user \
+	riscv64-linux-user \
+	x86_64-softmmu \
+	aarch64-softmmu \
+	riscv64-softmmu
+`
+
+and $CFLAGS is
+
+`	"-O2"
+	"-g0"
+	"-pipe"
+	"-Wall"
+	"-fexceptions"
+	"-fPIC"
+	"-Wp,-U_FORTIFY_SOURCE"
+	"-Wp,-D_FORTIFY_SOURCE=3"
+	"-Wp,-D_GLIBCXX_ASSERTIONS"
+	"-fstack-protector-strong"
+	"-fstack-clash-protection"
+` 
+
+This built qemu successfully with version 8.1.2 and earlier versions.
+
+From version 9.0.1 onwards the subproject dtc has been removed from the Source Tarball and the build came back with the error message
+
+Library fdt found: NO
+
+../meson.build:3190:18: ERROR: Git command failed: ['/usr/bin/git', 'fetch', '--depth', '1', 'origin', 'b6910bec11614980a21e46fbccc35934b671bd81']
+
+The git command failed as the distribution build is done with no network connection. All packages have to be available in the build and so the package cannot be downloaded during the build.
+
+Therefore I moved the dtc package in the IPFire build to before building qemu and added --disable-download to the ./configure options.
+
+The error message changed to
+
+Library fdt found: YES
+
+../meson.build:3182:7: ERROR: Problem encountered: system libfdt requested, but it is too old (1.5.1 or newer required)
+
+However the dtc libfdt version is 1.7.1 - definitely newer than 1.5.1
+
+Why is the version being seen as too old?
+How do I get this to detect the dtc libfdt version correctly (it has detected that libfdt is present in the IPFire build environment).
+
+-->
diff --git a/results/classifier/gemma3:12b/kernel/2585 b/results/classifier/gemma3:12b/kernel/2585
new file mode 100644
index 00000000..f0f75082
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2585
@@ -0,0 +1,8 @@
+
+qemu-system-arm highmem support broken with TCG
+Additional information:
+I initially bisected this to commit 39a1fd25287f ("target/arm: Fix handling of LPAE block descriptors"), which introduced an identical bug by masking the wrong address bits due to a type mismatch, but this was in turn fixed by commit c2360eaa0262 ("target/arm: Fix qemu-system-arm handling of LPAE block descriptors for highmem"). The bug resurfaced between qemu-7.1.0 and qemu-7.2.0 after commit f3639a64f602 ("target/arm: Use softmmu tlbs for page table walking"), but may be caused by the preceding 4a35855682ce ("target/arm: Plumb debug into S1Translate") which fails to boot for an unrelated reason.
+
+I reproduced this on qemu-7.2 as shipped by Debian as well as on qemu-9.1 (built locally).
+
+Part of this problem appeared to be hidden by the 'highmem=on' argument not having the intended effect during parts of the bisection, which I worked around by overriding the 'pa_bits' variable in machvirt_init().
diff --git a/results/classifier/gemma3:12b/kernel/2591 b/results/classifier/gemma3:12b/kernel/2591
new file mode 100644
index 00000000..0817f60a
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2591
@@ -0,0 +1,2 @@
+
+Black screen and DTB errors while trying to emulate the kernel of the RaspiOS (based on Debian Bookworm) using the parameter -machine raspi4b
diff --git a/results/classifier/gemma3:12b/kernel/2600 b/results/classifier/gemma3:12b/kernel/2600
new file mode 100644
index 00000000..52fd65d7
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2600
@@ -0,0 +1,2 @@
+
+qemu-user MAP_SHARED TB invalidation
diff --git a/results/classifier/gemma3:12b/kernel/2605 b/results/classifier/gemma3:12b/kernel/2605
new file mode 100644
index 00000000..a99b8b84
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2605
@@ -0,0 +1,2 @@
+
+amd64/v4 support
diff --git a/results/classifier/gemma3:12b/kernel/2618 b/results/classifier/gemma3:12b/kernel/2618
new file mode 100644
index 00000000..4723af2c
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2618
@@ -0,0 +1,2 @@
+
+INTEGER_OVERFLOW in sparc.c
diff --git a/results/classifier/gemma3:12b/kernel/2626 b/results/classifier/gemma3:12b/kernel/2626
new file mode 100644
index 00000000..3006888f
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2626
@@ -0,0 +1,9 @@
+
+QEMU crashes after host time moves backwards
+Description of problem:
+QEMU process crashes after time synchronized and moved backwards on the host.
+Steps to reproduce:
+As detailed in the [thread](https://bugzilla.redhat.com/show_bug.cgi?id=2228406)
+
+1. create a virtual machine and change tick period in the guest
+2. executing `while [ 1 ];do hwclock --systohc; hwclock --hctosys;done` on the host
diff --git a/results/classifier/gemma3:12b/kernel/2634 b/results/classifier/gemma3:12b/kernel/2634
new file mode 100644
index 00000000..c7a1262f
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2634
@@ -0,0 +1,178 @@
+
+Replay/record does not work with `rrsnapshot`/`loadvm`
+Description of problem:
+Qemu's record/replay feature does not properly work when using snapshots (like rrsnapshot).
+
+Record/replay without snapshotting works just fine, but when using `rrsnapshot=...` the replay is stuck at boot. `loadvm` monitor command also gets qemu stuck.
+
+Record command:
+
+```
+$ qemu-system-x86_64 \
+  -cpu SandyBridge -smp 1 \
+  -serial stdio -display none \
+  -m 4096 \
+  -drive file=./empty.qcow2,id=rr \
+  -kernel ./boot/vmlinuz-lts \
+  -initrd ./boot/initramfs-lts  .
+  -monitor telnet::12345,server,nowait \
+  -append "console=ttyS0 root=/dev/ram0 alpine_dev=cdrom:iso9660 modules=loop,squashfs,sd-mod,usb-storage quiet" \
+  -icount shift=auto,rrfile=rr,rr=record,rrsnapshot=init
+```
+
+Broken replay command, which gets qemu stuck:
+
+```
+$ qemu-system-x86_64 \
+  -cpu SandyBridge -smp 1 \
+  -serial stdio -display none \
+  -m 4096 \
+  -drive file=./empty.qcow2,id=rr \
+  -kernel ./boot/vmlinuz-lts \
+  -initrd ./boot/initramfs-lts  .
+  -monitor telnet::12345,server,nowait \
+  -append "console=ttyS0 root=/dev/ram0 alpine_dev=cdrom:iso9660 modules=loop,squashfs,sd-mod,usb-storage quiet" \
+  -icount shift=auto,rrfile=rr,rr=replay,rrsnapshot=init
+
+qemu-system-x86_64: warning: TCG doesn't support requested feature: CPUID.01H:ECX.tsc-deadline [bit 24]
+```
+
+Record/replay without `rrsnapshot`/`loadvm`/etc works as expected.
+Steps to reproduce:
+To reproduce i've used alpine linux kernel as the guest:
+
+```
+wget https://dl-cdn.alpinelinux.org/alpine/v3.20/releases/x86_64/alpine-standard-3.20.3-x86_64.iso
+7z x alpine-standard-3.20.3-x86_64.iso
+```
+
+Prerequisites - an empty qcow2 file for snapshots:
+
+```
+qemu-img create -f qcow2 empty.qcow2 1G
+```
+
+Running an alpine linux kernel with `rr=record` - works just fine, kernel boots, accepts input.
+
+```
+$ qemu-system-x86_64 \
+  -cpu SandyBridge -smp 1 \
+  -serial stdio -display none \
+  -m 4096 \
+  -drive file=./empty.qcow2,id=rr \
+  -kernel ./boot/vmlinuz-lts \
+  -initrd ./boot/initramfs-lts  .
+  -monitor telnet::12345,server,nowait \
+  -append "console=ttyS0 root=/dev/ram0 alpine_dev=cdrom:iso9660 modules=loop,squashfs,sd-mod,usb-storage quiet" \
+  -icount shift=auto,rrfile=rr,rr=record,rrsnapshot=init
+
+qemu-system-x86_64: warning: TCG doesn't support requested feature: CPUID.01H:ECX.tsc-deadline [bit 24]
+mount: mounting /dev/ram0 on /sysroot failed: Invalid argument
+Mounting root failed. 
+initramfs emergency recovery shell launched. Type 'exit' to continue boot
+sh: can't access tty; job control turned off
+~ # ls -alh
+total 32K    
+drwx------   18 root     root           0 Oct 21 13:02 .
+drwx------   18 root     root           0 Oct 21 13:02 ..
+-rw-------    1 root     root           8 Oct 21 13:02 .ash_history
+drwxr-xr-x    2 root     root           0 Jun 18 12:44 .modloop
+drwxr-xr-x    2 root     root           0 Oct 21 13:02 bin
+drwxr-xr-x    9 root     root        2.5K Oct 21 13:02 dev
+drwxr-xr-x    4 root     root           0 Oct 21 13:02 etc
+-rwxr-xr-x    1 root     root       25.9K Jun 18 12:44 init
+drwxr-xr-x    5 root     root           0 Jun 18 12:44 lib
+drwxr-xr-x    5 root     root           0 Jun 18 12:44 media
+drwxr-xr-x    2 root     root           0 Jun 18 12:44 newroot
+dr-xr-xr-x  114 root     root           0 Oct 21 13:02 proc
+drwx------    2 root     root           0 Sep  4 12:53 root
+drwxr-xr-x    3 root     root           0 Oct 21 13:02 run
+drwxr-xr-x    2 root     root           0 Oct 21 13:02 sbin
+dr-xr-xr-x   13 root     root           0 Oct 21 13:02 sys
+drwxr-xr-x    2 root     root           0 Oct 21 13:02 sysroot
+drwxr-xr-x    2 root     root           0 Oct 21 13:02 tmp
+drwxr-xr-x    5 root     root           0 Oct 21 13:02 usr
+drwxr-xr-x    3 root     root           0 Jun 18 12:44 var
+~ # echo "AAAAAAAA?"
+AAAAAAAA?
+~ # 
+```
+
+`rr`-file is produced, which can be used for replaying **without** `rrsnapshot`-option:
+
+```
+$ qemu-system-x86_64 \
+  -cpu SandyBridge -smp 1 \
+  -serial stdio -display none \
+  -m 4096 \
+  -drive file=./empty.qcow2,id=rr \
+  -kernel ./boot/vmlinuz-lts \
+  -initrd ./boot/initramfs-lts  .
+  -monitor telnet::12345,server,nowait \
+  -append "console=ttyS0 root=/dev/ram0 alpine_dev=cdrom:iso9660 modules=loop,squashfs,sd-mod,usb-storage quiet" \
+  -icount shift=auto,rrfile=rr,rr=replay
+
+qemu-system-x86_64: warning: TCG doesn't support requested feature: CPUID.01H:ECX.tsc-deadline [bit 24]
+mount: mounting /dev/ram0 on /sysroot failed: Invalid argument
+Mounting root failed. 
+initramfs emergency recovery shell launched. Type 'exit' to continue boot
+sh: can't access tty; job control turned off
+~ # ls -alh
+total 32K    
+drwx------   18 root     root           0 Oct 21 13:02 .
+drwx------   18 root     root           0 Oct 21 13:02 ..
+-rw-------    1 root     root           8 Oct 21 13:02 .ash_history
+drwxr-xr-x    2 root     root           0 Jun 18 12:44 .modloop
+drwxr-xr-x    2 root     root           0 Oct 21 13:02 bin
+drwxr-xr-x    9 root     root        2.5K Oct 21 13:02 dev
+drwxr-xr-x    4 root     root           0 Oct 21 13:02 etc
+-rwxr-xr-x    1 root     root       25.9K Jun 18 12:44 init
+drwxr-xr-x    5 root     root           0 Jun 18 12:44 lib
+drwxr-xr-x    5 root     root           0 Jun 18 12:44 media
+drwxr-xr-x    2 root     root           0 Jun 18 12:44 newroot
+dr-xr-xr-x  114 root     root           0 Oct 21 13:02 proc
+drwx------    2 root     root           0 Sep  4 12:53 root
+drwxr-xr-x    3 root     root           0 Oct 21 13:02 run
+drwxr-xr-x    2 root     root           0 Oct 21 13:02 sbin
+dr-xr-xr-x   13 root     root           0 Oct 21 13:02 sys
+drwxr-xr-x    2 root     root           0 Oct 21 13:02 sysroot
+drwxr-xr-x    2 root     root           0 Oct 21 13:02 tmp
+drwxr-xr-x    5 root     root           0 Oct 21 13:02 usr
+drwxr-xr-x    3 root     root           0 Jun 18 12:44 var
+~ # echo "AAAAAAAA?"
+AAAAAAAA?
+~ # 
+```
+
+As you can see, replaying emulation session works as expected. How ever, if I add the `rrsnapshot`-option, it gets stuck:
+
+```
+$ qemu-system-x86_64 \
+  -cpu SandyBridge -smp 1 \
+  -serial stdio -display none \
+  -m 4096 \
+  -drive file=./empty.qcow2,id=rr \
+  -kernel ./boot/vmlinuz-lts \
+  -initrd ./boot/initramfs-lts  .
+  -monitor telnet::12345,server,nowait \
+  -append "console=ttyS0 root=/dev/ram0 alpine_dev=cdrom:iso9660 modules=loop,squashfs,sd-mod,usb-storage quiet" \
+  -icount shift=auto,rrfile=rr,rr=replay,rrsnapshot=init
+
+qemu-system-x86_64: warning: TCG doesn't support requested feature: CPUID.01H:ECX.tsc-deadline [bit 24] 
+```
+
+This also can be reproduced without `rrsnapshot` option, by issuing `loadvm init` from qemu monitor:
+
+```
+$ telnet localhost 12345
+qemu> loadvm init
+...
+```
+
+Or, by using `gdb` and issuing reverse-commands that require `loadvm` to load previous state, like `reverse-stepi` or `reverse-continue`.
+
+Attaching a debugger & using debug-prints shows some thread being stuck in the [`rcu.c`](https://gitlab.com/qemu-project/qemu/-/blob/master/util/rcu.c), near the `qemu_event_wait(&rcu_call_ready_event);`. I've tried to wait for quite some time (about an hour) and there was no result.
+Additional information:
+**Qemu build.** Qemu binary built from sources of 9.1.0 with `--target-list=x86_64-softmmu`.
+
+**Host machine.** An almost clean Ubuntu 20.04 with necessary packages for building qemu from the latest release sources.
diff --git a/results/classifier/gemma3:12b/kernel/2641 b/results/classifier/gemma3:12b/kernel/2641
new file mode 100644
index 00000000..6abcc34f
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2641
@@ -0,0 +1,2 @@
+
+Possible DEREF_OF_NULL in linux-user/syscall.c
diff --git a/results/classifier/gemma3:12b/kernel/2647 b/results/classifier/gemma3:12b/kernel/2647
new file mode 100644
index 00000000..f9785c00
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2647
@@ -0,0 +1,48 @@
+
+A code error in accel/tcg/user-exec.c
+Description of problem:
+accel/tcg/user-exec.c:
+```
+static int probe_access_internal(CPUArchState *env, vaddr addr,
+                                 int fault_size, MMUAccessType access_type,
+                                 bool nonfault, uintptr_t ra)
+{
+    int acc_flag;
+    bool maperr;
+
+    switch (access_type) {
+    case MMU_DATA_STORE:
+        acc_flag = PAGE_WRITE_ORG;
+        break;
+    case MMU_DATA_LOAD:
+        acc_flag = PAGE_READ;
+        break;
+    case MMU_INST_FETCH:
+        acc_flag = PAGE_EXEC;
+        break;
+    default:
+        g_assert_not_reached();
+    }
+
+    if (guest_addr_valid_untagged(addr)) {
+        int page_flags = page_get_flags(addr);
+        if (page_flags & acc_flag) {
+            if ((acc_flag == PAGE_READ || acc_flag == PAGE_WRITE)
+                && cpu_plugin_mem_cbs_enabled(env_cpu(env))) {
+                return TLB_MMIO;
+            }
+            return 0; /* success */
+        }
+        maperr = !(page_flags & PAGE_VALID);
+    } else {
+        maperr = true;
+    }
+
+    if (nonfault) {
+        return TLB_INVALID_MASK;
+    }
+
+    cpu_loop_exit_sigsegv(env_cpu(env), addr, access_type, maperr, ra);
+}
+```
+The conditional judgment "acc_flag == PAGE_WRITE" seems to have an issue, because acc_flag can only be PAGE_WRITE_ORG, PAGE_READ or PAGE_EXEC from the previous code.
diff --git a/results/classifier/gemma3:12b/kernel/265 b/results/classifier/gemma3:12b/kernel/265
new file mode 100644
index 00000000..46147fd8
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/265
@@ -0,0 +1,2 @@
+
+x86: retf or iret pagefault sets wrong error code
diff --git a/results/classifier/gemma3:12b/kernel/2657 b/results/classifier/gemma3:12b/kernel/2657
new file mode 100644
index 00000000..4d4bf815
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2657
@@ -0,0 +1,12 @@
+
+Kernel crashed when installing OpenServer 6 D2M2a
+Description of problem:
+The kernel crashed when finishing installation.
+Steps to reproduce:
+1. Download OpenServer6D2M2a-DVD.iso for free from Xinuos website(a free account is needed, but the registation is easy to be done)
+2. Create new virtual hard drive
+3. Boot the installation ISO
+4. Install with all default settings and all packages, evaluate license is okay.
+5. Boom!
+Additional information:
+![QQ20241106-110404](/uploads/b42d5d6fef34606b4a6c672e33f06b97/QQ20241106-110404.png)
diff --git a/results/classifier/gemma3:12b/kernel/2662 b/results/classifier/gemma3:12b/kernel/2662
new file mode 100644
index 00000000..c925cdaa
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2662
@@ -0,0 +1,12 @@
+
+powerpc: MSR_ILE bit must not be restored in rfi
+Description of problem:
+On processors that implement the MSR_ILE bit (that is, G4 and prior), the MSR_ILE bit is not restored by the `rfi` instruction.
+
+qemu, however, does restore this bit from `srr1`.
+
+Some ppcel operating systems rely on MSR_ILE not being restored by `rfi`, for example, Windows NT when taking a syscall.
+Additional information:
+Patch provided: [rfi_msr_ile.patch](/uploads/aa661fc8bcbb47585ff63f8e4ebb38ba/rfi_msr_ile.patch)
+
+The correct behaviour for G4 and prior is performed for later processors too. Given PPC970 and later have that bit documented as reserved, this should not be a problem.
diff --git a/results/classifier/gemma3:12b/kernel/267 b/results/classifier/gemma3:12b/kernel/267
new file mode 100644
index 00000000..b1fa4a5d
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/267
@@ -0,0 +1,2 @@
+
+qemu-x86_64 segment prefixes error
diff --git a/results/classifier/gemma3:12b/kernel/2673 b/results/classifier/gemma3:12b/kernel/2673
new file mode 100644
index 00000000..4ac7d422
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2673
@@ -0,0 +1,6 @@
+
+qemu-system-riscv32 does not pass official riscv-tests
+Description of problem:
+I run riscv-tests using the above command and find qemu raises Illegalinstruction when `sret` in the machine mode.Therefore qemu cannot pass the rv32ui-v-and test.
+Additional information:
+The tests https://github.com/riscv-software-src/riscv-tests
diff --git a/results/classifier/gemma3:12b/kernel/2683 b/results/classifier/gemma3:12b/kernel/2683
new file mode 100644
index 00000000..2ba502d5
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2683
@@ -0,0 +1,40 @@
+
+TCG: probe_access() has inconsistent behavior
+Description of problem:
+In full-system mode, probe_access() will return NULL when the flag is TLB_MMIO.
+
+accel/tcg/cputlb.c: probe_access_internal()
+```
+    if (unlikely(flags & ~(TLB_WATCHPOINT | TLB_NOTDIRTY | TLB_CHECK_ALIGNED))
+        || (access_type != MMU_INST_FETCH && force_mmio)) {
+        *phost = NULL;
+        return TLB_MMIO;
+    }
+```
+But in linux-user mode, it will return correct address when the flag is TLB_MMIO.
+
+accel/tcg/user-exec.c: probe_access()
+```
+    return size ? g2h(env_cpu(env), addr) : NULL;
+```
+This will lead to some different behaviors, like cbo.zero in RISC-V.
+
+target/riscv/op_helper.c: helper_cbo_zero()
+```
+    mem = probe_write(env, address, cbozlen, mmu_idx, ra);
+
+    if (likely(mem)) {
+        memset(mem, 0, cbozlen);
+    } else {
+        for (int i = 0; i < cbozlen; i++) {
+            cpu_stb_mmuidx_ra(env, address + i, 0, mmu_idx, ra);
+        }
+    }
+```
+When the current instruction has memory callback by plugin:
+
+Full-system mode uses slow-path(cpu_stb_mmuidx_ra) and inject mem_cbs correctly.
+
+Linux-user mode uses fast-path(memset) and doesn't inject callbacks.
+
+To ensure consistent results, probe_access() should return NULL when the flag is TLB_MMIO in linux-user mode.
diff --git a/results/classifier/gemma3:12b/kernel/2702 b/results/classifier/gemma3:12b/kernel/2702
new file mode 100644
index 00000000..21c00641
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2702
@@ -0,0 +1,54 @@
+
+qtest-arm/sse-timer-test sometimes fails on s390x host
+Description of problem:
+The sse-timer-test sometimes fails on the s390x runner in Travis, see:
+
+https://app.travis-ci.com/github/huth/qemu/jobs/628508770#L6337 :
+
+```
+>>> G_TEST_DBUS_DAEMON=/home/travis/build/huth/qemu/tests/dbus-vmstate-daemon.sh MSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MESON_TEST_ITERATION=1 UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 PYTHON=/home/travis/build/huth/qemu/build/pyvenv/bin/python3 MALLOC_PERTURB_=165 QTEST_QEMU_BINARY=./qemu-system-arm /home/travis/build/huth/qemu/build/tests/qtest/sse-timer-test --tap -k
+
+▶  70/287 ERROR:../tests/qtest/sse-timer-test.c:91:test_counter: assertion failed (readl(COUNTER_BASE + CNTCV_LO) == 100): (0 == 100) ERROR         
+
+ 70/287 qemu:qtest+qtest-arm / qtest-arm/sse-timer-test                       ERROR            0.71s   killed by signal 6 SIGABRT
+
+――――――――――――――――――――――――――――――――――――― ✀  ―――――――――――――――――――――――――――――――――――――
+
+stderr:
+
+**
+
+ERROR:../tests/qtest/sse-timer-test.c:91:test_counter: assertion failed (readl(COUNTER_BASE + CNTCV_LO) == 100): (0 == 100)
+
+(test program exited with status code -6)
+
+――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
+```
+
+https://app.travis-ci.com/github/huth/qemu/jobs/628373181#L6336 :
+
+```
+>>> G_TEST_DBUS_DAEMON=/home/travis/build/huth/qemu/tests/dbus-vmstate-daemon.sh PYTHON=/home/travis/build/huth/qemu/build/pyvenv/bin/python3 UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 MSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 QTEST_QEMU_BINARY=./qemu-system-arm MALLOC_PERTURB_=250 MESON_TEST_ITERATION=1 /home/travis/build/huth/qemu/build/tests/qtest/sse-timer-test --tap -k
+
+▶  70/287 ERROR:../tests/qtest/sse-timer-test.c:91:test_counter: assertion failed (readl(COUNTER_BASE + CNTCV_LO) == 100): (0 == 100) ERROR         
+
+ 70/287 qemu:qtest+qtest-arm / qtest-arm/sse-timer-test                       ERROR            0.95s   killed by signal 6 SIGABRT
+
+――――――――――――――――――――――――――――――――――――― ✀  ―――――――――――――――――――――――――――――――――――――
+
+stderr:
+
+**
+
+ERROR:../tests/qtest/sse-timer-test.c:91:test_counter: assertion failed (readl(COUNTER_BASE + CNTCV_LO) == 100): (0 == 100)
+
+(test program exited with status code -6)
+
+――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
+```
+Steps to reproduce:
+1. Run the QEMU CI on Travis
+Additional information:
+It seems to be a new or intermittent problem, two weeks ago it was still working fine:
+
+https://app.travis-ci.com/github/huth/qemu/jobs/627999506#L6325
diff --git a/results/classifier/gemma3:12b/kernel/2721 b/results/classifier/gemma3:12b/kernel/2721
new file mode 100644
index 00000000..6ef748c3
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2721
@@ -0,0 +1,2 @@
+
+Failure with macOS 15.2 on ARM64: Property 'host-arm-cpu.sme' not found
diff --git a/results/classifier/gemma3:12b/kernel/2749 b/results/classifier/gemma3:12b/kernel/2749
new file mode 100644
index 00000000..78f1069b
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2749
@@ -0,0 +1,80 @@
+
+TSAN/RaceHunter data race on bh->flags in aio_compute_bh_timeout
+Description of problem:
+Switching the TSAN build for `test-aio-multithread` unit test reveals the data race on `bh->flags` in `aio_compute_bh_timeout`.
+
+The same data race can be found in the list of warnings in #851 and #1496.
+
+I investigated the data race and I can reproduce the same race with our tool RaceHunter on the test `tests/unit/test-thread-pool.c` where two accesses may happen simultaneously. It is not false alarm, because RaceHunter introduces the delay and catches both accesses exactly at the same time, not just predicting the race due to missing happens-before as TSAN does.
+
+```
+WARNING: SMC RaceHunter: Data race found:
+  read access from thread 0 [handle=0]  at pc=0x55b851f660b9, addr=7b1000000168 (4 bytes)
+    #0 aio_compute_bh_timeout util/async.c:259:18
+    #1 aio_compute_timeout util/async.c:282:15
+    #2 aio_poll util/aio-posix.c:628:26 (test-thread-pool+0xa4223f)
+    #3 test_submit_aio tests/unit/test-thread-pool.c:70:9
+    #4 main tests/unit/test-thread-pool.c
+
+  Previous atomic write access from thread 4 [handle=4]  at pc=0x55b851f65e24, addr=7b1000000168 (4 bytes)
+    #0 aio_bh_enqueue util/async.c:81:17
+    #1 qemu_bh_schedule util/async.c:235:5
+    #2 worker_thread util/thread-pool.c:118:9
+    #3 qemu_thread_start util/qemu-thread-posix.c:543:9
+```
+
+Both are accesses to `flags` in `BHList` (`bh->flags`)
+The write access in `aio_bh_enqueue` is protected by atomic operation `qatomic_fetch_or` while second read access is not atomic and not protected by locks.
+
+The read access in `aio_compute_bh_timeout` seems to rely on RCU mechanism `QSLIST_FOREACH_RCU(bh, head, next)`, but in this case the writer should also use RCU protected assign.
+Steps to reproduce:
+1. configure --enable-tsan --cc=clang --cxx=clang++ --enable-trace-backends=ust --enable-fdt=system --disable-slirp
+2. make check-unit test-aio-multithread
+3. See the warning in the log
+```
+WARNING: ThreadSanitizer: data race (pid=3514443)
+  Atomic write of size 4 at 0x7b1000000168 by thread T17:
+    #0 aio_bh_enqueue /home/mordan/qemu/build/../util/async.c:81:17 (test-thread-pool+0xa5e933)
+    #1 qemu_bh_schedule /home/mordan/qemu/build/../util/async.c:235:5 (test-thread-pool+0xa5e933)
+    #2 worker_thread /home/mordan/qemu/build/../util/thread-pool.c:118:9 (test-thread-pool+0xa66153)
+    #3 qemu_thread_start /home/mordan/qemu/build/../util/qemu-thread-posix.c:543:9 (test-thread-pool+0xa496c0)
+
+  Previous read of size 4 at 0x7b1000000168 by main thread:
+    #0 aio_compute_bh_timeout /home/mordan/qemu/build/../util/async.c:259:18 (test-thread-pool+0xa5ebc8)
+    #1 aio_compute_timeout /home/mordan/qemu/build/../util/async.c:282:15 (test-thread-pool+0xa5ebc8)
+    #2 aio_poll /home/mordan/qemu/build/../util/aio-posix.c:628:26 (test-thread-pool+0xa42d4f)
+    #3 do_test_cancel /home/mordan/qemu/build/../tests/unit/test-thread-pool.c:199:9 (test-thread-pool+0x50f0e8)
+    #4 test_cancel_async /home/mordan/qemu/build/../tests/unit/test-thread-pool.c:230:5 (test-thread-pool+0x50ec01)
+    #5 <null> <null> (libglib-2.0.so.0+0x7daed) (BuildId: e845b8fd2f396872c036976626389ffc4f50c9c5)
+    #6 __libc_start_call_main csu/../sysdeps/nptl/libc_start_call_main.h:58:16 (libc.so.6+0x29d8f) (BuildId: 490fef8403240c91833978d494d39e537409b92e)
+
+  As if synchronized via sleep:
+    #0 nanosleep out/lib/clangrt-x86_64-unknown-linux-gnu/./out/lib/clangrt-x86_64-unknown-linux-gnu/./toolchain/llvm-project/compiler-rt/lib/tsan/rtl/tsan_interceptors_posix.cpp:365:3 (test-thread-pool+0x34507d)
+    #1 g_usleep <null> (libglib-2.0.so.0+0x7ff76) (BuildId: e845b8fd2f396872c036976626389ffc4f50c9c5)
+    #2 worker_thread /home/mordan/qemu/build/../util/thread-pool.c:111:15 (test-thread-pool+0xa66115)
+    #3 qemu_thread_start /home/mordan/qemu/build/../util/qemu-thread-posix.c:543:9 (test-thread-pool+0xa496c0)
+
+  Location is heap block of size 56 at 0x7b1000000140 allocated by main thread:
+    #0 malloc out/lib/clangrt-x86_64-unknown-linux-gnu/./out/lib/clangrt-x86_64-unknown-linux-gnu/./toolchain/llvm-project/compiler-rt/lib/tsan/rtl/tsan_interceptors_posix.cpp:667:5 (test-thread-pool+0x346151)
+    #1 g_malloc <null> (libglib-2.0.so.0+0x5e738) (BuildId: e845b8fd2f396872c036976626389ffc4f50c9c5)
+    #2 thread_pool_init_one /home/mordan/qemu/build/../util/thread-pool.c:333:27 (test-thread-pool+0xa655c8)
+    #3 thread_pool_new /home/mordan/qemu/build/../util/thread-pool.c:348:5 (test-thread-pool+0xa655c8)
+    #4 aio_get_thread_pool /home/mordan/qemu/build/../util/async.c:441:28 (test-thread-pool+0xa5ed54)
+    #5 thread_pool_submit_aio /home/mordan/qemu/build/../util/thread-pool.c:246:24 (test-thread-pool+0xa64f0d)
+    #6 thread_pool_submit /home/mordan/qemu/build/../util/thread-pool.c:295:5 (test-thread-pool+0xa65362)
+    #7 test_submit /home/mordan/qemu/build/../tests/unit/test-thread-pool.c:49:5 (test-thread-pool+0x50e53f)
+    #8 <null> <null> (libglib-2.0.so.0+0x7daed) (BuildId: e845b8fd2f396872c036976626389ffc4f50c9c5)
+    #9 __libc_start_call_main csu/../sysdeps/nptl/libc_start_call_main.h:58:16 (libc.so.6+0x29d8f) (BuildId: 490fef8403240c91833978d494d39e537409b92e)
+
+  Thread T17 'worker' (tid=3514461, running) created by thread T16 at:
+    #0 pthread_create out/lib/clangrt-x86_64-unknown-linux-gnu/./out/lib/clangrt-x86_64-unknown-linux-gnu/./toolchain/llvm-project/compiler-rt/lib/tsan/rtl/tsan_interceptors_posix.cpp:1022:3 (test-thread-pool+0x34793d)
+    #1 qemu_thread_create /home/mordan/qemu/build/../util/qemu-thread-posix.c:583:11 (test-thread-pool+0xa49550)
+    #2 do_spawn_thread /home/mordan/qemu/build/../util/thread-pool.c:146:5 (test-thread-pool+0xa65f5e)
+    #3 worker_thread /home/mordan/qemu/build/../util/thread-pool.c:83:5 (test-thread-pool+0xa65f5e)
+    #4 qemu_thread_start /home/mordan/qemu/build/../util/qemu-thread-posix.c:543:9 (test-thread-pool+0xa496c0)
+
+SUMMARY: ThreadSanitizer: data race /home/mordan/qemu/build/../util/async.c:81:17 in aio_bh_enqueue
+```
+
+
+@hreitz, @kmwolf, @bonzini Are there any other synchronization that was intended to ensure that the accesses do not happen simultaneously?
diff --git a/results/classifier/gemma3:12b/kernel/2770 b/results/classifier/gemma3:12b/kernel/2770
new file mode 100644
index 00000000..6ba04395
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2770
@@ -0,0 +1,15 @@
+
+Build failure due to missing  keyctl_pkey_encrypt
+Description of problem:
+
+Steps to reproduce:
+1. git checkout v7.2.0
+2. ./configure --target-list=arm-softmmu;make
+3. ../backends/cryptodev-lkcf.c: In function ‘cryptodev_lkcf_execute_task’:
+../backends/cryptodev-lkcf.c:358:19: error: implicit declaration of function ‘keyctl_pkey_encrypt’; did you mean ‘keyctl_reject’? [-Werror=implicit-function-declaration]
+             ret = keyctl_pkey_encrypt(key_id, op_desc,
+                   ^~~~~~~~~~~~~~~~~~~
+                   keyctl_reject
+../backends/cryptodev-lkcf.c:358:19: error: nested extern declaration of ‘keyctl_pkey_encrypt’ [-Werror=nested-externs]
+Additional information:
+
diff --git a/results/classifier/gemma3:12b/kernel/2794 b/results/classifier/gemma3:12b/kernel/2794
new file mode 100644
index 00000000..0d3b104a
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2794
@@ -0,0 +1,50 @@
+
+qemu-system-m68k virt machine doesn't boot Linux kernels using 68020, 68030 and 68060 CPUs
+Description of problem:
+QEMU doesn't seem to be able to start Linux kernels using a CPU other than a 68040 (which does work fine)
+
+To rule out host issues, the issue is reproductible on Debian Unstable amd64 (with version QEMU emulator version 9.2.0)(Debian 1:9.2.0+ds-5))
+
+To rule out cross-compilation issues, the kernel has been rebuild inside a virt machine (using a 68040 CPU), running Debian Unstable 
+
+Each CPU model below gets stuck early before kernel boot during the ABCGHIJK thing. The Kernel doesn't seem to boot and QEMU process eat 100% of a CPU physical core
+
+**68020**
+```
+qemu-system-m68k -M virt -cpu m68060 -m 1G -nographic -kernel /home/demik/tmp/vmlinux
+ABCGH
+```
+
+**68030**
+```
+qemu-system-m68k -M virt -cpu m68060 -m 1G -nographic -kernel /home/demik/tmp/vmlinux
+ABC
+```
+
+**68060**
+```
+qemu-system-m68k -M virt -cpu m68060 -m 1G -nographic -kernel /home/demik/tmp/vmlinux
+ABC
+```
+Steps to reproduce:
+1. build a kernel with 68020/030/060 support (using virt_defconfig as base)
+2. start QEMU with the command line above
+Additional information:
+68020 is understandable as it may need some sort of 68851 emulation.
+
+Relevant Kernel config Processor configuration:
+```
+#
+# Processor Type
+#
+CONFIG_M68KCLASSIC=y
+# CONFIG_COLDFIRE is not set
+CONFIG_M68020=y
+CONFIG_M68030=y
+CONFIG_M68040=y
+CONFIG_M68060=y
+```
+
+This may be related to the following issues (but I don't have the skillset to confirm that)
+- https://gitlab.com/qemu-project/qemu/-/issues/2091
+- https://gitlab.com/qemu-project/qemu/-/issues/2500
diff --git a/results/classifier/gemma3:12b/kernel/2798 b/results/classifier/gemma3:12b/kernel/2798
new file mode 100644
index 00000000..d1fac671
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2798
@@ -0,0 +1,39 @@
+
+Cannot disconnect Split VMDK
+Description of problem:
+I used to mount VDI with qemu-nbd and it worked, I could mount/unmount many times. Since VDI was 400 GB, I converted to Split2G VMDK.
+In addition to file.vmdk, there are file-s001.vmdk, file-s002.vmdk..file-s201.vmdk 
+With that, I can mount, but disconnect does not work. Tried also with `blockdev`, did not help, not sure if that is needed.
+I know that with LV deactivation of volume group is needed before disconnect. Not aware if there is equivalent with Split VMDK.
+Cannot say if issue in qemu-nbd or qemu vmdk driver.
+Experienced in qemu 6.2.0 and also when upgraded to 9.0.2. May try later with master that seems to build 9.2.50.
+Steps to reproduce:
+1. sudo modprobe nbd max_part=4 && sudo qemu-nbd -f vmdk -c /dev/nbd1 file.vmdk && sudo mount /dev/nbd1p1 /mnt/vmdk
+2. sudo umount -l /mnt/vmdk && sleep 2 && sudo blockdev --flushbufs /dev/nbd1  && sleep 2 && sudo qemu-nbd -dv /dev/nbd1 
+3. lsblk # see still nbd1
+Additional information:
+```
+[  424.020397] block nbd1: NBD_DISCONNECT
+[  424.020417] block nbd1: Disconnected due to user request.
+[  424.020420] block nbd1: shutting down sockets
+[  424.024278] I/O error, dev nbd1, sector 842468736 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
+[  424.024318] I/O error, dev nbd1, sector 842468736 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
+[  424.024327] Buffer I/O error on dev nbd1, logical block 105308592, async page read
+[  424.028202] I/O error, dev nbd1, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
+[  424.028229] I/O error, dev nbd1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
+[  424.028233] Buffer I/O error on dev nbd1, logical block 0, async page read
+[  424.028249] I/O error, dev nbd1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
+[  424.028252] Buffer I/O error on dev nbd1, logical block 0, async page read
+--
+[  548.931610] block nbd1: NBD_DISCONNECT
+[  548.931620] block nbd1: Send disconnect failed -32
+[  548.935594] blk_print_req_error: 6 callbacks suppressed
+[  548.935598] I/O error, dev nbd1, sector 842468736 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
+[  548.935634] I/O error, dev nbd1, sector 842468736 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
+[  548.935642] buffer_io_error: 2 callbacks suppressed
+[  548.935644] Buffer I/O error on dev nbd1, logical block 105308592, async page read
+[  548.940187] I/O error, dev nbd1, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
+[  548.940211] I/O error, dev nbd1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
+[  548.940215] Buffer I/O error on dev nbd1, logical block 0, async page read
+[  548.940230] I/O error, dev nbd1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
+```
diff --git a/results/classifier/gemma3:12b/kernel/2799 b/results/classifier/gemma3:12b/kernel/2799
new file mode 100644
index 00000000..762df571
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2799
@@ -0,0 +1,42 @@
+
+compile failure for linux-user when host libc defines "struct sched_attr" in its sched.h
+Description of problem:
+When I tried to build commit 871af84d the build process stopped in  [3306/9698] Compiling C object libqemu...-linux-user.a.p/linux-user_syscall.c.o
+
+Here is the error log:
+
+```
+../linux-user/syscall.c:364:8: error: redefinition of 'struct sched_attr'
+  364 | struct sched_attr {
+      |        ^~~~~~~~~~
+In file included from /usr/include/bits/sched.h:63,
+                 from /usr/include/sched.h:43,
+                 from /usr/include/pthread.h:22,
+                 from /usr/include/glib-2.0/glib/deprecated/gthread.h:126,
+                 from /usr/include/glib-2.0/glib.h:115,
+                 from /home/fred/qemu-git/src/qemu/include/glib-compat.h:32,
+                 from /home/fred/qemu-git/src/qemu/include/qemu/osdep.h:161,
+                 from ../linux-user/syscall.c:20:
+/usr/include/linux/sched/types.h:98:8: note: originally defined here
+   98 | struct sched_attr {
+      |        ^~~~~~~~~~
+```
+Steps to reproduce:
+1. Grab commit 871af84d 
+2. Use this configure command line: 
+
+```
+--prefix=/usr \
+    --sysconfdir=/etc \
+    --localstatedir=/var \
+    --libexecdir=/usr/lib/qemu \
+    --smbd=/usr/bin/smbd \
+    --enable-modules \
+    --enable-sdl \
+    --disable-werror \
+    "${@:2}"
+```
+
+3. Launch ninja and wait.
+Additional information:
+
diff --git a/results/classifier/gemma3:12b/kernel/2822 b/results/classifier/gemma3:12b/kernel/2822
new file mode 100644
index 00000000..8741fa56
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2822
@@ -0,0 +1,12 @@
+
+Data race with state field of ThreadPoolElement
+Description of problem:
+A data race in the access of `ThreadPoolElement` state field in `util/thread-pool.c` was identified using TSAN.
+Steps to reproduce:
+```sh
+QEMU_BUILD_DIR=<path to the QEMU build directory>
+QEMU_DIR=<path to the QEMU repository directory>
+configure --enable-tsan --cc=clang --cxx=clang++ --enable-trace-backends=ust --enable-fdt=system --disable-slirp
+make tests/unit/test-thread-pool
+MALLOC_PERTURB_=111 G_TEST_SRCDIR=$QEMU_BUILD_DIR/tests/unit G_TEST_BUILDDIR=$QEMU_BUILD_DIR/tests/unit $QEMU_BUILD_DIR/tests/unit/test-thread-pool --tap -k
+```
diff --git a/results/classifier/gemma3:12b/kernel/2832 b/results/classifier/gemma3:12b/kernel/2832
new file mode 100644
index 00000000..251c2852
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2832
@@ -0,0 +1,100 @@
+
+Random kernel panic (2/3) in github macOS runner: IO-APIC + timer doesn't work!
+Description of problem:
+Random kernel panic (2/3 runs average) with this traceback:
+
+```
+[    0.020000] Kernel panic - not syncing: IO-APIC + timer doesn't work!  Boot with apic=debug and send a report.  Then try booting with the 'noapic' option.
+[    0.020000] CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.11.0-14-generic #15-Ubuntu
+[    0.020000] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS edk2-stable202408-prebuilt.qemu.org 08/13/2024
+[    0.020000] Call Trace:
+[    0.020000]  <TASK>
+[    0.020000]  show_stack+0x49/0x60
+[    0.020000]  dump_stack_lvl+0x5f/0x90
+[    0.020000]  dump_stack+0x10/0x18
+[    0.020000]  panic+0x16a/0x328
+[    0.020000]  check_timer+0x4d1/0x570
+[    0.020000]  setup_IO_APIC+0x1e5/0x210
+[    0.020000]  apic_intr_mode_init+0xd0/0xf0
+[    0.020000]  x86_late_time_init+0x24/0x40
+[    0.020000]  start_kernel+0x3f9/0x4a0
+[    0.020000]  x86_64_start_reservations+0x24/0x30
+[    0.020000]  x86_64_start_kernel+0xf2/0x100
+[    0.020000]  common_startup_64+0x13e/0x141
+[    0.020000]  </TASK>
+[    0.020000] ---[ end Kernel panic - not syncing: IO-APIC + timer doesn't work!  Boot with apic=debug and send a report.  Then try booting with the 'noapic' option. ]---
+```
+Steps to reproduce:
+1. Start qemu in macos-13 github runner
+Additional information:
+Example failed build:
+https://github.com/nirs/vmnet-helper/actions/runs/13477646025/job/37658748139
+
+serial.log:
+```
+3h3hBdsDxe: failed to load Boot0001 "UEFI QEMU QEMU CD-ROM " from PciRoot(0x0)/Pci(0x1,0x0)/Scsi(0x0,0x0): Not Found
+BdsDxe: loading Boot0002 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x3,0x0)
+BdsDxe: starting Boot0002 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x3,0x0)
+EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
+[    0.000000] Linux version 6.11.0-14-generic (buildd@lcy02-amd64-032) (x86_64-linux-gnu-gcc-14 (Ubuntu 14.2.0-4ubuntu2) 14.2.0, GNU ld (GNU Binutils for Ubuntu) 2.43.1) #15-Ubuntu SMP PREEMPT_DYNAMIC Fri Jan 10 23:48:25 UTC 2025 (Ubuntu 6.11.0-14.15-generic 6.11.0)
+[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-6.11.0-14-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
+[    0.000000] KERNEL supported cpus:
+[    0.000000]   Intel GenuineIntel
+[    0.000000]   AMD AuthenticAMD
+[    0.000000]   Hygon HygonGenuine
+[    0.000000]   Centaur CentaurHauls
+[    0.000000]   zhaoxin   Shanghai  
+[    0.000000] BIOS-provided physical RAM map:
+[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
+[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000007fffff] usable
+[    0.000000] BIOS-e820: [mem 0x0000000000800000-0x0000000000807fff] ACPI NVS
+[    0.000000] BIOS-e820: [mem 0x0000000000808000-0x000000000080afff] usable
+[    0.000000] BIOS-e820: [mem 0x000000000080b000-0x000000000080bfff] ACPI NVS
+[    0.000000] BIOS-e820: [mem 0x000000000080c000-0x0000000000810fff] usable
+[    0.000000] BIOS-e820: [mem 0x0000000000811000-0x00000000008fffff] ACPI NVS
+[    0.000000] BIOS-e820: [mem 0x0000000000900000-0x000000003ee41fff] usable
+[    0.000000] BIOS-e820: [mem 0x000000003ee42000-0x000000003ef02fff] reserved
+[    0.000000] BIOS-e820: [mem 0x000000003ef03000-0x000000003f8ecfff] usable
+[    0.000000] RCU Tasks: Setting shift to 0 and lim to 1 rcu_task_cb_adjust=1.
+[    0.000000] RCU Tasks Rude: Setting shift to 0 and lim to 1 rcu_task_cb_adjust=1.
+[    0.000000] RCU Tasks Trace: Setting shift to 0 and lim to 1 rcu_task_cb_adjust=1.
+[    0.000000] NR_IRQS: 524544, nr_irqs: 256, preallocated irqs: 16
+[    0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention.
+[    0.000000] Console: colour dummy device 80x25
+[    0.000000] printk: legacy console [tty1] enabled
+[    0.000000] printk: legacy console [ttyS0] enabled
+[    0.000000] ACPI: Core revision 20240322
+[    0.000000] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604467 ns
+[    0.001000] APIC: Switch to symmetric I/O mode setup
+[    0.003000] x2apic: IRQ remapping doesn't support X2APIC mode
+[    0.011000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
+[    0.013000] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
+[    0.013000] ...trying to set up timer (IRQ0) through the 8259A ...
+[    0.013000] ..... (found apic 0 pin 2) ...
+[    0.014000] ....... failed.
+[    0.014000] ...trying to set up timer as Virtual Wire IRQ...
+[    0.018000] ..... failed.
+[    0.018000] ...trying to set up timer as ExtINT IRQ...
+[    0.020000] ..... failed :(.
+[    0.020000] Kernel panic - not syncing: IO-APIC + timer doesn't work!  Boot with apic=debug and send a report.  Then try booting with the 'noapic' option.
+[    0.020000] CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.11.0-14-generic #15-Ubuntu
+[    0.020000] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS edk2-stable202408-prebuilt.qemu.org 08/13/2024
+[    0.020000] Call Trace:
+[    0.020000]  <TASK>
+[    0.020000]  show_stack+0x49/0x60
+[    0.020000]  dump_stack_lvl+0x5f/0x90
+[    0.020000]  dump_stack+0x10/0x18
+[    0.020000]  panic+0x16a/0x328
+[    0.020000]  check_timer+0x4d1/0x570
+[    0.020000]  setup_IO_APIC+0x1e5/0x210
+[    0.020000]  apic_intr_mode_init+0xd0/0xf0
+[    0.020000]  x86_late_time_init+0x24/0x40
+[    0.020000]  start_kernel+0x3f9/0x4a0
+[    0.020000]  x86_64_start_reservations+0x24/0x30
+[    0.020000]  x86_64_start_kernel+0xf2/0x100
+[    0.020000]  common_startup_64+0x13e/0x141
+[    0.020000]  </TASK>
+[    0.020000] ---[ end Kernel panic - not syncing: IO-APIC + timer doesn't work!  Boot with apic=debug and send a report.  Then try booting with the 'noapic' option. ]---
+```
+
+Same Ubuntu image never fail with vfkit vm on the same macos-13 github runners.
diff --git a/results/classifier/gemma3:12b/kernel/2846 b/results/classifier/gemma3:12b/kernel/2846
new file mode 100644
index 00000000..c8756401
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2846
@@ -0,0 +1,2 @@
+
+linux-user hangs if fd_trans_lock is held during fork
diff --git a/results/classifier/gemma3:12b/kernel/285 b/results/classifier/gemma3:12b/kernel/285
new file mode 100644
index 00000000..1792c1ef
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/285
@@ -0,0 +1,2 @@
+
+qemu-user child process hangs when forking due to glib allocation
diff --git a/results/classifier/gemma3:12b/kernel/2855 b/results/classifier/gemma3:12b/kernel/2855
new file mode 100644
index 00000000..1ebe5d46
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2855
@@ -0,0 +1,30 @@
+
+masking mode field in mepc before mret
+Description of problem:
+I thought I found a bug in OpenSBI (https://github.com/riscv-software-src/opensbi/issues/391) but it actually is a QEMU bug.
+It is described here: https://lists.infradead.org/pipermail/opensbi/2025-March/008166.html
+Steps to reproduce:
+1. use an application with vectored mode enabled (The RISC-V Instruction Set Manual: Volume II: Privileged Architecture / chapter 10.1.2) in QEMU 
+2. trigger an illegal instruction interrupt (handle it in machine mode - not by medeleg)
+3. in a machine mode trap: Store STVEC in MEPC.
+4. do a mret 
+5. the first bits of mepc are not masked so the address in mepc (comming from (v)stvec) will be false after mret
+Additional information:
+My guess is that the instructions from the following quote (masking of lower bits in mepc) from the official spec must be implemented here:
+https://gitlab.com/qemu-project/qemu/-/blob/master/target/riscv/op_helper.c?ref_type=heads#L387
+Maybe also somewhere else. 
+
+> 3.1.14. Machine Exception Program Counter (mepc)
+> 
+> mepc is an MXLEN-bit read/write register formatted as shown in Figure 21. The low bit of mepc
+> (mepc[0]) is always zero. On implementations that support only IALIGN=32, the two low bits
+> (mepc[1:0]) are always zero.
+> 
+> If an implementation allows IALIGN to be either 16 or 32 (by changing CSR misa, for example), then,
+> whenever IALIGN=32, bit mepc[1] is masked on reads so that it appears to be 0. This masking occurs
+> also for the implicit read by the MRET instruction. Though masked, mepc[1] remains writable when
+> IALIGN=32.
+> 
+> mepc is a WARL register that must be able to hold all valid virtual addresses. It need not be capable of
+> holding all possible invalid addresses. Prior to writing mepc, implementations may convert an invalid
+> address into some other invalid address that mepc is capable of holding.
diff --git a/results/classifier/gemma3:12b/kernel/289 b/results/classifier/gemma3:12b/kernel/289
new file mode 100644
index 00000000..b55c096a
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/289
@@ -0,0 +1,2 @@
+
+Guest freezes until there is a keyboard input on Windows version
diff --git a/results/classifier/gemma3:12b/kernel/2899 b/results/classifier/gemma3:12b/kernel/2899
new file mode 100644
index 00000000..24733665
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2899
@@ -0,0 +1,37 @@
+
+Regression 10.0.0rc1: Segmentation fault on executing QEMU advent calendar 2014, day 4
+Description of problem:
+On executing QEMU, a segmentation fault occurs
+Steps to reproduce:
+1. Download https://www.qemu-advent-calendar.org/2014/download/stxmas.tar.xz
+2. Execute with QEMU command line
+Additional information:
+git bisect finishes with:
+
+```
+456709db50f424d112bc5f07260fdc51555f3a24 is the first bad commit
+commit 456709db50f424d112bc5f07260fdc51555f3a24
+Author: Paolo Bonzini <pbonzini@redhat.com>
+Date:   Sun Dec 15 10:06:10 2024 +0100
+
+    target/i386: execute multiple REP/REPZ iterations without leaving TB
+    
+    Use a TCG loop so that it is not necessary to go through the setup steps
+    of REP and through the I/O check on every iteration.  Interestingly, this
+    is not a particularly effective optimization on its own, though it avoids
+    the cost of correct RF emulation that was added in the previous patch.
+    The main benefit lies in allowing the hoisting of loop invariants outside
+    the loop, which will happen separately.
+    
+    The loop exits when the low 16 bits of CX/ECX/RCX are zero (so generally
+    speaking the string operation runs in 65536 iteration batches) to give
+    the main loop an opportunity to pick up interrupts.
+    
+    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
+    Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
+    Link: https://lore.kernel.org/r/20241215090613.89588-12-pbonzini@redhat.com
+    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
+
+ target/i386/tcg/translate.c | 55 ++++++++++++++++++++++++++++++++++++++++-----
+ 1 file changed, 49 insertions(+), 6 deletions(-)
+```
diff --git a/results/classifier/gemma3:12b/kernel/2902 b/results/classifier/gemma3:12b/kernel/2902
new file mode 100644
index 00000000..d3dd7978
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2902
@@ -0,0 +1,12 @@
+
+Data Race with slh_first Field in test-aio-multithread
+Description of problem:
+Potential data races in the `QSLIST_INSERT_HEAD_ATOMIC` macro were identified using TSAN.
+Steps to reproduce:
+```sh
+QEMU_BUILD_DIR=<path to the QEMU build directory>
+QEMU_DIR=<path to the QEMU repository directory>
+configure --enable-tsan --cc=clang --cxx=clang++ --enable-trace-backends=ust --enable-fdt=system --disable-slirp
+make tests/unit/test-bdrv-drain
+MALLOC_PERTURB_=102 G_TEST_SRCDIR=$QEMU_BUILD_DIR/tests/unit G_TEST_BUILDDIR=$QEMU_BUILD_DIR/tests/unit $QEMU_BUILD_DIR/tests/unit/test-aio-multithread --tap -k
+```
diff --git a/results/classifier/gemma3:12b/kernel/2904 b/results/classifier/gemma3:12b/kernel/2904
new file mode 100644
index 00000000..35e37562
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2904
@@ -0,0 +1,12 @@
+
+Data Race in data->cb() call and cb assignment in test-aio-multithread
+Description of problem:
+Potential data races between the `data->cb()` call and the assignment of `cb` in `test-aio-multithread` were identified using TSAN.
+Steps to reproduce:
+```sh
+QEMU_BUILD_DIR=<path to the QEMU build directory>
+QEMU_DIR=<path to the QEMU repository directory>
+configure --enable-tsan --cc=clang --cxx=clang++ --enable-trace-backends=ust --enable-fdt=system --disable-slirp
+make tests/unit/test-bdrv-drain
+MALLOC_PERTURB_=102 G_TEST_SRCDIR=$QEMU_BUILD_DIR/tests/unit G_TEST_BUILDDIR=$QEMU_BUILD_DIR/tests/unit $QEMU_BUILD_DIR/tests/unit/test-aio-multithread --tap -k
+```
diff --git a/results/classifier/gemma3:12b/kernel/2907 b/results/classifier/gemma3:12b/kernel/2907
new file mode 100644
index 00000000..9d024502
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2907
@@ -0,0 +1,2 @@
+
+replay_mutex_unlock() assertion on macOS
diff --git a/results/classifier/gemma3:12b/kernel/2911 b/results/classifier/gemma3:12b/kernel/2911
new file mode 100644
index 00000000..5d53d5bb
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2911
@@ -0,0 +1,66 @@
+
+G5/970 emulation not complete enough for OSX ?
+Description of problem:
+Leopard image that boots on G4 does not boot on G5
+Steps to reproduce:
+1. Find preinstalled hdd image on Archive.org: MacOSLeopard.img
+2. Try to boot it like above with -cpu 970, or 970FX
+3. Observe early hang
+Additional information:
+```
+cpus[0] = 0x7f794b3e3040 0x7f794b3e5bc0
+cpus[1] = 0x7f794afe3ec0 0x7f794afe6a40
+Trying to write invalid spr 276 (0x114) at 00000000000b6634
+Trying to read invalid spr 277 (0x115) at 00000000000b6638
+Trying to read invalid spr 276 (0x114) at 00000000000b663c
+Trying to write invalid spr 277 (0x115) at 00000000000b6658
+Trying to write invalid spr 276 (0x114) at 00000000000b665c
+Trying to read invalid spr 276 (0x114) at 00000000000b6660
+Trying to write invalid spr 277 (0x115) at 00000000000b670c
+Trying to write invalid spr 276 (0x114) at 00000000000b6710
+Trying to read invalid spr 276 (0x114) at 00000000000b6714
+invalid/unsupported opcode: 00 - 00 - 00 - 00 (00000000) 0000000000000000
+Trying to write invalid spr 304 (0x130) at 0000000000003e14
+Trying to read invalid spr 304 (0x130) at 0000000000003e38
+Trying to write invalid spr 304 (0x130) at 0000000000003e14
+Trying to read invalid spr 304 (0x130) at 0000000000003e38
+Trying to write invalid spr 304 (0x130) at 0000000000003e14
+Trying to read invalid spr 304 (0x130) at 0000000000003e38
+Trying to write invalid spr 304 (0x130) at 0000000000003e14
+Trying to read invalid spr 304 (0x130) at 0000000000003e38
+Trying to write invalid spr 304 (0x130) at 0000000000003e14
+Trying to read invalid spr 304 (0x130) at 0000000000003e38
+Trying to write invalid spr 304 (0x130) at 0000000000003e14
+Trying to read invalid spr 304 (0x130) at 0000000000003e38
+Trying to write invalid spr 304 (0x130) at 0000000000003e14
+Trying to read invalid spr 304 (0x130) at 0000000000003e38
+Trying to read invalid spr 304 (0x130) at 0000000000003e38
+Trying to read invalid spr 304 (0x130) at 0000000000003e38
+invalid/unsupported opcode: 00 - 00 - 00 - 00 (00000000) 0000000000000008
+
+last lin repeats infinitely.
+```
+
+from my email  to qemu-ppc list:
+
+SPR 304 was already in target/ppc/cpu_init.c
+
+but sadly after adding those it still dies early :(
+
+I looked at
+
+IBM PowerPC 970FX RISC Microprocessor 11.6 SCOM Facility
+
+but whole thing a bit more complex than pair of regs.
+
+====
+
+11.6.1 Processor Core SCOM SPR Access Each processor (core) has two special purpose registers (SPRs) used to access the SCOM interface: SCOMC and SCOMD. SCOMC and SCOMD are both 64-bit read/write SPRs and are used for SCOM Control and SCOM Data respectively. The interface is implemented as a direct connection to the parallel-to-serial converter, which handles the arbitration between the core and service processor. 
+
+11.6.2 Operating System Protocol to Access SCOM SPRs In the PowerPC 970FX, SCOMC and SCOMD are complete operations. They do not require a software protocol in order to function properly except to disable external (asynchronous) interrupts. Software must check the error bits after performing an SCOMC to ensure that the command successfully completed. Table 11-14 Operating System Code to Access SCOM outlines a general software protocol for using these registers.
+
+====
+
+Low level asm init for OSX XNU kernel seems to live at
+
+https://github.com/apple-oss-distributions/xnu/blob/xnu-1228/osfmk/ppc/start.s
diff --git a/results/classifier/gemma3:12b/kernel/293 b/results/classifier/gemma3:12b/kernel/293
new file mode 100644
index 00000000..4e249936
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/293
@@ -0,0 +1,2 @@
+
+Qemu SPARC64 Panics on Sun Solaris 5.8 -  BOP_ALLOC failed
diff --git a/results/classifier/gemma3:12b/kernel/2933 b/results/classifier/gemma3:12b/kernel/2933
new file mode 100644
index 00000000..189ce3db
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2933
@@ -0,0 +1,23 @@
+
+After updating QEMU to 10.0, XNU kernel of OS X 10.8 throws kernel panic (type=0 divide error)
+Description of problem:
+Before updating to QEMU 10.0, my OS X 10.8 installation has worked pretty clear, but after QEMU update, XNU kernel now throws divide error during the boot.
+Steps to reproduce:
+1. Install OS X 10.8 on QEMU <10.0, for example 9.2.3.
+2. Update QEMU to 10.0 version
+3. Launch OS X
+Additional information:
+Screenshot of the issue:
+![Screenshot_2025-04-25_at_17.29.51](/uploads/b961258103a778ed8f12d036b3518eeb/Screenshot_2025-04-25_at_17.29.51.png)
+
+OpenCore config (not changed before update, so above suspicion):
+[config.plist](/uploads/4b80b60f9497e5ecd9237e4eeddcce8a/config.plist)
+
+Full OS X folder (without Installer.dmg):
+[OS_X_10.8.zip](/uploads/1af6150869495a8f196e18d18127011b/OS_X_10.8.zip)
+
+How I've done Installer.dmg:
+1. Go [here](https://updates.cdn-apple.com/2021/macos/031-0627-20210614-90D11F33-1A65-42DD-BBEA-E1D9F43A6B3F/InstallMacOSX.dmg)
+2. `xar -xf` to .pkg
+3. Show package contents to extracted .pkg
+4. Here it is: InstallESD.dmg, which I've renamed to Installer.dmg
diff --git a/results/classifier/gemma3:12b/kernel/2935 b/results/classifier/gemma3:12b/kernel/2935
new file mode 100644
index 00000000..2b253343
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2935
@@ -0,0 +1,25 @@
+
+strchrnul detection not suitable for macOS
+Description of problem:
+When qemu is compiled on macOS 15.4, targeting an earlier macOS version (e.g., 15.1), and then run on this earlier macOS version (15.1), it segfaults. This is because:
+
+- the meson test for strchrnul succeeds (the function is present in the library)
+- the strchrnul function is therefore used
+- but that function was introduced in the system's libc in 15.4 only
+
+The root cause for the bug is that the meson test for strchrnul does not include the appropriate header. Indeed, see the documentation for meson on compiler.has_function (https://mesonbuild.com/Compiler-properties.html#does-a-function-exist)
+
+> Note that, on macOS programs can be compiled targeting older macOS versions than the one that the program is compiled on. It can't be assumed that the OS version that is compiled on matches the OS version that the binary will run on.
+> 
+> Therefore when detecting function availability with compiler.has_function(), it is important to specify the correct header in the prefix argument.
+
+The correct fix would be, in qemu's meson.build, to change:
+
+`cc.has_function('strchrnul')`
+
+into `cc.has_function('strchrnul', prefix : '#include <string>')`
+
+This is the recommended best practice and would allow correct detection on all platforms, including macOS.
+Steps to reproduce:
+1. Install qemu from Homebrew, which is built on macOS 15.4
+2. Run it on a machine with macOS < 15.4
diff --git a/results/classifier/gemma3:12b/kernel/2953 b/results/classifier/gemma3:12b/kernel/2953
new file mode 100644
index 00000000..a010d6de
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2953
@@ -0,0 +1,67 @@
+
+"DMAR: DRHD: handling fault status reg 2" with vfio on kernel 6.13.11-200.fc41.x86_64, works with 6.13.9-200.fc41.x86_64
+Description of problem:
+Since kernel 6.13.11-200.fc41.x86_64, I cannot use VFIO to pass an NVIDIA GeForce GTX 1070 card to a Windows guest. The same setup works just fine in 6.13.9-200.fc41.x86_64. The issue symptoms are the same regardless if I use kernel command line arguments to isolate cpus or not.
+
+Symptoms:
+- qemu logs show:
+```
+2025-05-07T09:59:49.957891Z qemu-system-x86_64: vfio: Cannot reset device 0000:36:00.1, no available reset mechanism.
+2025-05-07T09:59:49.958444Z qemu-system-x86_64: vfio: Cannot reset device 0000:36:00.0, no available reset mechanism.
+2025-05-07T09:59:49.959119Z qemu-system-x86_64: vfio: Cannot reset device 0000:36:00.1, no available reset mechanism.
+2025-05-07T09:59:49.959635Z qemu-system-x86_64: vfio: Cannot reset device 0000:36:00.0, no available reset mechanism.
+```
+- in dmesg I see:
+```
+kernel: DMAR: DRHD: handling fault status reg 2
+kernel: DMAR: [INTR-REMAP] Request device [36:00.0] fault index 0x50 [fault reason 0x22] Present field in the IRTE entry is clear
+```
+- the VM hangs at boot (please see the notes below (*)).
+Steps to reproduce:
+Boot the same libvirt domain in kernel 6.13.9-200.fc41.x86_64 (works) and any other more recent kernel (>= 6.13.11-200.fc41.x86_64).
+Additional information:
+(*) Note that in a working kernel, the boot process is in any case finicky, and it shows these phases:
+1. tianocore logo shows, and one single cpu is fully utilized by the guest
+2. slowly, the loader find the Windows bootloader, and prints a message that it is loading and running it
+3. some time passes, while cpus seem idle
+4. finally the spinning wheel of the Windows bootloader appears
+
+Phase 1-3 can take anywhere from 0 to 60 seconds, in an apparently random manner.
+
+When running on the faulty kernels, it seems that the virtual machine gets stuck in phase 1, and I must use `virsh destroy` to interrupt it.
+
+lspci output:
+```
+-[0000:00]-+-00.0  Intel Corporation Tiger Lake-UP3/H35 4 cores Host Bridge/DRAM Registers
+           +-02.0  Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics]
+           +-04.0  Intel Corporation TigerLake-LP Dynamic Tuning Processor Participant
+           +-06.0-[01]----00.0  Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
+           +-07.0-[02-33]--
+           +-0a.0  Intel Corporation Tigerlake Telemetry Aggregator Driver
+           +-0d.0  Intel Corporation Tiger Lake-LP Thunderbolt 4 USB Controller
+           +-0d.2  Intel Corporation Tiger Lake-LP Thunderbolt 4 NHI #0
+           +-14.0  Intel Corporation Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller
+           +-14.2  Intel Corporation Tiger Lake-LP Shared SRAM
+           +-15.0  Intel Corporation Tiger Lake-LP Serial IO I2C Controller #0
+           +-15.1  Intel Corporation Tiger Lake-LP Serial IO I2C Controller #1
+           +-15.2  Intel Corporation Tiger Lake-LP Serial IO I2C Controller #2
+           +-16.0  Intel Corporation Tiger Lake-LP Management Engine Interface
+           +-1c.0-[34]----00.0  Intel Corporation Wi-Fi 6 AX200
+           +-1c.5-[35]----00.0  Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader
+           +-1d.0-[36]--+-00.0  NVIDIA Corporation GP104 [GeForce GTX 1070]
+           |            \-00.1  NVIDIA Corporation GP104 High Definition Audio Controller
+           +-1f.0  Intel Corporation Tiger Lake-LP LPC Controller
+           +-1f.3  Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller
+           +-1f.4  Intel Corporation Tiger Lake-LP SMBus Controller
+           \-1f.5  Intel Corporation Tiger Lake-LP SPI Controller
+```
+
+kernel command line arguments (optimized with cpu isolation):
+```
+intel_pstate=per_cpu_perf_limits rd.driver.blacklist=nouveau modprobe.blacklist=nouveau module_blacklist=nouveau default_hugepagesz=1G hugepagesz=1G hugepages=13 i2c_i801.disable_features=0x10 rd.driver.pre=vfio_pci,vfio,vfio_iommu_type1 vfio-pci.ids=10de:1b81,10de:10f0 modprobe.blacklist=xpad systemd.unit=multi-user.target systemd.wants=bluetooth.service isolcpus=domain,managed_irq,1-3,5-7 rcu_nocbs=1-3,5-7 irqaffinity=0,4 nospectre_v2
+```
+
+kernel command line arguments (without cpu isolation, same symptoms):
+```
+intel_pstate=per_cpu_perf_limits rd.driver.blacklist=nouveau modprobe.blacklist=nouveau module_blacklist=nouveau default_hugepagesz=1G hugepagesz=1G hugepages=13 rd.driver.pre=vfio_pci,vfio,vfio_iommu_type1 vfio-pci.ids=10de:1b81,10de:10f0 modprobe.blacklist=xpad systemd.unit=multi-user.target systemd.wants=bluetooth.service
+```
diff --git a/results/classifier/gemma3:12b/kernel/2978 b/results/classifier/gemma3:12b/kernel/2978
new file mode 100644
index 00000000..8b9c7c7e
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2978
@@ -0,0 +1,24 @@
+
+Qemu assertion issue
+Description of problem:
+This issue is **not caused by my OS**, as it runs perfectly under VMware and other emulators.
+
+However, when using QEMU, the emulator sometimes randomly **crashes or aborts** during boot or early execution. The crash is **inconsistent** — sometimes it runs, sometimes it fails immediately.
+
+QEMU fails with an **assertion failure** in `qemu_mutex_lock_iothread_impl`
+Steps to reproduce:
+Unfortunately, I do not know exactly what causes this issue. It may be specific to my system or configuration.
+
+1. 
+2.
+Additional information:
+Qemu stdout:
+
+```
+ERROR:system/cpus.c:504:qemu_mutex_lock_iothread_impl: assertion failed: (!qemu_mutex_iothread_locked()) Bail out! ERROR:system/cpus.c:504:qemu_mutex_lock_iothread_impl: assertion failed: (!qemu_mutex_iothread_locked()) ./run: line 3: 3544 Aborted (core dumped)
+```
+
+Command line:
+```
+ qemu-system-x86_64 -debugcon file:OxizeOS.log -drive file=output/OxizeOS.hdd,format=raw -serial stdio
+```
diff --git a/results/classifier/gemma3:12b/kernel/2983 b/results/classifier/gemma3:12b/kernel/2983
new file mode 100644
index 00000000..cbcb1d44
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/2983
@@ -0,0 +1,116 @@
+
+qemu-system-riscv64 randomly  turns MPP bits to 0 in the mstatus word.
+Description of problem:
+ToyOs runs the kernel in machine mode and user programs in user mode.  This is specific choice on my part to make sure the kernel code runs with machine address and user code runs with virtual addresses.  This is different than Linux, NetBSD or other OSes I know that run the kernel in supervisor mode. When running in machine mode and running kernel code, I get a a trap.  My error message looks like this:
+
+PANIC: Unexpected trap from machine mode!
+  mepc = 0x800002a8, mcause = 2, mtval=0xe78023 mstatus=0xa00000080
+
+Notice, the mstatus bits show the trap was due to a privileged instruction being run by a "user" mode instruction.   In the "assignment version" used for the above, no user code was run.  It was just multiple threads running in machine mode.   Also, the trap function is run with the MPP bits of 0, so even trying to recover from this trap can't be done as trying to manipulate the mstatus will generate yet again another trap to the same place and still running in "user" mode.
+
+This change does not happen on every run.  It happens more consistently recently when trying to debug the kernel with gdb.  This must be a race condition somewhere.
+
+The kernel is written in C++ with C libraries.
+Steps to reproduce:
+1.  You will need to have access to my kernel and possibly my code base.  This is a code base that I want to stay at WWU (Western Washington University).
+2.  Give the command "bmake run".  It often completes with no problems, but if you run it often enough it will generate this trap from "machine mode".   The example above had four good runs with no errors and on the fifth run it blew up.  There is not guaranteed way to get this to have a problem.   (This is why I haven't reported it before, I kept trying to get a minimal code set that had the problem, but I couldn't do it.)
+Additional information:
+This is a bug has been a problem for several years.  It didn't strike very often on some versions of qemu.  I think one of the 7.x.x versions happened not too often.  But with newer, faster machines and a different version of Linux, this bug has become a big problem for me and my students.
+
+Here is a sample bad run:  (All compilation has been done before so this just makes sure everything is up-to-date and then runs qemu-system-riscv64.  In this assignment, no user mode code is being run.  Threads are all running in machine mode for the entire time.  I am getting clock interrupts on the CPU, but that does not appear to be the problem.)
+
+$ bmake run
+if ! [ -e toolbin ] ; then mkdir toolbin ; fi;
+(cd tools; bmake install)
+(cd toy_fs; bmake)
+`toyfs' is up to date.
+(cd mkdep; bmake)
+`mkdep' is up to date.
+(cd toy_fs; bmake install)
+(cd mkdep; bmake install)
+Making in /home/phil/447/csci447_s25/lib
+Making in /home/phil/447/csci447_s25/kernel
+`DISK' is up to date.
+qemu-system-riscv64 -machine virt -bios none -m 1G -smp 1 -nographic -global virtio-mmio.force-legacy=false -drive file=DISK,if=none,format=raw,id=x0 -device virtio-blk-device,drive=x0,bus=virtio-mmio-bus.0 -kernel kernel/kernel -gdb tcp::27277
+Initializing scheduler ...
+Initializing frame set... 
+Initializing thread set ...
+Initializing process set ...
+Initializing fcb set ...
+Initializing OpenFile set ...
+Initializing pipe set ...
+Initializing vertio ...
+Initializing filesystem ...
+Starting os_main ...
+PANIC: Unexpected trap from machine mode!
+  mepc = 0x800002a8, mcause = 2, mtval=0xe78023 mstatus=0xa00000080
+attach with gdb!
+QEMU: Terminated
+
+$ riscv64-unknown-elf-addr2line -e kernel/kernel 0x800002a8
+/home/phil/447/csci447_s25/kernel/runtime.S:350
+
+And that instruction turns out to be "mret", the return from the clock interrupt.
+
+The following is a error free run of this.
+
+$ bmake run
+if ! [ -e toolbin ] ; then mkdir toolbin ; fi;
+(cd tools; bmake install)
+(cd toy_fs; bmake)
+`toyfs' is up to date.
+(cd mkdep; bmake)
+`mkdep' is up to date.
+(cd toy_fs; bmake install)
+(cd mkdep; bmake install)
+Making in /home/phil/447/csci447_s25/lib
+Making in /home/phil/447/csci447_s25/kernel
+`DISK' is up to date.
+qemu-system-riscv64 -machine virt -bios none -m 1G -smp 1 -nographic -global virtio-mmio.force-legacy=false -drive file=DISK,if=none,format=raw,id=x0 -device virtio-blk-device,drive=x0,bus=virtio-mmio-bus.0 -kernel kernel/kernel -gdb tcp::27277
+Initializing scheduler ...
+Initializing frame set... 
+Initializing thread set ...
+Initializing process set ...
+Initializing fcb set ...
+Initializing OpenFile set ...
+Initializing pipe set ...
+Initializing vertio ...
+Initializing filesystem ...
+Starting os_main ...
+
+Welcome to Toy OS, hartid = 0
+Assignment 3 ...
+
+********** Frame Tester **********
+1.3.2.4.5.6.7.8.9.10.12.11.13.14.15.16.17.18.19.20.21.22.23.24.25.26.27.28.29.30.31.32.33.34.35.36.37.38.39.40.41.42.43.44.45.46.47.48.49.50.51.52.53.54.55.56.57.58.59.60.61.62.63.64.65.66.67.68.69.70.71.72.73.74.75.76.77.78.79.80.81.82.83.85.84.87.86.88.89.91.92.90.93.94.95.96.97.98.99.100.101.102.103.104.105.106.107.108.109.110.111.113.112.114.115.116.117.119.118.120.121.122.123.124.125.126.127.128.129.130.131.132.133.134.135.136.137.138.139.140.161.162.163.164.166.165.167.168.169.170.171.172.173.174.175.177.178.176.179.180.181.182.183.184.185.186.187.188.189.190.191.194.193.192.195.197.196.198.200.199.201.202.203.204.206.205.207.209.208.210.211.212.214.213.215.216.217.218.219.220.221.222.223.224.225.226.227.228.230.231.229.232.233.234.235.236.237.238.239.240.241.242.243.244.245.246.247.248.249.250.252.253.251.254.255.256.257.258.259.260.261.262.263.264.265.266.267.268.269.270.271.273.272.274.275.276.277.278.279.280.281.282.283.284.285.286.287.288.289.290.291.292.293.294.295.296.297.298.299.300.301.302.303.304.305.306.308.307.309.310.311.312.313.314.315.316.317.318.319.320.341.342.343.344.345.346.347.348.349.350.351.353.352.354.356.355.357.358.359.360.361.362.363.364.365.366.367.368.369.370.371.372.373.374.375.376.377.378.379.380.382.381.383.384.385.386.387.388.389.390.391.392.394.395.393.396.397.398.399.400.401.402.403.404.405.406.407.409.408.410.411.412.413.414.415.416.417.418.420.419.421.422.423.425.426.424.427.428.429.430.432.431.433.434.435.436.437.438.439.440.441.442.443.444.445.446.447.448.449.450.451.452.453.455.454.457.456.458.459.460.461.462.463.464.465.466.467.468.469.470.471.472.473.474.475.476.477.478.479.480.481.482.483.484.485.486.487.488.489.490.491.492.493.494.495.496.497.498.499.500.521.523.522.524.525.526.528.527.529.530.531.532.533.534.535.536.537.538.539.540.542.544.543.541.545.546.548.547.549.551.550.553.552.555.554.557.556.559.558.560.561.562.563.564.565.566.567.568.569.570.571.572.573.574.575.576.577.578.579.580.581.582.583.584.585.586.587.588.589.590.591.592.593.594.595.596.597.598.599.600.601.602.603.604.605.606.607.608.609.610.611.612.613.614.615.616.617.618.619.620.621.622.623.624.625.626.627.628.629.630.631.632.633.634.635.636.637.638.639.640.641.642.643.644.645.646.647.648.649.650.651.652.653.654.655.656.657.658.659.660.661.662.663.664.665.666.667.668.669.670.671.672.673.675.674.676.677.678.679.680.701.702.704.703.705.706.707.708.709.711.710.712.713.714.715.716.717.718.719.720.723.722.721.724.725.727.726.728.729.730.731.732.733.734.735.737.736.738.739.741.740.742.744.743.746.747.745.748.749.750.751.752.753.754.756.755.757.758.759.761.760.762.763.764.765.766.767.768.769.770.771.772.773.774.775.776.777.778.780.779.781.782.783.784.785.786.787.788.789.790.791.792.793.794.795.797.796.798.799.800.801.802.803.804.805.806.807.808.809.810.811.812.813.814.815.816.817.818.819.820.821.822.823.825.824.826.827.828.829.830.831.832.833.834.835.836.837.838.839.840.841.842.843.844.845.846.847.848.849.850.851.852.853.854.855.856.857.858.859.860.882.881.884.883.885.886.888.887.890.889.891.892.893.894.895.896.897.898.899.901.900.902.903.904.905.906.907.908.909.910.911.913.912.914.915.916.917.918.919.920.921.922.923.924.925.926.928.927.929.930.931.932.933.934.935.936.937.939.938.940.941.942.943.944.945.946.947.948.949.950.951.952.953.954.955.956.957.958.959.961.960.962.963.964.965.966.967.968.969.970.971.972.973.974.975.976.977.978.979.980.981.982.983.984.985.986.987.988.989.990.991.992.993.994.995.996.997.998.999.1000.1001.1002.1003.1004.1005.1006.1008.1007.1009.1010.1011.1012.1014.1013.1015.1016.1017.1018.1019.1020.1021.1022.1023.1024.1025.1026.1027.1028.1029.1030.1031.1032.1033.1034.1035.1036.1037.1038.1039.1040.1061.1062.1063.1065.1064.1066.1069.1067.1068.1070.1071.1072.1073.1074.1075.1076.1077.1078.1079.1080.1082.1081.1084.1083.1085.1086.1087.1088.1089.1090.1091.1093.1092.1094.1095.1097.1096.1098.1099.1100.1101.1102.1103.1104.1105.1106.1107.1109.1108.1110.1111.1112.1113.1114.1115.1117.1116.1118.1119.1120.1121.1122.1123.1124.1125.1126.1127.1128.1129.1130.1131.1132.1133.1134.1135.1136.1137.1138.1139.1140.1141.1142.1143.1144.1145.1146.1147.1148.1149.1150.1151.1152.1153.1154.1155.1156.1157.1158.1159.1160.1161.1162.1163.1164.1165.1166.1167.1168.1169.1170.1172.1171.1173.1174.1175.1176.1177.1178.1179.1180.1181.1182.1183.1184.1185.1186.1187.1188.1189.1190.1191.1192.1193.1194.1195.1196.1197.1198.1199.1201.1200.1202.1203.1204.1205.1207.1206.1208.1209.1210.1211.1212.1213.1214.1215.1216.1217.1218.1219.1220.1241.1242.1244.1243.1245.1246.1247.1248.1249.1251.1250.1252.1253.1254.1255.1256.1257.1258.1259.1260.1261.1262.1263.1264.1265.1266.1267.1269.1268.1270.1272.1271.1274.1273.1275.1276.1277.1278.1279.1280.1281.1283.1282.1284.1285.1287.1286.1288.1290.1289.1291.1292.1293.1294.1295.1296.1297.1299.1298.1300.1301.1302.1303.1304.1305.1306.1307.1308.1309.1310.1311.1312.1313.1315.1314.1316.1317.1318.1319.1320.1321.1322.1323.1324.1325.1326.1327.1328.1329.1330.1331.1332.1333.1335.1334.1336.1337.1338.1339.1340.1341.1342.1343.1344.1345.1346.1347.1348.1349.1350.1351.1352.1353.1354.1355.1356.1357.1358.1360.1361.1359.1362.1364.1363.1365.1366.1367.1370.1369.1368.1371.1372.1373.1375.1374.1376.1377.1378.1379.1380.1381.1382.1383.1384.1385.1386.1387.1388.1389.1390.1391.1392.1393.1394.1395.1396.1397.1398.1400.1401.1419.1422.1423.1424.1426.1425.1427.1428.1429.1431.1430.1432.1434.1435.1433.1437.1436.1438.1440.1439.1441.1447.1442.1443.1444.1445.1446.1448.1449.1450.1452.1453.1451.1454.1455.1456.1457.1459.1458.1461.1460.1462.1463.1464.1465.1466.1467.1468.1469.1470.1471.1472.1473.1474.1475.1476.1477.1478.1479.1480.1481.1482.1483.1484.1486.1485.1487.1488.1489.1490.1491.1492.1493.1494.1495.1496.1498.1497.1499.1500.1501.1502.1503.1504.1505.1506.1507.1508.1509.1510.1511.1512.1513.1514.1515.1516.1517.1519.1518.1520.1521.1522.1523.1524.1525.1526.1527.1528.1529.1530.1531.1532.1533.1534.1535.1536.1537.1538.1539.1540.1541.1542.1543.1544.1545.1547.1546.1548.1549.1550.1551.1553.1552.1554.1555.1556.1557.1558.1559.1560.1561.1562.1563.1564.1565.1566.1567.1568.1569.1570.1571.1572.1573.1574.1575.1576.1577.1578.1579.1581.1600.1602.1603.1604.1605.1607.1606.1608.1609.1610.1612.1611.1613.1614.1616.1615.1617.1618.1619.1622.1621.1620.1623.1624.1625.1626.1627.1628.1629.1630.1631.1632.1633.1635.1634.1636.1637.1638.1639.1640.1641.1642.1643.1644.1646.1645.1647.1648.1650.1649.1652.1651.1653.1654.1655.1656.1657.1658.1659.1660.1661.1663.1662.1664.1665.1666.1667.1668.1669.1670.1671.1672.1673.1674.1675.1676.1677.1678.1679.1680.1681.1682.1683.1685.1684.1686.1687.1688.1689.1691.1690.1692.1693.1694.1695.1696.1698.1697.1699.1700.1701.1702.1703.1704.1705.1706.1707.1708.1709.1710.1711.1713.1712.1714.1715.1717.1716.1718.1719.1720.1721.1722.1723.1724.1725.1726.1727.1728.1729.1730.1731.1732.1733.1734.1735.1736.1737.1738.1739.1740.1741.1742.1743.1744.1745.1746.1747.1748.1749.1751.1750.1752.1753.1754.1755.1756.1757.1758.1759.1762.1780.1781.1784.1785.1783.1787.1788.1786.1789.1790.1791.1792.1794.1793.1795.1796.1799.1797.1800.1798.
+Frame  0, used 0x  Frame  1, used 0x  Frame  2, used 0x  
+Frame  3, used 438x  Frame  4, used 435x  Frame  5, used 429x  
+Frame  6, used 420x  Frame  7, used 414x  Frame  8, used 407x  
+Frame  9, used 396x  Frame 10, used 391x  Frame 11, used 386x  
+Frame 12, used 374x  Frame 13, used 372x  Frame 14, used 367x  
+Frame 15, used 361x  Frame 16, used 353x  Frame 17, used 345x  
+Frame 18, used 342x  Frame 19, used 335x  Frame 20, used 330x  
+Frame 21, used 329x  Frame 22, used 325x  Frame 23, used 319x  
+Frame 24, used 271x  Frame 25, used 262x  Frame 26, used 255x  
+Frame 27, used 141x  Frame 28, used 108x  Frame 29, used 95x  
+**********  Test Done   **********
+
+********** Thread Tester **********
+3.4.5.6.7.8.9.10.11.12.13.14.15.16.17.18.19.2.22.20.30.31.24.21.23.25.26.32.27.33.39.40.41.28.29.35.34.36.42.44.48.49.50.37.51.38.45.46.52.55.57.43.58.60.53.61.62.56.63.65.67.68.47.70.71.64.72.73.74.69.54.77.78.59.81.82.75.83.76.85.79.86.89.91.92.84.93.66.87.80.94.96.98.101.102.103.95.88.104.97.99.105.108.110.111.112.113.100.114.107.115.109.117.119.120.122.106.116.124.125.90.126.129.130.131.132.133.127.134.135.128.136.138.139.141.142.143.144.123.145.140.146.148.149.151.153.152.154.118.147.156.121.159.160.161.162.163.157.164.150.137.166.169.170.171.172.158.174.167.175.155.176.178.173.181.182.168.183.184.179.185.165.187.177.188.189.186.180.190.192.191.193.195.196.197.194.198.199.200.201.
+**********   Test Done   **********
+
+********** Process Tester **********
+5.6.7.8.9.10.2.3.11.4.23.22.24.19.21.12.13.14.25.26.29.28.15.16.17.30.18.20.34.35.38.39.32.40.31.27.41.33.43.44.48.49.50.42.36.51.37.45.52.54.56.58.59.60.61.46.47.53.62.57.67.68.69.70.71.55.63.64.65.73.76.78.79.72.81.66.74.82.75.83.86.88.90.91.77.84.92.85.93.80.95.97.99.101.87.102.94.89.103.96.98.100.108.112.104.113.105.114.106.107.109.115.110.122.123.124.116.111.117.118.119.125.120.132.134.121.126.127.135.130.128.136.129.139.133.131.145.138.137.142.140.143.146.141.155.147.148.144.149.152.150.151.153.156.157.158.154.162.159.160.161.163.166.164.167.165.168.172.170.169.180.173.176.171.174.181.175.177.178.179.188.189.182.185.183.190.186.184.187.191.193.194.192.195.196.197.198.199.200.201.
+**********   Test Done    **********
+
+********** OpenFile Tester **********
+3.4.5.2.8.6.9.7.11.10.13.12.14.16.15.17.18.19.21.20.22.23.24.26.25.27.28.29.31.30.32.33.34.36.35.37.39.38.40.41.42.43.45.44.47.46.49.48.50.52.51.53.55.54.56.58.57.59.60.62.61.63.65.66.64.67.69.68.70.71.72.74.73.76.77.75.78.80.79.81.82.83.85.84.86.87.88.90.89.91.92.94.95.93.97.96.98.99.100.102.101.103.105.104.106.108.107.109.111.110.113.112.115.114.116.117.118.119.120.121.122.123.124.125.126.127.128.129.130.131.132.133.134.135.136.138.137.139.140.141.142.143.144.145.146.147.148.149.150.152.151.153.154.155.156.157.158.159.160.161.162.163.164.166.165.167.168.169.170.172.171.173.174.176.175.177.178.180.179.181.183.182.185.184.186.187.188.189.190.191.192.194.193.195.197.196.198.199.200.201.
+**********   Test Done   **********
+
+********** FileControlBlock Tester **********
+2.3.4.5.6.7.8.9.10.2!W1.3!W2.5!W3.4!W4.6!W5.7!W6.8!W7.9!W8.10!F12.2!12.3!W1.12.5!W2.12.W3.12.12.12.12.12.10!4!W4.6!W5.7!9!W6.W7.8!W8.F12.12.12.20.12.12.12.20.12.12.12.20.20.20.20.20.20.20.
+**********   Test Done   **********
+
+All Assignment 3 tests done.
+
+I call this a "heisenbug" as I never know when it will strike and stop ToyOS from running.
diff --git a/results/classifier/gemma3:12b/kernel/311 b/results/classifier/gemma3:12b/kernel/311
new file mode 100644
index 00000000..c95fa2e1
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/311
@@ -0,0 +1,2 @@
+
+qemu user mode: rt signals not implemented for sparc guests
diff --git a/results/classifier/gemma3:12b/kernel/314 b/results/classifier/gemma3:12b/kernel/314
new file mode 100644
index 00000000..23dd2ed3
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/314
@@ -0,0 +1,2 @@
+
+qemu-user vm86() segfaults handling interrupt with ss:sp in same page as cs:ip
diff --git a/results/classifier/gemma3:12b/kernel/318 b/results/classifier/gemma3:12b/kernel/318
new file mode 100644
index 00000000..b25802b2
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/318
@@ -0,0 +1,2 @@
+
+QEMU crash after a QuickBASIC program integer overflow
diff --git a/results/classifier/gemma3:12b/kernel/333 b/results/classifier/gemma3:12b/kernel/333
new file mode 100644
index 00000000..ef06f351
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/333
@@ -0,0 +1,2 @@
+
+random errors on aarch64 when executing __aarch64_cas8_acq_rel
diff --git a/results/classifier/gemma3:12b/kernel/340 b/results/classifier/gemma3:12b/kernel/340
new file mode 100644
index 00000000..c3917a69
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/340
@@ -0,0 +1,2 @@
+
+qemu: uncaught target signal 6 (Aborted) - core dumped on Apple Silicon M1 arm64
diff --git a/results/classifier/gemma3:12b/kernel/355 b/results/classifier/gemma3:12b/kernel/355
new file mode 100644
index 00000000..8b93015b
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/355
@@ -0,0 +1,2 @@
+
+A possible divide by zero bug in get_whole_cluster
diff --git a/results/classifier/gemma3:12b/kernel/358 b/results/classifier/gemma3:12b/kernel/358
new file mode 100644
index 00000000..3662c23f
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/358
@@ -0,0 +1,2 @@
+
+qemu-user deadlocks when forked in a multithreaded process
diff --git a/results/classifier/gemma3:12b/kernel/382 b/results/classifier/gemma3:12b/kernel/382
new file mode 100644
index 00000000..f46986ad
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/382
@@ -0,0 +1,2 @@
+
+target/i386/seg_helper.c: 16-bit TSS struct format wrong?
diff --git a/results/classifier/gemma3:12b/kernel/394 b/results/classifier/gemma3:12b/kernel/394
new file mode 100644
index 00000000..37331859
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/394
@@ -0,0 +1,2 @@
+
+Windows 7 crashing due to PAGE_FAULT_IN_NONPAGED_AREA
diff --git a/results/classifier/gemma3:12b/kernel/417 b/results/classifier/gemma3:12b/kernel/417
new file mode 100644
index 00000000..64a2581a
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/417
@@ -0,0 +1,2 @@
+
+allow qemu_thread_create to return with error
diff --git a/results/classifier/gemma3:12b/kernel/419 b/results/classifier/gemma3:12b/kernel/419
new file mode 100644
index 00000000..59cd74aa
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/419
@@ -0,0 +1,2 @@
+
+bsd-user dumps core for all binaries emulated
diff --git a/results/classifier/gemma3:12b/kernel/448 b/results/classifier/gemma3:12b/kernel/448
new file mode 100644
index 00000000..5da652ab
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/448
@@ -0,0 +1,2 @@
+
+raspi0 machine leads to kernel panic of latest raspberry pi os kernel
diff --git a/results/classifier/gemma3:12b/kernel/456 b/results/classifier/gemma3:12b/kernel/456
new file mode 100644
index 00000000..3e30dd07
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/456
@@ -0,0 +1,30 @@
+
+Qemu User (x86_64) Hangs after futex function not implemented error
+Description of problem:
+Qemu User hangs on futex call with the following last strace
+```
+futex(0x0000004001a01654,FUTEX_PRIVATE_FLAG|FUTEX_UNLOCK_PI,0,NULL,NULL,0) = -1 errno=38 (Function not implemented)
+```
+This is the last call until giving a SIGINT with CTRL + C where the following strace is output
+```
+futex(0x00000040b0085180,FUTEX_PRIVATE_FLAG|FUTEX_WAIT,2,NULL,NULL,0) = -1 errno=4 (Interrupted system call)
+--- SIGINT {si_signo=SIGINT, si_code=SI_KERNEL, si_pid=0, si_uid=0} ---
+
+```
+Steps to reproduce:
+1. Install steamcmd https://developer.valvesoftware.com/wiki/SteamCMD
+2. In the steamcmd shell install Valheim dedicated server with `app_update 896660`
+3. Navigate to the downloaded app `cd ~/Steam/steamapps/common/Valheim\ dedicated\ server/`
+4. Run `qemu-x86_64 valheim_server.x86_64`
+5. The process hangs as per description.
+Additional information:
+The issue was originally encountered on a raspberry pi ARM64 host using the ubuntu 5.2.0 version of qemu. Installed cross libararies:
+* libc6-amd64-cross
+* libgcc-s1-amd64-cross
+
+It was then replicated on the x86 host fedora with a build of the qemu master branch.
+The full qemu -strace output is provided below
+[qemu_strace_output.log](/uploads/96e0e31b1e63191a94d73f05023c5173/qemu_strace_output.log)
+
+The expected output found when running `strace ./valheim_server.x86_64` without qemu on the x86_64 host is attached below
+[expected_output.log](/uploads/b3b25618103de8a3b9c0ef227bbffc9c/expected_output.log)
diff --git a/results/classifier/gemma3:12b/kernel/474 b/results/classifier/gemma3:12b/kernel/474
new file mode 100644
index 00000000..14cf3722
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/474
@@ -0,0 +1,31 @@
+
+[build][git]Build process stops while linking qemu-aarch64_be in util/async.c:426
+Description of problem:
+Looks like this is a followup of bug #463. Even if this bug is fixed, build process breaks later.
+
+This time, build process is stop while processing linking qemu-aarch64_be, really late at step 6492/9511.
+
+Error log start with:
+
+```
+[6492/9511] Linking target qemu-aarch64_be
+FAILED: qemu-aarch64_be 
+```
+
+And later I can read:
+
+```
+/usr/bin/ld: libqemuutil.a(util_async.c.o): in function `aio_setup_linux_io_uring':
+/build/qemu-git/src/qemu/build-full/../util/async.c:421: undefined reference to `luring_init'
+/usr/bin/ld: /build/qemu-git/src/qemu/build-full/../util/async.c:426: undefined reference to `luring_attach_aio_context'
+/usr/bin/ld: libqemuutil.a(util_async.c.o): in function `aio_ctx_finalize':
+/build/qemu-git/src/qemu/build-full/../util/async.c:334: undefined reference to `luring_detach_aio_context'
+/usr/bin/ld: /build/qemu-git/src/qemu/build-full/../util/async.c:335: undefined reference to `luring_cleanup'
+collect2: error: ld returned 1 exit status
+```
+Steps to reproduce:
+1. Grab source code at commit bd38ae2
+2. use these configure options: --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libexecdir=/usr/lib/qemu --smbd=/usr/bin/smbd --enable-modules --enable-sdl --disable-werror --enable-vhost-user --enable-slirp=system --enable-xfsctl --audio-drv-list="pa alsa sdl"
+3. Launch build process.
+Additional information:
+Adding building process log.[qemu-git-13_6.0.0.r2577.gbd38ae26ce-1-x86_64-build.log](/uploads/419d2323799aad3a0f4a7719ce123f35/qemu-git-13_6.0.0.r2577.gbd38ae26ce-1-x86_64-build.log)
diff --git a/results/classifier/gemma3:12b/kernel/479 b/results/classifier/gemma3:12b/kernel/479
new file mode 100644
index 00000000..6c6f5308
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/479
@@ -0,0 +1,13 @@
+
+qemu-6.0.0:  Assertion 'p_rcu_reader->depth != 0' failed
+Description of problem:
+assertion failure:
+```
+qemu-system-aarch64: /home/aileen/Downloads/qemu-6.0.0/include/qemu/rcu.h:93: rcu_read_unlock: Assertion `p_rcu_reader->depth != 0' failed.
+```
+Steps to reproduce:
+1. You cannot
+2.   unless I give
+3.   you the ELF file.
+Additional information:
+
diff --git a/results/classifier/gemma3:12b/kernel/503 b/results/classifier/gemma3:12b/kernel/503
new file mode 100644
index 00000000..1f158074
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/503
@@ -0,0 +1,2 @@
+
+QEMU aarch64 Segmentation fault on Mac OSX, machine raspi3
diff --git a/results/classifier/gemma3:12b/kernel/51 b/results/classifier/gemma3:12b/kernel/51
new file mode 100644
index 00000000..4e8d87b4
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/51
@@ -0,0 +1,2 @@
+
+Linux kernel oops on Malta board while accessing pflash
diff --git a/results/classifier/gemma3:12b/kernel/52 b/results/classifier/gemma3:12b/kernel/52
new file mode 100644
index 00000000..1746f518
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/52
@@ -0,0 +1,2 @@
+
+PowerPC64: tlbivax does not work for addresses above 4G
diff --git a/results/classifier/gemma3:12b/kernel/520 b/results/classifier/gemma3:12b/kernel/520
new file mode 100644
index 00000000..df05dffe
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/520
@@ -0,0 +1,34 @@
+
+qemu-ga fsfreeze crashes the kernel
+Description of problem:
+Hello,
+
+Still required your attention, duplicate from:
+https://bugs.launchpad.net/bugs/1807073
+https://bugs.launchpad.net/bugs/1813045
+
+We use mainly Cloudlinux, Debian and Centos.
+We experienced many crashes on our qemu instances based on Cloudlinux during a snapshot.
+The issue is not related to CloudLinux directly, but to Qemu agent, which does not freeze the file system(s) correctly. What is actually happening:
+
+When VM backup is invoked, Qemu agent freezes the file systems, so no single change will be made during the backup. But Qemu agent does not respect the loop* devices in freezing order (we have checked its sources), which leads to the next situation:
+1) freeze loopback fs
+              ---> send async reqs to loopback thread
+2) freeze main fs
+3) loopback thread wakes up and trying to write data to the main fs, which is still frozen, and this finally leads to the hung task and kernel crash.
+
+Moreover, a lot of Proxmox users are complaining about the issue as well:
+https://forum.proxmox.com/threads/error-vm-100-qmp-command-guest-fsfreeze-thaw-failed-got-timeout.68082/
+https://forum.proxmox.com/threads/problem-with-fsfreeze-freeze-and-qemu-guest-agent.65707/
+Steps to reproduce:
+1. Manually start backup for the VM with qemu-agent enabled.
+2. The backup process stuck at "INFO: issuing guest-agent 'fs-freeze' command"
+3. The VM become unavailable, you can only unlock it and force reset.
+Additional information:
+/var/log/messages logs:  
+Aug  6 21:54:00 cpanel qemu-ga: info: guest-ping called  
+Aug  6 21:54:01 cpanel qemu-ga: info: guest-fsfreeze called  
+Aug  6 21:54:01 cpanel qemu-ga: info: executing fsfreeze hook with arg 'freeze'  
+
+
+after this the VM becomes completely unavailable.
diff --git a/results/classifier/gemma3:12b/kernel/538808 b/results/classifier/gemma3:12b/kernel/538808
new file mode 100644
index 00000000..da711647
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/538808
@@ -0,0 +1,12 @@
+
+qemu-system-x86_64 0.12.2 crashes with -m 967 under Windows
+
+qemu 0.12.2 and 0.12.3 exit silently under Windows XP when using an -m value higher than 967.  Any value below 967 works fine.  Affects both qemu.exe and qemu-system-x86_64.exe (the only binaries currently available).
+qemu 0.12.3 under Linux (Ubuntu 8.10) works fine.
+Version 0.9.0 for Windows does not have this problem.  I do not have any other binaries to test.
+
+Command used:
+qemu-system-x86_64 -L . -m 967 -hda linux.img -localtime -M pc
+
+There is plenty of available RAM on the host PC (see attached systeminfo).
+Not sure what debugging options to use, but will attach whatever is necessary.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/546458 b/results/classifier/gemma3:12b/kernel/546458
new file mode 100644
index 00000000..e267b04d
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/546458
@@ -0,0 +1,48 @@
+
+kernel NULL pointer in -virtual (-server) kernel
+
+When stress testing eucalyptus we have run into this oops inside VMs
+[   82.907577] BUG: unable to handle kernel NULL pointer dereference at 0000000000000358^M
+[   82.908842] IP: [<ffffffff813982e8>] sym_int_sir+0x2a8/0x750^M
+[   82.909773] PGD 0 ^M
+[   82.910110] Thread overran stack, or stack corrupted^M
+[   82.910870] Oops: 0000 [#1] SMP ^M
+[   82.911407] last sysfs file: /sys/devices/virtual/block/ram9/uevent^M
+
+We launched 18 instances, 2 of them failed this way.  The instances run with 192M of memory.  With 6 VM launches on a single node all at the same time the host is under heavy load.
+
+This occurred in 20100323 lucid x86_64 uec-image instance.
+
+ProblemType: Bug
+AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
+AplayDevices: Error: [Errno 2] No such file or directory
+Architecture: amd64
+ArecordDevices: Error: [Errno 2] No such file or directory
+CurrentDmesg:
+ 
+Date: Wed Mar 24 22:06:32 2010
+DistroRelease: Ubuntu 10.04
+Frequency: Once a day.
+Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+MachineType: Bochs Bochs
+Package: linux-image-2.6.32-16-virtual 2.6.32-16.25
+PciMultimedia:
+ 
+ProcCmdLine: root=/dev/sda1 console=ttyS0
+ProcEnviron:
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
+ProcVersionSignature: User Name 2.6.32-16.25-server
+Regression: No
+Reproducible: No
+SourcePackage: linux
+TestedUpstream: No
+Uname: Linux 2.6.32-16-server x86_64
+dmi.bios.date: 01/01/2007
+dmi.bios.vendor: Bochs
+dmi.bios.version: Bochs
+dmi.chassis.type: 1
+dmi.chassis.vendor: Bochs
+dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
+dmi.product.name: Bochs
+dmi.sys.vendor: Bochs
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/568228 b/results/classifier/gemma3:12b/kernel/568228
new file mode 100644
index 00000000..f528cdc0
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/568228
@@ -0,0 +1,259 @@
+
+/home/qemu-0.12.3/tcg/tcg.c:1367: tcg fatal error
+
+I get the following error each time I start emulation in QEMU 0.12.3 on a Sun SunFire 280R running Debian Lenny 5.03 for Sparc64:
+
+/home/qemu-0.12.3/tcg/tcg.c:1367: tcg fatal error
+
+I had the same problem in Qemu 0.11.1.
+
+Here are informations about my system, I am not a programmer so I don't know what information to give, if you need more info just ask me:
+
+sunfire:/home# uname -a
+Linux sunfire 2.6.26 #1 Thu Apr 8 17:09:17 EDT 2010 sparc64 GNU/Linux
+sunfire:/home# dmesg
+nges:
+[    0.000000]   Normal          0 ->   130933
+[    0.000000] Movable zone start PFN for each node
+[    0.000000] early_node_map[7] active PFN ranges
+[    0.000000]     0:        0 ->   129023
+[    0.000000]     0:   129024 ->   130666
+[    0.000000]     0:   130796 ->   130803
+[    0.000000]     0:   130805 ->   130815
+[    0.000000]     0:   130818 ->   130826
+[    0.000000]     0:   130828 ->   130916
+[    0.000000]     0:   130919 ->   130933
+[    0.000000] On node 0 totalpages: 130792
+[    0.000000]   Normal zone: 896 pages used for memmap
+[    0.000000]   Normal zone: 0 pages reserved
+[    0.000000]   Normal zone: 129896 pages, LIFO batch:15
+[    0.000000]   Movable zone: 0 pages used for memmap
+[    0.000000] Booting Linux...
+[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 129896
+[    0.000000] Kernel command line: root=/dev/sdb2 ro
+[    0.000000] PID hash table entries: 4096 (order: 12, 32768 bytes)
+[    0.000000] clocksource: mult[c80000] shift[16]
+[    0.000000] clockevent: mult[147ae14] shift[32]
+[  380.165881] Console: colour dummy device 80x25
+[  380.183520] console handover: boot [earlyprom0] -> real [tty0]
+[  380.208131] Dentry cache hash table entries: 131072 (order: 7, 1048576 bytes)
+[  380.210503] Inode-cache hash table entries: 65536 (order: 6, 524288 bytes)
+[  380.235415] Memory: 1022064k available (4952k kernel code, 2064k data, 192k init) [fffff80000000000,000000003feea000]
+[  380.312667] Calibrating delay using timer specific routine.. 9.99 BogoMIPS (lpj=19990)
+[  380.312839] Security Framework initialized
+[  380.312870] SELinux:  Disabled at boot.
+[  380.312889] Capability LSM initialized
+[  380.312935] Mount-cache hash table entries: 512
+[  380.313505] Initializing cgroup subsys ns
+[  380.313524] Initializing cgroup subsys cpuacct
+[  380.313536] Initializing cgroup subsys devices
+[  380.314346] net_namespace: 1208 bytes
+[  380.314892] NET: Registered protocol family 16
+[  380.325288] PCI: Probing for controllers.
+[  380.325332] /pci@8,700000: SCHIZO PCI Bus Module ver[4:0]
+[  380.325349] /pci@8,700000: PCI IO[7ffef000000] MEM[7fe00000000]
+[  380.329864] /pci@8,600000: SCHIZO PCI Bus Module ver[4:0]
+[  380.329881] /pci@8,600000: PCI IO[7ffed000000] MEM[7fd00000000]
+[  380.334466] PCI: Scanning PBM /pci@8,600000
+[  380.334976] PCI: Scanning PBM /pci@8,700000
+[  380.336347] ebus0: [flashprom] [bbc] [ppm] [i2c -> (dimm-fru) (dimm-fru) (dimm-fru) (dimm-fru) (nvram) (idprom)] [i2c -> (cpu-fru) (temperature) (fan-control) (motherboard-fru) (i2c-bridge)] [beep] [rtc] [gpio] [pmc] [floppy] [parallel] [serial]
+[  380.349031] usbcore: registered new interface driver usbfs
+[  380.349274] usbcore: registered new interface driver hub
+[  380.349452] usbcore: registered new device driver usb
+[  380.353275] /pci@8,700000/ebus@5/rtc@1,300070: Clock regs at 000007fe7e300070
+[  380.354631] NET: Registered protocol family 2
+[  380.356677] Switched to high resolution mode on CPU 0
+[  380.388803] IP route cache hash table entries: 8192 (order: 3, 65536 bytes)
+[  380.389510] TCP established hash table entries: 32768 (order: 6, 524288 bytes)
+[  380.391238] TCP bind hash table entries: 32768 (order: 5, 262144 bytes)
+[  380.392036] TCP: Hash tables configured (established 32768 bind 32768)
+[  380.392052] TCP reno registered
+[  380.400796] NET: Registered protocol family 1
+[  380.401078] checking if image is initramfs... it is
+[  381.658428] Freeing initrd memory: 5829k freed
+[  381.659077] Mini RTC Driver
+[  381.659365] /memory-controller@0,400000: US3 memory controller at 0000040000400000 [ACTIVE]
+[  381.660085] audit: initializing netlink socket (disabled)
+[  381.660134] type=2000 audit(1271905721.644:1): initialized
+[  381.660454] Total HugeTLB memory allocated, 0
+[  381.660756] VFS: Disk quotas dquot_6.5.1
+[  381.660865] Dquot-cache hash table entries: 1024 (order 0, 8192 bytes)
+[  381.661363] Installing knfsd (copyright (C) 1996 <email address hidden>).
+[  381.662280] NTFS driver 2.1.29 [Flags: R/W].
+[  381.662397] msgmni has been set to 2009
+[  381.662746] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
+[  381.662775] io scheduler noop registered
+[  381.662788] io scheduler anticipatory registered
+[  381.662801] io scheduler deadline registered
+[  381.662844] io scheduler cfq registered (default)
+[  381.668602] Console: switching to colour frame buffer device 80x30
+[  381.672374] fb0: TVP4020 frame buffer device, memory = 8192K.
+[  381.681745] [drm] Initialized drm 1.1.0 20060810
+[  381.683020] f0086398: ttyS0 at MMIO 0x7fe7e400000 (irq = 10) is a SAB82532 V3.2
+[  381.686005] f0086398: ttyS1 at MMIO 0x7fe7e400040 (irq = 10) is a SAB82532 V3.2
+[  381.694246] brd: module loaded
+[  381.698234] loop: module loaded
+[  381.700507] sungem.c:v0.98 8/24/03 David S. Miller (<email address hidden>)
+[  381.703764] PHY ID: 18074c1, addr: 0
+[  381.704753] eth0: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:03:ba:12:bb:58
+[  381.707196] eth0: Found Generic MII PHY
+[  381.709903] Uniform Multi-Platform E-IDE driver
+[  381.712557] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
+[  381.719917] ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
+[  381.719963] ohci_hcd 0000:00:05.3: OHCI Host Controller
+[  381.723674] ohci_hcd 0000:00:05.3: new USB bus registered, assigned bus number 1
+[  381.731670] ohci_hcd 0000:00:05.3: irq 13, io mem 0x7fe01000000
+[  381.792942] usb usb1: configuration #1 chosen from 1 choice
+[  381.797235] hub 1-0:1.0: USB hub found
+[  381.801563] hub 1-0:1.0: 4 ports detected
+[  381.909230] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
+[  381.913796] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
+[  381.923701] usb usb1: Product: OHCI Host Controller
+[  381.928419] usb usb1: Manufacturer: Linux 2.6.26 ohci_hcd
+[  381.933108] usb usb1: SerialNumber: 0000:00:05.3
+[  381.937761] USB Universal Host Controller Interface driver v3.0
+[  381.942637] mice: PS/2 mouse device common for all mice
+[  382.164665] usb 1-2: new low speed USB device using ohci_hcd and address 2
+[  382.331310] usb 1-2: configuration #1 chosen from 1 choice
+[  382.336918] usb 1-2: New USB device found, idVendor=049f, idProduct=000e
+[  382.341070] usb 1-2: New USB device strings: Mfr=4, Product=20, SerialNumber=0
+[  382.349921] usb 1-2: Product: Compaq Internet Keyboard
+[  382.354146] usb 1-2: Manufacturer: Chicony
+[  382.612663] usb 1-3: new full speed USB device using ohci_hcd and address 3
+[  382.777825] usb 1-3: configuration #1 chosen from 1 choice
+[  382.783275] usb 1-3: New USB device found, idVendor=058f, idProduct=6387
+[  382.787329] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
+[  382.791996] usb 1-3: Product: Mass Storage
+[  382.795814] usb 1-3: Manufacturer: Generic
+[  382.799482] usb 1-3: SerialNumber: 0AC899D6
+[  383.056664] usb 1-4: new low speed USB device using ohci_hcd and address 4
+[  383.221349] usb 1-4: configuration #1 chosen from 1 choice
+[  383.226691] usb 1-4: New USB device found, idVendor=045e, idProduct=0039
+[  383.230537] usb 1-4: New USB device strings: Mfr=1, Product=3, SerialNumber=0
+[  383.235076] usb 1-4: Product: Microsoft 5-Button Mouse with IntelliEye(TM)
+[  383.238730] usb 1-4: Manufacturer: Microsoft
+[  383.248269] input: Chicony Compaq Internet Keyboard as /class/input/input0
+[  383.264794] input,hidraw0: USB HID v1.10 Keyboard [Chicony Compaq Internet Keyboard] on usb-0000:00:05.3-2
+[  383.286678] input: Chicony Compaq Internet Keyboard as /class/input/input1
+[  383.304765] input,hidraw1: USB HID v1.10 Device [Chicony Compaq Internet Keyboard] on usb-0000:00:05.3-2
+[  383.317738] input: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM) as /class/input/input2
+[  383.340859] input,hidraw2: USB HID v1.10 Mouse [Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)] on usb-0000:00:05.3-4
+[  383.349107] usbcore: registered new interface driver usbhid
+[  383.353153] usbhid: v2.6:USB HID core driver
+[  383.357245] Advanced Linux Sound Architecture Driver Version 1.0.16.
+[  383.402450] PCI: Enabling device: (0000:00:03.0), cmd 1
+[  384.100863] eth0: Link is up at 100 Mbps, full-duplex.
+[  384.846600] usbcore: registered new interface driver snd-usb-audio
+[  384.851077] ALSA device list:
+[  384.855394]   #0: Ensoniq AudioPCI ENS1371 at 0x7ffef000500, irq 17
+[  384.861036] TCP cubic registered
+[  384.865480] NET: Registered protocol family 17
+[  384.870147] RPC: Registered udp transport module.
+[  384.874530] RPC: Registered tcp transport module.
+[  384.879100] registered taskstats version 1
+[  384.883476] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
+[  386.429586] SCSI subsystem initialized
+[  386.509039] ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[12]  MMIO=[7fe00120000-7fe001207ff]  Max Packet=[2048]  IR/IT contexts=[4/4]
+[  386.596175] QLogic Fibre Channel HBA Driver: 8.02.01-k4
+[  386.600382] PCI: Enabling device: (0001:00:04.0), cmd 3
+[  386.602464] qla2xxx 0001:00:04.0: Found an ISP2200, irq 20, iobase 0x000007fd00100000
+[  386.612339] qla2xxx 0001:00:04.0: Configuring PCI space...
+[  386.616586] qla2xxx 0001:00:04.0: Configure NVRAM parameters...
+[  386.714919] qla2xxx 0001:00:04.0: Inconsistent NVRAM detected: checksum=0x0 id=<4>qla2xxx 0001:00:04.0: Falling back to functioning (yet invalid -- WWPN) defaults.
+[  386.728340] qla2xxx 0001:00:04.0: Verifying loaded RISC code...
+[  386.734153] PCI: Enabling device: (0000:00:06.0), cmd 147
+[  386.735307] sym0: <875> rev 0x37 at pci 0000:00:06.0 irq 14
+[  386.826112] sym0: No NVRAM, ID 7, Fast-20, SE, parity checking
+[  386.837235] sym0: SCSI BUS has been reset.
+[  386.841214] scsi1 : sym-2.2.3
+[  386.847653] PCI: Enabling device: (0000:00:06.1), cmd 147
+[  386.848824] sym1: <875> rev 0x37 at pci 0000:00:06.1 irq 15
+[  386.939517] sym1: No NVRAM, ID 7, Fast-20, SE, parity checking
+[  386.950672] sym1: SCSI BUS has been reset.
+[  386.954818] scsi2 : sym-2.2.3
+[  386.965219] firmware: requesting ql2200_fw.bin
+[  387.039293] Initializing USB Mass Storage driver...
+[  387.043558] scsi3 : SCSI emulation for USB Mass Storage devices
+[  387.050004] usbcore: registered new interface driver usb-storage
+[  387.054012] USB Mass Storage support registered.
+[  387.057924] usb-storage: device found at 3
+[  387.057930] usb-storage: waiting for device to settle before scanning
+[  388.004887] ieee1394: Host added: ID:BUS[0-00:1023]  GUID[0003bafffe12bb58]
+[  391.590521] scsi 1:0:6:0: CD-ROM            TOSHIBA  DVD-ROM SD-M1401 1009 PQ: 0 ANSI: 2
+[  391.599122]  target1:0:6: Beginning Domain Validation
+[  391.603264]  target1:0:6: asynchronous
+[  391.608968]  target1:0:6: FAST-20 SCSI 20.0 MB/s ST (50 ns, offset 16)
+[  391.614104]  target1:0:6: Domain Validation skipping write tests
+[  391.618025]  target1:0:6: Ending Domain Validation
+[  392.057675] usb-storage: device scan complete
+[  392.063643] scsi 3:0:0:0: Direct-Access     Generic  Flash Disk       8.07 PQ: 0 ANSI: 2
+[  394.008952] Driver 'sr' needs updating - please use bus_type methods
+[  394.017708] sr0: scsi3-mmc drive: 40x/40x cd/rw xa/form2 cdda tray
+[  394.021916] Uniform CD-ROM driver Revision: 3.20
+[  394.026310] sr 1:0:6:0: Attached scsi CD-ROM sr0
+[  394.056732] sr 1:0:6:0: Attached scsi generic sg0 type 5
+[  394.357542] scsi 3:0:0:0: Attached scsi generic sg1 type 0
+[  394.413753] Driver 'sd' needs updating - please use bus_type methods
+[  394.437062] sd 3:0:0:0: [sda] 4103936 512-byte hardware sectors (2101 MB)
+[  394.450042] sd 3:0:0:0: [sda] Write Protect is off
+[  394.454315] sd 3:0:0:0: [sda] Mode Sense: 03 00 00 00
+[  394.454322] sd 3:0:0:0: [sda] Assuming drive cache: write through
+[  394.481010] sd 3:0:0:0: [sda] 4103936 512-byte hardware sectors (2101 MB)
+[  394.493994] sd 3:0:0:0: [sda] Write Protect is off
+[  394.498261] sd 3:0:0:0: [sda] Mode Sense: 03 00 00 00
+[  394.498268] sd 3:0:0:0: [sda] Assuming drive cache: write through
+[  394.502483]  sda:
+[  394.548320] sd 3:0:0:0: [sda] Attached SCSI removable disk
+[  397.912726] qla2xxx 0001:00:04.0: Allocated (252 KB) for firmware dump...
+[  398.044667] qla2xxx 0001:00:04.0: LIP reset occured (f8ef).
+[  398.049170] scsi0 : qla2xxx
+[  398.054582] qla2xxx 0001:00:04.0: 
+[  398.054586]  QLogic Fibre Channel HBA Driver: 8.02.01-k4
+[  398.054590]   QLogic QLA22xx - 
+[  398.054592]   ISP2200: PCI (66 MHz) @ 0001:00:04.0 hdma-, host#=0, fw=2.02.08 TP
+[  398.091669] qla2xxx 0001:00:04.0: LIP occured (f8ef).
+[  398.097133] qla2xxx 0001:00:04.0: LOOP UP detected (1 Gbps).
+[  398.110704] scsi 0:0:0:0: Direct-Access     SEAGATE  ST336605FSUN36G  0638 PQ: 0 ANSI: 3
+[  398.126430] scsi 0:0:1:0: Direct-Access     SEAGATE  ST336605FSUN36G  0638 PQ: 0 ANSI: 3
+[  398.144907] scsi: waiting for bus probes to complete ...
+[  398.153043] sd 0:0:0:0: [sdb] 71132959 512-byte hardware sectors (36420 MB)
+[  398.159977] sd 0:0:0:0: [sdb] Write Protect is off
+[  398.164380] sd 0:0:0:0: [sdb] Mode Sense: db 00 10 08
+[  398.168750] sd 0:0:0:0: [sdb] Write cache: disabled, read cache: enabled, supports DPO and FUA
+[  398.181593] sd 0:0:0:0: [sdb] 71132959 512-byte hardware sectors (36420 MB)
+[  398.188754] sd 0:0:0:0: [sdb] Write Protect is off
+[  398.193390] sd 0:0:0:0: [sdb] Mode Sense: db 00 10 08
+[  398.197775] sd 0:0:0:0: [sdb] Write cache: disabled, read cache: enabled, supports DPO and FUA
+[  398.207949]  sdb: sdb1 sdb2 sdb3 sdb4
+[  398.219180] sd 0:0:0:0: [sdb] Attached SCSI disk
+[  398.223902] sd 0:0:0:0: Attached scsi generic sg2 type 0
+[  398.232492] sd 0:0:1:0: [sdc] 71132959 512-byte hardware sectors (36420 MB)
+[  398.239757] sd 0:0:1:0: [sdc] Write Protect is off
+[  398.244397] sd 0:0:1:0: [sdc] Mode Sense: db 00 10 08
+[  398.249021] sd 0:0:1:0: [sdc] Write cache: disabled, read cache: enabled, supports DPO and FUA
+[  398.262681] sd 0:0:1:0: [sdc] 71132959 512-byte hardware sectors (36420 MB)
+[  398.270173] sd 0:0:1:0: [sdc] Write Protect is off
+[  398.274917] sd 0:0:1:0: [sdc] Mode Sense: db 00 10 08
+[  398.279543] sd 0:0:1:0: [sdc] Write cache: disabled, read cache: enabled, supports DPO and FUA
+[  398.289888]  sdc: sdc1 sdc3
+[  398.304581] sd 0:0:1:0: [sdc] Attached SCSI disk
+[  398.309417] sd 0:0:1:0: Attached scsi generic sg3 type 0
+[  398.768132] kjournald starting.  Commit interval 5 seconds
+[  398.772864] EXT3-fs: mounted filesystem with ordered data mode.
+[  401.026534] udevd version 125 started
+[  405.141436] Adding 1566320k swap on /dev/sdb4.  Priority:-1 extents:1 across:1566320k
+[  405.604286] EXT3 FS on sdb2, internal journal
+[  408.242503] eth0: Link is up at 100 Mbps, full-duplex.
+[  408.249685] eth0: Pause is disabled
+[  410.325778] NET: Registered protocol family 10
+[  410.330075] lo: Disabled Privacy Extensions
+[  414.287849] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
+[  414.307535] NFSD: starting 90-second grace period
+[  418.763886] NET: Registered protocol family 5
+[  420.772658] eth0: no IPv6 routers present
+[  550.132380] ioctl32(xfce4-terminal:3010): Unknown cmd fd(8) cmd(0000530b){t:'S';sz:0} arg(f7e8a380) on /dev/pts/0
+[  550.132405] ioctl32(xfce4-terminal:3010): Unknown cmd fd(8) cmd(0000530b){t:'S';sz:0} arg(f7e8a388) on /dev/pts/0
+[  550.132420] ioctl32(xfce4-terminal:3010): Unknown cmd fd(8) cmd(0000530b){t:'S';sz:0} arg(f7e8a390) on /dev/pts/0
+[ 2388.411343] ioctl32(synaptic:3478): Unknown cmd fd(16) cmd(0000530b){t:'S';sz:0} arg(f755a380) on /dev/pts/1
+[ 2388.411368] ioctl32(synaptic:3478): Unknown cmd fd(16) cmd(0000530b){t:'S';sz:0} arg(f755a388) on /dev/pts/1
+[ 2388.411383] ioctl32(synaptic:3478): Unknown cmd fd(16) cmd(0000530b){t:'S';sz:0} arg(f755a390) on /dev/pts/1
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/587993 b/results/classifier/gemma3:12b/kernel/587993
new file mode 100644
index 00000000..88ea4b56
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/587993
@@ -0,0 +1,116 @@
+
+qemu-kvm 0.12.4+dfsg-1 from debian squeeze crashes "BUG: unable to handle kernel NULL pointer" (sym53c8xx)
+
+I use eucalyptus software (1.6.2) on debian squeeze with kvm 0.12.4+dfsg-1. Kernel 2.6.32-3-amd64. After a few days machines crash. There are no logs in host system. Guest is the same kernel and OS as host. The kvm process use 100% of cpu time. I can not even ping the guest. Here is the log from virtual machine:
+
+[ 3577.816666] sd 0:0:0:0: [sda] ABORT operation started
+[ 3582.816047] sd 0:0:0:0: ABORT operation timed-out.
+[ 3582.816781] sd 0:0:0:0: [sda] ABORT operation started
+[ 3587.816649] sd 0:0:0:0: ABORT operation timed-out.
+[ 3587.817379] sd 0:0:0:0: [sda] DEVICE RESET operation started
+[ 3592.816062] sd 0:0:0:0: DEVICE RESET operation timed-out.
+[ 3592.816882] sd 0:0:0:0: [sda] BUS RESET operation started
+[ 3592.820056] sym0: SCSI BUS reset detected.
+[ 3592.831538] sym0: SCSI BUS has been reset.
+[ 3592.831968] BUG: unable to handle kernel NULL pointer dereference at 0000000000000358
+[ 3592.832003] IP: [<ffffffffa01147c4>] sym_int_sir+0x62f/0x14e0 [sym53c8xx]
+[ 3592.832003] PGD 5f73e067 PUD 5fa53067 PMD 0 
+[ 3592.832003] Oops: 0000 [#1] SMP 
+[ 3592.832003] last sysfs file: /sys/devices/pci0000:00/0000:00:05.0/host0/target0:0:0/0:0:0:0/vendor
+[ 3592.832003] CPU 0 
+[ 3592.832003] Modules linked in: dm_mod openafs(P) ext2 snd_pcsp snd_pcm snd_timer serio_raw i2c_piix4 snd virtio_balloon evdev i2c_core soundcore psmouse button processor snd_page_alloc ext3 jbd mbcache sd_mod crc_t10dif ata_generic libata ide_pci_generic sym53c8xx scsi_transport_spi thermal piix uhci_hcd ehci_hcd floppy thermal_sys scsi_mod virtio_pci virtio_ring virtio e1000 ide_core usbcore nls_base [last unloaded: scsi_wait_scan]
+[ 3592.832003] Pid: 193, comm: scsi_eh_0 Tainted: P           2.6.32-3-amd64 #1 Bochs
+[ 3592.832003] RIP: 0010:[<ffffffffa01147c4>]  [<ffffffffa01147c4>] sym_int_sir+0x62f/0x14e0 [sym53c8xx]
+[ 3592.832003] RSP: 0018:ffff880001803cb0  EFLAGS: 00010287
+[ 3592.832003] RAX: 000000000000000a RBX: 000000000000000b RCX: 000000005f410090
+[ 3592.832003] RDX: 0000000000000000 RSI: ffff88005c450800 RDI: ffffc90000a5e006
+[ 3592.832003] RBP: ffff88005f410000 R08: 0000000000000000 R09: 0000000000000000
+[ 3592.832003] R10: 000000000000003a R11: ffffffff813b871e R12: ffff88005f410090
+[ 3592.832003] R13: 0000000000000084 R14: 0000000000000000 R15: 0000000000000001
+[ 3592.832003] FS:  0000000000000000(0000) GS:ffff880001800000(0000) knlGS:0000000000000000
+[ 3592.832003] CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
+[ 3592.832003] CR2: 0000000000000358 CR3: 000000005e269000 CR4: 00000000000006f0
+[ 3592.832003] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
+[ 3592.832003] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
+[ 3592.832003] Process scsi_eh_0 (pid: 193, threadinfo ffff88005f6fa000, task ffff88005f697880)
+[ 3592.832003] Stack:
+[ 3592.832003]  ffff88005f3fd000 0000000000000000 0000000000000130 0000000000000000
+[ 3592.832003] <0> ffff88005f407710 ffffc90000a64710 ffffffffffffff10 ffffffff81195301
+[ 3592.832003] <0> 0000000000000010 0000000000010212 ffff880001803d18 0000000000000018
+[ 3592.832003] Call Trace:
+[ 3592.832003]  <IRQ> 
+[ 3592.832003]  [<ffffffff81195301>] ? __memcpy_toio+0x9/0x19
+[ 3592.832003]  [<ffffffffa01164ed>] ? sym_interrupt+0x46c/0x6a3 [sym53c8xx]
+[ 3592.832003]  [<ffffffff8103fea0>] ? update_curr+0xa6/0x147
+[ 3592.832003]  [<ffffffffa010fbde>] ? sym53c8xx_intr+0x43/0x6a [sym53c8xx]
+[ 3592.832003]  [<ffffffff81093bfc>] ? handle_IRQ_event+0x58/0x126
+[ 3592.832003]  [<ffffffff810954e2>] ? handle_fasteoi_irq+0x7d/0xb5
+[ 3592.832003]  [<ffffffff81013957>] ? handle_irq+0x17/0x1d
+[ 3592.832003]  [<ffffffff81012fb1>] ? do_IRQ+0x57/0xb6
+[ 3592.832003]  [<ffffffff810114d3>] ? ret_from_intr+0x0/0x11
+[ 3592.832003]  [<ffffffff81053903>] ? __do_softirq+0x6e/0x19f
+[ 3592.832003]  [<ffffffff8106fa87>] ? tick_dev_program_event+0x2d/0x95
+[ 3592.832003]  [<ffffffff81011cac>] ? call_softirq+0x1c/0x30
+[ 3592.832003]  [<ffffffff81013903>] ? do_softirq+0x3f/0x7c
+[ 3592.832003]  [<ffffffff810537e1>] ? irq_exit+0x36/0x76
+[ 3592.832003]  [<ffffffff81025837>] ? smp_apic_timer_interrupt+0x87/0x95
+[ 3592.832003]  [<ffffffff81011673>] ? apic_timer_interrupt+0x13/0x20
+[ 3592.832003]  <EOI> 
+[ 3592.832003]  [<ffffffff8118e009>] ? delay_tsc+0x0/0x73
+[ 3592.832003]  [<ffffffffa010f900>] ? sym_eh_handler+0x22e/0x2e2 [sym53c8xx]
+[ 3592.832003]  [<ffffffffa008e5de>] ? scsi_try_bus_reset+0x50/0xd9 [scsi_mod]
+[ 3592.832003]  [<ffffffffa008f565>] ? scsi_eh_ready_devs+0x50c/0x781 [scsi_mod]
+[ 3592.832003]  [<ffffffffa008fd6b>] ? scsi_error_handler+0x3c1/0x5b5 [scsi_mod]
+[ 3592.832003]  [<ffffffffa008f9aa>] ? scsi_error_handler+0x0/0x5b5 [scsi_mod]
+[ 3592.832003]  [<ffffffff81064789>] ? kthread+0x79/0x81
+[ 3592.832003]  [<ffffffff81011baa>] ? child_rip+0xa/0x20
+[ 3592.832003]  [<ffffffff81064710>] ? kthread+0x0/0x81
+[ 3592.832003]  [<ffffffff81011ba0>] ? child_rip+0x0/0x20
+[ 3592.832003] Code: 48 c7 c7 82 92 11 a0 eb 63 48 8b 98 38 01 00 00 48 8d b8 28 01 00 00 e8 df d5 0f e1 48 89 da 48 89 c6 48 c7 c7 bc 92 11 a0 eb 6d <49> 8b 96 58 03 00 00 48 8b 82 80 00 00 00 48 8b a8 b0 00 00 00 
+[ 3592.832003] RIP  [<ffffffffa01147c4>] sym_int_sir+0x62f/0x14e0 [sym53c8xx]
+[ 3592.832003]  RSP <ffff880001803cb0>
+[ 3592.832003] CR2: 0000000000000358
+[ 3592.867935] ---[ end trace 06f90ebbdbd172ee ]---
+[ 3592.868360] Kernel panic - not syncing: Fatal exception in interrupt
+[ 3592.868906] Pid: 193, comm: scsi_eh_0 Tainted: P      D    2.6.32-3-amd64 #1
+[ 3592.869511] Call Trace:
+[ 3592.869727]  <IRQ>  [<ffffffff812ed349>] ? panic+0x86/0x141
+[ 3592.870225]  [<ffffffff81011673>] ? apic_timer_interrupt+0x13/0x20
+[ 3592.870778]  [<ffffffff811afbdc>] ? dummycon_dummy+0x0/0x3
+[ 3592.871250]  [<ffffffff81014a37>] ? oops_end+0x64/0xb4
+[ 3592.871694]  [<ffffffff81014a7a>] ? oops_end+0xa7/0xb4
+[ 3592.872150]  [<ffffffff810322b8>] ? no_context+0x1e9/0x1f8
+[ 3592.872626]  [<ffffffff8103246d>] ? __bad_area_nosemaphore+0x1a6/0x1ca
+[ 3592.873185]  [<ffffffff8106807c>] ? up+0xe/0x36
+[ 3592.873576]  [<ffffffff8104e219>] ? release_console_sem+0x17e/0x1af
+[ 3592.874125]  [<ffffffff81024d72>] ? lapic_next_event+0x18/0x1d
+[ 3592.874642]  [<ffffffff812ef595>] ? page_fault+0x25/0x30
+[ 3592.875103]  [<ffffffffa01147c4>] ? sym_int_sir+0x62f/0x14e0 [sym53c8xx]
+[ 3592.875678]  [<ffffffff81195301>] ? __memcpy_toio+0x9/0x19
+[ 3592.876162]  [<ffffffffa01164ed>] ? sym_interrupt+0x46c/0x6a3 [sym53c8xx]
+[ 3592.876748]  [<ffffffff8103fea0>] ? update_curr+0xa6/0x147
+[ 3592.877224]  [<ffffffffa010fbde>] ? sym53c8xx_intr+0x43/0x6a [sym53c8xx]
+[ 3592.877800]  [<ffffffff81093bfc>] ? handle_IRQ_event+0x58/0x126
+[ 3592.878319]  [<ffffffff810954e2>] ? handle_fasteoi_irq+0x7d/0xb5
+[ 3592.878848]  [<ffffffff81013957>] ? handle_irq+0x17/0x1d
+[ 3592.879305]  [<ffffffff81012fb1>] ? do_IRQ+0x57/0xb6
+[ 3592.879744]  [<ffffffff810114d3>] ? ret_from_intr+0x0/0x11
+[ 3592.880237]  [<ffffffff81053903>] ? __do_softirq+0x6e/0x19f
+[ 3592.880723]  [<ffffffff8106fa87>] ? tick_dev_program_event+0x2d/0x95
+[ 3592.881284]  [<ffffffff81011cac>] ? call_softirq+0x1c/0x30
+[ 3592.881762]  [<ffffffff81013903>] ? do_softirq+0x3f/0x7c
+[ 3592.882230]  [<ffffffff810537e1>] ? irq_exit+0x36/0x76
+[ 3592.882691]  [<ffffffff81025837>] ? smp_apic_timer_interrupt+0x87/0x95
+[ 3592.883258]  [<ffffffff81011673>] ? apic_timer_interrupt+0x13/0x20
+[ 3592.883795]  <EOI>  [<ffffffff8118e009>] ? delay_tsc+0x0/0x73
+[ 3592.884319]  [<ffffffffa010f900>] ? sym_eh_handler+0x22e/0x2e2 [sym53c8xx]
+[ 3592.884917]  [<ffffffffa008e5de>] ? scsi_try_bus_reset+0x50/0xd9 [scsi_mod]
+[ 3592.885522]  [<ffffffffa008f565>] ? scsi_eh_ready_devs+0x50c/0x781 [scsi_mod]
+[ 3592.886152]  [<ffffffffa008fd6b>] ? scsi_error_handler+0x3c1/0x5b5 [scsi_mod]
+[ 3592.886789]  [<ffffffffa008f9aa>] ? scsi_error_handler+0x0/0x5b5 [scsi_mod]
+[ 3592.887398]  [<ffffffff81064789>] ? kthread+0x79/0x81
+[ 3592.887836]  [<ffffffff81011baa>] ? child_rip+0xa/0x20
+[ 3592.888290]  [<ffffffff81064710>] ? kthread+0x0/0x81
+[ 3592.888721]  [<ffffffff81011ba0>] ? child_rip+0x0/0x20
+
+Unfortunatelly I have no idea how to reproduce the problem.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/61 b/results/classifier/gemma3:12b/kernel/61
new file mode 100644
index 00000000..a3d3e667
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/61
@@ -0,0 +1,2 @@
+
+qemu-system-arm segfaults while servicing SYS_HEAPINFO
diff --git a/results/classifier/gemma3:12b/kernel/611 b/results/classifier/gemma3:12b/kernel/611
new file mode 100644
index 00000000..73697d0f
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/611
@@ -0,0 +1,128 @@
+
+qemu-system-m68k: hw/scsi/scsi-disk.c  assertion failure
+Description of problem:
+QEMU assertion failure (crash):
+qemu-system-m68k: ../hw/scsi/scsi-disk.c:550: scsi_write_data: Assertion `r->req.aiocb == NULL' failed.
+Steps to reproduce:
+```
+$ xz -d initramfs-stress-ng.cpio.xz vmlinux-5.14-multi.xz
+$ cat rootfs.ext2.xz-part? | xz -dc > rootfs.ext2
+$ qemu-system-m68k -M q800 -m 128M -serial none -serial mon:stdio -g 800x600x4 -rtc base=localtime -drive file=rootfs.ext2,format=raw -kernel vmlinux-5.14-multi -append "console=ttyS0" -initrd initramfs-stress-ng.cpio 
+
+ABCFGHIJK
+[    0.000000] Linux version 5.14.0-multi (fthain@nippy) (m68k-linux-gnu-gcc (btc) 6.4.0, GNU ld (btc) 2.28) #5 Sat Sep 4 16:09:41 AEST 2021
+[    0.000000] Saving 140 bytes of bootinfo
+[    0.000000] Detected Macintosh model: 35
+[    0.000000] Apple Macintosh Quadra 800
+[    0.000000] Zone ranges:
+[    0.000000]   DMA      [mem 0x0000000000000000-0x0000007fffffffff]
+[    0.000000]   Normal   empty
+[    0.000000] Movable zone start for each node
+[    0.000000] Early memory node ranges
+[    0.000000]   node   0: [mem 0x0000000000000000-0x0000000007ffffff]
+[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000007ffffff]
+[    0.000000] initrd: 07d3e000 - 07fff600
+[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 32480
+[    0.000000] Kernel command line: console=ttyS0
+[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes, linear)
+[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes, linear)
+[    0.000000] Sorting __ex_table...
+[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
+[    0.000000] Memory: 121420K/131072K available (4074K kernel code, 327K rwdata, 752K rodata, 148K init, 117K bss, 9652K reserved, 0K cma-reserved)
+[    0.000000] SLUB: HWalign=16, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
+[    0.000000] NR_IRQS: 200
+[    0.000000] clocksource: via1: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 2439823894983 ns
+[    0.000000] Console: colour dummy device 80x25
+[    0.010000] printk: console [ttyS0] enabled
+[    0.020000] Calibrating delay loop... 841.31 BogoMIPS (lpj=4206592)
+[    0.110000] pid_max: default: 32768 minimum: 301
+[    0.110000] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
+[    0.110000] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
+[    0.150000] devtmpfs: initialized
+[    0.160000] random: get_random_u32 called from bucket_table_alloc.isra.28+0x70/0x1a6 with crng_init=0
+[    0.160000] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
+[    0.160000] futex hash table entries: 256 (order: -1, 3072 bytes, linear)
+[    0.160000] NET: Registered PF_NETLINK/PF_ROUTE protocol family
+[    0.170000] DMA: preallocated 128 KiB GFP_KERNEL pool for atomic allocations
+[    0.170000] DMA: preallocated 128 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
+[    0.200000] wait_for_initramfs() called before rootfs_initcalls
+[    0.220000] NuBus: Scanning NuBus slots.
+[    0.220000] Slot 9: Board resource not found!
+[    0.220000] SCSI subsystem initialized
+[    0.240000] clocksource: Switched to clocksource via1
+[    0.260000] NET: Registered PF_INET protocol family
+[    0.260000] IP idents hash table entries: 2048 (order: 2, 16384 bytes, linear)
+[    0.270000] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
+[    0.270000] TCP established hash table entries: 1024 (order: 0, 4096 bytes, linear)
+[    0.270000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes, linear)
+[    0.270000] TCP: Hash tables configured (established 1024 bind 1024)
+[    0.270000] UDP hash table entries: 256 (order: 0, 4096 bytes, linear)
+[    0.270000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes, linear)
+[    0.270000] NET: Registered PF_UNIX/PF_LOCAL protocol family
+[    0.280000] RPC: Registered named UNIX socket transport module.
+[    0.280000] RPC: Registered udp transport module.
+[    0.280000] RPC: Registered tcp transport module.
+[    0.280000] RPC: Registered tcp NFSv4.1 backchannel transport module.
+[    0.290000] Trying to unpack rootfs image as initramfs...
+[    0.290000] workingset: timestamp_bits=30 max_order=15 bucket_order=0
+[    0.310000] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
+[    0.310000] io scheduler mq-deadline registered
+[    0.310000] macfb: framebuffer at 0xf9001000, mapped to 0x(ptrval), size 234k
+[    0.310000] macfb: mode is 800x600x4, linelength=400
+[    0.330000] Console: switching to colour frame buffer device 100x37
+[    0.350000] fb0: DAFB frame buffer device
+[    0.350000] pmac_zilog: 0.6 (Benjamin Herrenschmidt <benh@kernel.crashing.org>)
+[    0.350000] scc.0: ttyS0 at MMIO 0x5000c022 (irq = 4, base_baud = 230400) is a Z85c30 ESCC - Serial port
+[    0.350000] scc.1: ttyS1 at MMIO 0x5000c020 (irq = 4, base_baud = 230400) is a Z85c30 ESCC - Serial port
+[    0.350000] Non-volatile memory driver v1.3
+[    0.390000] brd: module loaded
+[    0.390000] adb: Mac II ADB Driver v1.0 for Unified ADB
+[    0.410000] Detected ADB keyboard, type ANSI.
+[    0.410000] input: ADB keyboard as /devices/virtual/input/input0
+[    0.420000] random: fast init done
+[    0.420000] input: ADB mouse as /devices/virtual/input/input1
+[    0.430000] Freeing initrd memory: 2820K
+[    0.430000] mac_esp: using PDMA for controller 0
+[    0.430000] mac_esp mac_esp.0: esp0: regs[(ptrval):0] irq[19]
+[    0.430000] mac_esp mac_esp.0: esp0: is a ESP236, 16 MHz (ccf=4), SCSI ID 7
+[    3.520000] scsi host0: esp
+[    3.530000] scsi 0:0:0:0: Direct-Access     QEMU     QEMU HARDDISK    2.5+ PQ: 0 ANSI: 5
+[    3.540000] scsi target0:0:0: Beginning Domain Validation
+[    3.540000] scsi target0:0:0: Domain Validation skipping write tests
+[    3.540000] scsi target0:0:0: Ending Domain Validation
+[    3.550000] scsi 0:0:2:0: CD-ROM            QEMU     QEMU CD-ROM      2.5+ PQ: 0 ANSI: 5
+[    3.550000] scsi target0:0:2: Beginning Domain Validation
+[    3.560000] scsi target0:0:2: Domain Validation skipping write tests
+[    3.560000] scsi target0:0:2: Ending Domain Validation
+[    3.560000] sr 0:0:2:0: Power-on or device reset occurred
+[    3.570000] sr 0:0:2:0: [sr0] scsi3-mmc drive: 16x/50x cd/rw xa/form2 cdda tray
+[    3.570000] cdrom: Uniform CD-ROM driver Revision: 3.20
+[    3.570000] sd 0:0:0:0: Power-on or device reset occurred
+[    3.580000] sd 0:0:0:0: [sda] 322560 512-byte logical blocks: (165 MB/158 MiB)
+[    3.580000] sd 0:0:0:0: [sda] Write Protect is off
+[    3.580000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
+[    3.590000] sd 0:0:0:0: Attached scsi generic sg0 type 0
+[    3.590000] sr 0:0:2:0: Attached scsi generic sg1 type 5
+[    3.590000] Onboard/comm-slot SONIC, revision 0x0004, 32 bit DMA, register offset 2
+[    3.590000] SONIC ethernet @50f0a000, MAC 08:00:07:12:34:56, IRQ 3
+[    3.600000] sd 0:0:0:0: [sda] Attached SCSI disk
+[    3.610000] aoe: AoE v85 initialised.
+[    3.610000] mousedev: PS/2 mouse device common for all mice
+[    3.610000] rtc-generic rtc-generic: registered as rtc0
+[    3.620000] NET: Registered PF_PACKET protocol family
+[    3.630000] Freeing unused kernel image (initmem) memory: 148K
+[    3.630000] This architecture does not have kernel memory protection.
+[    3.630000] Run /init as init process
+/init: line 11: ifconfig: not found
+# mount /dev/sda /mnt
+[    9.030000] EXT4-fs (sda): mounting ext2 file system using the ext4 subsystem
+[    9.080000] EXT4-fs (sda): mounted filesystem without journal. Opts: (null). Quota mode: disabled.
+# cd /mnt
+# /root/stress-ng --mmap -1 --mmap-file --mmap-bytes=100%
+stress-ng: info:  [42] defaulting to a 86400 second (1 day, 0.00 secs) run per stressor
+stress-ng: info:  [42] dispatching hogs: 1 mmap
+qemu-system-m68k: ../hw/scsi/scsi-disk.c:550: scsi_write_data: Assertion `r->req.aiocb == NULL' failed.
+Aborted
+```
+Additional information:
+
diff --git a/results/classifier/gemma3:12b/kernel/616769 b/results/classifier/gemma3:12b/kernel/616769
new file mode 100644
index 00000000..6bbe5aa1
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/616769
@@ -0,0 +1,28 @@
+
+interrupt problem x86_64
+
+Hello.
+I'm studing the x86_64 arch to port colinux to this new architecture.
+
+For who does not know, colinux is a port of linux that runs on windows NATIVELY. Colinux is
+1) a small windows driver
+2) a kernel patched
+3) some windows user-space application that talk with linux kernel (network, console, ...)
+
+I have written the more internal part of colinux, that is the code that switch between windows and linux.
+This is done saving and restore the machine state :
+1) CR3
+2) IDT
+3) registers
+
+The problem I see is that after the switch I see the reboot of my virtual machine.
+I would say that the new IDT and/or CR3 is not flushed.
+My code is written in asm/C so I can follow the code step by step.
+I can say exactly the instruction that is broken.
+
+All my code runs nicely on bochs.
+I don't have an x86_64 real PC.
+
+If someone wants to repair this bug .... I'm here.
+
+Paolo Minazzi
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/619 b/results/classifier/gemma3:12b/kernel/619
new file mode 100644
index 00000000..44f962f5
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/619
@@ -0,0 +1,2 @@
+
+Move TCGCPUOps::fake_user_exception() to linux-user/i386/cpu_loop.c
diff --git a/results/classifier/gemma3:12b/kernel/623852 b/results/classifier/gemma3:12b/kernel/623852
new file mode 100644
index 00000000..d8c2cdd0
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/623852
@@ -0,0 +1,14 @@
+
+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.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/629791 b/results/classifier/gemma3:12b/kernel/629791
new file mode 100644
index 00000000..84b16fca
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/629791
@@ -0,0 +1,6 @@
+
+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.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/635 b/results/classifier/gemma3:12b/kernel/635
new file mode 100644
index 00000000..3a25eb71
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/635
@@ -0,0 +1,29 @@
+
+HPPA Error on Raspberry PI - deposit64: Assertion `start >= 0 && length > 0 && length <= 64 - start' failed
+Description of problem:
+The emulator starts normally but during the Guest OS installation (HP-UX 10.20) it crash with below error:
+(qemu) qemu-system-hppa: /root/qemu/include/qemu/bitops.h:496: deposit64: Assertion `start >= 0 && length > 0 && length <= 64 - start' failed.
+Steps to reproduce:
+1. Run qemu-system-hppa with the command listed above
+2. Start HP-UX 10.20 installation and finish the install wizard
+Additional information:
+It crashes after the installation step bolow:
+
+Executing user specified script:
+=========================================
+
+  [[ ! -a /dev/lan0 ]] && mknod /dev/lan0 c 52 0x000000
+
+=========================================
+       * Will use the cold-install media for swinstall as well.
+       * Starting swinstall:
+WARNING: The software specified contains a kernel fileset.  It will be
+         necessary to reconfigure and reboot the system to make the
+         kernel software functional.
+
+       * Beginning Analysis Phase.
+       * Source:           localhost:/SD_CDROM
+       * Target:           loopback:/
+       * Target logfile:   loopback:/var/adm/sw/swagent.log
+       * Reading source for product information.
+       * Reading source for file information.
diff --git a/results/classifier/gemma3:12b/kernel/64 b/results/classifier/gemma3:12b/kernel/64
new file mode 100644
index 00000000..e386530c
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/64
@@ -0,0 +1,2 @@
+
+raspi3 machine can not shutdown
diff --git a/results/classifier/gemma3:12b/kernel/648 b/results/classifier/gemma3:12b/kernel/648
new file mode 100644
index 00000000..efc6a8a8
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/648
@@ -0,0 +1,2 @@
+
+util/vfio-helpers: misaligned address for struct vfio_iova_range, which requires 8 byte alignment
diff --git a/results/classifier/gemma3:12b/kernel/650 b/results/classifier/gemma3:12b/kernel/650
new file mode 100644
index 00000000..2abb430e
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/650
@@ -0,0 +1,25 @@
+
+Monitor device_add triggers deadlock when calling drain_call_rcu on QEMU >= 6.0.0
+Description of problem:
+It hangs
+Steps to reproduce:
+1. Run the QEMU:
+   ```
+   ./qemu-system-mips64 -nographic
+   ```
+2. Enter into the QEMU monitor: press ctrl-a c
+3. Execute command `device_add` without arguments:
+```
+(qemu) device_add
+```
+4. It hangs so bad that only `kill -9` helps
+Additional information:
+I didn't test versions between 4.2.0 and 6.0.0, but I can confirm that 6.0.0, 6.1.0 and the latest master pull have this bug, while version 4.2.0 doesn't have it.
+
+I've tracked the problem and found this.
+
+1. Command `device_add` calls function `drain_call_rcu`. `drain_call_rcu` waits indefinitely for drain_complete_event.
+2. Function `cpu_exec` in accel/tcg/cpu-exec.c calls `rcu_read_lock` but does not call `rcu_read_unlock()`. `cpu_exec` just spins in its inner loop.
+3. Function `call_rcu_thread` hanged in calling the `synchronize_rcu` which calls `wait_for_readers`.
+
+If I execute `stop` command in QEMU monitor before calling `device_add` command, no hang happen.
diff --git a/results/classifier/gemma3:12b/kernel/655 b/results/classifier/gemma3:12b/kernel/655
new file mode 100644
index 00000000..3bc6a088
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/655
@@ -0,0 +1,33 @@
+
+Java crashes on s390x VM with SIGILL/ILL_PRVOPC at '__kernel_getcpu+0x8'
+Description of problem:
+The `java` command fails with the following message:
+
+```console
+$ /usr/lib/jvm/java-17-openjdk-s390x/bin/java --version
+#
+# A fatal error has been detected by the Java Runtime Environment:
+#
+# SIGILL (0x4) at pc=0x000003ff9e4fe6f4, pid=2883, tid=2884
+#
+# JRE version: (17.0+35) (build )
+# Java VM: OpenJDK 64-Bit Server VM (17+35-Ubuntu-120.04, mixed
+# mode, sharing, tiered, compressed oops, compressed class ptrs,
+# serial gc, linux-s390x)
+# Problematic frame:
+# C [linux-vdso64.so.1+0x6f8] __kernel_getcpu+0x8
+#
+# Core dump will be written. Default location: Core dumps may
+# be processed with "/usr/share/apport/apport %p %s %c %d %P %E"
+# (or dumping to /home/ubuntu/core.2883)
+#
+# An error report file with more information is saved as:
+# /home/ubuntu/hs_err_pid2883.log
+#
+#
+Aborted (core dumped)
+```
+Steps to reproduce:
+1. Run `java --version`
+Additional information:
+The corresponding log file is attached as the file [hs_err_pid2883.log](/uploads/1631b6a0f0aad2f77c4928ed6bb540c6/hs_err_pid2883.log).
diff --git a/results/classifier/gemma3:12b/kernel/672934 b/results/classifier/gemma3:12b/kernel/672934
new file mode 100644
index 00000000..1cb3904d
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/672934
@@ -0,0 +1,8 @@
+
+FPU incorrect on Mac OS X
+
+I am using the 0.13.0 release version of QEMU on Mac OS X 10.6.4. I work for a university and the affected guest OS is our own research OS. I believe I found a bug in QEMU's FPU emulation, which only triggers on the Mac. You can reproduce the problem by booting the attached ISO image.
+
+Investigating the problem, I found that the lua interpreter in our loader component (called "ned") internally uses doubles to represent all lua-numbers. These doubles are showing completely wrong values on QEMU/Mac, resulting in the lua code not processing properly.
+
+I also attached a patch which fixes the problem for me. The attached ZIP-file also contains "before" and "after" screenshots. Note that booting the ISO on a real machine or on a Linux-QEMU always shows the correct "after" behavior. Only QEMU on the Mac exhibits the wrong "before" behavior without my patch. The patch might break other systems setting the CONFIG_BSD flag, so maybe the preprocessor should check for __APPLE__ instead to make the fix Mac-only.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/676 b/results/classifier/gemma3:12b/kernel/676
new file mode 100644
index 00000000..c94f2e20
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/676
@@ -0,0 +1,55 @@
+
+Throws a PF when it should throw a GF/SS
+Description of problem:
+QEMU misreports what should be a #GP as a #PF 
+```
+check_exception old: 0xffffffff new 0xe
+     0: v=0e e=0001 i=0 cpl=0 IP=0028:ffffffffb28fa53b pc=ffffffffb28fa53b SP=0030:ffffffffb2901210 CR2=1fbf7020000772a4
+RAX=1fbf7020000772a4 RBX=0000000000000000 RCX=ffff80000006a0a8 RDX=ffff80000006a038
+RSI=1fbff0200000d26c RDI=0000000000000080 RBP=ffffffffb2901230 RSP=ffffffffb2901210
+R8 =ffffffffb28fb37f R9 =0000000000000000 R10=0000000000000000 R11=0000000000000000
+R12=0000000000000000 R13=0000000000000000 R14=0000000000000000 R15=0000000000000000
+RIP=ffffffffb28fa53b RFL=00000007 [-----PC] CPL=0 II=0 A20=1 SMM=0 HLT=0
+ES =0030 0000000000000000 00000000 00009300 DPL=0 DS   [-WA]
+CS =0028 0000000000000000 00000000 00209a00 DPL=0 CS64 [-R-]
+SS =0030 0000000000000000 00000000 00009300 DPL=0 DS   [-WA]
+DS =0030 0000000000000000 00000000 00009300 DPL=0 DS   [-WA]
+FS =0030 0000000000000000 00000000 00009300 DPL=0 DS   [-WA]
+GS =0030 0000000000000000 00000000 00009300 DPL=0 DS   [-WA]
+LDT=0000 0000000000000000 00000000 00008200 DPL=0 LDT
+TR =0000 0000000000000000 0000ffff 00008b00 DPL=0 TSS64-busy
+GDT=     000000000000edc0 00000037
+IDT=     000000000002e6a0 000000ff
+CR0=80000013 CR2=1fbf7020000772a4 CR3=0000000000058000 CR4=000006a0
+DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 
+DR6=00000000ffff0ff0 DR7=0000000000000400
+CCS=3f7fe0400001a4d9 CCD=1fbff0200000d26c CCO=SARQ    
+EFER=0000000000000501
+```
+
+Now, `CR2=1fbf7020000772a4` is of course a non-canonical address, and therefore should not generate a #PF, rather it should generate a #GP. I also tried to generate a #SS by dereferencing a non-canonical address through the stack, and that also throws a #PF instead of a #SS
+
+```
+check_exception old: 0xffffffff new 0xe
+     0: v=0e e=0001 i=0 cpl=0 IP=0028:fffffffff4bda92a pc=fffffffff4bda92a SP=0030:1fbf7020000772a4 CR2=1fbf70200007729c
+RAX=0000000000000000 RBX=0000000000000000 RCX=0000000000000000 RDX=fffffffff4bdb998
+RSI=0000000000000000 RDI=fffffffff4bdb998 RBP=fffffffff4bdf290 RSP=1fbf7020000772a4
+R8 =0000000000000000 R9 =0000000000000000 R10=0000000000000000 R11=0000000000000000
+R12=0000000000000000 R13=0000000000000000 R14=0000000000000000 R15=0000000000000000
+RIP=fffffffff4bda92a RFL=00000046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
+ES =0030 0000000000000000 00000000 00009300 DPL=0 DS   [-WA]
+CS =0028 0000000000000000 00000000 00209a00 DPL=0 CS64 [-R-]
+SS =0030 0000000000000000 00000000 00009300 DPL=0 DS   [-WA]
+DS =0030 0000000000000000 00000000 00009300 DPL=0 DS   [-WA]
+FS =0030 0000000000000000 00000000 00009300 DPL=0 DS   [-WA]
+GS =0030 0000000000000000 00000000 00009300 DPL=0 DS   [-WA]
+LDT=0000 0000000000000000 00000000 00008200 DPL=0 LDT
+TR =0000 0000000000000000 0000ffff 00008b00 DPL=0 TSS64-busy
+GDT=     000000000000edc0 00000037
+IDT=     000000000002e6a0 000000ff
+CR0=80000011 CR2=1fbf70200007729c CR3=00000000bffa5000 CR4=00000020
+```
+Steps to reproduce:
+1. Dereference a non-canonical address
+2. QEMU gives you a page fault instead of a gpf
+3. reconsider life
diff --git a/results/classifier/gemma3:12b/kernel/677 b/results/classifier/gemma3:12b/kernel/677
new file mode 100644
index 00000000..6cb35dae
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/677
@@ -0,0 +1,2 @@
+
+Qemu crashes when trying to load kernel inside of WSL2
diff --git a/results/classifier/gemma3:12b/kernel/679 b/results/classifier/gemma3:12b/kernel/679
new file mode 100644
index 00000000..a18b1bde
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/679
@@ -0,0 +1,2 @@
+
+powerpc/e500: QEMU freeze without any output when kernel size is a bit big
diff --git a/results/classifier/gemma3:12b/kernel/682360 b/results/classifier/gemma3:12b/kernel/682360
new file mode 100644
index 00000000..41e3b97c
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/682360
@@ -0,0 +1,23 @@
+
+Unaccessible memory
+
+Hello,
+
+I'm trying to develop a OS over L4/X2 microkernel and I use Linux debian and qemu 0.13 in 64 bits mode. When I start qemu with qemu-system-x86_64 -hdc freevms.img -smp 1 -serial stdio -m 128M -k fr, my kernel boots fine. If I modify this command line with -m 384M (for example), my kernel is loaded but enter in a deadlock. I have found a bug in my code until I have tried to use the _same_ disk image under virtualbox and it works without any trouble. I runs fine on a real PC also.
+
+I have bissected my code and qemu stops (maybe in a deadlock) when I try to access to memory :
+%MEM-I-VM_ALLOC, adding $0000000000045000 - $0000000000108FFF to VM allocator
+%MEM-I-VM_ALLOC, adding $000000000010B000 - $00000000003F2FFF to VM allocator
+%MEM-I-VM_ALLOC, adding $000000000040C000 - $0000000000FFFFFF to VM allocator
+%MEM-I-VM_ALLOC, adding $000000000100F000 - $FFFFFEFFFFFFFFFF to VM allocator
+%MEM-I-ACCMAP, accepting mapping
+%MEM-I-ACCMAP, virtual  $FFFF000000000000 - $FFFF000000000FFF
+%MEM-I-ACCMAP, physical $000000000009E000 - $000000000009EFFF
+
+Note that qemu doesn't crash. It only stops. My virtual memory subsystem maps $FFFF000000000000 in physical memory ($9E000). And when I try to initialize this memory, qemu enters in deadlock.
+
+A disk image to reproduce this bug is available at http://www.systella.fr/~bertrand/freevms.img.bz2
+
+Regards,
+
+JKB
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/704 b/results/classifier/gemma3:12b/kernel/704
new file mode 100644
index 00000000..e17d52ad
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/704
@@ -0,0 +1,2 @@
+
+linux-user: misaligned address for type 'struct linux_dirent64'
diff --git a/results/classifier/gemma3:12b/kernel/710234 b/results/classifier/gemma3:12b/kernel/710234
new file mode 100644
index 00000000..8752fcff
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/710234
@@ -0,0 +1,11 @@
+
+Qemu segfaults at start regardles if i suply an image or not
+
+I have tried both with latest development (git clone git://git.qemu.org/qemu.git ran around 12:00 2011-01-30) and with  qemu-0.13.0. Since i have not written c-code in the last years, and never really ran a debugger under Linux this will bug report will be a bit sketchy.
+
+When starting qemu, either just qemu or with an image it segfaults. The Qemu window flashes by and then i get the segfault message (qemu -nographic still segfaults so i guess it is not really graphics related).   When starting qemu with a garbled command line it returns an error and exits normally how ever.
+
+uname -a
+Linux LIX 2.6.33.4-smp #2 SMP Wed May 12 22:47:36 CDT 2010 i686 AMD Phenom(tm) II X4 810 Processor AuthenticAMD GNU/Linux
+
+I have tried recompiling with --disable-kvm since i run a 32 bit OS on a 64 bit CPU, but to no avail.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/721 b/results/classifier/gemma3:12b/kernel/721
new file mode 100644
index 00000000..1542ccc8
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/721
@@ -0,0 +1,31 @@
+
+Build failed at libqemu-aarch64-softmmu.fa.p/accel_tcg_cputlb.c.o
+Steps to reproduce:
+1. Download and build from source
+
+```
+wget https://download.qemu.org/qemu-6.1.0.tar.xz
+tar xvJf qemu-6.1.0.tar.xz
+cd qemu-6.1.0
+./configure
+make
+```
+Additional information:
+```
+[2150/9644] Compiling C object libqemu-alpha-softmmu.fa.p/migration_dirtyrate.c.o
+[2151/9644] Compiling C object libqemu-alpha-softmmu.fa.p/migration_ram.c.o
+[2152/9644] Compiling C object libqemu-alpha-softmmu.fa.p/target_alpha_fpu_helper.c.o
+[2153/9644] Compiling C object libqemu-aarch64-softmmu.fa.p/accel_tcg_translate-all.c.o
+[2154/9644] Compiling C object libqemu-alpha-softmmu.fa.p/migration_target.c.o
+[2155/9644] Compiling C object libqemu-aarch64-softmmu.fa.p/accel_tcg_cputlb.c.o
+FAILED: libqemu-aarch64-softmmu.fa.p/accel_tcg_cputlb.c.o
+gcc -Ilibqemu-aarch64-softmmu.fa.p -I. -I.. -Itarget/arm -I../target/arm -I../dtc/libfdt -I../capstone/include/capstone -Iqapi -Itrace -Iui -Iui/shader -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/valgrind -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -fdiagnostics-color=auto -Wall -Winvalid-pch -std=gnu11 -O2 -g -isystem /home/intel/Sources/qemu-6.1.0/linux-headers -isystem linux-headers -iquote . -iquote /home/intel/Sources/qemu-6.1.0 -iquote /home/intel/Sources/qemu-6.1.0/include -iquote /home/intel/Sources/qemu-6.1.0/disas/libvixl -iquote /home/intel/Sources/qemu-6.1.0/tcg/i386 -pthread -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -m64 -mcx16 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wold-style-declaration -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wimplicit-fallthrough=2 -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -g -O3 -feliminate-unused-debug-types -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -Wformat -Wformat-security -m64 -fasynchronous-unwind-tables -Wp,-D_REENTRANT -ftree-loop-distribute-patterns -Wl,-z -Wl,now -Wl,-z -Wl,relro -fno-semantic-interposition -ffat-lto-objects -fno-trapping-math -Wl,-sort-common -Wl,--enable-new-dtags -mtune=skylake -fPIE -isystem../linux-headers -isystemlinux-headers -DNEED_CPU_H '-DCONFIG_TARGET="aarch64-softmmu-config-target.h"' '-DCONFIG_DEVICES="aarch64-softmmu-config-devices.h"' -MD -MQ libqemu-aarch64-softmmu.fa.p/accel_tcg_cputlb.c.o -MF libqemu-aarch64-softmmu.fa.p/accel_tcg_cputlb.c.o.d -o libqemu-aarch64-softmmu.fa.p/accel_tcg_cputlb.c.o -c ../accel/tcg/cputlb.c
+during GIMPLE pass: fab
+In file included from /home/intel/Sources/qemu-6.1.0/include/qemu/osdep.h:37,
+                 from ../accel/tcg/cputlb.c:20:
+../accel/tcg/atomic_common.c.inc: In function ‘helper_atomic_fetch_andb’:
+/home/intel/Sources/qemu-6.1.0/include/exec/helper-head.h:21:27: internal compiler error: in optimize_atomic_bit_test_and, at tree-ssa-ccp.c:3245
+   21 | #define HELPER(name) glue(helper_, name)
+      |                           ^~~~~~~
+/home/intel/Sources/qemu-6.1.0/include/qemu/compiler.h:35:21: note: in definition of macro ‘xglue’
+   35 | #define xglue(x, y) x
diff --git a/results/classifier/gemma3:12b/kernel/734 b/results/classifier/gemma3:12b/kernel/734
new file mode 100644
index 00000000..28d5fa70
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/734
@@ -0,0 +1,29 @@
+
+aarch64 tlb range invalidate is not accurate
+Description of problem:
+In this (https://gitlab.com/qemu-project/qemu/-/commit/84940ed82552d3c7c7327c83076b02cee7978257) commit, tlb range invalidate support is added, and I think qemu's range calculation is wrong.
+
+In `tlbi_aa64_range_get_length` function, `num`, `scale`, `page_size_granule` is caculated as below.
+
+
+```
+    num = extract64(value, 39, 4);
+    scale = extract64(value, 44, 2);
+    page_size_granule = extract64(value, 46, 2);
+
+    page_shift = page_size_granule * 2 + 12;
+```
+
+As [Arm documentation](https://developer.arm.com/documentation/ddi0595/2021-06/AArch64-Instructions/TLBI-RVALE1--TLBI-RVALE1NXS--TLB-Range-Invalidate-by-VA--Last-level--EL1), NUM bits's length is 5, but the code above only extract 4bits.
+
+And `page_shift` also should be calculated as `(page_size_granule-1) <<1) + 12` rather than `page_size_granule * 2 + 12`.
+Steps to reproduce:
+1.
+2.
+3.
+Additional information:
+I found this issue while debugging a phenomenon that kernel panic occurs randomly in my qemu fork.
+
+I'm pretty sure this is one of the causes, but even if I roughly correct it, my problem has not been solved.
+
+I think my problem is TLB invalidate related issue, so if I find any more problems, I'll comment here.
diff --git a/results/classifier/gemma3:12b/kernel/735752 b/results/classifier/gemma3:12b/kernel/735752
new file mode 100644
index 00000000..aed8e4c1
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/735752
@@ -0,0 +1,62 @@
+
+qemu squeeze crashes "BUG: unable to handle kernel NULL pointer dereference at           (null)"
+
+my virtual machine server (qemu+libvirt) regularly breaks down with such a record in the logs
+I can not even ping the guest, but i can ping host, but can not do something with it (cannot ssh login for example)
+And I dont know how to reproduce the problem :(
+
+Mar 15 17:58:04 mainhost kernel: [65866.976982] BUG: unable to handle kernel NULL pointer dereference at           (null)                                    
+Mar 15 17:58:04 mainhost kernel: [65866.977422] IP: [<ffffffff8100efbe>] 0xffffffff8100efbe                                                                  
+Mar 15 17:58:04 mainhost kernel: [65866.977663] PGD 7387b7067 PUD 81b723067 PMD 0.                                                                           
+Mar 15 17:58:04 mainhost kernel: [65866.977902] Oops: 0000 [#1] SMP.                                                                                         
+Mar 15 17:58:04 mainhost kernel: [65866.978128] last sysfs file: /sys/devices/system/cpu/cpu3/topology/thread_siblings                                       
+Mar 15 17:58:04 mainhost kernel: [65866.978572] CPU 1.                                                                                                       
+Mar 15 17:58:04 mainhost kernel: [65866.978577] Modules linked in: nfs lockd nfs_acl auth_rpcgss sunrpc ebtable_nat ebtables coretemp bridge stp llc xt_state
+Mar 15 17:58:04 mainhost kernel: [65866.979737].                                                                                                             
+Mar 15 17:58:04 mainhost kernel: [65866.979959] Pid: 3369, comm: qemu-system-x86 Not tainted 2.6.37-gentoo-r2 #2 Intel S5000VSA/S5000VSA                     
+Mar 15 17:58:04 mainhost kernel: [65866.980085] RIP: 0010:[<ffffffff8100efbe>]  [<ffffffff8100efbe>] 0xffffffff8100efbe                                      
+Mar 15 17:58:04 mainhost kernel: [65866.980085] RSP: 0018:ffff880738767a48  EFLAGS: 00010246                                                                 
+Mar 15 17:58:04 mainhost kernel: [65866.980085] RAX: 0000000000000000 RBX: fffffffffffff001 RCX: ffff88081cbeb948                                            
+Mar 15 17:58:04 mainhost kernel: [65866.980085] RDX: 0000000000000022 RSI: fffffffffffff001 RDI: ffff88081cbeb000                                            
+Mar 15 17:58:04 mainhost kernel: [65866.980085] RBP: 0000000000000001 R08: 00000000000fee01 R09: 0000000000000022                                            
+Mar 15 17:58:04 mainhost kernel: [65866.980085] R10: 0000008000000000 R11: ffffea0000000000 R12: ffff880818d83490                                            
+Mar 15 17:58:04 mainhost kernel: [65866.980085] R13: 00000000155e5000 R14: 0000000000000000 R15: 0000000000000100                                            
+Mar 15 17:58:04 mainhost kernel: [65866.980085] FS:  00007f5f25e4e700(0000) GS:ffff88009f680000(0000) knlGS:fffff80001175000                                 
+Mar 15 17:58:04 mainhost kernel: [65866.980085] CS:  0010 DS: 002b ES: 002b CR0: 000000008005003b                                                            
+Mar 15 17:58:04 mainhost kernel: [65866.980085] CR2: 0000000000000000 CR3: 0000000806be9000 CR4: 00000000000426e0                                            
+Mar 15 17:58:04 mainhost kernel: [65866.980085] DR0: 0000000000000045 DR1: 0000000000000000 DR2: 0000000000000000                                            
+Mar 15 17:58:04 mainhost kernel: [65866.980085] DR3: 0000000000000005 DR6: 00000000ffff0ff0 DR7: 0000000000000400                                            
+Mar 15 17:58:04 mainhost kernel: [65866.980085] Process qemu-system-x86 (pid: 3369, threadinfo ffff880738766000, task ffff8808203ac360)                      
+Mar 15 17:58:04 mainhost kernel: [65866.980085] Stack:                                                                                                       
+Mar 15 17:58:04 mainhost kernel: [65866.980085]  0000000000000000 ffff8806a30f3ff8 ffff880753980000 ffffffff8100f06f                                         
+Mar 15 17:58:04 mainhost kernel: [65866.980085]  0000000000000ff8 ffff8807705d6b40 0000000000000ff8 ffffffff810123f0                                         
+Mar 15 17:58:04 mainhost kernel: [65866.980085]  0000000000000000 0000000000000000 0000000000000000 0000000000000000                                         
+Mar 15 17:58:04 mainhost kernel: [65866.980085] Call Trace:                                                                                                  
+Mar 15 17:58:04 mainhost kernel: [65866.980085]  [<ffffffff8100f06f>] ? 0xffffffff8100f06f                                                                   
+Mar 15 17:58:04 mainhost kernel: [65866.980085]  [<ffffffff810123f0>] ? 0xffffffff810123f0                                                                   
+Mar 15 17:58:04 mainhost kernel: [65866.980085]  [<ffffffff8100f744>] ? 0xffffffff8100f744                                                                   
+Mar 15 17:58:04 mainhost kernel: [65866.980085]  [<ffffffff8100ffaf>] ? 0xffffffff8100ffaf                                                                   
+Mar 15 17:58:04 mainhost kernel: [65866.980085]  [<ffffffff810011f1>] ? 0xffffffff810011f1                                                                   
+Mar 15 17:58:04 mainhost kernel: [65866.980085]  [<ffffffff810142fc>] ? 0xffffffff810142fc                                                                   
+Mar 15 17:58:04 mainhost kernel: [65866.980085]  [<ffffffff8100834d>] ? 0xffffffff8100834d                                                                   
+Mar 15 17:58:04 mainhost kernel: [65866.980085]  [<ffffffff81011af6>] ? 0xffffffff81011af6                                                                   
+Mar 15 17:58:04 mainhost kernel: [65866.980085]  [<ffffffff8100c5a7>] ? 0xffffffff8100c5a7                                                                   
+Mar 15 17:58:04 mainhost kernel: [65866.980085]  [<ffffffff81003a85>] ? 0xffffffff81003a85                                                                   
+Mar 15 17:58:04 mainhost kernel: [65866.980085]  [<ffffffff810e19b0>] ? 0xffffffff810e19b0                                                                   
+Mar 15 17:58:04 mainhost kernel: [65866.980085]  [<ffffffff81078cd8>] ? 0xffffffff81078cd8                                                                   
+Mar 15 17:58:04 mainhost kernel: [65866.980085]  [<ffffffff810e1a39>] ? 0xffffffff810e1a39                                                                   
+Mar 15 17:58:04 mainhost kernel: [65866.980085]  [<ffffffff810267fb>] ? 0xffffffff810267fb                                                                   
+Mar 15 17:58:04 mainhost kernel: [65866.980085] Code: 8b 47 50 8d 50 01 85 c0 89 57 50 75 07 41 58 e9 32 ff ff ff 5f c3 55 89 d5 53 48 89 f3 48 83 ec 08 e8 d
+Mar 15 17:58:04 mainhost kernel: [65866.980085] RIP  [<ffffffff8100efbe>] 0xffffffff8100efbe                                                                 
+Mar 15 17:58:04 mainhost kernel: [65866.980085]  RSP <ffff880738767a48>                                                                                      
+Mar 15 17:58:04 mainhost kernel: [65866.980085] CR2: 0000000000000000                                                                                        
+Mar 15 17:58:04 mainhost kernel: [65866.990753] ---[ end trace d147f74976c2654d ]---
+
+Linux mainhost 2.6.37-gentoo-r2 #2 SMP Mon Mar 14 22:53:20 MSK 2011 x86_64 Intel(R) Xeon(R) CPU E5405 @ 2.00GHz GenuineIntel GNU/Linux
+
+app-emulation/qemu-kvm-0.13.0-r2
+app-emulation/libvirt-0.8.8-r1
+
+mainhost log # ps ax|grep qemu
+ 2957 ?        Sl    12:28 /usr/bin/qemu-system-x86_64 --enable-kvm -S -M pc-0.13 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name dc1 -uuid f090bfc9-1cab-e4e9-51ea-80c9cc775bff -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/dc1.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -boot order=c,menu=off -drive file=/dev/vm-storage/dc1,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=13,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:7e:a1:a7,bus=pci.0,addr=0x4 -usb -device usb-tablet,id=input0 -vnc 0.0.0.0:0,password -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3
+ 2982 ?        Rl    10:34 /usr/bin/qemu-system-x86_64 --enable-kvm -S -M pc-0.13 -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name transarchive -uuid b96a3481-1ad6-9329-387e-a1504a17d0ee -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/transarchive.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -boot order=c,menu=off -drive file=/dev/vm-storage/transarchive,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=13,id=hostnet0,vhost=on,vhostfd=17 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:a9:f8:06,bus=pci.0,addr=0x3 -usb -device usb-tablet,id=input0 -vnc 0.0.0.0:3,password -vga std -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/744 b/results/classifier/gemma3:12b/kernel/744
new file mode 100644
index 00000000..54a46de4
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/744
@@ -0,0 +1,4 @@
+
+ppc64: Implement the remaining PowerISA v3.1 instructions
+Additional information:
+[PowerISA_public.v3.1.pdf](https://wiki.raptorcs.com/w/images/f/f5/PowerISA_public.v3.1.pdf)
diff --git a/results/classifier/gemma3:12b/kernel/749 b/results/classifier/gemma3:12b/kernel/749
new file mode 100644
index 00000000..c77037b4
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/749
@@ -0,0 +1,2 @@
+
+Enhance QEMU live patching
diff --git a/results/classifier/gemma3:12b/kernel/758 b/results/classifier/gemma3:12b/kernel/758
new file mode 100644
index 00000000..4cad89a9
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/758
@@ -0,0 +1,47 @@
+
+[Cross compilation] qemu: uncaught target signal 4 (Illegal instruction) - core dumped
+Description of problem:
+On the X86 platform, chroot to the latest MIP environment, download the source package, install the dependency, and then compile. It is found that the variation is in error
+
+Grab logs with GDB on the real machine
+
+Thread 1 "bash" received signal SIGSEGV, Segmentation fault.
+0x00007f094429c656 in code_gen_buffer ()
+(gdb) bt
+#0  0x00007f094429c656 in code_gen_buffer ()
+#1  0x000000000053878e in cpu_tb_exec (cpu=0x2441050, itb=<optimized out>, tb_exit=0x7ffd5bae38e8) at ../../accel/tcg/cpu-exec.c:353
+#2  0x000000000053965e in cpu_loop_exec_tb (tb_exit=0x7ffd5bae38e8, last_tb=<synthetic pointer>, tb=0x7f09441caac0 <code_gen_buffer+690835>, cpu=0x2441050) at ../../accel/tcg/cpu-exec.c:812
+#3  cpu_exec (cpu=cpu@entry=0x2441050) at ../../accel/tcg/cpu-exec.c:970
+#4  0x0000000000465b60 in cpu_loop (env=env@entry=0x2449340) at ../../linux-user/mips64/cpu_loop.c:78
+#5  0x0000000000413b27 in main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at ../../linux-user/main.c:910   
+(gdb) thread apply all bt
+
+Thread 2 (LWP 26312):
+#0  0x0000000000766a19 in syscall ()
+#1  0x000000000058ee0a in qemu_futex_wait (val=<optimized out>, f=<optimized out>) at ./include/qemu/trace-events:29
+#2  qemu_event_wait (ev=ev@entry=0xd44e68 <rcu_call_ready_event>) at ../../util/qemu-thread-posix.c:480
+#3  0x000000000059690a in call_rcu_thread (opaque=opaque@entry=0x0) at ./b/user-static/thread.h:258
+#4  0x000000000058dc29 in qemu_thread_start (args=<optimized out>) at ../../util/qemu-thread-posix.c:541
+#5  0x00000000006e665e in start_thread (arg=0x7f094c9a3640) at pthread_create.c:463
+#6  0x000000000076836f in clone ()
+
+Thread 1 (LWP 26310):
+#0  0x00007f094429c656 in code_gen_buffer ()
+#1  0x000000000053878e in cpu_tb_exec (cpu=0x2441050, itb=<optimized out>, tb_exit=0x7ffd5bae38e8) at ../../accel/tcg/cpu-exec.c:353
+#2  0x000000000053965e in cpu_loop_exec_tb (tb_exit=0x7ffd5bae38e8, last_tb=<synthetic pointer>, tb=0x7f09441caac0 <code_gen_buffer+690835>, cpu=0x2441050) at ../../accel/tcg/cpu-exec.c:812
+#3  cpu_exec (cpu=cpu@entry=0x2441050) at ../../accel/tcg/cpu-exec.c:970
+#4  0x0000000000465b60 in cpu_loop (env=env@entry=0x2449340) at ../../linux-user/mips64/cpu_loop.c:78
+#5  0x0000000000413b27 in main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at ../../linux-user/main.c:910
+(gdb) 
+```
+Steps to reproduce:
+```
+1.Minimum environment for building MIPS platform on 
+2.On X86 platform sudo chroot .
+3.cd build
+4.apt source adwaita-icon-theme
+5.cd adwaita-icon-theme-3.30.1
+6.debuild -b
+```
+Additional information:
+
diff --git a/results/classifier/gemma3:12b/kernel/760976 b/results/classifier/gemma3:12b/kernel/760976
new file mode 100644
index 00000000..61ab8595
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/760976
@@ -0,0 +1,15 @@
+
+Nexenta 3.0.1 fails to install
+
+The latest git version of qemu (commit 420b6c317de87890e06225de6e2f8af7bf714df0) fails to boot Nexenta3.0.1. I don't know if this is a bug in nextenta, or in QEMU or both.
+
+You can obtain a bootable image of Nextenta from http://www.nexenta.org/releases/nexenta-core-platform_3.0.1-b134_x86.iso.zip
+
+Host: Linux/x86_64 gcc4.5 ./configure --enable-linux-aio --enable-io-thread --enable-kvm
+
+qemu-img create nexenta3.0.1 3G
+qemu -hda nexenta3.0.1 -cdrom nexenta-core-platform3.0.1-b134x86.iso -boot d -k en-us -m 256
+
+Boots to grub OK, but when you hit install you get panic[cpu0]/thread=fec226c0: vmem_hash_delete(d4404690, d445abc0, 0): bad free.
+
+You get the same error with or without -enable-kvm
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/788881 b/results/classifier/gemma3:12b/kernel/788881
new file mode 100644
index 00000000..f600d308
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/788881
@@ -0,0 +1,17 @@
+
+i386-bsd-user and similar don't build on Mac OS X
+
+0.14.1 crashes on Mac OS X 64bit with some targets (*-bsd-user):
+
+  CC    i386-bsd-user/cpu-exec.o
+/Users/michael/Downloads/qemu-0.14.1/cpu-exec.c: In function ‘cpu_x86_signal_handler’:
+/Users/michael/Downloads/qemu-0.14.1/cpu-exec.c:895: error: dereferencing pointer to incomplete type
+/Users/michael/Downloads/qemu-0.14.1/cpu-exec.c:895: error: ‘REG_RIP’ undeclared (first use in this function)
+/Users/michael/Downloads/qemu-0.14.1/cpu-exec.c:895: error: (Each undeclared identifier is reported only once
+/Users/michael/Downloads/qemu-0.14.1/cpu-exec.c:895: error: for each function it appears in.)
+/Users/michael/Downloads/qemu-0.14.1/cpu-exec.c:897: error: dereferencing pointer to incomplete type
+/Users/michael/Downloads/qemu-0.14.1/cpu-exec.c:897: error: ‘REG_TRAPNO’ undeclared (first use in this function)
+/Users/michael/Downloads/qemu-0.14.1/cpu-exec.c:898: error: dereferencing pointer to incomplete type
+/Users/michael/Downloads/qemu-0.14.1/cpu-exec.c:898: error: ‘REG_ERR’ undeclared (first use in this function)
+/Users/michael/Downloads/qemu-0.14.1/cpu-exec.c:899: error: dereferencing pointer to incomplete type
+make[1]: *** [cpu-exec.o] Error 1
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/796202 b/results/classifier/gemma3:12b/kernel/796202
new file mode 100644
index 00000000..440c56c1
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/796202
@@ -0,0 +1,33 @@
+
+Doing a 64 bit load from a 32 bit local APIC register is allowed
+
+Doing
+
+u64 lapic_idregister = (u64) fix_to_virt(FIX_APIC_BASE) + 0x20;
+
+and later in an interrupt handler
+
+movq (lapic_idregister), %rcx
+movq (%rcx), %rcx
+
+in a linux kernel module works in qemu 0.13.91 but not on real hardware (it simply reboots).
+On real hardware only
+
+movl (%rcx), %ecx
+
+works (also in qemu).
+
+Commandline:
+qemu-system-x86_64 \
+		-kernel $LINUXDIR/arch/x86_64/boot/bzImage \
+		-hda $BUILDROOTDIR/output/images/rootfs.ext2 \
+		-append "root=/dev/sda rw rootfstype=ext2 maxcpus=4" \
+		-cpu phenom \
+		-smp 4 \
+		-gdb tcp::1234 \
+		-net nic -net user
+
+Guest:
+Vanilla Linux Kernel 2.6.37.6 64-bit with buildroot
+
+Mikael Pettersson from the linux kernel mailinglist told me it's an accepts-invalid bug in qemu.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/817 b/results/classifier/gemma3:12b/kernel/817
new file mode 100644
index 00000000..f7a1b704
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/817
@@ -0,0 +1,2 @@
+
+linux-user: waitid leaves target siginfo uninitialized when info.si_pid is zero
diff --git a/results/classifier/gemma3:12b/kernel/822 b/results/classifier/gemma3:12b/kernel/822
new file mode 100644
index 00000000..27255772
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/822
@@ -0,0 +1,17 @@
+
+hw/ppc/vof.c:1033: undefined reference to `fdt_get_max_phandle' in qemu-6.1.1, qemu-6.2.0
+Description of problem:
+Compilation of the source code of 6.1.1 and 6.2.0 fails in the qemu-system-ppc target ath the linking stage. Specifically the error in both cases is 
+usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: libqemu-ppc-softmmu.fa.p/hw_ppc_vof.c.o: in function `vof_build_dt':
+/home/silviu/qemu-work/qemu-6.1.1/build/../hw/ppc/vof.c:1033: undefined reference to `fdt_get_max_phandle'
+
+(same error for 6.2.0)
+
+This system has qemu-5.2.0 installed, which is the default for Funtoo currently. There were no compilation errors with 5.2.0. 
+gcc is version 9.2.0
+Steps to reproduce:
+1. download qemu-6.1.1.tar.xz/qemu-6.2.0.tar.xz and uncompress
+2. configure
+3. make[error.txt](/uploads/c9a987870eff85e586ddb29a113f64a7/error.txt)
+Additional information:
+the final part of the build log attached as text
diff --git a/results/classifier/gemma3:12b/kernel/836 b/results/classifier/gemma3:12b/kernel/836
new file mode 100644
index 00000000..1d33c7c1
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/836
@@ -0,0 +1,86 @@
+
+qemu-riscv32: Syscall LSEEK returns -14 (EFAULT)
+Description of problem:
+The lseek() system call returns -14 (EFAULT) if the file descriptor is correct,
+which it should never do (According to the lseek(2) man page).
+
+Here is some demonstrative code:
+```
+/* System Call numbers, according to https://github.com/riscv-software-src/riscv-pk/blob/master/pk/syscall.h */
+.set SYS_OPENAT,  0x38
+.set SYS_CLOSE,   0x39
+.set SYS_LSEEK,   0x3e
+.set SYS_READ,    0x3f
+.set SYS_WRITE,   0x40
+.set SYS_EXIT,    0x5d
+
+.set SEEK_CUR,    1
+
+/* According to https://elixir.bootlin.com/linux/v5.16.2/C/ident/AT_FDCWD */
+.set AT_FDCWD,    (-100)
+
+.section .text
+.global _start
+_start:
+
+/* Open the file with SYS_OPENAT, because SYS_OPEN does not exist on riscv32 for some reason.
+   Effectively:
+   s0 = open(argv[1], 0, 0644); */
+li a7, SYS_OPENAT
+li a0, AT_FDCWD
+lw a1, 8(sp)
+li a2, 0
+li a3, 0644
+ecall
+
+/* Error checking. This succeeds. */
+blt a0, zero, unrelated_error
+
+mv s0, a0
+
+/* The broken lseek() call.
+   Same also happens no matter the position in the file.
+   Effectively:
+   lseek(s0, 0, SEEK_CUR); */
+li a7, SYS_LSEEK
+mv a0, s0
+li a1, 0
+li a2, SEEK_CUR
+ecall
+
+/* XXX: lseek() returns -14 */
+blt a0, zero, lseek_error
+
+/* Close the file. */
+li a7, SYS_CLOSE
+mv a0, s0
+ecall
+
+/* Error checking. This also succeeds. */
+blt a0, zero, unrelated_error
+
+/* exit(0); */
+li a7, SYS_EXIT
+li a0, 0
+ecall
+
+/* exit(-return_value); */
+lseek_error:
+li a7, SYS_EXIT
+sub a0, zero, a0
+ecall
+
+unrelated_error:
+li a7, SYS_EXIT
+li a0, 128
+ecall
+```
+Steps to reproduce:
+1. riscv32-unknown-linux-gnu-as test.s -o test.o
+2. riscv32-unknown-linux-gnu-ld test.o
+3. qemu-riscv32 ./a.out test
+4. echo $? # This returns 14
+Additional information:
+Complete test setup:
+
+[test.tgz](/uploads/af68c9a5236628a9c6f31f2ce94e2f04/test.tgz)
diff --git a/results/classifier/gemma3:12b/kernel/842 b/results/classifier/gemma3:12b/kernel/842
new file mode 100644
index 00000000..07bf66f3
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/842
@@ -0,0 +1,14 @@
+
+ppc64: hard lockup / hang in Linux kernel v5.17-rc1
+Description of problem:
+The kernel deterministically triggers a hard lockup / hang under QEMU since v5.17-rc1 (upgrading from v5.16).
+
+Bisecting points to the kernel's [0faf20a1ad16](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0faf20a1ad1647c0fc0f5a367c71e5e84deaf899) ("powerpc/64s/interrupt: Don't enable MSR[EE] in irq handlers unless perf is in use"). Reverting it on top of v5.17-rc1 fixes the issue.
+
+Reported to [linuxppc-dev](https://lore.kernel.org/linuxppc-dev/CANiq72n_FmDx=r-o9J8gYc6LpwRL5EGmhM6Xzwv27Xc7h1TNDw@mail.gmail.com/). Confirmed. Suspected QEMU modeling issue by Cédric Le Goater.
+Steps to reproduce:
+1. Build kernel v5.17-rc1 or commit 0faf20a1ad16 for ppc64le with the attached config (either GCC or Clang).
+2. Run it under QEMU with at least `-smp 2`.
+Additional information:
+[qemu-and-dmesg.log](/uploads/7cb5ce1cb70e06262800c16f4c800157/qemu-and-dmesg.log)
+[kernel.config](/uploads/327e9cec48a731abc9e44cb40db67de9/kernel.config)
diff --git a/results/classifier/gemma3:12b/kernel/846 b/results/classifier/gemma3:12b/kernel/846
new file mode 100644
index 00000000..490fc9e7
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/846
@@ -0,0 +1,2 @@
+
+Why qemu crashes and calling SYS_SECCOMP function
diff --git a/results/classifier/gemma3:12b/kernel/854 b/results/classifier/gemma3:12b/kernel/854
new file mode 100644
index 00000000..343ee854
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/854
@@ -0,0 +1,63 @@
+
+rsync to ext4-fs on dynamic expanding qcow2 fails
+Description of problem:
+Firstly, this issue does not seem to happen when the virtual-disk is dd-raw-img or fixed qcow2 (preallocation=falloc). The guest-kernel has multiple tracebacks during rsync to dst folder on ext4-fs on qcow2. 
+I ctrl-C-ed the rsync process after the first traceback, which happened after copying around 52 GiB. 
+On a previous run, wherein I had let it continue, somewhere near the end, around 83 GiB, dmesg would bloat with a zillion trace-backs and stall. The sha256sum verify seems to have succeeded for all files copied so far and correctly gives error "Failed open or read" on subsequent files that were not copied. 
+In this test, the partial-rsync completed files were not corrupted. However, as qemu's disk emulation allocates blocks, qemu may be inducing paging-bugs into the guest-kernel. Paging issues like these may also lead to corruption. The guest-kernel should see the same full emulated disk regardless of whether qemu provided a fixed disk, dynamic disk, or even a different type of virtual-disk-format. The guest-vm should not detect/perceive any difference between them.
+
+There may be upcoming trouble round the 5.17 corner.
+
+It is beyond me to figure out if this is due to
+* qemu-6.2 block code
+* guest-kernel ( kernel-5.17 folio/page management or ntfs3 driver or something else )  
+
+It may be necessary to ascertain if this is a new bug on account of qemu not being ready for folio type page-management or a bug in upstream kernel.org. My apologies in advance if it turns out that this is not a qemu bug.
+
+There there does seem to be some problem with qemu dealing with expanding virtual disks, with bugs that show up only if the underlying virtual-disk is dynamic and expanding.
+
+I just think that storage/block-code should be made rock solid with a much higher priority than adding new features.
+If storage code is undependable, then qemu/vm cannot be used, and there is no point in any other feature. qcow2 in particular is the qemu's native virtual-disk format.
+
+I had to stop testing on Issue #727 , Issue #814 , on account of what I thought was a bug in 5.15 kernels. I filed the bug as "fs/ntfs3: page_cache_ra_unbounded on rsync from ntfs3 to ext4" https://bugzilla.kernel.org/show_bug.cgi?id=215460 . I assume that bug is different because it happens even on raw image. 
+
+setup is as follows:
+- Host: Fedora-35 with kernel-5.17.0-0.rc2.83.fc35.x86_64 self-built from srpm ( https://koji.fedoraproject.org/koji/buildinfo?buildID=1910212 )
+- Guest: Fedora-Workstation-Live-x86_64-Rawhide-20220201.n.0.iso with 5.17.0-0.rc2.83.fc36.x86_64 ( https://koji.fedoraproject.org/koji/buildinfo?buildID=1910892 )  
+- qemu: 6.2.0 (qemu-6.2.0-2.fc35.1) self-built from srpm  ( https://koji.fedoraproject.org/koji/buildinfo?buildID=1897713 )
+- hda: qcow2(dyn) with ext4 and also 4 combinations of raw_img/fixed_qcow2 with ext4/ntfs3
+- hdb: vhdx, ntfs3 (pre-prepared sgdata https://gitlab.com/qemu-project/qemu/-/issues/727#note_739930694 )  
+
+qcow2 image is created as follows:
+``` 
+[root@sirius ~]# qemu-img create -f qcow2 /mnt/a16/gkpics01.qcow2 99723771904
+Formatting '/mnt/a16/gkpics01.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off compression_type=zlib size=99723771904 lazy_refcounts=off refcount_bits=16 
+```
+
+qemu command is as follows:
+``` 
+[root@sirius ~]# qemu-system-x86_64 -cpu qemu64 -m 4096 -machine "type=q35" -accel "kvm" -smp "sockets=1,cores=8,threads=1" -boot "d" -cdrom "/vol/15KJ_Images/transcend/Fedora-Workstation-Live-x86_64-Rawhide-20220201.n.0.iso" -hda "/mnt/a16/gkpics01.raw" -hdb "/vol/15KJ_Images/test/sgdata.vhdx" -device "virtio-vga" -display "gtk,gl=on" -rtc "base=utc" -net "user" -device "virtio-net,netdev=vmnic" -netdev "user,id=vmnic,net=192.168.20.0/24,dns=192.168.20.3,dhcpstart=192.168.20.15" 
+```
+Steps to reproduce:
+1. Inside booted vm, use gdisk to partition /dev/sda1 if necessary
+2. ```dmesg -w (in another pty)``` 
+3. ```mkfs.ext4 /dev/sda1 -L fs_gkpics001``` 
+4. ```mkdir /mnt/a /mnt/b``` 
+5. ```mount -t ext4 /dev/sda1 /mnt/a``` 
+6. ```mount -t ntfs3 /dev/sdb2 /mnt/b```
+7. rsync testdata: ```(sdate=`date` ; echo "$sdate" ; cd /mnt/b ; rsync -avH ./photos001 /mnt/a | tee /tmp/rst.txt ; echo "$sdate" ; date )``` 
+8. ```umount /mnt/a ; ``` 
+9. ```mount -t ext4 /dev/sda1 /mnt/a``` 
+10. verify: ```(sdate=`date` ; echo "$sdate" ; cd /mnt/a/photos001 ; sha256sum -c ./find.CHECKSUM --quiet ; echo "$sdate" ; date )``` 
+11. ```umount /mnt/a ; umount /mnt/b;```
+Additional information:
+**Test attempts**
+- Bug does not happen with 5.17.0-0.rc2.83/qemu-6.2.0-2/5.17.0-0.rc2.83/ExFAT/rawimg/ext4 with vhdx/ntfs3/sgdata 
+- Bug does not happen with 5.17.0-0.rc2.83/qemu-6.2.0-2/5.17.0-0.rc2.83/ExFAT/rawimg/ntfs3 with vhdx/ntfs3/sgdata 
+- Bug does not happen with 5.17.0-0.rc2.83/qemu-6.2.0-2/5.17.0-0.rc2.83/ExFAT/qcow2(fixed)/ext4 with vhdx/ntfs3/sgdata 
+- Bug does not happen with 5.17.0-0.rc2.83/qemu-6.2.0-2/5.17.0-0.rc2.83/ExFAT/qcow2(fixed)/ntfs3 with vhdx/ntfs3/sgdata 
+- Bug **does** happen with 5.17.0-0.rc2.83/qemu-6.2.0-2/5.17.0-0.rc2.83/ExFAT/**qcow2(dyn)**/ext4 with vhdx/ntfs3/sgdata 
+- Bug does not happen directly on Host with 5.17.0-0.rc2.83/ExFat with ntfs3/sgdata
+- Bug does not happen directly on Host with 5.17.0-0.rc2.83/ntfs3 with ntfs3/sgdata
+
+Also filed a linux-kernel bug titled "during rsync, vm guest kernel trace arising from memcg_kmem_charge_page alloc_pages" https://bugzilla.kernel.org/show_bug.cgi?id=215563
diff --git a/results/classifier/gemma3:12b/kernel/865518 b/results/classifier/gemma3:12b/kernel/865518
new file mode 100644
index 00000000..f32c3e38
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/865518
@@ -0,0 +1,38 @@
+
+qemu segfaults when writing to very large qcow2 disk
+
+Create a ridiculously large qcow2 disk:
+
+qemu-img create -f qcow2 test1.img $((2**63-513))
+
+Attach it to a guest and try to use parted to partition it.  This is easy with virt-rescue: you just do:
+
+virt-rescue test1.img
+><rescue> parted /dev/vda mklabel gpt
+<-- bang! qemu segfaults here
+
+The stack trace is:
+
+Program received signal SIGSEGV, Segmentation fault.
+0x0000000000434cac in get_cluster_table (bs=0x3193030, offset=
+    9223372036854764544, new_l2_table=0x591e3c8, new_l2_offset=0x591e3c0, 
+    new_l2_index=0x591e408) at block/qcow2-cluster.c:506
+506	    l2_offset = s->l1_table[l1_index];
+(gdb) bt
+#0  0x0000000000434cac in get_cluster_table (bs=0x3193030, offset=
+    9223372036854764544, new_l2_table=0x591e3c8, new_l2_offset=0x591e3c0, 
+    new_l2_index=0x591e408) at block/qcow2-cluster.c:506
+#1  0x000000000043535b in qcow2_alloc_cluster_offset (bs=0x3193030, offset=
+    9223372036854764544, n_start=106, n_end=126, num=0x591e4e8, m=0x591e470)
+    at block/qcow2-cluster.c:719
+#2  0x000000000043b8d4 in qcow2_co_writev (bs=0x3193030, sector_num=
+    18014398509481962, remaining_sectors=20, qiov=0x4a81ee0)
+    at block/qcow2.c:554
+#3  0x0000000000428691 in bdrv_co_rw (opaque=0x38bad10) at block.c:2781
+#4  0x000000000046e03a in coroutine_trampoline (i0=59487248, i1=0)
+    at coroutine-ucontext.c:125
+#5  0x00000034dc6471b0 in ?? () from /lib64/libc.so.6
+#6  0x00007fff76cbb430 in ?? ()
+#7  0x0000000000000000 in ?? ()
+
+This is qemu from git (8f440cda08c6df574 from 2011-09-29)
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/877 b/results/classifier/gemma3:12b/kernel/877
new file mode 100644
index 00000000..b7df4721
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/877
@@ -0,0 +1,107 @@
+
+qemu-system-x86_64: Linux kernel warning when CONFIG_NUMA_EMU is enabled
+Description of problem:
+When Linux kernel is run on qemu 6.2, it prints a warning when `NUMA_EMU` is used. When the same kernel is run on qemu 6.1.1 (`54e1f5be86dd11744e45da8be6afad01d01d59e7`) or earlier, no such warning is printed.
+
+```
+[    0.341924] smpboot: CPU0: Intel QEMU Virtual CPU version 2.5+ (family: 0xf, model: 0x6b, stepping: 0x1)
+[    0.342371] Performance Events: unsupported Netburst CPU model 107 no PMU driver, software events only.
+[    0.343302] rcu: Hierarchical SRCU implementation.
+[    0.344470] smp: Bringing up secondary CPUs ...
+[    0.345349] x86: Booting SMP configuration:
+[    0.345945] .... node  #1, CPUs:      #1
+[    0.014099] ------------[ cut here ]------------
+[    0.014099] sched: CPU #1's llc-sibling CPU #0 is not on the same node! [node: 1 != 0]. Ignoring dependency.
+[    0.014099] WARNING: CPU: 1 PID: 0 at arch/x86/kernel/smpboot.c:423 topology_sane.isra.0+0x62/0x70
+[    0.014099] Modules linked in:
+[    0.014099] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.16.9 #6
+[    0.014099] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014
+[    0.014099] RIP: 0010:topology_sane.isra.0+0x62/0x70
+[    0.014099] Code: 80 3d e1 72 a1 01 00 75 f6 48 83 ec 08 4c 89 da 44 89 d6 48 c7 c7 c0 cd f4 8b 88 44 24 07 c6 05 c3 72 a1 01 01 e8 3c 16 b7 00 <0f> 0b 0f b6 44 24 07 48 83 c4 08 c3 66 90 48 8b 0d 21 95 a3 01 0f
+[    0.014099] RSP: 0000:ffffa8c3006a3ed8 EFLAGS: 00010086
+[    0.014099] RAX: 0000000000000000 RBX: ffffa335fdc15480 RCX: 0000000000000000
+[    0.014099] RDX: 0000000000000002 RSI: 00000000ffffffea RDI: 00000000ffffffff
+[    0.014099] RBP: ffffa3353dc15480 R08: ffffffff8c335ac8 R09: 00000000ffffdfff
+[    0.014099] R10: ffffffff8c255ae0 R11: ffffffff8c255ae0 R12: 0000000000000001
+[    0.014099] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000001
+[    0.014099] FS:  0000000000000000(0000) GS:ffffa335fdc00000(0000) knlGS:0000000000000000
+[    0.014099] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
+[    0.014099] CR2: 0000000000000000 CR3: 0000000112a0c000 CR4: 00000000000006e0
+[    0.014099] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
+[    0.014099] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
+[    0.014099] Call Trace:
+[    0.014099]  <TASK>
+[    0.014099]  set_cpu_sibling_map+0x16a/0x560
+[    0.014099]  start_secondary+0x42/0xf0
+[    0.014099]  secondary_startup_64_no_verify+0xc2/0xcb
+[    0.014099]  </TASK>
+[    0.014099] Kernel panic - not syncing: panic_on_warn set ...
+[    0.014099] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.16.9 #6
+[    0.014099] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014
+[    0.014099] Call Trace:
+[    0.014099]  <TASK>
+[    0.014099]  dump_stack_lvl+0x34/0x44
+[    0.014099]  panic+0xef/0x2a6
+[    0.014099]  ? topology_sane.isra.0+0x62/0x70
+[    0.014099]  __warn.cold+0x26/0x30
+[    0.014099]  ? topology_sane.isra.0+0x62/0x70
+[    0.014099]  report_bug+0x9a/0xc0
+[    0.014099]  handle_bug+0x3c/0x60
+[    0.014099]  exc_invalid_op+0x14/0x70
+[    0.014099]  asm_exc_invalid_op+0x12/0x20
+[    0.014099] RIP: 0010:topology_sane.isra.0+0x62/0x70
+[    0.014099] Code: 80 3d e1 72 a1 01 00 75 f6 48 83 ec 08 4c 89 da 44 89 d6 48 c7 c7 c0 cd f4 8b 88 44 24 07 c6 05 c3 72 a1 01 01 e8 3c 16 b7 00 <0f> 0b 0f b6 44 24 07 48 83 c4 08 c3 66 90 48 8b 0d 21 95 a3 01 0f
+[    0.014099] RSP: 0000:ffffa8c3006a3ed8 EFLAGS: 00010086
+[    0.014099] RAX: 0000000000000000 RBX: ffffa335fdc15480 RCX: 0000000000000000
+[    0.014099] RDX: 0000000000000002 RSI: 00000000ffffffea RDI: 00000000ffffffff
+[    0.014099] RBP: ffffa3353dc15480 R08: ffffffff8c335ac8 R09: 00000000ffffdfff
+[    0.014099] R10: ffffffff8c255ae0 R11: ffffffff8c255ae0 R12: 0000000000000001
+[    0.014099] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000001
+[    0.014099]  ? topology_sane.isra.0+0x62/0x70
+[    0.014099]  set_cpu_sibling_map+0x16a/0x560
+[    0.014099]  start_secondary+0x42/0xf0
+[    0.014099]  secondary_startup_64_no_verify+0xc2/0xcb
+[    0.014099]  </TASK>
+[    0.014099] ---[ end Kernel panic - not syncing: panic_on_warn set ... ]---
+```
+Steps to reproduce:
+1. Check out the Linux kernel:
+```
+git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
+cd linux-stable
+git checkout v5.16.9
+```
+2. Generate the configuration file:
+```
+make defconfig
+./scripts/config -e NUMA_EMU -e CMDLINE_BOOL --set-str CMDLINE "numa=fake=2 panic_on_warn=1" -d CONFIG_CMDLINE_OVERRIDE
+```
+3. Build the kernel
+```
+make -j32
+```
+4. Run qemu and wait for a couple of seconds:
+```
+./qemu-system-x86_64 -m 4G -smp 2 -kernel ~/linux-stable/arch/x86/boot/bzImage -append "console=ttyS0 root=/dev/sda earlyprintk=serial" -enable-kvm -nographic -snapshot
+```
+Additional information:
+With explicit NUMA configuration, it boots fine:
+```
+./qemu-system-x86_64 -m 4G -smp 2 -object memory-backend-ram,size=8G,id=m0 -numa node,cpus=0-1,nodeid=0,memdev=m0 -kernel ~/linux-stable/arch/x86/boot/bzImage -append "console=ttyS0 root=/dev/sda earlyprintk=serial" -enable-kvm -nographic -snapshot
+```
+
+On the host machine:
+```
+$ numactl -H
+available: 2 nodes (0-1)
+node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53
+node 0 size: 95259 MB
+node 0 free: 1767 MB
+node 1 cpus: 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71
+node 1 size: 96757 MB
+node 1 free: 2407 MB
+node distances:
+node   0   1 
+  0:  10  21 
+  1:  21  10 
+```
diff --git a/results/classifier/gemma3:12b/kernel/881 b/results/classifier/gemma3:12b/kernel/881
new file mode 100644
index 00000000..5ee00adb
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/881
@@ -0,0 +1,21 @@
+
+qemu-ga fs-freeze causes VM to
+Description of problem:
+I have fresh install of Debian 11 and installed MariaDB 10.7 from MariaDB's Repo. Guest is fully up to date.
+When Proxmox goes to do a backup it will call fs-freeze to the VM via the agent which then causes the backup process to hang and the VM will lockup or causes kernel message such as `**task qemu-ga:370 blocked for more than 120 seconds**`. The VM from what I can tell no longer is able to write to disk, and the only fix is to force reset the VM.
+
+The issue doesn't happen when the VM has first started or the agent has been restart from what I can tell, but if you leave it and wait for the nightly backup to run of the VM, it will then cause this issue to happen.
+
+There are other reports of this happening on the [proxmox forums](https://forum.proxmox.com/threads/snapshot-backup-not-working-guest-agent-fs-freeze-gets-timeout.99887/) More details on this topic. Other reports with the issue with MariaDB 10.6.
+
+My other Debian 11 VMs which were also setup recently, do not experience this problem, only difference is this VM is running the MariaDB. I have Gitlab, Docker, Mailcow, PowerDNS, OPNsense (each of these separate VM) in the other VMs and they do not experience this issue. All these VMs are running Debian 11.
+
+Agent Info
+```
+qemu-guest-agent/stable,stable-security,now 1:5.2+dfsg-11+deb11u1 amd64
+```
+Steps to reproduce:
+1. Install Proxmox (although I would assume any QEMU 6.1.1)
+2. Create a Debian 11 guest with MariaDB 10.7 from MariaDB repo
+3. Wait good few hours
+4. Issue a backup or fs-freeze
diff --git a/results/classifier/gemma3:12b/kernel/883 b/results/classifier/gemma3:12b/kernel/883
new file mode 100644
index 00000000..a4298fc4
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/883
@@ -0,0 +1,28 @@
+
+DRBG: could not allocate CTR cipher TFM handle: ctr(aes)
+Description of problem:
+
+Steps to reproduce:
+1. Install Debian in Qemu using the command:
+```
+REM example to create disk
+REM qemu-img create -f qcow2 debian-qcow2.img 32G 
+
+qemu-system-x86_64.exe -hda debian-qcow2.img -cdrom debian-11.2.0-amd64-netinst.iso -boot d -m 8G -accel hax
+```
+
+2. Fight with installer and partitions to finally get this:
+![lfs-ftw-128_-_Screenshot_2022-02-22_202452](/uploads/a823feb358c456bd4d76b181ca689bec/lfs-ftw-128_-_Screenshot_2022-02-22_202452.png)
+
+3. System boots and shows a bunch of FAILED messages with crypto error:
+![lfs-ftw-144_-_Screenshot_2022-02-22_223848](/uploads/bf8922239d9bbf0ee26c9ffafdf81f2e/lfs-ftw-144_-_Screenshot_2022-02-22_223848.png)
+
+![lfs-ftw-139_-_Screenshot_2022-02-22_213744](/uploads/9ad52214610fa3a54ed3263e122ae395/lfs-ftw-139_-_Screenshot_2022-02-22_213744.png)
+
+I am new at using Qemu so may need pointers to provide more information.
+
+The system seems to be working to some degree.
+
+Color me impressed!!!
+Additional information:
+Related: #880
diff --git a/results/classifier/gemma3:12b/kernel/886 b/results/classifier/gemma3:12b/kernel/886
new file mode 100644
index 00000000..1afae55f
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/886
@@ -0,0 +1,17 @@
+
+OpenIndiana panics when using -accel hvf
+Description of problem:
+OpenIndiana panics on boot.
+
+```
+Loading unix...
+Loading /platform/i86pc/amd64/boot_archive...
+Loading /platform/i86pc/amd64/boot_archive.hash...
+Booting...
+OpenIndiana Hipster 2021.10 Version illumos-79a6379db8 64-bit
+
+panic[cpu0]/thread=fffffffffbc49060:
+```
+Steps to reproduce:
+1. Run given command
+2. Wait
diff --git a/results/classifier/gemma3:12b/kernel/887 b/results/classifier/gemma3:12b/kernel/887
new file mode 100644
index 00000000..fad729d7
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/887
@@ -0,0 +1,2 @@
+
+OSX Sorbet Leopard 10.5.9 on QEMU ?
diff --git a/results/classifier/gemma3:12b/kernel/897193 b/results/classifier/gemma3:12b/kernel/897193
new file mode 100644
index 00000000..3f040799
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/897193
@@ -0,0 +1,44 @@
+
+virtfs: kernel compile fails
+
+I am trying to compile a kernel under virtfs, and am getting an error.  The error does not occur when compiling outside of the virtfs mount.
+
+Both guest and host are running the 3.0.4 kernel.
+QEMU is latest from git: bc75c9e50d308b2ec6623a40179c5cdc84b63dae
+
+QEMU command line:
+/usr/local/bin/qemu-system-x86_64 -nographic -boot c -m 1024 -machine type=pc,accel=kvm -drive file=/root/hdd1.img,if=virtio -drive file=/root/test1.img,if=virtio -drive file=/root/test2.img,if=virtio -virtfs local,path=/mnt/virtfs,security_model=none,mount_tag=virtfs -net nic,model=virtio,macaddr=DE:AD:BE:EF:AA:BB -net tap,ifname=qtap0,script=no
+
+virtfs line in /etc/fstab:
+virtfs                  /mnt/virtfs             9p      defaults,noauto,trans=virtio    0 0
+
+Steps to reproduce and output:
+
+[root@guest linux-3.0.4]# make mrproper
+  CLEAN   scripts/basic
+  CLEAN   scripts/kconfig
+  CLEAN   include/config include/generated
+  CLEAN   .config .config.old
+[root@guest linux-3.0.4]# make defconfig
+  HOSTCC  scripts/basic/fixdep
+  HOSTCC  scripts/kconfig/conf.o
+  SHIPPED scripts/kconfig/zconf.tab.c
+  SHIPPED scripts/kconfig/lex.zconf.c
+  SHIPPED scripts/kconfig/zconf.hash.c
+  HOSTCC  scripts/kconfig/zconf.tab.o
+  HOSTLD  scripts/kconfig/conf
+*** Default configuration is based on 'x86_64_defconfig'
+#
+# configuration written to .config
+#
+[root@guest linux-3.0.4]# make
+scripts/kconfig/conf --silentoldconfig Kconfig
+
+*** Error during update of the configuration.
+
+make[2]: *** [silentoldconfig] Error 1
+make[1]: *** [silentoldconfig] Error 2
+make: *** No rule to make target `include/config/auto.conf', needed by `include/config/kernel.release'.  Stop.
+
+
+Please let me know if you need any other information.  Thanks!
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/902720 b/results/classifier/gemma3:12b/kernel/902720
new file mode 100644
index 00000000..49ea6b34
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/902720
@@ -0,0 +1,17 @@
+
+TIME_MAX not set correctly for OpenBSD in qemu-common.h
+
+Looking at the OpenBSD buildbot logs I noticed a warning that appears to be a bug in the code.
+OpenBSD has a 32-bit time_t on all archs at the moment (32-bit and 64-bit).
+
+  CC    i386-softmmu/monitor.o
+/buildbot-qemu/default_openbsd_current/build/monitor.c: In function 'expire_password':
+/buildbot-qemu/default_openbsd_current/build/monitor.c:944: warning: overflow in implicit constant conversion
+
+qemu-common.h has...
+
+#ifndef TIME_MAX
+#define TIME_MAX LONG_MAX
+#endif
+
+for OpenBSD this should be INT_MAX.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/903 b/results/classifier/gemma3:12b/kernel/903
new file mode 100644
index 00000000..a355709e
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/903
@@ -0,0 +1,356 @@
+
+m1 MacOS panic testing lima with qemu HEAD/7.0.0
+Description of problem:
+I'm trying to help the `lima` project test the latest version of lima on m1 with the latest qemu https://github.com/lima-vm/lima/issues/713 and I got a panic and was told to report back in the qemu issue tracker.
+
+I created a VM with 8GiB memory, and got a panic.
+
+
+lima version:
+```
+⎈ |rancher-desktop:default) ~ ❯❯❯ limactl --version                                                                                                                                                                                                                                                                                            ✘ 1 
+limactl version HEAD-1164273
+```
+
+qemu version:
+```
+(⎈ |rancher-desktop:default) ~ ❯❯❯ qemu-system-aarch64 --version
+QEMU emulator version 6.2.50 (v6.2.0-2380-g1416688c53)
+Copyright (c) 2003-2022 Fabrice Bellard and the QEMU Project developers
+```
+
+MacOS panic:
+
+```
+panic(cpu 3 caller 0xfffffe001db6ea58): vm_fault() KERN_FAILURE from guest fault on state 0xfffffe6032c98000 @sleh.c:3091
+Debugger message: panic
+Memory ID: 0x6
+OS release type: User
+OS version: 21A559
+Kernel version: Darwin Kernel Version 21.1.0: Wed Oct 13 17:33:01 PDT 2021; root:xnu-8019.41.5~1/RELEASE_ARM64_T6000
+Fileset Kernelcache UUID: 3B2CA3833A09A383D66FB36667ED9CBF
+Kernel UUID: 67BCB41B-BAA4-3634-8E51-B0210457E324
+iBoot version: iBoot-7429.41.5
+secure boot?: YES
+Paniclog version: 13
+KernelCache slide: 0x00000000160d8000
+KernelCache base:  0xfffffe001d0dc000
+Kernel slide:      0x0000000016900000
+Kernel text base:  0xfffffe001d904000
+Kernel text exec slide: 0x00000000169e8000
+Kernel text exec base:  0xfffffe001d9ec000
+mach_absolute_time: 0x1661a3f15fc
+Epoch Time:        sec       usec
+  Boot    : 0x622a7219 0x00029f9b
+  Sleep   : 0x622ba92c 0x00061dca
+  Wake    : 0x622ba9d3 0x000ae46d
+  Calendar: 0x622bc0fb 0x000caf67
+
+Zone info:
+Foreign   : 0xfffffe0025c14000 - 0xfffffe0025c28000
+Native    : 0xfffffe10003bc000 - 0xfffffe30003bc000
+Readonly  : 0 - 0
+Metadata  : 0xfffffe64105d0000 - 0xfffffe641c53c000
+Bitmaps   : 0xfffffe641c53c000 - 0xfffffe6433f6c000
+CORE 0 PVH locks held: None
+CORE 1 PVH locks held: None
+CORE 2 PVH locks held: None
+CORE 3 PVH locks held: None
+CORE 4 PVH locks held: None
+CORE 5 PVH locks held: None
+CORE 6 PVH locks held: None
+CORE 7 PVH locks held: None
+CORE 8 PVH locks held: None
+CORE 9 PVH locks held: None
+CORE 0: PC=0xfffffe001da72c6c, LR=0xfffffe001da72c6c, FP=0xfffffe6110abbef0
+CORE 1: PC=0xfffffe001f2cdbe0, LR=0xfffffe001f2ceb54, FP=0xfffffe611027b600
+CORE 2: PC=0xfffffe001da72c70, LR=0xfffffe001da72c6c, FP=0xfffffe603778bef0
+CORE 3 is the one that panicked. Check the full backtrace for details.
+CORE 4: PC=0xfffffe001da72c6c, LR=0xfffffe001da72c6c, FP=0xfffffe61166fbef0
+CORE 5: PC=0xfffffe001da72c70, LR=0xfffffe001da72c6c, FP=0xfffffe6110a6bef0
+CORE 6: PC=0xfffffe001da72c70, LR=0xfffffe001da72c6c, FP=0xfffffe61121cbef0
+CORE 7: PC=0xfffffe001da72c70, LR=0xfffffe001da72c6c, FP=0xfffffe60b4be3ef0
+CORE 8: PC=0xfffffe001da72c70, LR=0xfffffe001da72c6c, FP=0xfffffe6032af3ef0
+CORE 9: PC=0xfffffe001da72c70, LR=0xfffffe001da72c6c, FP=0xfffffe6090a4bef0
+Panicked task 0xfffffe150e4ccd50: 17757 pages, 10 threads: pid 21141: qemu-system-aarc
+Panicked thread: 0xfffffe1515ae87d8, backtrace: 0xfffffe60d51e3300, tid: 979402
+		  lr: 0xfffffe001da3e488  fp: 0xfffffe60d51e3370
+		  lr: 0xfffffe001da3e158  fp: 0xfffffe60d51e33e0
+		  lr: 0xfffffe001db7a558  fp: 0xfffffe60d51e3400
+		  lr: 0xfffffe001db6d2d4  fp: 0xfffffe60d51e3480
+		  lr: 0xfffffe001db6ac9c  fp: 0xfffffe60d51e3540
+		  lr: 0xfffffe001d9f37f8  fp: 0xfffffe60d51e3550
+		  lr: 0xfffffe001da3ddcc  fp: 0xfffffe60d51e38f0
+		  lr: 0xfffffe001da3ddcc  fp: 0xfffffe60d51e3960
+		  lr: 0xfffffe001e23c748  fp: 0xfffffe60d51e3980
+		  lr: 0xfffffe001db6ea58  fp: 0xfffffe60d51e39e0
+		  lr: 0xfffffe001db6e5dc  fp: 0xfffffe60d51e3a50
+		  lr: 0xfffffe001d9fe828  fp: 0xfffffe60d51e3a60
+		  lr: 0xfffffe001db823f4  fp: 0xfffffe60d51e3e50
+		  lr: 0xfffffe001db6b140  fp: 0xfffffe60d51e3f10
+		  lr: 0xfffffe001d9f37f8  fp: 0xfffffe60d51e3f20
+
+last started kext at 1368960011: com.apple.filesystems.smbfs	4.0 (addr 0xfffffe001d8ea490, size 64483)
+loaded kexts:
+com.apple.filesystems.smbfs	4.0
+com.apple.filesystems.autofs	3.0
+com.apple.fileutil	20.036.15
+com.apple.UVCService	1
+com.apple.driver.AppleUSBTopCaseDriver	5010.1
+com.apple.iokit.SCSITaskUserClient	452.30.4
+com.apple.driver.AppleIntelI210Ethernet	2.3.1
+com.apple.driver.AppleBiometricServices	1
+com.apple.driver.CoreKDL	1
+com.apple.driver.AppleTopCaseHIDEventDriver	5010.1
+com.apple.driver.SEPHibernation	1
+com.apple.driver.BCMWLANFirmware4387.Hashstore	1
+com.apple.driver.DiskImages.ReadWriteDiskImage	493.0.0
+com.apple.driver.DiskImages.UDIFDiskImage	493.0.0
+com.apple.driver.DiskImages.RAMBackingStore	493.0.0
+com.apple.driver.DiskImages.FileBackingStore	493.0.0
+com.apple.filesystems.apfs	1933.41.2
+com.apple.driver.AppleUSBDeviceNCM	5.0.0
+com.apple.driver.AppleThunderboltIP	4.0.3
+com.apple.driver.AppleFileSystemDriver	3.0.1
+com.apple.nke.l2tp	1.9
+com.apple.filesystems.tmpfs	1
+com.apple.filesystems.lifs	1
+com.apple.IOTextEncryptionFamily	1.0.0
+com.apple.filesystems.hfs.kext	582.40.4
+com.apple.security.BootPolicy	1
+com.apple.BootCache	40
+com.apple.AppleFSCompression.AppleFSCompressionTypeZlib	1.0.0
+com.apple.AppleFSCompression.AppleFSCompressionTypeDataless	1.0.0d1
+com.apple.driver.AppleCS42L84Audio	502.6
+com.apple.driver.ApplePMP	1
+com.apple.driver.AppleSmartIO2	1
+com.apple.driver.AppleSN012776Amp	502.6
+com.apple.AppleEmbeddedSimpleSPINORFlasher	1
+com.apple.driver.AppleT6000SOCTuner	1
+com.apple.driver.AppleT6000CLPCv3	1
+com.apple.driver.AppleSmartBatteryManager	161.0.0
+com.apple.driver.AppleALSColorSensor	1.0.0d1
+com.apple.driver.AppleAOPVoiceTrigger	100.1
+com.apple.driver.ApplePMPFirmware	1
+com.apple.driver.AppleMCDP29XXUpdateSupport	1
+com.apple.driver.AppleM68Buttons	1.0.0d1
+com.apple.driver.AppleSamsungSerial	1.0.0d1
+com.apple.driver.AppleSerialShim	1
+com.apple.driver.usb.AppleSynopsysUSB40XHCI	1
+com.apple.driver.AppleSDXC	3.1.1
+com.apple.driver.AppleSPMIPMU	1.0.1
+com.apple.AGXG13X	187.57
+com.apple.driver.AppleAVD	415
+com.apple.driver.AppleAVE2	501.6.9
+com.apple.driver.AppleJPEGDriver	4.7.8
+com.apple.driver.AppleProResHW	126.2.0
+com.apple.driver.AppleMobileDispT600X-DCP	140.0
+com.apple.driver.AppleDPDisplayTCON	1
+com.apple.driver.AppleEventLogHandler	1
+com.apple.driver.AppleS5L8960XNCO	1
+com.apple.driver.AppleT6001PMGR	1
+com.apple.driver.AppleS8000AES	1
+com.apple.driver.AppleS8000DWI	1.0.0d1
+com.apple.driver.AppleInterruptControllerV2	1.0.0d1
+com.apple.driver.AppleT8110DART	1
+com.apple.driver.AppleBluetoothModule	1
+com.apple.driver.AppleBCMWLANBusInterfacePCIe	1
+com.apple.driver.AppleS5L8920XPWM	1.0.0d1
+com.apple.driver.AudioDMAController-T600x	100.51
+com.apple.driver.AppleT6000DART	1
+com.apple.driver.AppleSPIMC	1
+com.apple.driver.AppleS5L8940XI2C	1.0.0d2
+com.apple.driver.AppleT6000	1
+com.apple.iokit.IOUserEthernet	1.0.1
+com.apple.driver.usb.AppleUSBUserHCI	1
+com.apple.iokit.IOKitRegistryCompatibility	1
+com.apple.iokit.EndpointSecurity	1
+com.apple.driver.AppleDiskImages2	126.40.1
+com.apple.AppleSystemPolicy	2.0.0
+com.apple.nke.applicationfirewall	402
+com.apple.kec.InvalidateHmac	1
+com.apple.kec.AppleEncryptedArchive	1
+com.apple.driver.driverkit.serial	6.0.0
+com.apple.kext.triggers	1.0
+com.apple.driver.AppleUSBMergeNub	900.4.2
+com.apple.driver.usb.cdc.ecm	5.0.0
+com.apple.driver.usb.cdc.acm	5.0.0
+com.apple.driver.usb.serial	6.0.0
+com.apple.driver.usb.cdc.ncm	5.0.0
+com.apple.iokit.IOAVBFamily	1010.2
+com.apple.plugin.IOgPTPPlugin	1000.11
+com.apple.driver.usb.IOUSBHostHIDDevice	1.2
+com.apple.driver.usb.cdc	5.0.0
+com.apple.driver.AppleUSBAudio	412.8
+com.apple.iokit.IOAudioFamily	300.10
+com.apple.vecLib.kext	1.2.0
+com.apple.iokit.IOEthernetAVBController	1.1.0
+com.apple.driver.usb.AppleUSBXHCIPCI	1.2
+com.apple.driver.AppleMesaSEPDriver	100.99
+com.apple.iokit.IOBiometricFamily	1
+com.apple.driver.AppleHIDKeyboard	228
+com.apple.driver.AppleHSBluetoothDriver	5010.1
+com.apple.driver.IOBluetoothHIDDriver	9.0.0
+com.apple.driver.AppleActuatorDriver	5400.25
+com.apple.driver.AppleMultitouchDriver	5400.25
+com.apple.driver.AppleThunderboltPCIUpAdapter	4.1.1
+com.apple.driver.AppleThunderboltDPOutAdapter	8.5.0
+com.apple.driver.AppleSEPHDCPManager	1.0.1
+com.apple.driver.AppleTrustedAccessory	1
+com.apple.iokit.AppleSEPGenericTransfer	1
+com.apple.driver.DiskImages.KernelBacked	493.0.0
+com.apple.driver.AppleXsanScheme	3
+com.apple.driver.usb.networking	5.0.0
+com.apple.driver.AppleThunderboltUSBDownAdapter	1.0.4
+com.apple.driver.AppleThunderboltPCIDownAdapter	4.1.1
+com.apple.driver.AppleThunderboltDPInAdapter	8.5.0
+com.apple.driver.AppleThunderboltDPAdapterFamily	8.5.0
+com.apple.nke.ppp	1.9
+com.apple.driver.AppleHIDTransportSPI	5400.30
+com.apple.driver.AppleHIDTransport	5400.30
+com.apple.driver.AppleInputDeviceSupport	5400.30
+com.apple.driver.AppleBSDKextStarter	3
+com.apple.filesystems.hfs.encodings.kext	1
+com.apple.driver.AppleConvergedIPCOLYBTControl	1
+com.apple.driver.AppleConvergedPCI	1
+com.apple.driver.AppleBluetoothDebug	1
+com.apple.driver.AppleBTM	1.0.1
+com.apple.driver.AppleDiagnosticDataAccessReadOnly	1.0.0
+com.apple.driver.AppleCSEmbeddedAudio	502.6
+com.apple.driver.AppleDCPDPTXProxy	1.0.0
+com.apple.driver.DCPDPFamilyProxy	1
+com.apple.driver.ApplePassthroughPPM	3.0
+com.apple.driver.AppleAOPAudio	102.2
+com.apple.driver.AppleEmbeddedAudio	502.6
+com.apple.iokit.AppleARMIISAudio	100.1
+com.apple.driver.AppleSPU	1
+com.apple.iokit.IONVMeFamily	2.1.0
+com.apple.driver.AppleNANDConfigAccess	1.0.0
+com.apple.AGXFirmwareKextG13XRTBuddy	187.57
+com.apple.AGXFirmwareKextRTBuddy64	187.57
+com.apple.driver.AppleHPM	3.4.4
+com.apple.driver.DCPAVFamilyProxy	1
+com.apple.driver.AppleStockholmControl	1.0.0
+com.apple.driver.AppleT6000TypeCPhy	1
+com.apple.driver.AppleT8103TypeCPhy	1
+com.apple.driver.AppleUSBXDCIARM	1.0
+com.apple.driver.AppleUSBXDCI	1.0
+com.apple.iokit.IOUSBDeviceFamily	2.0.0
+com.apple.driver.usb.AppleSynopsysUSBXHCI	1
+com.apple.driver.usb.AppleUSBXHCI	1.2
+com.apple.driver.AppleEmbeddedUSBHost	1
+com.apple.driver.usb.AppleUSBHub	1.2
+com.apple.driver.usb.AppleUSBHostCompositeDevice	1.2
+com.apple.driver.AppleDialogPMU	1.0.1
+com.apple.driver.AppleSPMI	1.0.1
+com.apple.driver.usb.AppleUSBHostPacketFilter	1.0
+com.apple.iokit.IOGPUFamily	35.11
+com.apple.iokit.IOMobileGraphicsFamily-DCP	343.0.0
+com.apple.driver.AppleDCP	1
+com.apple.driver.AppleFirmwareKit	1
+com.apple.iokit.IOMobileGraphicsFamily	343.0.0
+com.apple.driver.AppleSART	1
+com.apple.driver.ApplePMGR	1
+com.apple.driver.AppleARMWatchdogTimer	1
+com.apple.driver.AppleDisplayCrossbar	1.0.0
+com.apple.iokit.IODisplayPortFamily	1.0.0
+com.apple.driver.AppleTypeCPhy	1
+com.apple.driver.AppleThunderboltNHI	7.2.8
+com.apple.driver.AppleT6000PCIeC	1
+com.apple.iokit.IOThunderboltFamily	9.3.2
+com.apple.driver.ApplePIODMA	1
+com.apple.driver.AppleT600xPCIe	1
+com.apple.driver.AppleMultiFunctionManager	1
+com.apple.driver.AppleBluetoothDebugService	1
+com.apple.driver.AppleBCMWLANCore	1.0.0
+com.apple.iokit.IO80211Family	1200.12.2b1
+com.apple.driver.IOImageLoader	1.0.0
+com.apple.driver.AppleOLYHAL	1
+com.apple.driver.corecapture	1.0.4
+com.apple.driver.AppleEmbeddedPCIE	1
+com.apple.driver.AppleMCA2-T600x	600.95
+com.apple.driver.AppleEmbeddedAudioLibs	100.9.1
+com.apple.driver.AppleFirmwareUpdateKext	1
+com.apple.driver.AppleH13CameraInterface	4.79.0
+com.apple.driver.AppleH10PearlCameraInterface	17.0.3
+com.apple.driver.AppleGPIOICController	1.0.2
+com.apple.driver.AppleFireStormErrorHandler	1
+com.apple.driver.AppleMobileApNonce	1
+com.apple.iokit.IOTimeSyncFamily	1000.11
+com.apple.driver.DiskImages	493.0.0
+com.apple.iokit.IOGraphicsFamily	593
+com.apple.iokit.IOBluetoothSerialManager	9.0.0
+com.apple.iokit.IOBluetoothHostControllerUSBTransport	9.0.0
+com.apple.iokit.IOBluetoothHostControllerUARTTransport	9.0.0
+com.apple.iokit.IOBluetoothHostControllerTransport	9.0.0
+com.apple.driver.IOBluetoothHostControllerPCIeTransport	9.0.0
+com.apple.iokit.IOBluetoothFamily	9.0.0
+com.apple.driver.FairPlayIOKit	68.13.0
+com.apple.iokit.CoreAnalyticsFamily	1
+com.apple.iokit.CSRBluetoothHostControllerUSBTransport	9.0.0
+com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport	9.0.0
+com.apple.driver.AppleSSE	1.0
+com.apple.driver.AppleSEPKeyStore	2
+com.apple.driver.AppleUSBTDM	532.40.7
+com.apple.iokit.IOUSBMassStorageDriver	209.40.6
+com.apple.iokit.IOPCIFamily	2.9
+com.apple.iokit.IOSCSIBlockCommandsDevice	452.30.4
+com.apple.iokit.IOSCSIArchitectureModelFamily	452.30.4
+com.apple.driver.AppleIPAppender	1.0
+com.apple.driver.AppleFDEKeyStore	28.30
+com.apple.driver.AppleEffaceableStorage	1.0
+com.apple.driver.AppleCredentialManager	1.0
+com.apple.driver.KernelRelayHost	1
+com.apple.iokit.IOUSBHostFamily	1.2
+com.apple.driver.AppleUSBHostMergeProperties	1.2
+com.apple.driver.usb.AppleUSBCommon	1.0
+com.apple.driver.AppleSMC	3.1.9
+com.apple.driver.RTBuddy	1.0.0
+com.apple.driver.AppleEmbeddedTempSensor	1.0.0
+com.apple.driver.AppleARMPMU	1.0
+com.apple.iokit.IOAccessoryManager	1.0.0
+com.apple.driver.AppleOnboardSerial	1.0
+com.apple.iokit.IOSkywalkFamily	1.0
+com.apple.driver.mDNSOffloadUserClient	1.0.1b8
+com.apple.iokit.IONetworkingFamily	3.4
+com.apple.iokit.IOSerialFamily	11
+com.apple.driver.AppleSEPManager	1.0.1
+com.apple.driver.AppleA7IOP	1.0.2
+com.apple.driver.IOSlaveProcessor	1
+com.apple.driver.AppleBiometricSensor	2
+com.apple.iokit.IOHIDFamily	2.0.0
+com.apple.driver.AppleANELoadBalancer	5.33.2
+com.apple.driver.AppleH11ANEInterface	5.33.0
+com.apple.AUC	1.0
+com.apple.iokit.IOAVFamily	1.0.0
+com.apple.iokit.IOHDCPFamily	1.0.0
+com.apple.iokit.IOCECFamily	1
+com.apple.iokit.IOAudio2Family	1.0
+com.apple.driver.AppleIISController	100.1
+com.apple.driver.AppleAudioClockLibs	100.9.1
+com.apple.driver.AppleM2ScalerCSCDriver	265.0.0
+com.apple.iokit.IOSurface	302.9
+com.apple.driver.IODARTFamily	1
+com.apple.security.quarantine	4
+com.apple.security.sandbox	300.0
+com.apple.kext.AppleMatch	1.0.0d1
+com.apple.driver.AppleMobileFileIntegrity	1.0.5
+com.apple.security.AppleImage4	4.1.0
+com.apple.kext.CoreTrust	1
+com.apple.iokit.IOCryptoAcceleratorFamily	1.0.1
+com.apple.driver.AppleARMPlatform	1.0.2
+com.apple.iokit.IOStorageFamily	2.1
+com.apple.iokit.IOSlowAdaptiveClockingFamily	1.0.0
+com.apple.iokit.IOReportFamily	47
+com.apple.kec.pthread	1
+com.apple.kec.Libm	1
+com.apple.kec.corecrypto	12.0
+
+
+
+** Stackshot Succeeded ** Bytes Traced 478480 (Uncompressed 1208976) **
+```
+Steps to reproduce:
+1. See https://github.com/lima-vm/lima/issues/713
+Additional information:
+
diff --git a/results/classifier/gemma3:12b/kernel/905 b/results/classifier/gemma3:12b/kernel/905
new file mode 100644
index 00000000..7a6ed2c6
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/905
@@ -0,0 +1,2 @@
+
+Null-ptr dereference in blk_bs
diff --git a/results/classifier/gemma3:12b/kernel/915 b/results/classifier/gemma3:12b/kernel/915
new file mode 100644
index 00000000..d55ecc03
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/915
@@ -0,0 +1,380 @@
+
+could not build qemu 6.2.0 in PPC64le
+Description of problem:
+Qemu 6.2.0 is not building in PPC64le
+Additional information:
+```
+Build Qemu
+Using './build' as the directory for build output
+Submodule 'dtc' (https://gitlab.com/qemu-project/dtc.git) registered for path 'dtc'
+Submodule 'meson' (https://gitlab.com/qemu-project/meson.git) registered for path 'meson'
+Submodule 'ui/keycodemapdb' (https://gitlab.com/qemu-project/keycodemapdb.git) registered for path 'ui/keycodemapdb'
+Cloning into '/home/jenkins/workspace/kata-containers-2.0-ppc64le-containerd-k8s-ubuntu-20-04-PR/go/src/github.com/qemu/qemu/dtc'...
+Cloning into '/home/jenkins/workspace/kata-containers-2.0-ppc64le-containerd-k8s-ubuntu-20-04-PR/go/src/github.com/qemu/qemu/meson'...
+Cloning into '/home/jenkins/workspace/kata-containers-2.0-ppc64le-containerd-k8s-ubuntu-20-04-PR/go/src/github.com/qemu/qemu/ui/keycodemapdb'...
+The Meson build system
+Version: 0.59.3
+Source dir: /home/jenkins/workspace/kata-containers-2.0-ppc64le-containerd-k8s-ubuntu-20-04-PR/go/src/github.com/qemu/qemu
+Build dir: /home/jenkins/workspace/kata-containers-2.0-ppc64le-containerd-k8s-ubuntu-20-04-PR/go/src/github.com/qemu/qemu/build
+Build type: native build
+Project name: qemu
+Project version: 6.2.0
+C compiler for the host machine: cc (gcc 9.4.0 "cc (Ubuntu 9.4.0-1ubuntu1~20.04) 9.4.0")
+C linker for the host machine: cc ld.bfd 2.34
+Host machine cpu family: ppc64
+Host machine cpu: ppc64le
+Program sh found: YES (/usr/bin/sh)
+Program python3 found: YES (/usr/bin/python3)
+WARNING: Broken python installation detected. Python files installed by Meson might not be found by python interpreter.
+C++ compiler for the host machine: c++ (gcc 9.4.0 "c++ (Ubuntu 9.4.0-1ubuntu1~20.04) 9.4.0")
+C++ linker for the host machine: c++ ld.bfd 2.34
+Program cgcc skipped: feature sparse disabled
+Library m found: YES
+Run-time dependency threads found: YES
+Library util found: YES
+Run-time dependency appleframeworks found: NO (tried framework)
+Found pkg-config: /usr/bin/pkg-config (0.29.1)
+Run-time dependency pixman-1 found: YES 0.38.4
+Run-time dependency zlib found: YES 1.2.11
+Library aio skipped: feature linux_aio disabled
+Run-time dependency liburing found: NO (tried pkgconfig)
+Dependency libxml-2.0 skipped: feature libxml2 disabled
+Dependency libnfs skipped: feature libnfs disabled
+Run-time dependency appleframeworks found: NO (tried framework)
+Run-time dependency libseccomp found: YES 2.5.1
+Has header "cap-ng.h" : YES 
+Library cap-ng found: YES
+Run-time dependency xkbcommon found: NO (tried pkgconfig)
+Library vdeplug skipped: feature vde disabled
+Run-time dependency libpulse found: NO (tried pkgconfig)
+Run-time dependency alsa found: NO (tried pkgconfig)
+Run-time dependency jack found: NO (tried pkgconfig)
+Run-time dependency spice-protocol found: NO (tried pkgconfig)
+Dependency spice-server skipped: feature spice disabled
+Library rt found: YES
+Dependency libiscsi skipped: feature libiscsi disabled
+Run-time dependency libzstd found: NO (tried pkgconfig)
+Dependency virglrenderer skipped: feature virglrenderer disabled
+Dependency libcurl skipped: feature curl disabled
+Dependency libudev skipped: feature libudev disabled
+Library brlapi skipped: feature brlapi disabled
+Dependency sdl2 skipped: feature sdl disabled
+Library rados found: YES
+Has header "rbd/librbd.h" : YES 
+Library rbd found: YES
+Dependency glusterfs-api skipped: feature glusterfs disabled
+Library bz2 skipped: feature bzip2 disabled
+Has header "lzfse.h" : NO 
+Has header "sys/soundcard.h" : YES 
+Run-time dependency gnutls found: NO (tried pkgconfig)
+Run-time dependency gnutls found: NO (tried pkgconfig)
+libgcrypt-config found: NO need ['>=1.8']
+Run-time dependency libgcrypt found: NO (tried config-tool)
+Dependency nettle skipped: feature nettle disabled
+Dependency gtk+-3.0 skipped: feature gtk disabled
+Library pam skipped: feature auth_pam disabled
+Library snappy skipped: feature snappy disabled
+Library lzo2 skipped: feature lzo disabled
+Dependency libcacard skipped: feature smartcard disabled
+Run-time dependency u2f-emu found: NO (tried pkgconfig)
+Dependency libusbredirparser-0.5 skipped: feature usb_redir disabled
+Dependency libusb-1.0 skipped: feature libusb disabled
+Dependency libpmem skipped: feature libpmem disabled
+Run-time dependency libdaxctl found: NO (tried pkgconfig)
+Run-time dependency libkeyutils found: NO (tried pkgconfig)
+Checking for function "gettid" : YES 
+Run-time dependency libselinux found: YES 3.0
+Run-time dependency fuse3 found: NO (tried pkgconfig)
+Run-time dependency libbpf found: NO (tried pkgconfig)
+Has header "sys/epoll.h" : YES 
+Has header "linux/magic.h" : YES 
+Has header "valgrind/valgrind.h" : NO 
+Has header "linux/btrfs.h" : YES 
+Has header "libdrm/drm.h" : NO 
+Has header "pty.h" : YES 
+Has header "sys/disk.h" : NO 
+Has header "sys/ioccom.h" : NO 
+Has header "sys/kcov.h" : NO 
+Checking for function "accept4" : YES 
+Checking for function "clock_adjtime" : YES 
+Checking for function "dup3" : YES 
+Checking for function "fallocate" : YES 
+Checking for function "posix_fallocate" : YES 
+Checking for function "posix_memalign" : YES 
+Checking for function "ppoll" : YES 
+Checking for function "preadv" : YES 
+Checking for function "sem_timedwait" with dependency threads: YES 
+Checking for function "sendfile" : YES 
+Checking for function "setns" : YES 
+Checking for function "unshare" : YES 
+Checking for function "syncfs" : YES 
+Checking for function "sync_file_range" : YES 
+Checking for function "timerfd_create" : YES 
+Checking for function "copy_file_range" : YES 
+Checking for function "openpty" with dependency -lutil: YES 
+Checking for function "strchrnul" : YES 
+Checking for function "system" : YES 
+Header <byteswap.h> has symbol "bswap_32" : YES 
+Header <sys/epoll.h> has symbol "epoll_create1" : YES 
+Header <unistd.h> has symbol "environ" : YES 
+Header <linux/falloc.h> has symbol "FALLOC_FL_PUNCH_HOLE" : YES 
+Header <linux/falloc.h> has symbol "FALLOC_FL_KEEP_SIZE" : YES 
+Header <linux/falloc.h> has symbol "FALLOC_FL_ZERO_RANGE" : YES 
+Has header "linux/fiemap.h" : YES 
+Header <linux/fs.h> has symbol "FS_IOC_FIEMAP" : YES 
+Checking for function "getrandom" : YES 
+Header <sys/random.h> has symbol "GRND_NONBLOCK" : YES 
+Header <sys/inotify.h> has symbol "inotify_init" : YES 
+Header <sys/inotify.h> has symbol "inotify_init1" : YES 
+Header <machine/bswap.h> has symbol "bswap32" : NO 
+Header <sys/prctl.h> has symbol "PR_SET_TIMERSLACK" : YES 
+Header <linux/rtnetlink.h> has symbol "IFLA_PROTO_DOWN" : YES 
+Header <sys/sysmacros.h> has symbol "makedev" : YES 
+Header <getopt.h> has symbol "optreset" : NO 
+Header <netinet/in.h> has symbol "IPPROTO_MPTCP" : NO 
+Checking whether type "struct sigevent" has member "sigev_notify_thread_id" : NO 
+Checking whether type "struct stat" has member "st_atim" : YES 
+Checking for type "struct iovec" : YES 
+Checking for type "struct utmpx" : YES 
+Checking for type "struct mmsghdr" : YES 
+Program scripts/minikconf.py found: YES (/usr/bin/python3 /home/jenkins/workspace/kata-containers-2.0-ppc64le-containerd-k8s-ubuntu-20-04-PR/go/src/github.com/qemu/qemu/scripts/minikconf.py)
+Configuring ppc64-softmmu-config-target.h using configuration
+Configuring ppc64-softmmu-config-devices.mak with command
+Reading depfile: /home/jenkins/workspace/kata-containers-2.0-ppc64le-containerd-k8s-ubuntu-20-04-PR/go/src/github.com/qemu/qemu/build/meson-private/ppc64-softmmu-config-devices.mak.d
+Configuring ppc64-softmmu-config-devices.h using configuration
+Library fdt found: NO
+Configuring config-host.h using configuration
+Program scripts/hxtool found: YES (/home/jenkins/workspace/kata-containers-2.0-ppc64le-containerd-k8s-ubuntu-20-04-PR/go/src/github.com/qemu/qemu/scripts/hxtool)
+Program scripts/shaderinclude.pl found: YES (/usr/bin/env perl /home/jenkins/workspace/kata-containers-2.0-ppc64le-containerd-k8s-ubuntu-20-04-PR/go/src/github.com/qemu/qemu/scripts/shaderinclude.pl)
+Program scripts/qapi-gen.py found: YES (/usr/bin/python3 /home/jenkins/workspace/kata-containers-2.0-ppc64le-containerd-k8s-ubuntu-20-04-PR/go/src/github.com/qemu/qemu/scripts/qapi-gen.py)
+Program scripts/qemu-version.sh found: YES (/home/jenkins/workspace/kata-containers-2.0-ppc64le-containerd-k8s-ubuntu-20-04-PR/go/src/github.com/qemu/qemu/scripts/qemu-version.sh)
+
+Executing subproject libvhost-user 
+
+libvhost-user| Project name: libvhost-user
+libvhost-user| Project version: undefined
+libvhost-user| C compiler for the host machine: cc (gcc 9.4.0 "cc (Ubuntu 9.4.0-1ubuntu1~20.04) 9.4.0")
+libvhost-user| C linker for the host machine: cc ld.bfd 2.34
+libvhost-user| Dependency threads found: YES unknown (cached)
+libvhost-user| Dependency glib-2.0 found: YES 6.2.0 (overridden)
+libvhost-user| Build targets in project: 9
+libvhost-user| Subproject libvhost-user finished.
+
+Program cat found: YES (/usr/bin/cat)
+Program scripts/decodetree.py found: YES (/usr/bin/python3 /home/jenkins/workspace/kata-containers-2.0-ppc64le-containerd-k8s-ubuntu-20-04-PR/go/src/github.com/qemu/qemu/scripts/decodetree.py)
+Program ../scripts/modules/module_block.py found: YES (/usr/bin/python3 /home/jenkins/workspace/kata-containers-2.0-ppc64le-containerd-k8s-ubuntu-20-04-PR/go/src/github.com/qemu/qemu/block/../scripts/modules/module_block.py)
+Program ../scripts/block-coroutine-wrapper.py found: YES (/usr/bin/python3 /home/jenkins/workspace/kata-containers-2.0-ppc64le-containerd-k8s-ubuntu-20-04-PR/go/src/github.com/qemu/qemu/block/../scripts/block-coroutine-wrapper.py)
+Program scripts/modinfo-collect.py found: YES (/home/jenkins/workspace/kata-containers-2.0-ppc64le-containerd-k8s-ubuntu-20-04-PR/go/src/github.com/qemu/qemu/scripts/modinfo-collect.py)
+Program scripts/modinfo-generate.py found: YES (/home/jenkins/workspace/kata-containers-2.0-ppc64le-containerd-k8s-ubuntu-20-04-PR/go/src/github.com/qemu/qemu/scripts/modinfo-generate.py)
+Program nm found: YES
+Program scripts/undefsym.py found: YES (/usr/bin/python3 /home/jenkins/workspace/kata-containers-2.0-ppc64le-containerd-k8s-ubuntu-20-04-PR/go/src/github.com/qemu/qemu/scripts/undefsym.py)
+Program scripts/feature_to_c.sh found: YES (/bin/sh /home/jenkins/workspace/kata-containers-2.0-ppc64le-containerd-k8s-ubuntu-20-04-PR/go/src/github.com/qemu/qemu/scripts/feature_to_c.sh)
+Configuring 50-qemu-virtiofsd.json using configuration
+Program qemu-keymap found: NO
+Program cp found: YES (/usr/bin/cp)
+Program sphinx-build-3 sphinx-build skipped: feature docs disabled
+Program python3 found: YES (/usr/bin/python3)
+Program diff found: YES (/usr/bin/diff)
+Program dbus-daemon found: YES (/usr/bin/dbus-daemon)
+Program /usr/bin/gdbus-codegen found: YES (/usr/bin/gdbus-codegen)
+Program initrd-stress.sh found: YES (/home/jenkins/workspace/kata-containers-2.0-ppc64le-containerd-k8s-ubuntu-20-04-PR/go/src/github.com/qemu/qemu/tests/migration/initrd-stress.sh)
+Build targets in project: 395
+
+qemu 6.2.0
+
+  Directories
+    Install prefix               : /usr
+    BIOS directory               : share/qemu/qemu
+    firmware path                : /usr/share/qemu/qemu-firmware
+    binary directory             : bin
+    library directory            : lib/qemu
+    module directory             : lib/qemu/qemu
+    libexec directory            : libexec/qemu
+    include directory            : include
+    config directory             : /usr/etc
+    local state directory        : /usr/var
+    Manual directory             : share/man
+    Doc directory                : /usr/share/doc
+    Build directory              : /home/jenkins/workspace/kata-containers-2.0-ppc64le-containerd-k8s-ubuntu-20-04-PR/go/src/github.com/qemu/qemu/build
+    Source path                  : /home/jenkins/workspace/kata-containers-2.0-ppc64le-containerd-k8s-ubuntu-20-04-PR/go/src/github.com/qemu/qemu
+    GIT submodules               : ui/keycodemapdb meson dtc
+
+  Host binaries
+    git                          : git
+    make                         : make
+    python                       : /usr/bin/python3 (version: 3.8)
+    sphinx-build                 : NO
+    gdb                          : /usr/bin/gdb
+    genisoimage                  : /usr/bin/genisoimage
+
+  Configurable features
+    Documentation                : NO
+    system-mode emulation        : YES
+    user-mode emulation          : NO
+    block layer                  : YES
+    Install blobs                : YES
+    module support               : NO
+    fuzzing support              : NO
+    Audio drivers                : oss
+    Trace backends               : log
+    QOM debugging                : NO
+    vhost-kernel support         : YES
+    vhost-net support            : YES
+    vhost-crypto support         : YES
+    vhost-scsi support           : YES
+    vhost-vsock support          : YES
+    vhost-user support           : YES
+    vhost-user-blk server support: YES
+    vhost-user-fs support        : YES
+    vhost-vdpa support           : YES
+    build guest agent            : NO
+
+  Compilation
+    host CPU                     : ppc64
+    host endianness              : little
+    C compiler                   : cc
+    Host C compiler              : cc
+    C++ compiler                 : c++
+    CFLAGS                       : -O2 -fno-semantic-interposition -falign-functions=32 -D_FORTIFY_SOURCE=2 -O2 -g
+    CXXFLAGS                     : -O2 -fno-semantic-interposition -falign-functions=32 -D_FORTIFY_SOURCE=2 -O2 -g
+    LDFLAGS                      : -O2 -fno-semantic-interposition -falign-functions=32 -D_FORTIFY_SOURCE=2 -z noexecstack -z relro -z now
+    QEMU_CFLAGS                  : -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wold-style-declaration -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wimplicit-fallthrough=2 -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -fstack-protector-strong
+    QEMU_LDFLAGS                 : -Wl,--warn-common -Wl,-z,relro -Wl,-z,now  -fstack-protector-strong
+    profiler                     : NO
+    link-time optimization (LTO) : NO
+    PIE                          : YES
+    static build                 : NO
+    malloc trim support          : YES
+    membarrier                   : NO
+    debug stack usage            : NO
+    mutex debugging              : NO
+    memory allocator             : system
+    avx2 optimization            : NO
+    avx512f optimization         : NO
+    gprof enabled                : NO
+    gcov                         : NO
+    thread sanitizer             : NO
+    CFI support                  : NO
+    strip binaries               : YES
+    sparse                       : NO
+    mingw32 support              : NO
+
+  Targets and accelerators
+    KVM support                  : YES
+    HAX support                  : NO
+    HVF support                  : NO
+    WHPX support                 : NO
+    NVMM support                 : NO
+    Xen support                  : NO
+    TCG support                  : NO
+    target list                  : ppc64-softmmu
+    default devices              : YES
+    out of process emulation     : YES
+
+  Block layer support
+    coroutine backend            : ucontext
+    coroutine pool               : YES
+    Block whitelist (rw)         : 
+    Block whitelist (ro)         : 
+    Use block whitelist in tools : NO
+    VirtFS support               : YES
+    build virtiofs daemon        : YES
+    Live block migration         : NO
+    replication support          : NO
+    bochs support                : NO
+    cloop support                : NO
+    dmg support                  : NO
+    qcow v1 support              : NO
+    vdi support                  : NO
+    vvfat support                : NO
+    qed support                  : NO
+    parallels support            : NO
+    FUSE exports                 : NO
+
+  Crypto
+    TLS priority                 : "NORMAL"
+    GNUTLS support               : NO
+    libgcrypt                    : NO
+    nettle                       : NO
+    crypto afalg                 : NO
+    rng-none                     : NO
+    Linux keyring                : YES
+
+  Dependencies
+    SDL support                  : NO
+    SDL image support            : NO
+    GTK support                  : NO
+    pixman                       : YES 0.38.4
+    VTE support                  : NO
+    slirp support                : NO
+    libtasn1                     : NO
+    PAM                          : NO
+    iconv support                : NO
+    curses support               : NO
+    virgl support                : NO
+    curl support                 : NO
+    Multipath support            : NO
+    VNC support                  : NO
+    OSS support                  : YES
+    ALSA support                 : NO
+    PulseAudio support           : NO
+    JACK support                 : NO
+    brlapi support               : NO
+    vde support                  : NO
+    netmap support               : NO
+    l2tpv3 support               : YES
+    Linux AIO support            : NO
+    Linux io_uring support       : NO
+    ATTR/XATTR support           : YES
+    RDMA support                 : NO
+    PVRDMA support               : NO
+    fdt support                  : internal
+    libcap-ng support            : YES
+    bpf support                  : NO
+    spice protocol support       : NO
+    rbd support                  : YES
+    xfsctl support               : NO
+    smartcard support            : NO
+    U2F support                  : NO
+    libusb                       : NO
+    usb net redir                : NO
+    OpenGL support               : NO
+    GBM                          : NO
+    libiscsi support             : NO
+    libnfs support               : NO
+    seccomp support              : YES 2.5.1
+    GlusterFS support            : NO
+    TPM support                  : NO
+    libssh support               : NO
+    lzo support                  : NO
+    snappy support               : NO
+    bzip2 support                : NO
+    lzfse support                : NO
+    zstd support                 : NO
+    NUMA host support            : NO
+    libxml2                      : NO
+    capstone                     : NO
+    libpmem support              : NO
+    libdaxctl support            : NO
+    libudev                      : NO
+    FUSE lseek                   : NO
+    selinux                      : YES 3.0
+
+  Subprojects
+    libvhost-user                : YES
+
+Found ninja-1.10.0 at /usr/bin/ninja
+```
+
+```
+[1330/1767] Compiling C object libqemu-ppc64-softmmu.fa.p/target_ppc_excp_helper.c.o
+FAILED: libqemu-ppc64-softmmu.fa.p/target_ppc_excp_helper.c.o 
+cc -Ilibqemu-ppc64-softmmu.fa.p -I. -I.. -Itarget/ppc -I../target/ppc -I../dtc/libfdt -Iqapi -Itrace -Iui -Iui/shader -I/usr/include/pixman-1 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -fdiagnostics-color=auto -Wall -Winvalid-pch -Werror -std=gnu11 -O2 -g -isystem /home/jenkins/workspace/kata-containers-2.0-ppc64le-containerd-k8s-ubuntu-20-04-PR/go/src/github.com/qemu/qemu/linux-headers -isystem linux-headers -iquote . -iquote /home/jenkins/workspace/kata-containers-2.0-ppc64le-containerd-k8s-ubuntu-20-04-PR/go/src/github.com/qemu/qemu -iquote /home/jenkins/workspace/kata-containers-2.0-ppc64le-containerd-k8s-ubuntu-20-04-PR/go/src/github.com/qemu/qemu/include -iquote /home/jenkins/workspace/kata-containers-2.0-ppc64le-containerd-k8s-ubuntu-20-04-PR/go/src/github.com/qemu/qemu/disas/libvixl -pthread -U_FORTIFY_SOURCE -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wold-style-declaration -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wimplicit-fallthrough=2 -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -O2 -fno-semantic-interposition -falign-functions=32 -D_FORTIFY_SOURCE=2 -fPIE -isystem../linux-headers -isystemlinux-headers -DNEED_CPU_H '-DCONFIG_TARGET="ppc64-softmmu-config-target.h"' '-DCONFIG_DEVICES="ppc64-softmmu-config-devices.h"' -MD -MQ libqemu-ppc64-softmmu.fa.p/target_ppc_excp_helper.c.o -MF libqemu-ppc64-softmmu.fa.p/target_ppc_excp_helper.c.o.d -o libqemu-ppc64-softmmu.fa.p/target_ppc_excp_helper.c.o -c ../target/ppc/excp_helper.c
+../target/ppc/excp_helper.c: In function ‘powerpc_excp’:
+../target/ppc/excp_helper.c:463:29: error: implicit declaration of function ‘cpu_ldl_code’ [-Werror=implicit-function-declaration]
+  463 |             uint32_t insn = cpu_ldl_code(env, env->nip);
+      |                             ^~~~~~~~~~~~
+../target/ppc/excp_helper.c:463:29: error: nested extern declaration of ‘cpu_ldl_code’ [-Werror=nested-externs]
+cc1: all warnings being treated as errors
+[1331/1767] Compiling C object libqemu-ppc64-softmmu.fa.p/hw_block_dataplane_virtio-blk.c.o
+```
diff --git a/results/classifier/gemma3:12b/kernel/917645 b/results/classifier/gemma3:12b/kernel/917645
new file mode 100644
index 00000000..f0c4dd1d
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/917645
@@ -0,0 +1,6 @@
+
+[Feature request] ia64-softmmu wanted
+
+Qemu is missing support for full system emulation of the Itanium architecture, which is one of the main non-x86 server architectures today (despite the alleged decline in popularity). It would be really nice if someone had interest in adding full ia64 support to Qemu. Many OS projects could then use Qemu as the universal machine emulator for development and testing.
+
+Note that there is an open source Ski simulator which can emulate an ia64 CPU, memory and a couple of Ski-specific devices, but the project seems inactive and the simulated machine is too simplified (no real devices, no real firmware). Moreover, it'd be better to have one tool such as Qemu for all architectures of interest rather than one per each architecture.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/921 b/results/classifier/gemma3:12b/kernel/921
new file mode 100644
index 00000000..eba90d02
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/921
@@ -0,0 +1,624 @@
+
+qemu 7.0-rc0 warning: cannot get sys attribute capabilities 0
+Description of problem:
+The guest fp not working properly
+Steps to reproduce:
+1. Start the docker
+```
+docker run -it --name qemu --rm \
+    --privileged \
+    --ipc=host \
+    -v /dev/log:/dev/log \
+    -v /dev/vhost-net:/dev/vhost-net \
+    -v /sys/kernel/debug:/sys/kernel/debug \
+    -v $ROOT:$ROOT \
+    -p 2222:22 \
+    -p 1234:1234 \
+    -p 1235:1235 \
+    -e ROOT=$ROOT \
+    -e XDG_RUNTIME_DIR=/tmp \
+    -e WAYLAND_DISPLAY=$WAYLAND_DISPLAY \
+    -v $XDG_RUNTIME_DIR/$WAYLAND_DISPLAY:/tmp/$WAYLAND_DISPLAY \
+    qemu
+```
+2.This is in the docker
+```
++ build/docker/qemu-system-x86_64 -enable-kvm -M q35 -smp 1 -m 4G -cpu host -net nic,model=virtio -net user,hostfwd=tcp::22-:22,hostfwd=tcp::1234-:1234 -hda /data/xemu-opengl/image/ubuntu.qcow2 -initrd /data/xemu-opengl/image/rootfs.cpio.gz -kernel /data/xemu-opengl/kernel/arch/x86_64/boot/bzImage -append 'root=/dev/sda3 nokaslr' -usb -device usb-tablet -object memory-backend-memfd,id=mem1,size=4G -machine memory-backend=mem1 -device virtio-vga-gl,context_init=true,blob=true,hostmem=1G -vga none -display sdl,gl=on,show-cursor=on -d guest_errors
+qemu-system-x86_64: warning: cannot get sys attribute capabilities 0
+qemu-system-x86_64: warning: cannot get sys attribute capabilities 0
+qemu-system-x86_64: warning: cannot get sys attribute capabilities 0
+qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 1]
+qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 2]
+qemu-system-x86_64: warning: cannot get sys attribute capabilities 0
+```
+
+3. In geust
+```
+dmesg
+[    0.000000] Linux version 5.16.14 (root@5bc45822eca9) (gcc (Ubuntu 11.2.0-7ubuntu2) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.37) #3 SMP PREEMPT Sun Mar 13 23:24:16 UTC 2022
+[    0.000000] Command line: root=/dev/sda3 nokaslr
+[    0.000000] x86/fpu: FP/SSE not present amongst the CPU's xstate features: 0x1.
+[    0.000000] signal: max sigframe size: 1440
+[    0.000000] BIOS-provided physical RAM map:
+[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
+[    0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
+[    0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
+[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000007ffddfff] usable
+[    0.000000] BIOS-e820: [mem 0x000000007ffde000-0x000000007fffffff] reserved
+[    0.000000] BIOS-e820: [mem 0x00000000b0000000-0x00000000bfffffff] reserved
+[    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
+[    0.000000] BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved
+[    0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
+[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000017fffffff] usable
+[    0.000000] NX (Execute Disable) protection: active
+[    0.000000] SMBIOS 2.8 present.
+[    0.000000] DMI: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014
+[    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
+[    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
+[    0.000000] last_pfn = 0x180000 max_arch_pfn = 0x400000000
+[    0.000000] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
+[    0.000000] last_pfn = 0x7ffde max_arch_pfn = 0x400000000
+[    0.000000] found SMP MP-table at [mem 0x000f5b70-0x000f5b7f]
+[    0.000000] Using GB pages for direct mapping
+[    0.000000] RAMDISK: [mem 0x7ffcf000-0x7ffcffff]
+[    0.000000] ACPI: Early table checksum verification disabled
+[    0.000000] ACPI: RSDP 0x00000000000F5980 000014 (v00 BOCHS )
+[    0.000000] ACPI: RSDT 0x000000007FFE22CB 000038 (v01 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.000000] ACPI: FACP 0x000000007FFE20C3 0000F4 (v03 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.000000] ACPI: DSDT 0x000000007FFE0040 002083 (v01 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.000000] ACPI: FACS 0x000000007FFE0000 000040
+[    0.000000] ACPI: APIC 0x000000007FFE21B7 000078 (v01 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.000000] ACPI: HPET 0x000000007FFE222F 000038 (v01 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.000000] ACPI: MCFG 0x000000007FFE2267 00003C (v01 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.000000] ACPI: WAET 0x000000007FFE22A3 000028 (v01 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.000000] ACPI: Reserving FACP table memory at [mem 0x7ffe20c3-0x7ffe21b6]
+[    0.000000] ACPI: Reserving DSDT table memory at [mem 0x7ffe0040-0x7ffe20c2]
+[    0.000000] ACPI: Reserving FACS table memory at [mem 0x7ffe0000-0x7ffe003f]
+[    0.000000] ACPI: Reserving APIC table memory at [mem 0x7ffe21b7-0x7ffe222e]
+[    0.000000] ACPI: Reserving HPET table memory at [mem 0x7ffe222f-0x7ffe2266]
+[    0.000000] ACPI: Reserving MCFG table memory at [mem 0x7ffe2267-0x7ffe22a2]
+[    0.000000] ACPI: Reserving WAET table memory at [mem 0x7ffe22a3-0x7ffe22ca]
+[    0.000000] No NUMA configuration found
+[    0.000000] Faking a node at [mem 0x0000000000000000-0x000000017fffffff]
+[    0.000000] NODE_DATA(0) allocated [mem 0x17fffa000-0x17fffdfff]
+[    0.000000] Zone ranges:
+[    0.000000]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
+[    0.000000]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
+[    0.000000]   Normal   [mem 0x0000000100000000-0x000000017fffffff]
+[    0.000000] Movable zone start for each node
+[    0.000000] Early memory node ranges
+[    0.000000]   node   0: [mem 0x0000000000001000-0x000000000009efff]
+[    0.000000]   node   0: [mem 0x0000000000100000-0x000000007ffddfff]
+[    0.000000]   node   0: [mem 0x0000000100000000-0x000000017fffffff]
+[    0.000000] Initmem setup node 0 [mem 0x0000000000001000-0x000000017fffffff]
+[    0.000000] On node 0, zone DMA: 1 pages in unavailable ranges
+[    0.000000] On node 0, zone DMA: 97 pages in unavailable ranges
+[    0.000000] On node 0, zone Normal: 34 pages in unavailable ranges
+[    0.000000] ACPI: PM-Timer IO Port: 0x608
+[    0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
+[    0.000000] IOAPIC[0]: apic_id 0, version 17, address 0xfec00000, GSI 0-23
+[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
+[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
+[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
+[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
+[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
+[    0.000000] ACPI: Using ACPI (MADT) for SMP configuration information
+[    0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
+[    0.000000] TSC deadline timer available
+[    0.000000] smpboot: Allowing 1 CPUs, 0 hotplug CPUs
+[    0.000000] PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
+[    0.000000] PM: hibernation: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
+[    0.000000] PM: hibernation: Registered nosave memory: [mem 0x000a0000-0x000effff]
+[    0.000000] PM: hibernation: Registered nosave memory: [mem 0x000f0000-0x000fffff]
+[    0.000000] PM: hibernation: Registered nosave memory: [mem 0x7ffde000-0x7fffffff]
+[    0.000000] PM: hibernation: Registered nosave memory: [mem 0x80000000-0xafffffff]
+[    0.000000] PM: hibernation: Registered nosave memory: [mem 0xb0000000-0xbfffffff]
+[    0.000000] PM: hibernation: Registered nosave memory: [mem 0xc0000000-0xfed1bfff]
+[    0.000000] PM: hibernation: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
+[    0.000000] PM: hibernation: Registered nosave memory: [mem 0xfed20000-0xfeffbfff]
+[    0.000000] PM: hibernation: Registered nosave memory: [mem 0xfeffc000-0xfeffffff]
+[    0.000000] PM: hibernation: Registered nosave memory: [mem 0xff000000-0xfffbffff]
+[    0.000000] PM: hibernation: Registered nosave memory: [mem 0xfffc0000-0xffffffff]
+[    0.000000] [mem 0xc0000000-0xfed1bfff] available for PCI devices
+[    0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns
+[    0.000000] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:1 nr_node_ids:1
+[    0.000000] percpu: Embedded 52 pages/cpu s174744 r8192 d30056 u2097152
+[    0.000000] pcpu-alloc: s174744 r8192 d30056 u2097152 alloc=1*2097152
+[    0.000000] pcpu-alloc: [0] 0 
+[    0.000000] Fallback order for Node 0: 0 
+[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 1031902
+[    0.000000] Policy zone: Normal
+[    0.000000] Kernel command line: root=/dev/sda3 nokaslr
+[    0.000000] Unknown kernel command line parameters "nokaslr", will be passed to user space.
+[    0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)
+[    0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
+[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
+[    0.000000] Memory: 4019736K/4193776K available (16398K kernel code, 2621K rwdata, 5052K rodata, 1252K init, 1332K bss, 173784K reserved, 0K cma-reserved)
+[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
+[    0.000000] Dynamic Preempt: full
+[    0.000000] rcu: Preemptible hierarchical RCU implementation.
+[    0.000000] rcu:     RCU event tracing is enabled.
+[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=1.
+[    0.000000]  Trampoline variant of Tasks RCU enabled.
+[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 100 jiffies.
+[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
+[    0.000000] NR_IRQS: 4352, nr_irqs: 256, preallocated irqs: 16
+[    0.000000] random: get_random_bytes called from start_kernel+0x492/0x65f with crng_init=0
+[    0.000000] Console: colour VGA+ 80x25
+[    0.000000] printk: console [tty0] enabled
+[    0.000000] ACPI: Core revision 20210930
+[    0.000000] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604467 ns
+[    0.001000] APIC: Switch to symmetric I/O mode setup
+[    0.002000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
+[    0.010000] tsc: Unable to calibrate against PIT
+[    0.011000] tsc: using HPET reference calibration
+[    0.012000] tsc: Detected 3699.687 MHz processor
+[    0.000260] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x6aa85c29371, max_idle_ns: 881590506582 ns
+[    0.001636] Calibrating delay loop (skipped), value calculated using timer frequency.. 7399.37 BogoMIPS (lpj=3699687)
+[    0.002617] pid_max: default: 32768 minimum: 301
+[    0.003888] LSM: Security Framework initializing
+[    0.004744] SELinux:  Initializing.
+[    0.006672] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
+[    0.007869] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
+[    0.014682] x86/cpu: User Mode Instruction Prevention (UMIP) activated
+[    0.016974] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
+[    0.017603] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
+[    0.018602] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
+[    0.018623] Spectre V2 : Mitigation: Retpolines
+[    0.019603] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
+[    0.020637] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
+[    0.021603] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl
+[    0.083192] Freeing SMP alternatives memory: 44K
+[    0.086287] smpboot: CPU0: AMD Ryzen Threadripper 3970X 32-Core Processor (family: 0x17, model: 0x31, stepping: 0x0)
+[    0.088185] Performance Events: Fam17h+ core perfctr, AMD PMU driver.
+[    0.088635] ... version:                0
+[    0.089365] ... bit width:              48
+[    0.089610] ... generic registers:      6
+[    0.090332] ... value mask:             0000ffffffffffff
+[    0.090611] ... max period:             00007fffffffffff
+[    0.091424] ... fixed-purpose events:   0
+[    0.091614] ... event mask:             000000000000003f
+[    0.092889] rcu: Hierarchical SRCU implementation.
+[    0.095245] smp: Bringing up secondary CPUs ...
+[    0.095612] smp: Brought up 1 node, 1 CPU
+[    0.096340] smpboot: Max logical packages: 1
+[    0.096609] smpboot: Total of 1 processors activated (7399.37 BogoMIPS)
+[    0.169912] devtmpfs: initialized
+[    0.175284] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns
+[    0.175676] futex hash table entries: 256 (order: 2, 16384 bytes, linear)
+[    0.177611] PM: RTC time: 10:29:46, date: 2022-03-20
+[    0.183040] NET: Registered PF_NETLINK/PF_ROUTE protocol family
+[    0.187536] audit: initializing netlink subsys (disabled)
+[    0.191857] thermal_sys: Registered thermal governor 'step_wise'
+[    0.191877] thermal_sys: Registered thermal governor 'user_space'
+[    0.192675] audit: type=2000 audit(1647772186.201:1): state=initialized audit_enabled=0 res=1
+[    0.194185] cpuidle: using governor menu
+[    0.198008] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xb0000000-0xbfffffff] (base 0xb0000000)
+[    0.198662] PCI: MMCONFIG at [mem 0xb0000000-0xbfffffff] reserved in E820
+[    0.200081] PCI: Using configuration type 1 for base access
+[    0.204517] kprobes: kprobe jump-optimization is enabled. All kprobes are optimized if possible.
+[    0.205408] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
+[    0.206698] ACPI: Added _OSI(Module Device)
+[    0.207453] ACPI: Added _OSI(Processor Device)
+[    0.207610] ACPI: Added _OSI(3.0 _SCP Extensions)
+[    0.208402] ACPI: Added _OSI(Processor Aggregator Device)
+[    0.208611] ACPI: Added _OSI(Linux-Dell-Video)
+[    0.209375] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
+[    0.209614] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
+[    0.212597] ACPI: 1 ACPI AML tables successfully acquired and loaded
+[    0.215363] ACPI: Interpreter enabled
+[    0.215779] ACPI: PM: (supports S0 S3 S4 S5)
+[    0.216543] ACPI: Using IOAPIC for interrupt routing
+[    0.216649] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
+[    0.217739] ACPI: Enabled 2 GPEs in block 00 to 3F
+[    0.221429] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
+[    0.221679] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3]
+[    0.222638] acpi PNP0A08:00: _OSC: platform does not support [LTR]
+[    0.223563] acpi PNP0A08:00: _OSC: OS now controls [PME PCIeCapability]
+[    0.223907] PCI host bridge to bus 0000:00
+[    0.224612] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
+[    0.225562] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
+[    0.225610] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
+[    0.226616] pci_bus 0000:00: root bus resource [mem 0x80000000-0xafffffff window]
+[    0.227610] pci_bus 0000:00: root bus resource [mem 0xc0000000-0xfebfffff window]
+[    0.228611] pci_bus 0000:00: root bus resource [mem 0x180000000-0x97fffffff window]
+[    0.229611] pci_bus 0000:00: root bus resource [bus 00-ff]
+[    0.230749] pci 0000:00:00.0: [8086:29c0] type 00 class 0x060000
+[    0.233477] pci 0000:00:01.0: [1af4:1000] type 00 class 0x020000
+[    0.234636] pci 0000:00:01.0: reg 0x10: [io  0xc040-0xc05f]
+[    0.236087] pci 0000:00:01.0: reg 0x14: [mem 0xfebd0000-0xfebd0fff]
+[    0.239084] pci 0000:00:01.0: reg 0x20: [mem 0x1c0000000-0x1c0003fff 64bit pref]
+[    0.240327] pci 0000:00:01.0: reg 0x30: [mem 0xfeb80000-0xfebbffff pref]
+[    0.242540] pci 0000:00:02.0: [1af4:1050] type 00 class 0x030000
+[    0.245344] pci 0000:00:02.0: reg 0x10: [mem 0xfe000000-0xfe7fffff pref]
+[    0.247587] pci 0000:00:02.0: reg 0x14: [mem 0xfebd1000-0xfebd1fff]
+[    0.250649] pci 0000:00:02.0: reg 0x18: [mem 0x1c0004000-0x1c0007fff 64bit pref]
+[    0.253628] pci 0000:00:02.0: reg 0x20: [mem 0x180000000-0x1bfffffff 64bit pref]
+[    0.256753] pci 0000:00:02.0: reg 0x30: [mem 0xfebc0000-0xfebcffff pref]
+[    0.258570] pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
+[    0.263325] pci 0000:00:1d.0: [8086:2934] type 00 class 0x0c0300
+[    0.265363] pci 0000:00:1d.0: reg 0x20: [io  0xc060-0xc07f]
+[    0.266765] pci 0000:00:1d.1: [8086:2935] type 00 class 0x0c0300
+[    0.269437] pci 0000:00:1d.1: reg 0x20: [io  0xc080-0xc09f]
+[    0.270732] pci 0000:00:1d.2: [8086:2936] type 00 class 0x0c0300
+[    0.273371] pci 0000:00:1d.2: reg 0x20: [io  0xc0a0-0xc0bf]
+[    0.274696] pci 0000:00:1d.7: [8086:293a] type 00 class 0x0c0320
+[    0.276035] pci 0000:00:1d.7: reg 0x10: [mem 0xfebd2000-0xfebd2fff]
+[    0.279317] pci 0000:00:1f.0: [8086:2918] type 00 class 0x060100
+[    0.280866] pci 0000:00:1f.0: quirk: [io  0x0600-0x067f] claimed by ICH6 ACPI/GPIO/TCO
+[    0.282331] pci 0000:00:1f.2: [8086:2922] type 00 class 0x010601
+[    0.284903] pci 0000:00:1f.2: reg 0x20: [io  0xc0c0-0xc0df]
+[    0.286143] pci 0000:00:1f.2: reg 0x24: [mem 0xfebd3000-0xfebd3fff]
+[    0.287991] pci 0000:00:1f.3: [8086:2930] type 00 class 0x0c0500
+[    0.290370] pci 0000:00:1f.3: reg 0x20: [io  0x0700-0x073f]
+[    0.293435] ACPI: PCI: Interrupt link LNKA configured for IRQ 10
+[    0.293726] ACPI: PCI: Interrupt link LNKB configured for IRQ 10
+[    0.294744] ACPI: PCI: Interrupt link LNKC configured for IRQ 11
+[    0.295723] ACPI: PCI: Interrupt link LNKD configured for IRQ 11
+[    0.296740] ACPI: PCI: Interrupt link LNKE configured for IRQ 10
+[    0.297763] ACPI: PCI: Interrupt link LNKF configured for IRQ 10
+[    0.298722] ACPI: PCI: Interrupt link LNKG configured for IRQ 11
+[    0.299743] ACPI: PCI: Interrupt link LNKH configured for IRQ 11
+[    0.300662] ACPI: PCI: Interrupt link GSIA configured for IRQ 16
+[    0.301579] ACPI: PCI: Interrupt link GSIB configured for IRQ 17
+[    0.301618] ACPI: PCI: Interrupt link GSIC configured for IRQ 18
+[    0.302625] ACPI: PCI: Interrupt link GSID configured for IRQ 19
+[    0.303570] ACPI: PCI: Interrupt link GSIE configured for IRQ 20
+[    0.303617] ACPI: PCI: Interrupt link GSIF configured for IRQ 21
+[    0.304524] ACPI: PCI: Interrupt link GSIG configured for IRQ 22
+[    0.304617] ACPI: PCI: Interrupt link GSIH configured for IRQ 23
+[    0.307401] iommu: Default domain type: Translated 
+[    0.307611] iommu: DMA domain TLB invalidation policy: lazy mode 
+[    0.309801] pci 0000:00:02.0: vgaarb: setting as boot VGA device
+[    0.310602] pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
+[    0.310612] pci 0000:00:02.0: vgaarb: bridge control possible
+[    0.311469] vgaarb: loaded
+[    0.312823] SCSI subsystem initialized
+[    0.314995] libata version 3.00 loaded.
+[    0.315348] ACPI: bus type USB registered
+[    0.315984] usbcore: registered new interface driver usbfs
+[    0.316671] usbcore: registered new interface driver hub
+[    0.317497] usbcore: registered new device driver usb
+[    0.317760] pps_core: LinuxPPS API ver. 1 registered
+[    0.318568] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
+[    0.318672] PTP clock support registered
+[    0.320169] Advanced Linux Sound Architecture Driver Initialized.
+[    0.322001] NetLabel: Initializing
+[    0.322614] NetLabel:  domain hash size = 128
+[    0.323353] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
+[    0.323799] NetLabel:  unlabeled traffic allowed by default
+[    0.324864] PCI: Using ACPI for IRQ routing
+[    0.486511] PCI: pci_cache_line_size set to 64 bytes
+[    0.487017] e820: reserve RAM buffer [mem 0x0009fc00-0x0009ffff]
+[    0.487056] e820: reserve RAM buffer [mem 0x7ffde000-0x7fffffff]
+[    0.488868] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
+[    0.489610] hpet0: 3 comparators, 64-bit 100.000000 MHz counter
+[    0.493993] clocksource: Switched to clocksource tsc-early
+[    0.595279] VFS: Disk quotas dquot_6.6.0
+[    0.604747] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
+[    0.606192] pnp: PnP ACPI init
+[    0.607564] system 00:05: [mem 0xb0000000-0xbfffffff window] has been reserved
+[    0.612917] pnp: PnP ACPI: found 6 devices
+[    0.630876] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
+[    0.635819] NET: Registered PF_INET protocol family
+[    0.639137] IP idents hash table entries: 65536 (order: 7, 524288 bytes, linear)
+[    0.648315] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes, linear)
+[    0.649938] TCP established hash table entries: 32768 (order: 6, 262144 bytes, linear)
+[    0.656731] TCP bind hash table entries: 32768 (order: 7, 524288 bytes, linear)
+[    0.668799] TCP: Hash tables configured (established 32768 bind 32768)
+[    0.670725] UDP hash table entries: 2048 (order: 4, 65536 bytes, linear)
+[    0.675922] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes, linear)
+[    0.677641] NET: Registered PF_UNIX/PF_LOCAL protocol family
+[    0.683489] RPC: Registered named UNIX socket transport module.
+[    0.684419] RPC: Registered udp transport module.
+[    0.685233] RPC: Registered tcp transport module.
+[    0.686051] RPC: Registered tcp NFSv4.1 backchannel transport module.
+[    0.690218] pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
+[    0.691147] pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
+[    0.692046] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
+[    0.695623] pci_bus 0000:00: resource 7 [mem 0x80000000-0xafffffff window]
+[    0.702621] pci_bus 0000:00: resource 8 [mem 0xc0000000-0xfebfffff window]
+[    0.703550] pci_bus 0000:00: resource 9 [mem 0x180000000-0x97fffffff window]
+[    0.709679] ACPI: \_SB_.GSIA: Enabled at IRQ 16
+[    0.711527] ACPI: \_SB_.GSIB: Enabled at IRQ 17
+[    0.717245] ACPI: \_SB_.GSIC: Enabled at IRQ 18
+[    0.718745] ACPI: \_SB_.GSID: Enabled at IRQ 19
+[    0.720153] PCI: CLS 0 bytes, default 64
+[    0.725883] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
+[    0.726841] software IO TLB: mapped [mem 0x000000007bfcf000-0x000000007ffcf000] (64MB)
+[    0.728264] Unpacking initramfs...
+[    0.744075] Freeing initrd memory: 4K
+[    0.756363] Initialise system trusted keyrings
+[    0.758663] workingset: timestamp_bits=56 max_order=20 bucket_order=0
+[    0.764972] NFS: Registering the id_resolver key type
+[    0.767942] Key type id_resolver registered
+[    0.768863] Key type id_legacy registered
+[    0.770030] 9p: Installing v9fs 9p2000 file system support
+[    0.775964] Key type asymmetric registered
+[    0.776761] Asymmetric key parser 'x509' registered
+[    0.777862] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
+[    0.779862] io scheduler mq-deadline registered
+[    0.780675] io scheduler kyber registered
+[    0.782859] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
+[    0.787721] ACPI: button: Power Button [PWRF]
+[    0.791799] ACPI: \_SB_.GSIF: Enabled at IRQ 21
+[    0.795895] ACPI: \_SB_.GSIG: Enabled at IRQ 22
+[    0.802029] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
+[    0.803727] 00:03: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
+[    0.806289] Non-volatile memory driver v1.3
+[    0.807110] Linux agpgart interface v0.103
+[    0.808280] ACPI: bus type drm_connector registered
+[    0.810106] [drm] pci: virtio-vga detected at 0000:00:02.0
+[    0.811033] virtio-pci 0000:00:02.0: vgaarb: deactivate vga console
+[    0.812950] Console: switching to colour dummy device 80x25
+[    0.814010] [drm] Host memory window: 0x180000000 +0x40000000
+[    0.814014] [drm] features: +virgl +edid +resource_blob +host_visible
+[    0.814015] [drm] features: +context_init
+[    0.815749] [drm] number of scanouts: 1
+[    0.815764] [drm] number of cap sets: 1
+[    0.822421] [drm] cap set 0: id 4, max-version 0, max-size 20
+[    0.823816] [drm] Initialized virtio_gpu 0.1.0 0 for virtio1 on minor 0
+[    0.835655] loop: module loaded
+[    0.836198] ahci 0000:00:1f.2: version 3.0
+[    0.838738] ahci 0000:00:1f.2: AHCI 0001.0000 32 slots 6 ports 1.5 Gbps 0x3f impl SATA mode
+[    0.838743] ahci 0000:00:1f.2: flags: 64bit ncq only 
+[    0.844268] scsi host0: ahci
+[    0.845062] scsi host1: ahci
+[    0.845675] scsi host2: ahci
+[    0.846482] scsi host3: ahci
+[    0.847257] scsi host4: ahci
+[    0.847860] scsi host5: ahci
+[    0.848240] ata1: SATA max UDMA/133 abar m4096@0xfebd3000 port 0xfebd3100 irq 27
+[    0.848266] ata2: SATA max UDMA/133 abar m4096@0xfebd3000 port 0xfebd3180 irq 27
+[    0.848281] ata3: SATA max UDMA/133 abar m4096@0xfebd3000 port 0xfebd3200 irq 27
+[    0.848295] ata4: SATA max UDMA/133 abar m4096@0xfebd3000 port 0xfebd3280 irq 27
+[    0.848310] ata5: SATA max UDMA/133 abar m4096@0xfebd3000 port 0xfebd3300 irq 27
+[    0.848324] ata6: SATA max UDMA/133 abar m4096@0xfebd3000 port 0xfebd3380 irq 27
+[    0.854343] e100: Intel(R) PRO/100 Network Driver
+[    0.854365] e100: Copyright(c) 1999-2006 Intel Corporation
+[    0.854401] e1000: Intel(R) PRO/1000 Network Driver
+[    0.854403] e1000: Copyright (c) 1999-2006 Intel Corporation.
+[    0.854505] e1000e: Intel(R) PRO/1000 Network Driver
+[    0.854506] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
+[    0.854562] sky2: driver version 1.30
+[    0.855224] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
+[    0.855227] ehci-pci: EHCI PCI platform driver
+[    0.856209] ehci-pci 0000:00:1d.7: EHCI Host Controller
+[    0.856447] ehci-pci 0000:00:1d.7: new USB bus registered, assigned bus number 1
+[    0.857195] ehci-pci 0000:00:1d.7: irq 19, io mem 0xfebd2000
+[    0.863684] ehci-pci 0000:00:1d.7: USB 2.0 started, EHCI 1.00
+[    0.863941] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.16
+[    0.863946] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
+[    0.863948] usb usb1: Product: EHCI Host Controller
+[    0.863950] usb usb1: Manufacturer: Linux 5.16.14 ehci_hcd
+[    0.863952] usb usb1: SerialNumber: 0000:00:1d.7
+[    0.864286] hub 1-0:1.0: USB hub found
+[    0.864294] hub 1-0:1.0: 6 ports detected
+[    0.864919] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
+[    0.864953] ohci-pci: OHCI PCI platform driver
+[    0.865050] uhci_hcd: USB Universal Host Controller Interface driver
+[    0.865658] uhci_hcd 0000:00:1d.0: UHCI Host Controller
+[    0.865792] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
+[    0.866072] uhci_hcd 0000:00:1d.0: irq 16, io port 0x0000c060
+[    0.866256] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.16
+[    0.866259] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
+[    0.866262] usb usb2: Product: UHCI Host Controller
+[    0.866263] usb usb2: Manufacturer: Linux 5.16.14 uhci_hcd
+[    0.866265] usb usb2: SerialNumber: 0000:00:1d.0
+[    0.866537] hub 2-0:1.0: USB hub found
+[    0.866542] hub 2-0:1.0: 2 ports detected
+[    0.867382] uhci_hcd 0000:00:1d.1: UHCI Host Controller
+[    0.867567] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
+[    0.867827] uhci_hcd 0000:00:1d.1: irq 17, io port 0x0000c080
+[    0.868033] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.16
+[    0.868037] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
+[    0.868039] usb usb3: Product: UHCI Host Controller
+[    0.868040] usb usb3: Manufacturer: Linux 5.16.14 uhci_hcd
+[    0.868042] usb usb3: SerialNumber: 0000:00:1d.1
+[    0.868240] hub 3-0:1.0: USB hub found
+[    0.868245] hub 3-0:1.0: 2 ports detected
+[    0.869174] uhci_hcd 0000:00:1d.2: UHCI Host Controller
+[    0.869321] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
+[    0.869553] uhci_hcd 0000:00:1d.2: irq 18, io port 0x0000c0a0
+[    0.869959] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.16
+[    0.869963] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
+[    0.869965] usb usb4: Product: UHCI Host Controller
+[    0.870002] usb usb4: Manufacturer: Linux 5.16.14 uhci_hcd
+[    0.870003] usb usb4: SerialNumber: 0000:00:1d.2
+[    0.870149] hub 4-0:1.0: USB hub found
+[    0.870153] hub 4-0:1.0: 2 ports detected
+[    0.870910] usbcore: registered new interface driver usblp
+[    0.870991] usbcore: registered new interface driver usb-storage
+[    0.871112] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
+[    0.873033] serio: i8042 KBD port at 0x60,0x64 irq 1
+[    0.873240] serio: i8042 AUX port at 0x60,0x64 irq 12
+[    0.874086] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
+[    0.878739] rtc_cmos 00:04: RTC can wake from S4
+[    0.880210] rtc_cmos 00:04: registered as rtc0
+[    0.880321] rtc_cmos 00:04: alarms up to one day, y3k, 242 bytes nvram, hpet irqs
+[    0.880886] i801_smbus 0000:00:1f.3: SMBus using PCI interrupt
+[    0.881236] i2c i2c-0: 1/1 memory slots populated (from DMI)
+[    0.881239] i2c i2c-0: Memory type 0x07 not supported yet, not instantiating SPD
+[    0.881737] device-mapper: ioctl: 4.45.0-ioctl (2021-03-22) initialised: dm-devel@redhat.com
+[    0.882038] hid: raw HID events driver (C) Jiri Kosina
+[    0.882495] usbcore: registered new interface driver usbhid
+[    0.882498] usbhid: USB HID core driver
+[    0.890838] Initializing XFRM netlink socket
+[    0.891351] NET: Registered PF_INET6 protocol family
+[    0.893594] Segment Routing with IPv6
+[    0.893647] In-situ OAM (IOAM) with IPv6
+[    0.893870] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
+[    0.894342] NET: Registered PF_PACKET protocol family
+[    0.894821] 9pnet: Installing 9P2000 support
+[    0.894914] Key type dns_resolver registered
+[    0.895481] IPI shorthand broadcast: enabled
+[    0.895672] sched_clock: Marking stable (908022380, -12397814)->(1044483817, -148859251)
+[    0.895978] registered taskstats version 1
+[    0.895980] Loading compiled-in X.509 certificates
+[    0.897126] cryptomgr_test (53) used greatest stack depth: 15480 bytes left
+[    0.897149] cryptomgr_test (54) used greatest stack depth: 15448 bytes left
+[    0.898086] cryptomgr_test (69) used greatest stack depth: 15392 bytes left
+[    0.900491] PM:   Magic number: 14:469:477
+[    0.901051] printk: console [netcon0] enabled
+[    0.901053] netconsole: network logging started
+[    0.901456] cfg80211: Loading compiled-in X.509 certificates for regulatory database
+[    0.903159] kworker/u2:6 (76) used greatest stack depth: 14656 bytes left
+[    0.903680] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
+[    0.903771] ALSA device list:
+[    0.903773]   No soundcards found.
+[    0.904412] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
+[    0.904450] cfg80211: failed to load regulatory.db
+[    1.094640] usb 1-1: new high-speed USB device number 2 using ehci-pci
+[    1.146521] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
+[    1.146780] ata1.00: ATA-7: QEMU HARDDISK, 2.5+, max UDMA/100
+[    1.146785] ata1.00: 33554432 sectors, multi 16: LBA48 NCQ (depth 32)
+[    1.146810] ata1.00: applying bridge limits
+[    1.147076] ata1.00: configured for UDMA/100
+[    1.147318] ata2: SATA link down (SStatus 0 SControl 300)
+[    1.154178] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
+[    1.154371] ata3.00: ATAPI: QEMU DVD-ROM, 2.5+, max UDMA/100
+[    1.154375] ata3.00: applying bridge limits
+[    1.154673] ata3.00: configured for UDMA/100
+[    1.155258] ata4: SATA link down (SStatus 0 SControl 300)
+[    1.155530] ata5: SATA link down (SStatus 0 SControl 300)
+[    1.155833] ata6: SATA link down (SStatus 0 SControl 300)
+[    1.157704] scsi 0:0:0:0: Direct-Access     ATA      QEMU HARDDISK    2.5+ PQ: 0 ANSI: 5
+[    1.158268] sd 0:0:0:0: [sda] 33554432 512-byte logical blocks: (17.2 GB/16.0 GiB)
+[    1.158307] sd 0:0:0:0: [sda] Write Protect is off
+[    1.158309] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
+[    1.158316] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
+[    1.158993] sd 0:0:0:0: Attached scsi generic sg0 type 0
+[    1.165858] scsi 2:0:0:0: CD-ROM            QEMU     QEMU DVD-ROM     2.5+ PQ: 0 ANSI: 5
+[    1.175815]  sda: sda1 sda2 sda3
+[    1.176475] sd 0:0:0:0: [sda] Attached SCSI disk
+[    1.181093] sr 2:0:0:0: [sr0] scsi3-mmc drive: 4x/4x cd/rw xa/form2 tray
+[    1.181149] cdrom: Uniform CD-ROM driver Revision: 3.20
+[    1.197445] sr 2:0:0:0: Attached scsi CD-ROM sr0
+[    1.197689] sr 2:0:0:0: Attached scsi generic sg1 type 5
+[    1.224877] usb 1-1: New USB device found, idVendor=0627, idProduct=0001, bcdDevice= 0.00
+[    1.224885] usb 1-1: New USB device strings: Mfr=1, Product=3, SerialNumber=10
+[    1.224887] usb 1-1: Product: QEMU USB Tablet
+[    1.224889] usb 1-1: Manufacturer: QEMU
+[    1.224891] usb 1-1: SerialNumber: 28754-0000:00:1d.7-1
+[    1.231334] input: QEMU QEMU USB Tablet as /devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1:1.0/0003:0627:0001.0001/input/input4
+[    1.231474] hid-generic 0003:0627:0001.0001: input,hidraw0: USB HID v0.01 Mouse [QEMU QEMU USB Tablet] on usb-0000:00:1d.7-1/input0
+[    1.484028] random: fast init done
+[    1.486085] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input3
+[    1.486277] md: Waiting for all devices to be available before autodetect
+[    1.486280] md: If you don't use raid, use raid=noautodetect
+[    1.486308] md: Autodetecting RAID arrays.
+[    1.486310] md: autorun ...
+[    1.486311] md: ... autorun DONE.
+[    1.489760] EXT4-fs (sda3): INFO: recovery required on readonly filesystem
+[    1.489764] EXT4-fs (sda3): write access will be enabled during recovery
+[    1.549515] EXT4-fs (sda3): recovery complete
+[    1.551218] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
+[    1.551395] VFS: Mounted root (ext4 filesystem) readonly on device 8:3.
+[    1.552185] devtmpfs: mounted
+[    1.564828] Freeing unused kernel image (initmem) memory: 1252K
+[    1.565429] Write protecting the kernel read-only data: 24576k
+[    1.588472] Freeing unused kernel image (text/rodata gap) memory: 2032K
+[    1.599305] Freeing unused kernel image (rodata/data gap) memory: 1092K
+[    1.600131] Run /sbin/init as init process
+[    1.600145]   with arguments:
+[    1.600145]     /sbin/init
+[    1.600145]     nokaslr
+[    1.600146]   with environment:
+[    1.600146]     HOME=/
+[    1.600146]     TERM=linux
+[    1.719163] systemd[1]: systemd 248.3-1ubuntu8.2 running in system mode. (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS -OPENSSL +ACL +BLKID +CURL +ELFUTILS -FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP -LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
+[    1.719924] systemd[1]: Detected virtualization kvm.
+[    1.719999] systemd[1]: Detected architecture x86-64.
+[    1.721691] systemd[1]: Hostname set to <lygstate-Standard-PC-Q35-ICH9-2009>.
+[    1.742316] (sd-executor) (84) used greatest stack depth: 13744 bytes left
+[    1.747792] tsc: Refined TSC clocksource calibration: 3699.944 MHz
+[    1.747936] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x6aaa423949d, max_idle_ns: 881591081251 ns
+[    1.748220] clocksource: Switched to clocksource tsc
+[    1.804055] friendly-recove (87) used greatest stack depth: 13736 bytes left
+[    1.857049] openvpn-generat (89) used greatest stack depth: 13672 bytes left
+[    1.857104] ls (104) used greatest stack depth: 13616 bytes left
+[    2.049195] systemd[1]: Queued start job for default target Graphical Interface.
+[    2.053399] systemd[1]: Created slice system-modprobe.slice.
+[    2.055075] systemd[1]: Created slice system-systemd\x2dfsck.slice.
+[    2.055330] systemd[1]: Created slice User and Session Slice.
+[    2.055443] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
+[    2.057210] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
+[    2.057325] systemd[1]: Reached target User and Group Name Lookups.
+[    2.057352] systemd[1]: Reached target Remote File Systems.
+[    2.057371] systemd[1]: Reached target Slices.
+[    2.057397] systemd[1]: Reached target Local Verity Integrity Protected Volumes.
+[    2.058182] systemd[1]: Listening on Syslog Socket.
+[    2.058530] systemd[1]: Listening on fsck to fsckd communication Socket.
+[    2.058768] systemd[1]: Listening on initctl Compatibility Named Pipe.
+[    2.059725] systemd[1]: Listening on Journal Audit Socket.
+[    2.059946] systemd[1]: Listening on Journal Socket (/dev/log).
+[    2.060156] systemd[1]: Listening on Journal Socket.
+[    2.060815] systemd[1]: Listening on udev Control Socket.
+[    2.060970] systemd[1]: Listening on udev Kernel Socket.
+[    2.065155] systemd[1]: Mounting Huge Pages File System...
+[    2.069417] systemd[1]: Mounting POSIX Message Queue File System...
+[    2.079658] systemd[1]: Mounting Kernel Debug File System...
+[    2.082741] systemd[1]: Mounting Kernel Trace File System...
+[    2.083848] systemd[1]: systemd-journald.service: unit configures an IP firewall, but the local system does not support BPF/cgroup firewalling.
+[    2.083853] systemd[1]: (This warning is only shown for the first unit using IP firewalling.)
+[    2.089029] systemd[1]: Starting Journal Service...
+[    2.275345] systemd[1]: Starting Set the console keyboard layout...
+[    2.331794] systemd[1]: Condition check resulted in Create list of static device nodes for the current kernel being skipped.
+[    2.373032] systemd[1]: Starting Load Kernel Module configfs...
+[    2.390012] systemd[1]: Starting Load Kernel Module drm...
+[    2.401425] systemd[1]: Starting Load Kernel Module fuse...
+[    2.418703] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
+[    2.420064] systemd[1]: Starting File System Check on Root Device...
+[    2.432087] systemd[1]: Starting Load Kernel Modules...
+[    2.452273] systemd[1]: Starting Coldplug All udev Devices...
+[    2.468269] systemd[1]: Starting Uncomplicated firewall...
+[    2.518424] systemd[1]: Mounted Huge Pages File System.
+[    2.518764] systemd[1]: Mounted POSIX Message Queue File System.
+[    2.518974] systemd[1]: Mounted Kernel Debug File System.
+[    2.519140] systemd[1]: Mounted Kernel Trace File System.
+[    2.530711] systemd[1]: modprobe@configfs.service: Deactivated successfully.
+[    2.531730] systemd[1]: Finished Load Kernel Module configfs.
+[    2.538860] systemd[1]: modprobe@drm.service: Deactivated successfully.
+[    2.544760] systemd[1]: Finished Load Kernel Module drm.
+[    2.545030] systemd[1]: modprobe@fuse.service: Deactivated successfully.
+[    2.546685] systemd[1]: Finished Load Kernel Module fuse.
+[    2.546931] systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
+[    2.546980] systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
+[    2.549652] systemd[1]: Failed to start Load Kernel Modules.
+[    2.552638] systemd[1]: Finished Uncomplicated firewall.
+[    2.553148] systemd[1]: Condition check resulted in FUSE Control File System being skipped.
+[    2.553189] systemd[1]: Condition check resulted in Kernel Configuration File System being skipped.
+[    2.557719] systemd[1]: Started File System Check Daemon to report status.
+[    2.566265] systemd[1]: Starting Apply Kernel Variables...
+[    2.579756] systemd[1]: Started Journal Service.
+[    2.641573] random: crng init done
+[    2.718179] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro. Quota mode: none.
+[    2.732681] Adding 752916k swap on /swapfile.  Priority:-2 extents:3 across:769300k 
+[    2.733844] swapon (132) used greatest stack depth: 13568 bytes left
+[    2.735312] systemd-journald[110]: Received client request to flush runtime journal.
+[    2.743169] systemd-journald[110]: File /var/log/journal/6baf11e8245c4ca98eface85b84be32f/system.journal corrupted or uncleanly shut down, renaming and replacing.
+[    2.811309] loop0: detected capacity change from 0 to 203424
+[    2.815025] loop1: detected capacity change from 0 to 126632
+[    2.815152] loop2: detected capacity change from 0 to 8
+[    2.827343] loop3: detected capacity change from 0 to 307976
+[    2.841748] loop0: detected capacity change from 0 to 133552
+[    2.843903] loop4: detected capacity change from 0 to 496320
+[    2.847378] loop1: detected capacity change from 0 to 111048
+[    2.914163] journal-offline (149) used greatest stack depth: 13344 bytes left
+[    3.788267] virtio_net virtio0 enp0s1: renamed from eth0
+[    9.114766] language-option (340) used greatest stack depth: 12992 bytes left
+[   12.965077] loop0: detected capacity change from 0 to 8
+[   15.602770] systemd-journald[110]: File /var/log/journal/6baf11e8245c4ca98eface85b84be32f/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
+[   19.878209] virtio_gpu virtio1: [drm] drm_plane_enable_fb_damage_clips() not called
+[  313.191235] loop0: detected capacity change from 0 to 8
+[  334.252458] loop0: detected capacity change from 0 to 126760
+[  336.575589] loop0: detected capacity change from 0 to 226664
+[  613.230337] loop0: detected capacity change from 0 to 8
+[  660.444496] kworker/dying (50) used greatest stack depth: 12400 bytes left
+[  809.013491] clocksource: timekeeping watchdog on CPU0: hpet wd-wd read-back delay of 65260ns
+[  809.013577] clocksource: wd-tsc-wd read-back delay of 1983150ns, clock-skew test skipped!
+[  913.163318] loop0: detected capacity change from 0 to 8
+[ 1213.159179] loop0: detected capacity change from 0 to 8
+[ 1513.151818] loop0: detected capacity change from 0 to 8
+[ 1813.150457] loop0: detected capacity change from 0 to 8
+```
diff --git a/results/classifier/gemma3:12b/kernel/923 b/results/classifier/gemma3:12b/kernel/923
new file mode 100644
index 00000000..53dbe557
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/923
@@ -0,0 +1,2 @@
+
+Kernel OOPS on SBSA-ref due to missing watchdog register
diff --git a/results/classifier/gemma3:12b/kernel/929 b/results/classifier/gemma3:12b/kernel/929
new file mode 100644
index 00000000..f085f529
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/929
@@ -0,0 +1,34 @@
+
+qemu-user syscall clone fails
+Description of problem:
+This seems very similar to the issue reported here (https://bugs.launchpad.net/qemu/+bug/1926996). When attempting to perform the clone syscall, an error of -1 is returned where I would expect it to succeed. Running the same executable outside of qemu works as expected.
+Steps to reproduce:
+1. gcc clone.c
+2. qemu-x86_64 a.out
+Additional information:
+I've tried building with gcc, zig cc, and clang and the output of each works fine when running natively, but running under qemu fails. I originally discovered it when cross compiling to riscv64 but it doesn't seem to be limited to that architecture.
+
+```
+// clone.c
+
+#include <linux/sched.h>
+#include <sched.h>
+#include <sys/syscall.h>
+#include <unistd.h>
+#include <stdio.h>
+
+int main(void) {
+
+  long pid = syscall( SYS_clone, 0, 0, 0, 0, 0 );
+
+  if (pid < 0) {
+    printf( "error %ld\n", pid );
+  } else if (pid == 0) {
+    printf( "child %ld\n", pid );
+  } else {
+    printf( "parent %ld\n", pid );
+  }
+
+  return 0;
+}
+```
diff --git a/results/classifier/gemma3:12b/kernel/932487 b/results/classifier/gemma3:12b/kernel/932487
new file mode 100644
index 00000000..3400aa4e
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/932487
@@ -0,0 +1,57 @@
+
+win32: git rev 59f971d crashes when accessing disk (coroutine issue)
+
+Host: XP SP3 / Vista SP2
+
+configure commandline: ./configure --target-list="i386-softmmu" --audio-drv-list=sdl --audio-card-list=ac97,sb16,adlib --disable-linux-aio --disable-vnc-thread --disable-vnc-jpeg --extra-cflags="-O0 -pipe"
+
+gcc -v:
+Using built-in specs.
+Target: mingw32
+Configured with: ../gcc-4.3.3/configure --prefix=/mingw --build=mingw32 --enable-languages=c,ada,c++,fortran,objc,obj-c++ --with-bugurl=http://www.tdragon.net/recentgcc/bugs.php --disable-nls --disable-win32-registry --enable-libgomp --disable-werror --enable-threads --disable-symvers --enable-cxx-flags='-fno-function-sections -fno-data-sections' --enable-fully-dynamic-string --enable-version-specific-runtime-libs --enable-sjlj-exceptions --with-pkgversion='4.3.3-tdm-1 mingw32'
+Thread model: win32
+gcc version 4.3.3 (4.3.3-tdm-1 mingw32)
+
+gdb output:
+C:\msys\home\User\qemu\i386-softmmu>gdb --args qemu-system-i386.exe -L ..\pc-bios -hda xp.vmdk
+GNU gdb (GDB) 7.3
+Copyright (C) 2011 Free Software Foundation, Inc.
+License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and redistribute it.
+There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
+and "show warranty" for details.
+This GDB was configured as "mingw32".
+For bug reporting instructions, please see:
+<http://www.gnu.org/software/gdb/bugs/>...
+Reading symbols from C:\msys\home\User\qemu\i386-softmmu/qemu-system-i386.exe...
+done.
+(gdb) r
+Starting program: C:\msys\home\User\qemu\i386-softmmu/qemu-system-i386.exe -L ..\\pc-bios -hda xp.vmdk
+[New Thread 2472.0x8e0]
+[New Thread 2472.0xdc4]
+[New Thread 2472.0x8f0]
+
+Program received signal SIGSEGV, Segmentation fault.
+[Switching to Thread 2472.0x8f0]
+0x7c81071e in SwitchToFiber () from C:\WINDOWS\system32\kernel32.dll
+(gdb) bt
+#0  0x7c81071e in SwitchToFiber () from C:\WINDOWS\system32\kernel32.dll
+#1  0x0044774c in qemu_coroutine_switch (from_=0x19593fc, to_=0xdcee9a8,
+    action=COROUTINE_YIELD) at coroutine-win32.c:48
+#2  0x004db18d in coroutine_swap (from=0x1e00, to=0xdcee9a8)
+    at qemu-coroutine.c:31
+#3  0x00411618 in bdrv_rw_co (bs=<optimized out>, sector_num=<optimized out>,
+    buf=0x2140000 "@", nb_sectors=1, is_write=false) at block.c:1335
+#4  0x00486e39 in ide_sector_read (s=0x1bbdaa0)
+    at C:/msys/home/User/qemu/hw/ide/core.c:480
+#5  0x0054e71f in memory_region_iorange_write (iorange=0x1bbcf60, offset=7,
+    width=1, data=32) at C:/msys/home/User/qemu/memory.c:431
+#6  0x005494e0 in ioport_writeb_thunk (opaque=0x1bbcf60, addr=7680, data=32)
+    at C:/msys/home/User/qemu/ioport.c:211
+#7  0x005496cf in ioport_write (data=<optimized out>,
+    address=<optimized out>, index=<optimized out>)
+    at C:/msys/home/User/qemu/ioport.c:82
+#8  cpu_outb (addr=2147340288, val=0 '\000')
+    at C:/msys/home/User/qemu/ioport.c:274
+#9  0x022c0397 in ?? ()
+Backtrace stopped: previous frame inner to this frame (corrupt stack?)
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/942659 b/results/classifier/gemma3:12b/kernel/942659
new file mode 100644
index 00000000..d299cdee
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/942659
@@ -0,0 +1,32 @@
+
+ARM: CORTEX M, PRIMASK does not disable interrupts
+
+qemu version 0.15.1
+but the same code is in qemu 1.0
+
+"CPSID I" does not disable interrupts for CORTEX M3
+
+
+if (interrupt_request & CPU_INTERRUPT_HARD
+                        && ((IS_M(env) && env->regs[15] < 0xfffffff0)
+                            || !(env->uncached_cpsr & CPSR_I))) {
+                        env->exception_index = EXCP_IRQ;
+                        do_interrupt(env);
+                        next_tb = 0;
+                    }
+
+
+do_interrupt() will be executed even if (env->uncached_cpsr & CPSR_I) == 1 , disable interrupt bit set.
+
+
+then changed to: 
+
+if (interrupt_request & CPU_INTERRUPT_HARD 
+                        && !(env->uncached_cpsr & CPSR_I)
+                        && (IS_M(env) ? env->regs[15] < 0xfffffff0: 1) ) {
+                        env->exception_index = EXCP_IRQ;
+                        do_interrupt(env);
+                        next_tb = 0;
+                    }
+
+works
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/948 b/results/classifier/gemma3:12b/kernel/948
new file mode 100644
index 00000000..206bf720
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/948
@@ -0,0 +1,33 @@
+
+7.0.0-rc1, -rc2 cannot build - config-poison.h is not generated
+Description of problem:
+`make` halts with:
+
+```
+[557/2583] Generating module_block.h with a custom command
+[558/2583] Generating block-gen.c with a custom command
+[559/2583] Generating x86_64-softmmu-gdbstub-xml.c with a custom command (wrapped by meson to capture output)
+[560/2583] Compiling C object libpage-vary-common.a.p/page-vary-common.c.o
+[561/2583] Generating trace-target_sparc.c with a custom command
+[562/2583] Generating trace-target_s390x_kvm.c with a custom command
+ninja: job failed: clang -m64 -mcx16 -Ilibpage-vary-common.a.p -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -flto -fcolor-diagnostics -Wall -Winvalid-pch -std=gnu11 -O2 -g -isystem /home/dummy/qemu-7.0.0-rc2/linux-headers -isystem linux-headers -iquote . -iquote /home/dummy/qemu-7.0.0-rc2 -iquote /home/dummy/qemu-7.0.0-rc2/include -iquote /home/dummy/qemu-7.0.0-rc2/disas/libvixl -iquote /home/dummy/qemu-7.0.0-rc2/tcg/i386 -pthread -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wno-initializer-overrides -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-string-plus-int -Wno-typedef-redefinition -Wno-tautological-type-limit-compare -Wno-psabi -fstack-protector-strong -fsanitize=cfi-icall -fsanitize-cfi-icall-generalize-pointers -fPIE -fno-lto -fno-sanitize=cfi-icall -MD -MQ libpage-vary-common.a.p/page-vary-common.c.o -MF libpage-vary-common.a.p/page-vary-common.c.o.d -o libpage-vary-common.a.p/page-vary-common.c.o -c ../page-vary-common.c
+In file included from ../page-vary-common.c:22:
+In file included from /home/dummy/qemu-7.0.0-rc2/include/qemu/osdep.h:34:
+/home/dummy/qemu-7.0.0-rc2/include/exec/poison.h:7:10: fatal error: 'config-poison.h' file not found
+#include "config-poison.h"
+         ^~~~~~~~~~~~~~~~~
+1 error generated.
+ninja: subcommand failed
+make[1]: *** [Makefile:163: run-ninja] Error 1
+make[1]: Leaving directory '/home/dummy/qemu-7.0.0-rc2/build'
+make: *** [GNUmakefile:11: all] Error 2
+
+```
+
+It seems that `config-poison.h` is not generated in `configure` and is not explicitly a dependency for some of necessary object file.
+Steps to reproduce:
+1. `docker pull alpine:3.15`
+2. `docker build -t qemubad .` with the attached dockerfile
+Additional information:
+6.2.0 is good
+7.0.0-rc0, 7.0.0-rc1, 7.0.0-rc2 exhibits the issue
diff --git a/results/classifier/gemma3:12b/kernel/949 b/results/classifier/gemma3:12b/kernel/949
new file mode 100644
index 00000000..4aaa9ef2
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/949
@@ -0,0 +1,315 @@
+
+M1 MacOS Panic with qemu version 6.2.0
+Description of problem:
+After running the command above, the macbook freeze and reboots, here is the stacktrace:
+```
+panic(cpu 2 caller 0xfffffe001748de90): vm_fault() KERN_FAILURE from guest fault on state 0xfffffe600c57c000 @sleh.c:3091
+Debugger message: panic
+Memory ID: 0x1
+OS release type: User
+OS version: 21D62
+Kernel version: Darwin Kernel Version 21.3.0: Wed Jan  5 21:37:58 PST 2022; root:xnu-8019.80.24~20/RELEASE_ARM64_T6000
+Fileset Kernelcache UUID: FA4EB485BA9DC1EBAA5D0E80232A48CC
+Kernel UUID: BADF56F4-2876-3FF4-AC12-F25E78B09AA1
+iBoot version: iBoot-7429.81.3
+secure boot?: YES
+Paniclog version: 13
+KernelCache slide: 0x000000000f9e8000
+KernelCache base:  0xfffffe00169ec000
+Kernel slide:      0x000000001021c000
+Kernel text base:  0xfffffe0017220000
+Kernel text exec slide: 0x0000000010304000
+Kernel text exec base:  0xfffffe0017308000
+mach_absolute_time: 0x2c74ea4beb
+Epoch Time:        sec       usec
+  Boot    : 0x62437319 0x0002a603
+  Sleep   : 0x62441e87 0x00018bb3
+  Wake    : 0x62442289 0x00044ebb
+  Calendar: 0x62442c00 0x000ccb26
+
+Zone info:
+Foreign   : 0xfffffe001fb94000 - 0xfffffe001fba8000
+Native    : 0xfffffe10001a8000 - 0xfffffe30001a8000
+Readonly  : 0xfffffe14cce74000 - 0xfffffe1666808000
+Metadata  : 0xfffffe62f056c000 - 0xfffffe62fc4f0000
+Bitmaps   : 0xfffffe62fc4f0000 - 0xfffffe6302084000
+CORE 0 PVH locks held: None
+CORE 1 PVH locks held: None
+CORE 2 PVH locks held: None
+CORE 3 PVH locks held: None
+CORE 4 PVH locks held: None
+CORE 5 PVH locks held: None
+CORE 6 PVH locks held: None
+CORE 7 PVH locks held: None
+CORE 0: PC=0xfffffe001738ef4c, LR=0xfffffe001738ef4c, FP=0xfffffe60ba06bef0
+CORE 1: PC=0xfffffe001738ef4c, LR=0xfffffe001738ef4c, FP=0xfffffe60b7003ef0
+CORE 2 is the one that panicked. Check the full backtrace for details.
+CORE 3: PC=0xfffffe001738ef50, LR=0xfffffe001738ef4c, FP=0xfffffe600c773ef0
+CORE 4: PC=0xfffffe001738ef50, LR=0xfffffe001738ef4c, FP=0xfffffe60a4dabef0
+CORE 5: PC=0xfffffe001738ef50, LR=0xfffffe001738ef4c, FP=0xfffffe600c683ef0
+CORE 6: PC=0xfffffe001738ef50, LR=0xfffffe001738ef4c, FP=0xfffffe60a5553ef0
+CORE 7: PC=0xfffffe001738ef4c, LR=0xfffffe001738ef4c, FP=0xfffffe60b7ae3ef0
+Panicked task 0xfffffe2997ce2d48: 24310 pages, 11 threads: pid 12708: qemu-system-aarc
+Panicked thread: 0xfffffe1ffd861860, backtrace: 0xfffffe600c5c3300, tid: 97347
+		  lr: 0xfffffe001735a4e8  fp: 0xfffffe600c5c3370
+		  lr: 0xfffffe001735a1b8  fp: 0xfffffe600c5c33e0
+		  lr: 0xfffffe001749a2bc  fp: 0xfffffe600c5c3400
+		  lr: 0xfffffe001748c6c8  fp: 0xfffffe600c5c3480
+		  lr: 0xfffffe001748a118  fp: 0xfffffe600c5c3540
+		  lr: 0xfffffe001730f7f8  fp: 0xfffffe600c5c3550
+		  lr: 0xfffffe0017359e2c  fp: 0xfffffe600c5c38f0
+		  lr: 0xfffffe0017359e2c  fp: 0xfffffe600c5c3960
+		  lr: 0xfffffe0017b6d738  fp: 0xfffffe600c5c3980
+		  lr: 0xfffffe001748de90  fp: 0xfffffe600c5c39e0
+		  lr: 0xfffffe001748da14  fp: 0xfffffe600c5c3a50
+		  lr: 0xfffffe001731a828  fp: 0xfffffe600c5c3a60
+		  lr: 0xfffffe00174a222c  fp: 0xfffffe600c5c3e50
+		  lr: 0xfffffe001748a530  fp: 0xfffffe600c5c3f10
+		  lr: 0xfffffe001730f7f8  fp: 0xfffffe600c5c3f20
+
+last started kext at 861542788: com.apple.driver.driverkit.serial	6.0.0 (addr 0xfffffe00170fced0, size 3432)
+loaded kexts:
+com.apple.fileutil	20.036.15
+com.apple.filesystems.autofs	3.0
+com.apple.driver.AppleBiometricServices	1
+com.apple.driver.CoreKDL	1
+com.apple.driver.AppleTopCaseHIDEventDriver	5020.1
+com.apple.driver.DiskImages.ReadWriteDiskImage	493.0.0
+com.apple.driver.DiskImages.UDIFDiskImage	493.0.0
+com.apple.driver.DiskImages.RAMBackingStore	493.0.0
+com.apple.driver.DiskImages.FileBackingStore	493.0.0
+com.apple.driver.SEPHibernation	1
+com.apple.driver.BCMWLANFirmware4387.Hashstore	1
+com.apple.filesystems.apfs	1933.80.3
+com.apple.driver.AppleUSBDeviceNCM	5.0.0
+com.apple.driver.AppleThunderboltIP	4.0.3
+com.apple.driver.AppleFileSystemDriver	3.0.1
+com.apple.nke.l2tp	1.9
+com.apple.filesystems.tmpfs	1
+com.apple.filesystems.lifs	1
+com.apple.IOTextEncryptionFamily	1.0.0
+com.apple.filesystems.hfs.kext	582.60.2
+com.apple.security.BootPolicy	1
+com.apple.BootCache	40
+com.apple.AppleFSCompression.AppleFSCompressionTypeZlib	1.0.0
+com.apple.AppleFSCompression.AppleFSCompressionTypeDataless	1.0.0d1
+com.apple.AppleEmbeddedSimpleSPINORFlasher	1
+com.apple.driver.ApplePMP	1
+com.apple.driver.AppleCS42L84Audio	530.2
+com.apple.driver.AppleSmartIO2	1
+com.apple.driver.AppleSN012776Amp	530.2
+com.apple.driver.AppleT6000SOCTuner	1
+com.apple.driver.AppleT6000CLPCv3	1
+com.apple.driver.AppleSmartBatteryManager	161.0.0
+com.apple.driver.AppleALSColorSensor	1.0.0d1
+com.apple.driver.AppleAOPVoiceTrigger	100.1
+com.apple.driver.ApplePMPFirmware	1
+com.apple.driver.AppleSPMIPMU	1.0.1
+com.apple.driver.AppleM68Buttons	1.0.0d1
+com.apple.driver.AppleSDXC	3.1.1
+com.apple.driver.AppleSamsungSerial	1.0.0d1
+com.apple.driver.AppleSerialShim	1
+com.apple.AGXG13X	188.10
+com.apple.driver.AppleAVD	555
+com.apple.driver.AppleAVE2	530.3.0
+com.apple.driver.AppleJPEGDriver	4.7.9
+com.apple.driver.AppleProResHW	128.2.0
+com.apple.driver.AppleMobileDispT600X-DCP	140.0
+com.apple.driver.usb.AppleSynopsysUSB40XHCI	1
+com.apple.driver.AppleMCDP29XXUpdateSupport	1
+com.apple.driver.AppleDPDisplayTCON	1
+com.apple.driver.AppleEventLogHandler	1
+com.apple.driver.AppleS5L8960XNCO	1
+com.apple.driver.AppleT6000PMGR	1
+com.apple.driver.AppleS8000AES	1
+com.apple.driver.AppleS8000DWI	1.0.0d1
+com.apple.driver.AppleInterruptControllerV2	1.0.0d1
+com.apple.driver.AppleT8110DART	1
+com.apple.driver.AppleBluetoothModule	1
+com.apple.driver.AppleBCMWLANBusInterfacePCIe	1
+com.apple.driver.AppleS5L8920XPWM	1.0.0d1
+com.apple.driver.AudioDMAController-T600x	100.51
+com.apple.driver.AppleT6000DART	1
+com.apple.driver.AppleSPIMC	1
+com.apple.driver.AppleS5L8940XI2C	1.0.0d2
+com.apple.driver.AppleT6000	1
+com.apple.iokit.IOUserEthernet	1.0.1
+com.apple.driver.usb.AppleUSBUserHCI	1
+com.apple.iokit.IOKitRegistryCompatibility	1
+com.apple.iokit.EndpointSecurity	1
+com.apple.driver.AppleDiskImages2	126.60.3
+com.apple.AppleSystemPolicy	2.0.0
+com.apple.nke.applicationfirewall	402
+com.apple.kec.InvalidateHmac	1
+com.apple.kec.AppleEncryptedArchive	1
+com.apple.driver.driverkit.serial	6.0.0
+com.apple.kext.triggers	1.0
+com.apple.iokit.IOAVBFamily	1010.2
+com.apple.plugin.IOgPTPPlugin	1000.11
+com.apple.iokit.IOEthernetAVBController	1.1.0
+com.apple.driver.AppleMesaSEPDriver	100.99
+com.apple.iokit.IOBiometricFamily	1
+com.apple.driver.AppleHIDKeyboard	228
+com.apple.driver.AppleActuatorDriver	5430.21
+com.apple.driver.AppleMultitouchDriver	5430.21
+com.apple.driver.AppleHSBluetoothDriver	5020.1
+com.apple.driver.IOBluetoothHIDDriver	9.0.0
+com.apple.driver.DiskImages.KernelBacked	493.0.0
+com.apple.driver.AppleSEPHDCPManager	1.0.1
+com.apple.driver.AppleTrustedAccessory	1
+com.apple.iokit.AppleSEPGenericTransfer	1
+com.apple.driver.AppleXsanScheme	3
+com.apple.driver.usb.networking	5.0.0
+com.apple.driver.AppleThunderboltUSBDownAdapter	1.0.4
+com.apple.driver.AppleThunderboltPCIDownAdapter	4.1.1
+com.apple.driver.AppleThunderboltDPInAdapter	8.5.1
+com.apple.driver.AppleThunderboltDPAdapterFamily	8.5.1
+com.apple.nke.ppp	1.9
+com.apple.driver.AppleBSDKextStarter	3
+com.apple.filesystems.hfs.encodings.kext	1
+com.apple.driver.AppleConvergedIPCOLYBTControl	1
+com.apple.driver.AppleConvergedPCI	1
+com.apple.driver.AppleBluetoothDebug	1
+com.apple.driver.AppleBTM	1.0.1
+com.apple.driver.AppleHIDTransportSPI	5400.30
+com.apple.driver.AppleHIDTransport	5400.30
+com.apple.driver.AppleInputDeviceSupport	5400.30
+com.apple.driver.AppleDCPDPTXProxy	1.0.0
+com.apple.driver.DCPDPFamilyProxy	1
+com.apple.driver.AppleDiagnosticDataAccessReadOnly	1.0.0
+com.apple.driver.AppleCSEmbeddedAudio	530.2
+com.apple.driver.ApplePassthroughPPM	3.0
+com.apple.driver.AppleAOPAudio	102.2
+com.apple.driver.AppleEmbeddedAudio	530.2
+com.apple.iokit.AppleARMIISAudio	100.1
+com.apple.driver.AppleSPU	1
+com.apple.AGXFirmwareKextG13XRTBuddy	188.10
+com.apple.AGXFirmwareKextRTBuddy64	188.10
+com.apple.driver.AppleStockholmControl	1.0.0
+com.apple.iokit.IONVMeFamily	2.1.0
+com.apple.driver.AppleNANDConfigAccess	1.0.0
+com.apple.driver.AppleDialogPMU	1.0.1
+com.apple.driver.usb.AppleUSBHostPacketFilter	1.0
+com.apple.iokit.IOGPUFamily	35.11
+com.apple.driver.DCPAVFamilyProxy	1
+com.apple.iokit.IOMobileGraphicsFamily-DCP	343.0.0
+com.apple.driver.AppleDCP	1
+com.apple.driver.AppleFirmwareKit	1
+com.apple.iokit.IOMobileGraphicsFamily	343.0.0
+com.apple.driver.AppleSPMI	1.0.1
+com.apple.driver.AppleUSBXDCIARM	1.0
+com.apple.driver.AppleUSBXDCI	1.0
+com.apple.iokit.IOUSBDeviceFamily	2.0.0
+com.apple.driver.usb.AppleSynopsysUSBXHCI	1
+com.apple.driver.usb.AppleUSBXHCI	1.2
+com.apple.driver.AppleEmbeddedUSBHost	1
+com.apple.driver.usb.AppleUSBHub	1.2
+com.apple.driver.usb.AppleUSBHostCompositeDevice	1.2
+com.apple.driver.AppleT6000TypeCPhy	1
+com.apple.driver.AppleT8103TypeCPhy	1
+com.apple.driver.AppleHPM	3.4.4
+com.apple.driver.AppleSART	1
+com.apple.driver.ApplePMGR	1
+com.apple.driver.AppleARMWatchdogTimer	1
+com.apple.driver.AppleDisplayCrossbar	1.0.0
+com.apple.iokit.IODisplayPortFamily	1.0.0
+com.apple.driver.AppleTypeCPhy	1
+com.apple.driver.AppleThunderboltNHI	7.2.8
+com.apple.driver.AppleT6000PCIeC	1
+com.apple.iokit.IOThunderboltFamily	9.3.3
+com.apple.driver.ApplePIODMA	1
+com.apple.driver.AppleT600xPCIe	1
+com.apple.driver.AppleMultiFunctionManager	1
+com.apple.driver.AppleBluetoothDebugService	1
+com.apple.driver.AppleBCMWLANCore	1.0.0
+com.apple.iokit.IO80211Family	1200.12.2b1
+com.apple.driver.IOImageLoader	1.0.0
+com.apple.driver.AppleOLYHAL	1
+com.apple.driver.corecapture	1.0.4
+com.apple.driver.AppleEmbeddedPCIE	1
+com.apple.driver.AppleMCA2-T600x	600.95
+com.apple.driver.AppleEmbeddedAudioLibs	100.9.1
+com.apple.driver.AppleFirmwareUpdateKext	1
+com.apple.driver.AppleH13CameraInterface	4.87.0
+com.apple.driver.AppleH10PearlCameraInterface	17.0.3
+com.apple.driver.AppleGPIOICController	1.0.2
+com.apple.driver.AppleFireStormErrorHandler	1
+com.apple.driver.AppleMobileApNonce	1
+com.apple.iokit.IOTimeSyncFamily	1000.11
+com.apple.driver.DiskImages	493.0.0
+com.apple.iokit.IOGraphicsFamily	593
+com.apple.iokit.IOBluetoothSerialManager	9.0.0
+com.apple.iokit.IOBluetoothHostControllerUSBTransport	9.0.0
+com.apple.iokit.IOBluetoothHostControllerUARTTransport	9.0.0
+com.apple.iokit.IOBluetoothHostControllerTransport	9.0.0
+com.apple.driver.IOBluetoothHostControllerPCIeTransport	9.0.0
+com.apple.iokit.IOBluetoothFamily	9.0.0
+com.apple.driver.FairPlayIOKit	68.13.1
+com.apple.iokit.CSRBluetoothHostControllerUSBTransport	9.0.0
+com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport	9.0.0
+com.apple.driver.AppleSSE	1.0
+com.apple.driver.AppleSEPKeyStore	2
+com.apple.driver.AppleUSBTDM	532.40.7
+com.apple.iokit.IOUSBMassStorageDriver	209.40.6
+com.apple.iokit.IOPCIFamily	2.9
+com.apple.iokit.IOSCSIBlockCommandsDevice	452.60.2
+com.apple.iokit.IOSCSIArchitectureModelFamily	452.60.2
+com.apple.driver.AppleIPAppender	1.0
+com.apple.driver.AppleFDEKeyStore	28.30
+com.apple.driver.AppleEffaceableStorage	1.0
+com.apple.driver.AppleCredentialManager	1.0
+com.apple.driver.KernelRelayHost	1
+com.apple.iokit.IOUSBHostFamily	1.2
+com.apple.driver.AppleUSBHostMergeProperties	1.2
+com.apple.driver.usb.AppleUSBCommon	1.0
+com.apple.driver.AppleSMC	3.1.9
+com.apple.driver.RTBuddy	1.0.0
+com.apple.driver.AppleEmbeddedTempSensor	1.0.0
+com.apple.driver.AppleARMPMU	1.0
+com.apple.iokit.IOAccessoryManager	1.0.0
+com.apple.driver.AppleOnboardSerial	1.0
+com.apple.iokit.IOSkywalkFamily	1.0
+com.apple.driver.mDNSOffloadUserClient	1.0.1b8
+com.apple.iokit.IONetworkingFamily	3.4
+com.apple.iokit.IOSerialFamily	11
+com.apple.driver.AppleSEPManager	1.0.1
+com.apple.driver.AppleA7IOP	1.0.2
+com.apple.driver.IOSlaveProcessor	1
+com.apple.driver.AppleBiometricSensor	2
+com.apple.iokit.IOHIDFamily	2.0.0
+com.apple.iokit.CoreAnalyticsFamily	1
+com.apple.driver.AppleANELoadBalancer	5.35.2
+com.apple.driver.AppleH11ANEInterface	5.35.0
+com.apple.AUC	1.0
+com.apple.iokit.IOAVFamily	1.0.0
+com.apple.iokit.IOHDCPFamily	1.0.0
+com.apple.iokit.IOCECFamily	1
+com.apple.iokit.IOAudio2Family	1.0
+com.apple.driver.AppleIISController	100.1
+com.apple.driver.AppleAudioClockLibs	100.9.1
+com.apple.driver.AppleM2ScalerCSCDriver	265.0.0
+com.apple.iokit.IOSurface	302.11.1
+com.apple.driver.IODARTFamily	1
+com.apple.security.quarantine	4
+com.apple.security.sandbox	300.0
+com.apple.kext.AppleMatch	1.0.0d1
+com.apple.driver.AppleMobileFileIntegrity	1.0.5
+com.apple.security.AppleImage4	4.2.0
+com.apple.kext.CoreTrust	1
+com.apple.iokit.IOCryptoAcceleratorFamily	1.0.1
+com.apple.driver.AppleARMPlatform	1.0.2
+com.apple.iokit.IOStorageFamily	2.1
+com.apple.iokit.IOSlowAdaptiveClockingFamily	1.0.0
+com.apple.iokit.IOReportFamily	47
+com.apple.kec.pthread	1
+com.apple.kec.Libm	1
+com.apple.kec.corecrypto	12.0
+
+
+
+** Stackshot Succeeded ** Bytes Traced 456730 (Uncompressed 1205472) **
+```
+Steps to reproduce:
+1. run the qemu command above
+Additional information:
+
diff --git a/results/classifier/gemma3:12b/kernel/954 b/results/classifier/gemma3:12b/kernel/954
new file mode 100644
index 00000000..4c012b9d
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/954
@@ -0,0 +1,1258 @@
+
+qemu 6.2.0 with SEV in x86_64 initrd unpack ?
+Description of problem:
+The guest kernel panic from qemu 6.2.0, works fine on 6.0.0 and 6.1.0, works fine without SEV on 6.2.0 too.
+
+From our research it seems that initrd is not unpacked and initialized in an SEV context on 6.2.0 as we can see in logs without SEV that the initrd is well unpacked. Please have a look on additional informations for all the logs.
+
+We can see this crash during guest initialization:  
+```
+[    0.252891] VFS: Cannot open root device \(null)\ or unknown-block(0,0): error -6
+[    0.253054] Please append a correct \root=\ boot option; here are the available partitions:
+[    0.253179] 0100            4096 ram0 
+[    0.253181]  (driver?)
+[    0.253285] 0101            4096 ram1 
+[    0.253286]  (driver?)
+[    0.253389] 0102            4096 ram2 
+[    0.253390]  (driver?)
+[    0.253490] 0103            4096 ram3 
+[    0.253491]  (driver?)
+[    0.253595] 0104            4096 ram4 
+[    0.253596]  (driver?)
+[    0.253708] 0105            4096 ram5 
+[    0.253709]  (driver?)
+[    0.253816] 0106            4096 ram6 
+[    0.253817]  (driver?)
+[    0.253965] 0107            4096 ram7 
+[    0.253967]  (driver?)
+[    0.254065] 0108            4096 ram8 
+[    0.254066]  (driver?)
+[    0.254170] 0109            4096 ram9 
+[    0.254171]  (driver?)
+[    0.254274] 010a            4096 ram10 
+[    0.254276]  (driver?)
+[    0.254392] 010b            4096 ram11 
+[    0.254393]  (driver?)
+[    0.254514] 010c            4096 ram12 
+[    0.254516]  (driver?)
+[    0.254639] 010d            4096 ram13 
+[    0.254640]  (driver?)
+[    0.254755] 010e            4096 ram14 
+[    0.254756]  (driver?)
+[    0.254871] 010f            4096 ram15 
+[    0.254872]  (driver?)
+[    0.254996] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
+[    0.255115] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.15.31 #1
+[    0.255215] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015
+[    0.255339] Call Trace:
+[    0.255387]  <TASK>
+[    0.255430]  dump_stack_lvl+0x34/0x44
+[    0.255499]  panic+0xe8/0x27a
+[    0.255563]  mount_block_root+0x16b/0x1fe
+[    0.255631]  ? rest_init+0xc0/0xc0
+[    0.255692]  prepare_namespace+0x131/0x160
+[    0.255757]  ? rest_init+0xc0/0xc0
+[    0.255823]  kernel_init+0x11/0x100
+[    0.255889]  ret_from_fork+0x22/0x30
+[    0.255969]  </TASK>
+[    0.256061] Kernel Offset: disabled
+[    0.256130] Rebooting in 1 seconds..
+```
+Steps to reproduce:
+1. build kernel with right config (build_kernel from kata-containers) with sev support (-x sev) & get kata-containers initrd
+2. Launch the command on a AMD SEV compatible device
+
+This is a complex problem I guess I can provide more informations if needed.
+Additional information:
+We didn't see any logs from QEMU when running this command line even when putting -D file...
+
+Complete output from QEMU 6.2.0 with SEV :  
+```
+[    0.000000] Linux version 5.10.25 (gitlab-runner@runner-buildah0) (gcc (Debian 11.2.0-12) 11.2.0, GNU ld (GNU Binutils for Debian) 2.37) #1 SMP Tue Dec 7 11:43:22 CET 2021
+[    0.000000] Command line: tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k console=hvc0 console=hvc1 console=ttyS0 cryptomgr.notests net.ifnames=0 pci=lastbus=0 debug panic=1 nr_cpus=32 scsi_mod.scan=none agent.log=debug
+[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
+[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
+[    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
+[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
+[    0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
+[    0.000000] BIOS-provided physical RAM map:
+[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
+[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000007fffff] usable
+[    0.000000] BIOS-e820: [mem 0x0000000000800000-0x0000000000807fff] ACPI NVS
+[    0.000000] BIOS-e820: [mem 0x0000000000808000-0x000000000080ffff] usable
+[    0.000000] BIOS-e820: [mem 0x0000000000810000-0x00000000008fffff] ACPI NVS
+[    0.000000] BIOS-e820: [mem 0x0000000000900000-0x000000007f6eefff] usable
+[    0.000000] BIOS-e820: [mem 0x000000007f6ef000-0x000000007f96efff] reserved
+[    0.000000] BIOS-e820: [mem 0x000000007f96f000-0x000000007f97efff] ACPI data
+[    0.000000] BIOS-e820: [mem 0x000000007f97f000-0x000000007f9fefff] ACPI NVS
+[    0.000000] BIOS-e820: [mem 0x000000007f9ff000-0x000000007fe5ffff] usable
+[    0.000000] BIOS-e820: [mem 0x000000007fe60000-0x000000007fe7ffff] reserved
+[    0.000000] BIOS-e820: [mem 0x000000007fe80000-0x000000007fffffff] ACPI NVS
+[    0.000000] BIOS-e820: [mem 0x00000000b0000000-0x00000000bfffffff] reserved
+[    0.000000] NX (Execute Disable) protection: active
+[    0.000000] efi: EFI v2.70 by EDK II
+[    0.000000] efi: SMBIOS=0x7f7ab000 ACPI=0x7f97e000 ACPI 2.0=0x7f97e014 MEMATTR=0x7e9d8118
+[    0.000000] SMBIOS 2.8 present.
+[    0.000000] DMI: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015
+[    0.000000] Hypervisor detected: KVM
+[    0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00
+[    0.000000] kvm-clock: cpu 0, msr 3d401001, primary cpu clock
+[    0.000000] kvm-clock: using sched offset of 4061892066 cycles
+[    0.000003] clocksource: kvm-clock: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns
+[    0.000006] tsc: Detected 2994.372 MHz processor
+[    0.000159] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
+[    0.000162] e820: remove [mem 0x000a0000-0x000fffff] usable
+[    0.000169] last_pfn = 0x7fe60 max_arch_pfn = 0x400000000
+[    0.000215] MTRR default type: write-back
+[    0.000216] MTRR fixed ranges enabled:
+[    0.000218]   00000-9FFFF write-back
+[    0.000219]   A0000-FFFFF uncachable
+[    0.000220] MTRR variable ranges enabled:
+[    0.000222]   0 base 0000C0000000 mask FFFFC0000000 uncachable
+[    0.000224]   1 base 0000B0000000 mask FFFFF0000000 uncachable
+[    0.000225]   2 base 001000000000 mask FFF800000000 uncachable
+[    0.000226]   3 disabled
+[    0.000227]   4 disabled
+[    0.000228]   5 disabled
+[    0.000229]   6 disabled
+[    0.000229]   7 disabled
+[    0.000277] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT
+[    0.008747] Using GB pages for direct mapping
+[    0.009448] Secure boot could not be determined
+[    0.009466] ACPI: Early table checksum verification disabled
+[    0.009476] ACPI: RSDP 0x000000007F97E014 000024 (v02 BOCHS )
+[    0.009482] ACPI: XSDT 0x000000007F97D0E8 000054 (v01 BOCHS  BXPC     00000001      01000013)
+[    0.009490] ACPI: FACP 0x000000007F978000 0000F4 (v03 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.009497] ACPI: DSDT 0x000000007F979000 003EAE (v01 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.009502] ACPI: FACS 0x000000007F9DD000 000040
+[    0.009506] ACPI: APIC 0x000000007F977000 000170 (v01 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.009510] ACPI: HPET 0x000000007F976000 000038 (v01 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.009515] ACPI: SRAT 0x000000007F975000 0002D0 (v01 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.009519] ACPI: MCFG 0x000000007F974000 00003C (v01 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.009523] ACPI: WAET 0x000000007F973000 000028 (v01 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.009532] ACPI: Local APIC address 0xfee00000
+[    0.009575] Zone ranges:
+[    0.009576]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
+[    0.009578]   DMA32    [mem 0x0000000001000000-0x000000007fe5ffff]
+[    0.009580]   Normal   empty
+[    0.009581]   Device   empty
+[    0.009582] Movable zone start for each node
+[    0.009583] Early memory node ranges
+[    0.009585]   node   0: [mem 0x0000000000001000-0x000000000009ffff]
+[    0.009587]   node   0: [mem 0x0000000000100000-0x00000000007fffff]
+[    0.009588]   node   0: [mem 0x0000000000808000-0x000000000080ffff]
+[    0.009589]   node   0: [mem 0x0000000000900000-0x000000007f6eefff]
+[    0.009590]   node   0: [mem 0x000000007f9ff000-0x000000007fe5ffff]
+[    0.009592] Initmem setup node 0 [mem 0x0000000000001000-0x000000007fe5ffff]
+[    0.009595] On node 0 totalpages: 522743
+[    0.009596]   DMA zone: 59 pages used for memmap
+[    0.009597]   DMA zone: 1814 pages reserved
+[    0.009599]   DMA zone: 3751 pages, LIFO batch:0
+[    0.009931]   DMA zone: 29017 pages in unavailable ranges
+[    0.009933]   DMA32 zone: 8122 pages used for memmap
+[    0.009934]   DMA32 zone: 518992 pages, LIFO batch:63
+[    0.014254]   DMA32 zone: 1200 pages in unavailable ranges
+[    0.014984] ACPI: PM-Timer IO Port: 0x608
+[    0.014988] ACPI: Local APIC address 0xfee00000
+[    0.015002] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
+[    0.015201] IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
+[    0.015205] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
+[    0.015207] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
+[    0.015209] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
+[    0.015210] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
+[    0.015212] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
+[    0.015213] ACPI: IRQ0 used by override.
+[    0.015214] ACPI: IRQ5 used by override.
+[    0.015216] ACPI: IRQ9 used by override.
+[    0.015217] ACPI: IRQ10 used by override.
+[    0.015217] ACPI: IRQ11 used by override.
+[    0.015220] Using ACPI (MADT) for SMP configuration information
+[    0.015223] ACPI: HPET id: 0x8086a201 base: 0xfed00000
+[    0.015228] TSC deadline timer available
+[    0.015233] smpboot: Allowing 32 CPUs, 31 hotplug CPUs
+[    0.015245] kvm-guest: KVM setup pv remote TLB flush
+[    0.015254] kvm-guest: setup PV sched yield
+[    0.015272] [mem 0xc0000000-0xffffffff] available for PCI devices
+[    0.015274] Booting paravirtualized kernel on KVM
+[    0.015278] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
+[    0.020479] setup_percpu: NR_CPUS:240 nr_cpumask_bits:240 nr_cpu_ids:32 nr_node_ids:1
+[    0.021723] percpu: Embedded 42 pages/cpu s143360 r0 d28672 u262144
+[    0.021732] pcpu-alloc: s143360 r0 d28672 u262144 alloc=1*2097152
+[    0.021734] pcpu-alloc: [0] 00 01 02 03 04 05 06 07 [0] 08 09 10 11 12 13 14 15
+[    0.021744] pcpu-alloc: [0] 16 17 18 19 20 21 22 23 [0] 24 25 26 27 28 29 30 31
+[    0.027310] kvm-guest: KVM setup async PF for cpu 0
+[    0.027318] kvm-guest: stealtime: cpu 0, msr 7d622080
+[    0.027332] Built 1 zonelists, mobility grouping on.  Total pages: 512748
+[    0.027335] Kernel command line: tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k console=hvc0 console=hvc1 console=ttyS0 cryptomgr.notests net.ifnames=0 pci=lastbus=0 debug panic=1 nr_cpus=32 scsi_mod.scan=none agent.log=debug
+[    0.027480] printk: log_buf_len individual max cpu contribution: 4096 bytes
+[    0.027481] printk: log_buf_len total cpu_extra contributions: 126976 bytes
+[    0.027483] printk: log_buf_len min size: 131072 bytes
+[    0.027731] printk: log_buf_len: 262144 bytes
+[    0.027733] printk: early log buf free: 123344(94%)
+[    0.027942] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
+[    0.028047] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
+[    0.028190] mem auto-init: stack:off, heap alloc:off, heap free:off
+[    0.041061] Memory: 1815804K/2090972K available (10242K kernel code, 956K rwdata, 1456K rodata, 892K init, 3564K bss, 274912K reserved, 0K cma-reserved)
+[    0.041173] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=32, Nodes=1
+[    0.041309] rcu: Hierarchical RCU implementation.
+[    0.041311] rcu: 	RCU restricting CPUs from NR_CPUS=240 to nr_cpu_ids=32.
+[    0.041312] 	All grace periods are expedited (rcu_expedited).
+[    0.041313] 	Tracing variant of Tasks RCU enabled.
+[    0.041315] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
+[    0.041316] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=32
+[    0.041372] NR_IRQS: 15616, nr_irqs: 680, preallocated irqs: 16
+[    0.041910] rcu: 	Offload RCU callbacks from CPUs: (none).
+[    0.042080] random: get_random_bytes called from start_kernel+0x2fc/0x4ae with crng_init=0
+[    0.042159] Console: colour dummy device 80x25
+[    0.162231] printk: console [ttyS0] enabled
+[    0.175286] AMD Memory Encryption Features active: SEV
+[    0.176044] ACPI: Core revision 20200925
+[    0.176768] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604467 ns
+[    0.178070] APIC: Switch to symmetric I/O mode setup
+[    0.180011] x2apic enabled
+[    0.182376] Switched APIC routing to physical x2apic.
+[    0.183044] kvm-guest: setup PV IPIs
+[    0.189694] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
+[    0.190655] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x2b29812ce43, max_idle_ns: 440795323173 ns
+[    0.191992] Calibrating delay loop (skipped) preset value.. 5988.74 BogoMIPS (lpj=11977488)
+[    0.193096] pid_max: default: 32768 minimum: 301
+[    0.224045] LSM: Security Framework initializing
+[    0.225340] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
+[    0.226368] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
+[    0.227912] x86/cpu: User Mode Instruction Prevention (UMIP) activated
+[    0.228021] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
+[    0.228758] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
+[    0.229578] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
+[    0.230655] Spectre V2 : Mitigation: Full AMD retpoline
+[    0.231993] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
+[    0.233038] Spectre V2 : Enabling Restricted Speculation for firmware calls
+[    0.234868] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
+[    0.235997] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp
+[    0.237657] Freeing SMP alternatives memory: 28K
+[    0.238528] smpboot: CPU0: AMD EPYC 7302P 16-Core Processor (family: 0x17, model: 0x31, stepping: 0x0)
+[    0.239991] Performance Events: Fam17h+ core perfctr, AMD PMU driver.
+[    0.239991] ... version:                0
+[    0.239991] ... bit width:              48
+[    0.239991] ... generic registers:      6
+[    0.239997] ... value mask:             0000ffffffffffff
+[    0.240552] ... max period:             00007fffffffffff
+[    0.241107] ... fixed-purpose events:   0
+[    0.241610] ... event mask:             000000000000003f
+[    0.242405] rcu: Hierarchical SRCU implementation.
+[    0.243319] smp: Bringing up secondary CPUs ...
+[    0.243787] smp: Brought up 1 node, 1 CPU
+[    0.244000] smpboot: Max logical packages: 32
+[    0.244475] smpboot: Total of 1 processors activated (5988.74 BogoMIPS)
+[    0.245487] devtmpfs: initialized
+[    0.245852] x86/mm: Memory block size: 128MB
+[    0.246502] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
+[    0.247472] futex hash table entries: 8192 (order: 7, 524288 bytes, linear)
+[    0.248308] NET: Registered protocol family 16
+[    0.249031] DMA: preallocated 256 KiB GFP_KERNEL pool for atomic allocations
+[    0.250111] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
+[    0.251331] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
+[    0.252043] thermal_sys: Registered thermal governor 'step_wise'
+[    0.252048] cpuidle: using governor menu
+[    0.253569] ACPI: bus type PCI registered
+[    0.253974] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
+[    0.254656] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xb0000000-0xbfffffff] (base 0xb0000000)
+[    0.255546] PCI: MMCONFIG at [mem 0xb0000000-0xbfffffff] reserved in E820
+[    0.256020] PCI: Using configuration type 1 for base access
+[    0.257219] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
+[    0.257889] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
+[    0.258633] ACPI: Added _OSI(Module Device)
+[    0.259073] ACPI: Added _OSI(Processor Device)
+[    0.259531] ACPI: Added _OSI(3.0 _SCP Extensions)
+[    0.259999] ACPI: Added _OSI(Processor Aggregator Device)
+[    0.260534] ACPI: Added _OSI(Linux-Dell-Video)
+[    0.260979] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
+[    0.261508] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
+[    0.263748] ACPI: 1 ACPI AML tables successfully acquired and loaded
+[    0.264963] ACPI: Interpreter enabled
+[    0.265375] ACPI: (supports S0 S5)
+[    0.265743] ACPI: Using IOAPIC for interrupt routing
+[    0.266290] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
+[    0.267390] ACPI: Enabled 3 GPEs in block 00 to 3F
+[    0.272364] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
+[    0.273025] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3]
+[    0.274136] acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug LTR]
+[    0.275108] acpi PNP0A08:00: _OSC: OS now controls [SHPCHotplug PME PCIeCapability]
+[    0.276009] PCI host bridge to bus 0000:00
+[    0.276413] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
+[    0.277047] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
+[    0.277707] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
+[    0.278440] pci_bus 0000:00: root bus resource [mem 0x80000000-0xafffffff window]
+[    0.279154] pci_bus 0000:00: root bus resource [mem 0xc0000000-0xfebfffff window]
+[    0.279885] pci_bus 0000:00: root bus resource [mem 0x1000000000-0x17ffffffff window]
+[    0.279995] pci_bus 0000:00: root bus resource [bus 00-ff]
+[    0.280579] pci 0000:00:00.0: [8086:29c0] type 00 class 0x060000
+[    0.281678] pci 0000:00:01.0: [1af4:1043] type 00 class 0x078000
+[    0.283998] pci 0000:00:01.0: reg 0x14: [mem 0xc0003000-0xc0003fff]
+[    0.287128] pci 0000:00:01.0: reg 0x20: [mem 0x1000000000-0x1000003fff 64bit pref]
+[    0.288918] pci 0000:00:02.0: [1b36:0001] type 01 class 0x060400
+[    0.294626] pci 0000:00:03.0: [1af4:1048] type 00 class 0x010000
+[    0.296349] pci 0000:00:03.0: reg 0x14: [mem 0xc0002000-0xc0002fff]
+[    0.299044] pci 0000:00:03.0: reg 0x20: [mem 0x1000004000-0x1000007fff 64bit pref]
+[    0.300892] pci 0000:00:04.0: [1af4:1044] type 00 class 0x00ff00
+[    0.303526] pci 0000:00:04.0: reg 0x20: [mem 0x1000008000-0x100000bfff 64bit pref]
+[    0.304902] pci 0000:00:05.0: [1af4:1049] type 00 class 0x000200
+[    0.306875] pci 0000:00:05.0: reg 0x14: [mem 0xc0001000-0xc0001fff]
+[    0.309436] pci 0000:00:05.0: reg 0x20: [mem 0x100000c000-0x100000ffff 64bit pref]
+[    0.311525] pci 0000:00:1f.0: [8086:2918] type 00 class 0x060100
+[    0.312373] pci 0000:00:1f.0: quirk: [io  0x0600-0x067f] claimed by ICH6 ACPI/GPIO/TCO
+[    0.314653] pci 0000:00:1f.2: [8086:2922] type 00 class 0x010601
+[    0.318160] pci 0000:00:1f.2: reg 0x20: [io  0x6040-0x605f]
+[    0.319336] pci 0000:00:1f.2: reg 0x24: [mem 0xc0000000-0xc0000fff]
+[    0.320607] pci 0000:00:1f.3: [8086:2930] type 00 class 0x0c0500
+[    0.323429] pci 0000:00:1f.3: reg 0x20: [io  0x6000-0x603f]
+[    0.325167] pci_bus 0000:01: extended config space not accessible
+[    0.325943] acpiphp: Slot [0] registered
+[    0.326344] acpiphp: Slot [1] registered
+[    0.326753] acpiphp: Slot [2] registered
+[    0.327153] acpiphp: Slot [3] registered
+[    0.327557] acpiphp: Slot [4] registered
+[    0.327962] acpiphp: Slot [5] registered
+[    0.328009] acpiphp: Slot [6] registered
+[    0.328416] acpiphp: Slot [7] registered
+[    0.328817] acpiphp: Slot [8] registered
+[    0.329218] acpiphp: Slot [9] registered
+[    0.329625] acpiphp: Slot [10] registered
+[    0.330033] acpiphp: Slot [11] registered
+[    0.330448] acpiphp: Slot [12] registered
+[    0.330854] acpiphp: Slot [13] registered
+[    0.331261] acpiphp: Slot [14] registered
+[    0.331675] acpiphp: Slot [15] registered
+[    0.332008] acpiphp: Slot [16] registered
+[    0.332419] acpiphp: Slot [17] registered
+[    0.332827] acpiphp: Slot [18] registered
+[    0.333234] acpiphp: Slot [19] registered
+[    0.333647] acpiphp: Slot [20] registered
+[    0.334055] acpiphp: Slot [21] registered
+[    0.334468] acpiphp: Slot [22] registered
+[    0.334886] acpiphp: Slot [23] registered
+[    0.335298] acpiphp: Slot [24] registered
+[    0.335702] acpiphp: Slot [25] registered
+[    0.336008] acpiphp: Slot [26] registered
+[    0.336420] acpiphp: Slot [27] registered
+[    0.336824] acpiphp: Slot [28] registered
+[    0.337232] acpiphp: Slot [29] registered
+[    0.337636] acpiphp: Slot [30] registered
+[    0.338041] acpiphp: Slot [31] registered
+[    0.338650] pci 0000:00:02.0: PCI bridge to [bus 01]
+[    0.339776] pci_bus 0000:00: on NUMA node 0
+[    0.340242] ACPI: PCI Interrupt Link [LNKA] (IRQs 5 *10 11)
+[    0.340849] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11)
+[    0.341462] ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11)
+[    0.342076] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 10 *11)
+[    0.342685] ACPI: PCI Interrupt Link [LNKE] (IRQs 5 *10 11)
+[    0.343300] ACPI: PCI Interrupt Link [LNKF] (IRQs 5 *10 11)
+[    0.343918] ACPI: PCI Interrupt Link [LNKG] (IRQs 5 10 *11)
+[    0.344059] ACPI: PCI Interrupt Link [LNKH] (IRQs 5 10 *11)
+[    0.344636] ACPI: PCI Interrupt Link [GSIA] (IRQs *16)
+[    0.345142] ACPI: PCI Interrupt Link [GSIB] (IRQs *17)
+[    0.345660] ACPI: PCI Interrupt Link [GSIC] (IRQs *18)
+[    0.346245] ACPI: PCI Interrupt Link [GSID] (IRQs *19)
+[    0.346799] ACPI: PCI Interrupt Link [GSIE] (IRQs *20)
+[    0.347365] ACPI: PCI Interrupt Link [GSIF] (IRQs *21)
+[    0.347889] ACPI: PCI Interrupt Link [GSIG] (IRQs *22)
+[    0.348004] ACPI: PCI Interrupt Link [GSIH] (IRQs *23)
+[    0.349647] iommu: Default domain type: Translated
+[    0.350207] vgaarb: loaded
+[    0.350578] SCSI subsystem initialized
+[    0.350959] pps_core: LinuxPPS API ver. 1 registered
+[    0.351500] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
+[    0.352007] PTP clock support registered
+[    0.352415] Registered efivars operations
+[    0.352914] PCI: Using ACPI for IRQ routing
+[    0.353321] PCI: pci_cache_line_size set to 64 bytes
+[    0.353916] e820: reserve RAM buffer [mem 0x00810000-0x008fffff]
+[    0.354487] e820: reserve RAM buffer [mem 0x7f6ef000-0x7fffffff]
+[    0.355053] e820: reserve RAM buffer [mem 0x7fe60000-0x7fffffff]
+[    0.355719] clocksource: Switched to clocksource kvm-clock
+[    0.355991] pnp: PnP ACPI init
+[    0.355991] pnp 00:00: Plug and Play ACPI device, IDs PNP0303 (active)
+[    0.355991] pnp 00:01: Plug and Play ACPI device, IDs PNP0f13 (active)
+[    0.355991] pnp 00:02: Plug and Play ACPI device, IDs PNP0501 (active)
+[    0.355991] pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
+[    0.355991] system 00:04: [mem 0xb0000000-0xbfffffff window] has been reserved
+[    0.356347] system 00:04: Plug and Play ACPI device, IDs PNP0c01 (active)
+[    0.357410] pnp: PnP ACPI: found 5 devices
+[    0.362961] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
+[    0.363871] NET: Registered protocol family 2
+[    0.364474] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear)
+[    0.365307] TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear)
+[    0.366095] TCP bind hash table entries: 16384 (order: 6, 262144 bytes, linear)
+[    0.366893] TCP: Hash tables configured (established 16384 bind 16384)
+[    0.367563] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear)
+[    0.368255] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear)
+[    0.369036] NET: Registered protocol family 1
+[    0.369533] pci 0000:00:02.0: PCI bridge to [bus 01]
+[    0.371860] pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
+[    0.372477] pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
+[    0.373092] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
+[    0.373765] pci_bus 0000:00: resource 7 [mem 0x80000000-0xafffffff window]
+[    0.374428] pci_bus 0000:00: resource 8 [mem 0xc0000000-0xfebfffff window]
+[    0.375109] pci_bus 0000:00: resource 9 [mem 0x1000000000-0x17ffffffff window]
+[    0.375904] PCI: CLS 0 bytes, default 64
+[    0.376370] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
+[    0.377008] software IO TLB: mapped [mem 0x000000006f600000-0x0000000073600000] (64MB)
+[    0.377807] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x2b29812ce43, max_idle_ns: 440795323173 ns
+[    0.379980] workingset: timestamp_bits=46 max_order=19 bucket_order=0
+[    0.381847] fuse: init (API version 7.32)
+[    0.382462] SGI XFS with security attributes, no debug enabled
+[    0.383337] 9p: Installing v9fs 9p2000 file system support
+[    0.383950] NET: Registered protocol family 38
+[    0.384407] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
+[    0.385291] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
+[    0.386003] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
+[    0.386731] ACPI: Power Button [PWRF]
+[    0.387428] PCI Interrupt Link [GSIF] enabled at IRQ 21
+[    0.388885] PCI Interrupt Link [GSIH] enabled at IRQ 23
+[    0.390255] PCI Interrupt Link [GSIE] enabled at IRQ 20
+[    0.393749] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
+[    0.394570] 00:02: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
+[    0.409740] software IO TLB: Memory encryption is active and system is using DMA bounce buffers
+[    0.411320] printk: console [hvc0] enabled
+[    0.413415] brd: module loaded
+[    0.414644] loop: module loaded
+[    0.416081] scsi host0: Virtio SCSI HBA
+[    0.417023] random: fast init done
+[    0.417469] VFIO - User Level meta-driver version: 0.3
+[    0.418175] random: crng init done
+[    0.418975] xt_time: kernel timezone is -0000
+[    0.419488] IPVS: Registered protocols (TCP, UDP, SCTP, AH, ESP)
+[    0.420221] IPVS: Connection hash table configured (size=4096, memory=64Kbytes)
+[    0.421119] IPVS: ipvs loaded.
+[    0.421478] IPVS: [rr] scheduler registered.
+[    0.421979] IPVS: [wrr] scheduler registered.
+[    0.422475] IPVS: [lc] scheduler registered.
+[    0.422970] IPVS: [wlc] scheduler registered.
+[    0.423461] IPVS: [fo] scheduler registered.
+[    0.423982] IPVS: [ovf] scheduler registered.
+[    0.424546] IPVS: [lblc] scheduler registered.
+[    0.425067] IPVS: [lblcr] scheduler registered.
+[    0.425580] IPVS: [dh] scheduler registered.
+[    0.426081] IPVS: [sh] scheduler registered.
+[    0.426572] IPVS: [sed] scheduler registered.
+[    0.427084] IPVS: [nq] scheduler registered.
+[    0.427578] IPVS: ftp: loaded support on port[0] = 21
+[    0.428167] IPVS: [sip] pe registered.
+[    0.428794] ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully
+[    0.429549] Initializing XFRM netlink socket
+[    0.430136] NET: Registered protocol family 10
+[    0.430960] Segment Routing with IPv6
+[    0.431417] NET: Registered protocol family 17
+[    0.431971] 9pnet: Installing 9P2000 support
+[    0.433142] NET: Registered protocol family 40
+[    0.433718] IPI shorthand broadcast: enabled
+[    0.434218] sched_clock: Marking stable (290414430, 142054672)->(447457221, -14988119)
+[    0.435600] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
+[    0.436567] Please append a correct "root=" boot option; here are the available partitions:
+[    0.437750] 0100            4096 ram0
+[    0.437750]  (driver?)
+[    0.438478] 0101            4096 ram1
+[    0.438478]  (driver?)
+[    0.439182] 0102            4096 ram2
+[    0.439183]  (driver?)
+[    0.439896] 0103            4096 ram3
+[    0.439897]  (driver?)
+[    0.440629] 0104            4096 ram4
+[    0.440630]  (driver?)
+[    0.441346] 0105            4096 ram5
+[    0.441346]  (driver?)
+[    0.442052] 0106            4096 ram6
+[    0.442053]  (driver?)
+[    0.442756] 0107            4096 ram7
+[    0.442756]  (driver?)
+[    0.443457] 0108            4096 ram8
+[    0.443457]  (driver?)
+[    0.444177] 0109            4096 ram9
+[    0.444177]  (driver?)
+[    0.444893] 010a            4096 ram10
+[    0.444893]  (driver?)
+[    0.445609] 010b            4096 ram11
+[    0.445610]  (driver?)
+[    0.446339] 010c            4096 ram12
+[    0.446340]  (driver?)
+[    0.447056] 010d            4096 ram13
+[    0.447057]  (driver?)
+[    0.447781] 010e            4096 ram14
+[    0.447781]  (driver?)
+[    0.448512] 010f            4096 ram15
+[    0.448513]  (driver?)
+[    0.449263] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
+[    0.450170] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.25 #1
+[    0.450848] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015
+[    0.451699] Call Trace:
+[    0.451995]  dump_stack+0x57/0x6a
+[    0.452378]  panic+0xf6/0x292
+[    0.452745]  mount_block_root+0x2aa/0x324
+[    0.453197]  ? rest_init+0xaa/0xaa
+[    0.453587]  prepare_namespace+0x131/0x160
+[    0.454053]  ? rest_init+0xaa/0xaa
+[    0.454442]  kernel_init+0x5/0xf6
+[    0.454838]  ret_from_fork+0x22/0x30
+[    0.455282] Kernel Offset: disabled
+[    0.455676] Rebooting in 1 seconds..
+```
+
+Complete output from QEMU 6.2.0 without SEV :  
+```
+[    0.000000] Linux version 5.10.25 (gitlab-runner@runner-buildah0) (gcc (Debian 11.2.0-12) 11.2.0, GNU ld (GNU Binutils for Debian) 2.37) #1 SMP Tue Dec 7 11:43:22 CET 2021
+[    0.000000] Command line: tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k console=hvc0 console=hvc1 console=ttyS0 cryptomgr.notests net.ifnames=0 pci=lastbus=0 debug panic=1 nr_cpus=32 scsi_mod.scan=none agent.log=debug
+[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
+[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
+[    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
+[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
+[    0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
+[    0.000000] BIOS-provided physical RAM map:
+[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
+[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000007fffff] usable
+[    0.000000] BIOS-e820: [mem 0x0000000000800000-0x0000000000807fff] ACPI NVS
+[    0.000000] BIOS-e820: [mem 0x0000000000808000-0x000000000080ffff] usable
+[    0.000000] BIOS-e820: [mem 0x0000000000810000-0x00000000008fffff] ACPI NVS
+[    0.000000] BIOS-e820: [mem 0x0000000000900000-0x000000007f6eefff] usable
+[    0.000000] BIOS-e820: [mem 0x000000007f6ef000-0x000000007f96efff] reserved
+[    0.000000] BIOS-e820: [mem 0x000000007f96f000-0x000000007f97efff] ACPI data
+[    0.000000] BIOS-e820: [mem 0x000000007f97f000-0x000000007f9fefff] ACPI NVS
+[    0.000000] BIOS-e820: [mem 0x000000007f9ff000-0x000000007fe5ffff] usable
+[    0.000000] BIOS-e820: [mem 0x000000007fe60000-0x000000007fe7ffff] reserved
+[    0.000000] BIOS-e820: [mem 0x000000007fe80000-0x000000007fffffff] ACPI NVS
+[    0.000000] BIOS-e820: [mem 0x00000000b0000000-0x00000000bfffffff] reserved
+[    0.000000] NX (Execute Disable) protection: active
+[    0.000000] efi: EFI v2.70 by EDK II
+[    0.000000] efi: SMBIOS=0x7f7ab000 ACPI=0x7f97e000 ACPI 2.0=0x7f97e014 MEMATTR=0x7e687118
+[    0.000000] SMBIOS 2.8 present.
+[    0.000000] DMI: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015
+[    0.000000] Hypervisor detected: KVM
+[    0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00
+[    0.000000] kvm-clock: cpu 0, msr 37201001, primary cpu clock
+[    0.000000] kvm-clock: using sched offset of 2589542167 cycles
+[    0.000002] clocksource: kvm-clock: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns
+[    0.000004] tsc: Detected 2994.372 MHz processor
+[    0.000078] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
+[    0.000081] e820: remove [mem 0x000a0000-0x000fffff] usable
+[    0.000084] last_pfn = 0x7fe60 max_arch_pfn = 0x400000000
+[    0.000106] MTRR default type: write-back
+[    0.000107] MTRR fixed ranges enabled:
+[    0.000108]   00000-9FFFF write-back
+[    0.000109]   A0000-FFFFF uncachable
+[    0.000110] MTRR variable ranges enabled:
+[    0.000111]   0 base 0000C0000000 mask FFFFC0000000 uncachable
+[    0.000111]   1 base 0000B0000000 mask FFFFF0000000 uncachable
+[    0.000112]   2 base 001000000000 mask FFF800000000 uncachable
+[    0.000113]   3 disabled
+[    0.000113]   4 disabled
+[    0.000114]   5 disabled
+[    0.000114]   6 disabled
+[    0.000114]   7 disabled
+[    0.000141] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT
+[    0.004269] Using GB pages for direct mapping
+[    0.004654] Secure boot could not be determined
+[    0.004655] RAMDISK: [mem 0x6f1ee000-0x757f5fff]
+[    0.004668] ACPI: Early table checksum verification disabled
+[    0.004673] ACPI: RSDP 0x000000007F97E014 000024 (v02 BOCHS )
+[    0.004676] ACPI: XSDT 0x000000007F97D0E8 000054 (v01 BOCHS  BXPC     00000001      01000013)
+[    0.004682] ACPI: FACP 0x000000007F978000 0000F4 (v03 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.004686] ACPI: DSDT 0x000000007F979000 003EAE (v01 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.004688] ACPI: FACS 0x000000007F9DD000 000040
+[    0.004690] ACPI: APIC 0x000000007F977000 000170 (v01 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.004692] ACPI: HPET 0x000000007F976000 000038 (v01 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.004694] ACPI: SRAT 0x000000007F975000 0002D0 (v01 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.004696] ACPI: MCFG 0x000000007F974000 00003C (v01 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.004698] ACPI: WAET 0x000000007F973000 000028 (v01 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.004703] ACPI: Local APIC address 0xfee00000
+[    0.004734] Zone ranges:
+[    0.004735]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
+[    0.004736]   DMA32    [mem 0x0000000001000000-0x000000007fe5ffff]
+[    0.004737]   Normal   empty
+[    0.004738]   Device   empty
+[    0.004739] Movable zone start for each node
+[    0.004740] Early memory node ranges
+[    0.004741]   node   0: [mem 0x0000000000001000-0x000000000009ffff]
+[    0.004742]   node   0: [mem 0x0000000000100000-0x00000000007fffff]
+[    0.004743]   node   0: [mem 0x0000000000808000-0x000000000080ffff]
+[    0.004743]   node   0: [mem 0x0000000000900000-0x000000007f6eefff]
+[    0.004744]   node   0: [mem 0x000000007f9ff000-0x000000007fe5ffff]
+[    0.004746] Initmem setup node 0 [mem 0x0000000000001000-0x000000007fe5ffff]
+[    0.004747] On node 0 totalpages: 522743
+[    0.004748]   DMA zone: 59 pages used for memmap
+[    0.004749]   DMA zone: 1814 pages reserved
+[    0.004750]   DMA zone: 3751 pages, LIFO batch:0
+[    0.005315]   DMA zone: 29017 pages in unavailable ranges
+[    0.005316]   DMA32 zone: 8122 pages used for memmap
+[    0.005317]   DMA32 zone: 518992 pages, LIFO batch:63
+[    0.011640]   DMA32 zone: 1200 pages in unavailable ranges
+[    0.012025] ACPI: PM-Timer IO Port: 0x608
+[    0.012028] ACPI: Local APIC address 0xfee00000
+[    0.012037] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
+[    0.012063] IOAPIC[0]: apic_id 0, version 17, address 0xfec00000, GSI 0-23
+[    0.012065] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
+[    0.012067] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
+[    0.012068] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
+[    0.012069] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
+[    0.012070] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
+[    0.012071] ACPI: IRQ0 used by override.
+[    0.012072] ACPI: IRQ5 used by override.
+[    0.012073] ACPI: IRQ9 used by override.
+[    0.012073] ACPI: IRQ10 used by override.
+[    0.012074] ACPI: IRQ11 used by override.
+[    0.012076] Using ACPI (MADT) for SMP configuration information
+[    0.012077] ACPI: HPET id: 0x8086a201 base: 0xfed00000
+[    0.012082] TSC deadline timer available
+[    0.012085] smpboot: Allowing 32 CPUs, 31 hotplug CPUs
+[    0.012093] kvm-guest: KVM setup pv remote TLB flush
+[    0.012099] kvm-guest: setup PV sched yield
+[    0.012110] [mem 0xc0000000-0xffffffff] available for PCI devices
+[    0.012116] Booting paravirtualized kernel on KVM
+[    0.012119] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
+[    0.015048] setup_percpu: NR_CPUS:240 nr_cpumask_bits:240 nr_cpu_ids:32 nr_node_ids:1
+[    0.016599] percpu: Embedded 42 pages/cpu s143360 r0 d28672 u262144
+[    0.016605] pcpu-alloc: s143360 r0 d28672 u262144 alloc=1*2097152
+[    0.016606] pcpu-alloc: [0] 00 01 02 03 04 05 06 07 [0] 08 09 10 11 12 13 14 15
+[    0.016611] pcpu-alloc: [0] 16 17 18 19 20 21 22 23 [0] 24 25 26 27 28 29 30 31
+[    0.016637] kvm-guest: KVM setup async PF for cpu 0
+[    0.016641] kvm-guest: stealtime: cpu 0, msr 6e822080
+[    0.016645] Built 1 zonelists, mobility grouping on.  Total pages: 512748
+[    0.016646] Kernel command line: tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k console=hvc0 console=hvc1 console=ttyS0 cryptomgr.notests net.ifnames=0 pci=lastbus=0 debug panic=1 nr_cpus=32 scsi_mod.scan=none agent.log=debug
+[    0.016721] printk: log_buf_len individual max cpu contribution: 4096 bytes
+[    0.016722] printk: log_buf_len total cpu_extra contributions: 126976 bytes
+[    0.016723] printk: log_buf_len min size: 131072 bytes
+[    0.016904] printk: log_buf_len: 262144 bytes
+[    0.016905] printk: early log buf free: 123296(94%)
+[    0.017240] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
+[    0.017535] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
+[    0.017618] mem auto-init: stack:off, heap alloc:off, heap free:off
+[    0.021841] Memory: 1782444K/2090972K available (10242K kernel code, 956K rwdata, 1456K rodata, 892K init, 3564K bss, 308272K reserved, 0K cma-reserved)
+[    0.021920] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=32, Nodes=1
+[    0.022033] rcu: Hierarchical RCU implementation.
+[    0.022034] rcu: 	RCU restricting CPUs from NR_CPUS=240 to nr_cpu_ids=32.
+[    0.022035] 	All grace periods are expedited (rcu_expedited).
+[    0.022036] 	Tracing variant of Tasks RCU enabled.
+[    0.022037] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
+[    0.022038] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=32
+[    0.022058] NR_IRQS: 15616, nr_irqs: 680, preallocated irqs: 16
+[    0.022381] rcu: 	Offload RCU callbacks from CPUs: (none).
+[    0.022525] random: get_random_bytes called from start_kernel+0x2fc/0x4ae with crng_init=0
+[    0.022585] Console: colour dummy device 80x25
+[    0.103996] printk: console [ttyS0] enabled
+[    0.104387] ACPI: Core revision 20200925
+[    0.104866] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604467 ns
+[    0.105761] APIC: Switch to symmetric I/O mode setup
+[    0.106341] x2apic enabled
+[    0.106708] Switched APIC routing to physical x2apic.
+[    0.107178] kvm-guest: setup PV IPIs
+[    0.108191] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
+[    0.108739] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x2b29812ce43, max_idle_ns: 440795323173 ns
+[    0.109650] Calibrating delay loop (skipped) preset value.. 5988.74 BogoMIPS (lpj=11977488)
+[    0.113651] pid_max: default: 32768 minimum: 301
+[    0.129407] LSM: Security Framework initializing
+[    0.129680] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
+[    0.130330] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
+[    0.131738] x86/cpu: User Mode Instruction Prevention (UMIP) activated
+[    0.132339] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
+[    0.132849] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
+[    0.133655] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
+[    0.134398] Spectre V2 : Mitigation: Full AMD retpoline
+[    0.134857] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
+[    0.135570] Spectre V2 : Enabling Restricted Speculation for firmware calls
+[    0.136182] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
+[    0.136913] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp
+[    0.137807] Freeing SMP alternatives memory: 28K
+[    0.138326] smpboot: CPU0: AMD EPYC 7302P 16-Core Processor (family: 0x17, model: 0x31, stepping: 0x0)
+[    0.141129] Performance Events: Fam17h+ core perfctr, AMD PMU driver.
+[    0.141649] ... version:                0
+[    0.141657] ... bit width:              48
+[    0.142342] ... generic registers:      6
+[    0.143012] ... value mask:             0000ffffffffffff
+[    0.143904] ... max period:             00007fffffffffff
+[    0.144790] ... fixed-purpose events:   0
+[    0.145529] ... event mask:             000000000000003f
+[    0.145867] rcu: Hierarchical SRCU implementation.
+[    0.147346] smp: Bringing up secondary CPUs ...
+[    0.148411] smp: Brought up 1 node, 1 CPU
+[    0.149351] smpboot: Max logical packages: 32
+[    0.149660] smpboot: Total of 1 processors activated (5988.74 BogoMIPS)
+[    0.151208] devtmpfs: initialized
+[    0.151830] x86/mm: Memory block size: 128MB
+[    0.152836] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
+[    0.153662] futex hash table entries: 8192 (order: 7, 524288 bytes, linear)
+[    0.155199] NET: Registered protocol family 16
+[    0.156041] DMA: preallocated 256 KiB GFP_KERNEL pool for atomic allocations
+[    0.157242] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
+[    0.157661] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
+[    0.159023] thermal_sys: Registered thermal governor 'step_wise'
+[    0.159027] cpuidle: using governor menu
+[    0.161335] ACPI: bus type PCI registered
+[    0.161655] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
+[    0.162805] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xb0000000-0xbfffffff] (base 0xb0000000)
+[    0.164441] PCI: MMCONFIG at [mem 0xb0000000-0xbfffffff] reserved in E820
+[    0.165592] PCI: Using configuration type 1 for base access
+[    0.166553] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
+[    0.167679] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
+[    0.169123] ACPI: Added _OSI(Module Device)
+[    0.169657] ACPI: Added _OSI(Processor Device)
+[    0.170402] ACPI: Added _OSI(3.0 _SCP Extensions)
+[    0.171180] ACPI: Added _OSI(Processor Aggregator Device)
+[    0.172120] ACPI: Added _OSI(Linux-Dell-Video)
+[    0.172866] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
+[    0.173655] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
+[    0.176672] ACPI: 1 ACPI AML tables successfully acquired and loaded
+[    0.178693] ACPI: Interpreter enabled
+[    0.179358] ACPI: (supports S0 S5)
+[    0.179937] ACPI: Using IOAPIC for interrupt routing
+[    0.180969] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
+[    0.181842] ACPI: Enabled 3 GPEs in block 00 to 3F
+[    0.188692] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
+[    0.189662] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3]
+[    0.191262] acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug LTR]
+[    0.192546] acpi PNP0A08:00: _OSC: OS now controls [SHPCHotplug PME PCIeCapability]
+[    0.193820] PCI host bridge to bus 0000:00
+[    0.194509] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
+[    0.195642] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
+[    0.196770] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
+[    0.197654] pci_bus 0000:00: root bus resource [mem 0x80000000-0xafffffff window]
+[    0.198902] pci_bus 0000:00: root bus resource [mem 0xc0000000-0xfebfffff window]
+[    0.200182] pci_bus 0000:00: root bus resource [mem 0x1000000000-0x17ffffffff window]
+[    0.201533] pci_bus 0000:00: root bus resource [bus 00-ff]
+[    0.201712] pci 0000:00:00.0: [8086:29c0] type 00 class 0x060000
+[    0.203324] pci 0000:00:01.0: [1af4:1003] type 00 class 0x078000
+[    0.205657] pci 0000:00:01.0: reg 0x10: [io  0x60c0-0x60ff]
+[    0.208353] pci 0000:00:01.0: reg 0x14: [mem 0xc0003000-0xc0003fff]
+[    0.213657] pci 0000:00:01.0: reg 0x20: [mem 0x1000000000-0x1000003fff 64bit pref]
+[    0.218281] pci 0000:00:02.0: [1b36:0001] type 01 class 0x060400
+[    0.223034] pci 0000:00:03.0: [1af4:1004] type 00 class 0x010000
+[    0.225394] pci 0000:00:03.0: reg 0x10: [io  0x6080-0x60bf]
+[    0.226822] pci 0000:00:03.0: reg 0x14: [mem 0xc0002000-0xc0002fff]
+[    0.230911] pci 0000:00:03.0: reg 0x20: [mem 0x1000004000-0x1000007fff 64bit pref]
+[    0.235919] pci 0000:00:04.0: [1af4:1005] type 00 class 0x00ff00
+[    0.237656] pci 0000:00:04.0: reg 0x10: [io  0x6120-0x613f]
+[    0.241656] pci 0000:00:04.0: reg 0x20: [mem 0x1000008000-0x100000bfff 64bit pref]
+[    0.244288] pci 0000:00:05.0: [1af4:1009] type 00 class 0x000200
+[    0.247672] pci 0000:00:05.0: reg 0x10: [io  0x6040-0x607f]
+[    0.249624] pci 0000:00:05.0: reg 0x14: [mem 0xc0001000-0xc0001fff]
+[    0.252855] pci 0000:00:05.0: reg 0x20: [mem 0x100000c000-0x100000ffff 64bit pref]
+[    0.257540] pci 0000:00:1f.0: [8086:2918] type 00 class 0x060100
+[    0.258154] pci 0000:00:1f.0: quirk: [io  0x0600-0x067f] claimed by ICH6 ACPI/GPIO/TCO
+[    0.259985] pci 0000:00:1f.2: [8086:2922] type 00 class 0x010601
+[    0.264875] pci 0000:00:1f.2: reg 0x20: [io  0x6100-0x611f]
+[    0.267416] pci 0000:00:1f.2: reg 0x24: [mem 0xc0000000-0xc0000fff]
+[    0.269582] pci 0000:00:1f.3: [8086:2930] type 00 class 0x0c0500
+[    0.271746] pci 0000:00:1f.3: reg 0x20: [io  0x6000-0x603f]
+[    0.274063] pci_bus 0000:01: extended config space not accessible
+[    0.275352] acpiphp: Slot [0] registered
+[    0.276038] acpiphp: Slot [1] registered
+[    0.277675] acpiphp: Slot [2] registered
+[    0.278353] acpiphp: Slot [3] registered
+[    0.279150] acpiphp: Slot [4] registered
+[    0.279837] acpiphp: Slot [5] registered
+[    0.280509] acpiphp: Slot [6] registered
+[    0.281280] acpiphp: Slot [7] registered
+[    0.281677] acpiphp: Slot [8] registered
+[    0.282360] acpiphp: Slot [9] registered
+[    0.283032] acpiphp: Slot [10] registered
+[    0.283814] acpiphp: Slot [11] registered
+[    0.284510] acpiphp: Slot [12] registered
+[    0.285203] acpiphp: Slot [13] registered
+[    0.285678] acpiphp: Slot [14] registered
+[    0.286378] acpiphp: Slot [15] registered
+[    0.287111] acpiphp: Slot [16] registered
+[    0.288055] acpiphp: Slot [17] registered
+[    0.288803] acpiphp: Slot [18] registered
+[    0.289541] acpiphp: Slot [19] registered
+[    0.289674] acpiphp: Slot [20] registered
+[    0.290384] acpiphp: Slot [21] registered
+[    0.291086] acpiphp: Slot [22] registered
+[    0.291778] acpiphp: Slot [23] registered
+[    0.292480] acpiphp: Slot [24] registered
+[    0.293211] acpiphp: Slot [25] registered
+[    0.293674] acpiphp: Slot [26] registered
+[    0.294385] acpiphp: Slot [27] registered
+[    0.295071] acpiphp: Slot [28] registered
+[    0.295953] acpiphp: Slot [29] registered
+[    0.296769] acpiphp: Slot [30] registered
+[    0.297594] acpiphp: Slot [31] registered
+[    0.297916] pci 0000:00:02.0: PCI bridge to [bus 01]
+[    0.300138] pci_bus 0000:00: on NUMA node 0
+[    0.301275] ACPI: PCI Interrupt Link [LNKA] (IRQs 5 *10 11)
+[    0.301748] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11)
+[    0.302965] ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11)
+[    0.304172] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 10 *11)
+[    0.305263] ACPI: PCI Interrupt Link [LNKE] (IRQs 5 *10 11)
+[    0.305787] ACPI: PCI Interrupt Link [LNKF] (IRQs 5 *10 11)
+[    0.306849] ACPI: PCI Interrupt Link [LNKG] (IRQs 5 10 *11)
+[    0.308110] ACPI: PCI Interrupt Link [LNKH] (IRQs 5 10 *11)
+[    0.309202] ACPI: PCI Interrupt Link [GSIA] (IRQs *16)
+[    0.309667] ACPI: PCI Interrupt Link [GSIB] (IRQs *17)
+[    0.310565] ACPI: PCI Interrupt Link [GSIC] (IRQs *18)
+[    0.311446] ACPI: PCI Interrupt Link [GSID] (IRQs *19)
+[    0.312329] ACPI: PCI Interrupt Link [GSIE] (IRQs *20)
+[    0.313253] ACPI: PCI Interrupt Link [GSIF] (IRQs *21)
+[    0.313672] ACPI: PCI Interrupt Link [GSIG] (IRQs *22)
+[    0.314722] ACPI: PCI Interrupt Link [GSIH] (IRQs *23)
+[    0.317172] iommu: Default domain type: Translated
+[    0.317728] vgaarb: loaded
+[    0.318310] SCSI subsystem initialized
+[    0.318954] pps_core: LinuxPPS API ver. 1 registered
+[    0.319804] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
+[    0.321326] PTP clock support registered
+[    0.321687] Registered efivars operations
+[    0.322500] PCI: Using ACPI for IRQ routing
+[    0.323211] PCI: pci_cache_line_size set to 64 bytes
+[    0.324206] e820: reserve RAM buffer [mem 0x00810000-0x008fffff]
+[    0.325212] e820: reserve RAM buffer [mem 0x7f6ef000-0x7fffffff]
+[    0.325657] e820: reserve RAM buffer [mem 0x7fe60000-0x7fffffff]
+[    0.326754] clocksource: Switched to clocksource kvm-clock
+[    0.327844] pnp: PnP ACPI init
+[    0.328425] pnp 00:00: Plug and Play ACPI device, IDs PNP0303 (active)
+[    0.329649] pnp 00:01: Plug and Play ACPI device, IDs PNP0f13 (active)
+[    0.329809] pnp 00:02: Plug and Play ACPI device, IDs PNP0501 (active)
+[    0.331078] pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
+[    0.332465] system 00:04: [mem 0xb0000000-0xbfffffff window] has been reserved
+[    0.333902] system 00:04: Plug and Play ACPI device, IDs PNP0c01 (active)
+[    0.335579] pnp: PnP ACPI: found 5 devices
+[    0.341670] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
+[    0.343568] NET: Registered protocol family 2
+[    0.345189] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear)
+[    0.346697] TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear)
+[    0.348298] TCP bind hash table entries: 16384 (order: 6, 262144 bytes, linear)
+[    0.349954] TCP: Hash tables configured (established 16384 bind 16384)
+[    0.351468] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear)
+[    0.352774] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear)
+[    0.354001] NET: Registered protocol family 1
+[    0.354738] pci 0000:00:02.0: PCI bridge to [bus 01]
+[    0.359275] pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
+[    0.360332] pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
+[    0.361390] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
+[    0.362681] pci_bus 0000:00: resource 7 [mem 0x80000000-0xafffffff window]
+[    0.364042] pci_bus 0000:00: resource 8 [mem 0xc0000000-0xfebfffff window]
+[    0.365243] pci_bus 0000:00: resource 9 [mem 0x1000000000-0x17ffffffff window]
+[    0.366666] PCI: CLS 0 bytes, default 64
+[    0.367453] Trying to unpack rootfs image as initramfs...
+[    2.474287] Freeing initrd memory: 104480K
+[    2.474789] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x2b29812ce43, max_idle_ns: 440795323173 ns
+[    2.476083] workingset: timestamp_bits=46 max_order=19 bucket_order=0
+[    2.477757] fuse: init (API version 7.32)
+[    2.478215] SGI XFS with security attributes, no debug enabled
+[    2.478997] 9p: Installing v9fs 9p2000 file system support
+[    2.479591] NET: Registered protocol family 38
+[    2.480035] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
+[    2.480870] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
+[    2.481582] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
+[    2.482309] ACPI: Power Button [PWRF]
+[    2.482943] PCI Interrupt Link [GSIF] enabled at IRQ 21
+[    2.484131] PCI Interrupt Link [GSIH] enabled at IRQ 23
+[    2.485303] PCI Interrupt Link [GSIE] enabled at IRQ 20
+[    2.486896] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
+[    2.487599] 00:02: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
+[    2.513070] printk: console [hvc0] enabled
+[    2.514550] brd: module loaded
+[    2.515360] random: fast init done
+[    2.516052] loop: module loaded
+[    2.516563] random: crng init done
+[    2.517477] scsi host0: Virtio SCSI HBA
+[    2.518342] VFIO - User Level meta-driver version: 0.3
+[    2.519286] xt_time: kernel timezone is -0000
+[    2.519803] IPVS: Registered protocols (TCP, UDP, SCTP, AH, ESP)
+[    2.520504] IPVS: Connection hash table configured (size=4096, memory=64Kbytes)
+[    2.521364] IPVS: ipvs loaded.
+[    2.521734] IPVS: [rr] scheduler registered.
+[    2.522232] IPVS: [wrr] scheduler registered.
+[    2.522732] IPVS: [lc] scheduler registered.
+[    2.523234] IPVS: [wlc] scheduler registered.
+[    2.523733] IPVS: [fo] scheduler registered.
+[    2.524237] IPVS: [ovf] scheduler registered.
+[    2.524741] IPVS: [lblc] scheduler registered.
+[    2.525253] IPVS: [lblcr] scheduler registered.
+[    2.525778] IPVS: [dh] scheduler registered.
+[    2.526281] IPVS: [sh] scheduler registered.
+[    2.526770] IPVS: [sed] scheduler registered.
+[    2.527273] IPVS: [nq] scheduler registered.
+[    2.527761] IPVS: ftp: loaded support on port[0] = 21
+[    2.528335] IPVS: [sip] pe registered.
+[    2.528913] ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully
+[    2.529668] Initializing XFRM netlink socket
+[    2.530243] NET: Registered protocol family 10
+[    2.530990] Segment Routing with IPv6
+[    2.531446] NET: Registered protocol family 17
+[    2.531980] 9pnet: Installing 9P2000 support
+[    2.532904] NET: Registered protocol family 40
+[    2.533452] IPI shorthand broadcast: enabled
+[    2.533957] sched_clock: Marking stable (2450694990, 83251786)->(2555552194, -21605418)
+[    2.535774] Freeing unused decrypted memory: 2036K
+[    2.536717] Freeing unused kernel image (initmem) memory: 892K
+[    2.537482] Write protecting the kernel read-only data: 14336k
+[    2.538869] Freeing unused kernel image (text/rodata gap) memory: 2044K
+[    2.539890] Freeing unused kernel image (rodata/data gap) memory: 592K
+[    2.540714] Run /init as init process
+[    2.541191]   with arguments:
+[    2.541582]     /init
+[    2.541885]   with environment:
+[    2.542325]     HOME=/
+[    2.542640]     TERM=linux
+```
+
+Expected output as previous versions 
+Complete output from QEMU 6.0.0 with SEV :  
+```
+[    0.000000] Linux version 5.10.25 (gitlab-runner@runner-buildah0) (gcc (Debian 11.2.0-12) 11.2.0, GNU ld (GNU Binutils for Debian) 2.37) #1 SMP Tue Dec 7 11:43:22 CET 2021
+[    0.000000] Command line: tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k console=hvc0 console=hvc1 console=ttyS0 cryptomgr.notests net.ifnames=0 pci=lastbus=0 debug panic=1 nr_cpus=32 scsi_mod.scan=none agent.log=debug
+[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
+[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
+[    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
+[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
+[    0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
+[    0.000000] BIOS-provided physical RAM map:
+[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
+[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000007fffff] usable
+[    0.000000] BIOS-e820: [mem 0x0000000000800000-0x0000000000807fff] ACPI NVS
+[    0.000000] BIOS-e820: [mem 0x0000000000808000-0x000000000080ffff] usable
+[    0.000000] BIOS-e820: [mem 0x0000000000810000-0x00000000008fffff] ACPI NVS
+[    0.000000] BIOS-e820: [mem 0x0000000000900000-0x000000007f6eefff] usable
+[    0.000000] BIOS-e820: [mem 0x000000007f6ef000-0x000000007f96efff] reserved
+[    0.000000] BIOS-e820: [mem 0x000000007f96f000-0x000000007f97efff] ACPI data
+[    0.000000] BIOS-e820: [mem 0x000000007f97f000-0x000000007f9fefff] ACPI NVS
+[    0.000000] BIOS-e820: [mem 0x000000007f9ff000-0x000000007fe5ffff] usable
+[    0.000000] BIOS-e820: [mem 0x000000007fe60000-0x000000007fe7ffff] reserved
+[    0.000000] BIOS-e820: [mem 0x000000007fe80000-0x000000007fffffff] ACPI NVS
+[    0.000000] BIOS-e820: [mem 0x00000000b0000000-0x00000000bfffffff] reserved
+[    0.000000] NX (Execute Disable) protection: active
+[    0.000000] efi: EFI v2.70 by EDK II
+[    0.000000] efi: SMBIOS=0x7f7ab000 ACPI=0x7f97e000 ACPI 2.0=0x7f97e014 MEMATTR=0x7e9d8118
+[    0.000000] SMBIOS 2.8 present.
+[    0.000000] DMI: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015
+[    0.000000] Hypervisor detected: KVM
+[    0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00
+[    0.000000] kvm-clock: cpu 0, msr 14201001, primary cpu clock
+[    0.000001] kvm-clock: using sched offset of 3987202924 cycles
+[    0.000004] clocksource: kvm-clock: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns
+[    0.000006] tsc: Detected 2994.372 MHz processor
+[    0.000158] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
+[    0.000161] e820: remove [mem 0x000a0000-0x000fffff] usable
+[    0.000168] last_pfn = 0x7fe60 max_arch_pfn = 0x400000000
+[    0.000215] MTRR default type: write-back
+[    0.000216] MTRR fixed ranges enabled:
+[    0.000218]   00000-9FFFF write-back
+[    0.000220]   A0000-FFFFF uncachable
+[    0.000220] MTRR variable ranges enabled:
+[    0.000222]   0 base 0000C0000000 mask FFFFC0000000 uncachable
+[    0.000224]   1 base 0000B0000000 mask FFFFF0000000 uncachable
+[    0.000226]   2 base 001000000000 mask FFF800000000 uncachable
+[    0.000227]   3 disabled
+[    0.000227]   4 disabled
+[    0.000228]   5 disabled
+[    0.000229]   6 disabled
+[    0.000230]   7 disabled
+[    0.000274] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT
+[    0.008664] Using GB pages for direct mapping
+[    0.009370] Secure boot could not be determined
+[    0.009372] RAMDISK: [mem 0x6f1ee000-0x757f5fff]
+[    0.009399] ACPI: Early table checksum verification disabled
+[    0.009410] ACPI: RSDP 0x000000007F97E014 000024 (v02 BOCHS )
+[    0.009415] ACPI: XSDT 0x000000007F97D0E8 000054 (v01 BOCHS  BXPC     00000001      01000013)
+[    0.009423] ACPI: FACP 0x000000007F978000 0000F4 (v03 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.009430] ACPI: DSDT 0x000000007F979000 003278 (v01 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.009435] ACPI: FACS 0x000000007F9DD000 000040
+[    0.009439] ACPI: APIC 0x000000007F977000 000170 (v01 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.009443] ACPI: HPET 0x000000007F976000 000038 (v01 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.009448] ACPI: SRAT 0x000000007F975000 0002D0 (v01 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.009452] ACPI: MCFG 0x000000007F974000 00003C (v01 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.009456] ACPI: WAET 0x000000007F973000 000028 (v01 BOCHS  BXPC     00000001 BXPC 00000001)
+[    0.009466] ACPI: Local APIC address 0xfee00000
+[    0.009507] Zone ranges:
+[    0.009508]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
+[    0.009511]   DMA32    [mem 0x0000000001000000-0x000000007fe5ffff]
+[    0.009513]   Normal   empty
+[    0.009514]   Device   empty
+[    0.009516] Movable zone start for each node
+[    0.009517] Early memory node ranges
+[    0.009518]   node   0: [mem 0x0000000000001000-0x000000000009ffff]
+[    0.009520]   node   0: [mem 0x0000000000100000-0x00000000007fffff]
+[    0.009521]   node   0: [mem 0x0000000000808000-0x000000000080ffff]
+[    0.009522]   node   0: [mem 0x0000000000900000-0x000000007f6eefff]
+[    0.009523]   node   0: [mem 0x000000007f9ff000-0x000000007fe5ffff]
+[    0.009525] Initmem setup node 0 [mem 0x0000000000001000-0x000000007fe5ffff]
+[    0.009528] On node 0 totalpages: 522743
+[    0.009529]   DMA zone: 59 pages used for memmap
+[    0.009531]   DMA zone: 1814 pages reserved
+[    0.009532]   DMA zone: 3751 pages, LIFO batch:0
+[    0.009843]   DMA zone: 29017 pages in unavailable ranges
+[    0.009845]   DMA32 zone: 8122 pages used for memmap
+[    0.009846]   DMA32 zone: 518992 pages, LIFO batch:63
+[    0.014033]   DMA32 zone: 1200 pages in unavailable ranges
+[    0.014785] ACPI: PM-Timer IO Port: 0x608
+[    0.014788] ACPI: Local APIC address 0xfee00000
+[    0.014803] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
+[    0.014994] IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
+[    0.014998] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
+[    0.015001] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
+[    0.015003] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
+[    0.015005] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
+[    0.015006] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
+[    0.015007] ACPI: IRQ0 used by override.
+[    0.015009] ACPI: IRQ5 used by override.
+[    0.015010] ACPI: IRQ9 used by override.
+[    0.015011] ACPI: IRQ10 used by override.
+[    0.015011] ACPI: IRQ11 used by override.
+[    0.015014] Using ACPI (MADT) for SMP configuration information
+[    0.015017] ACPI: HPET id: 0x8086a201 base: 0xfed00000
+[    0.015021] TSC deadline timer available
+[    0.015027] smpboot: Allowing 32 CPUs, 31 hotplug CPUs
+[    0.015039] kvm-guest: KVM setup pv remote TLB flush
+[    0.015048] kvm-guest: setup PV sched yield
+[    0.015065] [mem 0xc0000000-0xffffffff] available for PCI devices
+[    0.015066] Booting paravirtualized kernel on KVM
+[    0.015070] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
+[    0.020345] setup_percpu: NR_CPUS:240 nr_cpumask_bits:240 nr_cpu_ids:32 nr_node_ids:1
+[    0.021575] percpu: Embedded 42 pages/cpu s143360 r0 d28672 u262144
+[    0.021585] pcpu-alloc: s143360 r0 d28672 u262144 alloc=1*2097152
+[    0.021587] pcpu-alloc: [0] 00 01 02 03 04 05 06 07 [0] 08 09 10 11 12 13 14 15
+[    0.021596] pcpu-alloc: [0] 16 17 18 19 20 21 22 23 [0] 24 25 26 27 28 29 30 31
+[    0.027137] kvm-guest: KVM setup async PF for cpu 0
+[    0.027144] kvm-guest: stealtime: cpu 0, msr 7d622080
+[    0.027159] Built 1 zonelists, mobility grouping on.  Total pages: 512748
+[    0.027161] Kernel command line: tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k console=hvc0 console=hvc1 console=ttyS0 cryptomgr.notests net.ifnames=0 pci=lastbus=0 debug panic=1 nr_cpus=32 scsi_mod.scan=none agent.log=debug
+[    0.027288] printk: log_buf_len individual max cpu contribution: 4096 bytes
+[    0.027290] printk: log_buf_len total cpu_extra contributions: 126976 bytes
+[    0.027291] printk: log_buf_len min size: 131072 bytes
+[    0.027523] printk: log_buf_len: 262144 bytes
+[    0.027524] printk: early log buf free: 123296(94%)
+[    0.027737] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
+[    0.027850] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
+[    0.027991] mem auto-init: stack:off, heap alloc:off, heap free:off
+[    0.040909] Memory: 1711324K/2090972K available (10242K kernel code, 956K rwdata, 1456K rodata, 892K init, 3564K bss, 379392K reserved, 0K cma-reserved)
+[    0.041029] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=32, Nodes=1
+[    0.041170] rcu: Hierarchical RCU implementation.
+[    0.041171] rcu: 	RCU restricting CPUs from NR_CPUS=240 to nr_cpu_ids=32.
+[    0.041173] 	All grace periods are expedited (rcu_expedited).
+[    0.041174] 	Tracing variant of Tasks RCU enabled.
+[    0.041176] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
+[    0.041177] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=32
+[    0.041233] NR_IRQS: 15616, nr_irqs: 680, preallocated irqs: 16
+[    0.041739] rcu: 	Offload RCU callbacks from CPUs: (none).
+[    0.041913] random: get_random_bytes called from start_kernel+0x2fc/0x4ae with crng_init=0
+[    0.041995] Console: colour dummy device 80x25
+[    0.140890] printk: console [ttyS0] enabled
+[    0.154171] AMD Memory Encryption Features active: SEV
+[    0.154858] ACPI: Core revision 20200925
+[    0.155536] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604467 ns
+[    0.156743] APIC: Switch to symmetric I/O mode setup
+[    0.158619] x2apic enabled
+[    0.160959] Switched APIC routing to physical x2apic.
+[    0.161554] kvm-guest: setup PV IPIs
+[    0.168397] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
+[    0.169300] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x2b29812ce43, max_idle_ns: 440795323173 ns
+[    0.170521] Calibrating delay loop (skipped) preset value.. 5988.74 BogoMIPS (lpj=11977488)
+[    0.171487] pid_max: default: 32768 minimum: 301
+[    0.202181] LSM: Security Framework initializing
+[    0.202548] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
+[    0.203685] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
+[    0.205011] x86/cpu: User Mode Instruction Prevention (UMIP) activated
+[    0.205802] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
+[    0.206525] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
+[    0.207435] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
+[    0.208419] Spectre V2 : Mitigation: Full AMD retpoline
+[    0.209026] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
+[    0.209975] Spectre V2 : Enabling Restricted Speculation for firmware calls
+[    0.210523] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
+[    0.211737] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp
+[    0.213043] Freeing SMP alternatives memory: 28K
+[    0.213721] smpboot: CPU0: AMD EPYC 7302P 16-Core Processor (family: 0x17, model: 0x31, stepping: 0x0)
+[    0.214519] Performance Events: Fam17h+ core perfctr, AMD PMU driver.
+[    0.214519] ... version:                0
+[    0.214519] ... bit width:              48
+[    0.214519] ... generic registers:      6
+[    0.214519] ... value mask:             0000ffffffffffff
+[    0.214525] ... max period:             00007fffffffffff
+[    0.215142] ... fixed-purpose events:   0
+[    0.215616] ... event mask:             000000000000003f
+[    0.216346] rcu: Hierarchical SRCU implementation.
+[    0.217174] smp: Bringing up secondary CPUs ...
+[    0.217714] smp: Brought up 1 node, 1 CPU
+[    0.218184] smpboot: Max logical packages: 32
+[    0.218527] smpboot: Total of 1 processors activated (5988.74 BogoMIPS)
+[    0.219686] devtmpfs: initialized
+[    0.220119] x86/mm: Memory block size: 128MB
+[    0.220864] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
+[    0.221995] futex hash table entries: 8192 (order: 7, 524288 bytes, linear)
+[    0.222863] NET: Registered protocol family 16
+[    0.223660] DMA: preallocated 256 KiB GFP_KERNEL pool for atomic allocations
+[    0.224813] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
+[    0.225857] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
+[    0.226565] thermal_sys: Registered thermal governor 'step_wise'
+[    0.226569] cpuidle: using governor menu
+[    0.228447] ACPI: bus type PCI registered
+[    0.228925] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
+[    0.229775] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xb0000000-0xbfffffff] (base 0xb0000000)
+[    0.230527] PCI: MMCONFIG at [mem 0xb0000000-0xbfffffff] reserved in E820
+[    0.231331] PCI: Using configuration type 1 for base access
+[    0.232839] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
+[    0.233641] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
+[    0.234545] ACPI: Added _OSI(Module Device)
+[    0.235040] ACPI: Added _OSI(Processor Device)
+[    0.235568] ACPI: Added _OSI(3.0 _SCP Extensions)
+[    0.236115] ACPI: Added _OSI(Processor Aggregator Device)
+[    0.236745] ACPI: Added _OSI(Linux-Dell-Video)
+[    0.237264] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
+[    0.237886] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
+[    0.240277] ACPI: 1 ACPI AML tables successfully acquired and loaded
+[    0.242125] ACPI: Interpreter enabled
+[    0.242530] ACPI: (supports S0 S5)
+[    0.242933] ACPI: Using IOAPIC for interrupt routing
+[    0.243537] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
+[    0.244744] ACPI: Enabled 2 GPEs in block 00 to 3F
+[    0.250149] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
+[    0.250531] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3]
+[    0.251661] acpi PNP0A08:00: _OSC: platform does not support [LTR]
+[    0.252454] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug SHPCHotplug PME PCIeCapability]
+[    0.253626] PCI host bridge to bus 0000:00
+[    0.254115] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
+[    0.254526] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
+[    0.255309] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
+[    0.256179] pci_bus 0000:00: root bus resource [mem 0x80000000-0xafffffff window]
+[    0.257045] pci_bus 0000:00: root bus resource [mem 0xc0000000-0xfebfffff window]
+[    0.257910] pci_bus 0000:00: root bus resource [mem 0x1000000000-0x17ffffffff window]
+[    0.258525] pci_bus 0000:00: root bus resource [bus 00-ff]
+[    0.259223] pci 0000:00:00.0: [8086:29c0] type 00 class 0x060000
+[    0.260509] pci 0000:00:01.0: [1af4:1043] type 00 class 0x078000
+[    0.263098] pci 0000:00:01.0: reg 0x14: [mem 0xc0003000-0xc0003fff]
+[    0.267149] pci 0000:00:01.0: reg 0x20: [mem 0x1000000000-0x1000003fff 64bit pref]
+[    0.269843] pci 0000:00:02.0: [1b36:0001] type 01 class 0x060400
+[    0.275338] pci 0000:00:03.0: [1af4:1048] type 00 class 0x010000
+[    0.277811] pci 0000:00:03.0: reg 0x14: [mem 0xc0002000-0xc0002fff]
+[    0.281320] pci 0000:00:03.0: reg 0x20: [mem 0x1000004000-0x1000007fff 64bit pref]
+[    0.284951] pci 0000:00:04.0: [1af4:1044] type 00 class 0x00ff00
+[    0.287749] pci 0000:00:04.0: reg 0x20: [mem 0x1000008000-0x100000bfff 64bit pref]
+[    0.289851] pci 0000:00:05.0: [1af4:1049] type 00 class 0x000200
+[    0.292301] pci 0000:00:05.0: reg 0x14: [mem 0xc0001000-0xc0001fff]
+[    0.295709] pci 0000:00:05.0: reg 0x20: [mem 0x100000c000-0x100000ffff 64bit pref]
+[    0.298275] pci 0000:00:1f.0: [8086:2918] type 00 class 0x060100
+[    0.299038] pci 0000:00:1f.0: quirk: [io  0x0600-0x067f] claimed by ICH6 ACPI/GPIO/TCO
+[    0.300211] pci 0000:00:1f.2: [8086:2922] type 00 class 0x010601
+[    0.306084] pci 0000:00:1f.2: reg 0x20: [io  0x6040-0x605f]
+[    0.307285] pci 0000:00:1f.2: reg 0x24: [mem 0xc0000000-0xc0000fff]
+[    0.309200] pci 0000:00:1f.3: [8086:2930] type 00 class 0x0c0500
+[    0.312072] pci 0000:00:1f.3: reg 0x20: [io  0x6000-0x603f]
+[    0.314207] pci_bus 0000:01: extended config space not accessible
+[    0.314817] pci 0000:00:02.0: PCI bridge to [bus 01]
+[    0.317358] pci_bus 0000:00: on NUMA node 0
+[    0.318107] ACPI: PCI Interrupt Link [LNKA] (IRQs 5 *10 11)
+[    0.318611] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11)
+[    0.319355] ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11)
+[    0.320094] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 10 *11)
+[    0.320826] ACPI: PCI Interrupt Link [LNKE] (IRQs 5 *10 11)
+[    0.321565] ACPI: PCI Interrupt Link [LNKF] (IRQs 5 *10 11)
+[    0.322302] ACPI: PCI Interrupt Link [LNKG] (IRQs 5 10 *11)
+[    0.322608] ACPI: PCI Interrupt Link [LNKH] (IRQs 5 10 *11)
+[    0.323292] ACPI: PCI Interrupt Link [GSIA] (IRQs *16)
+[    0.323908] ACPI: PCI Interrupt Link [GSIB] (IRQs *17)
+[    0.324522] ACPI: PCI Interrupt Link [GSIC] (IRQs *18)
+[    0.325132] ACPI: PCI Interrupt Link [GSID] (IRQs *19)
+[    0.325746] ACPI: PCI Interrupt Link [GSIE] (IRQs *20)
+[    0.326356] ACPI: PCI Interrupt Link [GSIF] (IRQs *21)
+[    0.326533] ACPI: PCI Interrupt Link [GSIG] (IRQs *22)
+[    0.327148] ACPI: PCI Interrupt Link [GSIH] (IRQs *23)
+[    0.329169] iommu: Default domain type: Translated
+[    0.329808] vgaarb: loaded
+[    0.330245] SCSI subsystem initialized
+[    0.330537] pps_core: LinuxPPS API ver. 1 registered
+[    0.331124] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
+[    0.332182] PTP clock support registered
+[    0.332667] Registered efivars operations
+[    0.333281] PCI: Using ACPI for IRQ routing
+[    0.333783] PCI: pci_cache_line_size set to 64 bytes
+[    0.334528] e820: reserve RAM buffer [mem 0x00810000-0x008fffff]
+[    0.335230] e820: reserve RAM buffer [mem 0x7f6ef000-0x7fffffff]
+[    0.335932] e820: reserve RAM buffer [mem 0x7fe60000-0x7fffffff]
+[    0.336675] clocksource: Switched to clocksource kvm-clock
+[    0.337485] pnp: PnP ACPI init
+[    0.337896] pnp 00:00: Plug and Play ACPI device, IDs PNP0303 (active)
+[    0.338519] pnp 00:01: Plug and Play ACPI device, IDs PNP0f13 (active)
+[    0.338519] pnp 00:02: Plug and Play ACPI device, IDs PNP0501 (active)
+[    0.338519] pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
+[    0.338920] system 00:04: [mem 0xb0000000-0xbfffffff window] has been reserved
+[    0.339770] system 00:04: Plug and Play ACPI device, IDs PNP0c01 (active)
+[    0.341103] pnp: PnP ACPI: found 5 devices
+[    0.346943] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
+[    0.348014] NET: Registered protocol family 2
+[    0.348722] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear)
+[    0.349720] TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear)
+[    0.350698] TCP bind hash table entries: 16384 (order: 6, 262144 bytes, linear)
+[    0.351620] TCP: Hash tables configured (established 16384 bind 16384)
+[    0.352423] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear)
+[    0.353213] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear)
+[    0.354115] NET: Registered protocol family 1
+[    0.354654] pci 0000:00:02.0: PCI bridge to [bus 01]
+[    0.357279] pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
+[    0.358008] pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
+[    0.358744] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
+[    0.359541] pci_bus 0000:00: resource 7 [mem 0x80000000-0xafffffff window]
+[    0.360345] pci_bus 0000:00: resource 8 [mem 0xc0000000-0xfebfffff window]
+[    0.361145] pci_bus 0000:00: resource 9 [mem 0x1000000000-0x17ffffffff window]
+[    0.362089] PCI: CLS 0 bytes, default 64
+[    0.362638] Trying to unpack rootfs image as initramfs...
+[    2.307254] Freeing initrd memory: 104480K
+[    2.307791] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
+[    2.308521] software IO TLB: mapped [mem 0x0000000069000000-0x000000006d000000] (64MB)
+[    2.309454] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x2b29812ce43, max_idle_ns: 440795323173 ns
+[    2.311063] workingset: timestamp_bits=46 max_order=19 bucket_order=0
+[    2.313608] fuse: init (API version 7.32)
+[    2.314181] SGI XFS with security attributes, no debug enabled
+[    2.315435] 9p: Installing v9fs 9p2000 file system support
+[    2.316233] NET: Registered protocol family 38
+[    2.316827] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
+[    2.317926] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
+[    2.318847] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
+[    2.319752] ACPI: Power Button [PWRF]
+[    2.320661] PCI Interrupt Link [GSIF] enabled at IRQ 21
+[    2.322549] PCI Interrupt Link [GSIH] enabled at IRQ 23
+[    2.324157] PCI Interrupt Link [GSIE] enabled at IRQ 20
+[    2.326555] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
+[    2.327388] 00:02: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
+[    2.341959] software IO TLB: Memory encryption is active and system is using DMA bounce buffers
+[    2.344242] printk: console [hvc0] enabled
+[    2.346335] brd: module loaded
+[    2.347023] random: fast init done
+[    2.347786] random: crng init done
+[    2.349418] loop: module loaded
+[    2.351182] scsi host0: Virtio SCSI HBA
+[    2.352317] VFIO - User Level meta-driver version: 0.3
+[    2.353380] xt_time: kernel timezone is -0000
+[    2.354028] IPVS: Registered protocols (TCP, UDP, SCTP, AH, ESP)
+[    2.354873] IPVS: Connection hash table configured (size=4096, memory=64Kbytes)
+[    2.355859] IPVS: ipvs loaded.
+[    2.356319] IPVS: [rr] scheduler registered.
+[    2.356933] IPVS: [wrr] scheduler registered.
+[    2.357542] IPVS: [lc] scheduler registered.
+[    2.358152] IPVS: [wlc] scheduler registered.
+[    2.358787] IPVS: [fo] scheduler registered.
+[    2.359343] IPVS: [ovf] scheduler registered.
+[    2.359968] IPVS: [lblc] scheduler registered.
+[    2.360595] IPVS: [lblcr] scheduler registered.
+[    2.361236] IPVS: [dh] scheduler registered.
+[    2.361846] IPVS: [sh] scheduler registered.
+[    2.362468] IPVS: [sed] scheduler registered.
+[    2.363060] IPVS: [nq] scheduler registered.
+[    2.363623] IPVS: ftp: loaded support on port[0] = 21
+[    2.364272] IPVS: [sip] pe registered.
+[    2.364967] ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully
+[    2.365818] Initializing XFRM netlink socket
+[    2.366474] NET: Registered protocol family 10
+[    2.367351] Segment Routing with IPv6
+[    2.367888] NET: Registered protocol family 17
+[    2.368518] 9pnet: Installing 9P2000 support
+[    2.369955] NET: Registered protocol family 40
+[    2.370608] IPI shorthand broadcast: enabled
+[    2.371198] sched_clock: Marking stable (2249797515, 120751625)->(2381329269, -10780129)
+[    2.373554] Freeing unused decrypted memory: 2036K
+[    2.374622] Freeing unused kernel image (initmem) memory: 892K
+[    2.375403] Write protecting the kernel read-only data: 14336k
+[    2.377004] Freeing unused kernel image (text/rodata gap) memory: 2044K
+[    2.378219] Freeing unused kernel image (rodata/data gap) memory: 592K
+[    2.379114] Run /init as init process
+[    2.379599]   with arguments:
+[    2.380009]     /init
+[    2.380321]   with environment:
+[    2.380749]     HOME=/
+[    2.381071]     TERM=linux
+```
diff --git a/results/classifier/gemma3:12b/kernel/959992 b/results/classifier/gemma3:12b/kernel/959992
new file mode 100644
index 00000000..32756084
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/959992
@@ -0,0 +1,44 @@
+
+segfault in apic_report_irq_delivered when booting tinycore_3.3.iso
+
+it git head (33cf629) sometimes it segfaults in apic_report_irq_delivered() and backtrace is looping in apic_update_irq(#3-#4)
+
+Log:
+C:\msys\home\User\qemu\i386-softmmu>gdb --args qemu-system-i386.exe -L ..\pc-bios -cdrom tinycore_3.3.iso
+GNU gdb (GDB) 7.3
+Copyright (C) 2011 Free Software Foundation, Inc.
+License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and redistribute it.
+There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
+and "show warranty" for details.
+This GDB was configured as "mingw32".
+For bug reporting instructions, please see:
+<http://www.gnu.org/software/gdb/bugs/>...
+Reading symbols from C:\msys\home\User\qemu\i386-softmmu/qemu-system-i386.exe...
+done.
+(gdb) r
+Starting program: C:\msys\home\User\qemu\i386-softmmu/qemu-system-i386.exe -L ..\\pc-bios -cdrom tinycore_3.3.iso
+[New Thread 9012.0x2348]
+[New Thread 9012.0x2860]
+[New Thread 9012.0x2b64]
+
+Program received signal SIGSEGV, Segmentation fault.
+[Switching to Thread 9012.0x2b64]
+0x0053cde8 in apic_report_irq_delivered (delivered=0)
+    at C:/msys/home/User/qemu/hw/apic_common.c:110
+110     {
+(gdb) bt
+#0  0x0053cde8 in apic_report_irq_delivered (delivered=0)
+    at C:/msys/home/User/qemu/hw/apic_common.c:110
+#1  0x0053b9eb in apic_set_irq (s=0x1d7aff8, vector_num=<optimized out>,
+    trigger_mode=0) at C:/msys/home/User/qemu/hw/apic.c:390
+#2  0x0053b990 in apic_update_irq (s=0x1d7aff8)
+    at C:/msys/home/User/qemu/hw/apic.c:376
+#3  apic_update_irq (s=0x1d7aff8) at C:/msys/home/User/qemu/hw/apic.c:367
+#4  0x0053b990 in apic_update_irq (s=0x1d7aff8)
+    at C:/msys/home/User/qemu/hw/apic.c:376
+#5  apic_update_irq (s=0x1d7aff8) at C:/msys/home/User/qemu/hw/apic.c:367
+#6  0x0053b990 in apic_update_irq (s=0x1d7aff8)
+    at C:/msys/home/User/qemu/hw/apic.c:376
+#7  apic_update_irq (s=0x1d7aff8) at C:/msys/home/User/qemu/hw/apic.c:367
+...
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/964 b/results/classifier/gemma3:12b/kernel/964
new file mode 100644
index 00000000..f8a03161
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/964
@@ -0,0 +1,41 @@
+
+arm64 defconfig kernel (4.14.275) no longer boots after FEAT_LPA implementation in TCG
+Description of problem:
+I am not really sure if this is a bug or merely a scenario where this is not expected to work. After 7a928f43d8724bdf0777d7fc67a5ad973a0bf4bf, the attached `Image.gz` (`ARCH=arm64 defconfig`, based on the latest `linux-4.14.y`) just hangs with no output when using `-cpu max` (or `-cpu max,lpa2=off` due to 69b2265d5fe8e0f401d75e175e0a243a7d505e53). At 0af312b6edd231e1c8d0dec12494a80bc39ac761, `-cpu max` works just fine, as shown by the bisect log below.
+
+```
+$ git bisect log
+# bad: [99eb313ddbbcf73c1adcdadceba1423b691c6d05] ui/cocoa: Use the standard about panel
+# good: [44f28df24767cf9dca1ddc9b23157737c4cbb645] Update version for v6.2.0 release
+git bisect start '99eb313ddbbcf73c1adcdadceba1423b691c6d05' 'v6.2.0'
+# good: [2fc1b44dd0e7ea9ad5920352fd04179e4d6836d9] target/riscv: rvv-1.0: Allow Zve32f extension to be turned on
+git bisect good 2fc1b44dd0e7ea9ad5920352fd04179e4d6836d9
+# good: [e64e27d5cb103b7764f1a05b6eda7e7fedd517c5] 9pfs: Fix segfault in do_readdir_many caused by struct dirent overread
+git bisect good e64e27d5cb103b7764f1a05b6eda7e7fedd517c5
+# good: [747ffe28cad7129e1d326d943228fdcbe109530d] pnv/xive2: Add support XIVE2 P9-compat mode (or Gen1)
+git bisect good 747ffe28cad7129e1d326d943228fdcbe109530d
+# bad: [4377683df969e715e3cb2dbd258e44f9ff51f788] edid: Fix clock of Detailed Timing Descriptor
+git bisect bad 4377683df969e715e3cb2dbd258e44f9ff51f788
+# good: [755e8d7cb6ce2ba62d282ffbb367de391fe0cc3d] migration: Move static var in ram_block_from_stream() into global
+git bisect good 755e8d7cb6ce2ba62d282ffbb367de391fe0cc3d
+# bad: [6629bf78aac7e53f83fd0bcbdbe322e2302dfd1f] Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20220302' into staging
+git bisect bad 6629bf78aac7e53f83fd0bcbdbe322e2302dfd1f
+# good: [0af312b6edd231e1c8d0dec12494a80bc39ac761] target/arm: Implement FEAT_LVA
+git bisect good 0af312b6edd231e1c8d0dec12494a80bc39ac761
+# bad: [dc8bc9d6574aa563ed2fcc0ff495e77a2a2a8faa] target/arm: Report KVM's actual PSCI version to guest in dtb
+git bisect bad dc8bc9d6574aa563ed2fcc0ff495e77a2a2a8faa
+# bad: [d976de218c534735e307fc4a6c03e3ae764fd419] target/arm: Fix TLBIRange.base for 16k and 64k pages
+git bisect bad d976de218c534735e307fc4a6c03e3ae764fd419
+# bad: [13e481c9335582fc7eed12e24e8d4d7068b24ff8] target/arm: Extend arm_fi_to_lfsc to level -1
+git bisect bad 13e481c9335582fc7eed12e24e8d4d7068b24ff8
+# bad: [7a928f43d8724bdf0777d7fc67a5ad973a0bf4bf] target/arm: Implement FEAT_LPA
+git bisect bad 7a928f43d8724bdf0777d7fc67a5ad973a0bf4bf
+# first bad commit: [7a928f43d8724bdf0777d7fc67a5ad973a0bf4bf] target/arm: Implement FEAT_LPA
+```
+
+A `4.19.237` kernel boots right up with `-cpu max`/`-cpu max,lpa2=off`. Is this expected behavior given the age of the kernel or is there something else going on here? If this is expected, should we be using something like `-cpu cortex-a72` for these older kernels?
+Steps to reproduce:
+Run the above command with the attached `Image.gz` and `rootfs.cpio`.
+Additional information:
+[Image.gz](/uploads/7b25b70f210354663b8e391290d3f39c/Image.gz)
+[rootfs.cpio](/uploads/4793be1a500bdf615e212d3379c4c175/rootfs.cpio)
diff --git a/results/classifier/gemma3:12b/kernel/965133 b/results/classifier/gemma3:12b/kernel/965133
new file mode 100644
index 00000000..45d3757f
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/965133
@@ -0,0 +1,38 @@
+
+Sparc64 crash on start
+
+qemu version 1.0.1 compiled on a Ubuntu live on a HP laptop win a x64 architecture.
+
+With more than 4G of memory sparc64 machine crash on start.
+
+command line: qemu-system-sparc64 -m 4G
+
+output:
+VNC server running on `127.0.0.1:5900'
+qemu: fatal: Trap 0x0064 while trap level (5) >= MAXTL (5), Error state
+pc: 00000000ffd04c80  npc: 00000000ffd04c84
+General Registers:
+%g0-3: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%g4-7: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
+
+Current Register Window:
+%o0-3: 00000000ffd00000 0000000000080000 0000000000080000 0000000000000000 
+%o4-7: 0000000000000000 0000000000000000 00000000fff754e1 00000000ffd144d4 
+%l0-3: 0000000100000000 00000000fff75c4d 0000000000000000 0000000000000000 
+%l4-7: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 
+%i0-3: 0000000000000000 0000000000000000 0000000100000000 0000000000000036 
+%i4-7: 00000000ffe87418 00000000ffe87648 00000000fff75591 00000000ffd0bf54 
+
+Floating Point Registers:
+%f00: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%f08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%f16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%f24: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%f32: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%f40: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%f48: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
+%f56: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
+pstate: 00000414 ccr: 99 (icc: N--C xcc: N--C) asi: 00 tl: 5 pil: 0
+cansave: 5 canrestore: 1 otherwin: 0 wstate: 0 cleanwin: 6 cwp: 3
+fsr: 0000000000000000 y: 0000000000000000 fprs: 0000000000000000
+Aborted (core dumped)
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/kernel/995 b/results/classifier/gemma3:12b/kernel/995
new file mode 100644
index 00000000..a09f8c12
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/995
@@ -0,0 +1,12 @@
+
+Segfault when saving VM snapshot via QEMU monitor on MIPS and MIPSEL
+Description of problem:
+When entering the QEMU monitor using Ctrl-A then C, and running the savevm QEMU command, the emulator hangs for a while and then exits with a segfault. This occurs on MIPS and MIPSEL system emulators using the same command line arguments. ARM32, aarch64 and x86_64 emulators don't seem to have this problem. I haven't tested it on any other architectures as I don't have kernel or drive images for them. `qemu-img` seems to work fine with the QCOW2 images used for this test, I was able to create and load offline snapshots from them. The images were created from raw EXT2 filesystem images produced by Buildroot, using `qemu-img convert`.
+Steps to reproduce:
+1. Start the QEMU system emulator for MIPS/MIPSEL with the given command line.
+2. Enter the QEMU monitor with Ctrl-A, C.
+3. Run `savevm <vm name>`.
+Additional information:
+I tried logging what QEMU was doing with the `-D ./log.txt` command line option, but the produced log file was empty.
+
+If you need me to send you the kernel image files and QCOW2 images used, I would be happy to do so.
author	Christian Krinitsin <mail@krinitsin.com>	2025-07-03 07:27:52 +0000
committer	Christian Krinitsin <mail@krinitsin.com>	2025-07-03 07:27:52 +0000
commit	d0c85e36e4de67af628d54e9ab577cc3fad7796a (patch)
tree	f8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/gemma3:12b/kernel
parent	7f4364274750eb8cb39a3e7493132fca1c01232e (diff)
download	emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip