Re: next/master bisection: baseline.login on qemu_arm-vexpress-a9

From: Rob Herring <robh@kernel.org>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	"kernelci-results@groups.io" <kernelci-results@groups.io>,
	devicetree@vger.kernel.org,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Liviu Dudau <liviu.dudau@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Subject: Re: next/master bisection: baseline.login on qemu_arm-vexpress-a9
Date: Mon, 27 Sep 2021 13:56:49 -0500	[thread overview]
Message-ID: <CAL_JsqLc_O9sk4nTiofo4r+87wNeqCz_cNKHfiz=apCG-ziANQ@mail.gmail.com> (raw)
In-Reply-To: <1e8409b3-0649-5d7c-da3f-911880b15c2e@collabora.com>

On Mon, Sep 27, 2021 at 11:15 AM Guillaume Tucker
<guillaume.tucker@collabora.com> wrote:
>
> On 24/09/2021 21:05, Rob Herring wrote:
> > On Thu, Sep 23, 2021 at 12:28 PM Guillaume Tucker
> > <guillaume.tucker@collabora.com> wrote:
> >>
> >> Hi Rob,
> >>
> >> Please see the bisection report below about a boot failure on ARM
> >> Versatile Express.
> >>
> >> Reports aren't automatically sent to the public while we're
> >> trialing new bisection features on kernelci.org but this one
> >> looks valid.
> >
> > Have you considered given you have the commit, if there's a Link tag,
> > sending this as a reply to the original patch? That would be a bit
> > easier to find IMO.
>
> Absolutely, in fact it's also possible to search in Lore for the
> original thread if there's no Link: trailer in the commit.  Then
> if subsequent bisections get run, the bot could reply to
> say "still failing" with new kernel revisions until it's fixed
> and then reply to confirm it is.  That's the plan, there's still
> a bit of work to do to have it all automated though.
>
> >> Some more details can be found here, for Cortex A9:
> >>
> >>   https://linux.kernelci.org/test/case/id/614c36cf0c427f123799a2db/
> >
> > I should have remembered there's a qemu model... Anyways, sending out
> > a fix in a moment.
> >
> > The log here was empty. Any reason 'earlycon' is not set here? I also
> > noticed stdout-path is not set on many of the Arm Ltd boards. I'll
> > send a patch for that, too. You really shouldn't have to set the
> > console on the cmdline nowadays unless you want the non-default.
>
> I believe earlycon is not set because it requires specific
> options on different platforms, so there's some configuration
> overhead involved here.  But it's a very good point that has been
> raised in the past, I guess someone needs to take the time to
> look into enabling it properly.  It shouldn't be that hard.

If the DT has stdout-path set, then all you need is just 'earlycon'
with no options.

Rob