nvdla / sw

NVDLA SW
Other
489 stars 193 forks source link

error:libnvdla<1> fillTaskAddressList ali=3 -> mem_id=3 has a null memory handle. #238

Open Yuxin-Yu opened 1 year ago

Yuxin-Yu commented 1 year ago

Hello, I use RISC-V as the driver CPU for NVDLA,and in order to adapt to the SOC corresponding to Large NVDLA, I used the compiler to generate the Loadable file corresponding to Lenet mini. Before generating the loadable file, I opened the SRAM enable function as follows: // setUseCVSRAMAllocate(true); Then I executed the following command to generate the corresponding loadable file in Large mode: ./nvdla-sw/umd/out/apps/compiler/nvdla_compiler/nvdla_compiler --profile performance --configtarget nv_large --cprecision int8 --prototxt /home/yyx/riscv/document/nvdla_loadables/lenet-minist-caffe/lenet-minist.prototxt --caffemodel /home/yyx/riscv/document/nvdla_loadables/lenet-minist-caffe/lenet-minist.caffemodel --informat nchw --calibtable /home/yyx/riscv/document/nvdla_loadables/lenet-minist-caffe/lenet-minist.int8.json However, when executing the inference, the following error occurred:

creating new runtime context...
Read and load loabable file time = 40900037.000000 us  
 dlaimg height: 28 x 28 x 1: LS: 896 SS: 0 Size: 25088 
Image load time = 32252.000000 us  
submitting tasks...   
 libnvdla<1> fillTaskAddressList ali=3 -> mem_id=3 has a null memory handle. 
[ 3174.072539] nvdla_runtime_l[151]: unhandled signal 11 code 0x1 at 0x0000000000000000 in libnvdla_runtime.so[3febadd000+2f000]                                     
[ 3174.084092] CPU: 0 PID: 151 Comm: nvdla_runtime_l Tainted: G           O      5.7.0-rc3-58540-g4c3d31704413-dirty #3                                            
[ 3174.094839] epc: 0000003febaf46a0 ra : 0000003febafa064 sp : 0000003fffed4730
[ 3174.101841]  gp : 000000000003a800 tp : 0000003feb797380 t0 : 0000003febadf9c8 
[ 3174.109123]  t1 : 0000000000000004 t2 : 0000003febb0e1a0 s0 : 0000003fffeec760 
[ 3174.116435]  s1 : 0000000000000000 a0 : 0000003fffeec7e0 a1 : 0000000000000000 
[ 3174.123745]  a2 : 0000003fffeec7a0 a3 : 0000000000000001 a4 : 0000003fffed4730
[ 3174.131053]  a5 : 0000003fffed4740 a6 : 0000003fffed4770 a7 : 000000000004feb0
[ 3174.138367]  s2 : 0000003fffeec790 s3 : 0000000000065160 s4 : fffffffffffe8000
[ 3174.145664]  s5 : 0000003fffeec7a0 s6 : 000000000004feb0 s7 : 0000000000000000 
 [ 3174.152980]  s8 : 0000000000000000 s9 : 0000003febb0da40 s10: 2e8ba2e8ba2e8ba3
[ 3174.160288]  s11: 0000000000000000 t3 : 0000000000018000 t4 : 000000000000000b 
[ 3174.167570]  t5 : 0000000000018010 t6 : 0000000000000000
[ 3174.172995] status: 8000000200006020 badaddr: 0000000000000000 cause: 000000000000000d 
Segmentation fault 

What could be the reason? Thanks

long771 commented 1 year ago

这是来自QQ邮箱的自动回复邮件。 您好,我是龙欣荣,很高兴收到您的邮件,我将尽快处理。