Re: [Xen-devel] Data Abort while in booting when using latest version on arm32 fastmodels

[Julien Grall <julien.grall@xxxxxxx>]

On 12/07/16 06:20, Wonseok Ko wrote:
> Hi, All
Hello,

> I founded the previous post to solve the problem as the same as mine,
> the patch was applied in latest version, but I've got the data abort.
> previous post:
> https://lists.xen.org/archives/html/xen-devel/2013-09/msg00606.html and I 
> referred
> to the wiki page:
> http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/FastModels
This page has not been updated for a while for ARM32. It might be 
possible that the page is out-of-date for the newer models.
> I build the latest version of Xen with command as below:
> # make distclean; XEN_TARGET_ARCH=arm32
> CROSS_COMPILE=arm-linux-gnueabihf- debug=y CONFIG_EARLY_PRINTK=fastmodel
> ./configure
> # make xen XEN_TARGET_ARCH=arm32 CROSS_COMPILE=arm-linux-gnueabihf-
> debug=y CONFIG_EARLY_PRINTK=fastmodel -j 8
>
> My fastmodels command as below:
>
> FVP_VE_Cortex-A15x4-A7x4 -acoretile.cluster0.*=./linux-system-semi.axf \
>
> -acoretile.cluster1.*=./linux-system-semi.axf \
>
> -Cmotherboard.smsc_91c111.enabled=1-Cmotherboard.hostbridge.userNetworking=1\
>
> -Ccoretile.dualclustersystemconfigurationblock.CFG_ACTIVECLUSTER=0x3 \
>
> -Ccoretile.cluster0.cpu0.semihosting-cmd_line="\
>
>                              --kernel ../xen/xen/xen \
>
>                              --module ../linux/arch/arm/boot/zImage \
>
>                              --dtb rtsm_ve-cortex_a15x4_a7x4.dtb \
>
>                              -- earlyprintk console=ttyAMA0 mem=2048M
> root=/dev/nfs nfsroot=192.168.0.8:/srv/nfsroot/ rw ip=dhcp"
This should be the Xen command line and not Linux one.

> Does anybody help me to fix it? or If I did something wrong, please let
> me know.
>
> here is log:
>
> Trying 127.0.0.1...
>
> Connected to localhost.
>
> Escape character is '^]'.
>
> - UART enabled -
>
> - CPU 00000000 booting -
>
> - Xen starting in Hyp mode -
>
> - Zero BSS -
>
> - Setting up control registers -
>
> - Turning on paging -
>
> - Ready -
>
> (XEN) Checking for initrd in /chosen
>
> (XEN) RAM: 0000000080000000 - 00000000ffffffff
>
> (XEN)
>
> (XEN) MODULE[0]: 0000000080d0230c - 0000000080d0473d Device Tree
>
> (XEN) MODULE[1]: 0000000080a00000 - 0000000080d904b8 Kernel
> console=ttyAMA0
If I am not mistaken, the Device Tree and the Kernel overlaps in the 
memory. So Xen will try to free twice the same page, hence the data 
abort later one.
I would look into the bootwrapper to find out why the addresses overlap.

[...]

> (XEN) Xen call trace:
>
> (XEN)    [<0021be40>] page_alloc.c#free_heap_pages+0x2c0/0x428 (PC)
>
> (XEN)    [<0021be18>] page_alloc.c#free_heap_pages+0x298/0x428 (LR)
>
> (XEN)    [<0021cbb8>] page_alloc.c#init_heap_pages+0x100/0x118
>
> (XEN)    [<0021ce78>] init_domheap_pages+0xb0/0xb4
>
> (XEN)    [<002549e8>] dt_unreserved_regions+0xf4/0xfc
>
> (XEN)    [<0028b378>] discard_initial_modules+0x138/0x178
>
> (XEN)    [<0024b1b0>] construct_dom0+0xb24/0xc8c
>
> (XEN)    [<0028c12c>] start_xen+0xd38/0xeb0
>
> (XEN)    [<00200550>] arm32/head.o#paging+0x94/0xd8
Regards,

--
Julien Grall

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