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 10:22 -0600, Alex Williamson wrote:

>    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,

   Quick update.  Still some user error on my part here.  I was trying
to boot a p2m/vp kernel w/ a non-p2m/vp xen.  The failure was because
the ioremap was returning -ENOSYS, which we happily tried to use as the
ioremapped address.  I think we need some error checking in that path.
The domain should probably panic if such fundamental hypercalls are
unavailable.  Unfortunately when I enable p2m/vp in xen, I don't even
get to the point of starting to boot dom0.  I seem to be taking an MCA
from some stray reference to 0xA0000 around the calls to
dom_fw_dom0_passthrough().  I haven't yet narrowed down exactly where
that's coming from.  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