- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's been 3 days that I'm trying to make hardware event-based sampling work on intel vtune but at this point I cannot really figure out what my problem can be.
I'm running Ubuntu 18.04 on a macbook pro with Intel i7-4870HQ, 2.5Ghz. It's not a virtual machine, it's booted and I'm using rEFInd for selecting the OS at startup. When I run uname -r I get: 5.3.0-51-generic.
I installed vtune as described in the installation page. I also checked the kernel configuration to match for correct hardware event-based sampling and I also set the kptr_restrict to 0.
To open vtune I run sudo ./vtune-gui from /opt/intel/vtune_profiler_2020.1.0.607630/bin64/.
The binary that gets profiled is compiled with gcc and using the -g and -O3 flags.
However when I try running the vtune profiler with hardware event-based sampling I get the warning displayed in the image at the bottom. Before I also had the warnings like: cannot locate 'vtssoo.ko', and: cannot locate debugging information for the linux kernel. Now they're gone but I'm not sure if they are solved though.
I think these warnings boil down to the drivers. I run ./insmod-sep -q from /opt/intel/vtune_profiler_2020.1.0.607630/sepdk/src and I get this output:
pax driver is loaded and owned by group "vtune" with file permissions "660".
socperf3 driver is not correctly loaded.
sep5 driver is not correctly loaded.
socwatch driver is loaded.
vtsspp driver is loaded and owned by group "vtune" with file permissions "660".
2 drivers are not loaded correctly. Following the instructions to build the drivers didn't help either and I still get this result.
A colleague of mine has the same setup (same OS and version) but he's using a lenovo and not macbook pro. In his case after the installation he could already run hardware event-based sampling without warnings and with all the useful information.
I'm starting to think that it might be something with the macbook pro build. What could the problem be? I would really appreciate any help because I really need this feature. Thanks a lot for you effort and time.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Nihat,
We are forwarding this case for SME to check. They will get back to you on this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Chithra,
Thanks for the answer. I will be waiting.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Nihat,
Could you fully unload the driver (./rmmod-sep -s) and load it again? (./insmod-sep)
I need a full output of the load script.
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello! Please run the command dmesg >& log and attach the log. If there are any error messages, I will be able to file a JIRA and the development team will take a look. Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Nihat,
Is your issue resolved? Do you have any updates?
Regards,
Janani Chandran
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
We assume that your issue is resolved.If you need any additional information, please submit a new question as this thread will no longer be monitored.
Regards,
Janani Chandran
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm having the same issue though slightly different hardware and software as the OP. I also have a 2015 MBP but my processor is Intel i7-4890HQ, and I'm on Ubuntu 20.04. I've compiled my application with Intel Fortran 2021.1 with `-g -O2` flags (CMake's RelWithDebInfo build type).
I have installed VTune 2022 both with apt and then again with the VTune standalone shell script installer through the website.
./insmod-sep -q
pax driver is loaded and owned by group "vtune" with file permissions "660".
socperf3 driver is not correctly loaded.
sep5 driver is not correctly loaded.
socwatch driver is not loaded.
vtsspp driver is loaded and owned by group "vtune" with file permissions "660".
@Vladimir_T_Intel here's the result of your suggestion above to remove the drivers and reinstall
>>ubuntu@/opt/intel/oneapi/vtune/latest/sepdk/src $ sudo ./rmmod-sep -s
Removing sep5 driver from the kernel ... done.
The sep5 driver has been successfully unloaded.
Removing vtsspp driver from the kernel ... done.
The vtsspp driver has been successfully unloaded.
Warning: no socwatch driver was found loaded in the kernel.
Removing socperf3 driver from the kernel ... done.
The socperf3 driver has been successfully unloaded.
Attempting to stop PAX service ...
Removing pax driver from the kernel ... done.
The pax driver has been successfully unloaded.
PAX service has been stopped.
>>ubuntu@/opt/intel/oneapi/vtune/latest/sepdk/src $ sudo ./insmod-sep
PYTHON is set to python3
--------------------- Loading PAX driver ---------------------
Checking for PMU arbitration service (PAX) ... not detected.
Attempting to start PAX service ...
Executing: insmod ./pax/pax-x32_64-5.13.0-44-genericsmp.ko
Setting group ownership of devices to group "vtune" ... done.
Setting file permissions on devices to "660" ... done.
The pax driver has been successfully loaded.
--------------------- Loading SOCPERF driver ---------------------
Checking for socperf driver ... not detected.
Attempting to start socperf service ...
Executing: insmod ./socperf/src/socperf3-x32_64-5.13.0-44-genericsmp.ko
Setting group ownership of devices to group "vtune" ... done.
Setting file permissions on devices to "660" ... done.
The socperf3 driver has been successfully loaded.
--------------------- Loading SEP driver ---------------------
Executing: insmod ./sep5-x32_64-5.13.0-44-genericsmp.ko sym_lookup_func_addr="ffffffff965648f0"
Setting group ownership of devices to group "vtune" ... done.
Setting file permissions on devices to "660" ... done.
The sep5 driver has been successfully loaded.
--------------------- Loading VTSSPP driver ---------------------
Checking for vtsspp driver ... not detected.
Executing: insmod ./vtsspp/vtsspp-x32_64-5.13.0-44-genericsmp.ko gid=1001 mode=0660 ksyms="ffffffff965648f0"
The vtsspp driver has been successfully loaded.
--------------------- Loading SOCWATCH driver ---------------------
Checking for socwatch driver ... not detected.
./socwatch/insmod-socwatch: 312: [: ./socwatch/drivers/socwatch2_15-x32_64-5.13.0-30-genericsmp.ko: unexpected operator
Executing: insmod ./socwatch/drivers/socwatch2_15-x32_64-5.13.0-30-genericsmp.ko
socwatch2_15-x32_64-5.13.0-39-genericsmp.ko
socwatch2_15-x32_64-5.13.0-41-genericsmp.ko
socwatch2_15-x32_64-5.13.0-44-genericsmp.ko
insmod: ERROR: could not insert module ./socwatch/drivers/socwatch2_15-x32_64-5.13.0-30-genericsmp.ko: Invalid module format
Error: socwatch driver failed to load!
You may need to build socwatch driver for your kernel.
Please see the socwatch driver README for instructions.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page