PINE64+ Release APs, APs not started

classic Classic list List threaded Threaded
19 messages Options
Reply | Threaded
Open this post in threaded view
|

PINE64+ Release APs, APs not started

Henri Hennebert
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 ?

Henri
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: PINE64+ Release APs, APs not started

Michael Tuexen-3
> On 25. Jul 2017, at 19:22, Henri Hennebert <[hidden email]> 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...

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

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: PINE64+ Release APs, APs not started

Henri Hennebert


On 07/25/2017 20:35, Michael Tuexen wrote:

>> On 25. Jul 2017, at 19:22, Henri Hennebert <[hidden email]> 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
>> _______________________________________________
>> [hidden email] mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
>> To unsubscribe, send any mail to "[hidden email]"
>
>
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: PINE64+ Release APs, APs not started

Emmanuel Vadot-7
In reply to this post by Henri Hennebert
On Tue, 25 Jul 2017 19:22:19 +0200
Henri Hennebert <[hidden email]> 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 ?
>
> Henri


 Hello Henri,

 I'm in the process of updating the u-boot port for pine64 which adds
new and better PSCI support. I should be done by the end of the week.
 In the meantime you can use the u-boot I built from here :
 fetch https://people.freebsd.org/~manu/uboot/u-boot-pine64.bin
 dd if=u-boot-pine64.bin of=/dev/da0 bs=1k seek=8 conv=sync

 Cheers,

--
Emmanuel Vadot <[hidden email]> <[hidden email]>
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: PINE64+ Release APs, APs not started

Henri Hennebert
On 07/27/2017 07:52, Emmanuel Vadot wrote:

> On Tue, 25 Jul 2017 19:22:19 +0200
> Henri Hennebert <[hidden email]> 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 ?
>>
>> Henri
>
>
>   Hello Henri,
>
>   I'm in the process of updating the u-boot port for pine64 which adds
> new and better PSCI support. I should be done by the end of the week.
>   In the meantime you can use the u-boot I built from here :
>   fetch https://people.freebsd.org/~manu/uboot/u-boot-pine64.bin
>   dd if=u-boot-pine64.bin of=/dev/da0 bs=1k seek=8 conv=sync
>
>   Cheers,
>
Here is the boot dialog with kernel 12.0 r321371:

U-Boot SPL 2017.07-00011-g41b31da7ca-dirty (Jul 27 2017 - 07:37:57)
DRAM: 2048 MiB
Trying to boot from MMC1


U-Boot 2017.07-00011-g41b31da7ca-dirty (Jul 27 2017 - 07:37:57 +0200)
Allwinner Technology


 >> FreeBSD EFI boot block
    Loader path: /boot/loader.efi

    Initializing modules: ZFS UFS
    Probing 3 block devices.....* done
     ZFS found no pools
     UFS found 1 partition
Consoles: EFI console
Command line arguments: loader.efi
Image base: 0xb6dbd008
EFI version: 2.05
EFI Firmware: Das U-boot (rev 0.00)

FreeBSD/arm64 EFI loader, Revision 1.1
(Tue Jul 25 03:58:20 CEST 2017 [hidden email])
EFI boot environment
Loading /boot/defaults/loader.conf
/boot/kernel/kernel text=0x71e578 data=0xa2a80+0x39e6a6
syms=[0x8+0xf6db0+0x8+0xeaf4a]
/boot/entropy size=0x1000

Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...
Using DTB provided by EFI at 0x48000000.
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 1992-2017 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
         The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 12.0-CURRENT #0 r321371M: Tue Jul 25 16:02:39 CEST 2017
     [hidden email]:/usr/obj/usr/src/sys/NORQUAY arm64
FreeBSD clang version 5.0.0 (trunk 308421) (based on LLVM 5.0.0svn)
VT: init without driver.
Starting CPU 1 (1)
Starting CPU 2 (2)
Starting CPU 3 (3)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
random: unblocking device.
random: entropy device external interface
kbd0 at kbdmux0
ofwbus0: <Open Firmware Device Tree>
clk_fixed0: <Fixed clock> on ofwbus0
clk_fixed1: <Fixed clock> on ofwbus0
clk_fixed2: <Fixed clock> on ofwbus0
simplebus0: <Flattened device tree simple bus> on ofwbus0
aw_ccung0: <Allwinner Clock Control Unit NG> mem 0x1c20000-0x1c203ff on
simplebus0
aw_ccung0: Cannot set parent to pll_ddr for dram
regfix0: <Fixed Regulator> on ofwbus0
psci0: <ARM Power State Co-ordination Interface Driver> on ofwbus0
awusbphy0: <Allwinner USB PHY> mem
0x1c19400-0x1c19413,0x1c1a800-0x1c1a803,0x1c1b800-0x1c1b803 on simplebus0
gic0: <ARM Generic Interrupt Controller> mem
0x1c81000-0x1c81fff,0x1c82000-0x1c83fff,0x1c84000-0x1c85fff,0x1c86000-0x1c87fff
irq 210
gic0: pn 0x2, arch 0x2, rev 0x1, implementer 0x43b irqs 224
gpio0: <Allwinner GPIO/Pinmux controller> mem 0x1c20800-0x1c20bff irq
10,11,12 on simplebus0
gpiobus0: <OFW GPIO bus> on gpio0
gpio1: <Allwinner GPIO/Pinmux controller> mem 0x1f02c00-0x1f02fff irq 24
on simplebus0
gpiobus1: <OFW GPIO bus> on gpio1
generic_timer0: <ARMv8 Generic Timer> irq 0,1,2,3 on ofwbus0
Timecounter "ARM MPCore Timecounter" frequency 24000000 Hz quality 1000
Event timer "ARM MPCore Eventtimer" frequency 24000000 Hz quality 1000
rtc0: <Allwinner RTC> mem 0x1f00000-0x1f00053 irq 22,23 on simplebus0
rtc0: registered as a time-of-day clock, resolution 1.000000s
cpulist0: <Open Firmware CPU Group> on ofwbus0
cpu0: <Open Firmware CPU> on cpulist0
cpu1: <Open Firmware CPU> on cpulist0
cpu2: <Open Firmware CPU> on cpulist0
cpu3: <Open Firmware CPU> on cpulist0
a10_mmc0: <Allwinner Integrated MMC/SD controller> mem
0x1c0f000-0x1c0ffff irq 4 on simplebus0
mmc0: <MMC/SD bus> on a10_mmc0
ohci0: <Generic OHCI Controller> mem 0x1c1b400-0x1c1b4ff irq 9 on simplebus0
usbus0 on ohci0
gpioc0: <GPIO controller> on gpio0
uart0: <16750 or compatible> mem 0x1c28000-0x1c283ff irq 13 on simplebus0
uart0: console (115384,n,8,1)
gpioc1: <GPIO controller> on gpio1
awg0: <Allwinner Gigabit Ethernet> mem
0x1c30000-0x1c31fff,0x1c00030-0x1c00033 irq 25 on simplebus0
miibus0: <MII bus> on awg0
rgephy0: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 0 on miibus0
rgephy0:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX,
100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, w
rgephy1: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 1 on miibus0
rgephy1:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX,
100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, w
awg0: Ethernet address: 02:ba:cf:46:d5:39
cryptosoft0: <software crypto>
Timecounters tick every 1.000 msec
usbus0: 12Mbps Full Speed USB v1.0
ugen0.1: <Generic OHCI root HUB> at usbus0
uhub0: <Generic OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
device_attach: uhub0 attach returned 6
usbus0: Root HUB problem, error=USB_ERR_NO_ROOT_HUB
mmcsd0: 16GB <SDHC SL16G 8.0 SN A9A41D45 MFG 03/2017 by 3 SD> at mmc0
50.0MHz/4bit/65535-block
Release APs
APs not started
   x0: ffff00000096dd00
   x1: fffffd000094c540
   x2:               ü

And now I try the kernel r320599 which can detect the processors:


U-Boot SPL 2017.07-00011-g41b31da7ca-dirty (Jul 27 2017 - 07:37:57)
DRAM: 2048 MiB
Trying to boot from MMC1


U-Boot 2017.07-00011-g41b31da7ca-dirty (Jul 27 2017 - 07:37:57 +0200)
Allwinner Technology


 >> FreeBSD EFI boot block
    Loader path: /boot/loader.efi

    Initializing modules: ZFS UFS
    Probing 3 block devices.....* done
     ZFS found no pools
     UFS found 1 partition
Consoles: EFI console
Command line arguments: loader.efi
Image base: 0xb6dbd008
EFI version: 2.05
EFI Firmware: Das U-boot (rev 0.00)

FreeBSD/arm64 EFI loader, Revision 1.1
(Tue Jul 25 03:58:20 CEST 2017 [hidden email])
EFI boot environment
Loading /boot/defaults/loader.conf
/boot/kernel/kernel text=0x71e578 data=0xa2a80+0x39e6a6
syms=[0x8+0xf6db0+0x8+0xeaf4a]
/boot/entropy size=0x1000

Hit [Enter] to boot immediately, or any other key for command prompt.


Type '?' for a list of commands, 'help' for more detailed help.
OK unload
OK load /boot/kernel.r320599/kernel
/boot/kernel.r320599/kernel text=0x7240cc data=0x9fcf8+0x39e6ce
syms=[0x8+0xf5f88+0x8+0xea601]
OK set module_path=/boot/kernel.r320599
OK boot -s
Booting...
Using DTB provided by EFI at 0x48000000.
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 1992-2017 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
         The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 12.0-CURRENT #0 r320599M: Sat Jul  8 18:24:19 CEST 2017
     [hidden email]:/usr/obj/usr/src/sys/NORQUAY arm64
FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on
LLVM 4.0.0)
VT: init without driver.
Starting CPU 1 (1)
Starting CPU 2 (2)
Starting CPU 3 (3)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
arc4random: no preloaded entropy cache
random: entropy device external interface
kbd0 at kbdmux0
ofwbus0: <Open Firmware Device Tree>
clk_fixed0: <Fixed clock> on ofwbus0
clk_fixed1: <Fixed clock> on ofwbus0
clk_fixed2: <Fixed clock> on ofwbus0
simplebus0: <Flattened device tree simple bus> on ofwbus0
regfix0: <Fixed Regulator> on ofwbus0
psci0: <ARM Power State Co-ordination Interface Driver> on ofwbus0
awusbphy0: <Allwinner USB PHY> mem
0x1c19400-0x1c19413,0x1c1a800-0x1c1a803,0x1c1b800-0x1c1b803 on simplebus0
gic0: <ARM Generic Interrupt Controller> mem
0x1c81000-0x1c81fff,0x1c82000-0x1c83fff,0x1c84000-0x1c85fff,0x1c86000-0x1c87fff
irq 210
gic0: pn 0x2, arch 0x2, rev 0x1, implementer 0x43b irqs 224
gpio0: <Allwinner GPIO/Pinmux controller> mem 0x1c20800-0x1c20bff irq
10,11,12 on simplebus0
gpiobus0: <OFW GPIO bus> on gpio0
gpio1: <Allwinner GPIO/Pinmux controller> mem 0x1f02c00-0x1f02fff irq 24
on simplebus0
gpiobus1: <OFW GPIO bus> on gpio1
generic_timer0: <ARMv8 Generic Timer> irq 0,1,2,3 on ofwbus0
Timecounter "ARM MPCore Timecounter" frequency 24000000 Hz quality 1000
Event timer "ARM MPCore Eventtimer" frequency 24000000 Hz quality 1000
rtc0: <Allwinner RTC> mem 0x1f00000-0x1f00053 irq 22,23 on simplebus0
cpulist0: <Open Firmware CPU Group> on ofwbus0
cpu0: <Open Firmware CPU> on cpulist0
cpu1: <Open Firmware CPU> on cpulist0
cpu2: <Open Firmware CPU> on cpulist0
cpu3: <Open Firmware CPU> on cpulist0
ohci0: <Generic OHCI Controller> mem 0x1c1b400-0x1c1b4ff irq 9 on simplebus0
usbus0 on ohci0
gpioc0: <GPIO controller> on gpio0
uart0: <Non-standard ns8250 class UART with FIFOs> mem
0x1c28000-0x1c283ff irq 13 on simplebus0
uart0: console (-1,n,8,1)
gpioc1: <GPIO controller> on gpio1
cryptosoft0: <software crypto>
Timecounters tick every 1.000 msec
usbus0: 12Mbps Full Speed USB v1.0
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
arc4random: no preloaded entropy cache

Trying to mount root from ufs:/dev/mmcsd0s2a [rw,noatime]...

Root mount waiting for:ugen0.1: <Generic OHCI root HUB> at usbus0

  usbus0

uhub0: <Generic OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
device_attach: uhub0 attach returned 6
usbus0: Root HUB problem, error=USB_ERR_NO_ROOT_HUB
mountroot: waiting for device /dev/mmcsd0s2a...
Mounting from ufs:/dev/mmcsd0s2a failed with error 19.

Loader variables:
   vfs.root.mountfrom=ufs:/dev/mmcsd0s2a
   vfs.root.mountfrom.options=rw,noatime

Manual root filesystem specification:
   <fstype>:<device> [options]
       Mount <device> using filesystem <fstype>
       and with the specified (optional) option list.

     eg. ufs:/dev/da0s1a
         zfs:tank
         cd9660:/dev/cd0 ro
           (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /)

   ?               List valid disk boot devices
   .               Yield 1 second (for background tasks)
   <empty line>    Abort manual input

mountroot>

To be noted:

device_attach: uhub0 attach returned 6
usbus0: Root HUB problem, error=USB_ERR_NO_ROOT_HUB

and mmcsd0 is not detected.

I think that the DTB is wrong.

Note that my kernel config have:

options         FDT                     # Flattened Device Tree bus driver
options         FDT_DTB_STATIC          # Statically embed a DTB file
into a kernel image
makeoptions     FDT_DTS_FILE=pine64_plus.dts

Henri


_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: PINE64+ Release APs, APs not started

Emmanuel Vadot-7
On Thu, 27 Jul 2017 14:31:18 +0200
Henri Hennebert <[hidden email]> wrote:

> On 07/27/2017 07:52, Emmanuel Vadot wrote:
> > On Tue, 25 Jul 2017 19:22:19 +0200
> > Henri Hennebert <[hidden email]> 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 ?
> >>
> >> Henri
> >
> >
> >   Hello Henri,
> >
> >   I'm in the process of updating the u-boot port for pine64 which adds
> > new and better PSCI support. I should be done by the end of the week.
> >   In the meantime you can use the u-boot I built from here :
> >   fetch https://people.freebsd.org/~manu/uboot/u-boot-pine64.bin
> >   dd if=u-boot-pine64.bin of=/dev/da0 bs=1k seek=8 conv=sync
> >
> >   Cheers,
> >
> Here is the boot dialog with kernel 12.0 r321371:
>
> U-Boot SPL 2017.07-00011-g41b31da7ca-dirty (Jul 27 2017 - 07:37:57)
> DRAM: 2048 MiB
> Trying to boot from MMC1
>
>
> U-Boot 2017.07-00011-g41b31da7ca-dirty (Jul 27 2017 - 07:37:57 +0200)
> Allwinner Technology
>
>
>  >> FreeBSD EFI boot block
>     Loader path: /boot/loader.efi
>
>     Initializing modules: ZFS UFS
>     Probing 3 block devices.....* done
>      ZFS found no pools
>      UFS found 1 partition
> Consoles: EFI console
> Command line arguments: loader.efi
> Image base: 0xb6dbd008
> EFI version: 2.05
> EFI Firmware: Das U-boot (rev 0.00)
>
> FreeBSD/arm64 EFI loader, Revision 1.1
> (Tue Jul 25 03:58:20 CEST 2017 [hidden email])
> EFI boot environment
> Loading /boot/defaults/loader.conf
> /boot/kernel/kernel text=0x71e578 data=0xa2a80+0x39e6a6
> syms=[0x8+0xf6db0+0x8+0xeaf4a]
> /boot/entropy size=0x1000
>
> Hit [Enter] to boot immediately, or any other key for command prompt.
> Booting [/boot/kernel/kernel]...
> Using DTB provided by EFI at 0x48000000.

 I'm not sure this is true.

> KDB: debugger backends: ddb
> KDB: current backend: ddb
> Copyright (c) 1992-2017 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
>          The Regents of the University of California. All rights reserved.
> FreeBSD is a registered trademark of The FreeBSD Foundation.
> FreeBSD 12.0-CURRENT #0 r321371M: Tue Jul 25 16:02:39 CEST 2017
>      [hidden email]:/usr/obj/usr/src/sys/NORQUAY arm64
> FreeBSD clang version 5.0.0 (trunk 308421) (based on LLVM 5.0.0svn)
> VT: init without driver.
> Starting CPU 1 (1)
> Starting CPU 2 (2)
> Starting CPU 3 (3)
> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
> random: unblocking device.
> random: entropy device external interface
> kbd0 at kbdmux0
> ofwbus0: <Open Firmware Device Tree>
> clk_fixed0: <Fixed clock> on ofwbus0
> clk_fixed1: <Fixed clock> on ofwbus0
> clk_fixed2: <Fixed clock> on ofwbus0
> simplebus0: <Flattened device tree simple bus> on ofwbus0
> aw_ccung0: <Allwinner Clock Control Unit NG> mem 0x1c20000-0x1c203ff on
> simplebus0
> aw_ccung0: Cannot set parent to pll_ddr for dram

 This error is weird.

