Errors on power analysis with vtune

[mnt]

Hello,

When I enable "power" analysis for matrix multiplication example, I see the following errors and warnings:

All things look fine I guess. I mean, the library files are present:

$ uname -r
5.19.0-35-generic
$ ls /lib/modules/5.19.0-35-generic/
build   modules.alias              modules.builtin.bin      modules.devname  modules.symbols.bin
initrd  modules.alias.bin          modules.builtin.modinfo  modules.order    updates
kernel  modules.builtin            modules.dep              modules.softdep  vdso
misc    modules.builtin.alias.bin  modules.dep.bin          modules.symbols

So, the warning is weird. Also, I don't know how to resolve the SoC Watch error, because the user belongs to vtune group as you can see below.  The CPU is i5-6600.

Any idea on how to fix that?

[RemyaP_Intel · Accepted solution]

Hi,

Thank you for posting in Intel communities.

Could you please check if the drivers are loaded correctly. 

Move to <install_dir>/sepdk/src/ and give the command:  ./insmod-sep -q

You should see all the drivers loaded. Make sure soc watch driver is also loaded. 

If any of them are not loaded, unload and reload all of the drivers.

Commands for the same are shown below:

root@245ebe597626:/home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src# ./rmmod-sep

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.



Removing socwatch2_15 driver from the kernel ... done.

The socwatch2_15 driver has been successfully unloaded.



Removing socperf3 driver from the kernel ... done.

The socperf3 driver has been successfully unloaded.



No driver needs PMU arbitration anymore: the PAX service can be safely 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.

root@245ebe597626:/home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src# ./insmod-sep -q

pax driver is not loaded.

socperf3 driver is not loaded.

sep5 driver is not loaded.



socwatch driver is not loaded.



vtsspp driver is not loaded.

root@245ebe597626:/home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src# ./build-driver



C compiler to use: [ /bin/gcc ]

C compiler version: 11.3.0



Make command to use: [ /bin/make ]

Make version: 4.3



Kernel source directory: [ /lib/modules/5.15.0-57-generic/build ]

Kernel version: 5.15.0-57-generic



Cleaning workspaces ...

Done



Building socperf driver ...

Skipping BTF generation for /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socperf/src/socperf3.ko due to unavailability of vmlinux

Done



Building sep driver ...

/home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/sys64.o: warning: objtool: SYS_Get_GDT_Base()+0x3: 'naked' return found in RETHUNK build

/home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/sys64.o: warning: objtool: SYS_IO_Delay()+0x0: 'naked' return found in RETHUNK build

/home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/sys64.o: warning: objtool: SYS_Get_GDT_Base()+0x3: missing int3 after ret

/home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/sys64.o: warning: objtool: SYS_IO_Delay()+0x0: missing int3 after ret

Skipping BTF generation for /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/sep5.ko due to unavailability of vmlinux

Done



Building pax driver ...

Skipping BTF generation for /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/pax/pax.ko due to unavailability of vmlinux

Done



Building vtsspp driver ...

make[1]: Entering directory '/home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/vtsspp'

Skipping BTF generation for /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/vtsspp/vtsspp.ko due to unavailability of vmlinux

make[1]: Leaving directory '/home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/vtsspp'

Done



Building socwatch driver ...

Building drivers for Linux target

-n switch is deprecated. Now it does not have any effect.

/lib/modules/5.15.0-57-generic/build will be used as the kernel build directory

Removing previously built driver and scripts from /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/drivers

mkdir: cannot create directory ‘/home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/drivers’: File exists

-c /bin/gcc -l -k /lib/modules/5.15.0-57-generic/build will be used to build the SoCWatch driver

-c /bin/gcc -l -k /lib/modules/5.15.0-57-generic/build

************ Building socwatch2_15.ko driver ************

Using C compiler = /bin/gcc

Using kernel build dir = /lib/modules/5.15.0-57-generic/build

No module symvers file found

Using common inc dir = /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/../common/include

"/lib/modules/5.15.0-57-generic/build/include/linux/cpufreq.h" exists!

Using file name sw_driver

Make args = KERNEL_SRC_DIR=/lib/modules/5.15.0-57-generic/build CPUFREQ_FIX_BACKPORTED=1 DO_DEBUG_BUILD=0 DO_PROFILING=0 COMMON_INC_DIR=/home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/../common/include MODULE_SYMVERS_FILE= FILE_NAME=sw_driver

make[1]: Entering directory '/home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver'

make -C /lib/modules/5.15.0-57-generic/build M=/home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver clean

make[2]: Entering directory '/usr/src/linux-headers-5.15.0-57-generic'

 CLEAN  /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/Module.symvers

make[2]: Leaving directory '/usr/src/linux-headers-5.15.0-57-generic'

make[1]: Leaving directory '/home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver'

Using C compiler = /bin/gcc

Using kernel build dir = /lib/modules/5.15.0-57-generic/build

No module symvers file found

Using common inc dir = /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/../common/include

"/lib/modules/5.15.0-57-generic/build/include/linux/cpufreq.h" exists!

Using file name sw_driver

Make args = KERNEL_SRC_DIR=/lib/modules/5.15.0-57-generic/build CPUFREQ_FIX_BACKPORTED=1 DO_DEBUG_BUILD=0 DO_PROFILING=0 COMMON_INC_DIR=/home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/../common/include MODULE_SYMVERS_FILE= FILE_NAME=sw_driver

make[1]: Entering directory '/home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver'

make -C /lib/modules/5.15.0-57-generic/build M=/home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver clean

make[2]: Entering directory '/usr/src/linux-headers-5.15.0-57-generic'

make[2]: Leaving directory '/usr/src/linux-headers-5.15.0-57-generic'

