[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Xen on (RELEASE-4.4.0) crashed when booting on Cubieboard2
On 05/04/14 07:30, duqi wrote: Hi, Hello duqi, The dtb is compiled into xen and init ramdisk is bind into the kernel zImage. Dom0_mem is configured as 128MB. Why do you compile the DTB into Xen? I guess you have hardcoded the chosen node... if so can you paste the content here? 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 I can't find this commit in xen repository? Where does it come from? What did you modify on the code? [..] (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) I'm suprised that the call trace is so small. Did you copy everything? Regards, -- Julien Grall _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |