❌ FAIL: Test?report?for?kernel?5.11.0-rc7 (arm-next)

[Will Deacon]

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?

Cheers,

Will