[Xen-devel] Data Abort while in booting when using Julien's new patches on Arndale Board

[Gihun Jung <gihun.jung@xxxxxxxxx>]

Hello,

I am trying to boot Arndale board with Julien's new XenARM patch series.
But I have got "Data Abort" while in booting.

My environment is:
     - Arndale Board
     - Xen-4.3-unstable from branch "arm" in
git://xenbits.xen.org/people/julieng/xen-unstable.git
     - Dom0 Kernel from branch "dev-arndale-dom0-3.9" in
git://xenbits.xen.org/people/julieng/linux-arm.git

I have found the causing "Data Abort" code while I am some debugging.

static int exynos5_specific_mapping(struct domain *d)
{

    ....snip....
    p2m_populate_ram(d, 0x0, 0x1000 - 1);

    res = gvirt_to_maddr(0, &ma);
    ...snip....
}

>From above code, "gvirt_to_maddr" calls "gva_to_ma_par":

static inline uint64_t gva_to_ma_par(vaddr_t va)
{
    uint64_t par, tmp;
    tmp = READ_CP64(PAR);
    WRITE_CP32(va, ATS12NSOPR);
    isb(); /* Ensure result is available. */
    par = READ_CP64(PAR);
    WRITE_CP64(tmp, PAR);
    return par;
}


When I have tired to debugging, I have found " WRITE_CP32(va,
ATS12NSOPR)[1]" that cause data abort. It seems [1] translates stage 1
and 2 MMU and returns PA corresponding input va.

Does anybody see same problem? I attach my log below:

=== log ===
(XEN) /voltage-regulator nirq = 0 naddr = 0
(XEN) handle /fixedregulator@0
(XEN) /fixedregulator@0 nirq = 0 naddr = 0
(XEN) CPU0: Unexpected Trap: Data Abort
(XEN) ----[ Xen-4.3-unstable  arm32  debug=y  Tainted:    C ]----
(XEN) CPU:    0
(XEN) PC:     0024d78c exynos5_specific_mapping+0x30/0xf4
(XEN) CPSR:   2000015a MODE:Hypervisor
(XEN)      R0: 00000000 R1: 00000000 R2: 00000000 R3: 00000000
(XEN)      R4: 40011000 R5: 00000001 R6: 00000001 R7: 0028fb54
(XEN)      R8: 00004d24 R9: 7fffa000 R10:00000000 R11:0028fad4 R12:80000001
(XEN) HYP: SP: 0028fab4 LR: 0024718c
(XEN)
(XEN) HTTBR bfed2000
(XEN) HDFAR 0
(XEN) HIFAR 0
(XEN) HPFAR 0
(XEN) HCR 00002835
(XEN) HSR   94000155
(XEN) VTTBR 0000000000
(XEN)
(XEN) DFSR 0 DFAR 0
(XEN) IFSR 0 IFAR 0
(XEN)
(XEN) Xen stack trace from sp=0028fab4:
(XEN)    0024d784 00000fff 00000000 00000001 00000001 0028fb54 40028000 0028fadc
(XEN)    0026850c 0028fee4 00243404 b0000000 00000000 00020000 00000000 00000000
(XEN)    40037f58 4003f000 0025c4b4 fffffd48 00255c90 00000008 40011000 00000001
(XEN)    00000001 00000000 00000000 10000000 00000000 50000000 00000000 00255b78
(XEN)    00000000 00255b38 00000001 7ffe0f08 0028fb5c 01000000 0f000000 080f0000
(XEN)    000000b0 00000200 00000000 00000000 2c6e6578 2d6e6578 00332e34 2c6e6578
(XEN)    006e6578 00000001 00000001 00000001 00000001 00000001 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000001 00000001 00000000 00000000 00000000 00000000 00000000
(XEN)    30303030 61303430 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 40028000 00000000 00000001 00000000 50000000 00000000 10000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 50000100 00000000 50008000
(XEN)    00000000 00000000 00000000 a0000000 00000000 50008000 00000000 001be4c0
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN) Xen call trace:
(XEN)    [<0024d78c>] exynos5_specific_mapping+0x30/0xf4
(XEN)    [<0026850c>] ???
(XEN)    [<00243404>] construct_dom0+0x8d4/0xae4
(XEN)    [<002690c0>] ???
(XEN)    [<00200518>] puts+0x8/0x1c

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel