• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 100 subscribers
  • Views 618 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.

DM816x Soft kernel crash with v4l2 driver.

Krunal Patil
Genius 3120 points
Other Parts Discussed in Thread: TVP7002

Hi,

When I run saLoopback application with V4l2 based capture (TVP7002). I get following crash. Has anyone encountered same issue? If yes, did anyone tried to find root cause or solution of this problem?

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

------------[ cut here ]------------
WARNING: at kernel/softirq.c:159 local_bh_enable+0x54/0xc4()
Modules linked in: bufferclass_ti omaplfb pvrsrvkm ti81xxhdmi tvp7002 ti81xxvin sii9135 ti81xxvo ti81xxfb vpss syslink ipv6
Backtrace:
[<c0048b58>] (dump_backtrace+0x0/0x110) from [<c036b8d8>] (dump_stack+0x18/0x1c)
 r7:00000000 r6:c00712d0 r5:c042e572 r4:0000009f
[<c036b8c0>] (dump_stack+0x0/0x1c) from [<c006bd54>] (warn_slowpath_common+0x54/0x6c)
[<c006bd00>] (warn_slowpath_common+0x0/0x6c) from [<c006bd90>] (warn_slowpath_null+0x24/0x2c)
 r9:c04d94bc r8:cb08c880 r7:0000000f r6:c72a1a00 r5:c04b330c
r4:c05047c0
[<c006bd6c>] (warn_slowpath_null+0x0/0x2c) from [<c00712d0>] (local_bh_enable+0x54/0xc4)
[<c007127c>] (local_bh_enable+0x0/0xc4) from [<c0065c58>] (omap_mbox_msg_send+0xcc/0xdc)
 r5:c04b330c r4:00000000
[<c0065b8c>] (omap_mbox_msg_send+0x0/0xdc) from [<c02aca90>] (notify_shm_drv_send_event+0x1c8/0x208)
 r5:00000001 r4:00000000
[<c02ac8c8>] (notify_shm_drv_send_event+0x0/0x208) from [<c02aa220>] (notify_send_event+0x114/0x26c)
[<c02aa10c>] (notify_send_event+0x0/0x26c) from [<bf18c610>] (vps_fvid2_queue+0x94/0x1cc [vpss])
[<bf18c57c>] (vps_fvid2_queue+0x0/0x1cc [vpss]) from [<bf1955b0>] (capture_queue+0x50/0x64 [vpss])
 r8:bf1cd404 r7:60000013 r6:c6fecd80 r5:00000000 r4:c5f6b400
[<bf195560>] (capture_queue+0x0/0x64 [vpss]) from [<bf1cc1c8>] (ti81xxvin_buffer_queue+0x9c/0xe8 [ti81xxvin])
 r5:c5fb4000 r4:c5f6b400
[<bf1cc12c>] (ti81xxvin_buffer_queue+0x0/0xe8 [ti81xxvin]) from [<c0283a78>] (videobuf_streamon+0x80/0xd0)
 r7:60000013 r6:c5fb41c4 r5:c5fb4104 r4:c6fecd80
[<c02839f8>] (videobuf_streamon+0x0/0xd0) from [<bf1cbc40>] (vidioc_streamon+0x244/0x400 [ti81xxvin])
 r7:c5ffd600 r6:00000001 r5:c5fb4000 r4:c5fb4104
[<bf1cb9fc>] (vidioc_streamon+0x0/0x400 [ti81xxvin]) from [<c0279380>] (__video_do_ioctl+0x1618/0x3f34)
 r6:40045612 r5:00000000 r4:00000001
[<c0277d68>] (__video_do_ioctl+0x0/0x3f34) from [<c0277b58>] (__video_usercopy+0x2e4/0x428)
[<c0277874>] (__video_usercopy+0x0/0x428) from [<c0277ccc>] (video_ioctl2+0x30/0x38)
[<c0277c9c>] (video_ioctl2+0x0/0x38) from [<c0276d0c>] (v4l2_ioctl+0xe8/0x11c)
 r5:c5ffd600 r4:c6fecb80
[<c0276c24>] (v4l2_ioctl+0x0/0x11c) from [<c00d10e4>] (vfs_ioctl+0x28/0x44)
 r9:c7172000 r8:beeb5c94 r7:00000003 r6:00000003 r5:c6fecb80
r4:00000000
[<c00d10bc>] (vfs_ioctl+0x0/0x44) from [<c00d17f4>] (do_vfs_ioctl+0x500/0x540)
[<c00d12f4>] (do_vfs_ioctl+0x0/0x540) from [<c00d188c>] (sys_ioctl+0x58/0x7c)
[<c00d1834>] (sys_ioctl+0x0/0x7c) from [<c0044da0>] (ret_fast_syscall+0x0/0x30)
 r8:c0044f48 r7:00000036 r6:000124d0 r5:0001215c r4:beeb5c94
---[ end trace 356cb976708ec655 ]---

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

--

Regards,

Krunal

  • 0
    TI__Prodigy 495 points

    Hi Krunal,

    Below is the procedure to run the saLoopback example on ezSDK setup.

    cp /usr/share/ti/ti-media-controller-utils/load-hd-v4l2-firmware.sh /etc/init.d/load-hd-firmware.sh
    $ sync

    Power cycles your board.

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

    echo 0 > /sys/devices/platform/vpss/graphics0/enabled

    Now run  saLoopBack (Display will come on HDMI)

    What version of ezSDK you are using?

    Thanks and regards

    Sachin Kumar

  • 0 in reply to Sachin Thathgur
    Genius 3120 points

    Hi Sachin,

    I am using ezsdk_5_03 and followed the same steps.

    I am able to see display on HDMI, their is no issue with the expected functionality but the crash looks annoying on the terminal, So just wanted to know is it know issue? If yes, is there any kernel patch or solution available for this?

    --

    Regards,

    Krunal

  • 0 in reply to Krunal Patil
    TI__Prodigy 495 points

    Hi Krunal,

    I have not seen this issue on ezSDK_05_03_01_15 DM8168 PG-2.0,Rev H.

    Very first time below error is coming

    VPSS_DCTRL: failed to disable the venc.
    VPSS_DCTRL: failed to disable hdmi venc
    VPSS_DCTRL: stop venc before changing mode

    And for next run the display is proper and no error message is coming.

    This example (saLoopBack) is not part of ezSDK. From where you have downloaded this example. I have attached the saLoopBack.c .

    Thanks and regards

    Sachin Kumar

  • 0 in reply to Sachin Thathgur
    Expert 2425 points

    I had the similar problem with you.

    Please try this:

        #/etc/init.d/matrix-gui-e stop
        #/etc/init.d/pvr-init stop
        #echo 0 > /sys/devices/platform/vpss/display1/enabled
        #echo 1080p-60 > /sys/devices/platform/vpss/display1/mode
        #echo 1 > /sys/devices/platform/vpss/display1/enabled
        #cat /sys/devices/platform/vpss/display1/mode

    Regards,

    Jun