FAQ: [#6805] run mcapi case msg1 msg2 continuously would make coreb execption(2011)

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

[#6805] run mcapi case msg1 msg2 continuously would make coreb execption

Submitted By: Mingquan Pan

Open Date

2011-09-30 03:18:02    

Priority:

Medium High     Assignee:

steven miao

Status:

Open     Fixed In Release:

N/A

Found In Release:

2011R1     Release:

Category:

N/A     Board:

N/A

Processor:

BF561     Silicon Revision:

Is this bug repeatable?:

Yes     Resolution:

N/A

Uboot version or rev.:

    Toolchain version or rev.:

5013

App binary format:

N/A     

Summary: run mcapi case msg1 msg2 continuously would make coreb execption

Details:

 

run mcapi case msg1 msg2 continuously would make coreb execption .

 

On the target, it would print:

 

COREB: execption 26 addr feb03f9c

COREB: execption 26 addr feb03f9c

COREB: execption 26 addr feb03f9c

COREB: execption 26 addr feb03f9c

 

 

Follow-ups

 

--- steven miao                                              2011-10-10 23:40:14

caused by WARN_ON when multi process call icc_release

 

--- Mingquan Pan                                             2011-10-14 01:39:52

Now these two cases can run together without this error, but if run all of the

cases in a low and repeatedly in a loop, it would still show this coreb

execption after two rounds of all cases and stops at pkt1.

 

 

 

--- steven miao                                              2011-11-18 03:43:13

it will fail at the 68th test of 100, there's a memory leak problem in icc

driver somewhere

 

--- Mingquan Pan                                             2011-11-24 22:42:40

It is now repeating msg1 about 40 times.

 

CAPI_DEBUG:mcapi_trans_valid_endpoint endpoint=0x65 (database indices:

n=0,e=101) rc=1^M

MCAPI_DEBUG:domain 0 node 0 endpoint 101^M

MCAPI_DEBUG:index 101 101^M

MCAPI_DEBUG:mcapi_trans_msg_available avail = 0^M

MCAPI_DEBUG:domain 0 node 0 endpoint 101^M

MCAPI_DEBUG:index 101 101^M

MCAPI_DEBUG:mcapi_trans_valid_endpoint endpoint=0x65 (database indices:

n=0,e=101) rc=1^M

MCAPI_DEBUG:domain 0 node 0 endpoint 101^M

MCAPI_DEBUG:index 101 101^M

MCAPI_DEBUG:mcapi_trans_msg_available avail = 0^M

MCAPI_DEBUG:domain 0 node 0 endpoint 101^M

MCAPI_DEBUG:index 101 101^M

MCAPI_DEBUG:mcapi_trans_valid_endpoint endpoint=0x65 (database indices:

n=0,e=101) rc=1^M

MCAPI_DEBUG:domain 0 node 0 endpoint 101^M

MCAPI_DEBUG:index 101 101^M

MCAPI_DEBUG:mcapi_trans_msg_available avail = 0^M

MCAPI_DEBUG:domain 0 node 0 endpoint 101^M

MCAPI_DEBUG:index 101 101^M

MCAPI_DEBUG:mcapi_trans_valid_endpoint endpoint=0x65 (database indices: n=time

out!!

 

Last passed test result is not found!!

 

Case 38 ...FAIL

 

--- steven miao                                              2011-12-16 02:30:55

add dcplb miss handler for coreb

 

--- Mingquan Pan                                             2011-12-29 04:47:50

From the test log these days, this error still would come out from time to

time.

 

And the longest testing process is ending up with 200+ rounds of testcases, and

then failed with malloc failure.

 

COREB: free buffer 3d84000^M

The case is ending!! corea_case_status: 1, coreb_case_status 1 ,

execption_count 0!!

case pass!!!

 

Case 204 ...PASS

 

Case 204 ...PASS

 

!!!!!#####The second part. Case_name: msg2, the 98 time testing! t = 8, i = 97

!

COREB: sm_handle_control_message type 4000000^M

...

root:/bin> ^[[6n./icc_loader -f -e ./mcapi_msg2 ^M

writingCtoO0x0Rc00E00,B0x5:54    bstesm OK_handle_control_message type

2000000^M

^M

task_init_addr 3c00208^M

task_exit_addr ffffffff^M

COREB: sm_handle_control_message 2000000 2000000^M

COREB: task exit 0^M

COREB: task init 3c00208 exit 0^M

m /COREB: @@@ gen pool create0 ^M

COREB: @@@ gen pool create1 ^M

COREB: session table 3d00000^M

COREB: sm_send_message_internal() dst 0 src 1 2000001^M

tCOREB: finish sm_handle_control_message task status 1^M

COREB: finish1 sm_handle_control_message task status 1^M

COREB: before run task 3c00208^M

COREB: [icc_task_init] 71^M

mpCOREB: [icc_task_init] 76^M

COREB: create ep ^M

COREB: create ep index 0 srcep 5^M

COREB: ep1 10005   ^M

/COREB: create ep ^M

COREB: index 0 ,local ep 5^M

COREB: create ep index 1 srcep 6^M

COREB: ep2 10006   ^M

* 2> /dev/null; dmesg -c > /dev/null^M

root:/bin> rm /tmp/* 2> /dev/null; dmesg -c > /dev/null^M

root:/bin> ^[[6nspawn /bin/sh -c rsh -l root 10.100.4.50 ' msg2 >

/tmp/corea.log  2>&1 ; cat /tmp/* ; dmesg' ^M

sh: can't execute 'cat': Cannot allocate memory^M

sh: can't execute 'dmesg': Cannot allocate memory^M

The case is ending!! corea_case_status: 0, coreb_case_status 0 ,

execption_count 0!!

case fail!!!

spawn /bin/sh^M

linux66-561-jtag-capture:~/work/cruise/checkouts/uclinux-dist/testsuites/mcapi>

rsh -l root 10.100.4.50 ' cat /tmp/* ; dmesg' ^M

sh: can't execute 'cat': Cannot allocate memory^M

sh: can't execute 'dmesg': Cannot allocate memory^M

linux66-561-jtag-capture:~/work/cruise/checkouts/uclinux-dist/testsuites/mcapi>

print log time out!!

 

Last passed test result is not found!!

 

Case 205 ...FAIL

 

 

 

    Files

    Changes

    Commits

    Dependencies

    Duplicates

    Associations

    Tags

 

File Name     File Type     File Size     Posted By

mcapi_test_log    application/octet-stream    632691    Mingquan Pan

Attachments

Outcomes