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

[Peter Robinson]

On Fri, Mar 8, 2019 at 6:34 PM Jagan Teki <jagan at amarulasolutions.com> wrote:
>
> On Fri, Mar 8, 2019 at 11:32 PM Peter Robinson <pbrobinson at gmail.com> wrote:
> >
> > Hey Tom and Jagan,
> >
> > > Hey all,
> > >
> > > So it's release day and I've put up v2019.04-rc3, I've updated git and
> > > the tarballs are also up now.
> > >
> > > Thanks again to having signed tags, between -rc2 and -rc3 we have a good
> > > changelog under 'git log --merges v2019.04-rc2..v2019.04-rc3'
> > >
> > > We're looking at release on April 8th, 2019.
> >
> > I've had reports of crashes on AllWinner A20 devices, at least
> > Cubieboard2, CubieTruck and BananaPi, with rc2/rc3 (I'm not 100% sure
> > when it started) in Fedora. I'm suspecting some of the DM migration
> > here.
> >
> > Are either of you aware of any issues there?
> >
> > Crash below.
> >
> > Regards,
> > Peter
> >
> > U-Boot SPL 2019.04-rc3 (Mar 05 2019 - 14:49:53 +0000)
> > DRAM: 2048 MiB
> > CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
> > Trying to boot from MMC1
> >
> >
> > U-Boot 2019.04-rc3 (Mar 05 2019 - 14:49:53 +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... ** No valid partitions found **
> > 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
> > switch to partitions #0, OK
> > mmc0 is current device
> > ** Invalid partition 1 **
>
> are you sure, your sd has partitions?
>
> Can you switch mmc dev and check the contents, mean while I can try it
> on A20 later tomorrow.

these devices boot with the version we shipped with F-29, which was
2018.09 and the users report if they reflash back to that version it
works.

Peter