On Sat, Jan 6, 2018 at 12:10 AM, Kevin Hilman <khilman@xxxxxxxxxxxx> wrote: > On Wed, Dec 13, 2017 at 11:46 AM, Kevin Hilman <khilman@xxxxxxxxxxxx> wrote: >> On Wed, Dec 13, 2017 at 9:13 AM, Priit Laes <plaes@xxxxxxxxx> wrote: >>> On Wed, Dec 13, 2017 at 05:09:33PM +0000, Priit Laes wrote: >>>> On Tue, Dec 12, 2017 at 01:24:52PM -0800, Kevin Hilman wrote: >>>> > On Tue, Dec 12, 2017 at 9:26 AM, Priit Laes <plaes@xxxxxxxxx> wrote: >>>> > > On Mon, Dec 11, 2017 at 02:22:30PM -0800, Kevin Hilman wrote: >>>> > >> On Sun, Mar 26, 2017 at 10:20 AM, Priit Laes <plaes@xxxxxxxxx> wrote: >>>> > >> > Convert sun4i-a10.dtsi to new CCU driver. >>>> > >> > >>>> > >> > Signed-off-by: Priit Laes <plaes@xxxxxxxxx> >>>> > >> >>>> > >> I finally got around to bisecting a mainline boot failure on >>>> > >> sun4i-a10-cubieboard that's been happening for quite a while. Based >>>> > >> on on kernelci.org, it showed up sometime during the v4.15 merge >>>> > >> window[1]. It bisected down to this commit (in mainline as commit >>>> > >> 41193869f2bdb585ce09bfdd16d9482aadd560ad). >>>> > >> >>>> > >> When it fails, there is no output on the serial console, so I don't >>>> > >> know exactly how it's failing, just that it no longer boots. >>>> > > >>>> > > We tried out latest 4.15 with various compilers and it works: >>>> > > - gcc version 7.1.1 20170622 (Red Hat Cross 7.1.1-3) (GCC) - A10 Gemei G9 tablet >>>> > > - gcc 7.2.0-debian - A10 Cubieboard >>>> > >>>> > And you can reproduce the bug with gcc5 or gcc6? >>>> >>>> Tried following commits on Gemei G9 (A10 tablet): >>>> * 4.15.0-rc3-00037-gd39a01eff9af - latest master >>>> * 4.14.0-rc1-00002-g41193869f2bd - the exact commit, causing the issue. >>>> >>>> With the same Linaro toolchain: >>>> (gcc version 5.3.1 20160412 (Linaro GCC 5.3-2016.05)) >>> >>> And I also tried the same dtb and zImage from kernelci page [1] and it works with >>> that too... >>> >>> https://storage.kernelci.org/mainline/master/v4.15-rc3/arm/sunxi_defconfig/ >> >> Can you share a full boot-log (including all the u-boot output etc.) >> so I can see exactly how the kernel is being loaded? Especially the >> u-boot version? >> >> As $SUBJECT patch seems to be changing clocks around, perhaps this is >> an issue where some u-boot dependency is uncovered, and older versions >> of u-boot don't play well with this change. > > Ping. > > This is still failing in mainline, but passing int stable <= v4.14 Just did a test with clean builds of v4.15-rc7 with sunxi_defconfig and U-boot 2018.01-rc3 with Cubieboard_defconfig. It successfully boots to a prompt. My previous bootloader was U-boot 2017.05 with some local modifications. Here is the full boot log: https://wens.tw/cb-boot-log.txt The boot script is: setenv bootargs console=tty0 console=ttyS0,115200n8 root=/dev/mmcblk0p1 rootwait panic=10 earlycon=uart,mmio32,0x01c28000 consoleblank=0 drm.debug=0x1e load ${devtype} ${devnum}:${distro_bootpart} ${kernel_addr_r} boot/zImage load ${devtype} ${devnum}:${distro_bootpart} ${fdt_addr_r} boot/${fdtfile} bootz ${kernel_addr_r} - ${fdt_addr_r} Regards ChenYu -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
