Hi Everybody,
i am using following Ubuntu version;
Distributor ID: Ubuntu
Description: Ubuntu 21.04
Release: 21.04
Codename: hirsute
... and I have updated today 9/12/21 the oneApi as well as Vtune ...
Issue:
vtune: Error: [Instrumentation Engine]: Source/pin/injector_u/loadercommands.cpp: NotifyOnMiniloaderFailure: 689: Injector: caught unexpected signal 11 while running miniloader on file /usr/bin/dash
vtune: Error: Result path `/home/aron/git/SweTools/regtests/worms2/vtune.T490s/vtune.T490s.vtune' does not exist.
Vtune command:
mpirun -n 4 vtune -quiet -collect hotspots -trace-mpi -result-dir vtune swetools
I have attached the log output of the self-checker ...
Thanks in advance ...
Aron
链接已复制
Hi,
Thanks for posting in Intel forums.
In your command you have mentioned swetools and we are not sure if that is executable or result directory name.So we tried in Ubuntu 20.04 with a matrix sample with the below command and were able to run successfully.
"mpirun -n 16 -ppn 4 -l vtune -collect hotspots -k sampling-mode=sw -trace-mpi -result-dir my_result -- ./matrix_mul_dpc"
This command is from the documentation(https://software.intel.com/content/www/us/en/develop/documentation/vtune-help/top/analyze-performance/code-profiling-scenarios/mpi-code-analysis.html).You can refer the above link for mpi analysis.
Try this and let us know.
Regards,
Janani Chandran
Hi Janani,
so yes "swetools" is the exe that I want to profile. Now I have invoked vtune with ...
mpirun -n 4 -ppn 4 -l vtune -collect hotspots -k sampling-mode=sw -trace-mpi -result-dir my_result swetools
and the error is quite similar.
[0] vtune: Error: [Instrumentation Engine]: Source/pin/injector_u/loadercommands.cpp: NotifyOnMiniloaderFailure: 689: Injector: caught unexpected signal 11 while running miniloader on file /usr/bin/dash
[0] vtune: Collection failed.
[0] vtune: Internal Error
I like to add that I have been profiling this code for the last 5 years with parallel studio with no issue.
I like to thank u very much for your prompt reply and hope that we can sort out this issue.
Cheers
Aron
Hi,
Could you try the exact command given below.
mpirun -n 16 -ppn 4 -l vtune -collect hotspots -k sampling-mode=hw -trace-mpi -result-dir my_result -- ./swetools
We could see a minor change in your previous command and in the above command we have mentioned hardware sampling so try the same and let us know.
After trying this if you get any error, then share the appropriate error log and screenshots.
Regards,
Janani Chandran
