T1023RDB Kernel dump for Bad area access

Showing results for 
Search instead for 
Did you mean: 

T1023RDB Kernel dump for Bad area access

Contributor III


We are using T1023RDB based custom board for WiFi-AP project. The QorIQ SDK 1.7 is installed and its corresponding boot-images are used for booting this board. The SDK is built with 32-bit configuration (source ./fsl_setup_env -m t1023rdb). While the system is booted and loaded the application software, the following instruction dump is printed on console,

This switch software is implemented using Open sources from OpenSSL,OpenSSH,and other open source community.
To see a full description, type "show system acknowledgement"

Poky (Yocto Project Reference Distro) 1.6.1 t1023rdb /dev/ttyS0

t1023rdb login: Unable to handle kernel paging request for data at address 0x61616165
Faulting instruction address: 0xc00f0000
Oops: Kernel access of bad area, sig: 11 [#1]
SMP NR_CPUS=8 CoreNet Generic
Modules linked in: aptxdrv(O) aprcvdrv(O) umac(O) ath_dev(PO) ath_rate_atheros(PO) hst_tx99(PO) ath_spectral(PO) ath_dfs(PO))
CPU: 0 PID: 1851 Comm: WTP.exe Tainted: P O 3.12.19-rt30-QorIQ-SDK-V1.7+g6619b8b #2
task: e9135a30 ti: c43e2000 task.ti: c43e2000
NIP: c00f0000 LR: c00efdbc CTR: 00000000
REGS: c43e3d50 TRAP: 0300 Tainted: P O (3.12.19-rt30-QorIQ-SDK-V1.7+g6619b8b)
MSR: 00023002 <CE,FP,ME> CR: 28228488 XER: 20000000
DEAR: 61616165, ESR: 00800000

GPR00: c00efcfc c43e3e00 e9135a30 c8db09c0 000000d0 00000000 000006cb 0002f642
GPR08: 00000000 e9008f84 61616161 00000000 48222442 10ef8dd0 c09f0000 e9008f94
GPR16: e9008f8c c09f0000 00100100 00200200 00000001 e9008f84 e9008f80 c8db001c
GPR24: 00000000 000000d0 c43e2000 c09ec4e8 e9003a40 e901e600 ffffffff c8db0000
NIP [c00f0000] cache_alloc_refill+0x2d0/0x710
LR [c00efdbc] cache_alloc_refill+0x8c/0x710
Call Trace:
[c43e3e00] [28222448] 0x28222448 (unreliable)
[c43e3e60] [c00efcfc] kmem_cache_alloc+0xcc/0x100
[c43e3e80] [c002d714] dup_mm+0x104/0x4d0
[c43e3ec0] [c002e398] copy_process.part.55+0x838/0xe80
[c43e3f10] [c002eb50] do_fork+0xc0/0x2c0
[c43e3f40] [c000fcd4] ret_from_syscall+0x0/0x3c
--- Exception: c00 at 0xfd94c04
LR = 0xfd94e74
Instruction dump:
7c0803a6 7d810120 7d808120 38210060 4e800020 60000000 60000000 60000000
813f0004 3bc0ffff 815f0000 4f900000 <912a0004> 91490000 925f0000 927f0004
---[ end trace e2282300996e3766 ]---

The application software is built with 32 bit configuration. Please suggest the possible ways of getting this instruction dump.



0 Kudos
1 Reply

NXP TechSupport
NXP TechSupport

The message you are observing appears when an attempt is made to access
an invalid address. It is a generic bad pointer, not necessarily a
physical address width or 32/64 bit mode issue. The basic recommendation in
this regard it to debug your software.

More information can be found at the links below:


The call trace in your console log shows kernel memory allocation related
calls, it may be either due to improper use of that API (e.g. an access
to a deallocated object) or some kernel upstream ussue. It may be useful
to try the same software with a more recent QorIQ SDK, built around a
newer kernel.

Have a great day,

Note: If this post answers your question, please click the Correct Answer button. Thank you!

0 Kudos