when run ./app_remote.xv5T, linux crash

liangxiao zhang

Other Parts Discussed in Thread: OMAP3530

hi,my board is omap3530

when insmod cmemk.ko, I set cmem:CMEM_MODPARAMS="phys_start=0x85000000 phys_end=0x86000000 pools=20x4096,10x131072,2x1048576"

after ./loadmodules.sh, I run:./app_remote.xv5T, the linux crash

as follows:

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

[ 869.889648] CMEMK module: built on May 29 2013 at 18:40:59
[ 869.905487] Reference Linux version 2.6.32
[ 869.910369] File /usr/local/dvsdk/linuxutils_2_25_05_11/packages/ti/sdo/linuxutils/cmem/src/module/cmemk.c
[ 869.924896] allocated heap buffer 0xc8000000 of size 0xcac000
[ 869.931396] cmemk initialized
[ 870.256103] DSPLINK Module (1.65.00.02) created on Date: May 30 2013 Time: 11:29:26
[ 873.092834] Unable to handle kernel NULL pointer dereference at virtual address 00000050
[ 873.100982] pgd = c305c000
[ 873.103729] [00000050] *pgd=82833031, *pte=00000000, *ppte=00000000
[ 873.110076] Internal error: Oops: 17 [#1] PREEMPT
[ 873.114807] last sysfs file: /sys/devices/platform/gpio-keys/modalias
[ 873.121276] Modules linked in: lpm_omap3530 dsplinkk cmemk gpio_keys
[ 873.127746] CPU: 0 Not tainted (2.6.32 #564)
[ 873.132415] PC is at down_interruptible+0x18/0x6c
[ 873.137145] LR is at down_interruptible+0x18/0x6c
[ 873.141906] pc : [<c007f774>] lr : [<c007f774>] psr: 80000093
[ 873.141906] sp : c17dbe48 ip : c4805600 fp : 00000026
[ 873.153472] r10: c4875640 r9 : c3280000 r8 : 00000050
[ 873.158721] r7 : fffffff4 r6 : 00000000 r5 : a0000013 r4 : 00000050
[ 873.165313] r3 : 00000001 r2 : c17da000 r1 : 00000000 r0 : 00000001
[ 873.171905] Flags: Nzcv IRQs off FIQs on Mode SVC_32 ISA ARM Segment user
[ 873.179168] Control: 10c5387d Table: 8305c019 DAC: 00000015
[ 873.184967] Process app_remote.xv5T (pid: 3946, stack limit = 0xc17da2e8)

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

I debug the code ,find Engine_open cause crash.

can you help me?I don't know how to do?

over 12 years ago

0 Cvetolin Shulev-XID over 12 years ago

TI__Guru 65405 points

Hi,

I would like to ask you some questions which could help to investigate the issue:

Are you using codec engine demos?

Are you stop the graphics before running ./app_remote.xv5T?

Which version of DVSDK you are using?

Tsvetolin Shulev

0 liangxiao zhang over 12 years ago in reply to Cvetolin Shulev-XID

Expert 1430 points

Are you using codec engine demos?

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

yes,I use codec engine demos.but the kernel in board is my company project.I just compile and run .ko and xv5T to my board.

---------------------

Are you stop the graphics before running ./app_remote.xv5T?

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

I cann't understand what is graphics?

---------------

Which version of DVSDK you are using?

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

dvsdk_4_01_00_09_omap3530_Release_Notes.pdf

------------------------------------------------------------------------------------------------------------------------------------

I debug the code.log is :

@0,116,162us: [+0 T:0x4001d2f0] ti.sdo.ce.osal.Sem - Sem_create> count: 0
@0,116,254us: [+0 T:0x4001d2f0] ti.sdo.ce.osal.Sem - Leaving Sem_create> sem[0x5b1c0]
@0,116,315us: [+0 T:0x4001d2f0] ti.sdo.ce.osal.Sem - Sem_create> count: 0
@0,116,345us: [+0 T:0x4001d2f0] ti.sdo.ce.osal.Sem - Leaving Sem_create> sem[0x5b1d8]
@0,116,406us: [+0 T:0x4001d2f0] OT - Thread_create> Enter (fxn=0x2b9ac, attrs=0x0)
@0,116,742us: [+0 T:0x4001d2f0] OT - Thread_create> Exit (task=0x5b210)
@0,116,956us: [+0 T:0x4001d2f0] ti.sdo.ce.alg - ALG_init> Enter
@0,117,017us: [+0 T:0x4001d2f0] ti.sdo.ce.alg - ALG_init> Exit
@0,117,108us: [+6 T:0x4001d2f0] CE - Engine_init> CE debugging on (CE_DEBUG=2; allowed CE_DEBUG levels: 1=min, 2=good, 3=max)
@0,117,230us: [+0 T:0x4001d2f0] CS - Server_init()
@0,117,291us: [+0 T:0x4001d2f0] CS - Server_init> Global_useLinkArbiter = 0
@0,117,353us: [+2 T:0x4001d2f0] ti.sdo.ce.examples.apps.video_copy - main> ti.sdo.ce.examples.apps.video_copy
@0,117,597us: [+1 T:0x4001d2f0] ti.sdo.ce.examples.apps.video_copy - App-> Application started.
@0,117,749us: [+4 T:0x4001d2f0] OM - Memory_contigAlloc> CMEM_alloc(1024) = 0x4001f000.
@0,117,810us: [+4 T:0x4001d2f0] OM - Memory_contigAlloc> CMEM_getPhys(0x4001f000) = 0x85fff000.
@0,117,902us: [+4 T:0x4001d2f0] OM - Memory_contigAlloc> CMEM_alloc(1024) = 0x40020000.
@0,117,963us: [+4 T:0x4001d2f0] OM - Memory_contigAlloc> CMEM_getPhys(0x40020000) = 0x85ffe000.
@0,118,054us: [+4 T:0x4001d2f0] OM - Memory_contigAlloc> CMEM_alloc(1024) = 0x40021000.
@0,118,115us: [+4 T:0x4001d2f0] OM - Memory_contigAlloc> CMEM_getPhys(0x40021000) = 0x85ffd000.
@0,118,329us: [+0 T:0x4001d2f0] CE - Engine_open> Enter('video_copy', 0x0, 0xbeac8c1c)
@0,118,421us: [+0 T:0x4001d2f0] CE - rserverOpen('all.x64P'), count = 0
@0,118,482us: [+0 T:0x4001d2f0] OP - Processor_create> Enter(imageName='all.x64P', linkCfg='(null)', attrs=0xbeac8c00)
@0,118,604us: [+0 T:0x4001d2f0] OP - doCmd> Enter (cmdId=1, proc=0x5b880)
@0,118,665us: [+0 T:0x4001d2f0] ti.sdo.ce.osal.Sem - Entered Sem_post> sem[0x5b1c0]
@0,118,756us: [+0 T:0x4001d2f0] ti.sdo.ce.osal.Sem - Leaving Sem_post> sem[0x5b1c0]
@0,118,817us: [+0 T:0x4001d2f0] ti.sdo.ce.osal.Sem - Entered Sem_pend> sem[0x5b1d8] timeout[0xffffffff]
@0,118,970us: [+1 T:0x4096d490] OP - daemon> thread created.
@0,119,031us: [+0 T:0x4096d490] OP - getCmd_d> Enter (proc=0x4096cdd8)
@0,119,062us: [+0 T:0x4096d490] ti.sdo.ce.osal.Sem - Entered Sem_pend> sem[0x5b1c0] timeout[0xffffffff]
@0,119,123us: [+0 T:0x4096d490] ti.sdo.ce.osal.Sem - Leaving Sem_pend> sem[0x5b1c0] status[0]
@0,119,153us: [+0 T:0x4096d490] OP - getCmd_d> Exit (result=1)
@0,119,214us: [+0 T:0x4096d490] OP - Processor_create_d> Enter(proc=0x5b880)
@0,119,245us: [+0 T:0x4096d490] ti.sdo.ce.ipc.Power - Power_on> Enter(handle=0x5b89c)
@0,119,306us: [+2 T:0x4096d490] ti.sdo.ce.ipc.Power - Power_on> Opening Local Power Manager for the DSP on /dev/lpm0...

system crash.

ti.sdo.ce.osal.Sem - Entered Sem_pend> sem[0x5b1c0] timeout[0xffffffff]

why is timeout?

I gusess it is dsp mem cause crash.

so I change the all_evm3530.tci.but it still crash.

can you tell why? and how to config the mem and how many files to config?

0 Cvetolin Shulev-XID over 12 years ago in reply to liangxiao zhang

TI__Guru 65405 points

Hi Liangxiao,

As I write "graphics" I mean "The Matrix Application Launcher GUI" and make sure you have terminated the Matrix GUI before running any other applications
from the command line:

/etc/init.d/matrix-gui-e stop

/etc/init.d/pvr-init stop

Then try to start the application with debugs with the following commands:

cd /usr/share/ti/ti-codec-engine-examples/
./loadmodules.sh
cd video1_copy

CE_DEBUG=3 ./app_remote.xv5T -s all.x64P

It should be useful to see the output.

Tsvetolin Shulev

0 Margarita Gashova over 12 years ago in reply to liangxiao zhang

TI__Guru* 80190 points

Hello

liangxiao zhang said:
yes,I use codec engine demos.but the kernel in board is my company project.I just compile and run .ko and xv5T to my board.

liangxiao zhang said:
@0,118,817us: [+0 T:0x4001d2f0] ti.sdo.ce.osal.Sem - Entered Sem_pend> sem[0x5b1d8] timeout[0xffffffff]
@0,118,970us: [+1 T:0x4096d490] OP - daemon> thread created.
@0,119,031us: [+0 T:0x4096d490] OP - getCmd_d> Enter (proc=0x4096cdd8)
@0,119,062us: [+0 T:0x4096d490] ti.sdo.ce.osal.Sem - Entered Sem_pend> sem[0x5b1c0] timeout[0xffffffff]
@0,119,123us: [+0 T:0x4096d490] ti.sdo.ce.osal.Sem - Leaving Sem_pend> sem[0x5b1c0] status[0]

Maybe your build is broken . Check which libs are getting linked in

Could you double check XDCPATH and then recompile xv5T.

Best Regards,

Margarita

Processors

Processors forum

when run ./app_remote.xv5T, linux crash