WARNING - OLD ARCHIVES

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

xen-devel

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

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

from [Mike Wray] [Permanent Link][Original]
To: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Xeno-unstable crashing at boot
From: Mike Wray <mike.wray@xxxxxx>
Date: Tue, 17 May 2005 10:19:30 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 17 May 2005 09:29:27 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D1E405C@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D1E405C@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2 (X11/20050317) 
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@xxxxxxxxxx) (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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: FW: [Xen-devel] Creating domain crashes xend with the latest xenunstable tree, Mike Wray
Next by Date:  Re: [Xen-devel] Re: Install paravirtualized drivers after bootingforhigh-performance IO, Mark Williamson
Previous by Thread:  RE: [Xen-devel] Xeno-unstable crashing at boot, Ian Pratt
Next by Thread:  Re: [Xen-devel] Xeno-unstable crashing at boot, Christian Limpach
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

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