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

[duqi <duqi_2009@xxxxxxx>]

>>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/

We get the code with the following instructions:

host$ git clone git://xenbits.xen.org/xen.git xen
host$ cd xen
host$ git checkout RELEASE-4.4.0
host$ git cherry-pick 0c68ddf3085b90d72b7d3b6affd1fe8fa16eb6be

>Â
>
>>>Â(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.

I also tried to modify the code in page_alloc.c:698.
It is a bug report :
BUG_ON(pg[i].count_info != PGC_state_free);
If i commit this line, the boot progress will go through and get stuck when the 
initial console hvc0 is used.

>
>ManyÂthanks.
>
>
>duqi.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel