PINE64+ Release APs, APs not started

Henri Hennebert hlh at restart.be
Wed Jul 26 07:27:38 UTC 2017



On 07/25/2017 20:35, Michael Tuexen wrote:
>> On 25. Jul 2017, at 19:22, Henri Hennebert <hlh at restart.be> wrote:
>>
>> Hello,
>>
>> With FreeBSD 12.0-CURRENT #0 r320599 I can boot normally:
>>
>> ...
>> Release APs
>> CPU  0: ARM Cortex-A53 r0p4 affinity:  0
>> Instruction Set Attributes 0 = <AES+PMULL,SHA1,SHA2,CRC32>
>> Instruction Set Attributes 1 = <0>
>>          Processor Features 0 = <AdvSIMD,Float,EL3 32,EL2 32,EL1 32,EL0 32>
>>          Processor Features 1 = <0>
>>       Memory Model Features 0 = <4k Granule,64k Granule,MixedEndian,S/NS Mem,16bit ASID,1TB PA>
>>       Memory Model Features 1 = <>
>>              Debug Features 0 = <2 CTX Breakpoints,4 Watchpoints,6 Breakpoints,PMUv3,Debug v8>
>>              Debug Features 1 = <0>
>>          Auxiliary Features 0 = <0>
>>          Auxiliary Features 1 = <0>
>> CPU  1: ARM Cortex-A53 r0p4 affinity:  1
>> CPU  2: ARM Cortex-A53 r0p4 affinity:  2
>> CPU  3: ARM Cortex-A53 r0p4 affinity:  3
>> ...
>>
>> With r320869, I get
>>
>> Release APs
>> APs not started
>>   x0: ffff000000977d80
>>   x1: fffffd000299ba80
>>   x2:                3
>>
>> I succeed one time to boot with r321003 but after that I try multiple times and get the same error: APs not started
>>
>> I try r321371 to no avail.
>>
>> Any idea ?
> I reported a similar behaviour on a RPi3 with some way of workaround... But I don't have a solution...

Your workaround work fine for the PINE64+

<quote>

When powering up, typing ? followed by typing boot-conf,

</quote>

Thanks a lot

Henri

> Best regards
> Michael
>>
>> Henri
>> _______________________________________________
>> freebsd-arm at freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"
> 
> 


More information about the freebsd-arm mailing list