summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/105/boot/627982
blob: 15dd58cf10b7202994c53931c999855dafb9c94c (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
boot: 0.935
mistranslation: 0.866
semantic: 0.724
device: 0.688
other: 0.670
instruction: 0.635
graphic: 0.579
network: 0.463
socket: 0.410
vnc: 0.408
assembly: 0.311
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).