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.

Internal Error with DM368 V2.6

Expert 1840 points

Hi all,

I am working in Appro design based custom DM368 IPNC. We used latest software IPNC V2.6.

Our camera can start and work normally but it frozen sometimes.

The bugs happen randomly so I still can not figure out the reason.

Some times the error was raised without any message and sometime the error message relate to internal kernel was print out.

I attached the error log in this post. If you have some experiences in this problem please help me.

Thank you very much0184.ev_camera_error.txt!

 

  • It is tough to say from the log, what could have crashed it,

    Can you enable debug messages in Audio thr, AVSERVER_DEBUG_AUDIO_THR by keeping this ON.

    I suspect is due to motion detct + audio combination

     

    Regards,

     

    Raghu

     

  • really thanks for your quick response! 

    I followed your suggestion and got the error message: Error: Alarm server creat thread fail after some minutes of moving camera to create the motion event quickly.

    that mean when the alarm happen the alarm thread got problem to be created if event was raised too fast.

    I printed out the error code of pthread_create and I got 12. This show that an out of memory error was happened during new alarm thread was produced.

    I have never seen this with Appro DM368 camera so I guess our hardware have some problem that effect to these issues.

    However, my experiences are not enough to take it out. Please give your help!

    I attached the log below. I will try to reproduce the internal error and report later.

    Thanks

     

    5657.ev_camera_error1.txt

  • Now, I can reproduce the internal error that relate to stack limit above. I guest this come from around the audio share memory, but I can not figure out which things 

    make this happen. I attached the log in this post. It is great if someone can share me your suggestion or useful hint to step over this problem.

    0045.ev_camera_error2.txt

  • Can you try using the file avServer.c located at av_server\src\common from v2.5 and check if this solves the memroy issue.

    One change the MV data alloc was changed, this can cause this issue.

     

    Regards,

     

    Raghu

     

  • I tried your suggestion. It look better but the problem still available.

    The Issue showed something relate to stack limit in IPNC processes: AVserver, system server, ... I really confuse about these.

    If you have some ideas please support to me. Thanks