> regfix0: <Fixed Regulator> on ofwbus0
> psci0: <ARM Power State Co-ordination Interface Driver> on ofwbus0
> awusbphy0: <Allwinner USB PHY> mem
> 0x1c19400-0x1c19413,0x1c1a800-0x1c1a803,0x1c1b800-0x1c1b803 on simplebus0
> gic0: <ARM Generic Interrupt Controller> mem
> 0x1c81000-0x1c81fff,0x1c82000-0x1c83fff,0x1c84000-0x1c85fff,0x1c86000-0x1c87fff
> irq 210
> gic0: pn 0x2, arch 0x2, rev 0x1, implementer 0x43b irqs 224
> gpio0: <Allwinner GPIO/Pinmux controller> mem 0x1c20800-0x1c20bff irq
> 10,11,12 on simplebus0
> gpiobus0: <OFW GPIO bus> on gpio0
> gpio1: <Allwinner GPIO/Pinmux controller> mem 0x1f02c00-0x1f02fff irq 24
> on simplebus0
> gpiobus1: <OFW GPIO bus> on gpio1
> generic_timer0: <ARMv8 Generic Timer> irq 0,1,2,3 on ofwbus0
> Timecounter "ARM MPCore Timecounter" frequency 24000000 Hz quality 1000
> Event timer "ARM MPCore Eventtimer" frequency 24000000 Hz quality 1000
> rtc0: <Allwinner RTC> mem 0x1f00000-0x1f00053 irq 22,23 on simplebus0
> rtc0: registered as a time-of-day clock, resolution 1.000000s
> cpulist0: <Open Firmware CPU Group> on ofwbus0
> cpu0: <Open Firmware CPU> on cpulist0
> cpu1: <Open Firmware CPU> on cpulist0
> cpu2: <Open Firmware CPU> on cpulist0
> cpu3: <Open Firmware CPU> on cpulist0
> a10_mmc0: <Allwinner Integrated MMC/SD controller> mem
> 0x1c0f000-0x1c0ffff irq 4 on simplebus0
> mmc0: <MMC/SD bus> on a10_mmc0
> ohci0: <Generic OHCI Controller> mem 0x1c1b400-0x1c1b4ff irq 9 on simplebus0
> usbus0 on ohci0
> gpioc0: <GPIO controller> on gpio0
> uart0: <16750 or compatible> mem 0x1c28000-0x1c283ff irq 13 on simplebus0
> uart0: console (115384,n,8,1)
> gpioc1: <GPIO controller> on gpio1
> awg0: <Allwinner Gigabit Ethernet> mem
> 0x1c30000-0x1c31fff,0x1c00030-0x1c00033 irq 25 on simplebus0
> miibus0: <MII bus> on awg0
> rgephy0: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 0 on miibus0
> rgephy0:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX,
> 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, w
> rgephy1: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 1 on miibus0
> rgephy1:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX,
> 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, w
> awg0: Ethernet address: 02:ba:cf:46:d5:39
> cryptosoft0: <software crypto>
> Timecounters tick every 1.000 msec
> usbus0: 12Mbps Full Speed USB v1.0
> ugen0.1: <Generic OHCI root HUB> at usbus0
> uhub0: <Generic OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
> device_attach: uhub0 attach returned 6
> usbus0: Root HUB problem, error=USB_ERR_NO_ROOT_HUB
> mmcsd0: 16GB <SDHC SL16G 8.0 SN A9A41D45 MFG 03/2017 by 3 SD> at mmc0
> 50.0MHz/4bit/65535-block
> Release APs
> APs not started
>    x0: ffff00000096dd00
>    x1: fffffd000094c540
>    x2:               ü
>
> And now I try the kernel r320599 which can detect the processors:
>
>
> U-Boot SPL 2017.07-00011-g41b31da7ca-dirty (Jul 27 2017 - 07:37:57)
> DRAM: 2048 MiB
> Trying to boot from MMC1
>
>
> U-Boot 2017.07-00011-g41b31da7ca-dirty (Jul 27 2017 - 07:37:57 +0200)
> Allwinner Technology
>
>
>  >> FreeBSD EFI boot block
>     Loader path: /boot/loader.efi
>
>     Initializing modules: ZFS UFS
>     Probing 3 block devices.....* done
>      ZFS found no pools
>      UFS found 1 partition
> Consoles: EFI console
> Command line arguments: loader.efi
> Image base: 0xb6dbd008
> EFI version: 2.05
> EFI Firmware: Das U-boot (rev 0.00)
>
> FreeBSD/arm64 EFI loader, Revision 1.1
> (Tue Jul 25 03:58:20 CEST 2017 [hidden email])
> EFI boot environment
> Loading /boot/defaults/loader.conf
> /boot/kernel/kernel text=0x71e578 data=0xa2a80+0x39e6a6
> syms=[0x8+0xf6db0+0x8+0xeaf4a]
> /boot/entropy size=0x1000
>
> Hit [Enter] to boot immediately, or any other key for command prompt.
>
>
> Type '?' for a list of commands, 'help' for more detailed help.
> OK unload
> OK load /boot/kernel.r320599/kernel
> /boot/kernel.r320599/kernel text=0x7240cc data=0x9fcf8+0x39e6ce
> syms=[0x8+0xf5f88+0x8+0xea601]
> OK set module_path=/boot/kernel.r320599
> OK boot -s
> Booting...
> Using DTB provided by EFI at 0x48000000.
> KDB: debugger backends: ddb
> KDB: current backend: ddb
> Copyright (c) 1992-2017 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
>          The Regents of the University of California. All rights reserved.
> FreeBSD is a registered trademark of The FreeBSD Foundation.
> FreeBSD 12.0-CURRENT #0 r320599M: Sat Jul  8 18:24:19 CEST 2017
>      [hidden email]:/usr/obj/usr/src/sys/NORQUAY arm64
> FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on
> LLVM 4.0.0)
> VT: init without driver.
> Starting CPU 1 (1)
> Starting CPU 2 (2)
> Starting CPU 3 (3)
> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
> arc4random: no preloaded entropy cache
> random: entropy device external interface
> kbd0 at kbdmux0
> ofwbus0: <Open Firmware Device Tree>
> clk_fixed0: <Fixed clock> on ofwbus0
> clk_fixed1: <Fixed clock> on ofwbus0
> clk_fixed2: <Fixed clock> on ofwbus0
> simplebus0: <Flattened device tree simple bus> on ofwbus0
> regfix0: <Fixed Regulator> on ofwbus0
> psci0: <ARM Power State Co-ordination Interface Driver> on ofwbus0
> awusbphy0: <Allwinner USB PHY> mem
> 0x1c19400-0x1c19413,0x1c1a800-0x1c1a803,0x1c1b800-0x1c1b803 on simplebus0
> gic0: <ARM Generic Interrupt Controller> mem
> 0x1c81000-0x1c81fff,0x1c82000-0x1c83fff,0x1c84000-0x1c85fff,0x1c86000-0x1c87fff
> irq 210
> gic0: pn 0x2, arch 0x2, rev 0x1, implementer 0x43b irqs 224
> gpio0: <Allwinner GPIO/Pinmux controller> mem 0x1c20800-0x1c20bff irq
> 10,11,12 on simplebus0
> gpiobus0: <OFW GPIO bus> on gpio0
> gpio1: <Allwinner GPIO/Pinmux controller> mem 0x1f02c00-0x1f02fff irq 24
> on simplebus0
> gpiobus1: <OFW GPIO bus> on gpio1
> generic_timer0: <ARMv8 Generic Timer> irq 0,1,2,3 on ofwbus0
> Timecounter "ARM MPCore Timecounter" frequency 24000000 Hz quality 1000
> Event timer "ARM MPCore Eventtimer" frequency 24000000 Hz quality 1000
> rtc0: <Allwinner RTC> mem 0x1f00000-0x1f00053 irq 22,23 on simplebus0
> cpulist0: <Open Firmware CPU Group> on ofwbus0
> cpu0: <Open Firmware CPU> on cpulist0
> cpu1: <Open Firmware CPU> on cpulist0
> cpu2: <Open Firmware CPU> on cpulist0
> cpu3: <Open Firmware CPU> on cpulist0
> ohci0: <Generic OHCI Controller> mem 0x1c1b400-0x1c1b4ff irq 9 on simplebus0
> usbus0 on ohci0
> gpioc0: <GPIO controller> on gpio0
> uart0: <Non-standard ns8250 class UART with FIFOs> mem
> 0x1c28000-0x1c283ff irq 13 on simplebus0
> uart0: console (-1,n,8,1)
> gpioc1: <GPIO controller> on gpio1
> cryptosoft0: <software crypto>
> Timecounters tick every 1.000 msec
> usbus0: 12Mbps Full Speed USB v1.0
> 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
> arc4random: no preloaded entropy cache
>
> Trying to mount root from ufs:/dev/mmcsd0s2a [rw,noatime]...
>
> Root mount waiting for:ugen0.1: <Generic OHCI root HUB> at usbus0
>
>   usbus0
>
> uhub0: <Generic OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
> device_attach: uhub0 attach returned 6
> usbus0: Root HUB problem, error=USB_ERR_NO_ROOT_HUB
> mountroot: waiting for device /dev/mmcsd0s2a...
> Mounting from ufs:/dev/mmcsd0s2a failed with error 19.
>
> Loader variables:
>    vfs.root.mountfrom=ufs:/dev/mmcsd0s2a
>    vfs.root.mountfrom.options=rw,noatime
>
> Manual root filesystem specification:
>    <fstype>:<device> [options]
>        Mount <device> using filesystem <fstype>
>        and with the specified (optional) option list.
>
>      eg. ufs:/dev/da0s1a
>          zfs:tank
>          cd9660:/dev/cd0 ro
>            (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /)
>
>    ?               List valid disk boot devices
>    .               Yield 1 second (for background tasks)
>    <empty line>    Abort manual input
>
> mountroot>
>
> To be noted:
>
> device_attach: uhub0 attach returned 6
> usbus0: Root HUB problem, error=USB_ERR_NO_ROOT_HUB
>
> and mmcsd0 is not detected.

 There is no aw_ccung in the last dmesg, which is definitively wrong.

> I think that the DTB is wrong.
>
> Note that my kernel config have:
>
> options         FDT                     # Flattened Device Tree bus driver
> options         FDT_DTB_STATIC          # Statically embed a DTB file
> into a kernel image
> makeoptions     FDT_DTS_FILE=pine64_plus.dts

 FDT_DTB_STATIC shouldn't be used unless you *exactly* know what you're
doing. Please use GENERIC kernel on ARM64.

> Henri


