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

["Tian, Kevin" <kevin.tian@xxxxxxxxx>]

Hi, Alex,
        Do you check whether xen_ia64_dom0_virtual_physical is set in 
xen? I found that flag disabled by default. Just now I saw a similar error 
as yours by enable vp mode in xenlinux, but forgot to turn on 
xen_ia64_dom0_virtual_physical in xen. Though I forgot to capture the 
output, the final screen is a xenlinux stack dump in iosapic_guest_write 
and then machine_restart(in Xen) is hit.

        I'll try recompilation and test again.

Thanks,
Kevin

>-----Original Message-----
>From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
>Tian, Kevin
>Sent: 2006年5月11日 9:58
>To: Alex Williamson; Isaku Yamahata
>Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: RE: [PATCH] compilation fix of ia64 hypervisor.c,utils.c (was
>Re:[Xen-ia64-devel] latest tree building fail.)
>
>>From: Alex Williamson
>>Sent: 2006年5月11日 0:23
>>
>>> - 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
>>
>
>I met a similar error when debugging patch for moving iosapic
>previously:
>ACPI: Error parsing MADT - no IOSAPIC entries
>
>The reason at that time was because xen and xenlinux had different
>NR_IOSAPICS definition. Xenlinux defaulted to 256 while xen limited to
>4.
>On my tiger4 box, there's 6 IOSAPICS however. Then xen only initialized
>4 IOSAPIC related structures, while xenlinux saw all 6 IOSAPICs. Finally
>when xenlinux operated 5th IOSAPIC, MCA happens. However the
>difference is, MCA occurred to me at MPT SCSI controller initialization,
>instead of immediately after above ACPI error message.
>
>Since above error has been solved, yours should be a bit different which
>may relate to bogus mapping. How can people reproduce your error? Or
>maybe debug can be postponed if current dom0 on VP is not full ready?
>
>Thanks,
>Kevin
>
>_______________________________________________
>Xen-ia64-devel mailing list
>Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-ia64-devel

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