1 files changed, 61 insertions, 0 deletions
diff --git a/results/classifier/118/kernel/627982 b/results/classifier/118/kernel/627982
new file mode 100644
index 00000000..9eeb0ddc
--- /dev/null
+++ b/results/classifier/118/kernel/627982
@@ -0,0 +1,61 @@
+kernel: 0.935
+boot: 0.935
+mistranslation: 0.866
+register: 0.810
+PID: 0.732
+semantic: 0.724
+device: 0.688
+user-level: 0.599
+graphic: 0.579
+performance: 0.543
+permissions: 0.513
+virtual: 0.491
+x86: 0.487
+network: 0.463
+VMM: 0.443
+ppc: 0.420
+socket: 0.410
+vnc: 0.408
+architecture: 0.387
+i386: 0.379
+risc-v: 0.377
+files: 0.376
+TCG: 0.368
+peripherals: 0.350
+arm: 0.337
+assembly: 0.311
+debug: 0.303
+KVM: 0.279
+hypervisor: 0.239
+
+linux 2.6.35 hangs with -no-acpi
+
+Linux 2.6.35 hangs at boot when giving -no-acpi to qemu, for instance the Debian kernel:
+
+qemu -no-acpi -kernel /boot/vmlinuz-2.6.35-trunk-686 
+
+There is no output except just "Booting the kernel"
+
+  On 09/01/2010 01:54 PM, Samuel thibault wrote:
+> Public bug reported:
+>
+> Linux 2.6.35 hangs at boot when giving -no-acpi to qemu, for instance
+> the Debian kernel:
+>
+> qemu -no-acpi -kernel /boot/vmlinuz-2.6.35-trunk-686
+>
+> There is no output except just "Booting the kernel"
+>
+
+Is this a kernel regression?  A qemu regression?  What do 'info 
+registers' and 'x/20i $eip' show?
+
+You know better than this.
+
+-- 
+I have a truly marvellous patch that fixes the bug which this
+signature is too narrow to contain.
+
+
+Since kernel 2.6.35 is pretty much outdated nowadays, I think we can close this bug now (Feel free to re-open it if necessary).
+