From: Luiz Capitulino <luizcap@redhat.com>
To: LKML <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Cc: ardb@kernel.org, ryan.roberts@arm.com
Subject: kernel BUG at arch/arm64/mm/mmu.c:185!
Date: Tue, 18 Feb 2025 21:27:18 -0500 [thread overview]
Message-ID: <a3d9acbe-07c2-43b6-9ba9-a7585f770e83@redhat.com> (raw)
Hi,
I'm getting the crash below with Linus tree commit
2408a807bfc3f738850ef5ad5e3fd59d66168996 on a Ampere Mt. Jade with two sockets
(backtrace below).
It happens very early during boot. Passing 'nokaslr' in the command-line works
around the issue (ie. I can boot and use the system normally). Doesn't seem to
happen with 6.13. I tried bisecting it but got nowhere...
[ 0.000000] ------------[ cut here ]------------
[ 0.000000] kernel BUG at arch/arm64/mm/mmu.c:185!
[ 0.000000] Internal error: Oops - BUG: 00000000f2000800 [#1] SMP
[ 0.000000] Modules linked in:
[ 0.000000] CPU: 0 UID: 0 PID: 0 Comm: swapper Not tainted 6.14.0-rc3+ #8
[ 0.000000] pstate: 400000c9 (nZcv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 0.000000] pc : alloc_init_cont_pte+0x20c/0x3d0
[ 0.000000] lr : alloc_init_cont_pte+0x204/0x3d0
[ 0.000000] sp : ffffb45836ec78b0
[ 0.000000] x29: ffffb45836ec7940 x28: ffff6fea00000000 x27: 0068000000000f07
[ 0.000000] x26: ffff6fea00200000 x25: 0000400000000000 x24: ffffffffff433000
[ 0.000000] x23: dfff800000000000 x22: 0000d01600000000 x21: 0068000000000f07
[ 0.000000] x20: ffff6fea00000000 x19: ffff6fea00010000 x18: 00000000ae5a3fb1
[ 0.000000] x17: 0000000000001114 x16: 00000000bfc60000 x15: 0000000000000200
[ 0.000000] x14: 0000000000000000 x13: 1ffff68b06dd8f1c x12: 00000000f1f1f1f1
[ 0.000000] x11: ffff768b06dd8f1c x10: ffffb45835a1ca38 x9 : 0000000000000000
[ 0.000000] x8 : 0000000041b58ab3 x7 : 0000000000000000 x6 : 0000000000000000
[ 0.000000] x5 : 006840000a861f07 x4 : 000000000000a861 x3 : 000000000000a861
[ 0.000000] x2 : 006840000a861f03 x1 : 0068400000000f07 x0 : 0000000000000000
[ 0.000000] Call trace:
[ 0.000000] alloc_init_cont_pte+0x20c/0x3d0 (P)
[ 0.000000] alloc_init_cont_pmd+0x20c/0x4d0
[ 0.000000] alloc_init_pud+0x244/0x400
[ 0.000000] create_kpti_ng_temp_pgd+0xf8/0x1c8
[ 0.000000] map_mem.constprop.0+0x1d8/0x3b8
[ 0.000000] paging_init+0x98/0x330
[ 0.000000] setup_arch+0xac/0x170
[ 0.000000] start_kernel+0x74/0x3c8
[ 0.000000] __primary_switched+0x8c/0xa0
[ 0.000000] Code: f9400301 97ffff64 72001c1f 54fffe21 (d4210000)
[ 0.000000] ---[ end trace 0000000000000000 ]---
[ 0.000000] Kernel panic - not syncing: Oops - BUG: Fatal exception
[ 0.000000] ---[ end Kernel panic - not syncing: Oops - BUG: Fatal exception ]---
next reply other threads:[~2025-02-19 2:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 2:27 Luiz Capitulino [this message]
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
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=a3d9acbe-07c2-43b6-9ba9-a7585f770e83@redhat.com \
--to=luizcap@redhat.com \
--cc=ardb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryan.roberts@arm.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