--
Emmanuel Vadot <[hidden email]> <[hidden email]>
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: PINE64+ Release APs, APs not started

Andrew Turner

> On 27 Jul 2017, at 15:43, Emmanuel Vadot <[hidden email]> wrote:
>
> On Thu, 27 Jul 2017 14:31:18 +0200
> Henri Hennebert <[hidden email] <mailto:[hidden email]>> wrote:
>> I think that the DTB is wrong.
>>
>> Note that my kernel config have:
>>
>> options         FDT                     # Flattened Device Tree bus driver
>> options         FDT_DTB_STATIC          # Statically embed a DTB file
>> into a kernel image
>> makeoptions     FDT_DTS_FILE=pine64_plus.dts
>
> FDT_DTB_STATIC shouldn't be used unless you *exactly* know what you're
> doing. Please use GENERIC kernel on ARM64.

On arm64 we don’t use it so you just end up with a larger kernel image.

Andrew

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: PINE64+ Release APs, APs not started

Emmanuel Vadot-7
On Thu, 27 Jul 2017 15:57:40 +0100
Andrew Turner <[hidden email]> wrote:

>
> > On 27 Jul 2017, at 15:43, Emmanuel Vadot <[hidden email]> wrote:
> >
> > On Thu, 27 Jul 2017 14:31:18 +0200
> > Henri Hennebert <[hidden email] <mailto:[hidden email]>> wrote:
> >> I think that the DTB is wrong.
> >>
> >> Note that my kernel config have:
> >>
> >> options         FDT                     # Flattened Device Tree bus driver
> >> options         FDT_DTB_STATIC          # Statically embed a DTB file
> >> into a kernel image
> >> makeoptions     FDT_DTS_FILE=pine64_plus.dts
> >
> > FDT_DTB_STATIC shouldn't be used unless you *exactly* know what you're
> > doing. Please use GENERIC kernel on ARM64.
>
> On arm64 we don?t use it so you just end up with a larger kernel image.
>
> Andrew
>

 I recall that you didn't want it but I assumed that some errors will
be thrown if specified, can we do that ?

--
Emmanuel Vadot <[hidden email]> <[hidden email]>
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: PINE64+ Release APs, APs not started

Henri Hennebert
On 07/27/2017 17:02, Emmanuel Vadot wrote:

> On Thu, 27 Jul 2017 15:57:40 +0100
> Andrew Turner <[hidden email]> wrote:
>
>>
>>> On 27 Jul 2017, at 15:43, Emmanuel Vadot <[hidden email]> wrote:
>>>
>>> On Thu, 27 Jul 2017 14:31:18 +0200
>>> Henri Hennebert <[hidden email] <mailto:[hidden email]>> wrote:
>>>> I think that the DTB is wrong.
>>>>
>>>> Note that my kernel config have:
>>>>
>>>> options         FDT                     # Flattened Device Tree bus driver
>>>> options         FDT_DTB_STATIC          # Statically embed a DTB file
>>>> into a kernel image
>>>> makeoptions     FDT_DTS_FILE=pine64_plus.dts
>>>
>>> FDT_DTB_STATIC shouldn't be used unless you *exactly* know what you're
>>> doing. Please use GENERIC kernel on ARM64.

I will remove it from my kernel config.

I previously encounter this problem:
https://lists.freebsd.org/pipermail/freebsd-current/2017-May/065875.html
so I don't load zfs and opensolaris before boot.
I use this script to get my root fs on zfs:

#!/bin/sh

# PROVIDE: rebootonzfs
# BEFORE: sysctl


. /etc/rc.subr

name="rebootonzfs"
desc="Reboot with root on ZFS"
command="/sbin/reboot"
stop_cmd=":"
start_cmd="rebootonzfs_start"
rcvar="rebootonzfs_enable"

rebootonzfs_start()
{
        /sbin/zpool list
        /bin/kenv vfs.root.mountfrom="zfs:rpool/ROOT/default"
        ${command} -r
}

load_rc_config $name
run_rc_command "$1"

But today, I try with r321371 to load zfs and opensolaris before boot
and it allow most of the time the Release APs to complete.

Believing it is a timing problem, I modify mp_machdep.c:

Index: sys/arm64/arm64/mp_machdep.c
===================================================================
--- sys/arm64/arm64/mp_machdep.c (revision 321371)
+++ sys/arm64/arm64/mp_machdep.c (working copy)
@@ -209,6 +209,7 @@
  if (mp_ncpus == 1)
  return;

+ DELAY(1000000);
  intr_pic_ipi_setup(IPI_AST, "ast", ipi_ast, NULL);
  intr_pic_ipi_setup(IPI_PREEMPT, "preempt", ipi_preempt, NULL);
  intr_pic_ipi_setup(IPI_RENDEZVOUS, "rendezvous", ipi_rendezvous, NULL);

but it don't get better.

Henri

>>
>> On arm64 we don?t use it so you just end up with a larger kernel image.
>>
>> Andrew
>>
>
>   I recall that you didn't want it but I assumed that some errors will
> be thrown if specified, can we do that ?
>
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: PINE64+ Release APs, APs not started

Emmanuel Vadot-7
On Thu, 27 Jul 2017 18:34:53 +0200
Henri Hennebert <[hidden email]> wrote:

> On 07/27/2017 17:02, Emmanuel Vadot wrote:
> > On Thu, 27 Jul 2017 15:57:40 +0100
> > Andrew Turner <[hidden email]> wrote:
> >
> >>
> >>> On 27 Jul 2017, at 15:43, Emmanuel Vadot <[hidden email]> wrote:
> >>>
> >>> On Thu, 27 Jul 2017 14:31:18 +0200
> >>> Henri Hennebert <[hidden email] <mailto:[hidden email]>> wrote:
> >>>> I think that the DTB is wrong.
> >>>>
> >>>> Note that my kernel config have:
> >>>>
> >>>> options         FDT                     # Flattened Device Tree bus driver
> >>>> options         FDT_DTB_STATIC          # Statically embed a DTB file
> >>>> into a kernel image
> >>>> makeoptions     FDT_DTS_FILE=pine64_plus.dts
> >>>
> >>> FDT_DTB_STATIC shouldn't be used unless you *exactly* know what you're
> >>> doing. Please use GENERIC kernel on ARM64.
>
> I will remove it from my kernel config.

 I've just tested latest head with me soon to be u-boot-pine64 port and
I don't have any problems.
 I've corrected the dram/pll_ddr problem (but it shouldn't change
anything)

 Boot log : https://people.freebsd.org/~manu/pine64_bootlog.txt

--
Emmanuel Vadot <[hidden email]> <[hidden email]>
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: PINE64+ Release APs, APs not started

Mark Millard-2
On 2017-Jul-27, at 10:57 AM, Emmanuel Vadot <manu at bidouilliste.com> wrote:

> On Thu, 27 Jul 2017 18:34:53 +0200
> Henri Hennebert <hlh at restart.be> wrote:
>
>> On 07/27/2017 17:02, Emmanuel Vadot wrote:
>>> On Thu, 27 Jul 2017 15:57:40 +0100
>>> Andrew Turner <[hidden email]> wrote:
>>>
>>>>
>>>>> On 27 Jul 2017, at 15:43, Emmanuel Vadot <[hidden email]> wrote:
>>>>>
>>>>> On Thu, 27 Jul 2017 14:31:18 +0200
>>>>> Henri Hennebert <[hidden email] <mailto:[hidden email]>> wrote:
>>>>>> I think that the DTB is wrong.
>>>>>>
>>>>>> Note that my kernel config have:
>>>>>>
>>>>>> options         FDT                     # Flattened Device Tree bus driver
>>>>>> options         FDT_DTB_STATIC          # Statically embed a DTB file
>>>>>> into a kernel image
>>>>>> makeoptions     FDT_DTS_FILE=pine64_plus.dts
>>>>>
>>>>> FDT_DTB_STATIC shouldn't be used unless you *exactly* know what you're
>>>>> doing. Please use GENERIC kernel on ARM64.
>>
>> I will remove it from my kernel config.
>
> I've just tested latest head with me soon to be u-boot-pine64 port and
> I don't have any problems.
> I've corrected the dram/pll_ddr problem (but it shouldn't change
> anything)
>
> Boot log : https://people.freebsd.org/~manu/pine64_bootlog.txt

