[U-Boot] [ANN] U-Boot v2019.04-rc3 released

[Jagan Teki]

On Thu, Mar 28, 2019 at 12:10 AM Peter Robinson <pbrobinson at gmail.com> wrote:
>
> > > Hi Jagan,
> > >
> > > Did you get a chance to test this? We've seen this on at least Cubie2,
> > > CubieTruck and BananaPi and it still persists with rc4
> >
> > I made a quick test on v2019.01 vs v2019.04-rc3, below are the
> > results. I even grab the reg dump for your information. please check
> > the same.
>
> So further testing on this from the people seeing the problem shows
> it's an issue when booting the OS off a SATA/AHCI attached device. So
> a mSD card with U-Boot on it and the rest of the OS on a SSD or
> similar, booting the OS off mSD works as expected.

Is sd issue still persist?

>
> Output:
>
> U-Boot SPL 2019.04-rc4 (Mar 20 2019 - 15:48:13 +0000)
> DRAM: 2048 MiB
> CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
> Trying to boot from MMC1
>
>
> U-Boot 2019.04-rc4 (Mar 20 2019 - 15:48:13 +0000) Allwinner Technology
>
> CPU:   Allwinner A20 (SUN7I)
> Model: Cubietech Cubietruck
> I2C:   ready
> DRAM:  2 GiB
> MMC:   mmc at 1c0f000: 0, mmc at 1c12000: 1
> Loading Environment from FAT... Unable to use mmc 0:2... Setting up a
> 1024x768 vga console (overscan 0x0)
> In:    serial
> Out:   vga
> Err:   vga
> Allwinner mUSB OTG (Peripheral)
> SCSI:  Target spinup took 0 ms.
> AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
> flags: ncq stag pm led clo only pmp pio slum part ccc apst
>
> Net:   sunxi_set_gate: (CLK#66) unhandled
> eth0: ethernet at 1c50000
> Warning: usb_ether using MAC address from ROM
> , eth1: usb_ether
> starting USB...
> USB0:   USB EHCI 1.00
> USB1:   USB OHCI 1.0
> USB2:   USB EHCI 1.00
> USB3:   USB OHCI 1.0
> scanning bus 0 for devices... 1 USB Device(s) found
> scanning bus 1 for devices... 1 USB Device(s) found
> scanning bus 2 for devices... 1 USB Device(s) found
> scanning bus 3 for devices... 1 USB Device(s) found
>        scanning usb for storage devices... 0 Storage Device(s) found
> Hit any key to stop autoboot:  0
> => scsi info
> => scsi reset
>
> Reset SCSI
> scanning bus for devices...
> data abort
> pc : [<bef8b82a>]          lr : [<bef86e51>]
> reloc pc : [<4a01c82a>]    lr : [<4a017e51>]
> sp : baf46b58  ip : 0000001c     fp : 000000c0
> r10: 00000000  r9 : baf4eed8     r8 : 00000000
> r7 : baf46dd8  r6 : befd4094     r5 : befdbd30  r4 : befdbd30
> r3 : 00000000  r2 : 00000000     r1 : ea000016  r0 : befdbd30
> Flags: nZcv  IRQs off  FIQs off  Mode SVC_32
> Code: e92dbd10 f8d045f0 b0858080 1000f8d8 (f8d14604)
> Resetting CPU ...

Have you reproduce the same in previous release? better bisect it.