From: Ryan Roberts <ryan.roberts@arm.com>
To: Luiz Capitulino <luizcap@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Cc: ardb@kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Will Deacon <will@kernel.org>
Subject: Re: kernel BUG at arch/arm64/mm/mmu.c:185!
Date: Tue, 25 Feb 2025 09:47:30 +0000 [thread overview]
Message-ID: <b39a37c8-c9b5-406d-a97a-24fa67622b49@arm.com> (raw)
In-Reply-To: <dee18de8-7938-4df1-badb-c00832d6995f@redhat.com>
(Adding arm folks for visibility)
See original report here for context:
https://lore.kernel.org/all/a3d9acbe-07c2-43b6-9ba9-a7585f770e83@redhat.com/
TL;DR is that 6.14 doesn't boot on Ampere Altra when kaslr is enabled.
On 20/02/2025 20:08, Luiz Capitulino wrote:
> On 2025-02-19 09:40, Luiz Capitulino wrote:
>
>>>> Btw, I'll try to bisect again and will also try to update the system's firmware
>>>> just in case.
>
> I tried to bisect it and again, got nowhere.
>
> Git bisect says the first bad commit is 8883957b3c9de2087fb6cf9691c1188cccf1ac9c .
> But I'm able to boot that tree...
>
OK, think I've found the dodgy commit:
Commit 62cffa496aac ("arm64/mm: Override PARange for !LPA2 and use it consistently")
Based on the changes it certainly looks like it could be the issue, but I
haven't spotted exactly what the problem is yet. Ard, could you take a look?
I managed to hack multi ram bank support into kvmtool, so I can now repro the
issue in virtualization. Then was able to bisect to get to the above commit.
I'll keep digging to see if I can get to the root cause, but I suspect Ard is
best placed to hypothesise at this point.
Thanks,
Ryan
next prev parent reply other threads:[~2025-02-25 9:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 2:27 kernel BUG at arch/arm64/mm/mmu.c:185! Luiz Capitulino
2025-02-19 8:41 ` Ryan Roberts
2025-02-19 14:16 ` Luiz Capitulino
2025-02-19 14:26 ` Ryan Roberts
2025-02-19 14:40 ` Luiz Capitulino
2025-02-20 20:08 ` Luiz Capitulino
2025-02-25 9:47 ` Ryan Roberts [this message]
2025-02-25 11:10 ` Mark Rutland
2025-02-25 11:19 ` Ryan Roberts
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=b39a37c8-c9b5-406d-a97a-24fa67622b49@arm.com \
--to=ryan.roberts@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=ardb@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luizcap@redhat.com \
--cc=will@kernel.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