Your (Emmanuel's) reported boot:

FreeBSD clang version 5.0.0 (trunk 308421) (based on LLVM 5.0.0svn)
WARNING: WITNESS option enabled, expect reduced performance.
VT: init without driver.

vs. one of the reported failing boots (Henri):

FreeBSD clang version 5.0.0 (trunk 308421) (based on LLVM 5.0.0svn)
VT: init without driver.


It looks like the problem is for production-style
(non-debug) builds.


===
Mark Millard
markmi at dsl-only.net

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: PINE64+ Release APs, APs not started

Emmanuel Vadot-7
On Thu, 27 Jul 2017 11:26:19 -0700
Mark Millard <[hidden email]> wrote:

> On 2017-Jul-27, at 10:57 AM, Emmanuel Vadot <manu at bidouilliste.com> wrote:
>
> > On Thu, 27 Jul 2017 18:34:53 +0200
> > Henri Hennebert <hlh at restart.be> wrote:
> >
> >> On 07/27/2017 17:02, Emmanuel Vadot wrote:
> >>> On Thu, 27 Jul 2017 15:57:40 +0100
> >>> Andrew Turner <[hidden email]> wrote:
> >>>
> >>>>
> >>>>> On 27 Jul 2017, at 15:43, Emmanuel Vadot <[hidden email]> wrote:
> >>>>>
> >>>>> On Thu, 27 Jul 2017 14:31:18 +0200
> >>>>> Henri Hennebert <[hidden email] <mailto:[hidden email]>> wrote:
> >>>>>> I think that the DTB is wrong.
> >>>>>>
> >>>>>> Note that my kernel config have:
> >>>>>>
> >>>>>> options         FDT                     # Flattened Device Tree bus driver
> >>>>>> options         FDT_DTB_STATIC          # Statically embed a DTB file
> >>>>>> into a kernel image
> >>>>>> makeoptions     FDT_DTS_FILE=pine64_plus.dts
> >>>>>
> >>>>> FDT_DTB_STATIC shouldn't be used unless you *exactly* know what you're
> >>>>> doing. Please use GENERIC kernel on ARM64.
> >>
> >> I will remove it from my kernel config.
> >
> > I've just tested latest head with me soon to be u-boot-pine64 port and
> > I don't have any problems.
> > I've corrected the dram/pll_ddr problem (but it shouldn't change
> > anything)
> >
> > Boot log : https://people.freebsd.org/~manu/pine64_bootlog.txt
>
> Your (Emmanuel's) reported boot:
>
> FreeBSD clang version 5.0.0 (trunk 308421) (based on LLVM 5.0.0svn)
> WARNING: WITNESS option enabled, expect reduced performance.
> VT: init without driver.
>
> vs. one of the reported failing boots (Henri):
>
> FreeBSD clang version 5.0.0 (trunk 308421) (based on LLVM 5.0.0svn)
> VT: init without driver.
>
>
> It looks like the problem is for production-style
> (non-debug) builds.

 Good catch,

 I now have the same problem, I'll look into it.

--
Emmanuel Vadot <[hidden email]> <[hidden email]>
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: PINE64+ Release APs, APs not started

Mark Millard-2

On 2017-Jul-27, at 11:59 AM, Emmanuel Vadot <[hidden email]> wrote:

> On Thu, 27 Jul 2017 11:26:19 -0700
> Mark Millard <[hidden email]> wrote:
>
>> On 2017-Jul-27, at 10:57 AM, Emmanuel Vadot <manu at bidouilliste.com> wrote:
>>
>>> On Thu, 27 Jul 2017 18:34:53 +0200
>>> Henri Hennebert <hlh at restart.be> wrote:
>>>
>>>> On 07/27/2017 17:02, Emmanuel Vadot wrote:
>>>>> On Thu, 27 Jul 2017 15:57:40 +0100
>>>>> Andrew Turner <[hidden email]> wrote:
>>>>>
>>>>>>
>>>>>>> On 27 Jul 2017, at 15:43, Emmanuel Vadot <[hidden email]> wrote:
>>>>>>>
>>>>>>> On Thu, 27 Jul 2017 14:31:18 +0200
>>>>>>> Henri Hennebert <[hidden email] <mailto:[hidden email]>> wrote:
>>>>>>>> I think that the DTB is wrong.
>>>>>>>>
>>>>>>>> Note that my kernel config have:
>>>>>>>>
>>>>>>>> options         FDT                     # Flattened Device Tree bus driver
>>>>>>>> options         FDT_DTB_STATIC          # Statically embed a DTB file
>>>>>>>> into a kernel image
>>>>>>>> makeoptions     FDT_DTS_FILE=pine64_plus.dts
>>>>>>>
>>>>>>> FDT_DTB_STATIC shouldn't be used unless you *exactly* know what you're
>>>>>>> doing. Please use GENERIC kernel on ARM64.
>>>>
>>>> I will remove it from my kernel config.
>>>
>>> I've just tested latest head with me soon to be u-boot-pine64 port and
>>> I don't have any problems.
>>> I've corrected the dram/pll_ddr problem (but it shouldn't change
>>> anything)
>>>
>>> Boot log : https://people.freebsd.org/~manu/pine64_bootlog.txt
>>
>> Your (Emmanuel's) reported boot:
>>
>> FreeBSD clang version 5.0.0 (trunk 308421) (based on LLVM 5.0.0svn)
>> WARNING: WITNESS option enabled, expect reduced performance.
>> VT: init without driver.
>>
>> vs. one of the reported failing boots (Henri):
>>
>> FreeBSD clang version 5.0.0 (trunk 308421) (based on LLVM 5.0.0svn)
>> VT: init without driver.
>>
>>
>> It looks like the problem is for production-style
>> (non-debug) builds.
>
> Good catch,
>
> I now have the same problem, I'll look into it.

Based on Henri H. reporting:

A) -r320599 working
B) -r320869 not working

and looking around at:

https://svnweb.freebsd.org/base/head/sys/arm/allwinner/?sortby=rev&sortdir=down&pathrev=320869#dirlist

it looks like -r320612 may have made the difference.

But I note that it is described in part with:

"USB is not working for now"

so it appears that it was expected to have a significant
regression-status for now. (I've historically run with the
root ufs file system on a USB SSD, both for Pine64+ 2GB
and RPI3. But it has been a significant time since I've
updated: pre-INO64.)


===
Mark Millard
markmi at dsl-only.net

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: PINE64+ Release APs, APs not started

Henri Hennebert
In reply to this post by Henri Hennebert
On 07/27/2017 18:34, Henri Hennebert wrote:

> On 07/27/2017 17:02, Emmanuel Vadot wrote:
>> On Thu, 27 Jul 2017 15:57:40 +0100
>> Andrew Turner <[hidden email]> wrote:
>>
>>>
>>>> On 27 Jul 2017, at 15:43, Emmanuel Vadot <[hidden email]> wrote:
>>>>
>>>> On Thu, 27 Jul 2017 14:31:18 +0200
>>>> Henri Hennebert <[hidden email] <mailto:[hidden email]>> wrote:
>>>>> I think that the DTB is wrong.
>>>>>
>>>>> Note that my kernel config have:
>>>>>
>>>>> options         FDT                     # Flattened Device Tree bus
>>>>> driver
>>>>> options         FDT_DTB_STATIC          # Statically embed a DTB file
>>>>> into a kernel image
>>>>> makeoptions     FDT_DTS_FILE=pine64_plus.dts
>>>>
>>>> FDT_DTB_STATIC shouldn't be used unless you *exactly* know what you're
>>>> doing. Please use GENERIC kernel on ARM64.
>
> I will remove it from my kernel config.
>

I retry with your u-boot:

U-Boot SPL 2017.07-00011-g41b31da7ca-dirty (Jul 27 2017 - 07:37:57)
DRAM: 2048 MiB
Trying to boot from MMC1

 >> FreeBSD EFI boot block
    Loader path: /boot/loader.efi

    Initializing modules: ZFS UFS
    Probing 5 block devices.......* done
     ZFS found no pools
     UFS found 1 partition
Consoles: EFI console
Command line arguments: loader.efi
Image base: 0xb6dbd008
EFI version: 2.05
EFI Firmware: Das U-boot (rev 0.00)

FreeBSD/arm64 EFI loader, Revision 1.1
(Tue Jul 25 03:58:20 CEST 2017 [hidden email])
EFI boot environment
Loading /boot/defaults/loader.conf
/boot/kernel/kernel text=0x71e548 data=0x9cc80+0x39e6a6
syms=[0x8+0xf6d80+0x8+0xeaf3b]
/boot/entropy size=0x1000
/boot/kernel/zfs.ko text=0x7a418 text=0xdc390 data=0x11528+0x9e970
syms=[0x8+0x1ddd8+0x8+0x18d38]
/boot/kernel/opensolaris.ko text=0x1358 text=0xd90 data=0x10160+0x125d0
syms=[0x8+0x1020+0x8+0x8ca]

Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...
Using DTB provided by EFI at 0x48000000.
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 1992-2017 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
         The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 12.0-CURRENT #0 r321371M: Thu Jul 27 19:52:17 CEST 2017
     [hidden email]:/usr/obj/usr/src/sys/NORQUAY arm64
