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

[Will Deacon]

On Mon, Feb 15, 2021 at 08:13:18AM -0500, Veronika Kabatova wrote:
> > > 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:
> > > > > 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.
> > 
> 
> I finally got access to the machine and don't have any good news. The hang
> is from before early printk takes effect. The output is identical to what
> I sent before, with nothing resembling kernel lines in there.

Oh well, thanks for giving it a shot. I've already dropped the for-next/mm
branch from my pull request for 5.12, but please keep a note of the
problematic machine if possible so that we can try further debugging in
future.

Cheers,

Will