• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 1067 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Booting problem with DVR RDK

A0132246
Intellectual 360 points

Hello,

We are using DVR RDK 4.1 for our product development on DM8168 platform. I have tested the system by rebooting continuously. Out of 600 trials of rebooting I have faced the following error in 4 times. After this error, in the next boot the system is booting properly. This error is also very random in nature. Any suggestion? How to fix this issue?

Running init.sh
*** Bootargs Validated for mem param ***
*** Bootargs Validated for notifyk.vpssm3 params ***
*** Kernel Base address validated ***
Kernel bootargs validated
 [c6xdsp ] Remote Debug Shared Memory @ 0xbf000000
 [m3video] Remote Debug Shared Memory @ 0xbf010820
 [m3vpss ] Remote Debug Shared Memory @ 0xbf021040
SysLink version : 2.20.02.20
SysLink module created on Date:Aug 25 2016 Time:15:03:00
Trace enabled
Trace SetFailureReason enabled
 Setting DMM priority for [DUCATI  ] to [0] ( 0x4e000624 = 0x08000000 )
 Setting DMM priority for [HDVICP0 ] to [2] ( 0x4e000634 = 0x0000000a )
 Setting DMM priority for [HDVICP1 ] to [2] ( 0x4e000634 = 0x000a0000 )
 Setting DMM priority for [HDVICP2 ] to [2] ( 0x4e000634 = 0x00a00000 )
/opt/dvr_rdk/ti816x
Running load.sh
Dev_pollOpen: Couldn't open /dev/syslinkipc_Osal: No such file or directory
    Please ensure that SysLink's device driver module (syslink.ko) is installed
OsalDrv driver open: /dev/syslinkipc_Osal: No such file or directory
OsalDrv driver close: /dev/syslinkipc_Osal: Bad file descriptor
Dev_pollOpen: Couldn't open /dev/syslinkipc_MultiProc: No such file or directory
    Please ensure that SysLink's device driver module (syslink.ko) is installed
/dev/syslinkipc_MultiProc: No such file or directory
MultiProc driver close: : Bad file descriptor
Dev_pollOpen: Couldn't open /dev/syslinkipc_SharedRegion: No such file or directory
    Please ensure that SysLink's device driver module (syslink.ko) is installed
SharedRegion driver open: : No such file or directory
SharedRegion driver close: : Bad file descriptor
Dev_pollOpen: Couldn't open /dev/syslinkipc_GateMP: No such file or directory
    Please ensure that SysLink's device driver module (syslink.ko) is installed
/dev/syslinkipc_GateMP: No such file or directory
Dev_pollOpen: Couldn't open /dev/syslinkipc_MessageQ: No such file or directory
    Please ensure that SysLink's device driver module (syslink.ko) is installed
MessageQ driver close: : Bad file descriptor
Dev_pollOpen: Couldn't open /dev/syslinkipc_Notify: No such file or directory
    Please ensure that SysLink's device driver module (syslink.ko) is installed
Notify driver close: /dev/syslinkipc_Notify: Bad file descriptor
Dev_pollOpen: Couldn't open /dev/syslinkipc_ProcMgr: No such file or directory
    Please ensure that SysLink's device driver module (syslink.ko) is installed
ProcMgr driver open: /dev/syslinkipc_ProcMgr: No such file or directory
ProcMgr driver close: /dev/syslinkipc_ProcMgr: Bad file descriptor
Dev_pollOpen: Couldn't open /dev/syslinkipc_HeapBufMP: No such file or directory
    Please ensure that SysLink's device driver module (syslink.ko) is installed
PHY: 0:07 - Link is Up - 1000/Full
Dev_pollOpen: Couldn't open /dev/syslinkipc_HeapMemMP: No such file or directory
    Please ensure that SysLink's device driver module (syslink.ko) is installed
/dev/syslinkipc_HeapMemMP: No such file or directory
Dev_pollOpen: Couldn't open /dev/syslinkipc_ListMP: No such file or directory
    Please ensure that SysLink's device driver module (syslink.ko) is installed
/dev/syslinkipc_ListMP: No such file or directory
Dev_pollOpen: Couldn't open /dev/syslinkipc_RingIO: No such file or directory
    Please ensure that SysLink's device driver module (syslink.ko) is installed
/dev/syslinkipc_RingIO: No such file or directory
RingIO driver close: : Bad file descriptor
Dev_pollOpen: Couldn't open /dev/syslinkipc_RingIOShm: No such file or directory
    Please ensure that SysLink's device driver module (syslink.ko) is installed
/dev/syslinkipc_RingIOShm: No such file or directory
RingIO driver close: : Bad file descriptor
Dev_pollOpen: Couldn't open /dev/syslinkipc_ClientNotifyMgr: No such file or directory
    Please ensure that SysLink's device driver module (syslink.ko) is installed
/dev/syslinkipc_ClientNotifyMgr: No such file or directory
ClientNotifyMgr driver close: : Bad file descriptor
Dev_pollOpen: Couldn't open /dev/syslinkipc_FrameQBufMgr: No such file or directory
    Please ensure that SysLink's device driver module (syslink.ko) is installed
/dev/syslinkipc_FrameQBufMgr: No such file or directory
FrameQBufMgr driver close: : Bad file descriptor
Dev_pollOpen: Couldn't open /dev/syslinkipc_FrameQ: No such file or directory
    Please ensure that SysLink's device driver module (syslink.ko) is installed
/dev/syslinkipc_FrameQ: No such file or directory
FrameQ driver close: : Bad file descriptor
Dev_pollOpen: Couldn't open /dev/syslinkipc_Ipc: No such file or directory
    Please ensure that SysLink's device driver module (syslink.ko) is installed