FreeBSD clang version 5.0.0 (trunk 308421) (based on LLVM 5.0.0svn)
VT: init without driver.
Starting CPU 1 (1)
Starting CPU 2 (2)
Starting CPU 3 (3)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
random: unblocking device.
random: entropy device external interface
kbd0 at kbdmux0
ofwbus0: <Open Firmware Device Tree>
clk_fixed0: <Fixed clock> on ofwbus0
clk_fixed1: <Fixed clock> on ofwbus0
clk_fixed2: <Fixed clock> on ofwbus0
simplebus0: <Flattened device tree simple bus> on ofwbus0
aw_ccung0: <Allwinner Clock Control Unit NG> mem 0x1c20000-0x1c203ff on
simplebus0
aw_ccung0: Cannot set parent to pll_ddr for dram
regfix0: <Fixed Regulator> on ofwbus0
psci0: <ARM Power State Co-ordination Interface Driver> on ofwbus0
awusbphy0: <Allwinner USB PHY> mem
0x1c19400-0x1c19413,0x1c1a800-0x1c1a803,0x1c1b800-0x1c1b803 on simplebus0
gic0: <ARM Generic Interrupt Controller> mem
0x1c81000-0x1c81fff,0x1c82000-0x1c83fff,0x1c84000-0x1c85fff,0x1c86000-0x1c87fff
irq 210
gic0: pn 0x2, arch 0x2, rev 0x1, implementer 0x43b irqs 224
gpio0: <Allwinner GPIO/Pinmux controller> mem 0x1c20800-0x1c20bff irq
10,11,12 on simplebus0
gpiobus0: <OFW GPIO bus> on gpio0
gpio1: <Allwinner GPIO/Pinmux controller> mem 0x1f02c00-0x1f02fff irq 24
on simplebus0
gpiobus1: <OFW GPIO bus> on gpio1
generic_timer0: <ARMv8 Generic Timer> irq 0,1,2,3 on ofwbus0
Timecounter "ARM MPCore Timecounter" frequency 24000000 Hz quality 1000
Event timer "ARM MPCore Eventtimer" frequency 24000000 Hz quality 1000
rtc0: <Allwinner RTC> mem 0x1f00000-0x1f00053 irq 22,23 on simplebus0
rtc0: registered as a time-of-day clock, resolution 1.000000s
cpulist0: <Open Firmware CPU Group> on ofwbus0
cpu0: <Open Firmware CPU> on cpulist0
cpu1: <Open Firmware CPU> on cpulist0
cpu2: <Open Firmware CPU> on cpulist0
cpu3: <Open Firmware CPU> on cpulist0
a10_mmc0: <Allwinner Integrated MMC/SD controller> mem
0x1c0f000-0x1c0ffff irq 4 on simplebus0
mmc0: <MMC/SD bus> on a10_mmc0
ohci0: <Generic OHCI Controller> mem 0x1c1b400-0x1c1b4ff irq 9 on simplebus0
usbus0 on ohci0
gpioc0: <GPIO controller> on gpio0
uart0: <16750 or compatible> mem 0x1c28000-0x1c283ff irq 13 on simplebus0
uart0: console (115384,n,8,1)
gpioc1: <GPIO controller> on gpio1
awg0: <Allwinner Gigabit Ethernet> mem
0x1c30000-0x1c31fff,0x1c00030-0x1c00033 irq 25 on simplebus0
miibus0: <MII bus> on awg0
rgephy0: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 0 on miibus0
rgephy0:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX,
100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, w
rgephy1: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 1 on miibus0
rgephy1:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX,
100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, w
awg0: Ethernet address: 02:ba:cf:46:d5:39
cryptosoft0: <software crypto>
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
Timecounters tick every 1.000 msec
usbus0: 12Mbps Full Speed USB v1.0
ugen0.1: <Generic OHCI root HUB> at usbus0
uhub0: <Generic OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
device_attach: uhub0 attach returned 6
usbus0: Root HUB problem, error=USB_ERR_NO_ROOT_HUB
mmcsd0: 16GB <SDHC SL16G 8.0 SN A9A41D45 MFG 03/2017 by 3 SD> at mmc0
50.0MHz/4bit/65535-block
Release APs
APs not started
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: (null) (null) r0p0 affinity:  0
CPU  2: (null) (null) r0p0 affinity:  0
CPU  3: (null) (null) r0p0 affinity:  0
   x0: ffff000000967f00
   x1: fffffd0ø

But the Release APs don't work.

I retry with the old u-boot and the Release APs don't work either.

With your u-boot and r320599 (with the embeded DTB) I get the same
strange boot as before (no aw_ccung). So the embeded DTB is the culprit.

Henri
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: PINE64+ Release APs, APs not started

Emmanuel Vadot-7
On Fri, 28 Jul 2017 09:15:52 +0200
Henri Hennebert <[hidden email]> wrote:

> On 07/27/2017 18:34, Henri Hennebert wrote:
> > On 07/27/2017 17:02, Emmanuel Vadot wrote:
> >> On Thu, 27 Jul 2017 15:57:40 +0100
> >> Andrew Turner <[hidden email]> wrote:
> >>
> >>>
> >>>> On 27 Jul 2017, at 15:43, Emmanuel Vadot <[hidden email]> wrote:
> >>>>
> >>>> On Thu, 27 Jul 2017 14:31:18 +0200
> >>>> Henri Hennebert <[hidden email] <mailto:[hidden email]>> wrote:
> >>>>> I think that the DTB is wrong.
> >>>>>
> >>>>> Note that my kernel config have:
> >>>>>
> >>>>> options         FDT                     # Flattened Device Tree bus
> >>>>> driver
> >>>>> options         FDT_DTB_STATIC          # Statically embed a DTB file
> >>>>> into a kernel image
> >>>>> makeoptions     FDT_DTS_FILE=pine64_plus.dts
> >>>>
> >>>> FDT_DTB_STATIC shouldn't be used unless you *exactly* know what you're
> >>>> doing. Please use GENERIC kernel on ARM64.
> >
> > I will remove it from my kernel config.
> >
>
> I retry with your u-boot:
>
> U-Boot SPL 2017.07-00011-g41b31da7ca-dirty (Jul 27 2017 - 07:37:57)
> DRAM: 2048 MiB
> Trying to boot from MMC1
>
>  >> FreeBSD EFI boot block
>     Loader path: /boot/loader.efi
>
>     Initializing modules: ZFS UFS
>     Probing 5 block devices.......* done
>      ZFS found no pools
>      UFS found 1 partition
> Consoles: EFI console
> Command line arguments: loader.efi
> Image base: 0xb6dbd008
> EFI version: 2.05
> EFI Firmware: Das U-boot (rev 0.00)
>
> FreeBSD/arm64 EFI loader, Revision 1.1
> (Tue Jul 25 03:58:20 CEST 2017 [hidden email])
> EFI boot environment
> Loading /boot/defaults/loader.conf
> /boot/kernel/kernel text=0x71e548 data=0x9cc80+0x39e6a6
> syms=[0x8+0xf6d80+0x8+0xeaf3b]
> /boot/entropy size=0x1000
> /boot/kernel/zfs.ko text=0x7a418 text=0xdc390 data=0x11528+0x9e970
> syms=[0x8+0x1ddd8+0x8+0x18d38]
> /boot/kernel/opensolaris.ko text=0x1358 text=0xd90 data=0x10160+0x125d0
> syms=[0x8+0x1020+0x8+0x8ca]
>
> Hit [Enter] to boot immediately, or any other key for command prompt.
> Booting [/boot/kernel/kernel]...
> Using DTB provided by EFI at 0x48000000.
> KDB: debugger backends: ddb
> KDB: current backend: ddb
> Copyright (c) 1992-2017 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
>          The Regents of the University of California. All rights reserved.
> FreeBSD is a registered trademark of The FreeBSD Foundation.
> FreeBSD 12.0-CURRENT #0 r321371M: Thu Jul 27 19:52:17 CEST 2017
>      [hidden email]:/usr/obj/usr/src/sys/NORQUAY arm64
> FreeBSD clang version 5.0.0 (trunk 308421) (based on LLVM 5.0.0svn)
> VT: init without driver.
> Starting CPU 1 (1)
> Starting CPU 2 (2)
> Starting CPU 3 (3)
> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
> random: unblocking device.
> random: entropy device external interface
> kbd0 at kbdmux0
> ofwbus0: <Open Firmware Device Tree>
> clk_fixed0: <Fixed clock> on ofwbus0
> clk_fixed1: <Fixed clock> on ofwbus0
> clk_fixed2: <Fixed clock> on ofwbus0
> simplebus0: <Flattened device tree simple bus> on ofwbus0
> aw_ccung0: <Allwinner Clock Control Unit NG> mem 0x1c20000-0x1c203ff on
> simplebus0
> aw_ccung0: Cannot set parent to pll_ddr for dram
> regfix0: <Fixed Regulator> on ofwbus0
> psci0: <ARM Power State Co-ordination Interface Driver> on ofwbus0
> awusbphy0: <Allwinner USB PHY> mem
> 0x1c19400-0x1c19413,0x1c1a800-0x1c1a803,0x1c1b800-0x1c1b803 on simplebus0
> gic0: <ARM Generic Interrupt Controller> mem
> 0x1c81000-0x1c81fff,0x1c82000-0x1c83fff,0x1c84000-0x1c85fff,0x1c86000-0x1c87fff
> irq 210
> gic0: pn 0x2, arch 0x2, rev 0x1, implementer 0x43b irqs 224
> gpio0: <Allwinner GPIO/Pinmux controller> mem 0x1c20800-0x1c20bff irq
> 10,11,12 on simplebus0
> gpiobus0: <OFW GPIO bus> on gpio0
> gpio1: <Allwinner GPIO/Pinmux controller> mem 0x1f02c00-0x1f02fff irq 24
> on simplebus0
> gpiobus1: <OFW GPIO bus> on gpio1
> generic_timer0: <ARMv8 Generic Timer> irq 0,1,2,3 on ofwbus0
> Timecounter "ARM MPCore Timecounter" frequency 24000000 Hz quality 1000
> Event timer "ARM MPCore Eventtimer" frequency 24000000 Hz quality 1000
> rtc0: <Allwinner RTC> mem 0x1f00000-0x1f00053 irq 22,23 on simplebus0
> rtc0: registered as a time-of-day clock, resolution 1.000000s
> cpulist0: <Open Firmware CPU Group> on ofwbus0
> cpu0: <Open Firmware CPU> on cpulist0
> cpu1: <Open Firmware CPU> on cpulist0
> cpu2: <Open Firmware CPU> on cpulist0
> cpu3: <Open Firmware CPU> on cpulist0
> a10_mmc0: <Allwinner Integrated MMC/SD controller> mem
> 0x1c0f000-0x1c0ffff irq 4 on simplebus0
> mmc0: <MMC/SD bus> on a10_mmc0
> ohci0: <Generic OHCI Controller> mem 0x1c1b400-0x1c1b4ff irq 9 on simplebus0
> usbus0 on ohci0
> gpioc0: <GPIO controller> on gpio0
> uart0: <16750 or compatible> mem 0x1c28000-0x1c283ff irq 13 on simplebus0
> uart0: console (115384,n,8,1)
> gpioc1: <GPIO controller> on gpio1
> awg0: <Allwinner Gigabit Ethernet> mem
> 0x1c30000-0x1c31fff,0x1c00030-0x1c00033 irq 25 on simplebus0
> miibus0: <MII bus> on awg0
> rgephy0: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 0 on miibus0
> rgephy0:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX,
> 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, w
> rgephy1: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 1 on miibus0
> rgephy1:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX,
> 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, w
> awg0: Ethernet address: 02:ba:cf:46:d5:39
> cryptosoft0: <software crypto>
> ZFS filesystem version: 5
> ZFS storage pool version: features support (5000)
> Timecounters tick every 1.000 msec
> usbus0: 12Mbps Full Speed USB v1.0
> ugen0.1: <Generic OHCI root HUB> at usbus0
> uhub0: <Generic OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
> device_attach: uhub0 attach returned 6
> usbus0: Root HUB problem, error=USB_ERR_NO_ROOT_HUB
> mmcsd0: 16GB <SDHC SL16G 8.0 SN A9A41D45 MFG 03/2017 by 3 SD> at mmc0
> 50.0MHz/4bit/65535-block
> Release APs
> APs not started
> 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: (null) (null) r0p0 affinity:  0
> CPU  2: (null) (null) r0p0 affinity:  0
> CPU  3: (null) (null) r0p0 affinity:  0
>    x0: ffff000000967f00
>    x1: fffffd0ø
>
> But the Release APs don't work.
>
> I retry with the old u-boot and the Release APs don't work either.
>
> With your u-boot and r320599 (with the embeded DTB) I get the same
> strange boot as before (no aw_ccung). So the embeded DTB is the culprit.
>
> Henri

 Can you please try using the latest source and use GENERIC and
