2008-01-22 02:41:19     cplb error

Document created by Aaronwu Employee on Aug 5, 2013
Version 1Show Document
  • View in full screen mode

2008-01-22 02:41:19     cplb error

jk Thiruppathi (INDIA)

Message: 49907    hi all,

I m using a bf533 based custom h/w. In that, while running my application, I got cplb error. Sometimes it is working fine. But, I got this error very frequently.

===================================================================================

Data access CPLB miss

- Used by the MMU to signal a CPLB miss on a data access.

 

CURRENT PROCESS:

 

COMM=testexe PID=53

TEXT = 0x00e00000-0x00f4de14 DATA = 0x02000e14-0x02547b8c

BSS = 0x02547b8c-0x00900000 USER-STACK = 0x0091fec0

 

return address: 0x00cb42fa; contents of [PC-16...PC+8]:

e801 0000 05b4 0010 0000 05f5 e800 0003

3228 3039 3032 e3ff ffac 3208 932f b06e X

e588 0041 b0a8 afca 0c42 bcea 1805 09d5

 

RETE: 00000000 RETN: 02814000 RETX: 00cb42fa RETS: 00cb42f4

IPEND: 0030 SYSCFG: 0036

SEQSTAT: 00000026 SP: 02813f24

R0: 0a787878 R1: 0a787878 R2: 02836673 R3: 00f3e41c

R4: 00000008 R5: 008f18b8 R6: 008f0f50 R7: 0093e8b0

P0: 00000000 P1: 0a787878 P2: 0083000c P3: 0082d010

P4: 0225f3e8 P5: 028367d4 FP: 02836688

A0.w: 00000000 A0.x: 00000000 A1.w: 00000000 A1.x: 00000000

LB0: 030dd5c1 LT0: 030dd5c0 LC0: 00000000

LB1: 00ee5e7f LT1: 00ee5e7e LC1: 00000000

B0: 00000000 L0: 00000000 M0: 00000000 I0: 025474e4

B1: 00000000 L1: 00000000 M1: 00000000 I1: 00000000

B2: 00000000 L2: 00000000 M2: 00000000 I2: 00000000

B3: 00000000 L3: 00000000 M3: 00000000 I3: 00000000

 

USP: 0283667c ASTAT: 02003004

DCPLB_FAULT_ADDR=0a7878b9

ICPLB_FAULT_ADDR=00cb42fa

 

 

Hardware Trace:

0 Target : <0x003034d4> { _trap_c + 0x0 }

Source : <0xffa00b3c> { _exception_to_level5 + 0xb4 }

1 Target : <0xffa00a88> { _exception_to_level5 + 0x0 }

Source : <0xffa00a86> { _ex_trap_c + 0x4e }

2 Target : <0xffa009e0> { _handle_bad_cplb + 0x0 }

Source : <0xffa004f4> { __cplb_hdr + 0x5c }

3 Target : <0xffa004f2> { __cplb_hdr + 0x5a }

Source : <0x00303466> { _panic_cplb_error + 0x16 }

4 Target : <0x00303450> { _panic_cplb_error + 0x0 }

Source : <0xffa004ee> { __cplb_hdr + 0x56 }

5 Target : <0xffa004ea> { __cplb_hdr + 0x52 }

Source : <0xffa004da> { __cplb_hdr + 0x42 }

6 Target : <0xffa004d4> { __cplb_hdr + 0x3c }

Source : <0xffa004ce> { __cplb_hdr + 0x36 }

7 Target : <0xffa004cc> { __cplb_hdr + 0x34 }

Source : <0xffa004c4> { __cplb_hdr + 0x2c }

8 Target : <0xffa004c0> { __cplb_hdr + 0x28 }

Source : <0xffa00638> { _cplb_mgr + 0x140 }

9 Target : <0xffa00634> { _cplb_mgr + 0x13c }

Source : <0xffa0079c> { _cplb_mgr + 0x2a4 }

10 Target : <0xffa00794> { _cplb_mgr + 0x29c }

Source : <0xffa007a0> { _cplb_mgr + 0x2a8 }

11 Target : <0xffa00794> { _cplb_mgr + 0x29c }

Source : <0xffa007b0> { _cplb_mgr + 0x2b8 }

12 Target : <0xffa00794> { _cplb_mgr + 0x29c }

Source : <0xffa007b0> { _cplb_mgr + 0x2b8 }

13 Target : <0xffa00794> { _cplb_mgr + 0x29c }

Source : <0xffa007b0> { _cplb_mgr + 0x2b8 }

14 Target : <0xffa00794> { _cplb_mgr + 0x29c }

Source : <0xffa007b0> { _cplb_mgr + 0x2b8 }

15 Target : <0xffa00794> { _cplb_mgr + 0x29c }

Source : <0xffa007b0> { _cplb_mgr + 0x2b8 }

Stack from 02813f04:

02095ee0 ffa00b40 00458710 00458710 0045870c 0280d000 0225f3e4 00300000

00cb42fa 00000030 00000026 00000000 02814000 00cb42fa 00cb42fa 00cb42f4

