|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] Crash while loading dom0
Ray,
I saw the same problem on x86_64 the last time I was able to build it
and attempted to boot it. There is a bug defect,
http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=26
, written for this issue. Yes, it is a result of acpi issues (refer to
defect).
On Wed, 2005-05-11 at 10:34 -0400, Ray Lanza wrote:
> I'm trying to get unstable running on a dual opteron system. Xen is crashing
> while dom0 is initializing. Is this a result of acpi issues? Is there a
> workaround? I've tried passing acpi=off but without any luck.
>
> thanks,
> ray
>
>
>
> \ \/ /___ _ __ |___ / / _ \ __| | _____ _____| |
> \ // _ \ '_ \ |_ \| | | |__ / _` |/ _ \ \ / / _ \ |
> / \ __/ | | | ___) | |_| |__| (_| | __/\ V / __/ |
> /_/\_\___|_| |_| |____(_)___/ \__,_|\___| \_/ \___|_|
>
> http://www.cl.cam.ac.uk/netos/xen
> University of Cambridge Computer Laboratory
>
> Xen version 3.0-devel (rjl@xxxxxxxxxx) (gcc version 3.3.6 (Debian
> 1:3.3.6-4)) Wed May 11 10:16:08 EDT 2005
> Latest ChangeSet: information unavailable
>
> (XEN) Physical RAM map:
> (XEN) 0000000000000000 - 000000000009f000 (usable)
> (XEN) 000000000009f000 - 00000000000a0000 (reserved)
> (XEN) 00000000000e8000 - 0000000000100000 (reserved)
> (XEN) 0000000000100000 - 000000007fff9700 (usable)
> (XEN) 000000007fff9700 - 0000000080000000 (reserved)
> (XEN) 00000000fec00000 - 0000000100000000 (reserved)
> (XEN) 0000000100000000 - 0000000480000000 (usable)
> (XEN) System RAM: 16383MB (16776800kB)
> (XEN) Xen heap: 14MB (14336kB)
> (XEN) CPU0: Before vendor init, caps: 078bfbff e3d3fbff 00000000, vendor = 2
> (XEN) CPU caps: 078bfbff e3d3fbff 00000000 00000000
> (XEN) found SMP MP-table at 000fef70
> (XEN) ACPI: RSDP (v002 HP ) @
> 0x00000000000e8210
> (XEN) ACPI: XSDT (v001 HP CPQ0062 0x20050201 0x00000000) @
> 0x000000007fff97ec
> (XEN) ACPI: FADT (v003 HP VIPER 0x00000001 0x00000000) @
> 0x000000007fff99ac
> (XEN) ACPI: SSDT (v001 HP PROJECT 0x00000001 MSFT 0x0100000e) @
> 0x000000007fffad8b
> (XEN) ACPI: MADT (v001 HP VIPER 0x00000001 0x00000000) @
> 0x000000007fff9ab8
> (XEN) ACPI: MCFG (v001 HP VIPER 0x00000001 0x00000000) @
> 0x000000007fff9b56
> (XEN) ACPI: DSDT (v001 HP DSDT 0x00000001 MSFT 0x0100000e) @
> 0x0000000000000000
> (XEN) ACPI: Local APIC address 0xfee00000
> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
> (XEN) Processor #0 15:5 APIC version 16
> (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
> (XEN) Processor #1 15:5 APIC version 16
> (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] 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) Using ACPI for processor (LAPIC) configuration information
> (XEN) Intel MultiProcessor Specification v1.4
> (XEN) Virtual Wire compatibility mode.
> (XEN) OEM ID: HP Product ID: workstation APIC at: 0xFEE00000
> (XEN) I/O APIC #8 Version 17 at 0xFEC00000.
> (XEN) I/O APIC #9 Version 17 at 0xF2600000.
> (XEN) I/O APIC #10 Version 17 at 0xF2601000.
> (XEN) I/O APIC #11 Version 17 at 0xF2700000.
> (XEN) Enabling APIC mode: Flat. Using 7 I/O APICs
> (XEN) Processors: 2
> (XEN) WARNING: bogus zero IO-APIC address found in MPTABLE, disabling
> IO/APIC support!
> (XEN) Using scheduler: Borrowed Virtual Time (bvt)
> (XEN) Initializing CPU#0
> (XEN) Detected 2593.143 MHz processor.
> (XEN) CPU0 booted
> (XEN) SMP motherboard not detected.
> (XEN) enabled ExtINT on CPU#0
> (XEN) Using local APIC timer interrupts.
> (XEN) Calibrating APIC timer for CPU0...
> (XEN) ..... CPU clock speed is 2593.1283 MHz.
> (XEN) ..... host bus clock speed is 199.4714 MHz.
> (XEN) ..... bus_scale = 0x0000CC44
> (XEN) Time init:
> (XEN) .... cpu_freq: 00000000:9A903900
> (XEN) .... scale: 00000001:8AE338F4
> (XEN) .... Wall Clock: 1115807416s 50000us
> (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=0xffffffff80100000,LOADE
> R=generic'
> (XEN) PHYSICAL MEMORY ARRANGEMENT:
> (XEN) Dom0 alloc.: 0000000010000000->0000000020000000 (62482 pages to be
> allocated)
> (XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN) Loaded kernel: ffffffff80100000->ffffffff80538085
> (XEN) Init. ramdisk: ffffffff80539000->ffffffff80539000
> (XEN) Phys-Mach map: ffffffff80539000->ffffffff805b6048
> (XEN) Page tables: ffffffff805b7000->ffffffff805be000
> (XEN) Start info: ffffffff805be000->ffffffff805bf000
> (XEN) Boot stack: ffffffff805bf000->ffffffff805c0000
> (XEN) TOTAL: ffffffff80000000->ffffffff80800000
> (XEN) ENTRY ADDRESS: ffffffff80100000
> (XEN) Scrubbing Free RAM:
> ............................................................................
> ............................................................................
> .................................done.
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to
> Xen).
> Xen: 0000000000000000 - 000000001f412000 (usable)
> kernel direct mapping tables upto ffff88001f412000 @ 5be000-6bb000
> Linux version 2.6.11-xen0 (rjl@fossil) (gcc version 3.3.6 (Debian
> 1:3.3.6-4)) #1 Wed May 11 10:21:00 EDT 2005
> Registering memory for bootmem: from 800000, size = 1ec12000
> Built 1 zonelists
> Kernel command line: root=/dev/sda1 ro console=ttyS0 acpi=off
> Initializing CPU#0
> PID hash table entries: 2048 (order: 11, 65536 bytes)
> Xen reported: 2593.143 MHz processor.
> Using tsc for high-res timesource
> Console: colour VGA+ 80x25
> Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
> Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
> (XEN) BUG at domain.c:125
> (XEN) CPU: 0
> (XEN) EIP: 0810:[<ffff830000107d91>]
> (XEN) EFLAGS: 00000000000d1296
> (XEN) rax: 0000000000000000 rbx: ffff830000ff0c00 rcx: 0000000000000000
> rdx: 0000000000000000
> (XEN) rsi: 000000000000000a rdi: ffff83000015a3f4 rbp: ffff880001063c00
> rsp: ffff830000105ef8
> (XEN) r8: 00000000000011fa r9: ffff8300000b8f00 r10: ffff8300000b8000
> r11: 0000000000000018
> (XEN) r12: 0000000000000006 r13: 0000000000000000 r14: 0000000000001c80
> r15: ffffffff804826a0
> (XEN) Stack trace from RSP=ffff830000105ef8:
> (XEN) [ffff830000107e80] ffff830000fec080 ffff880001063c00
> [ffff830000107e89] 0000000000000000 [ffff830000135686] ffffffff804826a0
> 0000000000001c80
> (XEN) 0000000000000000 0000000000000006 ffff880001063c00
> 0000000000000246 ffffffff804d1f20 ffff880001000000 0000000000000000
> ffff8800010646f0
> (XEN) 0000000000000032 0000000000000833 0000000000000006
> ffff880001063c00 000000ef00000000 0000000100000000 0000000000000833
> 0000000000000830
> (XEN) 00000000000c1f02 000000000000082b 000000000000082b
> 000000000000082b 0000000000000000 0000000000000000 0000000000000000
> 0000000000000000
> (XEN) ffff830000fec080
> (XEN) Call Trace from RSP=ffff830000105ef8:
> (XEN) [<ffff830000107e80>] [<ffff830000107e89>] [<ffff830000135686>]
>
> ****************************************
> CPU0 FATAL TRAP: vector = 6 (invalid operand)
> [error_code=0000]
> Aieee! CPU0 is toast...
> ****************************************
>
> Reboot in five seconds...
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|