************************************************************

KERNEL_SRC_DIR=/lib/modules/5.15.0-57-generic/build

CPUFREQ_FIX_BACKPORTED=1

DO_SOCPERF=0

MODULE_SYMVERS_FILE=

DO_DRIVER_PROFILING=0

INCDIR_1=/home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/../common/include

************************************************************

make -C /lib/modules/5.15.0-57-generic/build M=/home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver modules PWD=/home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver

make[2]: Entering directory '/usr/src/linux-headers-5.15.0-57-generic'

 CC [M] /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/./src/sw_driver.o

 CC [M] /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/./src/sw_hardware_io.o

 CC [M] /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/./src/sw_output_buffer.o

 CC [M] /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/./src/sw_tracepoint_handlers.o

 CC [M] /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/./src/sw_collector.o

 CC [M] /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/./src/sw_mem.o

 CC [M] /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/./src/sw_internal.o

 CC [M] /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/./src/sw_file_ops.o

 CC [M] /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/./src/sw_ops_provider.o

 CC [M] /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/./src/sw_trace_notifier_provider.o

 CC [M] /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/./src/sw_reader.o

 CC [M] /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/./src/sw_telem.o

 CC [M] /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/./src/sw_pmt.o

 CC [M] /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/./src/sw_counter_list.o

 CC [M] /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/./src/sw_pci.o

 LD [M] /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/socwatch2_15.o

 MODPOST /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/Module.symvers

 CC [M] /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/socwatch2_15.mod.o

 LD [M] /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/socwatch2_15.ko

 BTF [M] /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/socwatch2_15.ko

Skipping BTF generation for /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/socwatch2_15.ko due to unavailability of vmlinux

make[2]: Leaving directory '/usr/src/linux-headers-5.15.0-57-generic'

make[1]: Leaving directory '/home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver'

************ Built drivers are copied to /home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/drivers directory ************

Done



Done building the drivers



root@245ebe597626:/home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src# ./insmod-sep

PYTHON is set to python3

Detecting Secure Boot status...

Secure Boot is disabled

---------------------  Loading PAX driver  ---------------------

Detecting Secure Boot status...

Secure Boot is disabled

Checking for PMU arbitration service (PAX) ... not detected.

Attempting to start PAX service ...

Executing: insmod ./pax/pax-x32_64-5.15.0-57-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 ---------------------

Detecting Secure Boot status...

Secure Boot is disabled

Checking for socperf driver ... not detected.

Attempting to start socperf service ...

Executing: insmod ./socperf/src/socperf3-x32_64-5.15.0-57-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.15.0-57-genericsmp.ko sym_lookup_func_addr="ffffffff819984e0"

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.15.0-57-genericsmp.ko gid=1003 mode=0660 ksyms="ffffffff819984e0"

The vtsspp driver has been successfully loaded.



--------------------- Loading SOCWATCH driver ---------------------

Checking for socwatch driver ... not detected.



Executing: insmod ./socwatch/drivers/socwatch2_15-x32_64-5.15.0-57-genericsmp.ko



Setting group ownership of device file to group "vtune" ... done.

Setting file permissions of device file to "660" ... done.



The socwatch driver has been successfully loaded.



NOTE:



The driver is accessible only to users under the group vtune.

Please add the users to the group 'vtune' to use the tool.



To change driver access group, reinstall the driver using -g <desired_group> option.





NOTE:

The driver is accessible only to users under the group vtune.

Please add the users to the group vtune to use the tool.



To change driver access group, reload the driver using -g <desired_group> option.



root@245ebe597626:/home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src# ./insmod-sep -q

pax driver is loaded and owned by group "vtune" with file permissions "660".

socperf3 driver is loaded and owned by group "vtune" with file permissions "660".

sep5 driver is loaded and owned by group "vtune" with file permissions "660".



socwatch driver is loaded and owned by group "vtune" with file permissions "660".



vtsspp driver is loaded and owned by group "vtune" with file permissions "660".

root@245ebe597626:/home/sdp/intel/oneapi/vtune/2023.0.0/sepdk/src#

Regards,

Remya Premdas

[mnt]

Hello,

I don't see the same output. Please see the following:

I think the problem is at this line:

Skipping BTF generation for /opt/intel/oneapi/vtune/2023.0.0/sepdk/src/socwatch/socwatch_driver/socwatch2_15.ko due to unavailability of vmlinux

How can I fix that?

[mnt]

EDITED POST.

[mnt]

Hi again,

Sorry for spamming. In fact I was able to run the commands you mentioned and the driver is now loaded.

# ./rmmod-sep
# ./build-driver
# ./insmod-sep
# ./insmod-sep -q
pax driver is loaded and owned by group "vtune" with file permissions "660".
socperf3 driver is loaded and owned by group "vtune" with file permissions "660".
sep5 driver is loaded and owned by group "vtune" with file permissions "660".

socwatch driver is loaded and owned by group "vtune" with file permissions "660".

vtsspp driver is loaded and owned by group "vtune" with file permissions "660".

So, this means the soc watch driver is loaded.

I then proceeded and opened vtune-gui again, customized HotSpot analysis and selected "power analysis". It still says the same error as I saw in the first post.

As you can see in the error (first post), the problem is permission denied for a file named ./_60598_1804289383

I though that it wants to write in the installed location of vtune, so I changed the ownership of /opt/intel to my username and the problem is now solved. I will close the topic. Thanks.

[RemyaP_Intel]

Hi,

Glad to know that your issue is resolved. Thanks for sharing the solution with us. If you need any additional information, please post a new question as this thread will no longer be monitored by Intel.

Regards,

Remya Premdas