From: Will Deacon <will@kernel.org>
To: Veronika Kabatova <vkabatov@redhat.com>
Cc: catalin marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org,
CKI Project <cki-project@redhat.com>
Subject: Re: ❌ FAIL: Test?report?for?kernel?5.11.0-rc7 (arm-next)
Date: Wed, 10 Feb 2021 20:17:53 +0000 [thread overview]
Message-ID: <20210210201752.GB29192@willie-the-truck> (raw)
In-Reply-To: <719557748.27305363.1612985505202.JavaMail.zimbra@redhat.com>
On Wed, Feb 10, 2021 at 02:31:45PM -0500, Veronika Kabatova wrote:
> > > > > The machine in question can on course be somewhat flaky (hard to
> > > > > eliminate
> > > > > that possibility completely), but I checked our historical data and it
> > > > > didn't fail to boot a single time other than with these two new
> > > > > kernels.
> > > >
> > > > So the first thing we should probably try is whether vanilla -rc7 fails
> > > > on
> > > > the machine causing us problems. If it does, then the arm64 queue for
> > > > 5.12
> > > > is out of the equation, if not then we can try a targetted bisection.
> > > >
> > > > Would you be able to try v5.11-rc7 please?
> > >
> > > Can do.
> >
> > Brill, thanks.
> >
> > > Someone snatched up the machine in the meanwhile and appears to have it
> > > reserved till next Monday :/ I sincerely hope that they'll release it
> > > sooner
> > > and have queued up the test job with high priority. Will let you know right
> > > as I get the results.
> >
> > Just tell them the machine is broken and they really don't want to use it
> > for anything important ;)
> >
>
> Our wishes were granted by the lab fairy and the machine was returned
> rather quickly :)
>
> The 5.11-rc7 kernel boots.
Fantastic! Then it's something in the arm64 for-next/core tree that was
added since then. The diff isn't huge and one change stands out for me, so
let me try reverting that and I'll update the branch...
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-02-10 20:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 21:07 ❌ FAIL: Test report for kernel 5.11.0-rc7 (arm-next) CKI Project
2021-02-10 9:29 ` Will Deacon
2021-02-10 12:01 ` Veronika Kabatova
2021-02-10 15:24 ` Veronika Kabatova
2021-02-10 16:09 ` ❌ FAIL: Test report for kernel?5.11.0-rc7 (arm-next) Will Deacon
2021-02-10 17:07 ` Veronika Kabatova
2021-02-10 17:31 ` ❌ FAIL: Test report for?kernel?5.11.0-rc7 (arm-next) Will Deacon
2021-02-10 18:06 ` Veronika Kabatova
2021-02-10 18:56 ` ❌ FAIL: Test report?for?kernel?5.11.0-rc7 (arm-next) Will Deacon
2021-02-10 19:31 ` Veronika Kabatova
2021-02-10 20:17 ` Will Deacon [this message]
2021-02-10 20:32 ` ❌ FAIL: Test?report?for?kernel?5.11.0-rc7 (arm-next) Will Deacon
2021-02-11 10:46 ` Veronika Kabatova
2021-02-11 11:50 ` ❌ FAIL:?Test?report?for?kernel?5.11.0-rc7 (arm-next) Will Deacon
2021-02-11 12:25 ` Veronika Kabatova
2021-02-15 13:13 ` Veronika Kabatova
2021-02-15 18:24 ` Will Deacon
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=20210210201752.GB29192@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cki-project@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=vkabatov@redhat.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).