LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Guillaume Tucker <email@example.com>
To: Rob Herring <firstname.lastname@example.org>
Cc: Sudeep Holla <email@example.com>,
Linus Walleij <firstname.lastname@example.org>,
Liviu Dudau <email@example.com>,
Lorenzo Pieralisi <firstname.lastname@example.org>
Subject: Re: next/master bisection: baseline.login on qemu_arm-vexpress-a9
Date: Mon, 27 Sep 2021 18:15:27 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
On 24/09/2021 21:05, Rob Herring wrote:
> On Thu, Sep 23, 2021 at 12:28 PM Guillaume Tucker
> <firstname.lastname@example.org> 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:
> 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.
Thanks for the feedback and the quick fix!
next prev parent reply other threads:[~2021-09-27 16:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <email@example.com>
2021-09-23 17:28 ` Guillaume Tucker
2021-09-24 20:05 ` Rob Herring
2021-09-27 16:15 ` Guillaume Tucker [this message]
2021-09-27 18:56 ` Rob Herring
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--subject='Re: next/master bisection: baseline.login on qemu_arm-vexpress-a9' \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).