AnsweredAssumed Answered

segmentation fault on mpc8309 SBC

Question asked by vishnu prasad on Jul 16, 2018
Latest reply on Jul 24, 2018 by Yiping Wang

Hi,

I have a MPC8309 based SBC  which runs a linux application for about 20 minutes and then crashes with seg fault. The most predominant message appearing on prompt is "vmap allocation for size 8192 failed: use vmalloc=<size> to increase size" . I have searched all over that recommend increase in size of vmap, but conceptually I do not understand why system crashes exactly after 20 min. If there were problem in vmap allocation, the application should not have run in the first place?

What could be the problem?

Following is the complete list of error messages

vmap allocation for size 8192 failed: use vmalloc=<size> to increase size.
vmap allocation for size 8192 failed: use vmalloc=<size> to increase size.
vmap allocation for size 8192 failed: use vmalloc=<size> to increase size.
vmap allocation for size 8192 failed: use vmalloc=<size> to increase size.
vmap allocation for size 8192 failed: use vmalloc=<size> to increase size.
vmap allocation for size 8192 failed: use vmalloc=<size> to increase size.
vmap allocation for size 8192 failed: use vmalloc=<size> to increase size.
vmap allocation for size 8192 failed: use vmalloc=<size> to increase size.
vmap allocation for size 8192 failed: use vmalloc=<size> to increase size.
vmap allocation for size 8192 failed: use vmalloc=<size> to increase size.
Unable to handle kernel paging request for data at address 0x00000000
Faulting instruction address: 0xd18c14a0
Oops: Kernel access of bad area, sig: 11 [#1]
MPC8309 SOM
last sysfs file: /sys/kernel/uevent_seqnum
Modules linked in: drv
NIP: d18c14a0 LR: d18c11e4 CTR: 00000000
REGS: ced35d50 TRAP: 0300   Not tainted  (2.6.34)
MSR: 00009032 <EE,ME,IR,DR>  CR: 24000288  XER: 20000000
DAR: 00000000, DSISR: 22000000
TASK = ced0ad10[1699] 'main' THREAD: ced34000
GPR00: 40000000 ced35e00 ced0ad10 00000000 00000001 00000006 00000001 00010000
GPR08: d18c182f 48000000 01000000 69000000 00000006 1001a678 00000000 00000000
GPR16: 00000000 00000000 00000000 d189ec08 d18a2c08 d18bec08 00000000 00000000
GPR24: 00000000 00000000 00000000 d189ac08 00000000 d18c0000 00000007 00004808
Call Trace:
[ced35e00] [d18c11e4] 0xd18c11e4 (unreliable)
[ced35ef0] [c0080d10] 0xc0080d10
[ced35f10] [c0081260] 0xc0081260
[ced35f40] [c0010e38] 0xc0010e38
---  
    LR = 0x10001c28
Instruction dump:
800a0000 394a0004 7c840214 419dffc0 5487801e 548ac00e 2b9fffff 419d008c
57e9800e 3c004000 901b0000 3d606900 <913c0000> 3c008000 57e9c00e 90130000
---[ end trace 59b64ab64092c6b2 ]---
Segmentation fault

Outcomes