summary refs log tree commit diff stats
path: root/results/classifier/118/kernel/1069
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/118/kernel/1069')
-rw-r--r--results/classifier/118/kernel/106943
1 files changed, 0 insertions, 43 deletions
diff --git a/results/classifier/118/kernel/1069 b/results/classifier/118/kernel/1069
deleted file mode 100644
index b3a94847..00000000
--- a/results/classifier/118/kernel/1069
+++ /dev/null
@@ -1,43 +0,0 @@
-kernel: 0.968
-graphic: 0.959
-device: 0.932
-architecture: 0.838
-PID: 0.660
-semantic: 0.644
-debug: 0.599
-x86: 0.570
-register: 0.535
-boot: 0.502
-vnc: 0.440
-performance: 0.407
-ppc: 0.403
-permissions: 0.393
-i386: 0.361
-hypervisor: 0.345
-socket: 0.325
-user-level: 0.313
-risc-v: 0.307
-TCG: 0.284
-mistranslation: 0.270
-network: 0.263
-VMM: 0.229
-virtual: 0.226
-arm: 0.200
-files: 0.171
-peripherals: 0.133
-assembly: 0.052
-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 ?