Re: [Xen-devel] Data Abort in Dom0 for cubieboard2

[Josh Zhao <joshsystem@xxxxxxxxx>]

2013/9/9 Julien Grall <julien.grall@xxxxxxxxxx>:
> On 09/09/2013 08:36 AM, Josh Zhao wrote:
>>
>> Hi all,
>> Anyone got the similar problem like this:
>>
>>
>>
>>   Starting kernel ...
>>
>> - UART enabled -
>> - CPU 00000000 booting -
>> - Machine ID 000010bb -
>> - Started in Hyp mode -
>> - Zero BSS -
>> - Setting up control registers -
>> - Turning on paging -
>> - Ready -
>> -DTB R8 402d7700 -
>> - PADDR R9 40200000 -
>> - phys-offset R10 40000000 -
>> RAM: 0000000040000000 - 00000000bfffffff
>>
>> MODULE[1]: 0000000060000000 - 0000000060400000
>> Placing Xen at 0x00000000bfe00000-0x00000000c0000000
>> Xen heap: 65536 pages  Dom heap: 458752 pages
>> Looking for UART console serial0
>> ns16550_uart_dt_init
>> ns16550 at 1c28000-1c28400
>> console done?
>> UART mapped at 10007000
>> divisor 0
>>   __  __            _  _   _  _                      _        _     _
>>   \ \/ /___ _ __   | || | | || |     _   _ _ __  ___| |_ __ _| |__ | | ___
>>    \  // _ \ '_ \  | || |_| || |_ __| | | | '_ \/ __| __/ _` | '_ \| |/ _
>> \
>>    /  \  __/ | | | |__   _|__   _|__| |_| | | | \__ \ || (_| | |_) | |
>> __/
>>   /_/\_\___|_| |_|    |_|(_) |_|     \__,_|_|
>> |_|___/\__\__,_|_.__/|_|\___|
>>
>> (XEN) Xen version 4.4-unstable (joshzhao@)
>> (arm-unknown-linux-gnueabi-gcc (GCC) 4.6.3) debug=y Mon Sep  9
>> 15:30:08 CST 2013
>> (XEN) Latest ChangeSet: Mon Aug 26 12:40:44 2013 +0200 git:8a7769b-dirty
>> (XEN) Console output is synchronous.
>> (XEN) Processor: "ARM Limited", variant: 0x0, part 0xc07, rev 0x4
>> (XEN) 32-bit Execution:
>> (XEN)   Processor Features: 00001131:00011011
>> (XEN)     Instruction Sets: AArch32 Thumb Thumb-2 ThumbEE Jazelle
>> (XEN)     Extensions: GenericTimer Security
>> (XEN)   Debug Features: 02010555
>> (XEN)   Auxiliary Features: 00000000
>> (XEN)   Memory Model Features: 10101105 40000000 01240000 02102211
>> (XEN)  ISA Features: 02101110 13112111 21232041 11112131 10011142 00000000
>> (XEN) Platform: ALLWINNER SUN7I-A20
>> (XEN) Generic Timer IRQ: phys=55 hyp=57 virt=56
>> (XEN) clock-frequency res:0
>> (XEN) Using generic timer at 24000 KHz boot_count:0000000021817d4d
>> (XEN) GIC initialization:
>> (XEN)         gic_dist_addr=0000000001c81000
>> (XEN)         gic_cpu_addr=0000000001c82000
>> (XEN)         gic_hyp_addr=0000000001c84000
>> (XEN)         gic_vcpu_addr=0000000001c86000
>> (XEN)         gic_maintenance_irq=25
>> (XEN) GIC: 160 lines, 1 cpu, secure (IID 0100143b).
>> (XEN) Waiting for 0 other CPUs to be ready
>> (XEN) Using scheduler: SMP Credit Scheduler (credit)
>> (XEN) Allocated console ring of 16 KiB.
>> (XEN) VFP implementer 0x41 architecture 2 part 0x30 variant 0x7 rev 0x4
>> (XEN) Brought up 1 CPUs
>> (XEN) *** LOADING DOMAIN 0 ***
>> (XEN) Populate P2M 0x90000000->0xa0000000 (1:1 mapping for dom0)
>> (XEN) Device-tree contains "xen,xen" node. Ignoring.
>> (XEN) Loading kernel from boot module 1
>> (XEN) Loading zImage from 0000000060000000 to
>> 0000000090008000-0000000090375d08
>> (XEN) Loading dom0 DTB to 0x000000009fe00000-0x000000009fe0106f
>> (XEN) CPU0: Unexpected Trap: Data Abort
>> (XEN) ----[ Xen-4.4-unstable  arm32  debug=y  Tainted:    C ]----
>> (XEN) CPU:    0
>> (XEN) PC:     00214270 free_heap_pages+0x228/0x40c
>> (XEN) CPSR:   8000005a MODE:Hypervisor
>> (XEN)      R0: 00100100 R1: 00200200 R2: 00000000 R3: 01800000
>> (XEN)      R4: 00000012 R5: 02000000 R6: 00000012 R7: 00000001
>> (XEN)      R8: 002d200c R9: 02600000 R10:000c0000 R11:0028fa2c
>> R12:00261dcc
>> (XEN) HYP: SP: 0028fa04 LR: 00000000
>> (XEN)
>> (XEN)   VTCR_EL2: 80002558
>> (XEN)  VTTBR_EL2: 00010000bfdfc000
>> (XEN)
>> (XEN)  SCTLR_EL2: 30cd187f
>> (XEN)    HCR_EL2: 0000000000282835
>> (XEN)  TTBR0_EL2: 00000000bfed1000
>> (XEN)
>> (XEN)    ESR_EL2: 94000006
>> (XEN)  HPFAR_EL2: 00000000920e0a40
>> (XEN)      HDFAR: 01800008
>> (XEN)      HIFAR: 8285a320
>> (XEN)
>> (XEN) Xen stack trace from sp=0028fa04:
>> (XEN)    002140d8 0029a3a0 000003ff 02407fe0 00299118 00000400 0029a3a0
>> 00000000
>> (XEN)    4ffff117 0028fa54 00214f0c 00000000 00000fff 00000000 00270010
>> 00000000
>> (XEN)    60000000 00000000 4ffff117 0028fa64 002151e0 002704b0 00000001
>> 0028fa84
>> (XEN)    0026b8bc 00000040 9fe00000 00000000 9fe00000 00000f68 00000000
>> 0028fedc
>> (XEN)    00243470 9fe0106f 00000000 00020000 00000000 4ffeff58 40012000
>> 90000000
>> (XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000
>> 00000008
>> (XEN)    00000001 00000001 00000000 0025dde0 00000000 00000000 4fff4000
>> 00000008
>> (XEN)    00000008 00256ef4 00000002 00000000 00000f10 00000001 00000001
>> 00000001
>> (XEN)    00000001 00000000 00000000 00000000 00000000 00000000 00000000
>> 00000000
>> (XEN)    00000000 00000000 00000000 00000000 00000000 00000001 00000001
>> 00000001
>> (XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000
>> 00000000
>> (XEN)    00000000 00000000 00000000 00000000 00000000 2c6e6578 2d6e6578
>> 00342e34
>> (XEN)    2c6e6578 006e6578 000000b0 00000200 00000000 00000000 01000000
>> 0f000000
>> (XEN)    080f0000 00000000 00000000 00000000 00000000 00000000 4fffe280
>> 40013e80
>> (XEN)    0028fb94 40010000 00000000 10000000 00000000 00000001 00000000
>> 90000000
>> (XEN)    00000000 10000000 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
>> 9fe00000
>> (XEN)    00000000 90008000 00000000 00000000 00000000 60000000 00000000
>> 90008000
>> (XEN) Xen call trace:
>> (XEN)    [<00214270>] free_heap_pages+0x228/0x40c (PC)
>> (XEN)    [<00000000>] ??? (LR)
>> (XEN)    [<00214f0c>] init_heap_pages+0x108/0x120
>> (XEN)    [<002151e0>] init_domheap_pages+0x98/0xa8
>> (XEN)    [<0026b8bc>] discard_initial_modules+0x6c/0x98
>> (XEN)    [<00243470>] construct_dom0+0xc7c/0xe2c
>> (XEN)    [<0026c3b8>] start_xen+0xa94/0xb60
>> (XEN)    [<002005a0>] launch+0x98/0xc8
>> (XEN)
>
>
> I had a similar issue with the Arndale board. Do you have the commit ceb93c7
> "xen/arm: add lower-bound check in mfn_valid" in your tree? It should
> resolve your problem.
>

Thanks Julien. The issue is fixed after applying the patch. I am
wondering why the mfn will be lower than frametable_base_mfn?



> Cheers,
>
> --
> Julien Grall

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