[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190815151616.2A298206C1@mail.kernel.org>
Date: Thu, 15 Aug 2019 08:16:15 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Mark Brown <broonie@...nel.org>
Cc: "kernelci.org bot" <bot@...nelci.org>,
Sylwester Nawrocki <s.nawrocki@...sung.com>,
enric.balletbo@...labora.com, guillaume.tucker@...labora.com,
khilman@...libre.com, matthew.hart@...aro.org,
mgalka@...labora.com, tomeu.vizoso@...labora.com,
Chen-Yu Tsai <wens@...e.org>,
Maxime Ripard <maxime.ripard@...tlin.com>,
Michael Turquette <mturquette@...libre.com>,
linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: clk/clk-next boot bisection: v5.3-rc1-79-g31f58d2f58cb on sun8i-h3-libretech-all-h3-cc
Quoting Mark Brown (2019-08-15 04:26:14)
> On Wed, Aug 14, 2019 at 09:02:20PM -0700, Stephen Boyd wrote:
> > Quoting kernelci.org bot (2019-08-14 20:35:25)
>
> > > clk/clk-next boot bisection: v5.3-rc1-79-g31f58d2f58cb on sun8i-h3-libretech-all-h3-cc
>
> > If this is the only board that failed, great! Must be something in a
> > sun8i driver that uses the init structure after registration.
>
> The infrastructure suppresses duplicate-seeming bisections so I'd not
> count on it, check the reports on the web site.
Hmm ok. I can remove the change from -next, but I'd still like to figure
out what is using the init pointer after registration. Is there a way to
get earlycon logs?
Powered by blists - more mailing lists