GENERIC-NODEBUG just to see if we do see the same problem please ?

 My overdrive 1000 is currently building world up to the latest source
so I can see if -NODEBUG work on it or not.

--
Emmanuel Vadot <[hidden email]> <[hidden email]>
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: PINE64+ Release APs, APs not started

Henri Hennebert
On 07/28/2017 10:29, Emmanuel Vadot wrote:

> On Fri, 28 Jul 2017 09:15:52 +0200
> Henri Hennebert <[hidden email]> wrote:
>
>
>   Can you please try using the latest source and use GENERIC and
> GENERIC-NODEBUG just to see if we do see the same problem please ?
>
>   My overdrive 1000 is currently building world up to the latest source
> so I can see if -NODEBUG work on it or not.
>
I build GENERIC-DEBUG from r321649 and get this:

U-Boot SPL 2017.07-00011-g41b31da7ca-dirty (Jul 27 2017 - 07:37:57)
DRAM: 2048 MiB
Trying to boot from MMC1

 >> FreeBSD EFI boot block
    Loader path: /boot/loader.efi

    Initializing modules: ZFS UFS
    Probing 5 block devices.......* done
     ZFS found no pools
     UFS found 1 partition
Consoles: EFI console
Command line arguments: loader.efi
Image base: 0xb6dbd008
EFI version: 2.05
EFI Firmware: Das U-boot (rev 0.00)

FreeBSD/arm64 EFI loader, Revision 1.1
(Tue Jul 25 03:58:20 CEST 2017 [hidden email])
EFI boot environment
Loading /boot/defaults/loader.conf
/boot/kernel/kernel text=0x7c2010 data=0xa2980+0x39d0de
syms=[0x8+0x106980+0x8+0xfb2a4]
/boot/entropy size=0x1000
/boot/kernel/zfs.ko text=0x7a418 text=0xdc3b0 data=0x11528+0x9e970
syms=[0x8+0x1ddd8+0x8+0x18d38]
/boot/kernel/opensolaris.ko text=0x1358 text=0xd90 data=0x10160+0x125d0
syms=[0x8+0x1020+0x8+0x8ca]

Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...
Using DTB provided by EFI at 0x48000000.
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 1992-2017 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
         The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 12.0-CURRENT #0 r321649M: Fri Jul 28 13:54:42 CEST 2017
     [hidden email]:/usr/obj/usr/src/sys/GENERIC-NODEBUG arm64
FreeBSD clang version 5.0.0 (trunk 308421) (based on LLVM 5.0.0svn)
VT: init without driver.
Starting CPU 1 (1)
Starting CPU 2 (2)
Starting CPU 3 (3)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
random: unblocking device.
random: entropy device external interface
kbd0 at kbdmux0
ofwbus0: <Open Firmware Device Tree>
clk_fixed0: <Fixed clock> on ofwbus0
clk_fixed1: <Fixed clock> on ofwbus0
clk_fixed2: <Fixed clock> on ofwbus0
simplebus0: <Flattened device tree simple bus> on ofwbus0
aw_ccung0: <Allwinner Clock Control Unit NG> mem 0x1c20000-0x1c203ff on
simplebus0
iichb0: <Allwinner Integrated I2C Bus Controller> mem
0x1c2b000-0x1c2b3ff irq 19 on simplebus0
iicbus0: <OFW I2C bus> on iichb0
regfix0: <Fixed Regulator> on ofwbus0
psci0: <ARM Power State Co-ordination Interface Driver> on ofwbus0
awusbphy0: <Allwinner USB PHY> mem
0x1c19400-0x1c19413,0x1c1a800-0x1c1a803,0x1c1b800-0x1c1b803 on simplebus0
gic0: <ARM Generic Interrupt Controller> mem
0x1c81000-0x1c81fff,0x1c82000-0x1c83fff,0x1c84000-0x1c85fff,0x1c86000-0x1c87fff
irq 210
gic0: pn 0x2, arch 0x2, rev 0x1, implementer 0x43b irqs 224
gpio0: <Allwinner GPIO/Pinmux controller> mem 0x1c20800-0x1c20bff irq
10,11,12 on simplebus0
gpiobus0: <OFW GPIO bus> on gpio0
gpio1: <Allwinner GPIO/Pinmux controller> mem 0x1f02c00-0x1f02fff irq 24
on simplebus0
gpiobus1: <OFW GPIO bus> on gpio1
generic_timer0: <ARMv8 Generic Timer> irq 0,1,2,3 on ofwbus0
Timecounter "ARM MPCore Timecounter" frequency 24000000 Hz quality 1000
Event timer "ARM MPCore Eventtimer" frequency 24000000 Hz quality 1000
rtc0: <Allwinner RTC> mem 0x1f00000-0x1f00053 irq 22,23 on simplebus0
rtc0: registered as a time-of-day clock, resolution 1.000000s
cpulist0: <Open Firmware CPU Group> on ofwbus0
cpu0: <Open Firmware CPU> on cpulist0
cpu1: <Open Firmware CPU> on cpulist0
cpu2: <Open Firmware CPU> on cpulist0
cpu3: <Open Firmware CPU> on cpulist0
a10_mmc0: <Allwinner Integrated MMC/SD controller> mem
0x1c0f000-0x1c0ffff irq 4 on simplebus0
mmc0: <MMC/SD bus> on a10_mmc0
ohci0: <Generic OHCI Controller> mem 0x1c1b400-0x1c1b4ff irq 9 on simplebus0
usbus0 on ohci0
gpioc0: <GPIO controller> on gpio0
uart0: <16750 or compatible> mem 0x1c28000-0x1c283ff irq 13 on simplebus0
uart0: console (115384,n,8,1)
iic0: <I2C generic I/O> on iicbus0
gpioc1: <GPIO controller> on gpio1
awg0: <Allwinner Gigabit Ethernet> mem
0x1c30000-0x1c31fff,0x1c00030-0x1c00033 irq 25 on simplebus0
miibus0: <MII bus> on awg0
rgephy0: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 0 on miibus0
rgephy0:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX,
100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, w
rgephy1: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 1 on miibus0
rgephy1:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX,
100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, w
awg0: Ethernet address: 02:ba:cf:46:d5:39
cryptosoft0: <software crypto>
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
Timecounters tick every 1.000 msec
usbus0: 12Mbps Full Speed USB v1.0
ugen0.1: <Generic OHCI root HUB> at usbus0
uhub0: <Generic OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
uhub_attach: getting USB 2.0 HUB descriptor failed,error=USB_ERR_SHORT_XFER
device_attach: uhub0 attach returned 6
usbus0: Root HUB problem, error=USB_ERR_NO_ROOT_HUB
mmcsd0: 16GB <SDHC SL16G 8.0 SN A9A41D45 MFG 03/2017 by 3 SD> at mmc0
50.0MHz/4bit/65535-block
Release APs
APs not started
   x0: ffff000000a11280
   x1: f

Henri
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: PINE64+ Release APs, APs not started

Henri Hennebert
In reply to this post by Emmanuel Vadot-7

>
>   Can you please try using the latest source and use GENERIC and
> GENERIC-NODEBUG just to see if we do see the same problem please ?
>
>   My overdrive 1000 is currently building world up to the latest source
> so I can see if -NODEBUG work on it or not.
>
I build GENERIC from r321649 and get this:

