| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Re: [Xen-users] 3.0.4 Early fatal page fault
I have seen the same thing. The output from a debug build of Xen is:
l210-3_4-20050802)) Mon Feb 5 06:44:14 PST 2007 is highlighted.
Latest ChangeSet: Mon Feb 05 06:40:50 2007 -0800 13177:14c648dc16ef
commands before booting, or 'c' for a command-line.
(XEN) Command line: /boot/amd64/xen.gz dom0_mem=1524288 console=com1
com1=9600,8n1
(XEN) Physical RAM map:
(XEN) 0000000000000000 - 000000000009ac00 (usable)
(XEN) 000000000009ac00 - 00000000000a0000 (reserved)
(XEN) 00000000000e0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000f9ff0000 (usable)
(XEN) 00000000f9ff0000 - 00000000f9ffe000 (ACPI data)
(XEN) 00000000f9ffe000 - 00000000fa000000 (ACPI NVS)
(XEN) 00000000ff700000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000000400000000 (usable)
(XEN) System RAM: 16287MB (16678440kB)
(XEN) ACPI: RSDP (v002 SUN ) @
0x00000000000f6fb0
(XEN) ACPI: XSDT (v001 SUN X4500 0x00000015 MSFT 0x00000097) @
0x00000000f9ff0100
(XEN) ACPI: FADT (v003 SUN X4500 0x00000015 MSFT 0x00000097) @
0x00000000f9ff0290
(XEN) ACPI: MADT (v001 SUN X4500 0x00000015 MSFT 0x00000097) @
0x00000000f9ff0390
(XEN) ACPI: SLIT (v001 SUN X4500 0x00000015 MSFT 0x00000097) @
0x00000000f9ff04c0
(XEN) ACPI: SPCR (v001 SUN X4500 0x00000015 MSFT 0x00000097) @
0x00000000f9ff0470
(XEN) ACPI: OEMB (v001 SUN X4500 0x00000015 MSFT 0x00000097) @
0x00000000f9ffe040
(XEN) ACPI: SRAT (v001 SUN X4500 0x00000015 MSFT 0x00000097) @
0x00000000f9ff4a80
(XEN) ACPI: DSDT (v001 SUN X4500 0x00000015 INTL 0x02002026) @
0x0000000000000000
(XEN) Early fatal page fault at 1f3928:ffff830000124724
(cr2=ffff8300f9ff04e4, ec=0000)
(XEN) BUG at /export/xen-clone/xen.hg/xen/include/asm/spinlock.h:37
(XEN) Unknown interrupt
That corresponds to the first ASSERT() below:
static inline void _raw_spin_unlock(spinlock_t *lock)
{
#if !defined(CONFIG_X86_OOSTORE)
ASSERT(spin_is_locked(lock));
__asm__ __volatile__ (
"movb $1,%0"
: "=m" (lock->lock) : : "memory" );
#else
char oldval = 1;
ASSERT(spin_is_locked(lock));
__asm__ __volatile__ (
"xchgb %b0, %1"
: "=q" (oldval), "=m" (lock->lock) : "0" (oldval) : "memory" );
#endif
}
Adding acpi=off to the xen command line seems to work here as well.
John Hannfield wrote:
Hello,
I'm trying to install Xen on a dual Opteron (dual core) system. It
runs fine on a Fedora or Ubuntu kernel, but neither the xen binary
install or source install will boot. It seems to be a problem with
ACPI or APIC. Here is my console bootlog:
* Ubuntu, kernel 2.6.15-26-amd64-server
* [01;00H
[02;00H kernel /boot/xen-3.0.gz
com1=115200,8n1 console=vga,com1 [03;00H
[Multiboot-elf, <0x100000:0x9e898:0x5a768>, shtab=0x1f9078,
entry=0x100000] [04;00H module /boot/vmlinuz-2.6.16.33-xen_test6
root=/dev/sda1 ro console=tty0 console [05;00H =ttyS0
[06;00H
[07;00H __ __
_____ ___ _ _ _
\ \/ /___ _ __ |___ / / _ \| || | / |
\ // _ \ '_ \ |_ \| | | | || |_ __| |
/ \ __/ | | | ___) | |_| |__ _|__| |
/_/\_\___|_| |_| |____(_)___(_) |_| |_|
http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer Laboratory
Xen version 3.0.4-1 (root@) (gcc version 4.0.3 (Ubuntu
4.0.3-1ubuntu5)) Fri Feb 16 15:30:33 GMT 2007
Latest ChangeSet: unavailable
(XEN) Command line: /boot/xen-3.0.gz com1=115200,8n1 console=vga,com1
(XEN) Physical RAM map:
(XEN) 0000000000000000 - 000000000009dc00 (usable)
(XEN) 000000000009dc00 - 00000000000a0000 (reserved)
(XEN) 00000000000e0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 000000007fff0000 (usable)
(XEN) 000000007fff0000 - 000000007fffe000 (ACPI data)
(XEN) 000000007fffe000 - 0000000080000000 (ACPI NVS)
(XEN) 00000000e0000000 - 00000000f0000000 (reserved)
(XEN) 00000000fec00000 - 00000000fec01000 (reserved)
(XEN) 00000000fee00000 - 00000000fef00000 (reserved)
(XEN) 00000000ff700000 - 0000000100000000 (reserved)
(XEN) System RAM: 2047MB (2096692kB)
(XEN) ACPI: RSDP (v002 ACPIAM ) @
0x00000000000f9480
(XEN) ACPI: XSDT (v001 A M I OEMXSDT 0x12000614 MSFT 0x00000097) @
0x000000007fff0100
(XEN) ACPI: FADT (v003 A M I OEMFACP 0x12000614 MSFT 0x00000097) @
0x000000007fff0290
(XEN) ACPI: MADT (v001 A M I OEMAPIC 0x12000614 MSFT 0x00000097) @
0x000000007fff0390
(XEN) ACPI: SPCR (v001 A M I OEMSPCR 0x12000614 MSFT 0x00000097) @
0x000000007fff0410
(XEN) ACPI: SLIT (v001 A M I OEMSLIT 0x12000614 MSFT 0x00000097) @
0x000000007fff04a0
(XEN) ACPI: OEMB (v001 A M I AMI_OEM 0x12000614 MSFT 0x00000097) @
0x000000007fffe040
(XEN) ACPI: HPET (v001 A M I OEMHPET0 0x12000614 MSFT 0x00000097) @
0x000000007fff54d0
(XEN) ACPI: SRAT (v001 AMD HAMMER 0x00000001 AMD 0x00000001) @
0x000000007fff5510
(XEN) ACPI: SSDT (v001 A M I POWERNOW 0x00000001 AMD 0x00000001) @
0x000000007fff5600
(XEN) ACPI: DSDT (v001 DATER DATER111 0x00000111 INTL 0x20051117) @
0x0000000000000000
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Early fatal page fault at e010:ffff830000170890
(cr2=ffff83007fff04c4, ec=0000)
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...
(XEN) Unknown interrupt
I have tried adding acpi=off or acpi=noirq to the xen command
line, but it doesn't
seem to make any difference. Does this look like an ACPI error, or
could it be APIC?
Any ideas how to troubleshoot it further?
Thanks,
--
-----------------------------------------------------
Russ Blaine | Solaris Kernel | russell.blaine@xxxxxxx
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home