VTune installation failure on Fedora 35

[Andrew_B_Intel]

When upgrading a Fedora 35 machine, the VTune RPM fails to install:

 Running scriptlet: intel-oneapi-vtune-2022.3.0-195.x86_64                                                                                         140/364

C compiler version: 11.3.1
Make version: 4.3
Kernel version: 5.17.6-200

Cleaning workspaces ...
Done

Building socperf driver ...
Skipping BTF generation for /opt/intel/oneapi/vtune/2022.3.0/sepdk/src/socperf/src/socperf3.ko due to unavailability of vmlinux
Done

Building sep driver ...
/opt/intel/oneapi/vtune/2022.3.0/sepdk/src/linuxos.c: In function ‘LINUXOS_Install_Hooks’:
/opt/intel/oneapi/vtune/2022.3.0/sepdk/src/linuxos.c:1301:11: error: implicit declaration of function ‘profile_event_register’ [-Werror=implicit-function-declaration]
 1301 |     err = profile_event_register(MY_UNMAP, &linuxos_exec_unmap_nb);
      |           ^~~~~~~~~~~~~~~~~~~~~~
/opt/intel/oneapi/vtune/2022.3.0/sepdk/src/linuxos.c:95:18: error: ‘PROFILE_MUNMAP’ undeclared (first use in this function)
   95 | #define MY_UNMAP PROFILE_MUNMAP
      |                  ^~~~~~~~~~~~~~
/opt/intel/oneapi/vtune/2022.3.0/sepdk/src/linuxos.c:1301:34: note: in expansion of macro ‘MY_UNMAP’
 1301 |     err = profile_event_register(MY_UNMAP, &linuxos_exec_unmap_nb);
      |                                  ^~~~~~~~
/opt/intel/oneapi/vtune/2022.3.0/sepdk/src/linuxos.c:95:18: note: each undeclared identifier is reported only once for each function it appears in
   95 | #define MY_UNMAP PROFILE_MUNMAP
      |                  ^~~~~~~~~~~~~~
/opt/intel/oneapi/vtune/2022.3.0/sepdk/src/linuxos.c:1301:34: note: in expansion of macro ‘MY_UNMAP’
 1301 |     err = profile_event_register(MY_UNMAP, &linuxos_exec_unmap_nb);
      |                                  ^~~~~~~~
/opt/intel/oneapi/vtune/2022.3.0/sepdk/src/linuxos.c:94:18: error: ‘PROFILE_TASK_EXIT’ undeclared (first use in this function)
   94 | #define MY_TASK  PROFILE_TASK_EXIT
      |                  ^~~~~~~~~~~~~~~~~
/opt/intel/oneapi/vtune/2022.3.0/sepdk/src/linuxos.c:1302:34: note: in expansion of macro ‘MY_TASK’
 1302 |     err2= profile_event_register(MY_TASK,  &linuxos_exit_task_nb);
      |                                  ^~~~~~~
/opt/intel/oneapi/vtune/2022.3.0/sepdk/src/linuxos.c: In function ‘LINUXOS_Uninstall_Hooks’:
/opt/intel/oneapi/vtune/2022.3.0/sepdk/src/linuxos.c:1402:5: error: implicit declaration of function ‘profile_event_unregister’ [-Werror=implicit-function-declaration]
 1402 |     profile_event_unregister(MY_UNMAP, &linuxos_exec_unmap_nb);
      |     ^~~~~~~~~~~~~~~~~~~~~~~~
/opt/intel/oneapi/vtune/2022.3.0/sepdk/src/linuxos.c:95:18: error: ‘PROFILE_MUNMAP’ undeclared (first use in this function)
   95 | #define MY_UNMAP PROFILE_MUNMAP
      |                  ^~~~~~~~~~~~~~
/opt/intel/oneapi/vtune/2022.3.0/sepdk/src/linuxos.c:1402:30: note: in expansion of macro ‘MY_UNMAP’
 1402 |     profile_event_unregister(MY_UNMAP, &linuxos_exec_unmap_nb);
      |                              ^~~~~~~~
/opt/intel/oneapi/vtune/2022.3.0/sepdk/src/linuxos.c:94:18: error: ‘PROFILE_TASK_EXIT’ undeclared (first use in this function)
   94 | #define MY_TASK  PROFILE_TASK_EXIT
      |                  ^~~~~~~~~~~~~~~~~
/opt/intel/oneapi/vtune/2022.3.0/sepdk/src/linuxos.c:1403:30: note: in expansion of macro ‘MY_TASK’
 1403 |     profile_event_unregister(MY_TASK,  &linuxos_exit_task_nb);
      |                              ^~~~~~~
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:288: /opt/intel/oneapi/vtune/2022.3.0/sepdk/src/linuxos.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [Makefile:1841: /opt/intel/oneapi/vtune/2022.3.0/sepdk/src] Error 2
make: *** [Makefile:215: default] Error 2

Failed to build the drivers


Warning:  the following driver(s) were not found loaded in the kernel:  sep5.

Warning:  no vtsspp driver was found loaded in the kernel.

Warning:  no socwatch driver was found loaded in the kernel.


Warning:  the following driver(s) were not found loaded in the kernel:  socperf3.


The PAX service is not loaded anymore.
PYTHON is set to python

ERROR: sep5 driver "sep5-x32_64-5.17.6-200.fc35.x86_64smp.ko"
was not found in directory "." !

This means you may need to build sep5 driver from the provided
driver sources. Please see the driver README for instructions.

Note: Ensure that the driver is built for kernel version 5.17.6-200.fc35.x86_64

Configuring sep5 boot script with the following options:
    driver files = /opt/intel/oneapi/vtune/2022.3.0/sepdk/src/.
Creating systemd load script /usr/local/sbin/sep5-load.sh ...
done.
Creating systemd boot config file /usr/lib/systemd/system/sep5.service ...
done.
Configuring autoload of sep5.service service ...
Job for sep5.service failed because the control process exited with error code.
See "systemctl status sep5.service" and "journalctl -xeu sep5.service" for details.
WARNING: systemctl start returned error 1 ...
done.

This error was observed on the following Linux kernel version: 5.17.12-200.fc35.x86_64.

See the following related issues for context: building sepdk driver, corrupted data file.

[JananiC_Intel]

Hi,

Thanks for posting in Intel Forum.

We are working on this. We will get back to you soon.

Regards,

Janani Chandran

[Jeffrey_R_Intel1]

Linux kernel 5.17 removes callback mechanism for process exit notification and module unmap notification which the SEP driver uses to track dynamic process creation / termination and dynamic module load / unload, respectively, during collection.

The workaround for this issue will be available in Intel VTune Profiler 2022.4.

[JananiC_Intel]

Hi,

Is your issue resolved? Do you have any updates?

Regards,

Janani Chandran

[Aren]

Hello, 

I get the same error while trying to build drivers are there solutions for this?

best 

Aren

[JananiC_Intel]

Hi,

We assume that your issue is resolved. If you need any additional information, please post a new question as this thread will no longer be monitored by Intel.

@Aren, Workaround for this issue will be available in vtune 2022.4.We will let you know once it is available.

Regards,

Janani Chandran

[Andrew_B_Intel]

> We assume that your issue is resolved

Well, the issue is not resolved yet since I have to wait for 2022.4 but I will try again once that is released.