U-Boot SPL 2017.07-00011-g41b31da7ca-dirty (Jul 27 2017 - 07:37:57)
DRAM: 2048 MiB
Trying to boot from MMC1

 >> FreeBSD EFI boot block
    Loader path: /boot/loader.efi

    Initializing modules: ZFS UFS
    Probing 5 block devices.......* done
     ZFS found no pools
     UFS found 1 partition
Consoles: EFI console
Command line arguments: loader.efi
Image base: 0xb6dbd008
EFI version: 2.05
EFI Firmware: Das U-boot (rev 0.00)

FreeBSD/arm64 EFI loader, Revision 1.1
(Tue Jul 25 03:58:20 CEST 2017 [hidden email])
EFI boot environment
Loading /boot/defaults/loader.conf
/boot/kernel/kernel text=0x7bccf8 data=0xa4000+0x43c1e2
syms=[0x8+0x109368+0x8+0xfd93d]
/boot/entropy size=0x1000
/boot/kernel/zfs.ko text=0x923a8 text=0x10bc40 data=0x11540+0x9f9d0
syms=[0x8+0x1e8d0+0x8+0x19400]
/boot/kernel/opensolaris.ko text=0x14f8 text=0x1000 data=0x10160+0x125d0
syms=[0x8+0x1068+0x8+0x906]

Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...
Using DTB provided by EFI at 0x48000000.
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 1992-2017 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
         The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 12.0-CURRENT #0 r321649M: Fri Jul 28 17:11:01 CEST 2017
     [hidden email]:/usr/obj/usr/src/sys/GENERIC arm64
FreeBSD clang version 5.0.0 (trunk 308421) (based on LLVM 5.0.0svn)
WARNING: WITNESS option enabled, expect reduced performance.
VT: init without driver.
Starting CPU 1 (1)
Starting CPU 2 (2)
Starting CPU 3 (3)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
random: unblocking device.
random: entropy device external interface
kbd0 at kbdmux0
ofwbus0: <Open Firmware Device Tree>
clk_fixed0: <Fixed clock> on ofwbus0
clk_fixed1: <Fixed clock> on ofwbus0
clk_fixed2: <Fixed clock> on ofwbus0
simplebus0: <Flattened device tree simple bus> on ofwbus0
aw_ccung0: <Allwinner Clock Control Unit NG> mem 0x1c20000-0x1c203ff on
simplebus0
iichb0: <Allwinner Integrated I2C Bus Controller> mem
0x1c2b000-0x1c2b3ff irq 19 on simplebus0
iicbus0: <OFW I2C bus> on iichb0
regfix0: <Fixed Regulator> on ofwbus0
psci0: <ARM Power State Co-ordination Interface Driver> on ofwbus0
awusbphy0: <Allwinner USB PHY> mem
0x1c19400-0x1c19413,0x1c1a800-0x1c1a803,0x1c1b800-0x1c1b803 on simplebus0
gic0: <ARM Generic Interrupt Controller> mem
0x1c81000-0x1c81fff,0x1c82000-0x1c83fff,0x1c84000-0x1c85fff,0x1c86000-0x1c87fff
irq 210
gic0: pn 0x2, arch 0x2, rev 0x1, implementer 0x43b irqs 224
gpio0: <Allwinner GPIO/Pinmux controller> mem 0x1c20800-0x1c20bff irq
10,11,12 on simplebus0
gpiobus0: <OFW GPIO bus> on gpio0
gpio1: <Allwinner GPIO/Pinmux controller> mem 0x1f02c00-0x1f02fff irq 24
on simplebus0
gpiobus1: <OFW GPIO bus> on gpio1
generic_timer0: <ARMv8 Generic Timer> irq 0,1,2,3 on ofwbus0
Timecounter "ARM MPCore Timecounter" frequency 24000000 Hz quality 1000
Event timer "ARM MPCore Eventtimer" frequency 24000000 Hz quality 1000
rtc0: <Allwinner RTC> mem 0x1f00000-0x1f00053 irq 22,23 on simplebus0
rtc0: registered as a time-of-day clock, resolution 1.000000s
cpulist0: <Open Firmware CPU Group> on ofwbus0
cpu0: <Open Firmware CPU> on cpulist0
cpu1: <Open Firmware CPU> on cpulist0
cpu2: <Open Firmware CPU> on cpulist0
cpu3: <Open Firmware CPU> on cpulist0
a10_mmc0: <Allwinner Integrated MMC/SD controller> mem
0x1c0f000-0x1c0ffff irq 4 on simplebus0
mmc0: <MMC/SD bus> on a10_mmc0
ohci0: <Generic OHCI Controller> mem 0x1c1b400-0x1c1b4ff irq 9 on simplebus0
usbus0 on ohci0
gpioc0: <GPIO controller> on gpio0
uart0: <16750 or compatible> mem 0x1c28000-0x1c283ff irq 13 on simplebus0
uart0: console (115384,n,8,1)
iic0: <I2C generic I/O> on iicbus0
gpioc1: <GPIO controller> on gpio1
awg0: <Allwinner Gigabit Ethernet> mem
0x1c30000-0x1c31fff,0x1c00030-0x1c00033 irq 25 on simplebus0
miibus0: <MII bus> on awg0
rgephy0: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 0 on miibus0
rgephy0:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX,
100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, w
rgephy1: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 1 on miibus0
rgephy1:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX,
100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, w
awg0: Ethernet address: 02:ba:cf:46:d5:39
cryptosoft0: <software crypto>
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
Timecounters tick every 1.000 msec
usbus0: 12Mbps Full Speed USB v1.0
ugen0.1: <Generic OHCI root HUB> at usbus0
uhub0: <Generic OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
uhub_attach: getting USB 2.0 HUB descriptor failed,error=USB_ERR_SHORT_XFER
device_attach: uhub0 attach returned 6
usbus0: Root HUB problem, error=USB_ERR_NO_ROOT_HUB
mmcsd0: 16GB <SDHC SL16G 8.0 SN A9A41D45 MFG 03/2017 by 3 SD> at mmc0
50.0MHz/4bit/65535-block
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
WARNING: WITNESS option enabled, expect reduced performance.
Trying to mount root from zfs:rpool/ROOT/default [rw,noatime]...
Solaris: NOTICE: Cannot find the pool label for 'rpool'
Mounting from zfs:rpool/ROOT/default failed with error 5.

Loader variables:
   vfs.root.mountfrom=zfs:rpool/ROOT/default
   vfs.root.mountfrom.options=rw,noatime

Manual root filesystem specification:
   <fstype>:<device> [options]
       Mount <device> using filesystem <fstype>
       and with the specified (optional) option list.

     eg. ufs:/dev/da0s1a
         zfs:tank
         cd9660:/dev/cd0 ro
           (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /)

   ?               List valid disk boot devices
   .               Yield 1 second (for background tasks)
   <empty line>    Abort manual input

mountroot>

Note device_attach: uhub0 attach returned 6

I retry 5 times with the same result.

Henri
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: PINE64+ Release APs, APs not started

Mark Millard-2
On 2017-Jul-28, at 9:22 AM, Henri Hennebert <hlh at restart.be> wrote:

. . .
> usbus0: 12Mbps Full Speed USB v1.0
> ugen0.1: <Generic OHCI root HUB> at usbus0
> uhub0: <Generic OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
> uhub_attach: getting USB 2.0 HUB descriptor failed,error=USB_ERR_SHORT_XFER
> device_attach: uhub0 attach returned 6
> usbus0: Root HUB problem, error=USB_ERR_NO_ROOT_HUB
. . .


-r320612 is described in part with:

"USB is not working for now"

for A64 contexts. So if I understand
right the above sort of thing is expected
for now.

The update has unfortunately temporarily
regressed significant functionality for
A64. Hopefully this status is not intended
to last all that long.

===
Mark Millard
markmi at dsl-only.net

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: PINE64+ Release APs, APs not started - a solution...

Henri Hennebert
In reply to this post by Henri Hennebert
On 07/25/2017 19:22, Henri Hennebert 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 ?
>
> Henri

If I boot with kernel r320599 (unload; load /boot/kernel.r320599/kernel;
set module_path=/boot/kernel.r320599; load zfs; load opensolaris; boot),
the boot complete without problem.
Then I do a shutdown -r now to reboot with my default kernel
(/boot/kernel) the boot complete without problem:

[root@norquay ~]# uname -a
FreeBSD norquay.restart.bel 12.0-CURRENT FreeBSD 12.0-CURRENT #0
r322109M: Wed Aug  9 17:16:41 CEST 2017
[hidden email]:/usr/obj/usr/src/sys/NORQUAY  arm64

with my rpool on 2 USB disks connected to a self powered hub:

root@norquay ~]# zpool status
   pool: rpool
  state: ONLINE
   scan: scrub repaired 0 in 3h3m with 0 errors on Sat Jul 29 16:33:00 2017
config:

        NAME               STATE     READ WRITE CKSUM
        rpool              ONLINE       0     0     0
          mirror-0         ONLINE       0     0     0
            gpt/disk0-zfs  ONLINE       0     0     0
            gpt/disk1-zfs  ONLINE       0     0     0

errors: No known data errors


BUT after a power off power on, this same kernel encounter the
  APs not started error.

If I boot with /boot/kernel.r320599 and then do a shutdown -r now
the r322109 boot without problem.

Henri
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[hidden email]"