summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/118/kernel/2281
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/zero-shot/118/kernel/2281')
-rw-r--r--results/classifier/zero-shot/118/kernel/228137
1 files changed, 37 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/118/kernel/2281 b/results/classifier/zero-shot/118/kernel/2281
new file mode 100644
index 000000000..3013bfec0
--- /dev/null
+++ b/results/classifier/zero-shot/118/kernel/2281
@@ -0,0 +1,37 @@
+kernel: 0.949
+debug: 0.924
+graphic: 0.918
+device: 0.807
+semantic: 0.624
+architecture: 0.475
+register: 0.470
+network: 0.456
+files: 0.436
+arm: 0.429
+PID: 0.389
+socket: 0.389
+risc-v: 0.366
+boot: 0.341
+TCG: 0.339
+vnc: 0.284
+performance: 0.274
+ppc: 0.268
+VMM: 0.208
+permissions: 0.181
+virtual: 0.126
+mistranslation: 0.118
+user-level: 0.117
+i386: 0.080
+peripherals: 0.076
+assembly: 0.060
+x86: 0.055
+hypervisor: 0.024
+KVM: 0.006
+
+[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.
+
+#