Sweet Potato - Unable to handle kernel paging event

Hi @ all,

I have three sweet potato devices. They are all connected to the same POE power source and used the same kernel / modules.

On one, I’m getting frequently this error:

[10519.594982] Unable to handle kernel paging request at virtual address ffff8000847ae090
[10519.597323] Mem abort info:
[10519.608626] ESR = 0x0000000096000007
[10519.608722] EC = 0x25: DABT (current EL), IL = 32 bits
[10519.612178] SET = 0, FnV = 0
[10519.615116] EA = 0, S1PTW = 0
[10519.618174] FSC = 0x07: level 3 translation fault
[10519.623036] Data abort info:
[10519.625849] ISV = 0, ISS = 0x00000007, ISS2 = 0x00000000
[10519.631309] CM = 0, WnR = 0, TnD = 0, TagAccess = 0
[10519.636303] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
[10519.641571] swapper pgtable: 4k pages, 48-bit VAs, pgdp=000000002c61f000
[10519.648218] [ffff8000847ae090] pgd=1000000001254403, p4d=1000000001254403, pud=1000000001255403, pmd=10000000393f2403, pte=0000000000000000
[10519.660668] Internal error: Oops: 0000000096000007 [#2] SMP
[10519.666228] Modules linked in: cuse fuse zram sch_fq_codel binfmt_misc lima gpu_sched meson_vdec(C) videobuf2_dma_contig v4l2_mem2mem videobuf2_memops meson_rng videobuf2_v4l2 videobuf2_common rng_core meson_ir videodev dw_hdmi_i2s_audio rc_core ao_cec snd_soc_meson_aiu snd_soc_meson_codec_glue mc snd_soc_meson_gx_sound_card snd_soc_meson_card_utils efi_pstore drm_shmem_helper pstore drm_sysfb_helper simplefb polyval_ce rtc_meson_vrtc amlogic_gxl_crypto crypto_engine scpi_hwmon
[10519.708410] CPU: 3 UID: 250 PID: 95531 Comm: sed Tainted: G D C 6.17.8-gentoo #1 PREEMPT(full)
[10519.718172] Tainted: [D]=DIE, [C]=CRAP
[10519.721849] Hardware name: libre-computer aml-s905x-cc-v2/aml-s905x-cc-v2, BIOS 2025.07+ 07/01/2025
[10519.732639] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=–)
[10519.738647] pc : vma_complete+0x11c/0x2b8
[10519.742606] lr : vma_complete+0x274/0x2b8
[10519.746546] sp : ffff8000847aba60
[10519.749801] x29: ffff8000847aba60 x28: ffff000043be4f00 x27: ffff8000847abcc8
[10519.756882] x26: ffff00000670b700 x25: 0000000000000000 x24: bffd8000847abc90
[10519.763946] x23: ffe680008072b880 x22: ffff000043be4e40 x21: ffff00000670b700
[10519.771014] x20: ffff8000807abcd0 x19: ffff8000847aba90 x18: ffff8000847abcd0
[10519.778073] x17: 0000000000000000 x16: 0000000000000000 x15: ffffdabe95407850
[10519.785135] x14: 0000ffff979cffff x13: 0000ffff979bffff x12: 0000000000000000
[10519.792197] x11: 0000000000000006 x10: 0000ffff979cffff x9 : ffffdabe93e2df24
[10519.799257] x8 : ffff00003ec95380 x7 : 000000000000000e x6 : 0000000000000000
[10519.806338] x5 : ffff8000847abcd0 x4 : 0000000000000000 x3 : 0000000000000000
[10519.813403] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
[10519.820469] Call trace:
[10519.822882] vma_complete+0x11c/0x2b8 (P)
[10519.826852] __split_vma+0x2a4/0x360
[10519.830381] vma_modify+0x2ec/0x528
[10519.833823] vma_modify_flags+0x90/0xd0
[10519.837609] mprotect_fixup+0x90/0x280
[10519.841312] do_mprotect_pkey+0x368/0x4b0
[10519.845270] __arm64_sys_mprotect+0x28/0x40
[10519.849398] invoke_syscall+0x50/0x120
[10519.853088] el0_svc_common.constprop.0+0x48/0xf0
[10519.857746] do_el0_svc+0x24/0x38
[10519.861004] el0_svc+0x34/0xf0
[10519.864000] el0t_64_sync_handler+0xa0/0xf0
[10519.868126] el0t_64_sync+0x198/0x1a0
[10519.871727] Code: 91024000 97f65b8e f9402260 36000aa0 (f9401a60)
[10519.877764] —[ end trace 0000000000000000 ]—

Is this a hardware issue?