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: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Xeno-unstable crashing at boot
From: Mike Wray <mike.wray@xxxxxx>
Date: Thu, 19 May 2005 11:42:47 +0100
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Christian.Limpach@xxxxxxxxxxxx
Delivery-date: Thu, 19 May 2005 10:53:18 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <8645c8f4b59294d599ce36c062add45a@xxxxxxxxxxxx>
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> <4289B722.6090205@xxxxxx> <3d8eece205051703296725f8f5@xxxxxxxxxxxxxx> <4289DB07.9010204@xxxxxx> <4d971950d2aa365b19698ccae800a504@xxxxxxxxxxxx> <428A3684.9050508@xxxxxx> <8645c8f4b59294d599ce36c062add45a@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2 (X11/20050317) 
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@xxxxxxxxxx) (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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: [Xen-devel] HT Vulnerability CAN-2005-0109, Nils Toedtmann
Next by Date:  RE: [Xen-devel] HT Vulnerability CAN-2005-0109, Ian Pratt
Previous by Thread:  Re: [Xen-devel] Xeno-unstable crashing at boot, Keir Fraser
Next by Thread:  Re: [Xen-devel] Xeno-unstable crashing at boot, Keir Fraser
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

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