2009-04-05 08:18:40 Crash log analysis help
Hari Prasad (INDIA)
Message: 72174
Hi,
We are getting the following crash info when we run our application in 2008R1.5 kernel. We request someone to guide us in understanding the trace and help us catch the issue. Trace info is:
Data access misaligned address violation
- Attempted misaligned data memory or data cache access.
Defered Exception context
CURRENT PROCESS:
COMM=MyApp PID=100
TEXT = 0x03000000-0x03247498 DATA = 0x02000498-0x029634a0
BSS = 0x029634a0-0x03260000 USER-STACK = 0x0327fe60
return address: [0x00a2eb84]; contents of:
0x00a2eb60: 51fa 181d 0000 0000 ac51 0c41 1809 0000
0x00a2eb70: 0000 9109 3071 520e 6460 0803 1820 322a
0x00a2eb80: 0c40 5a95 [bc51] bc90 1818 bc42 0c41 1802
0x00a2eb90: bc8a 324a 9317 2fd3 6800 2fc4 0c40 1bfa
SEQUENCER STATUS: Tainted: P
SEQSTAT: 00000024 IPEND: 0030 SYSCFG: 0006
HWERRCAUSE: 0x0
EXCAUSE : 0x24
RETE: <0x00000000> /* Maybe null pointer? */
RETN: <0x02968000> [ MyApp + 0x0 ]
RETX: <0x00a2eb84> [ /lib/libuClibc-0.9.29.so + 0x2eb84 ]
RETS: <0x00a2e760> [ /lib/libuClibc-0.9.29.so + 0x2e760 ]
PC : <0x00a2eb84> [ /lib/libuClibc-0.9.29.so + 0x2eb84 ]
DCPLB_FAULT_ADDR: <0x0271b020> [ /MyApp + 0x962020 ]
ICPLB_FAULT_ADDR: <0x00a2eb84> [ /lib/libuClibc-0.9.29.so + 0x2eb84 ]
PROCESSOR STATE:
R0 : 0138fe38 R1 : 000001c8 R2 : 0138c211 R3 : 02718211
R4 : 02969bd8 R5 : 02969514 R6 : 0138fff4 R7 : 0138e231
P0 : 012b8ff4 P1 : 0138fff4 P2 : 0271b01d P3 : 02969510
P4 : 02970004 P5 : 0138c211 FP : 03e788f0 SP : 02967f24
LB0: 00a1efcd LT0: 00a1efcc LC0: 00000000
LB1: 031311fd LT1: 031311d4 LC1: 000003f6
B0 : 00000003 L0 : 00000000 M0 : 00000007 I0 : 02c5b24d
B1 : 000000df L1 : 00000000 M1 : 00000000 I1 : 00000000
B2 : 005c49e0 L2 : 00000000 M2 : 00000000 I2 : 00000000
B3 : 00000140 L3 : 00000000 M3 : 000000ff I3 : 03e77754
A0.w: 00000000 A0.x: 00000000 A1.w: 00000000 A1.x: 00000000
USP : 03e788f0 ASTAT: 02003004
Hardware Trace:
0 Target : <0x00183a14> { _trap_c + 0x0 }
Source : <0xffa00734> { _exception_to_level5 + 0xb4 }
1 Target : <0xffa00680> { _exception_to_level5 + 0x0 }
Source : <0xffa005d8> { _ex_trap_c + 0x5c }
2 Target : <0xffa0057c> { _ex_trap_c + 0x0 }
Source : <0xffa007d4> { _trap + 0x28 }
3 Target : <0xffa007ac> { _trap + 0x0 }
Source : <0x00a2eb82> [ /lib/libuClibc-0.9.29.so + 0x2eb82 ]
4 Target : <0x00a2eb4a> [ /lib/libuClibc-0.9.29.so + 0x2eb4a ]
Source : <0x00a2eb10> [ /lib/libuClibc-0.9.29.so + 0x2eb10 ]
5 Target : <0x00a2eb08> [ /lib/libuClibc-0.9.29.so + 0x2eb08 ]
Source : <0x00a2eb1c> [ /lib/libuClibc-0.9.29.so + 0x2eb1c ]
6 Target : <0x00a2eb08> [ /lib/libuClibc-0.9.29.so + 0x2eb08 ]
Source : <0x00a2eb1c> [ /lib/libuClibc-0.9.29.so + 0x2eb1c ]
7 Target : <0x00a2eb08> [ /lib/libuClibc-0.9.29.so + 0x2eb08 ]
Source : <0x00a2eb1c> [ /lib/libuClibc-0.9.29.so + 0x2eb1c ]
8 Target : <0x00a2eb08> [ /lib/libuClibc-0.9.29.so + 0x2eb08 ]
Source : <0x00a2eb1c> [ /lib/libuClibc-0.9.29.so + 0x2eb1c ]
9 Target : <0x00a2eb08> [ /lib/libuClibc-0.9.29.so + 0x2eb08 ]
Source : <0x00a2eb1c> [ /lib/libuClibc-0.9.29.so + 0x2eb1c ]
10 Target : <0x00a2eb08> [ /lib/libuClibc-0.9.29.so + 0x2eb08 ]
Source : <0x00a2eb1c> [ /lib/libuClibc-0.9.29.so + 0x2eb1c ]
11 Target : <0x00a2eb08> [ /lib/libuClibc-0.9.29.so + 0x2eb08 ]
Source : <0x00a2eb1c> [ /lib/libuClibc-0.9.29.so + 0x2eb1c ]
12 Target : <0x00a2eb08> [ /lib/libuClibc-0.9.29.so + 0x2eb08 ]
Source : <0x00a2eb1c> [ /lib/libuClibc-0.9.29.so + 0x2eb1c ]
13 Target : <0x00a2eb08> [ /lib/libuClibc-0.9.29.so + 0x2eb08 ]
Source : <0x00a2eb1c> [ /lib/libuClibc-0.9.29.so + 0x2eb1c ]
14 Target : <0x00a2eb08> [ /lib/libuClibc-0.9.29.so + 0x2eb08 ]
Source : <0x00a2eb1c> [ /lib/libuClibc-0.9.29.so + 0x2eb1c ]
15 Target : <0x00a2eb08> [ /lib/libuClibc-0.9.29.so + 0x2eb08 ]
Source : <0x00a2eb1c> [ /lib/libuClibc-0.9.29.so + 0x2eb1c ]
Stack from 02967f04:
ffa00aea ffa00738 002c8554 002c8554 002c8550 002c8560 00000006 00187438
00a2eb84 00000030 00000024 00000000 02968000 00a2eb84 00a2eb84 00a2e760
0138fe38 02003004 031311fd 00a1efcd 031311d4 00a1efcc 000003f6 00000000
00000000 00000000 00000000 00000000 00000140 005c49e0 000000df 00000003
00000000 00000000 00000000 00000000 000000ff 00000000 00000000 00000007
03e77754 00000000 00000000 02c5b24d 03e788f0 03e788f0 0138c211 02970004
QuoteReplyEditDelete
2009-04-05 09:30:36 Re: Crash log analysis help
Robin Getz (UNITED STATES)
Message: 72175
Hari:
No one can do much for you, except send you do the standard documentation.
Since we don't have the exact setup (application or library) that you do to replicate the problem.
-Robin