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)) > > Very strange that a DT only patch would cause a gcc related regression > and if it does, it should be investigated. I don't think requiring > gcc7 is an appropriate solution. > > @Chen-Yu, @Maxime: are you guys OK with requiring gcc7 for working > upstream boot for A10? > > Kevin > > -- > You received this message because you are subscribed to the Google Groups "linux-sunxi" group. > To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscribe@xxxxxxxxxxxxxxxx. > For more options, visit https://groups.google.com/d/optout. -- 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
