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

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

Have to say it's bad news. When I turned on 
xen_ia64_dom0_virtual_physical in xen, it halts even before starting 
dom0. Based on tip (Rev 9992). Maybe we should try this feature later 
when all patch sets are checked in. :-(

Thanks,
Kevin

(XEN) assign_domain_page: mpaddr 7ff80000 already mapped!

(XEN) assign_domain_page: mpaddr 7ff84000 already mapped!

(XEN) ia64_fault, vector=0x0000000000000004, ifa=f3ffffffffd00000, 
iip=f00000000404b580, ipsr=0000101008622030, isr=0000080200000000

(XEN) Alt ITLB.

(XEN) d 0xf000000007ff8018 domid 32767

(XEN) vcpu 0xf0000000040c4000 vcpu 0

(XEN) 

(XEN) CPU 0

(XEN) psr : 0000101008622030 ifs : 8000000000000308 ip  : [<f00000000404b580>]

(XEN) ip is at assign_domain_page+0xd0/0x120

(XEN) unat: 0000000000000000 pfs : 0000000000000309 rsc : 0000000000000003

(XEN) rnat: effffffff1000000 bsps: 000000000000fffe pr  : 10a0808800c51a9b

(XEN) ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c8a70433f

(XEN) csd : 0930ffff00090000 ssd : 0930ffff00090000

(XEN) b0  : f00000000404bb40 b6  : f000000004044010 b7  : f00000007fb1c7a0

(XEN) f6  : 0fffafffffffff0000000 f7  : 0ffdde000000000000000

(XEN) f8  : 10001e000000000000000 f9  : 100038000000000000000

(XEN) f10 : 0fffddffffffff2000000 f11 : 1003e0000000000000000

(XEN) r1  : f000000004302a90 r2  : 000000007ffb8000 r3  : f000000004164000

(XEN) r8  : 0000000000000000 r9  : f000000004164020 r10 : f000000004164030

(XEN) r11 : f000000004164040 r12 : f0000000040cbcb0 r13 : f0000000040c4000

(XEN) r14 : f3ffffffffd00000 r15 : 001000007ffb4761 r16 : 0000000000000000

(XEN) r17 : 000000000001ffed r18 : ffffffffffffe551 r19 : f000000004104f10

(XEN) r20 : 0000000000000001 r21 : f00000000410bf10 r22 : ffffc0000000001f

(XEN) r23 : 0000000000000053 r24 : 0000000000000053 r25 : 0000000000000054

(XEN) r26 : 000000000000005f r27 : 0000000000000000 r28 : 0000000000000000

(XEN) r29 : 0000000000000000 r30 : 0000000000000000 r31 : f000000004113aa0

(XEN) 

(XEN) Call Trace:

(XEN)  [<f00000000408a100>] show_stack+0x80/0xa0

(XEN)                                 sp=f0000000040cb860 bsp=f0000000040c51e0

(XEN)  [<f000000004060f70>] ia64_fault+0x290/0x680

(XEN)                                 sp=f0000000040cba30 bsp=f0000000040c51a8

(XEN)  [<f000000004088da0>] ia64_leave_kernel+0x0/0x310

(XEN)                                 sp=f0000000040cbab0 bsp=f0000000040c51a8

(XEN)  [<f00000000404b580>] assign_domain_page+0xd0/0x120

(XEN)                                 sp=f0000000040cbcb0 bsp=f0000000040c5168

(XEN)  [<f00000000404bb40>] assign_domain_same_page+0x60/0xa0

(XEN)                                 sp=f0000000040cbcb0 bsp=f0000000040c5138

(XEN)  [<f00000000404bc00>] assign_domain_mach_page+0x30/0x50

(XEN)                                 sp=f0000000040cbcc0 bsp=f0000000040c5108

(XEN)  [<f000000004051e70>] dom_fw_dom0_passthrough+0x2b0/0x2c0

(XEN)                                 sp=f0000000040cbcc0 bsp=f0000000040c50c8

(XEN)  [<f000000004087ba0>] efi_memmap_walk_type+0xc0/0xf0

(XEN)                                 sp=f0000000040cbcc0 bsp=f0000000040c5080

(XEN)  [<f000000004054080>] dom_fw_setup+0x21c0/0x2ae0

(XEN)                                 sp=f0000000040cbcc0 bsp=f0000000040c4ec0

(XEN)  [<f00000000404a8f0>] new_thread+0x2e0/0x4a0

(XEN)                                 sp=f0000000040cbd00 bsp=f0000000040c4e70

(XEN)  [<f00000000404df40>] construct_dom0+0x8a0/0x1000

(XEN)                                 sp=f0000000040cbd00 bsp=f0000000040c4d80

(XEN)  [<f00000000406d2d0>] start_kernel+0xf10/0x1180

(XEN)                                 sp=f0000000040cbde0 bsp=f0000000040c4d28

(XEN)  [<f00000000401a0a0>] _start+0x340/0x360

(XEN)                                 sp=f0000000040cbe00 bsp=f0000000040c4cc0

(XEN) 

(XEN) ****************************************

(XEN) Panic o

>-----Original Message-----
>From: Tian, Kevin
>Sent: 2006年5月11日 10:23
>To: Tian, Kevin; 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.)
>
>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