Assertion at Line no: 344 in /home/jebaraj/dm8168/DVRRDK_04.01.00.02/dvr_rdk/../ti_tools/syslink/syslink_2_20_02_20/packages/ti/syslink/utils/hlos/usr/MultiProc.c: (MultiProc_module->refCount > 0) : failed
Invalid <Core name> specified!
UsagDMA: Module install successful, device major num = 237
e : ./fw_load.ouDRV: Module install successful
t <startup|shutdDRV: Module built on Aug 25 2016 15:03:20
own> <Core name> [File path]

  • 0
    Intellectual 360 points

    One more question, In the same environment I have faced the segmentation fault issue  for 9 times out of 600 trials. But system recovers in the next boot. These 2 error condition occurs independent to each other. The error log:

    INIT: version 2.86 booting

    Please wait: booting...

    Starting udev

    udevd (69): /proc/69/oom_adj is deprecated, please use /proc/69/oom_score_adj instead.

    udev: starting version 141

    Root filesystem already rw, not remounting

    Caching udev devnodes

    Populating dev cache

    Segmentation fault

    FAT: bogus number of reserved sectors

    VFS: Can't find a valid FAT filesystem on dev mmcblk0.

    Configuring network interfaces... net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:07, id=221612)

    done.

    Setting up IP spoofing protection: rp_filter.

    /sbin/ldconfig: /lib/libavformat.so.54 is not a symbolic link

    /sbin/ldconfig: /lib/libswscale.so.2 is not a symbolic link

    /sbin/ldconfig: /lib/libavdevice.so.54 is not a symbolic link

    /sbin/ldconfig: /lib/libavutil.so.51 is not a symbolic link

    /sbin/ldconfig: /lib/libavcodec.so.54 is not a symbolic link

    /sbin/ldconfig: /lib/libavfilter.so.3 is not a symbolic link

    Segmentation fault

    expr: syntax error

    sh: 1: unknown operand

    INIT: Entering runlevel: 5

    Starting system message bus: dbus.

    Starting telnet daemon.

    Starting syslogd/klogd: done

    Starting thttpd.

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

    ==========Starting VPU Application=========

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

    Running init.sh

    *** Bootargs Validated for mem param ***

    *** Bootargs Validated for notifyk.vpssm3 params ***

    *** Kernel Base address validated ***

    Kernel bootargs validated

    [c6xdsp ] Remote Debug Shared Memory @ 0xbf000000

    [m3video] Remote Debug Shared Memory @ 0xbf010820

    [m3vpss ] Remote Debug Shared Memory @ 0xbf021040

    SysLink version : 2.20.02.20

    SysLink module created on Date:Aug 25 2016 Time:15:03:00

    Trace enabled

    Trace SetFailureReason enabled

    Setting DMM priority for [DUCATI  ] to [0] ( 0x4e000624 = 0x08000000 )

    Setting DMM priority for [HDVICP0 ] to [2] ( 0x4e000634 = 0x0000000a )

    Setting DMM priority for [HDVICP1 ] to [2] ( 0x4e000634 = 0x000a0000 )

    Setting DMM priority for [HDVICP2 ] to [2] ( 0x4e000634 = 0x00a00000 )

    /opt/dvr_rdk/ti816x

    Running load.sh

    Attached to slave procId 2.

    Loaded file ../firmware/dvr_rdk_fw_m3vpss_1024M_256M.xem3 on slave procId 2.

    Started slave procId 2.

    After Ipc_loadcallback status [0x00000000]

    [m3vpss ] ***** VPSS Firmware build time 15:21:01 Aug 25 2016  EDG gcc 3.0 mode

    [m3vpss ] ***** SYSTEM  : Frequency <ORG> - 250000000, <NEW> - 274909088

    [m3vpss ] notify_attach  rtnVal  0

    [m3vpss ] initProxyServer  rtnVal  0

    [m3vpss ]  

    After Ipc_startcallback status [0x00000000]

    [m3vpss ]  *** UTILS: CPU KHz = 549818 Khz ***

    [m3vpss ]  

    [m3vpss ]  35: SYSTEM  : System Common Init in progress !!!

    [m3vpss ]  35: SYSTEM: IPC init in progress !!!

    [m3vpss ]  35: SYSTEM: Attaching to [HOST] ...

    [m3vpss ]  47: SYSTEM: Attaching to [HOST] ... SUCCESS !!!

    Attached to slave procId 1.

    DMA: Module install successful, device major num = 237

    DRV: Module install successful

    DRV: Module built on Aug 25 2016 15:03:20

    Segmentation fault

    BusyBox v1.13.2 (2011-03-14 20:51:34 IST) multi-call binary

    Usage: mknod [OPTIONS] NAME TYPE MAJOR MINOR

    Create a special file (block, character, or pipe)

    Options:

    -m Create the special file using the specified mode (default a=rw)

    TYPEs include:

    b: Make a block device

    c or u: Make a character device

    p: Make a named pipe (MAJOR and MINOR are ignored)

    [c6xdsp ] Remote Debug Shared Memory @ 0xbf000000

    [m3video] Remote Debug Shared Memory @ 0xbf010820

    [m3vpss ] Remote Debug Shared Memory @ 0xbf021040

    Attached to slave procId 0.

  • 0 in reply to A0132246
    TI__Guru* 80190 points
    Hello,

    For DVRRDK support check here:
    e2e.ti.com/.../426680

    You could search in the e2e for similar issue.

    BR
    Margarita