Forums - Failed to perform benchmark for DSP_timing

6 posts / 0 new
Last post
Failed to perform benchmark for DSP_timing
chenkun
Join Date: 31 Oct 17
Posts: 3
Posted: Wed, 2017-11-15 19:25

Hi, it was failed to perform benchmark for DSP_timing when I tested my network written by Tensorflow. The log shows below:

****************************************************************************

2017-11-16 09:55:19,098 - INFO - snpe_bench: DSP_timing
2017-11-16 09:55:19,099 - INFO - snpe_bench: Run 1
2017-11-16 09:55:24,907 - ERROR - _execute_adbcmd_raw: adb -H localhost -s 3efa0095 shell "sh /data/local/tmp/snpebm/artifacts/arm-android-gcc4.9/bin/snpe-bench_cmds.sh && echo ADB_SHELL_CMD_SUCCESS" failed with stderr of: WARNING: linker: Warning: unable to normalize ""
WARNING: linker: Warning: unable to normalize ""
-------------------------------------------------------------------------------
Model String: N/A
Processing DNN Input: cropped/notice_sign.raw
error_code=910; error_message=Undefined error. Failed to execute network.  Error code: -6.; error_component=SNPE; line_no=250; thread_id=-162597580
 
2017-11-16 09:55:24,907 - WARNING - _execute_adbcmd_raw: adb shell command failed to execute:
WARNING: linker: Warning: unable to normalize ""
WARNING: linker: Warning: unable to normalize ""
-------------------------------------------------------------------------------
Model String: N/A
Processing DNN Input: cropped/notice_sign.raw
error_code=910; error_message=Undefined error. Failed to execute network.  Error code: -6.; error_component=SNPE; line_no=250; thread_id=-162597580
 
2017-11-16 09:55:24,908 - WARNING - snpe_bench: Failed to perform benchmark for DSP_timing.
****************************************************************************
 
It was right with the CPU_timing and GPU_timing.
It also right using the tools snpe-net-run with --use_dsp.
 
Would you help us?
Thank you!
Best wishes
chenkun
 
  • Up0
  • Down0
jesliger
Join Date: 6 Aug 13
Posts: 75
Posted: Wed, 2017-11-15 19:53

Thanks for trying out SNPE.  If it runs fine with snpe-net-run that is a good sign that your network is working with dsp.

What type of device are you using to test?  Does this issue happen even after performing a fresh reboot of the device?  Also, once you get the device to fail this benchmark, does snpe-net-run with --use_dsp still work ok?

 

  • Up0
  • Down0
chenkun
Join Date: 31 Oct 17
Posts: 3
Posted: Wed, 2017-11-15 20:38

The device is Oneplus5.

Yes, I reboot the phone but it also failed.

Yes, the snpe-net-run with --use_dsp works rightly on this device, but get wrong to benchmark for DSP_timing.

We might focus on the error "unable to normalize".

Does someone else meet this before?

  • Up0
  • Down0
jesliger
Join Date: 6 Aug 13
Posts: 75
Posted: Wed, 2017-11-15 20:56

Unable to normalize is expected.  I can't remember why, but it's not the cause of this problem.  We are able to benchmark a OnePlus 5 using dsp.  You'll notice you'll see "unable to normalize" when manually invoking snpe-net-run.

The benchmark script simply invokes snpe-net-run. Can you try adb shell and go into "/data/local/tmp/snpebm/artifacts/arm-android-gcc4.9/bin" and run the script "snpe-bench_cmds.sh" there?  (This is what the benchmark does.)

Also, can you provide logcat for the failure case please?

 

  • Up0
  • Down0
chenkun
Join Date: 31 Oct 17
Posts: 3
Posted: Wed, 2017-11-15 21:32

ok,run the script "snpe-bench_cmds.sh", it shows:

:/data/local/tmp/snpebm/artifacts/arm-android-gcc4.9/bin # ./sn
snpe-bench_cmds.sh  snpe-net-run
/snpe-bench_cmds.sh                                                           <
WARNING: linker: Warning: unable to normalize ""
WARNING: linker: Warning: unable to normalize ""
-------------------------------------------------------------------------------
Model String: N/A
Processing DNN Input: cropped/notice_sign.raw
error_code=910; error_message=Undefined error. Failed to execute network.  Error code: -6.; error_component=SNPE; line_no=250; thread_id=-193071820
 
 
the logcat here:
 
