armv7 translation fault

From: Sulev-Madis Silber <freebsd-current-freebsd-org111_at_ketas.si.pri.ee>
Date: Fri, 03 Oct 2025 07:28:50 UTC
i have allwinner h3 in hw nanopi neo core for which i use own dtb and uboot for nanopi m1 plus to get emmc up and working

and i have those things

Fatal kernel mode data abort: 'Translation Fault (L1)' on write

Fatal kernel mode data abort: 'Translation Fault (L2)' on read

Starting devd.
panic: acquiring blockable sleep lock with spinlock or critical section held (sleep mutex) pmap @ sys/arm/arm/pmap-v6.c:6476

(last one came from debug kernel)

seems like i get more of them, almost indefinite amount, if i try to mess with uboot and efi loader trying to get update fault tolerant things up

once i get system up into userland (could be single or multi) and then reboot from there, they all disappear and i can boot as much as i want

are those my hw specific or something leaves something in memory which later messes things up? i don't have enough knowledge here and currently didn't try to cold boot from total power off state

is this an error and can it be fixed? if ram or other hw indeed ends up in questionable state, could it be possible for kernel to rectify it somehow

never seen them before too, despite messing around in uboot and loader shell a lot, before. so a recent bug?

tried to look up what that error is and unfortunately i'm not going to learn how mmu works in one day. so any ideas eh...