Part Number:AM3505
Tool/software: Linux
Q1: We have been experiencing a random kernel crash on our radio with AM3505 and Kernel 2.6.37 and wondering if any patches from TI could be involved?
Even if this isn't relevant to Texas Instruments would appreciate you know of someone else in the forum have reported something along these lines,
[115471.753753] kernel BUG at mm/prio_tree.c:79!
[115471.753784] Unable to handle kernel NULL pointer dereference at virtual address 00000000
[115471.753814] pgd = c60f8000
[115471.753814] [00000000] *pgd=86062031, *pte=00000000, *ppte=00000000
[115471.753845] Internal error: Oops: 817 [#1]
[115471.758239] last sysfs file: /sys/devices/virtual/fpga_ctrl/fpga_ctrl/energy_save
[115471.766174] Modules linked in: heartbeat mdl_driver omap3_crypto rohc gpio_driver fpga_driver spi_fpga
[115471.776031] CPU: 0 Not tainted (2.6.37 #2)
[115471.780822] PC is at __bug+0x1c/0x28
[115471.784667] LR is at __bug+0x18/0x28
[115471.788482] pc : [<c004139c>] lr : [<c0041398>] psr: 20000093
[115471.788513] sp : c6093ec8 ip : 00006528 fp : c61dc498
[115471.800720] r10: 0000000b r9 : c61dc4b4 r8 : c61dc4b8
[115471.806274] r7 : c607a500 r6 : c67dbac8 r5 : c60d3ac8 r4 : 401a5000
[115471.813201] r3 : 00000000 r2 : c6093ebc r1 : c041a567 r0 : 00000037
[115471.820159] Flags: nzCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment user
[115471.827819] Control: 10c5387d Table: 860f8019 DAC: 00000015
[115471.833923] Process stat_manager (pid: 4542, stack limit = 0xc60922f0)
[115471.840881] Stack: (0xc6093ec8 to 0xc6094000)
[115471.845550] 3ec0: 00000044 c00ab73c c612ecc0 c0060d48 c61f1ec0 c607a534
[115471.854217] 3ee0: c612ecf4 c61dc4a4 c04dacd4 c615a800 01200011 00000000 c615a8f0 00000000
[115471.862884] 3f00: 40358068 c60b9dc0 c04dacb0 c0061508 000030b0 c04bf1e8 00000001 beeeaa58
[115471.871551] 3f20: c6093fb0 00000000 00000000 00000000 00000001 01200011 00000000 c6093fb0
[115471.880249] 3f40: 00000000 00000000 beeeaa58 00000000 beeeaa9c c0061c80 40358068 00000000
[115471.888916] 3f60: 00000000 00000000 00000000 beeeaab8 00026008 00000167 c003dc08 beeeaab8
[115471.897583] 3f80: 00000008 00000000 40358068 beeeaa58 000011be 00000078 c003dc08 c6092000
[115471.906250] 3fa0: 00000000 c003da60 00000000 40358068 01200011 00000000 00000000 00000000
[115471.914947] 3fc0: 40358068 beeeaa58 000011be 00000078 40349000 40358000 4034c2b8 beeeaa9c
[115471.923614] 3fe0: 403584c0 beeeaa58 000011be 402b4ff8 60000010 01200011 87ffe021 87ffe421
[115471.932312] [<c004139c>] (__bug+0x1c/0x28) from [<c00ab73c>] (vma_prio_tree_add+0x4c/0xbc)
[115471.941101] [<c00ab73c>] (vma_prio_tree_add+0x4c/0xbc) from [<c0060d48>] (dup_mm+0x22c/0x3a0)
[115471.950134] [<c0060d48>] (dup_mm+0x22c/0x3a0) from [<c0061508>] (copy_process+0x61c/0xc28)
[115471.958923] [<c0061508>] (copy_process+0x61c/0xc28) from [<c0061c80>] (do_fork+0x148/0x304)
[115471.967773] [<c0061c80>] (do_fork+0x148/0x304) from [<c003da60>] (ret_fast_syscall+0x0/0x30)
[115471.976715] Code: e59f0010 e1a01003 eb0cb1b3 e3a03000 (e5833000)
[115471.983398] ---[ end trace be115207729a3577 ]---
Q2: The side effects of this problem is a device reboot, hence a general question to the CPU reset source. Is there any way to know from the CPU how it was reset (after it has been reset), i.e. which type of reset triggered the reboot?
Appreciate your attention.
Regards,
Yakir M.
MiMOMax Wireless Ltd.