[Xen-devel] Xen on (RELEASE-4.4.0) crashed when booting on Cubieboard2

[duqi <duqi_2009@xxxxxxx>]

Hi,

I am trying to port xen 4.4 release to my cubieboard2. I used the dom0 kernel 
from :https://github.com/jwrdegoede/linux-sunxi.git and sunxi-test branch

Following the instructions of
http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Allwinner
http://blog.xen.org/index.php/2014/04/01/virtualization-on-arm-with-xen/

and the discussion about dom0 memory here :
http://lists.xen.org/archives/html/xen-devel/2014-01/msg02059.html

We have got xen memory layout as the following:
------------------------------------------------------
file name | address         | size(byte)
------------------------------------------------------
xen         | 0x7ea00000  | 861910
zImage    |0x7f600000   | 7367296
------------------------------------------------------


The dtb is compiled into xen and init ramdisk is bind into the kernel zImage. 
Dom0_mem is configured as 128MB.

However, when we boot the system with the follow command:
fatload mmc 0 0x7ea00000 boot/xen                                               
                                                 
fatload mmc 0 0x7f600000 boot/zImage
bootz 0x7ea00000

we crash message on a page allocation bug.
Here is our message dumped.

CPU:   Allwinner A20 (SUN7I)
Board: Cubieboard2
I2C:   ready
DRAM:  1 GiB
MMC:   SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   emac
Hit any key to stop autoboot:  0 
sun7iVirt# fatload mmc 0 0x7ea00000 boot/xen 
reading boot/xen
861910 bytes read in 45 ms (18.3 MiB/s)
sun7iVirt# fatload mmc 0 0x7f600000 boot/zImage
reading boot/zImage
7367296 bytes read in 335 ms (21 MiB/s)
sun7iVirt# bootz 0x7ea00000
Kernel image @ 0x7ea00000 [ 0x000000 - 0x0cf700 ]
WARNING: ignoring attempt to set core boot address 7ff88454 on core -1
WARNING: Not kicking secondary CPUs

Starting kernel ...

 Xen 4.4.0
(XEN) Xen version 4.4.0 (root@) (arm-linux-gnueabihf-gcc (Ubuntu/Linaro 
4.7.2-1ubuntu1) 4.7.2) debug=n Sat Apr  5 14:15:18 CST 24
(XEN) Latest ChangeSet: Fri Mar 14 12:00:11 2014 +0000 git:4e61575-dirty
(XEN) Console output is synchronous.
(XEN) Processor: 410fc074: "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) Generic Timer IRQ: phys=30 hyp=26 virt=27
(XEN) Using generic timer at 24000 KHz
(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, 2 cpus, secure (IID 0100143b).
(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 0x68000000->0x70000000 (1:1 mapping for dom0)
(XEN) Loading kernel from boot module 2
(XEN) Loading zImage from 000000007f600000 to 000000006f800000-000000006ff06a80
(XEN) Loading dom0 initrd from 0000000060000000 to 
0x0000000069800000-0x000000006f800000
(XEN) Loading dom0 DTB to 0x0000000069600000-0x000000006960295f
(XEN) Scrubbing Free RAM: .........done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(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 
Xen)
(XEN) Freed 244kB init memory.
(XEN) Xen BUG at page_alloc.c:698
(XEN) CPU0: Unexpected Trap: Undefined Instruction
(XEN) ----[ Xen-4.4.0  arm32  debug=n  Tainted:    C ]----
(XEN) CPU:    0
(XEN) PC:     00232338 __bug+0x20/0x40
(XEN) CPSR:   6000015a MODE:Hypervisor
(XEN)      R0: 002516e0 R1: 00000002 R2: 00000000 R3: 00000000
(XEN)      R4: 000002ba R5: 0024ac64 R6: 00291118 R7: 00000014
(XEN)      R8: 0029118c R9: 00000000 R10:00291118 R11:00000001 R12:00000003
(XEN) HYP: SP: 47fe7c64 LR: 00232338
(XEN) 
(XEN)   VTCR_EL2: 80002558
(XEN)  VTTBR_EL2: 000100007eacc000
(XEN) 
(XEN)  SCTLR_EL2: 30cd187f
(XEN)    HCR_EL2: 0000000000282835
(XEN)  TTBR0_EL2: 000000007f4c6000
(XEN) 
(XEN)    ESR_EL2: 00000000
(XEN)  HPFAR_EL2: 000000000001c810
(XEN)      HDFAR: c8800f00
(XEN)      HIFAR: 3736781b
(XEN) 
(XEN) Xen stack trace from sp=47fe7c64:
(XEN)    00000000 03800000 00212f8c 0029113c 00000028 0000001c 00000001 00000070
(XEN)    00000000 00000000 00000000 ffffffff 00000001 bfffffff fffffbff ffffffff
(XEN)    ffffffff ffbfffff 00000000 00000000 00000000 00000000 0000001c 00000000
(XEN)    feace000 feacc000 002141a0 00000000 ffffffff 40009000 00000000 00000000
(XEN)    feace000 feace000 00239bb4 00001000 00000000 00001000 00000000 00000000
(XEN)    00000000 feace000 00239f70 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000001 40009100
(XEN)    ffffffff 40009000 00000000 002ce500 002cf614 00001000 00000000 760116ff
(XEN)    00800000 760116ff 00800000 ffffffff 76012000 00000000 00000000 00000001
(XEN)    00000000 00000000 00000000 002ce500 0023a6a8 00002000 00000000 76012000
(XEN)    00000000 0000000f 00000001 00076012 00000000 40009000 002395c4 00000001
(XEN)    00007ff0 00000018 47fe7e98 ef855e50 00000001 00000000 c7855e50 00007ff0
(XEN)    40009000 c7854038 00000000 002ce500 00211d8c 00000001 00000000 c7854038
(XEN)    00000001 47fe7f58 0020c0a4 47fe7e4c 47fe7e54 00000007 47fe7e90 052da43d
(XEN)    00000000 00000000 40008c30 002ce500 47fe7ea0 47fe7ed8 47fe7e6c 00000002
(XEN)    00000001 47fe7e94 00000002 00000003 00002800 c7855e60 47fe7e9c 00000002
(XEN)    00000006 00000007 00000000 00000000 00000000 00000000 47fee8d8 47fee528
(XEN)    00000006 47fee000 47fee538 00000001 00000001 00007ff0 00000001 00000000
(XEN)    00000000 00000001 00000000 40009000 47fe7ed4 ffffffff ffffffff 47fe7ed8
(XEN)    002ce588 47fee000 002cf614 002ce500 002ce588 00000001 00000000 00244118
(XEN) Xen call trace:
(XEN)    [<00232338>] __bug+0x20/0x40 (PC)
(XEN)    [<00232338>] __bug+0x20/0x40 (LR)
(XEN) 
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel