? FAIL (91/181 SKIPPED): Test report for for-kernelci (6.2.0-rc5, arm-next, 2e84eedb)

[Will Deacon]

On Thu, Jan 26, 2023 at 03:09:58PM +0000, Mark Rutland wrote:
> On Thu, Jan 26, 2023 at 12:52:03PM +0000, Will Deacon wrote:
> > [+Mark and Ard in case they have ideas]
> > 
> > On Wed, Jan 25, 2023 at 09:21:19AM -0000, cki-project at redhat.com wrote:
> > > Hi, we tested your kernel and here are the results:
> > > 
> > >     Overall result: FAILED
> > >              Merge: OK
> > >            Compile: OK
> > >               Test: FAILED
> > > 
> > > 
> > > Kernel information:
> > >     Commit message: Merge branch 'for-next/core' into for-kernelci
> > > 
> > > You can find all the details about the test run at
> > >     https://datawarehouse.cki-project.org/kcidb/checkouts/66828
> > > 
> > > One or more kernel tests failed:
> > >     Unrecognized or new issues:
> > >          aarch64 - kdump - kexec_boot
> > >                    Logs: https://datawarehouse.cki-project.org/kcidb/tests/6799495
> > 
> > This looks like we run into an undefined instruction when we jump to the
> > kexec relocation code. Do you know if the failure is reproducible, and is
> > the log identical each time?
> 
> I had a go in a QEMU KVM VM on ThunderX2, and a QEMU KVM TCG VM. With defconfig
> I don't see the issue, but with the config from the test run link above I
> consistently see the issue both under KVM and TCG (logs below).
> 
> It should be simple enough to figure out which config option is tickling this;
> I'll go dig in to that..

Cheers, Mark. If you get a chance, it's probably also worth testing vanilla
-rc5 to confirm that it's a regression in our queue (which we could
assumedly bisect if necessary).

Will