From: Will Deacon <will@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: cki-project@redhat.com, xiawu@redhat.com,
catalin.marinas@arm.com, bhe@redhat.com,
linux-arm-kernel@lists.infradead.org, ardb@kernel.org
Subject: Re: ? FAIL (91/181 SKIPPED): Test report for for-kernelci (6.2.0-rc5, arm-next, 2e84eedb)
Date: Thu, 26 Jan 2023 15:17:16 +0000 [thread overview]
Message-ID: <20230126151715.GA29322@willie-the-truck> (raw)
In-Reply-To: <Y9KXxhSrYyQEogV0@FVFF77S0Q05N.cambridge.arm.com>
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@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
_______________________________________________
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:[~2023-01-26 15:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 9:21 ❌ FAIL (91/181 SKIPPED): Test report for for-kernelci (6.2.0-rc5, arm-next, 2e84eedb) cki-project
2023-01-26 12:52 ` Will Deacon
2023-01-26 14:53 ` ? " Mark Rutland
2023-01-26 15:09 ` Mark Rutland
2023-01-26 15:17 ` Will Deacon [this message]
2023-01-26 17:25 ` Mark Rutland
2023-01-26 18:33 ` Ard Biesheuvel
2023-01-27 12:14 ` [PATCH] arm64: avoid executing padding bytes during kexec / hibernation (WAS: Re: ? FAIL (91/181 SKIPPED): Test report for for-kernelci (6.2.0-rc5, arm-next, 2e84eedb)) Mark Rutland
2023-01-27 12:45 ` Ard Biesheuvel
2023-01-27 17:46 ` Catalin Marinas
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=20230126151715.GA29322@willie-the-truck \
--to=will@kernel.org \
--cc=ardb@kernel.org \
--cc=bhe@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=cki-project@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=xiawu@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