From: Veronika Kabatova <vkabatov@redhat.com>
To: Will Deacon <will@kernel.org>
Cc: catalin marinas <catalin.marinas@arm.com>,
CKI Project <cki-project@redhat.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: ❌ FAIL:?Test?report?for?kernel?5.11.0-rc7 (arm-next)
Date: Thu, 11 Feb 2021 07:25:34 -0500 (EST) [thread overview]
Message-ID: <419175028.27367825.1613046334236.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20210211115049.GA29894@willie-the-truck>
----- Original Message -----
> 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>
> Sent: Thursday, February 11, 2021 12:50:50 PM
> Subject: Re: ❌ FAIL:?Test?report?for?kernel?5.11.0-rc7 (arm-next)
>
> On Thu, Feb 11, 2021 at 05:46:02AM -0500, Veronika Kabatova wrote:
> > > On Wed, Feb 10, 2021 at 08:17:53PM +0000, Will Deacon wrote:
> > > > 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...
> > >
> > > Ok, I updated for-kernelci so that it contains the arm64 for-next/core
> > > branch merged into -rc7, but with a couple of patches reverted on top.
> > >
> > > HEAD is e56137cc7606 ("Revert "arm64/mm: Fix pfn_valid() for ZONE_DEVICE
> > > based memory""). Please can you try that?
> > >
> >
> > I didn't actually have to, the autopick picked the machine for the testing
> > and it happily booted :) \o/
>
> Phew, so I'll drop those from linux-next as well. Do you know if "earlycon"
> works on the problematic machine? If possible, it would be helpful to try
> booting the bad kernel with earlycon on the cmdline to see if it manages to
> say anything in its dying breath.
>
No idea, we don't have the option enabled and I can't find any information
about it. I submitted a new job with the option and let's see whether it
works or not. The machine is reserved again so there may be some delays.
> > Apparently IT cut off our email sending access because we're sending too
> > many emails so that's why you don't have the report yet. When we work
> > around it I'll make sure to retrigger the sending so you have it.
>
> That's nice of them...
>
Update for the drama loving folks: IT is actually innocent in this.
Someone deployed a misconfigured application in the same cluster as our
reporting system is in, and this application is sending out emails
every 3 seconds. We're collateral damage. Working on resolution, but
right now it seems that the situation is under control.
Veronika
> 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-11 12:26 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 ` ❌ FAIL: Test?report?for?kernel?5.11.0-rc7 (arm-next) Will Deacon
2021-02-10 20:32 ` 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 [this message]
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=419175028.27367825.1613046334236.JavaMail.zimbra@redhat.com \
--to=vkabatov@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=cki-project@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=will@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.