Syslink_destroy failure

S A Joshi

Hi,

I'm using syslink version 2.00.02.80 with ezsdk 5.2.01.59 and in my application when I call syslink_destroy while tearing down the OpenMAX sequence, there is a crash on DSP with below message:

Serv*** NotifyDrv_detach: The specified user process was not found registered with Notify Driver module.
Error [0xfffffffb] at Line no: 2154 in file /syslink_2_00_02_80/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/ipc/hlos/knl/Linux/NotifyDrv.c
iceMgr_stopXferA*** NotifyDrv_ioctl: Kernel-side NotifyDrv_detach failed

Please let me know what could be the root cause. Any pointers or suggestion would be helpful.

Thanks & Regards,

Joshi

over 13 years ago

0 Chris Ring over 13 years ago

TI__Genius 17205 points

The error reported is 0xfffffffb == -5 == Notify_E_NOTFOUND.

This matches the source code at the reported error condition - line 2154 of NotifyDrv.c. Peeking at that source code shows that error is returned if someone tries to detach from a processor they haven't attached to. Note that attach/detach also appear to be reference counted, so if you attach once, then detach twice, you might also get this.

Maybe you can turn on more trace and look for matching attach/detach calls?

Chris

0 S A Joshi over 13 years ago in reply to Chris Ring

Prodigy 160 points

Thanks Chris for the quick feedback! We are checking on the lines that you suggested and hopefully we should have some sort of root cause...

Best Regards,

Joshi

0 S A Joshi over 13 years ago in reply to S A Joshi

Prodigy 160 points

Chris,

0 S A Joshi over 13 years ago in reply to S A Joshi

Prodigy 160 points

Chris, We found out that syslink_setup() was getting called twice wheras the syslink_destroy() was being called only once. Once we removed the extra syslink_setup() function, this issue seems to be resolved. Thanks for your help!

Processors

Processors forum

Syslink_destroy failure