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,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Subject: Re: next/master bisection: baseline.login on qemu_arm-vexpress-a9
Date: Fri, 24 Sep 2021 15:05:27 -0500 [thread overview]
Message-ID: <CAL_JsqJ9fDXkVgcXTiO+NM9T7OKO+p43NGmJPRvvLi3-_Bd4dQ@mail.gmail.com> (raw)
In-Reply-To: <8d6223d2-8ca7-0373-bb49-b62894e5fad7@collabora.com>
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.
> 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.
Rob
next prev parent reply other threads:[~2021-09-24 20:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <614ad319.1c69fb81.2a0c1.4782@mx.google.com>
2021-09-23 17:28 ` next/master bisection: baseline.login on qemu_arm-vexpress-a9 Guillaume Tucker
2021-09-24 20:05 ` Rob Herring [this message]
2021-09-27 16:15 ` Guillaume Tucker
2021-09-27 18:56 ` Rob Herring
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAL_JsqJ9fDXkVgcXTiO+NM9T7OKO+p43NGmJPRvvLi3-_Bd4dQ@mail.gmail.com \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=guillaume.tucker@collabora.com \
--cc=kernelci-results@groups.io \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=sudeep.holla@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).