Soroosh129 / NeuOS

Source code for the paper: "A Latency-Predictable Multi-Dimensional Optimization Framework forDNN-driven Autonomous Systems"
Other
19 stars 5 forks source link

Segmentation fault (core dumped) caused by classify.bin #1

Closed liusiping10 closed 4 years ago

liusiping10 commented 4 years ago

Hi, thank you for the excellent work!

I encounter a segmentation fault problem, when I run the classify.bin. If I set the iteration from 15 to 1, It runs correct. How to solve this problem?

++++ shmemus/sched_energy: 52 0 Concorrency= 0 Latency(us)/Energy(mJ): 0 0 Using lowrank instead. Layer names:conv1_v and conv1_h Latency(us)/Energy(mJ): 82483 332.063 Latency(us)/Energy(mJ): 26 0 Latency(us)/Energy(mJ): 179 0.719461 Latency(us)/Energy(mJ): 94 0.237628 Using lowrank instead. Layer names:conv2_v and conv2_h Latency(us)/Energy(mJ): 5808 20.0019 Latency(us)/Energy(mJ): 22 0 Latency(us)/Energy(mJ): 143 0.527584 Latency(us)/Energy(mJ): 94 0.260632 Using lowrank instead. Layer names:conv3_v and conv3_h Latency(us)/Energy(mJ): 1285 5.00857 Latency(us)/Energy(mJ): 21 0 Using lowrank instead. Layer names:conv4_v and conv4_h Latency(us)/Energy(mJ): 1807 7.31882 Latency(us)/Energy(mJ): 20 0 Using lowrank instead. Layer names:conv5_v and conv5_h Latency(us)/Energy(mJ): 4245 17.9505 Latency(us)/Energy(mJ): 21 0.313044 Latency(us)/Energy(mJ): 84 0.326688 Latency(us)/Energy(mJ): 3703 17.2541 Latency(us)/Energy(mJ): 23 0 Latency(us)/Energy(mJ): 0 0 Latency(us)/Energy(mJ): 4901 27.0591 Latency(us)/Energy(mJ): 39 0 Latency(us)/Energy(mJ): 0 0 Latency(us)/Energy(mJ): 2076 13.6563 Latency(us)/Energy(mJ): 83 0.576356 _peroid: 25 Progress Cohort={ 20.5,0,0,0,0,0,0,0,0,0,Accuracy Cohort={ 20.5,0,0,0,0,0,0,0,0,0,} } ++++ sched_us/sched_energy: 52 11.5271 ++++ xup_exec_us/xup_energy_mj: 107157 443.274 ++++ shmemus/sched_energy: 73 0 Concorrency= 1101266944 Segmentation fault (core dumped)

Soroosh129 commented 4 years ago

What platform are you using? Could you please give me the following: AGX or TX2 Jetpack version

liusiping10 commented 4 years ago

Thank you for this quick reply. I am using Jetson TX2 with Jetpack 4.4 DP (Ubuntu 18.04, CUDA 10.2, cuDNN 8.0). Is this highly related to the Jetpack version?

Soroosh129 commented 4 years ago

It might. I am currently investigating this issue. I will keep you posted. Thank you for reporting this.

liusiping10 commented 4 years ago

Thank you again. I have solved this problem by 'touch' file /home/nvidia/approxfile, /home/nvidia/datafile and /home/nvidia/concurrfile after debugging and reading the source code.

Soroosh129 commented 4 years ago

Ah yes thank you. I forgot to add that to the README. I've updated the README file.