From: Will Deacon <will@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: cki-project@redhat.com, linux-arm-kernel@lists.infradead.org,
catalin.marinas@arm.com
Subject: Re: ❌ FAIL: Test report for for-kernelci (6.13.0-rc3, upstream-arm-next, 06a57361)
Date: Fri, 20 Dec 2024 13:25:50 +0000 [thread overview]
Message-ID: <20241220132549.GA26731@willie-the-truck> (raw)
In-Reply-To: <CAMj1kXGx+Li4qwh_05Uf-aTtEOLSThv8o3JjKgWrPp9t8rqQyg@mail.gmail.com>
On Fri, Dec 20, 2024 at 02:06:21PM +0100, Ard Biesheuvel wrote:
> On Fri, 20 Dec 2024 at 13:49, Ard Biesheuvel <ardb@kernel.org> wrote:
> >
> > On Fri, 20 Dec 2024 at 13:35, Will Deacon <will@kernel.org> wrote:
> > >
> > > On Thu, Dec 19, 2024 at 11:12:08PM -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 (Did not boot)
> > > >
> > > >
> > > > 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/redhat:1596629923
> > > >
> > > > One or more kernel builds failed:
> > > > Builds that are failing to boot:
> > > > aarch64 - https://datawarehouse.cki-project.org/kcidb/builds/redhat:1596629923-aarch64-kernel
> > >
> > > Hmm, I can't find any console logs here. Did the machines really fail that
> > > early?
> > >
> >
> > This appears to be my fault: commit 32d053d6f5e92efd
> >
> > arm64/mm: Drop configurable 48-bit physical address space limit
> >
> > inadvertently sets CONFIG_ARM64_LPA2 for all VA space sizes. The
> > following hunk needs to be applied to address this
> >
> > --- a/arch/arm64/Kconfig
> > +++ b/arch/arm64/Kconfig
> > @@ -1418,7 +1418,7 @@ config ARM64_VA_BITS
> >
> > config ARM64_LPA2
> > def_bool y
> > - depends on !ARM64_64K_PAGES
> > + depends on ARM64_VA_BITS_52 && !ARM64_64K_PAGES
> >
> > choice
> > prompt "Endianness"
>
> On second thought, let's just omit commit 32d053d6f5e92efd for now -
> it's at the tip of the for-next/mm branch so it can just be dropped.
>
> I'll revisit this later - I have to double check that non-LPA2 configs
> (such as the one this report is about) work correctly on LPA2 capable
> hardware, and don't deviate from LPA2 configs booting with arm64.nolva
Sure thing, I'll drop it for now. I've managed to repro the failure
under qemu using the CKI .config, so I'll check that things are happy
again before I pushed the updated branch.
Will
next prev parent reply other threads:[~2024-12-20 13:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 23:12 ❌ FAIL: Test report for for-kernelci (6.13.0-rc3, upstream-arm-next, 06a57361) cki-project
2024-12-20 12:35 ` Will Deacon
[not found] ` <CAMj1kXENrzsF6JzvbGSwiJT5nupfJbij86zp0k2+YbqUCqvqNA@mail.gmail.com>
[not found] ` <CAMj1kXGx+Li4qwh_05Uf-aTtEOLSThv8o3JjKgWrPp9t8rqQyg@mail.gmail.com>
2024-12-20 13:25 ` Will Deacon [this message]
2024-12-20 13:43 ` Will Deacon
2024-12-20 22:35 ` Konrad Dybcio
2024-12-20 22:36 ` Konrad Dybcio
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=20241220132549.GA26731@willie-the-truck \
--to=will@kernel.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cki-project@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox