Getting kernel traps in pthread process execution

Submitted by Anonymous
on January 15, 2009 - 6:11am

Hi,

I am getting kernel traps in pthread execution. logs are as follows

Signal: 11 SIGSEGV si_code: 00000001
Process Info:
TID: 3373 PID: 3372 PPID: 1
THREAD: 3012d4e0 THREAD MASTER: 00000000

Command Line:
/usr/local/bin/ee/fastHs /etc/mtc/fastHs.conf

Processor State Registers:
TRAP: 00000300
MSR: 0200d032 [ user mode, prefix 0xfff, big endian ]
DAR: 0000000c
DSISR: 40000000

Misc User registers:
IAR: 0fd26ca0 :__pthread_mutex_lock + 34
LR: 0fd42228
CTR: 00000000
XER: 20000000 [ carry + Count=0 ]

Condition Register:
CR: 44042484 [ 0:gt 1:gt 2:?? 3:gt 4:eq 5:gt 6:lt 7:gt ]

General Purpose registers:
GPR 00-04: 0ffa4714 3012c9e0 30134950 00000000 0ffc0978
GPR 05-09: 00000000 00000000 00008000 00000000 0ffc0978
GPR 10-14: 00000002 3012ca50 44042484 1001a9a4 10000000
GPR 15-19: 00000000 00000000 7fbcaa24 30020cf8 0f755838
GPR 20-24: 30027738 0fd42254 00000001 00000003 00001000
GPR 25-29: 7fbcaa30 003d0f00 3012d080 003d0f00 3012cb50
GPR 30-31: 0fd42228 00000000

Floating Point Registers:
FPSCR: 00000000 [ ]
FPR 00-03: 8.188007e-308 0.000000e+00 0.000000e+00 0.000000e+00
FPR 04-03: 0.000000e+00 0.000000e+00 0.000000e+00 0.000000e+00
FPR 08-03: 0.000000e+00 0.000000e+00 0.000000e+00 0.000000e+00
FPR 12-03: 0.000000e+00 3.069136e-320 0.000000e+00 0.000000e+00
FPR 16-03: 0.000000e+00 0.000000e+00 0.000000e+00 0.000000e+00
FPR 20-03: 0.000000e+00 0.000000e+00 0.000000e+00 0.000000e+00
FPR 24-03: 0.000000e+00 0.000000e+00 0.000000e+00 0.000000e+00
FPR 28-03: 0.000000e+00 0.000000e+00 0.000000e+00 0.000000e+00

Instructions near trap:
0fd26c6c :__pthread_mutex_lock + 0 7c0802a6 mflr r0
0fd26c70 :__pthread_mutex_lock + 4 9421ffd0 stwu r1, #ffd0(r1)
0fd26c74 :__pthread_mutex_lock + 8 93a10024 stw r29, #0024(r1)
0fd26c78 :__pthread_mutex_lock + c 4801b5ad bl 0fd42224
0fd26c7c :__pthread_mutex_lock + 10 93c10028 stw r30, #0028(r1)
0fd26c80 :__pthread_mutex_lock + 14 7fc802a6 mflr r30
0fd26c84 :__pthread_mutex_lock + 18 93e1002c stw r31, #002c(r1)
0fd26c88 :__pthread_mutex_lock + 1c 7c7f1b78 mr r31, r3
0fd26c8c :__pthread_mutex_lock + 20 90010034 stw r0, #0034(r1)
0fd26c90 :__pthread_mutex_lock + 24 93210014 stw r25, #0014(r1)
0fd26c94 :__pthread_mutex_lock + 28 93410018 stw r26, #0018(r1)
0fd26c98 :__pthread_mutex_lock + 2c 9361001c stw r27, #001c(r1)
0fd26c9c :__pthread_mutex_lock + 30 93810020 stw r28, #0020(r1)
T> 0fd26ca0 :__pthread_mutex_lock + 34 8143000c lwz r10, #000c(r3)
0fd26ca4 :__pthread_mutex_lock + 38 83a28bd8 lwz r29, #8bd8(r2)
0fd26ca8 :__pthread_mutex_lock + 3c 2b8a0033 cmplwi cr7, r10, #0033
0fd26cac :__pthread_mutex_lock + 40 419d00a0 bt cr7, :__pthread_mutex_lock + e0
0fd26cb0 :__pthread_mutex_lock + 44 817efeac lwz r11, #feac(r30)
0fd26cb4 :__pthread_mutex_lock + 48 5540103a extlwi r0, r10, 30, 2
0fd26cb8 :__pthread_mutex_lock + 4c 7d2b002e lwzx r9, r11, r0

Traceback:
0fd26ca0 :__pthread_mutex_lock + 34
0ffa4714 :_ZN11CHsOsMutext4lockEv + 24
0ff81130 :_ZN16CHsOsMutextGuardC1ER11CHsOsMutext + 40
0ff833cc :_Z9hsMapMainv + b4
0ffa4a20 :_Z11ThreadProcLPv + 38
0f755940 :ee_thread_create_start_routine + 108
0fd248dc :start_thread + 88

Stack Dump:
0fd26ca0 /lib/libpthread-2.3.6.so:__pthread_mutex_lock + 34
3012c9e0: 3012ca10 00000000 00000000 00000000 0...............
3012c9f0: 00000000 7fbcaa30 003d0f00 3012d080 .......0.=..0...
3012ca00: 003d0f00 3012cb50 0ffc8288 3012ca10 .=..0..P....0...
---------------------------------------------
0ffa4714 /usr/local/lib/libhsMap.so.0.0.1:_ZN11CHsOsMutext4lockEv + 24
3012ca10: 3012ca30 0ffa4714 0ffc0978 00000020 0..0..G....x...
3012ca20: 3012c990 0112cb6c 3012ca30 00000000 0......l0..0....
---------------------------------------------
0ff81130 /usr/local/lib/libhsMap.so.0.0.1:_ZN16CHsOsMutextGuardC1ER11CHsOsMutext + 40
3012ca30: 3012ca50 0ff81130 3012cb50 0ffc0978 0..P...00..P...x
3012ca40: 3012ca50 00000000 0ffc8288 3012ca50 0..P........0..P
---------------------------------------------

And its intermittent in nature. Its PPC machine