S32v232 with Linux Kernel 4.19.31

Showing results for 
Search instead for 
Did you mean: 

S32v232 with Linux Kernel 4.19.31

Contributor I

Can anyone advice me with this error code?

Unable to handle kernel paging request at virtual address ffffffff800005c0
Mem abort info:
ESR = 0x96000145
Exception class = DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
Data abort info:
ISV = 0, ISS = 0x00000145
CM = 1, WnR = 1
swapper pgtable: 4k pages, 39-bit VAs, pgdp = 00000000b9ddca07
[ffffffff800005c0] pgd=0000000000000000, pud=0000000000000000
Internal error: Oops: 96000145 [#1] SMP
Modules linked in: xxxxx(O)
CPU: 0 PID: 0 Comm: swapper/0 Tainted: G O 4.19.31-xxxx
Hardware name: xxxxx based on Freescale S32V234 (DT)
pstate: 00000085 (nzcv daIf -PAN -UAO)
pc : __dma_inv_area+0x28/0x58
lr : __swiotlb_sync_single_for_cpu+0x4c/0x70
sp : ffffff8008003cc0
x29: ffffff8008003cc0 x28: ffffff80006b5000
x27: ffffffc03c420800 x26: ffffff80006b5000
x25: ffffffc03c420800 x24: 000000000000003c
x23: ffffffc03c4a7a00 x22: ffffffc03c420000
x21: 00000000000005f3 x20: 0000000000000000
x19: ffffffc03dd6a0a8 x18: ffffffffffffffff
x17: 0000000000000001 x16: 0000000000000007
x15: ffffff80088c8588 x14: ffffff808892189f
x13: ffffff80089218ad x12: 0000000000000000
x11: ffffff80083c1090 x10: 0000000005f5e0ff
x9 : 00000000ffffffd0 x8 : 323033203a747075
x7 : ffffff80088c85b8 x6 : 00000000000003ee
x5 : 0000000000000001 x4 : ffffffff80000000
x3 : 000000000000003f x2 : 0000000000000040
x1 : ffffffff800005c0 x0 : ffffffff80000000
Process swapper/0 (pid: 0, stack limit = 0x00000000057e45cf)
Call trace:



Code: d1000443 ea03003f 8a230021 54000040 (d50b7e21)
---[ end trace 263bcb19fc625165 ]---
Kernel panic - not syncing: Fatal exception in interrupt
SMP: stopping secondary CPUs
Kernel Offset: disabled
CPU features: 0x0,20802004
Memory Limit: none
---[ end Kernel panic - not syncing: Fatal exception in interrupt ]---

Labels (1)
0 Kudos
1 Reply

NXP TechSupport
NXP TechSupport

The error means the code  attempted a jump or a data access to
a virtual address for which there was no page table entry. This can happen
due to multiple reasons, most typically corrupt or uninitialized pointer, memory decay
or invalid memory size reported by the bootloader.  Kernel debugging is
required to see why and where it fails.



0 Kudos