Re: dom0 crash with unstable

[Jeremy Fitzhardinge <jeremy@goop.org>]

On 09/30/09 11:05, Bryan D. Payne wrote:
> I'm trying to install Xen-unstable on a new machine.  At first boot,
> I'm getting a dom0 crash.  The crash output is shown below.  The
> complete console log is attached.
>
> (XEN) Std. Loglevel: All
> (XEN) Guest Loglevel: All
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xe)
> (XEN) Freed 148kB init memory.
> mapping kernel into physical memory
> Xen: setup ISA identity maps
> (XEN) traps.c:466:d0 Unhandled invalid opcode fault/trap [#6] on VCPU 0 [ec=000]
> (XEN) domain_crash_sync called from entry.S
> (XEN) Domain 0 (vcpu#0) crashed on cpu#0:
> (XEN) ----[ Xen-3.5-unstable  x86_64  debug=y  Not tainted ]----
> (XEN) CPU:    0
> (XEN) RIP:    e033:[<ffffffff819067de>]
> (XEN) RFLAGS: 0000000000000212   EM: 1   CONTEXT: pv guest
> (XEN) rax: ffffffff865ce000   rbx: ffffffff81001000   rcx: 0000000000000006
> (XEN) rdx: 0000000000800000   rsi: 00000000deadbeef   rdi: 00000000deadbeef
> (XEN) rbp: ffffffff81807fa8   rsp: ffffffff81807f68   r8:  000000000000001d
> (XEN) r9:  ffffffff81807fd8   r10: 0000000006606000   r11: 00000000818ec000
> (XEN) r12: 0000000000000000   r13: 0000000000000000   r14: 0000000000000000
> (XEN) r15: 0000000000000000   cr0: 000000008005003b   cr4: 00000000000026f0
> (XEN) cr3: 0000000919001000   cr2: 0000000000000000
> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033
> (XEN) Guest stack trace from rsp=ffffffff81807f68:
> (XEN)    0000000000000006 00000000818ec000 ffffffff819067de 000000010000e030
> (XEN)    0000000000010012 ffffffff81807fa8 000000000000e02b ffffffff81906d64
> (XEN)    ffffffff81807ff8 ffffffff81906166 0000000000000000 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000001 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000
> (XEN) Domain 0 crashed: rebooting machine in 5 seconds.
>
> I pulled from Xen unstable yesterday (bd376919f03a tip), and built it
> simply using "make world".  The machine has four Intel E5540
> processors and 36GB of RAM.  In the BIOS, I have VT-d disabled, and
> VT-x enabled.  Any suggestions on what steps I should take for
> debugging this problem and getting dom0 to boot?
>   

It looks like something has hit a BUG_ON.  The first step is to try to
identify which one:

$ gdb vmlinux
(gdb) x/i 0xffffffff819067de
(gdb) x/i 0xffffffff81906d64
(gdb) x/i 0xffffffff81906166

should give a first clue.

Thanks,
    J