Forums - tile operation cause DSP runtime crash during loading model

6 posts / 0 new
or Register
Last post
tile operation cause DSP runtime crash during loading model
zf.africa
Join Date: 15 Jun 17
Posts: 51
Posted: Thu, 2019-04-25 03:43
Top

Hi All,

Does anyone run tile operation on DSP runtime successfully?

I have a tile operation outputs to a conv2d, after converting model, and load it on DSP runtime.

It would return NULL pointer by snpe builder.

After remove tile operation, it can be loaded perfectly.

Does it a issue of DSP runtime driver or something else?

Anyone knows about this issue? Any comments are appreciated!

BTW: I am using tensorflow r1.13, and C++ API of SNPE SDK.

 

 

  • Up0
  • Down0
Re: tile operation cause DSP runtime crash during loading model
gesqdn-forum
Join Date: 4 Nov 18
Posts: 184
Posted: Mon, 2019-04-29 07:20
Top

Hi,
From the information provided in SNPE Docs, the "tile operation layer" is not supported for tensorflow framework.
Kindly check the supported layers from the reference document mentioned above.
 

  • Up0
  • Down0
Re: tile operation cause DSP runtime crash during loading model
zf.africa
Join Date: 15 Jun 17
Posts: 51
Posted: Mon, 2019-04-29 23:21
Top

Hi,

Does it mean that, in the "Supported Network Layers", blank cell stands for "Not Supported" by the related framework?

What does "n/a" mean? Not yet tested?

  • Up0
  • Down0
Re: tile operation cause DSP runtime crash during loading model
zf.africa
Join Date: 15 Jun 17
Posts: 51
Posted: Tue, 2019-04-30 01:00
Top

Hi gesqdn-forum,

The issue only appears on DSP runtime, the models works fine on CPU/GPU runtime.

So it supports no DSP runtime?

  • Up0
  • Down0
Re: tile operation cause DSP runtime crash during loading model
gesqdn-forum
Join Date: 4 Nov 18
Posts: 184
Posted: Tue, 2019-04-30 07:27
Top

Hi,
can you share more details of the crash, so that we can help you in debugging the issue.

  • Up0
  • Down0
Re: tile operation cause DSP runtime crash during loading model
zf.africa
Join Date: 15 Jun 17
Posts: 51
Posted: Sat, 2019-05-04 23:49
Top

Hi gesqdn-forum,

The crash log is listed below:

Quote:

04-04 02:42:52.161 25580-25580/com.via.viadetect E/VIADetect: runtime: DSP Supported
04-04 02:42:53.223 25580-25580/com.via.viadetect D/com.via.viadetect: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:651: Error ffffffff: remote handle invoke failed. domain 0, handle 3760d580, sc 30200, pra 0x7ff8dd4200
04-04 02:42:53.223 25580-25612/com.via.viadetect D/com.via.viadetect: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:651: Error ffffffff: remote handle invoke failed. domain 0, handle 3, sc 4020200, pra 0x762a5e53f8
04-04 02:42:53.223 25580-25612/com.via.viadetect E/com.via.viadetect: vendor/qcom/proprietary/adsprpc/src/listener_android.c:246:listener protocol failure ffffffff
04-04 02:42:53.224 25580-25612/com.via.viadetect D/com.via.viadetect: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:651: Error 27: remote handle invoke failed. domain 0, handle 3, sc 4020200, pra 0x762a5e53f8
04-04 02:42:53.224 25580-25612/com.via.viadetect E/com.via.viadetect: vendor/qcom/proprietary/adsprpc/src/listener_android.c:253::error: 39: 0 == (nErr = __QAIC_HEADER(adsp_listener_next2)( ctx, nErr, 0, 0, &ctx, &handle, &sc, inBufs, inBufsLen, &inBufsLenReq))
04-04 02:42:53.224 25580-25612/com.via.viadetect E/com.via.viadetect: vendor/qcom/proprietary/adsprpc/src/listener_android.c:335:Error 27: listener thread exited
04-04 02:42:53.224 25580-25612/com.via.viadetect D/com.via.viadetect: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:1153: Error 4b: adsp current process handle failed. domain 0
04-04 02:42:53.225 25580-25612/com.via.viadetect D/com.via.viadetect: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:651: Error 27: remote handle invoke failed. domain 0, handle 0, sc 20200, pra 0x762a5e51e8
04-04 02:42:53.225 25580-25612/com.via.viadetect D/com.via.viadetect: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:651: Error 27: remote handle invoke failed. domain 0, handle ffffffff, sc 1000000, pra 0x0
04-04 02:42:53.225 25580-25612/com.via.viadetect D/com.via.viadetect: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:1153: Error 4b: adsp current process handle failed. domain 0
04-04 02:42:53.226 25580-25612/com.via.viadetect D/com.via.viadetect: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:651: Error 27: remote handle invoke failed. domain 0, handle 0, sc 20200, pra 0x762a5e51e8
04-04 02:42:53.226 25580-25612/com.via.viadetect D/com.via.viadetect: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:651: Error 27: remote handle invoke failed. domain 0, handle ffffffff, sc 1000000, pra 0x0
04-04 02:42:53.226 25580-25612/com.via.viadetect D/com.via.viadetect: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:1153: Error 4b: adsp current process handle failed. domain 0
04-04 02:42:53.227 25580-25612/com.via.viadetect D/com.via.viadetect: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:651: Error 27: remote handle invoke failed. domain 0, handle 0, sc 20200, pra 0x762a5e51e8
04-04 02:42:53.227 25580-25612/com.via.viadetect D/com.via.viadetect: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:651: Error 27: remote handle invoke failed. domain 0, handle ffffffff, sc 1000000, pra 0x0
04-04 02:42:53.227 25580-25612/com.via.viadetect D/com.via.viadetect: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:1153: Error 4b: adsp current process handle failed. domain 0
04-04 02:42:53.228 25580-25612/com.via.viadetect D/com.via.viadetect: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:651: Error 27: remote handle invoke failed. domain 0, handle 0, sc 20200, pra 0x762a5e51e8
04-04 02:42:53.229 25580-25612/com.via.viadetect D/com.via.viadetect: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:651: Error 27: remote handle invoke failed. domain 0, handle ffffffff, sc 1000000, pra 0x0
04-04 02:42:53.230 25580-25580/com.via.viadetect E/VIADetect: snpe is null

It report fastrpc error, I think it may be a driver issue? And it return a null pointer by SNPE builder.

Thanks.

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.