error with ioctl on qcom adreno 730
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- android, cpp
- Domain
- embedded-iot, performance
Research direction
Start by reproducing the reported command, ./gpu_adreno_pmu_test 1000 10 1, using the ./android_build.sh -g adreno build entry point on an Adreno 730 device. Investigate the reported permission failure while reading the event set; done means the test can read the event value and complete without the runtime error.
Written by the indexing model from the issue text.
Description
./gpu_adreno_pmu_test 1000 10 1
opencl lib found but can not be opened: /system/lib64/libOpenCL.so err=(null)
opencl lib found but can not be opened: /system/lib64/libOpenCL_system.so err=(null)
opencl lib found but can not be opened: /system/lib64/egl/libGLES_mali.so err=(null)
opencl lib found but can not be opened: /system/vendor/lib64/egl/libGLES_mali.so err=(null)
opencl lib found but can not be opened: /system/vendor/lib64/libPVROCL.so err=(null)
opencl lib found but can not be opened: /usr/lib64/libGLESv2.so.2.1.0 err=(null)
opencl lib found but can not be opened: /data/data/org.pocl.libs/files/lib64/libpocl.so err=(null)
use opencl: libOpenCL.so
ioctl: read in the current value of an event set failed: Operation not permitted
terminating with uncaught exception of type std::runtime_error: Failed to read the value of an event set.
Aborted
device info: Qualcomm, Adreno (TM) 730
build cmd: ./android_build.sh -g adreno
- Dominant language
- C++
- Stars
- 199
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MegEngine/mperf
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
在树莓派上进行测试Open
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
Similar issues
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
flashinfer-ai/flashinfer#6212 ·
Maintainers usually reply within 1 day
-
bug graphics
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
FlaxEngine/FlaxEngine#4295 · 2 comments ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Algorithmiq/monoprop#390 ·
Maintainers usually reply within 1 day
-
docs
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
leethomason/tinyxml2#1097 ·