0a787878 02003004 00ee5e7f 030dd5c1 00ee5e7e 030dd5c0 00000000 00000000

00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 00000000 025474e4 0283667c 02836688 028367d4 0225f3e8

Call Trace:

 

 

Exception: IRQ 0x5 entered

code=[0x0000c026], stack frame=0x02813dfc, bad PC=0x0030ef54

----------- HARDWARE ERROR -----------

External Memory Addressing Error

 

CURRENT PROCESS:

 

COMM=testexe PID=53

TEXT = 0x00e00000-0x00f4de14 DATA = 0x02000e14-0x02547b8c

BSS = 0x02547b8c-0x00900000 USER-STACK = 0x0091fec0

 

return address: 0x0030ef54; contents of [PC-16...PC+8]:

 

 

RETE: 00000000 RETN: 02814000 RETX: 00cb42fa RETS: ffa00482

IPEND: 4020 SYSCFG: 0036

SEQSTAT: 0000c026 SP: 02813dfc

R0: 0000ffe0 R1: 00000100 R2: 00000100 R3: 00000000

R4: 00000008 R5: 008f18b8 R6: 0000000a R7: 00000002

P0: 02813e7c P1: 008245a8 P2: 02812000 P3: 00498a18

P4: 00496f58 P5: 0049a348 FP: 00491ae0

A0.w: 00000000 A0.x: 00000000 A1.w: 00000000 A1.x: 00000000

LB0: 030dd5c1 LT0: 030dd5c0 LC0: 00000000

LB1: 00ee5e7f LT1: 00ee5e7e LC1: 00000000

B0: 00000000 L0: 00000000 M0: 00000000 I0: 00000001

B1: 00000000 L1: 00000000 M1: 00000000 I1: 00000000

B2: 00000000 L2: 00000000 M2: 00000000 I2: ffffa646

B3: 00000000 L3: 00000000 M3: 00000000 I3: 00000000

 

USP: 0283667c ASTAT: 02002000

DCPLB_FAULT_ADDR=0a7878b9

ICPLB_FAULT_ADDR=00cb42fa

 

 

Kernel panic - not syncing: Unhandled IRQ or exceptions!

==========================================================================================

 

 

 

After this, using the "debugging application" webpage of blackfin doc website, I have enabled the option in

kernel hacking->trace user application. After that, I got the following error message.

 

===========================================================================================

Data access misaligned address violation

- Attempted misaligned data memory or data cache access.

 

CURRENT PROCESS:

 

COMM=testexe PID=53

TEXT = 0x00c00000-0x00d4de14 DATA = 0x02000e14-0x02547b8c

BSS = 0x02547b8c-0x03100000 USER-STACK = 0x0311fec0

 

return address: 0x032eb9c4; contents of [PC-16...PC+8]:

3208 0c04 bc8d 930d b04e 1804 3204 b080

2005 321f e51a 00f9 9310 0c44 1c03 a238 X

9220 e801 0000 3044 05a4 0010 0578 0c00

 

RETE: 00000000 RETN: 00e52000 RETX: 032eb9c4 RETS: 032eb916

IPEND: 0030 SYSCFG: 0036

SEQSTAT: 00000024 SP: 00e51f24

R0: 00002a40 R1: 00002a40 R2: 496b7162 R3: 00e67ff4

R4: 00e291c8 R5: 00010001 R6: 00003009 R7: 00e298b8

P0: 00e291c8 P1: 00ae74bc P2: 00e291dc P3: 0302d010

P4: b77b0e9e P5: 00e291cc FP: 00e6affc

A0.w: 00000000 A0.x: 00000000 A1.w: d7abec6c A1.x: 00000000

LB0: 032dd521 LT0: 032dd51e LC0: 00000000

LB1: 00ce5e7f LT1: 00ce5e7e LC1: 00000000

B0: 02547294 L0: 00000000 M0: 60502f16 I0: 00e252bc

B1: 025472d4 L1: 00000000 M1: 34d94745 I1: 00e298b8

B2: 00e665d0 L2: 00000000 M2: 00000000 I2: 00e665d4

B3: 02546f94 L3: 00000000 M3: 00000000 I3: 02546f94

 

USP: 00e6afe4 ASTAT: 02003005

DCPLB_FAULT_ADDR=b77b0e9c

ICPLB_FAULT_ADDR=032eb9c4

 

 

Hardware Trace:

0 Target : <0x003034d4> { _trap_c + 0x0 }

Source : <0xffa00b78> { _exception_to_level5 + 0xb4 }

1 Target : <0xffa00ac4> { _exception_to_level5 + 0x0 }

Source : <0xffa00ac2> { _ex_trap_c + 0x5a }

2 Target : <0xffa00bf0> { _trap + 0x0 }

Source : <0x032eb9c2> [ /lib/libuClibc-0.9.29.so + 0x2b9c2 ]

3 Target : <0x032eb9c2> [ /lib/libuClibc-0.9.29.so + 0x2b9c2 ]

Source : <0x032eb918> [ /lib/libuClibc-0.9.29.so + 0x2b918 ]

