[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
AtÂ2014-04-06Â00:13:25,"JulienÂGrall"Â<julien.grall@xxxxxxxxxx>Âwrote: > > >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? Yeah, I tried to use the configuration in dtb when I boot the xen. Here is my chosen node in dtb: chosen { bootargs = "dom0_mem=128M sync_console console=dtuart dtuart=serial0"; xen,dom0-bootargs = "console=hvc0,115200n8 debug ignore_loglevel rw earlyprintk=xen clk_ignore_unused init=/init"; modules { module@0 { compatible = "xen,linux-zimage", "xen,multiboot-module"; reg = <0x7f600000 0xf00000>; }; module@1 { compatible = "xen,linux-initrd", "xen,multiboot-module"; reg = <0x60000000 0x6000000>; linux,initrd-start = <0x60000000>; linux,initrd-end = <0x66000000>; }; }; }; hypervisor { compatible = "xen,xen-4.2", "xen,xen"; reg = <0xb0000000 0x20000>; interrupts = <1 15 0xf08>; }; aliases { serial0 = "/soc@01c00000/serial@01c28000"; }; > >>Â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? Sorry , I have not noticed this commit. I just used the tree from :git://xenbits.xen.org/xen.git. and the RELEASE-4.4.0 branch. I got a patch from this blog:http://blog.xen.org/index.php/2014/04/01/virtualization-on-arm-with-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) > >I'mÂsuprisedÂthatÂtheÂcallÂtraceÂisÂsoÂsmall.ÂDidÂyouÂcopyÂeverything? Yeah, that's all the call trace. Many thanks. duqi. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |