thr3ads.net - Xen devel - [Xen-devel] Xeno-unstable crashing at boot [May 2005]

If this information is useful, please help other people find it:
Share via:

Mike Wray

2005-May-13 18:26 UTC

[Xen-devel] Xeno-unstable crashing at boot

I''m getting the following crash every time I boot xeno-unstable.

Mike

  Xen version 3.0-devel (mjw@hpl.hp.com) (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@lists.xensource.com
http://lists.xensource.com/xen-devel

Ian Pratt

2005-May-13 18:43 UTC

head link

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

> I''m getting the following crash every time I boot xeno-unstable.
Are you sure you''re using the kernel version with the extra version
extension ?
e.g. vmlinuz-2.6.11.8-xen0 (note the .8)

Ian
>   Xen version 3.0-devel (mjw@hpl.hp.com) (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@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

David F Barrera

2005-May-13 18:46 UTC

head link

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

Is this on x86_64?  If so, we''ve opened up a defect on the xensource
bugzilla system:

http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=26

On Fri, 2005-05-13 at 19:26 +0100, Mike Wray wrote:> I''m getting the following crash every time I boot xeno-unstable.
> 
> Mike
> 
>   Xen version 3.0-devel (mjw@hpl.hp.com) (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@lists.xensource.com
> http://lists.xensource.com/xen-devel
> -- 
Regards,

David F Barrera
Linux Technology Center
Systems and Technology Group, IBM

"The wisest men follow their own direction. "
                                                        Euripides


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Anthony Liguori

2005-May-13 18:48 UTC

head link

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

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.

Regards,
Anthony Liguori
> Mike
>
>  Xen version 3.0-devel (mjw@hpl.hp.com) (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@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Mike Wray

2005-May-13 18:55 UTC

head link

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

Ian Pratt wrote:>>I''m getting the following crash every time I boot
xeno-unstable.
> 
> 
> Are you sure you''re using the kernel version with the extra
version
> extension ?
> e.g. vmlinuz-2.6.11.8-xen0 (note the .8)
Missed that, but it doesn''t make any difference, 2.6.11.8
still crashes.

Mike> 
> Ian
> 
> 
>>  Xen version 3.0-devel (mjw@hpl.hp.com) (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@lists.xensource.com
>>http://lists.xensource.com/xen-devel
>>
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Mike Wray

2005-May-13 18:56 UTC

head link

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@hpl.hp.com) (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@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Ian Pratt

2005-May-13 19:42 UTC

head link

RE: [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@lists.xensource.com 
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Mike Wray
> Sent: 13 May 2005 19:57
> To: Anthony Liguori
> Cc: xen-devel@lists.xensource.com
> 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@hpl.hp.com) (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@lists.xensource.com
> >> http://lists.xensource.com/xen-devel
> >>
> > 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Kip Macy

2005-May-13 20:20 UTC

head link

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

What hardware configuration are you running on? 

In response to your crash, I *just* pulled a fresh tree and did a make
world. It boots without issue on my test system.

      -Kip


On 5/13/05, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
wrote:> 
> 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@lists.xensource.com
> > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Mike Wray
> > Sent: 13 May 2005 19:57
> > To: Anthony Liguori
> > Cc: xen-devel@lists.xensource.com
> > 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@hpl.hp.com) (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@lists.xensource.com
> > >> http://lists.xensource.com/xen-devel
> > >>
> > >
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> >
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Mike Wray

2005-May-16 12:57 UTC

head link

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

Ian Pratt wrote:> 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.
> 
OK, I tried again with a fresh bk pull and those debug statements added.
I get the same crash, see below. The machine is a dual-processor xeon
(cpuinfo attached). I tried the same build on another machine
(cpuinfo2) and it was OK, so it appears hardware related.

Booting ''Xen / XenoLinux (2.6.11.8)''

root (hd1,0)
  Filesystem type is ext2fs, partition type 0x83
kernel /xen.gz dom0_mem=131072 com1=115200,8n1 console=com1
    [Multiboot-elf, <0x100000:0x50148:0x1eeb8>, shtab=0x16f078,
entry=0x100000]
module /vmlinuz-2.6.11.8-xen0 ro root=/dev/hdb3 4 console=ttyS0
    [Multiboot-module @ 0x170000, 0x4a1398 bytes]

  __  __            _____  ___         _                _
  \ \/ /___ _ __   |___ / / _ \     __| | _____   _____| |
   \  // _ \ ''_ \    |_ \| | | |__ / _` |/ _ \ \ / / _ \ |
   /  \  __/ | | |  ___) | |_| |__| (_| |  __/\ V /  __/ |
  /_/\_\___|_| |_| |____(_)___/    \__,_|\___| \_/ \___|_|

  http://www.cl.cam.ac.uk/netos/xen
  University of Cambridge Computer Laboratory

  Xen version 3.0-devel (mjw@hpl.hp.com) (gcc version 3.2.2 20030222 (Red Hat
Linux 3.2.2-5)) Mon
May 16 13:48:15 BST 2005
  Latest ChangeSet: 2005/05/16 08:43:46 1.1411 42884f321efBfAPblIV0mrlYL-DYpA

(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: bfebfbff 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.043 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: bfebfbff 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:A65BF080
(XEN) .... scale:       00000001:6EE34DEB
(XEN) .... Wall Clock:  1116250571s 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->c05d0160
(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).
Linux version 2.6.11.8-xen0 (mjw@wray-m-3.hpl.hp.com) (gcc version 3.2.2
20030222 (Red Hat Linux
3.2.2-5)) #2 Mon May 16 13:48:47 BST 2005
<6>BIOS-provided physical RAM map:
  Xen: 0000000000100000 - 0000000008000000 (usable)
<5>128MB LOWMEM available.
<7>On node 0 totalpages: 32768
<7>  DMA zone: 32768 pages, LIFO batch:8
<7>  Normal zone: 0 pages, LIFO batch:1
<7>  HighMem zone: 0 pages, LIFO batch:1
<6>found SMP MP-table at 3bfe2bf0
<6>DMI 2.3 present.
<7>ACPI: RSDP (v000 COMPAQ                                ) @ 0x000ea810
<7>ACPI: RSDT (v001 COMPAQ CPQ0054  0x20030821  0x00000000) @ 0x7fff7b40
<7>ACPI: FADT (v001 COMPAQ PLACER   0x00000001  0x00000000) @ 0x7fff7bf8
<7>ACPI: SSDT (v001 COMPAQ  PROJECT 0x00000001 MSFT 0x0100000e) @
0x7fff894d
<7>ACPI: SSDT (v001 COMPAQ CORE_PNP 0x00000001 MSFT 0x0100000e) @
0x7fff8ee7
(XEN) Guest EIP is 00000000
(XEN)    00000000 00000000 00000000 00000819 00210217 00000000 00000000 00000000
(XEN)    00000819 00210217 00000000 00000000 00000000 00000819 00210217 00000000
(XEN)    00000000 00000000 00000819 00210217 00000000 00000000 00000000 00000819
(XEN)    00210217 00000000 00000000 00000000 00000819 00210217 00000000 00000000
(XEN)    00000000 00000819 00210217 00000000 00000000 00000000 00000819 00210217
(XEN)    00000000 00000000 00000000 00000819 00210217 00000000 00000000 00000000
(XEN)    00000819 00210217 00000000 00000000 00000000 00000819 00210217 00000000
(XEN)    00000000 00000000 00000819 00210217 00000000 00000000 00000000 00000819
(XEN)    00210217 00000000 00000000 00000000 00000819 00210217 00000000 00000000
(XEN)    00000000 00000819 00210217 00000000 00000000 00000000 00000819 00210217
(XEN)    00000000 00000000 00000000 00000819 00210217 00000000 00000000 00000000
(XEN)    00000819 00210217 00000000 00000000 00000000 00000819 00210217 00000000
(XEN)    00000000 00000000 00000819 00210217 00000000 00000000 00000000 00000819
(XEN)    00210217 00000000 00000000 00000000 00000819 00210217 00000000 00000000
(XEN)    00000000 00000819 00210217 00000000 00000000 00000000 00000819 00210217
(XEN)    00000000 00000000 00000000 00000819 00210217 00000000 00000000 00000000
(XEN)    00000819 00210217 00000000 00000000 00000000 00000819 00210217 00000000
(XEN)    00000000 00000000 00000819 00210217 00000000 00000000 00000000 00000819
(XEN)    00210217 00000000 00000000 00000000 00000819 00210217 00000000 00000000
(XEN)    00000000 00000819 00210217 00000000 00000000 00000000 00000819 00210217
(XEN) BUG at domain.c:126
(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: c04537e9   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 0000007e c0102ff4 c04537e9 ffbf3080 c0102ff4
[ff106198]
(XEN)    [ff106190] 00000808 00210292 [ff135165] 00002834 fbff1000 00000432
00000024
(XEN)    c04537e9 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@lists.xensource.com
http://lists.xensource.com/xen-devel

Ian Pratt

2005-May-16 13:27 UTC

head link

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

> OK, I tried again with a fresh bk pull and those debug 
> statements added.
> I get the same crash, see below. The machine is a 
> dual-processor xeon (cpuinfo attached). I tried the same 
> build on another machine
> (cpuinfo2) and it was OK, so it appears hardware related.
What hardware is the problem machine? It has an impresively long list of
ACPI table entries. Since the code being executed is the native Linux
code it''s surprising that it''s having problems. 

Please can you try using a DEBUG=y build of Xen, and then adding
show_guest_stack earlier in the failure path.

Thanks,
Ian

> Booting ''Xen / XenoLinux (2.6.11.8)''
> 
> root (hd1,0)
>   Filesystem type is ext2fs, partition type 0x83 kernel 
> /xen.gz dom0_mem=131072 com1=115200,8n1 console=com1
>     [Multiboot-elf, <0x100000:0x50148:0x1eeb8>, 
> shtab=0x16f078, entry=0x100000] module /vmlinuz-2.6.11.8-xen0 
> ro root=/dev/hdb3 4 console=ttyS0
>     [Multiboot-module @ 0x170000, 0x4a1398 bytes]
> 
>   __  __            _____  ___         _                _
>   \ \/ /___ _ __   |___ / / _ \     __| | _____   _____| |
>    \  // _ \ ''_ \    |_ \| | | |__ / _` |/ _ \ \ / / _ \ |
>    /  \  __/ | | |  ___) | |_| |__| (_| |  __/\ V /  __/ |
>   /_/\_\___|_| |_| |____(_)___/    \__,_|\___| \_/ \___|_|
> 
>   http://www.cl.cam.ac.uk/netos/xen
>   University of Cambridge Computer Laboratory
> 
>   Xen version 3.0-devel (mjw@hpl.hp.com) (gcc version 3.2.2 
> 20030222 (Red Hat Linux 3.2.2-5)) Mon May 16 13:48:15 BST 2005
>   Latest ChangeSet: 2005/05/16 08:43:46 1.1411 
> 42884f321efBfAPblIV0mrlYL-DYpA
> 
> (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: bfebfbff 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.043 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: bfebfbff 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:A65BF080
> (XEN) .... scale:       00000001:6EE34DEB
> (XEN) .... Wall Clock:  1116250571s 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->c05d0160
> (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).
> Linux version 2.6.11.8-xen0 (mjw@wray-m-3.hpl.hp.com) (gcc 
> version 3.2.2 20030222 (Red Hat Linux
> 3.2.2-5)) #2 Mon May 16 13:48:47 BST 2005 <6>BIOS-provided 
> physical RAM map:
>   Xen: 0000000000100000 - 0000000008000000 (usable) <5>128MB 
> LOWMEM available.
> <7>On node 0 totalpages: 32768
> <7>  DMA zone: 32768 pages, LIFO batch:8 <7>  Normal zone: 0 
> pages, LIFO batch:1 <7>  HighMem zone: 0 pages, LIFO batch:1 
> <6>found SMP MP-table at 3bfe2bf0 <6>DMI 2.3 present.
> <7>ACPI: RSDP (v000 COMPAQ                                ) @ 
> 0x000ea810
> <7>ACPI: RSDT (v001 COMPAQ CPQ0054  0x20030821  0x00000000) @ 
> 0x7fff7b40
> <7>ACPI: FADT (v001 COMPAQ PLACER   0x00000001  0x00000000) @ 
> 0x7fff7bf8
> <7>ACPI: SSDT (v001 COMPAQ  PROJECT 0x00000001 MSFT 
> 0x0100000e) @ 0x7fff894d
> <7>ACPI: SSDT (v001 COMPAQ CORE_PNP 0x00000001 MSFT 
> 0x0100000e) @ 0x7fff8ee7
> (XEN) Guest EIP is 00000000
> (XEN)    00000000 00000000 00000000 00000819 00210217 
> 00000000 00000000 00000000
> (XEN)    00000819 00210217 00000000 00000000 00000000 
> 00000819 00210217 00000000
> (XEN)    00000000 00000000 00000819 00210217 00000000 
> 00000000 00000000 00000819
> (XEN)    00210217 00000000 00000000 00000000 00000819 
> 00210217 00000000 00000000
> (XEN)    00000000 00000819 00210217 00000000 00000000 
> 00000000 00000819 00210217
> (XEN)    00000000 00000000 00000000 00000819 00210217 
> 00000000 00000000 00000000
> (XEN)    00000819 00210217 00000000 00000000 00000000 
> 00000819 00210217 00000000
> (XEN)    00000000 00000000 00000819 00210217 00000000 
> 00000000 00000000 00000819
> (XEN)    00210217 00000000 00000000 00000000 00000819 
> 00210217 00000000 00000000
> (XEN)    00000000 00000819 00210217 00000000 00000000 
> 00000000 00000819 00210217
> (XEN)    00000000 00000000 00000000 00000819 00210217 
> 00000000 00000000 00000000
> (XEN)    00000819 00210217 00000000 00000000 00000000 
> 00000819 00210217 00000000
> (XEN)    00000000 00000000 00000819 00210217 00000000 
> 00000000 00000000 00000819
> (XEN)    00210217 00000000 00000000 00000000 00000819 
> 00210217 00000000 00000000
> (XEN)    00000000 00000819 00210217 00000000 00000000 
> 00000000 00000819 00210217
> (XEN)    00000000 00000000 00000000 00000819 00210217 
> 00000000 00000000 00000000
> (XEN)    00000819 00210217 00000000 00000000 00000000 
> 00000819 00210217 00000000
> (XEN)    00000000 00000000 00000819 00210217 00000000 
> 00000000 00000000 00000819
> (XEN)    00210217 00000000 00000000 00000000 00000819 
> 00210217 00000000 00000000
> (XEN)    00000000 00000819 00210217 00000000 00000000 
> 00000000 00000819 00210217
> (XEN) BUG at domain.c:126
> (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: c04537e9   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 0000007e c0102ff4 c04537e9 
> ffbf3080 c0102ff4 [ff106198]
> (XEN)    [ff106190] 00000808 00210292 [ff135165] 00002834 
> fbff1000 00000432 00000024
> (XEN)    c04537e9 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@lists.xensource.com
http://lists.xensource.com/xen-devel

Steven Hand

2005-May-16 13:29 UTC

head link

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

> > OK, I tried again with a fresh bk pull and those debug 
> > statements added.
> > I get the same crash, see below. The machine is a 
> > dual-processor xeon (cpuinfo attached). I tried the same 
> > build on another machine
> > (cpuinfo2) and it was OK, so it appears hardware related.
> 
> What hardware is the problem machine? It has an impresively long list of
> ACPI table entries. Since the code being executed is the native Linux
> code it''s surprising that it''s having problems. 
> 
> Please can you try using a DEBUG=y build of Xen, and then adding
> show_guest_stack earlier in the failure path.

That''s 

# cd xen-unstable.bk/xen 
# make debug=y 

btw (i.e. "debug" is case sensitive). 


cheers,

S.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Mark Williamson

2005-May-16 13:33 UTC

head link

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

> That''s
>
> # cd xen-unstable.bk/xen
> # make debug=y
>
> btw (i.e. "debug" is case sensitive).
You should probably "make clean" before doing this, otherwise some
object
files may not be rebuilt with debug info.

Cheers,
Mark
>
>
> cheers,
>
> S.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Mike Wray

2005-May-16 18:18 UTC

head link

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

Ian Pratt wrote:>  
> 
>>OK, I tried again with a fresh bk pull and those debug 
>>statements added.
>>I get the same crash, see below. The machine is a 
>>dual-processor xeon (cpuinfo attached). I tried the same 
>>build on another machine
>>(cpuinfo2) and it was OK, so it appears hardware related.
> 
> 
> What hardware is the problem machine? It has an impresively long list of
> ACPI table entries. Since the code being executed is the native Linux
> code it''s surprising that it''s having problems. 
It''s a dual processor 2.8GHz xeon, 2GB RAM.
The cpuinfo was attached to an earlier email.
I''ve attached it again, with hwconf.
> 
> Please can you try using a DEBUG=y build of Xen, and then adding
> show_guest_stack earlier in the failure path.
So ''DEBUG=y make world''?
Can you suggest what a good place ''earlier in the failure
path'' might be?

Thanks,
Mike
>>Booting ''Xen / XenoLinux (2.6.11.8)''
>>
>>root (hd1,0)
>>  Filesystem type is ext2fs, partition type 0x83 kernel 
>>/xen.gz dom0_mem=131072 com1=115200,8n1 console=com1
>>    [Multiboot-elf, <0x100000:0x50148:0x1eeb8>, 
>>shtab=0x16f078, entry=0x100000] module /vmlinuz-2.6.11.8-xen0 
>>ro root=/dev/hdb3 4 console=ttyS0
>>    [Multiboot-module @ 0x170000, 0x4a1398 bytes]
>>
>>  __  __            _____  ___         _                _
>>  \ \/ /___ _ __   |___ / / _ \     __| | _____   _____| |
>>   \  // _ \ ''_ \    |_ \| | | |__ / _` |/ _ \ \ / / _ \ |
>>   /  \  __/ | | |  ___) | |_| |__| (_| |  __/\ V /  __/ |
>>  /_/\_\___|_| |_| |____(_)___/    \__,_|\___| \_/ \___|_|
>>
>>  http://www.cl.cam.ac.uk/netos/xen
>>  University of Cambridge Computer Laboratory
>>
>>  Xen version 3.0-devel (mjw@hpl.hp.com) (gcc version 3.2.2 
>>20030222 (Red Hat Linux 3.2.2-5)) Mon May 16 13:48:15 BST 2005
>>  Latest ChangeSet: 2005/05/16 08:43:46 1.1411 
>>42884f321efBfAPblIV0mrlYL-DYpA
>>
>>(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: bfebfbff 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.043 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: bfebfbff 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:A65BF080
>>(XEN) .... scale:       00000001:6EE34DEB
>>(XEN) .... Wall Clock:  1116250571s 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->c05d0160
>>(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).
>>Linux version 2.6.11.8-xen0 (mjw@wray-m-3.hpl.hp.com) (gcc 
>>version 3.2.2 20030222 (Red Hat Linux
>>3.2.2-5)) #2 Mon May 16 13:48:47 BST 2005 <6>BIOS-provided 
>>physical RAM map:
>>  Xen: 0000000000100000 - 0000000008000000 (usable) <5>128MB 
>>LOWMEM available.
>><7>On node 0 totalpages: 32768
>><7>  DMA zone: 32768 pages, LIFO batch:8 <7>  Normal zone: 0
>>pages, LIFO batch:1 <7>  HighMem zone: 0 pages, LIFO batch:1 
>><6>found SMP MP-table at 3bfe2bf0 <6>DMI 2.3 present.
>><7>ACPI: RSDP (v000 COMPAQ                                ) @ 
>>0x000ea810
>><7>ACPI: RSDT (v001 COMPAQ CPQ0054  0x20030821  0x00000000) @ 
>>0x7fff7b40
>><7>ACPI: FADT (v001 COMPAQ PLACER   0x00000001  0x00000000) @ 
>>0x7fff7bf8
>><7>ACPI: SSDT (v001 COMPAQ  PROJECT 0x00000001 MSFT 
>>0x0100000e) @ 0x7fff894d
>><7>ACPI: SSDT (v001 COMPAQ CORE_PNP 0x00000001 MSFT 
>>0x0100000e) @ 0x7fff8ee7
>>(XEN) Guest EIP is 00000000
>>(XEN)    00000000 00000000 00000000 00000819 00210217 
>>00000000 00000000 00000000
>>(XEN)    00000819 00210217 00000000 00000000 00000000 
>>00000819 00210217 00000000
>>(XEN)    00000000 00000000 00000819 00210217 00000000 
>>00000000 00000000 00000819
>>(XEN)    00210217 00000000 00000000 00000000 00000819 
>>00210217 00000000 00000000
>>(XEN)    00000000 00000819 00210217 00000000 00000000 
>>00000000 00000819 00210217
>>(XEN)    00000000 00000000 00000000 00000819 00210217 
>>00000000 00000000 00000000
>>(XEN)    00000819 00210217 00000000 00000000 00000000 
>>00000819 00210217 00000000
>>(XEN)    00000000 00000000 00000819 00210217 00000000 
>>00000000 00000000 00000819
>>(XEN)    00210217 00000000 00000000 00000000 00000819 
>>00210217 00000000 00000000
>>(XEN)    00000000 00000819 00210217 00000000 00000000 
>>00000000 00000819 00210217
>>(XEN)    00000000 00000000 00000000 00000819 00210217 
>>00000000 00000000 00000000
>>(XEN)    00000819 00210217 00000000 00000000 00000000 
>>00000819 00210217 00000000
>>(XEN)    00000000 00000000 00000819 00210217 00000000 
>>00000000 00000000 00000819
>>(XEN)    00210217 00000000 00000000 00000000 00000819 
>>00210217 00000000 00000000
>>(XEN)    00000000 00000819 00210217 00000000 00000000 
>>00000000 00000819 00210217
>>(XEN)    00000000 00000000 00000000 00000819 00210217 
>>00000000 00000000 00000000
>>(XEN)    00000819 00210217 00000000 00000000 00000000 
>>00000819 00210217 00000000
>>(XEN)    00000000 00000000 00000819 00210217 00000000 
>>00000000 00000000 00000819
>>(XEN)    00210217 00000000 00000000 00000000 00000819 
>>00210217 00000000 00000000
>>(XEN)    00000000 00000819 00210217 00000000 00000000 
>>00000000 00000819 00210217
>>(XEN) BUG at domain.c:126
>>(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: c04537e9   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 0000007e c0102ff4 c04537e9 
>>ffbf3080 c0102ff4 [ff106198]
>>(XEN)    [ff106190] 00000808 00210292 [ff135165] 00002834 
>>fbff1000 00000432 00000024
>>(XEN)    c04537e9 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@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Ian Pratt

2005-May-16 19:55 UTC

head link

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

> > What hardware is the problem machine? It has an impresively 
> long list of
> > ACPI table entries. Since the code being executed is the 
> native Linux
> > code it''s surprising that it''s having problems. 
> 
> It''s a dual processor 2.8GHz xeon, 2GB RAM.
> The cpuinfo was attached to an earlier email.
> I''ve attached it again, with hwconf.
No, I mean the make and model of the machine. I have 3 different kinds
of dual 2.8GHz Xeon with tg3 NICs that Xen unstable works fine with. It
something specific to your particular machine, probably the BIOS. (BTW:
are their BIOS upgrades available?)
> > Please can you try using a DEBUG=y build of Xen, and then adding
> > show_guest_stack earlier in the failure path.
> 
> So ''DEBUG=y make world''?
"make clean; make debug=y dist" should do it.
> Can you suggest what a good place ''earlier in the failure 
> path'' might be?
I expect you''ll get an error message from Xen before the BUG in domain
crash. See where the error message comes from, and then add the
show_guest_stack to the appropriate path.

Thanks,
Ian


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Mike Wray

2005-May-17 09:19 UTC

head link

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

Ian Pratt wrote:>  > > What hardware is the problem machine? It has an impresively 
> 
>>long list of
>>
>>>ACPI table entries. Since the code being executed is the 
>>
>>native Linux
>>
>>>code it''s surprising that it''s having problems. 
>>
>>It''s a dual processor 2.8GHz xeon, 2GB RAM.
>>The cpuinfo was attached to an earlier email.
>>I''ve attached it again, with hwconf.
> 
> 
> No, I mean the make and model of the machine. I have 3 different kinds
> of dual 2.8GHz Xeon with tg3 NICs that Xen unstable works fine with. It
> something specific to your particular machine, probably the BIOS. (BTW:
> are their BIOS upgrades available?)
It''s an ''HP Workstation xw6000'', part no. DF521A.
There don''t appear to be any relevant BIOS updates.
>>>Please can you try using a DEBUG=y build of Xen, and then adding
>>>show_guest_stack earlier in the failure path.
>>
>>So ''DEBUG=y make world''?
 >>  "make clean; make debug=y dist" should do it.
> 
> 
>>Can you suggest what a good place ''earlier in the failure 
>>path'' might be?
> 
> I expect you''ll get an error message from Xen before the BUG in
domain
> crash. See where the error message comes from, and then add the
> show_guest_stack to the appropriate path.
A debug build gave the following crash.
It''s different, a page fault, but there''s no previous error
message
that lets me see where to put the show_guest_stack.

However the map shows

c02232c4 T acpi_table_print
c0223352 T acpi_table_print_madt_entry
c022350c t acpi_table_compute_checksum
c0223540 T acpi_os_initialize
c0223543 T acpi_os_initialize1

so the EIP c022352c looks like it''s in acpi_table_compute_checksum?


  Xen version 3.0-devel (mjw@hpl.hp.com) (gcc version 3.2.2 20030222 (Red Hat
Linux 3.2.2-5)) Mon
May 16 19:29:28 BST 2005
  Latest ChangeSet: 2005/05/16 14:16:20 1.1412 42889d24Cf_SZ1HYkTCtmREploQuWg

(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 (10680kB)
(XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0
(XEN) CPU#0: Physical ID: 0, Logical ID: 0
(XEN) CPU caps: bfebfbff 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.039 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: bfebfbff 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:A65BE270
(XEN) .... scale:       00000001:6EE36CEF
(XEN) .... Wall Clock:  1116272862s 140000us
(XEN) mtrr: v2.0 (20020519)
(XEN) (file=grant_table.c, line=1230) Grant table init
(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->c05d0160
(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) CPU:    0
(XEN) EIP:    0819:[<c022352c>]
(XEN) EFLAGS: 00210217   CONTEXT: guest
(XEN) eax: 00000000   ebx: 00002834   ecx: fbff1000   edx: 00000432
(XEN) esi: 00000024   edi: c04537e9   ebp: 00000002   esp: c053ff38
(XEN) ds: 0821   es: 0821   fs: 0000   gs: 0000   ss: 0821   cs: 0819
(XEN) Stack trace from ESP=ff103fe4:
(XEN)    c053ff38 00000821 00000821 00000821 00000000 00000000 ffbf8080
(XEN) Call Trace from ESP=ff103fe4:
(XEN)
(XEN) Guest EIP is c022352c
(XEN)    7fff8ee7 c0554814 fbff0ee7 0000054c fbff0ee7 7fff8ee7 00000018 fbff0ee7
(XEN)    fbfef810 00000000 00000010 00000000 c0554a0c fbfef810 00000000 00000000
(XEN)    c054b7fd 00000010 c054d83f c053ff9c c0548b0f c059ba20 c043af65 00000000
(XEN)    0000008e 00000006 c053e000 00000001 0000008b 00000000 c011cea9 0000000a
(XEN)    00000400 c042bba0 c053ffe4 c053e000 c05f4200 c053e000 c05f4200 c059b620
(XEN)    00000000 c05406c8 c053fff4 00000000 00000000 00000000 00000000 c059ba20
(XEN)    0002080b c010006c
(XEN) debugtrace_dump() starting
(XEN) debugtrace_dump() finished

****************************************
CPU0 FATAL PAGE FAULT
[error_code=0000]
Faulting linear address: fbff1000
Aieee! CPU0 is toast...
****************************************

HTH,

Mike

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Christian Limpach

2005-May-17 10:29 UTC

head link

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

On 5/17/05, Mike Wray <mike.wray@hp.com> wrote:> >  "make clean; make debug=y dist" should do it.
> >
> >
> >>Can you suggest what a good place ''earlier in the failure
> >>path'' might be?
> >
> > I expect you''ll get an error message from Xen before the BUG
in domain
> > crash. See where the error message comes from, and then add the
> > show_guest_stack to the appropriate path.
> 
> A debug build gave the following crash.
> It''s different, a page fault, but there''s no previous
error message
> that lets me see where to put the show_guest_stack.
The guest stack is now always printed when dom0 fails, which is why
you get a more relevant error message.

Could you please add "earlyprintk=serial" to the linux command line
options (CONFIG_EARLY_PRINTK should be enabled in your kernel config
file by default -- if not, please enable it) and add a call do
dump_stack() at the beginning of acpi_table_compute_checksum in
linux-2.6.11-xen-sparse/drivers/acpi/tables.c.  Thanks!

    christian

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Mike Wray

2005-May-17 11:52 UTC

head link

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

Christian Limpach wrote:> On 5/17/05, Mike Wray <mike.wray@hp.com> wrote:
> 
>>> "make clean; make debug=y dist" should do it.
>>>
>>>
>>>
>>>>Can you suggest what a good place ''earlier in the
failure
>>>>path'' might be?
>>>
>>>I expect you''ll get an error message from Xen before the
BUG in domain
>>>crash. See where the error message comes from, and then add the
>>>show_guest_stack to the appropriate path.
>>
>>A debug build gave the following crash.
>>It''s different, a page fault, but there''s no previous
error message
>>that lets me see where to put the show_guest_stack.
> 
> 
> The guest stack is now always printed when dom0 fails, which is why
> you get a more relevant error message.
> 
> Could you please add "earlyprintk=serial" to the linux command
line
> options (CONFIG_EARLY_PRINTK should be enabled in your kernel config
> file by default -- if not, please enable it) and add a call do
> dump_stack() at the beginning of acpi_table_compute_checksum in
> linux-2.6.11-xen-sparse/drivers/acpi/tables.c.  Thanks!
OK, I did that and planted a few dump_stack() calls in the acpi code:

  Xen version 3.0-devel (mjw@hpl.hp.com) (gcc version 3.2.2 20030222 (Red Hat
Linux 3.2.2-5)) Tue
May 17 12:46:45 BST 2005
  Latest ChangeSet: 2005/05/16 14:16:20 1.1412 42889d24Cf_SZ1HYkTCtmREploQuWg

(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 (10680kB)
(XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0
(XEN) CPU#0: Physical ID: 0, Logical ID: 0
(XEN) CPU caps: bfebfbff 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.052 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: bfebfbff 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:A65C1600
(XEN) .... scale:       00000001:6EE2FB37
(XEN) .... Wall Clock:  1116333274s 140000us
(XEN) mtrr: v2.0 (20020519)
(XEN) (file=grant_table.c, line=1230) Grant table init
(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->c05d0160
(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).
Linux version 2.6.11.8-xen0 (mjw@wray-m-3.hpl.hp.com) (gcc version 3.2.2
20030222 (Red Hat Linux
3.2.2-5)) #7 Tue May 17 12:47:10 BST 2005
<6>BIOS-provided physical RAM map:
  Xen: 0000000000100000 - 0000000008000000 (usable)
<5>128MB LOWMEM available.
<7>On node 0 totalpages: 32768
<7>  DMA zone: 32768 pages, LIFO batch:8
<7>  Normal zone: 0 pages, LIFO batch:1
<7>  HighMem zone: 0 pages, LIFO batch:1
<6>found SMP MP-table at 3bfe2bf0
<6>DMI 2.3 present.
<6>acpi_table_init>
<6>acpi_table_init> dump_stack:
  [<c0554a0a>] acpi_table_init+0x25/0xc6
  [<c054b7fd>] acpi_boot_table_init+0x2d/0xe0
  [<c054d83f>] dmi_scan_machine+0x1f/0x30
  [<c0548b0f>] setup_arch+0x43f/0x540
  [<c011ceb9>] vprintk+0x149/0x200
  [<c05406c8>] start_kernel+0x28/0x1f0
<7>ACPI: RSDP (v000 COMPAQ                                ) @ 0x000ea810
<6>acpi_table_compute_checksum> table_pointer=fbfef810 length=20
<6>acpi_table_compute_checksum> dump_stack:
  [<c022353e>] acpi_table_compute_checksum+0x32/0x64
  [<c0554a52>] acpi_table_init+0x6d/0xc6
  [<c054b7fd>] acpi_boot_table_init+0x2d/0xe0
  [<c054d83f>] dmi_scan_machine+0x1f/0x30
  [<c0548b0f>] setup_arch+0x43f/0x540
  [<c011ceb9>] vprintk+0x149/0x200
  [<c05406c8>] start_kernel+0x28/0x1f0
<6>acpi_table_init> dump_stack:
  [<c0554a83>] acpi_table_init+0x9e/0xc6
  [<c054b7fd>] acpi_boot_table_init+0x2d/0xe0
  [<c054d83f>] dmi_scan_machine+0x1f/0x30
  [<c0548b0f>] setup_arch+0x43f/0x540
  [<c011ceb9>] vprintk+0x149/0x200
  [<c05406c8>] start_kernel+0x28/0x1f0
<6>acpi_table_get_sdt>
<6>acpi_table_get_sdt> dump_stack:
  [<c055469e>] acpi_table_get_sdt+0x35/0x37c
  [<c0554a89>] acpi_table_init+0xa4/0xc6
  [<c054b7fd>] acpi_boot_table_init+0x2d/0xe0
  [<c054d83f>] dmi_scan_machine+0x1f/0x30
  [<c0548b0f>] setup_arch+0x43f/0x540
  [<c011ceb9>] vprintk+0x149/0x200
  [<c05406c8>] start_kernel+0x28/0x1f0
<6>acpi_table_compute_checksum> table_pointer=fbff0b40 length=104
<6>acpi_table_compute_checksum> dump_stack:
  [<c022353e>] acpi_table_compute_checksum+0x32/0x64
  [<c055474a>] acpi_table_get_sdt+0xe1/0x37c
  [<c0554a89>] acpi_table_init+0xa4/0xc6
  [<c054b7fd>] acpi_boot_table_init+0x2d/0xe0
  [<c054d83f>] dmi_scan_machine+0x1f/0x30
  [<c0548b0f>] setup_arch+0x43f/0x540
  [<c011ceb9>] vprintk+0x149/0x200
  [<c05406c8>] start_kernel+0x28/0x1f0
<7>ACPI: RSDT (v001 COMPAQ CPQ0054  0x20030821  0x00000000) @ 0x7fff7b40
<7>ACPI: FADT (v001 COMPAQ PLACER   0x00000001  0x00000000) @ 0x7fff7bf8
<6>acpi_table_compute_checksum> table_pointer=fbff0bf8 length=116
<6>acpi_table_compute_checksum> dump_stack:
  [<c022353e>] acpi_table_compute_checksum+0x32/0x64
  [<c055483a>] acpi_table_get_sdt+0x1d1/0x37c
  [<c0554a89>] acpi_table_init+0xa4/0xc6
  [<c054b7fd>] acpi_boot_table_init+0x2d/0xe0
  [<c054d83f>] dmi_scan_machine+0x1f/0x30
  [<c0548b0f>] setup_arch+0x43f/0x540
  [<c011ceb9>] vprintk+0x149/0x200
  [<c05406c8>] start_kernel+0x28/0x1f0
<7>ACPI: SSDT (v001 COMPAQ  PROJECT 0x00000001 MSFT 0x0100000e) @
0x7fff894d
<6>acpi_table_compute_checksum> table_pointer=fbff094d length=1434
<6>acpi_table_compute_checksum> dump_stack:
  [<c022353e>] acpi_table_compute_checksum+0x32/0x64
  [<c055483a>] acpi_table_get_sdt+0x1d1/0x37c
  [<c0554a89>] acpi_table_init+0xa4/0xc6
  [<c054b7fd>] acpi_boot_table_init+0x2d/0xe0
  [<c054d83f>] dmi_scan_machine+0x1f/0x30
  [<c0548b0f>] setup_arch+0x43f/0x540
  [<c011ceb9>] vprintk+0x149/0x200
  [<c05406c8>] start_kernel+0x28/0x1f0
<7>ACPI: SSDT (v001 COMPAQ CORE_PNP 0x00000001 MSFT 0x0100000e) @
0x7fff8ee7
<6>acpi_table_compute_checksum> table_pointer=fbff0ee7 length=1356
<6>acpi_table_compute_checksum> dump_stack:
  [<c022353e>] acpi_table_compute_checksum+0x32/0x64
  [<c055483a>] acpi_table_get_sdt+0x1d1/0x37c
  [<c0554a89>] acpi_table_init+0xa4/0xc6
  [<c054b7fd>] acpi_boot_table_init+0x2d/0xe0
  [<c054d83f>] dmi_scan_machine+0x1f/0x30
  [<c0548b0f>] setup_arch+0x43f/0x540
  [<c011ceb9>] vprintk+0x149/0x200
  [<c05406c8>] start_kernel+0x28/0x1f0
(XEN) CPU:    0
(XEN) EIP:    0819:[<c0223558>]
(XEN) EFLAGS: 00210217   CONTEXT: guest
(XEN) eax: 00000000   ebx: 00000432   ecx: c04ac2f8   edx: 00000001
(XEN) esi: fbff1000   edi: 00002834   ebp: 00000002   esp: c053ff28
(XEN) ds: 0821   es: 0821   fs: 0000   gs: 0000   ss: 0821   cs: 0819
(XEN) Stack trace from ESP=ff103fe4:
(XEN)    c053ff28 00000821 00000821 00000821 00000000 00000000 ffbf8080
(XEN) Call Trace from ESP=ff103fe4:
(XEN)
(XEN) Guest EIP is c0223558
(XEN)    7fff8ee7 00000024 c0453869 c055483a fbff0ee7 0000054c fbff0ee7 7fff8ee7
(XEN)    00000018 fbff0ee7 fbfef810 00000000 00000010 00000000 c0554a89 fbfef810
(XEN)    c0453884 c042fad3 00000000 00000000 c054b7fd 00000010 c054d83f c053ff9c
(XEN)    c0548b0f c059ba20 c043afe5 00000000 0000008e 00000006 c053e000 00000001
(XEN)    0000008b 00000000 c011ceb9 0000000a 00000400 c042bbe0 c053ffe4 c053e000
(XEN)    c05f4200 c053e000 c05f4200 c059b620 00000000 c05406c8 c053fff4 00000000
(XEN)    00000000 00000000 00000000 c059ba20 0002080b c010006c
(XEN) debugtrace_dump() starting
(XEN) debugtrace_dump() finished

****************************************
CPU0 FATAL PAGE FAULT
[error_code=0000]
Faulting linear address: fbff1000
Aieee! CPU0 is toast...
****************************************

Reboot in five seconds...

Mike


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Keir Fraser

2005-May-17 13:26 UTC

head link

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

On 17 May 2005, at 12:52, Mike Wray wrote:
>> The guest stack is now always printed when dom0 fails, which is why
>> you get a more relevant error message.
>> Could you please add "earlyprintk=serial" to the linux
command line
>> options (CONFIG_EARLY_PRINTK should be enabled in your kernel config
>> file by default -- if not, please enable it) and add a call do
>> dump_stack() at the beginning of acpi_table_compute_checksum in
>> linux-2.6.11-xen-sparse/drivers/acpi/tables.c.  Thanks!
>
> OK, I did that and planted a few dump_stack() calls in the acpi code:
I''ve just checked in a fix -- the Xen-specific acpi_map_table() 
function was both unnecessary and broken. Hopefully latest unstable 
will boot on your test machine.

  -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Grzegorz Milos

2005-May-17 16:01 UTC

head link

[Xen-devel] memory mapping

Hi there!

You were in a meeting half an hour ago (or so), so instead of asking in person 
I am writing this email.

I am looking at the memory mapping done from a privileged domain, and I am 
getting a bit lost in the call stack. Could you possibly fill in the missing 
gap (hopefully I did not get everything wrong :) ):

xc_map_foreign_range   (userspace dom0)
ioctl (userspace dom0)

privcmd_ioctl (kernelspace dom0)
direct_remap_area_pages (kernelspace dom0)
__HYPERVISOR_do_mmu_update ?
....

do_mmu_update (Xen)


Also, when dom0 decides to unmap some memory, isn''t it that domain just
drops
appropirate entry from its pagetable and Xen is not even informed? This would 
mean that the counter we talked about could not be really made to work that 
easily. 
What if I wanted to force dom0 to drop some mapping. Any simple way of doing 
that?

Thanks
Gregor



-- 
Quidquid latine dictum sit, altum viditur --- Anon

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Grzegorz Milos

2005-May-17 16:09 UTC

head link

Re: [Xen-devel] memory mapping

Oops, sorry, that was supposed to be send to Keir directly. Please ignore.

Gregor
> Hi there!
>
> You were in a meeting half an hour ago (or so), so instead of asking in
> person I am writing this email.
>
> I am looking at the memory mapping done from a privileged domain, and I am
> getting a bit lost in the call stack. Could you possibly fill in the
> missing gap (hopefully I did not get everything wrong :) ):
>
> xc_map_foreign_range   (userspace dom0)
> ioctl (userspace dom0)
>
> privcmd_ioctl (kernelspace dom0)
> direct_remap_area_pages (kernelspace dom0)
> __HYPERVISOR_do_mmu_update ?
> ....
>
> do_mmu_update (Xen)
>
>
> Also, when dom0 decides to unmap some memory, isn''t it that domain
just
> drops appropirate entry from its pagetable and Xen is not even informed?
> This would mean that the counter we talked about could not be really made
> to work that easily.
> What if I wanted to force dom0 to drop some mapping. Any simple way of
> doing that?
>
> Thanks
> Gregor
-- 
Quidquid latine dictum sit, altum viditur --- Anon

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Mike Wray

2005-May-17 18:23 UTC

head link

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

Keir Fraser wrote:> 
> On 17 May 2005, at 12:52, Mike Wray wrote:
> 
>>> The guest stack is now always printed when dom0 fails, which is why
>>> you get a more relevant error message.
>>> Could you please add "earlyprintk=serial" to the linux
command line
>>> options (CONFIG_EARLY_PRINTK should be enabled in your kernel
config
>>> file by default -- if not, please enable it) and add a call do
>>> dump_stack() at the beginning of acpi_table_compute_checksum in
>>> linux-2.6.11-xen-sparse/drivers/acpi/tables.c.  Thanks!
>>
>>
>> OK, I did that and planted a few dump_stack() calls in the acpi code:
> 
> 
> I''ve just checked in a fix -- the Xen-specific acpi_map_table()
function
> was both unnecessary and broken. Hopefully latest unstable will boot on 
> your test machine.
> 
Just updated and rebuilt - still crashing.

Mike


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Keir Fraser

2005-May-17 19:49 UTC

head link

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

On 17 May 2005, at 19:23, Mike Wray wrote:
>>> OK, I did that and planted a few dump_stack() calls in the acpi
code:
>> I''ve just checked in a fix -- the Xen-specific
acpi_map_table()
>> function was both unnecessary and broken. Hopefully latest unstable 
>> will boot on your test machine.
>
> Just updated and rebuilt - still crashing.
It''s probably crashing in a different place now. Can you please send 
output from latest build, with early printk and some suitable 
dump_stack() calls inserted?

  -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Mike Wray

2005-May-19 10:42 UTC

head link

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

Keir Fraser wrote:> 
> On 17 May 2005, at 19:23, Mike Wray wrote:
> 
>>>> OK, I did that and planted a few dump_stack() calls in the acpi
code:
>>>
>>> I''ve just checked in a fix -- the Xen-specific
acpi_map_table()
>>> function was both unnecessary and broken. Hopefully latest unstable
>>> will boot on your test machine.
>>
>>
>> Just updated and rebuilt - still crashing.
> 
> 
> It''s probably crashing in a different place now. Can you please
send
> output from latest build, with early printk and some suitable 
> dump_stack() calls inserted?
> 
>  -- Keir
> 
Here''s the crash from a build at 4 p.m. yesterday.
Unfortunately it seems to have hosed my machine completely,
and since I''m remote at the moment I can''t reset it.

Mike

  Xen version 3.0-devel (mjw@hpl.hp.com) (gcc version 3.2.2 20030222 (Red Hat
Linux 3.2.2-5)) Wed
May 18 16:15:49 BST 2005
  Latest ChangeSet: 2005/05/18 16:21:32 1.1450 428b5d7cJ4XUGw6DYur-hyo9pRpNwg

(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 (10672kB)
(XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0
(XEN) CPU#0: Physical ID: 0, Logical ID: 0
(XEN) CPU caps: bfebfbff 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.083 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: bfebfbff 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:A65C8E00
(XEN) .... scale:       00000001:6EE1F293
(XEN) .... Wall Clock:  1116501824s 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->c05d0160
(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) CPU:    0
(XEN) EIP:    e019:[<c010000d>]
(XEN) EFLAGS: 00210282   CONTEXT: guest
(XEN) (file=extable.c, line=76) Pre-exception: ff105cad -> 00000000
(XEN) eax: 00000000   ebx: 00000000   ecx: 00000000   edx: 00000000
(XEN) CPU:    1
(XEN) EIP:    e008:[<ff105cad>]
(XEN) EFLAGS: 00210046   CONTEXT: hypervisor
(XEN) eax: 7e8767b7   ebx: 00000000   ecx: 7e883031   edx: 00000000
(XEN) esi: c05f4200   edi: c059b620   ebp: 00000000   esp: c05f6000
(XEN) esi: 00000002   edi: 00000080   ebp: 00000000   esp: ff19ff1c
(XEN) ds: e010   es: e010   fs: e010   gs: e010   ss: e010   cs: e008
(XEN) ds: e021   es: e021   fs: e021   gs: e021   ss: e021   cs: e019
(XEN) Xen stack trace from esp=ff19ff1c:
(XEN)    Xen stack trace from esp=ff105fe4:
(XEN)    7e8767b7 00000000 00000080 [ff114de2] ffbf9080 7e3b1c77 00000000
[ff10f72c]
(XEN)    ff169fd8 ff169fd8 ff169010 ffbf9080 7e876ce1 00000000 00000000 ffbf9d80
(XEN)    ff169010 00000001 00000000 00000001 00000080 00000080 00000001
[ff115002]
(XEN)    00000005 00000080 00000001 00000000 00ef0000 ffbf9080 00000005
[ff11efbc]
(XEN)    00102000 9b840dff 880fc04a ffbf9080 00000000 ffbf9080 00000080 00000001
(XEN)    30a3d231 31c05a34 74e0a3c0 d089c05a 00768dc3 5a3430a1 768dc3c0 27bc8d00
(XEN)    00000000 be565755 ffffe000 8353e621 44c70cec 00000824 768d0000 27bc8d00
(XEN)    ffbf9080
(XEN) Xen call trace from esp=ff19ff1c:
(XEN)    c05f6000 [<ff114de2>] 0000e021 0000e021 [<ff10f72c>]
0000e021 0000e021 0000e021
[<ff115002>] [<ff11efbc>] ff19d080
(XEN) Xen call trace from esp=ff105fe4:
(XEN)
(XEN) Trace empty.
(XEN) Faulting linear address: 7e8767b7
(XEN) ************************************
(XEN) Guest stack trace from esp=c05f6000:
(XEN)    CPU1 FATAL TRAP 14 (page fault), ERROR_CODE 0002, IN INTERRUPT CONTEXT.
(XEN) System shutting down -- need manual reset.
(XEN) ************************************

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Keir Fraser

2005-May-19 14:18 UTC

head link

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

On 19 May 2005, at 11:42, Mike Wray wrote:
> Here''s the crash from a build at 4 p.m. yesterday.
> Unfortunately it seems to have hosed my machine completely,
> and since I''m remote at the moment I can''t reset it.
XenLinux is dying very early indeed: looks like a Xen/Linux mismatch (I 
think you are using an up-to-date Xen image with an old Linux image).

  -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Mike Wray

2005-May-19 16:22 UTC

head link

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

Keir Fraser wrote:> 
> On 19 May 2005, at 11:42, Mike Wray wrote:
> 
>> Here''s the crash from a build at 4 p.m. yesterday.
>> Unfortunately it seems to have hosed my machine completely,
>> and since I''m remote at the moment I can''t reset it.
> 
> 
> XenLinux is dying very early indeed: looks like a Xen/Linux mismatch (I 
> think you are using an up-to-date Xen image with an old Linux image).
This was from ''make clean; make debug=y dist'', so that should
OK?
Anyway, will try again with ''make world'' tomorrow, when
I''ll
be able to reset the machine.

Mike

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Ian Pratt

2005-May-19 16:43 UTC

head link

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

> > XenLinux is dying very early indeed: looks like a Xen/Linux 
> mismatch 
> > (I think you are using an up-to-date Xen image with an old 
> Linux image).
> 
> This was from ''make clean; make debug=y dist'', so that
should OK?
> Anyway, will try again with ''make world'' tomorrow, when
I''ll
> be able to reset the machine.
Not necessarily, if new files have been added or removed from the sparse
tree (which they have).

Blow away old dist/install/boot/config* files as well.

Ian 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Mike Wray

2005-May-20 16:24 UTC

head link

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

Ian Pratt wrote:>>>XenLinux is dying very early indeed: looks like a Xen/Linux 
>>
>>mismatch 
>>
>>>(I think you are using an up-to-date Xen image with an old 
>>
>>Linux image).
>>
>>This was from ''make clean; make debug=y dist'', so that
should OK?
>>Anyway, will try again with ''make world'' tomorrow,
when I''ll
>>be able to reset the machine.
> 
> 
> Not necessarily, if new files have been added or removed from the sparse
> tree (which they have).
> 
> Blow away old dist/install/boot/config* files as well.
> 
I just did a bk pull and tried ''make world'' and it failed. So
I bloew away everything and cloned again, and it still fails:

gcc -Wall -O2 -g -fno-strict-aliasing -I. 
-I/home/mjw/repos-bk/xeno-unstable.bk/tools/ioemu/target-i386 
-I/home/mjw/repos-bk/xeno-unstable.bk/tools/ioemu -I../../../xen/include/public 
-I../../../tools/libxc -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-c -o helper2.o
helper2.c
In file included from helper2.c:324:
/usr/include/asm/bitops.h:327:2: warning: #warning This includefile is not
available on all
architectures.
/usr/include/asm/bitops.h:328:2: warning: #warning Using kernel headers in
userspace: atomicity not
guaranteed
rm -f libqemu.a
ar rcs libqemu.a  helper2.o
gcc  -Wl,-T,/home/mjw/repos-bk/xeno-unstable.bk/tools/ioemu/i386-vl.ld -o
qemu-dm vl.o exec.o
monitor.o osdep.o block.o readline.o pci.o console.o block-cloop.o ide.o
ne2000.o pckbd.o vga.o
dma.o fdc.o mc146818rtc.o serial.o i8259.o i8254.o pc.o sdl.o libqemu.a  -lm 
-L../../../dist/install/usr/lib -lxc -lxutil -lz -L/usr/lib -Wl,-rpath,/usr/lib
-lSDL -lpthread -lm
-ldl -L/usr/X11R6/lib -lX11 -lXext  -lutil
libqemu.a(helper2.o)(.text+0x1c): In function `modify_ldt'':
/home/mjw/repos-bk/xeno-unstable.bk/tools/ioemu/target-i386-dm/helper2.c:74:
undefined reference to
`errno''
collect2: ld returned 1 exit status
make[5]: *** [qemu-dm] Error 1
make[5]: Leaving directory
`/home/mjw/repos-bk/xeno-unstable.bk/tools/ioemu/target-i386-dm''
make[4]: *** [all] Error 1
make[4]: Leaving directory
`/home/mjw/repos-bk/xeno-unstable.bk/tools/ioemu''
make[3]: *** [ioemuinstall] Error 2
make[3]: Leaving directory `/home/mjw/repos-bk/xeno-unstable.bk/tools''
make[2]: *** [install] Error 2
make[2]: Leaving directory `/home/mjw/repos-bk/xeno-unstable.bk/tools''
make[1]: *** [tools] Error 2
make[1]: Leaving directory `/home/mjw/repos-bk/xeno-unstable.bk''
make: *** [world] Error 2

Mike


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Nakajima, Jun

2005-May-20 16:58 UTC

head link

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

Mike Wray wrote:> Ian Pratt wrote:
>>>> XenLinux is dying very early indeed: looks like a Xen/Linux
>>> 
>>> mismatch
>>> 
>>>> (I think you are using an up-to-date Xen image with an old
>>> 
>>> Linux image).
>>> 
>>> This was from ''make clean; make debug=y dist'', so
that should OK?
>>> Anyway, will try again with ''make world''
tomorrow, when I''ll
>>> be able to reset the machine.
>> 
>> 
>> Not necessarily, if new files have been added or removed from the
>> sparse tree (which they have). 
>> 
>> Blow away old dist/install/boot/config* files as well.
>> 
> 
> I just did a bk pull and tried ''make world'' and it
failed. So
> I bloew away everything and cloned again, and it still fails:
> 
I think the priority now is to test xen and dom0 xenlinux that have
Keir''s fix. We had a problem with booting yesterday.

I typically do:

1. "make kernels"
2. Kill it in 10 sec. when it starts building dom0 linux
3. cd linux-2.6.11-xen0
4. "ARCH=xen make -j<N> vmlinuz" and copy vmlinuz to the target
machine
5. cd xen
6. "make" (or "make debug=y"), and copy xen.gz to the target
machine

Jun

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Anthony Liguori

2005-May-20 17:16 UTC

head link

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

Mike Wray wrote:
> I just did a bk pull and tried ''make world'' and it
failed. So
> I bloew away everything and cloned again, and it still fails:
See bug #52  Apparently, it doesn''t happen on all Linux distros...

Regards,

Anthony Liguori

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Christian Limpach

2005-May-20 21:42 UTC

head link

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

On 5/20/05, Nakajima, Jun <jun.nakajima@intel.com>
wrote:> I typically do:
> 
> 1. "make kernels"
> 2. Kill it in 10 sec. when it starts building dom0 linux
> 3. cd linux-2.6.11-xen0
> 4. "ARCH=xen make -j<N> vmlinuz" and copy vmlinuz to the
target machine
> 5. cd xen
> 6. "make" (or "make debug=y"), and copy xen.gz to the
target machine
You might want to give these slightly simpler alternatives a try:
- build xen:
make xen -j<N>
- build dom0 kernel:
make linux-2.6-xen0-build -j<N>

To make sure you start from scratch:
- xen:
make -C xen clean
- linux:
remove dist/install/boot/config*xen0 and linux-2.6.11-xen0

    christian

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Xen devel - May 2005 - Xeno-unstable crashing at boot

[Xen-devel] Xeno-unstable crashing at boot

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Xen-devel] memory mapping

Re: [Xen-devel] memory mapping

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

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

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

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

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

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

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

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

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

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