03-16 18:42:02.681   746 15519 E tftp_server: pid=746 tid=15519 tftp-server : ERR :[tftp_os_la.c, 65] open failed: [2] [No such file or directory]
03-16 18:42:02.682   746 15519 E tftp_server: pid=746 tid=15519 tftp-server : ERR :[tftp_server.c, 1519] open failed : [-2] [Unknown error -2]
03-16 18:42:02.683   746 15519 E tftp_server: pid=746 tid=15519 tftp-server : ERR :[tftp_protocol.c, 1146] sending error-pkt. Code = 1, Msg = Err=2 String=No such file or directory
03-16 18:42:06.449 15544 15544 E linker  : normalize_path - invalid input: "", the input path should be absolute
03-16 18:42:06.450 15544 15544 W linker  : Warning: unable to normalize ""
03-16 18:42:06.500 15545 15545 E linker  : normalize_path - invalid input: "", the input path should be absolute
03-16 18:42:06.500 15545 15545 W linker  : Warning: unable to normalize ""
03-16 18:42:10.894 15583 15583 E linker  : normalize_path - invalid input: "", the input path should be absolute
03-16 18:42:10.894 15583 15583 W linker  : Warning: unable to normalize ""
03-16 18:42:10.933 15584 15584 E linker  : normalize_path - invalid input: "", the input path should be absolute
03-16 18:42:10.933 15584 15584 W linker  : Warning: unable to normalize ""
03-16 18:42:15.463 15620 15620 E linker  : normalize_path - invalid input: "", the input path should be absolute
03-16 18:42:15.463 15620 15620 W linker  : Warning: unable to normalize ""
03-16 18:42:15.508 15622 15622 E linker  : normalize_path - invalid input: "", the input path should be absolute
03-16 18:42:15.509 15622 15622 W linker  : Warning: unable to normalize ""
03-16 18:42:20.079 15660 15660 E linker  : normalize_path - invalid input: "", the input path should be absolute
03-16 18:42:20.079 15660 15660 W linker  : Warning: unable to normalize ""
03-16 18:42:20.131 15661 15661 E linker  : normalize_path - invalid input: "", the input path should be absolute
03-16 18:42:20.131 15661 15661 W linker  : Warning: unable to normalize ""
03-16 18:42:23.286  2225  2225 I LoadedApk: com.android.keyguard.KeyguardUpdateMonitor$3@12f3b9b onReceive android.intent.action.BATTERY_CHANGED start
03-16 18:42:23.287  2225  2225 I LoadedApk: com.android.keyguard.KeyguardUpdateMonitor$3@12f3b9b onReceive android.intent.action.BATTERY_CHANGED in 0ms
03-16 18:42:23.287  2225  2225 I LoadedApk: com.android.systemui.power.PowerUI$Receiver@16270ca onReceive android.intent.action.BATTERY_CHANGED start
03-16 18:42:23.287  2384  2384 I LoadedApk: com.android.internal.telephony.RIL$2@2ef8313 onReceive android.intent.action.BATTERY_CHANGED start
03-16 18:42:23.287  2384  2384 I LoadedApk: com.android.internal.telephony.RIL$2@2ef8313 onReceive android.intent.action.BATTERY_CHANGED in 0ms
03-16 18:42:23.287  2384  2384 I LoadedApk: com.android.internal.telephony.RIL$2@d9cc950 onReceive android.intent.action.BATTERY_CHANGED start
03-16 18:42:23.287  2384  2384 I LoadedApk: com.android.internal.telephony.RIL$2@d9cc950 onReceive android.intent.action.BATTERY_CHANGED in 1ms
03-16 18:42:23.287  2384  2384 I LoadedApk: com.qualcomm.ims.vt.LowBatteryHandler$1@1155c8a onReceive android.intent.action.BATTERY_CHANGED start
03-16 18:42:23.288  3229  3229 I LoadedApk: android.mtp.MtpDatabase$1@a589ad5 onReceive android.intent.action.BATTERY_CHANGED start
03-16 18:42:23.288  3315  3315 I LoadedApk: com.oneplus.opbackup.download.processor.BatteryWatcher$InnerReceiver@a27cb38 onReceive android.intent.action.BATTERY_CHANGED start
03-16 18:42:23.288  3315  3315 D AbstractProcessor: onBatteryChange Percent:100 State:5 
03-16 18:42:23.288  3315  3315 I LoadedApk: com.oneplus.opbackup.download.processor.BatteryWatcher$InnerReceiver@a27cb38 onReceive android.intent.action.BATTERY_CHANGED in 1ms
03-16 18:42:23.288  3229  3229 I LoadedApk: android.mtp.MtpDatabase$1@a589ad5 onReceive android.intent.action.BATTERY_CHANGED in 1ms
03-16 18:42:23.289  2225  2225 I LoadedApk: com.android.systemui.power.PowerUI$Receiver@16270ca onReceive android.intent.action.BATTERY_CHANGED in 2ms
03-16 18:42:23.289  2225  2225 I LoadedApk: com.android.systemui.statusbar.policy.BatteryControllerImpl@de10bca onReceive android.intent.action.BATTERY_CHANGED start
03-16 18:42:23.289  2225  2225 I BatteryController:  fireBatteryLevelChanged mLevel:100 PluggedIn:true Charging:true Fastcharge:false show:false style:0
03-16 18:42:23.290  3266  3266 I LoadedApk: com.oneplus.security.WidgetViewService$BatteryReceiver@592418b onReceive android.intent.action.BATTERY_CHANGED start
03-16 18:42:23.290  3266  3266 I LoadedApk: com.oneplus.security.WidgetViewService$BatteryReceiver@592418b onReceive android.intent.action.BATTERY_CHANGED in 1ms
03-16 18:42:23.291  2225  2225 I LoadedApk: com.android.systemui.statusbar.policy.BatteryControllerImpl@de10bca onReceive android.intent.action.BATTERY_CHANGED in 2ms
03-16 18:42:23.292  2225  2574 D Tile.BatteryTile: update, false
03-16 18:42:23.293  2384  2384 E QtiImsExtUtils: getConfigForPhoneId subId is invalid
03-16 18:42:23.293  2225  2574 D Tile.BatteryTile: Time cost in handleMessage: name=handleRefreshState, time=2 ms
03-16 18:42:23.293  2384  2384 E QtiImsExtUtils: isCarrierConfigEnabled bundle is null
03-16 18:42:23.293  2384  2384 I LoadedApk: com.qualcomm.ims.vt.LowBatteryHandler$1@1155c8a onReceive android.intent.action.BATTERY_CHANGED in 5ms
03-16 18:42:23.293  2225  2225 D BatteryMeterDrawable: onPowerSaveChanged , false
03-16 18:42:23.294  2225  2225 D BatteryMeterDrawable: onPowerSaveChanged , false
03-16 18:42:24.666 15696 15696 E linker  : normalize_path - invalid input: "", the input path should be absolute
03-16 18:42:24.666 15696 15696 W linker  : Warning: unable to normalize ""
03-16 18:42:24.700 15697 15697 E linker  : normalize_path - invalid input: "", the input path should be absolute
03-16 18:42:24.701 15697 15697 W linker  : Warning: unable to normalize ""
 
 
It tells me that "the input path should be absolute", but I set the input path as the example of Inception_v3.
The input file list in the "target_raw_list.txt" as beblow:
cropped/notice_sign.raw
cropped/handicap_sign.raw
cropped/plastic_cup.raw
cropped/trash_bin.raw
cropped/chairs.raw
 
By the way, the example of Inception_v3 can work right.
So how can I edit the input path?
 
  • Up0
  • Down0
jesliger
Join Date: 6 Aug 13
Posts: 75
Posted: Mon, 2017-11-20 04:42

You can edit target_raw_list.txt and put absolute paths in there (instead of relative.)

Once you do that, try running each line of the shell script independently.   One of the key factors for DSP runtime is the proper setting of ADSP_LIBRARY_PATH environment variable.  To ensure that it is being set correctly, perhaps compare the value of that variable when running manually vs running with the benchmark shell script.

  • 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.