1 files changed, 46 insertions, 0 deletions
diff --git a/results/classifier/108/boot/627982 b/results/classifier/108/boot/627982
new file mode 100644
index 000000000..e915d2af3
--- /dev/null
+++ b/results/classifier/108/boot/627982
@@ -0,0 +1,46 @@
+boot: 0.935
+PID: 0.732
+semantic: 0.724
+device: 0.688
+other: 0.670
+graphic: 0.579
+performance: 0.543
+permissions: 0.513
+network: 0.463
+socket: 0.410
+vnc: 0.408
+files: 0.376
+debug: 0.303
+KVM: 0.279
+
+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).
+