Jacob Gorm Hansen
2005-May-20 02:48 UTC
[Xen-devel] dom0 / xen crash with latest unstable tarball
Please see boot log below, this is on a 3.2GHz P4 with Hyperthtreading,
but enabled and disabled (''noht''):
Jacob
__ __ _____ ___ _ _
\ \/ /___ _ __ |___ / / _ \ __| | _____ _____| |
\ // _ \ ''_ \ |_ \| | | |__ / _` |/ _ \ \ / / _ \ |
/ \ __/ | | | ___) | |_| |__| (_| | __/\ V / __/ |
/_/\_\___|_| |_| |____(_)___/ \__,_|\___| \_/ \___|_|
http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer Laboratory
Xen version 3.0-devel (jacobg@(none)) (gcc version 3.3.4 20040623
(Gentoo Linux
3.3.4-r1, ssp-3.3.2-2, pie-8.7.6)) Thu May 19 19:19:10 PDT 2005
Latest ChangeSet: information unavailable
(XEN) Physical RAM map:
(XEN) 0000000000000000 - 00000000000a0000 (usable)
(XEN) 00000000000f0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 000000003ff74000 (usable)
(XEN) 000000003ff74000 - 000000003ff76000 (ACPI NVS)
(XEN) 000000003ff76000 - 000000003ff97000 (ACPI data)
(XEN) 000000003ff97000 - 0000000040000000 (reserved)
(XEN) 00000000fec00000 - 00000000fec10000 (reserved)
(XEN) 00000000fecf0000 - 00000000fecf1000 (reserved)
(XEN) 00000000fed20000 - 00000000fed90000 (reserved)
(XEN) 00000000fee00000 - 00000000fee10000 (reserved)
(XEN) 00000000ffb00000 - 0000000100000000 (reserved)
(XEN) System RAM: 1023MB (1047632kB)
(XEN) Xen heap: 10MB (10712kB)
(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 000fe710
(XEN) ACPI: RSDP (v000 DELL ) @ 0x000feb90
(XEN) ACPI: RSDT (v001 DELL WS 360 0x00000007 ASL 0x00000061) @
0x000fd160
(XEN) ACPI: FADT (v001 DELL WS 360 0x00000007 ASL 0x00000061) @
0x000fd198
(XEN) ACPI: SSDT (v001 DELL st_ex 0x00001000 MSFT 0x0100000d) @
0xfffc8775
(XEN) ACPI: MADT (v001 DELL WS 360 0x00000007 ASL 0x00000061) @
0x000fd20c
(XEN) ACPI: BOOT (v001 DELL WS 360 0x00000007 ASL 0x00000061) @
0x000fd278
(XEN) ACPI: ASF! (v016 DELL WS 360 0x00000007 ASL 0x00000061) @
0x000fd2a0
(XEN) ACPI: DSDT (v001 DELL dt_ex 0x00001000 MSFT 0x0100000d) @
0x00000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 15:3 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 15:3 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] disabled)
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 2, 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 3192.147 MHz processor.
(XEN) CPU0 booted
(XEN) Error: only one processor found.
(XEN) ENABLING IO-APIC IRQs
(XEN) ..TIMER: vector=0x31 pin1=2 pin2=-1
(XEN) Time init:
(XEN) .... cpu_freq: 00000000:BE444EE0
(XEN) .... scale: 00000001:40C9838D
(XEN) .... Wall Clock: 1116557016s 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_BASE0xC0000000,LOADER=generic''
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 10000000->20000000
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: c0100000->c05b4744
(XEN) Init. ramdisk: c05b5000->c05b5000
(XEN) Phys-Mach map: c05b5000->c05f5000
(XEN) Page tables: c05f5000->c05f8000
(XEN) Start info: c05f8000->c05f9000
(XEN) Boot stack: c05f9000->c05fa000
(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) (file=extable.c, line=76) Pre-exception: ff105d00 -> 00000000
(XEN) CPU: 0
(XEN) EIP: e008:[<ff105d00>]
(XEN) EFLAGS: 00210046 CONTEXT: hypervisor
(XEN) eax: 28881b52 ebx: 00000000 ecx: 28c1245d edx: 00000000
(XEN) esi: 00000002 edi: cc800000 ebp: 00000000 esp: ff105f34
(XEN) ds: e010 es: e010 fs: e010 gs: e010 ss: e010 cs: e008
(XEN) Xen stack trace from esp=ff105f34:
(XEN) c05f78a8 ff15c9c8 00000004 ff18c800 80000005 80000004 00000000
[ff105fb
4]
(XEN) ff18ca00 36020001 105f7021 [ff105fb4] 28c0610d 00000000
00000000 ff18c4
80
(XEN) ff167fc0 00000000 [ff137747] 00000001 00000000 cc800000
0000c800 [ff115
112]
(XEN) 00000000 fec6d001 ffbfb080 ffbfb080 00007ff0 ffbfb080 00007ff0
[ff142a4
6]
(XEN) c051deec 80000001 00000000 00007ff0 cc800000 0000c800 00000001
000e0003
(XEN) c0116e38 0000e019 00200246 c051deec 0000e021 0000e021 0000e021
00000000
(XEN) 00000000 00000000 ffbfb080
(XEN) Xen call trace from esp=ff105f34:
(XEN) [<ff105fb4>] [<ff105fb4>] [<ff137747>]
[<ff115112>] [<ff142a46>]
(XEN) Faulting linear address: 28881b52
(XEN) ************************************
(XEN) CPU0 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-20 07:58 UTC
Re: [Xen-devel] dom0 / xen crash with latest unstable tarball
On 20 May 2005, at 03:48, Jacob Gorm Hansen wrote:> Please see boot log below, this is on a 3.2GHz P4 with > Hyperthtreading, but enabled and disabled (''noht''):The tarball lags behind the repository -- I fixed this problem (a stack alignment bug) already. Anyone else who was seeing crashes early during boot: please re-test and confirm the bug is gone. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jacob Gorm Hansen
2005-May-20 21:44 UTC
Re: [Xen-devel] dom0 / xen crash with latest unstable tarball
Keir Fraser wrote:> The tarball lags behind the repository -- I fixed this problem (a stack > alignment bug) already. > > Anyone else who was seeing crashes early during boot: please re-test and > confirm the bug is gone.I can confirm that with the latest tarball the problem is fixed. thanks, Jacob _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel