nvdla / sw

NVDLA SW
Other
489 stars 193 forks source link

NvDlaSubmit: Error IOCTL failed (Cannot allocate memory) #171

Open liufengwuhen opened 5 years ago

liufengwuhen commented 5 years ago

I am running nvdla_runtime on nv_small on a fpga, but it has some error? Can some one tell me why? root@xilinx-zcu106-2018_3:~# ./nvdla_runtime --loadable PDP_L0_0_small_fbuf creating new runtime context... Emulator starting submitting tasks... NvDlaSubmit: Error IOCTL failed (Cannot allocate memory) (Info) Error 0x0003000f: (propagating from ../umd/core/runtime/Runtime.cpp, function submitInternal(), line 666) (Info) Error 0x00000004: runtime->submit() failed (in ../umd/tests/runtime/RuntimeTest.cpp, function runTest(), line 387) (Info) Error 0x00000004: (propagating from ../umd/tests/runtime/RuntimeTest.cpp, function run(), line 440) Shutdown signal received, exiting (Info) Error 0x00000004: (propagating from ../umd/tests/runtime/main.cpp, function launchTest(), line 87)

akioolin commented 5 years ago

is the opendla.ko been inserted into kernel before execute nvdla_runtime?

liufengwuhen commented 5 years ago

I have inserted the kernel module opendla.ko, the mistake has been solved. The new question is that the processor halt at "Exit: dla_initiate_processors status=0 "

akioolin commented 5 years ago

what test do you did?

btw, please check the content of /proc/interrupts. if nvdla issued any interrupt, there will be a record in /proc/interrupts

liufengwuhen commented 5 years ago

My command is "./nvdla_runtime --loadable CONV_D_L0_0_small_fbuf". I use ChipScope to collect the interrupt, but it has nothing. The record in /proc/interrupts also has nothing.

akioolin commented 5 years ago

I think the problem is caused by interrupt no send out to cpu. the nvdla interrupt had to be checked at first

liufengwuhen commented 5 years ago

Which bit should be checked?

akioolin commented 5 years ago

please check engine_isr.c

liufengwuhen commented 5 years ago

I use ChipScope to collect the interrupt, but it has nothing. The record in /proc/interrupts also has nothing. So the file engine_isr.c can not display anything.

akioolin commented 5 years ago

the root cause could be focus on nvdla's interrupt issue related design

liufengwuhen commented 5 years ago

Ok, We will check the related design and registers.

gitosu67 commented 5 years ago

Hi, any update on this? I am facing a similar issue.

NicolasWu97 commented 3 years ago

I have inserted the kernel module opendla.ko, the mistake has been solved. The new question is that the processor halt at "Exit: dla_initiate_processors status=0 "

How do you solve the problem?(The first mentioned),just by insert opendla.ko? Hope to get your help,Thank U

sunny-yellow commented 3 years ago

Which bit should be checked?

Hello, did you solve the problem? I met the same issue.

Yuxin-Yu commented 1 year ago

Have anybody solve this problem ?