4 Target : <0x032eb916> [ /lib/libuClibc-0.9.29.so + 0x2b916 ]

Source : <0x00ae5abe> [ /lib/libpthread-0.9.29.so + 0x5abe ]

5 Target : <0x00ae5ab8> [ /lib/libpthread-0.9.29.so + 0x5ab8 ]

Source : <0x00ae5a84> [ /lib/libpthread-0.9.29.so + 0x5a84 ]

6 Target : <0x00ae5a82> [ /lib/libpthread-0.9.29.so + 0x5a82 ]

Source : <0x00ae5a94> [ /lib/libpthread-0.9.29.so + 0x5a94 ]

7 Target : <0x00ae5a94> [ /lib/libpthread-0.9.29.so + 0x5a94 ]

Source : <0x00ae74ca> [ /lib/libpthread-0.9.29.so + 0x74ca ]

8 Target : <0x00ae74bc> [ /lib/libpthread-0.9.29.so + 0x74bc ]

Source : <0x00ae3df4> [ /lib/libpthread-0.9.29.so + 0x3df4 ]

9 Target : <0x00ae3dec> [ /lib/libpthread-0.9.29.so + 0x3dec ]

Source : <0x00ae5a90> [ /lib/libpthread-0.9.29.so + 0x5a90 ]

10 Target : <0x00ae5a8a> [ /lib/libpthread-0.9.29.so + 0x5a8a ]

Source : <0x00ae5a5e> [ /lib/libpthread-0.9.29.so + 0x5a5e ]

11 Target : <0x00ae5a48> [ /lib/libpthread-0.9.29.so + 0x5a48 ]

Source : <0x032ef3ac> [ /lib/libuClibc-0.9.29.so + 0x2f3ac ]

12 Target : <0x032ef394> [ /lib/libuClibc-0.9.29.so + 0x2f394 ]

Source : <0x032cba4e> [ /lib/libuClibc-0.9.29.so + 0xba4e ]

13 Target : <0x032cba46> [ /lib/libuClibc-0.9.29.so + 0xba46 ]

Source : <0x032eb912> [ /lib/libuClibc-0.9.29.so + 0x2b912 ]

14 Target : <0x032eb90c> [ /lib/libuClibc-0.9.29.so + 0x2b90c ]

Source : <0x032ebda0> [ /lib/libuClibc-0.9.29.so + 0x2bda0 ]

15 Target : <0x032ebd9c> [ /lib/libuClibc-0.9.29.so + 0x2bd9c ]

Source : <0x032ebd92> [ /lib/libuClibc-0.9.29.so + 0x2bd92 ]

Stack from 00e51f04:

ffa003c8 ffa00b7c 00458710 00458710 0045870c 000000b4 00e291c8 00ae73ba

032eb9c4 00000030 00000024 00000000 00e52000 032eb9c4 032eb9c4 032eb916

00002a40 02003005 00ce5e7f 032dd521 00ce5e7e 032dd51e 00000000 00000000

d7abec6c 00000000 00000000 00000000 02546f94 00e665d0 025472d4 02547294

00000000 00000000 00000000 00000000 00000000 00000000 34d94745 60502f16

02546f94 00e665d4 00e298b8 00e252bc 00e6afe4 00e6affc 00e291cc b77b0e9e

Call Trace:

===========================================================================================

any suggestion on solving this???

 

 

regards,

jk

QuoteReplyEditDelete

 

 

2008-01-22 03:03:10     Re: cplb error

Mike Frysinger (UNITED STATES)

Message: 49909    what kernel/toolchain version are you using ?

QuoteReplyEditDelete

 

 

2008-01-22 03:33:09     Re: cplb error

jk Thiruppathi (INDIA)

Message: 49910    I m using 2007R1

QuoteReplyEditDelete

 

 

2008-01-22 03:52:14     Re: cplb error

Mike Frysinger (UNITED STATES)

Message: 49911    you'll have to gather the symbols from the libraries you have, but it seems that it's crashing instead of sigwait and that you're using a pthreaded application ?

 

i dont think 2007R1 has it, but the next release will have the ability to increase the size of the trace buffer so you could see the last function your application called ...

QuoteReplyEditDelete

 

 

2008-01-22 04:06:47     Re: cplb error

jk Thiruppathi (INDIA)

Message: 49912    Dear mike, I m using pthread application. So, you mean that, currently the trace buffer is not having enough size to hold the last function called?, Is there any other method/way to resolve this issue? So that, I will try.

 

Regards,

Jk

QuoteReplyEditDelete

 

 

2008-01-23 10:45:00     Re: cplb error

Robin Getz (UNITED STATES)

Message: 50034    You can try to do, in the kernel:

- Kernel hacking -> Trace user apps

 

This will help a bit.

 

-Robin

QuoteReplyEditDelete

 

 

2008-01-23 11:50:14     Re: cplb error

Andrea Federico (UNITED STATES)

Message: 50042    I have the same problem.

I use uClinux_2007R1-RC3 and relative toolchain.

 

This problem is present if I compile in FDPIC format and it run perfectly if I compile in FLAT.

Attachments

    Outcomes