[VTUNE] sep5.service failed: 236/SMACK_PROCESS_LABEL

[Bram_S_]

After installing intel-oneapi-vtune (2023.1.0-44286) on Ubuntu 23.04: 

$ sudo systemctl status sep5
× sep5.service - systemd script to load sep5 driver at boot time
     Loaded: loaded (/lib/systemd/system/sep5.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Thu 2023-04-27 12:50:19 PDT; 6min ago
    Process: 261391 ExecStart=/usr/local/sbin/sep5-load.sh start (code=exited, status=236/SMACK_PROCESS_LABEL)
   Main PID: 261391 (code=exited, status=236/SMACK_PROCESS_LABEL)
        CPU: 62ms

Apr 27 12:50:19 deca systemd[1]: Starting sep5.service - systemd script to load sep5 driver at boot time...
Apr 27 12:50:19 deca sep5-load.sh[261391]: Loading the sep5 driver:
Apr 27 12:50:19 deca groupmod[261445]: group changed in /etc/group (group vtune/1002)
Apr 27 12:50:19 deca sep5-load.sh[261392]: The sep5 driver is already loaded!  Use ./rmmod-sep to unload it.
Apr 27 12:50:19 deca systemd[1]: sep5.service: Main process exited, code=exited, status=236/SMACK_PROCESS_LABEL
Apr 27 12:50:19 deca systemd[1]: sep5.service: Failed with result 'exit-code'.
Apr 27 12:50:19 deca systemd[1]: Failed to start sep5.service - systemd script to load sep5 driver at boot time.
$

OS: Ubuntu 23.04

CPU: i12600k

[IonutNechita]

Hi @yuzhang3_intel ,

I installed steps, 2.1.2 and 2.1.3 and i notice similar output:

 /opt/intel/oneapi/vtune/latest/bin64/vtune-self-checker.sh
Intel(R) VTune(TM) Profiler Self Check Utility
Copyright (C) 2009 Intel Corporation. All rights reserved.
Build Number: 627177

HW event-based analysis (counting mode) (Intel driver)
Example of analysis types: Performance Snapshot
    Collection: Ok
    Finalization: Ok...
    Report: Ok

Instrumentation based analysis check
Example of analysis types: Hotspots and Threading with user-mode sampling
    Collection: Ok
    Finalization: Ok...
    Report: Ok

HW event-based analysis check (Intel driver)
Example of analysis types: Hotspots with HW event-based sampling, HPC Performance Characterization, etc.
    Collection: Ok
vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes.
    Finalization: Ok...
vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions.

    Report: Ok

HW event-based analysis check (Intel driver)
Example of analysis types: Microarchitecture Exploration
    Collection: Ok
vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes.
    Finalization: Ok...
vtune: Warning: The result contains a lot of raw data. Finalization may take a long time to complete.

vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions.

    Report: Ok

HW event-based analysis with uncore events (Intel driver)
Example of analysis types: Memory Access
    Collection: Ok
vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes.
    Finalization: Ok...
vtune: Warning: The result contains a lot of raw data. Finalization may take a long time to complete.

vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions.

    Report: Ok

HW event-based analysis with stacks (Intel driver)
Example of analysis types: Hotspots with HW event-based sampling and call stacks
    Collection: Ok
vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes.
    Finalization: Ok...
vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions.

    Report: Ok

HW event-based analysis with context switches (Intel driver)
Example of analysis types: Threading with HW event-based sampling
    Collection: Ok
vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes.
    Finalization: Ok...
vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions.

    Report: Ok

Checking DPC++ application as prerequisite for GPU analyses: Ok

GPU HW event-based analysis with runtime tracing
Example of analysis types: GPU Compute/Media Hotspots (characterization mode)
    Collection: Ok
vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes.
    Finalization: Ok...
vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions.
    Report: Ok

GPU software event-based analysis with runtime tracing
Example of analysis types: GPU Compute/Media Hotspots (source analysis mode)
    Collection: Fail
vtune: Error: [Instrumentation Engine]: GTPin:  IGC-GTPin interface version 4090511487 is not supported
vtune: Warning: [Instrumentation Engine]: GTPin:  GTPin didn't find any kernels... Exiting without doing anything.

The check observed a product failure on your system.
Review errors in the output above to fix a problem or contact Intel technical support.

The system is ready for the following analyses:
* Performance Snapshot
* Hotspots and Threading with user-mode sampling
* Hotspots with HW event-based sampling, HPC Performance Characterization, etc.
* Microarchitecture Exploration
* Memory Access
* Hotspots with HW event-based sampling and call stacks
* Threading with HW event-based sampling
* GPU HW event-based analysis with runtime tracing

The following analyses have failed on the system:
* GPU Compute/Media Hotspots (source analysis mode)

[IonutNechita]

Hi @yuzhang3_intel ,

I updated this packages:

Get:1 https://repositories.intel.com/gpu/ubuntu jammy/client amd64 libdrm-dev amd64 2.4.112.4+2056~u22.04 [279 kB]
Get:2 https://repositories.intel.com/gpu/ubuntu jammy/client amd64 libdrm-intel1 amd64 2.4.112.4+2056~u22.04 [72,8 kB]
Get:3 https://repositories.intel.com/gpu/ubuntu jammy/client amd64 libdrm-radeon1 amd64 2.4.112.4+2056~u22.04 [31,0 kB]
Get:4 https://repositories.intel.com/gpu/ubuntu jammy/client amd64 libdrm-nouveau2 amd64 2.4.112.4+2056~u22.04 [27,4 kB]
Get:5 https://repositories.intel.com/gpu/ubuntu jammy/client amd64 libdrm-amdgpu1 amd64 2.4.112.4+2056~u22.04 [29,5 kB]
Get:6 https://repositories.intel.com/gpu/ubuntu jammy/client amd64 libdrm2 amd64 2.4.112.4+2056~u22.04 [45,1 kB]
Get:7 https://repositories.intel.com/gpu/ubuntu jammy/client amd64 libdrm-common all 2.4.112.4+2056~u22.04 [4.604 B]
Get:8 https://repositories.intel.com/gpu/ubuntu jammy/client amd64 intel-metrics-discovery amd64 1.12.169-775~22.04 [3.917 kB]
Get:9 https://repositories.intel.com/gpu/ubuntu jammy/client amd64 libigc1 amd64 1.0.15136.24-775~22.04 [22,1 MB]
Get:10 https://repositories.intel.com/gpu/ubuntu jammy/client amd64 libigdfcl1 amd64 1.0.15136.24-775~22.04 [34,4 MB]
Fetched 60,9 MB in 33s (1.863 kB/s)

And now i have this:

/opt/intel/oneapi/vtune/latest/bin64/vtune-self-checker.sh
Intel(R) VTune(TM) Profiler Self Check Utility
Copyright (C) 2009 Intel Corporation. All rights reserved.
Build Number: 627177

HW event-based analysis (counting mode) (Intel driver)
Example of analysis types: Performance Snapshot
    Collection: Ok
    Finalization: Ok...
    Report: Ok

Instrumentation based analysis check
Example of analysis types: Hotspots and Threading with user-mode sampling
    Collection: Ok
    Finalization: Ok...
    Report: Ok

HW event-based analysis check (Intel driver)
Example of analysis types: Hotspots with HW event-based sampling, HPC Performance Characterization, etc.
    Collection: Ok
vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes.
    Finalization: Ok...
vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions.

    Report: Ok

HW event-based analysis check (Intel driver)
Example of analysis types: Microarchitecture Exploration
    Collection: Ok
vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes.
    Finalization: Ok...
vtune: Warning: The result contains a lot of raw data. Finalization may take a long time to complete.

vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions.

    Report: Ok

HW event-based analysis with uncore events (Intel driver)
Example of analysis types: Memory Access
    Collection: Ok
vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes.
    Finalization: Ok...
vtune: Warning: The result contains a lot of raw data. Finalization may take a long time to complete.

vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions.

    Report: Ok

HW event-based analysis with stacks (Intel driver)
Example of analysis types: Hotspots with HW event-based sampling and call stacks
    Collection: Ok
vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes.
    Finalization: Ok...
vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions.

    Report: Ok

HW event-based analysis with context switches (Intel driver)
Example of analysis types: Threading with HW event-based sampling
    Collection: Ok
vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes.
    Finalization: Ok...
vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions.

    Report: Ok

Checking DPC++ application as prerequisite for GPU analyses: Ok

GPU HW event-based analysis with runtime tracing
Example of analysis types: GPU Compute/Media Hotspots (characterization mode)
    Collection: Ok
vtune: Warning: To enable hardware event-based sampling, VTune Profiler has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes.
    Finalization: Ok...
vtune: Warning: Cannot locate debugging information for the Linux kernel. Source-level analysis will not be possible. Function-level analysis will be limited to kernel symbol tables. See the Enabling Linux Kernel Analysis topic in the product online help for instructions.

    Report: Ok

GPU software event-based analysis with runtime tracing
Example of analysis types: GPU Compute/Media Hotspots (source analysis mode)
    Collection: Ok
    Finalization: Ok...
    Report: Ok

The system is ready to be used for performance analysis with Intel VTune Profiler.
Review warnings in the output above to find product limitations, if any.

The system is ready for the following analyses:
* Performance Snapshot
* Hotspots and Threading with user-mode sampling
* Hotspots with HW event-based sampling, HPC Performance Characterization, etc.
* Microarchitecture Exploration
* Memory Access
* Hotspots with HW event-based sampling and call stacks
* Threading with HW event-based sampling
* GPU HW event-based analysis with runtime tracing
* GPU software event-based analysis with runtime tracing

Log location: /tmp/vtune-tmp-root/self-checker-2024.03.07_17.53.45/log.txt

[yuzhang3_intel]

From the self-check result, the VTune environment is ready now, you can do profiling on CPU/GPU.

[yuzhang3_intel]

BTW, can you share the instructions you update packages? thanks.

[IonutNechita]

Ok. Understood.

But for sep5.service this service remain failed.

In this case i restarted target and this issue is gone.

Maybe this issue appear for first installation without reboot machine.