Re: [PATCH] compilation fix of ia64 hypervisor.c, utils.c (was Re: [Xen-ia64-devel] latest tree building fail.)

[Alex Williamson <alex.williamson@xxxxxx>]

On Wed, 2006-05-10 at 14:41 +0900, Isaku Yamahata wrote:
> On Tue, May 09, 2006 at 03:11:09PM -0600, Alex Williamson wrote:

> > (XEN) ACPI: Local APIC address ffffffffffffffda
> > ACPI: [APIC:0x07] ignored 4 entries of 8 found
> > ACPI: Error parsing MADT - no IOSAPIC entries
> > 
> > I don't know if this matters at this point since the recommendation is
> > currently XEN_IA64_DOM0_VP=n.  With that, everything builds and works
> > with no obvious regressions.  Thanks,
> 
> It matters.
> Dom0 should boot with XEN_IA64_DOM0_VP=y at least.
> I tried the changeset 9984:e2fba6729281 of xen-ia64-unstable.hg
> with with XEN_IA64_DOM0_VP=y.
> I could boot dom0  and 1 domU.
> (Multiple domU might have problems. I'm debugging it now)
> 
> - Did you pass nosmp boot parameter to xen?

   I did not, but unfortunately fixing that mistake still doesn't make
it boot.  I also added a max_addr=1G, but that didn't help either.

> - Does xen reboot after the above messages or just be silent?
>   It seems that something occurs somewhere in acpi_boot_init() of
>   linux/arch/ia64/kernel/acpi.c.
>   Could you track it down more?

   It MCAs at this point.  The error record indicates a bus error w/
target ID 0x0000001804108804.  The chipset reports a response timeout
with this same address.  The bad memory reference seems to have come
from iosapic_guest_write(), but as indicated by the bad lapic address
above, the problem appears to have started earlier.  I'll investigate
further.  Thanks,

        Alex

-- 
Alex Williamson                             HP Linux & Open Source Lab


_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel