summaryrefslogtreecommitdiffstats
path: root/results/classifier/zero-shot/108/graphic/1069
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-03 19:39:53 +0200
committerChristian Krinitsin <mail@krinitsin.com>2025-07-03 19:39:53 +0200
commitdee4dcba78baf712cab403d47d9db319ab7f95d6 (patch)
tree418478faf06786701a56268672f73d6b0b4eb239 /results/classifier/zero-shot/108/graphic/1069
parent4d9e26c0333abd39bdbd039dcdb30ed429c475ba (diff)
downloademulator-bug-study-dee4dcba78baf712cab403d47d9db319ab7f95d6.tar.gz
emulator-bug-study-dee4dcba78baf712cab403d47d9db319ab7f95d6.zip
restructure results
Diffstat (limited to 'results/classifier/zero-shot/108/graphic/1069')
-rw-r--r--results/classifier/zero-shot/108/graphic/106928
1 files changed, 28 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/graphic/1069 b/results/classifier/zero-shot/108/graphic/1069
new file mode 100644
index 00000000..0180f972
--- /dev/null
+++ b/results/classifier/zero-shot/108/graphic/1069
@@ -0,0 +1,28 @@
+graphic: 0.959
+device: 0.932
+PID: 0.660
+semantic: 0.644
+debug: 0.599
+boot: 0.502
+other: 0.477
+vnc: 0.440
+performance: 0.407
+permissions: 0.393
+socket: 0.325
+network: 0.263
+files: 0.171
+KVM: 0.025
+
+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 ?