[Qemu-devel] [Bug 627982] [NEW] linux 2.6.35 hangs with -no-acpi

[Qemu-devel] [Bug 627982] [NEW] linux 2.6.35 hangs with -no-acpi

[Samuel thibault]

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"

** Affects: qemu
     Importance: Undecided
         Status: New

-- 
linux 2.6.35 hangs with -no-acpi
https://bugs.launchpad.net/bugs/627982
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: New

Bug description:
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"

Re: [Qemu-devel] [Bug 627982] [NEW] linux 2.6.35 hangs with -no-acpi

[Avi Kivity]

  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.

Re: [Qemu-devel] [Bug 627982] [NEW] linux 2.6.35 hangs with -no-acpi

[Samuel Thibault]

Avi Kivity, le Wed 01 Sep 2010 15:17:50 +0300, a écrit :
> On 09/01/2010 01:54 PM, Samuel thibault wrote:
> >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?

Debian 2.6.32 does work.

> A qemu regression?

It works when using qemu-system-x86_64, but hangs when using qemu (kvm
disabled in both cases).

> What do 'info registers' and 'x/20i $eip' show?

         EIP=c102e576 EFL=00000296 [--S-AP-] CPL=0 II=0 A20=1 SMM=0 HLT=0                
         ES =007b 00000000 ffffffff 00cff300 DPL=3 DS   [-WA]                            
         CS =0060 00000000 ffffffff 00cf9a00 DPL=0 CS32 [-R-]                            
         SS =0068 00000000 ffffffff 00cf9300 DPL=0 DS   [-WA]                            
         DS =007b 00000000 ffffffff 00cff300 DPL=3 DS   [-WA]                            
         FS =00d8 00000000 ffffffff 00cf9300 DPL=0 DS   [-WA]                            
         GS =00e0 c1481fc0 00000018 c1409148 DPL=0 DS   [--A]                            
         LDT=0000 00000000 00000000 00008200 DPL=0 LDT                                   
         TR =0020 00001000 00000067 00008900 DPL=0 TSS32-avl                             
         GDT=     c147a000 000000ff                                                      
         IDT=     c13c5000 000007ff                                                      
         CR0=80050033 CR2=ffffb030 CR3=01487000 CR4=00000090                             
         DR0=00000000 DR1=00000000 DR2=00000000 DR3=00000000                             
         DR6=ffff0ff0 DR7=00000400                                                       
         FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00001f80                                  
         FPR0=0000000000000000 0000 FPR1=0000000000000000 0000                           
         FPR2=0000000000000000 0000 FPR3=0000000000000000 0000                           
         FPR4=0000000000000000 0000 FPR5=0000000000000000 0000                           
         FPR6=0000000000000000 0000 FPR7=0000000000000000 0000                           
         XMM00=00000000000000000000000000000000 XMM01=00000000000000000000000000000000   
         XMM02=00000000000000000000000000000000 XMM03=00000000000000000000000000000000   
         XMM04=00000000000000000000000000000000 XMM05=00000000000000000000000000000000   
         XMM06=00000000000000000000000000000000 XMM07=00000000000000000000000000000000

c102e576 is in panic_blink_one_second:

c102e51b t panic_blink_one_second
c102e57e t do_oops_enter_exit

i.e. the kernel just paniced.
Digging in the RAM tells that the panic msg is "Attempted to kill the
idle task!", i.e. somehow do_exit() got called in what seemed like the
idle task (!tsk->pid). Digging on the stack gives me

0xc13f0ea0 (init_task)
0xc1270241 (panic)
0xc1031612 (do_exit)
0xc102f27e (kmsg_dump)
0xc1272c8e (oops_end)
0xc101cc90 (no_context)
0xc12742f0 (do_page_fault)
0xc101cd9e (bad_area_nosemaphore)
0xc1272337 (error_code)
... (probable trap limit)
0xc10157e1 (native_apic_mem_read)
0xc1014be7 (get_physical_broadcast)
0xc142f029 (io_apic_get_unique_id)
0xc142f18b (io_apic_unique_id)
0xc142f233 (mp_register_ioapic)
0xc142cc64 (default_get_smp_config)
0xc1424f5c (setup_arch)

It's really easy to reproduce, just try with these kernels:

http://dept-info.labri.fr/~thibault/tmp/qemu/vmlinuz-2.6.35-trunk-686
http://dept-info.labri.fr/~thibault/tmp/qemu/System.map-2.6.35-trunk-686

and as I said on the list, I won't take the time to dig a lot.

Samuel

[Qemu-devel] [Bug 627982] Re: linux 2.6.35 hangs with -no-acpi

[Thomas Huth]

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).

** Changed in: qemu
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/627982

Title:
  linux 2.6.35 hangs with -no-acpi

Status in QEMU:
  Won't Fix

Bug description:
  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"

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/627982/+subscriptions