Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
liufengwuhen opened this issue Oct 7, 2019 · 14 comments
Open

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

liufengwuhen opened this issue Oct 7, 2019 · 14 comments

Comments

@liufengwuhen
Copy link

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
Copy link

akioolin commented Oct 7, 2019

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

@liufengwuhen
Copy link
Author

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
Copy link

akioolin commented Oct 8, 2019

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
Copy link
Author

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
Copy link

akioolin commented Oct 8, 2019

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

@liufengwuhen
Copy link
Author

Which bit should be checked?

@akioolin
Copy link

akioolin commented Oct 9, 2019

please check engine_isr.c

@liufengwuhen
Copy link
Author

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
Copy link

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

@liufengwuhen
Copy link
Author

liufengwuhen commented Oct 14, 2019

Ok, We will check the related design and registers.

@gitosu67
Copy link

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

@NicolasWu97
Copy link

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
Copy link

Which bit should be checked?

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

@Yuxin-Yu
Copy link

Have anybody solve this problem ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants