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

[duqi <duqi_2009@xxxxxxx>]

At 2014-04-09 22:37:22,"Ian Campbell" <Ian.Campbell@xxxxxxxxxx> wrote:
>On Wed, 2014-04-09 at 22:08 +0800, duqi wrote:
>> We have tried to follow the wiki page's instruction to boot dom0 on
>> xen , but we found that there are something wrong with it. We made
>> some simple modification about bootargs.
>
>Can you say what you changed?
>
>AFAICT: Added sync_console to the xen bootargs. Added a bunch of stuff
>to the Linux command line, much of which looks unnecessary:
>
>console=hvc0,115200n8:         the ",115200n8" is not needed.
>debug ignore_loglevel rw:              OK
>earlyprintk=xen:                               I don't believe "=xen" does 
>anything
>init=/init:                                    OK, but what does this do?
>

I will test this soon without ",115200n8" 、"=xen" and so on , but I believe 
this doesn't master.

>I notice that you don't seem to have earlyprintk enabled in your
>hypervisor, although I suppose that doesn't matter here.
>
>> fatload mmc 0 ${fdt_addr} /boot/sun7i-a20-cubieboard2-xen2.dtb
>
>What is this? How does it differ from sun7i-a20-cubieboard2.dtb from the
>kernel source? You should not need to modify the dtb to run under Xen.
>

I tested the sun7i-a20-cubieboard.dtb a moment ago, the result is all the same.

>> Whithout this change , it would be stuck at the start of the dom0's boot.
>
>Where exactly?
>

setenv bootargs "sync_console console=dtuart 
dtuart=/soc@01c00000/serial@01c28000 dom0_mem=128M"
In this command, the xen dom0 don't be booted if I dont't add the ‘sync_console’


On the other hand ,  I got above result  by making the modification in 
xen/xen/common/page_alloc.c(698):

   ——    BUG_ON(pg[i].count_info != PGC_state_free);                            
                                                  
   ++     if(pg[i].count_info != PGC_state_free)
   ++            pg[i].count_info = PGC_state_free;

If I don't make this change , the kerneldump will be this and the Xen BUG at 
page_alloc.c:698 is there :

Kernel image @ 0x7e800000 [ 0x000000 - 0x0cf700 ]
## Flattened Device Tree blob at 7ea00000
   Booting using the fdt blob at 0x7ea00000
   reserving fdt memory region: addr=7ea00000 size=3000
   Using Device Tree in place at 7ea00000, end 7ea05fff

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 Wed Apr  9 22:28:36 CST 24
(XEN) Latest ChangeSet: Fri Mar 14 12:00:11 2014 +0000 git:69bae51-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 000000007f400000 to 000000006f800000-000000006ff08fa0
(XEN) Loading dom0 DTB to 0x000000006f600000-0x000000006f6028ef
(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:     0023232c __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: 0023232c
(XEN) 
(XEN)   VTCR_EL2: 80002558
(XEN)  VTTBR_EL2: 000100007ea06000
(XEN) 
(XEN)  SCTLR_EL2: 30cd187f
(XEN)    HCR_EL2: 0000000000282835
(XEN)  TTBR0_EL2: 000000007f2c6000
(XEN) 
(XEN)    ESR_EL2: 00000000
(XEN)  HPFAR_EL2: 000000000001c810
(XEN)      HDFAR: c8800f00
(XEN)      HIFAR: 67e0f778
(XEN) 
(XEN) Xen stack trace from sp=47fe7c64:
(XEN)    00000000 03800000 00212f80 0029113c 00000028 0000001c 00000001 00000070
(XEN)    00000000 00000000 00000000 11df0005 00000001 1ebf5584 877b0898 6f6f3816
(XEN)    3cfa0020 25370892 00000000 00000000 00000000 00000000 0000001c 00000000
(XEN)    fea05000 fea06000 00214194 00000000 fe6e4200 40009000 00000000 00000000
(XEN)    fea05000 fea05000 00239bb4 00001000 00000000 00001000 00000000 00000000
(XEN)    00000000 fea05000 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 d6dc2122 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 ee895e50 00000001 00000000 c6895e50 00007ff0
(XEN)    40009000 00000000 00000000 002ce500 00211d80 00000001 00000000 00000000
(XEN)    00000001 47fe7f58 0020c098 47fe7e4c 47fe7e54 00000007 47fe7e90 db6b5965
(XEN)    00000000 00000000 40008c30 002ce500 47fe7ea0 47fe7ed8 47fe7e6c 00000002
(XEN)    00000001 47fe7e94 00000002 00000003 00002800 c6895e60 47fe7e9c 00000002
(XEN)    00000006 00000007 00000000 00000000 00000000 00003b20 0000b800 0000007a
(XEN)    00000000 00000000 0000ee6b 00002800 00000001 c0937ff0 00000001 00000000
(XEN)    00000000 00000001 00000000 00000000 015ec8b0 00000000 7174aa00 015ec8b0
(XEN)    3b9aca00 47fe7f58 002405dc 47fe7ed8 00210954 3b20b800 00000000 00000000
(XEN) Xen call trace:
(XEN)    [<0023232c>] __bug+0x20/0x40 (PC)
(XEN)    [<0023232c>] __bug+0x20/0x40 (LR)
(XEN) 


Many thanks!

duqi.


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