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

[Gihun Jung <gihun.jung@xxxxxxxxx>]

2013/5/1 Julien Grall <julien.grall@xxxxxxxxxx>:

> This is not related, but this branch doesn't work. If you want to try
> Linux 3.9 I advise you use to "dev-arndale-dom0-3.9-rc4". I use this
> branch for my test.
>
> - DTS: arch/arm/boot/exynos5250-arndale.dts
> - config: arch/arm/configs/xen_dom0_arndale_defconfig

I have tried "dev-arndale-dom0-3.9-rc4" and followed what you suggest.
FYI, I am using the latest u-boot version from linaro-stable
(git://git.linaro.org/git-ro/boot/u-boot-linaro-stable.git)

> I have noticed this issue yesterday. The lines between
> p2m_populate_ram... and unmap_domain_page... should be removed.

I have removed it; available to go next step without data abort.

> But there is another issue with linux 3.7. If you want to use
> this version you need to checkout "arndale" branch in my xen git.
> Otherwise you can use the branch "arm" with linux 3.9.
>
> Let me know if you have any issue with this patch series.

But, I am still facing a problem to booting :(
According to log, it seems to success to load the zImage to newly
mapping area for dom0.
It was not working; It was hang on Guest ABT

In here, I have questions. When I used "1:1 mapping for dom0" from
Anthony's patch (i.e. that is removed and improved by your new patch
series),
Xen told me that it populated P2M for dom0 (i.e. mem size = 256M) from
0x40000000 - 0x50000000.
It is exactly same start address of physical RAM of Arndale Board.
Buy, in your patch series, it is in 0x50000000 - 0x60000000.
Is it possible to be a cause of Data Abort?

Please see attached log:

(XEN) Brought up 2 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Device-tree contains "xen,xen" node. Ignoring.
(XEN) Populate P2M 0x50000000->0x60000000 (1:1 mapping for dom0)
(XEN) Loading kernel from boot module 1
... many snips ...
(XEN) Loading zImage from 00000000a0008000 to 0000000050008000-00000000503b5ea0
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) **********************************************
(XEN) ******* WARNING: CONSOLE OUTPUT IS SYNCHRONOUS
(XEN) ******* This option is intended to aid debugging of Xen by ensuring
(XEN) ******* that all output is synchronously delivered on the serial line.
(XEN) ******* However it can introduce SIGNIFICANT latencies and affect
(XEN) ******* timekeeping. It is NOT recommended for production use!
(XEN) **********************************************
(XEN) 3... 2... 1...
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to X)
(XEN) Freed 224kB init memory.
(XEN) *** Serial input -> Xen (type 'CTRL-a' three times to switch input to DO)
(XEN) 'd' pressed -> dumping registers
(XEN)
(XEN) *** Dumping CPU0 guest state (d0:v0): ***
(XEN) ----[ Xen-4.3-unstable  arm32  debug=y  Tainted:    C ]----
(XEN) CPU:    0
(XEN) PC:     ffff000c
(XEN) CPSR:   200001d7 MODE:32-bit Guest ABT
(XEN)      R0: c0b3b114 R1: 000000ff R2: c0e00000 R3: c0e00001
(XEN)      R4: c0b3b114 R5: ffff308d R6: 0000085a R7: c0619c48
(XEN)      R8: c06e88ac R9: c0b2e174 R10:c07f304c R11:00000000 R12:c0510dc4
(XEN) USR: SP: 00000000 LR: 00000000
(XEN) SVC: SP: c071dec0 LR: c03db50c SPSR:000001d3
(XEN) ABT: SP: c077c5cc LR: ffff0010 SPSR:200001d7
(XEN) UND: SP: c077c5d8 LR: c077c5d8 SPSR:00000000
(XEN) IRQ: SP: c077c5c0 LR: c077c5c0 SPSR:00000000
(XEN) FIQ: SP: 00000000 LR: 00000000 SPSR:00000000
(XEN) FIQ: R8: 00000000 R9: 00000000 R10:00000000 R11:00000000 R12:00000000
(XEN)
(XEN) TTBR0 0050003000 TTBR1 0050007000 TCR b5023500
(XEN) SCTLR 30c5387d
(XEN) IFAR ffff000c DFAR c0e00000
(XEN)
(XEN) HTTBR bfed2000
(XEN) HDFAR 0
(XEN) HIFAR 0
(XEN) HPFAR 0
(XEN) HCR 00002835
(XEN) HSR   4a000000
(XEN) VTTBR 10000a040e000
(XEN)
(XEN) DFSR 206 DFAR c0e00000
(XEN) IFSR 206 IFAR ffff000c
(XEN)
(XEN) GUEST STACK GOES HERE
(XEN)
(XEN) *** Dumping CPU1 host state: ***
(XEN) ----[ Xen-4.3-unstable  arm32  debug=y  Tainted:    C ]----
(XEN) CPU:    1
(XEN) PC:     00241b84 idle_loop+0x160/0x198
(XEN) CPSR:   6000015a MODE:Hypervisor
(XEN)      R0: 00000000 R1: 00000000 R2: 00000001 R3: 00000000
(XEN)      R4: 002d7614 R5: 002d7614 R6: 002d7614 R7: 002d7614
(XEN)      R8: 002d6308 R9: 80200000 R10:80000000 R11:40017f54 R12:ffffffff
(XEN) HYP: SP: 40017f34 LR: 00226bdc
(XEN)
(XEN) HTTBR 60018000
(XEN) HDFAR 0
(XEN) HIFAR 0
(XEN) HPFAR 0
(XEN) HCR 00002835
(XEN) HSR   0
(XEN) VTTBR 0000000000
(XEN)
(XEN) DFSR 0 DFAR 0
(XEN) IFSR 0 IFAR 0
(XEN)
(XEN) Xen stack trace from sp=40017f34:
(XEN)    00241b8c 40017f58 00000001 002d4298 e9920be5 3497a020 802d7700 40017f4
(XEN)    002481fc 00000000 00000000 00000000 00000000 00000000 00000000 0000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000
(XEN)    00000000 00000000 00000000
(XEN) Xen call trace:
(XEN)    [<00241b84>] idle_loop+0x160/0x198
(XEN)    [<002481fc>] start_secondary+0x14c/0x164
(XEN)

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