WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 		  
Home Products Support Community News
 
   
 

xen-devel

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

RE: [Xen-devel] Xeno-unstable crashing at boot

from [Ian Pratt] [Permanent Link][Original]
To: "Mike Wray" <mike.wray@xxxxxx>, "Anthony Liguori" <aliguori@xxxxxxxxxx>
Subject: RE: [Xen-devel] Xeno-unstable crashing at boot
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Fri, 13 May 2005 20:42:00 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 13 May 2005 19:41:30 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcVX7s9GiGHfI3zIQYGRLMXKFcj7PgABJ1dg
Thread-topic: [Xen-devel] Xeno-unstable crashing at boot 
Please can you add a show_guest_stack() before the appropriate BUG call,
and also add the usual "HYPERVISOR_console_io(CONSOLEIO_write,
sizeof(printk_buf), printk_buf);" after vscnprintf in kernel/printk.c to
get early printk output.

I've tried but failed to reproduce this on 3 machines.

Thanks,
Ian

> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Mike Wray
> Sent: 13 May 2005 19:57
> To: Anthony Liguori
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] Xeno-unstable crashing at boot
> 
> Anthony Liguori wrote:
> > Mike Wray wrote:
> > 
> >> I'm getting the following crash every time I boot xeno-unstable.
> > 
> > 
> > I was seeing a crash at a similar time during boot.  Keir 
> checked in a 
> > fix last night that fixed the problem.  See bug #36.
> 
> This is from a fresh build this afternoon (last change set 3.30 p.m.).
> 
> Mike
> 
> > 
> > Regards,
> > Anthony Liguori
> > 
> >> Mike
> >>
> >>  Xen version 3.0-devel (mjw@xxxxxxxxxx) (gcc version 3.2.2 
> 20030222 
> >> (Red Hat Linux 3.2.2-5)) Fri May 13 15:30:05 BST 2005  Latest 
> >> ChangeSet: 2005/05/13 15:37:25 1.1401 
> 4284bba5zgcyWRg6WwOIZIaOia4E2g
> >>
> >> (XEN) Physical RAM map:
> >> (XEN)  0000000000000000 - 000000000009fc00 (usable)
> >> (XEN)  000000000009fc00 - 00000000000a0000 (reserved)
> >> (XEN)  00000000000e8000 - 0000000000100000 (reserved)
> >> (XEN)  0000000000100000 - 000000007fff7b00 (usable)
> >> (XEN)  000000007fff7b00 - 0000000080000000 (reserved)
> >> (XEN)  00000000fec00000 - 0000000100000000 (reserved)
> >> (XEN) System RAM: 2047MB (2096728kB)
> >> (XEN) Xen heap: 10MB (10756kB)
> >> (XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, 
> >> vendor = 0
> >> (XEN) CPU#0: Physical ID: 0, Logical ID: 0
> >> (XEN) CPU caps: afebfbff 00000000 00000000 00000000
> >> (XEN) found SMP MP-table at 000f9bf0
> >> (XEN) ACPI: RSDP (v000 COMPAQ                                ) @ 
> >> 0x000ea810
> >> (XEN) ACPI: RSDT (v001 COMPAQ CPQ0054  0x20030821  0x00000000) @ 
> >> 0x7fff7b40
> >> (XEN) ACPI: FADT (v001 COMPAQ PLACER   0x00000001  0x00000000) @ 
> >> 0x7fff7bf8
> >> (XEN) ACPI: SSDT (v001 COMPAQ  PROJECT 0x00000001 MSFT 
> 0x0100000e) @ 
> >> 0x7fff894d
> >> (XEN) ACPI: SSDT (v001 COMPAQ CORE_PNP 0x00000001 MSFT 
> 0x0100000e) @
> >> 0x7fff8ee7
> >> (XEN) ACPI: SSDT (v001 COMPAQ CORE_UTL 0x00000001 MSFT 
> 0x0100000e) @
> >> 0x7fff9433
> >> (XEN) ACPI: SSDT (v001 COMPAQ VILLTBL1 0x00000001 MSFT 
> 0x0100000e) @ 
> >> 0x7fff95ce
> >> (XEN) ACPI: SSDT (v001 COMPAQ LGCYLITE 0x00000001 MSFT 
> 0x0100000e) @
> >> 0x7fff98d6
> >> (XEN) ACPI: SSDT (v001 COMPAQ    UART2 0x00000001 MSFT 
> 0x0100000e) @ 
> >> 0x7fff9e15
> >> (XEN) ACPI: SSDT (v001 COMPAQ   FLOPPY 0x00000001 MSFT 
> 0x0100000e) @ 
> >> 0x7fff9f7c
> >> (XEN) ACPI: MADT (v001 COMPAQ PLACER   0x00000001  0x00000000) @ 
> >> 0x7fff7c6c
> >> (XEN) ACPI: SSDT (v001 COMPAQ     APIC 0x00000001 MSFT 
> 0x0100000e) @ 
> >> 0x7fffba41
> >> (XEN) ACPI: ASF! (v016 COMPAQ PLACER   0x00000001  0x00000000) @ 
> >> 0x7fff7cf0
> >> (XEN) ACPI: SSDT (v001 COMPAQ PNP_PRSS 0x00000001 MSFT 
> 0x0100000e) @
> >> 0x7fffa538
> >> (XEN) ACPI: SSDT (v001 COMPAQ UR2_PRSS 0x00000001 MSFT 
> 0x0100000e) @ 
> >> 0x7fffa95c
> >> (XEN) ACPI: SSDT (v001 COMPAQ FPY_PRSS 0x00000001 MSFT 
> 0x0100000e) @
> >> 0x7fffaac9
> >> (XEN) ACPI: SSDT (v001 COMPAQ       S1 0x00000001 MSFT 
> 0x0100000e) @ 
> >> 0x7fffabe2
> >> (XEN) ACPI: SSDT (v001 COMPAQ      L08 0x00000001 MSFT 
> 0x0100000e) @ 
> >> 0x7fffb7e4
> >> (XEN) ACPI: SSDT (v001 COMPAQ    FINIS 0x00000001 MSFT 
> 0x0100000e) @ 
> >> 0x7fffbbdc
> >> (XEN) ACPI: DSDT (v001 COMPAQ     DSDT 0x00000001 MSFT 
> 0x0100000e) @ 
> >> 0x00000000
> >> (XEN) ACPI: Local APIC address 0xfee00000
> >> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
> >> (XEN) Processor #0 15:2 APIC version 20
> >> (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x06] enabled)
> >> (XEN) Processor #6 15:2 APIC version 20
> >> (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] disabled)
> >> (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
> >> (XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
> >> (XEN) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
> >> (XEN) ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
> >> (XEN) ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
> >> (XEN) IOAPIC[0]: apic_id 1, version 32, address 
> 0xfec00000, GSI 0-23
> >> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> >> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
> >> (XEN) ACPI: IRQ0 used by override.
> >> (XEN) ACPI: IRQ2 used by override.
> >> (XEN) ACPI: IRQ9 used by override.
> >> (XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
> >> (XEN) Using ACPI (MADT) for SMP configuration information
> >> (XEN) Using scheduler: Borrowed Virtual Time (bvt)
> >> (XEN) Initializing CPU#0
> >> (XEN) Detected 2791.093 MHz processor.
> >> (XEN) CPU0 booted
> >> (XEN) Booting processor 1/6 eip 90000
> >> (XEN) Initializing CPU#1
> >> (XEN) CPU1: Before vendor init, caps: bfebfbff 00000000 00000000, 
> >> vendor = 0
> >> (XEN) CPU#1: Physical ID: 3, Logical ID: 0
> >> (XEN) CPU caps: afebfbff 00000000 00000000 00000000
> >> (XEN) CPU1 has booted.
> >> (XEN) Total of 2 processors activated.
> >> (XEN) ENABLING IO-APIC IRQs
> >> (XEN) ..TIMER: vector=0x31 pin1=2 pin2=-1
> >> (XEN) checking TSC synchronization across CPUs: passed.
> >> (XEN) Time init:
> >> (XEN) .... cpu_freq:    00000000:A65CB560
> >> (XEN) .... scale:       00000001:6EE19BBD
> >> (XEN) .... Wall Clock:  1115998803s 140000us
> >> (XEN) mtrr: v2.0 (20020519)
> >> (XEN) *** LOADING DOMAIN 0 ***
> >> (XEN) Xen-ELF header found: 
> >> 
> 'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xC0000000
> ,LOADER=generic' 
> >>
> >> (XEN) PHYSICAL MEMORY ARRANGEMENT:
> >> (XEN)  Dom0 alloc.:   08000000->10000000
> >> (XEN) VIRTUAL MEMORY ARRANGEMENT:
> >> (XEN)  Loaded kernel: c0100000->c05d00e0
> >> (XEN)  Init. ramdisk: c05d1000->c05d1000
> >> (XEN)  Phys-Mach map: c05d1000->c05f1000
> >> (XEN)  Page tables:   c05f1000->c05f4000
> >> (XEN)  Start info:    c05f4000->c05f5000
> >> (XEN)  Boot stack:    c05f5000->c05f6000
> >> (XEN)  TOTAL:         c0000000->c0800000
> >> (XEN)  ENTRY ADDRESS: c0100000
> >> (XEN) Scrubbing Free RAM: .....................done.
> >> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times 
> to switch 
> >> input to Xen).
> >> (XEN) BUG at domain.c:125
> >> (XEN) CPU:    0
> >> (XEN) EIP:    0808:[<ff10618c>]
> >> (XEN) EFLAGS: 00210296   CONTEXT: hypervisor
> >> (XEN) eax: 00000000   ebx: ffbf6900   ecx: 000003f8   edx: 00000000
> >> (XEN) esi: ffbf3080   edi: c0453729   ebp: 00000002   esp: ff103f88
> >> (XEN) ds: 0810   es: 0810   fs: 0810   gs: 0810   ss: 0810 
>   cs: 0808
> >> (XEN) Stack trace from ESP=ff103f88:
> >> (XEN)    ff143308 ff143347 0000007d c0102ff4 c0453729 ffbf3080 
> >> c0102ff4 [ff106198]
> >> (XEN)    [ff106190] 00000808 00210292 [ff135165] 00002834 fbff1000 
> >> 00000432 00000024
> >> (XEN)    c0453729 00000002 00000000 000e0000 00000000 00000819 
> >> 00210217 c0103000
> >> (XEN)    00000821 00000821 00000821 00000000 00000000 ffbf3080
> >> (XEN) Call Trace from ESP=ff103f88:
> >> (XEN)    [<ff106198>] [<ff106190>] [<ff135165>]
> >>
> >> ****************************************
> >> CPU0 FATAL TRAP: vector = 6 (invalid operand) [error_code=0000] 
> >> Aieee! CPU0 is toast...
> >> ****************************************
> >>
> >> _______________________________________________
> >> Xen-devel mailing list
> >> Xen-devel@xxxxxxxxxxxxxxxxxxx
> >> http://lists.xensource.com/xen-devel
> >>
> > 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: [Xen-devel] Xeno-unstable crashing at boot, Mike Wray
Next by Date:  Re: [Xen-devel] Xeno-unstable crashing at boot, Kip Macy
Previous by Thread:  Re: [Xen-devel] Xeno-unstable crashing at boot, Mike Wray
Next by Thread:  Re: [Xen-devel] Xeno-unstable crashing at boot, Kip Macy
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy