VTune's self-check fails on GPU Compute/Media Hotspots

[Hrishi2407]

Hi,

I'm using

OS: Ubuntu 24.10
VTune: 2025.0.1
CPU: Intel(R) Core(TM) Ultra 7 
GPU: Intel(R) Arc(TM) Graphics

After running "vtune-self-checker.sh"

Intel(R) VTune(TM) Profiler Self Check Utility
Copyright (C) 2009 Intel Corporation. All rights reserved.
Build Number: 629235

HW event-based analysis (counting mode) (Perf)   
Example of analysis types: Performance Snapshot
    Collection: Ok
vtune: Error: Cannot stop collection of GPU events
    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 (Perf)   
Example of analysis types: Hotspots with HW event-based sampling, HPC Performance Characterization, etc.
    Collection: Ok
vtune: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location.
vtune: Warning: Precise events are not available on this platform in the driverless mode and will be collected as non-precise. Some metrics may be less accurately attributed to the program code. Please consider loading VTune Profiler driver. Updating Linux kernel to newer version may also help.
    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 (Perf)   
Example of analysis types: Microarchitecture Exploration
    Collection: Ok
vtune: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location.
vtune: Warning: Precise events are not available on this platform in the driverless mode and will be collected as non-precise. Some metrics may be less accurately attributed to the program code. Please consider loading VTune Profiler driver. Updating Linux kernel to newer version may also help.
    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 uncore events (Perf)   
Example of analysis types: Memory Access
    Collection: Ok
vtune: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location.
vtune: Warning: Precise events are not available on this platform in the driverless mode and will be collected as non-precise. Some metrics may be less accurately attributed to the program code. Please consider loading VTune Profiler driver. Updating Linux kernel to newer version may also help.
    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 stacks (Perf)   
Example of analysis types: Hotspots with HW event-based sampling and call stacks
    Collection: Ok
vtune: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location.
vtune: Warning: Precise events are not available on this platform in the driverless mode and will be collected as non-precise. Some metrics may be less accurately attributed to the program code. Please consider loading VTune Profiler driver. Updating Linux kernel to newer version may also help.
    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 (Perf)   
Example of analysis types: Threading with HW event-based sampling
    Collection: Ok
vtune: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location.
vtune: Warning: Precise events are not available on this platform in the driverless mode and will be collected as non-precise. Some metrics may be less accurately attributed to the program code. Please consider loading VTune Profiler driver. Updating Linux kernel to newer version may also help.
    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: Fail
Unable to run DPC++ application on GPU connected to this system. If you are using an Intel GPU and want to verify profiling support for DPC++ applications, check these requirements:
* Install Intel(R) GPU driver.
* Install Intel(R) Level Zero GPU runtime.
* Install Intel(R) oneAPI DPC++ Runtime and set the environment.

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

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

Log location: /tmp/vtune-tmp-user/self-checker-2025.03.07_05.36.40/log.txt

The drivers are loaded properly and SYCL programs run on the GPU, but VTune's self-check fails on GPU Compute/Media Hotspots. Any solutions to this?

[yuzhang3_intel]

Please run the command line below to capture gpu hotspots:

$ vtune -collect gpu-hotspots --  /opt/intel/oneapi/vtune/latest/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp

[Hrishi2407]

Results after running "vtune -collect gpu-hotspots -result-dir ~/vtune_results -- /opt/intel/oneapi/vtune/latest/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp"

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.
Warning: PMU counter(s) [GP2 ] on p-core cores is (are) already in use by other software and the data collected on these counter(s) may be incorrect
vtune: Collection started. To stop the collection, either press CTRL-C or enter from another console window: vtune -r /home/user/vtune_results -command stop.
Address of buf1 = 0x70f1476a4010
Offset of buf1 = 0x70f1476a4180
Address of buf2 = 0x70f146ea3010
Offset of buf2 = 0x70f146ea31c0
Address of buf3 = 0x70f1466a2010
Offset of buf3 = 0x70f1466a2100
Address of buf4 = 0x70f141dff010
Offset of buf4 = 0x70f141dff140
Using multiply kernel: multiply1

Available devices:
Intel(R) Arc(TM) Graphics
Intel(R) Arc(TM) Graphics

*****
* Running on Intel(R) Arc(TM) Graphics
*****
No subdevices available, using the whole device


*****
* Running on Intel(R) Arc(TM) Graphics
*****
No subdevices available, using the whole device

************
* Finished *
************
Elapsed Time: 1.37159s
vtune: Collection stopped.
vtune: Using result path `/home/user/vtune_results'
vtune: Executing actions 19 % Resolving information for `libgcc_s.so.1'        
vtune: Warning: Cannot locate debugging information for file `/usr/lib/x86_64-linux-gnu/libgcc_s.so.1'.
vtune: Executing actions 19 % Resolving information for `libxed.so'            
vtune: Warning: Cannot locate debugging information for file `/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.33'.
vtune: Executing actions 19 % Resolving information for `libittnotify_collector
vtune: Warning: Cannot locate debugging information for file `/opt/intel/oneapi/vtune/2025.0/lib64/runtime/libittnotify_collector.so'.
vtune: Executing actions 19 % Resolving information for `libc++abi.so'         
vtune: Warning: Cannot locate debugging information for file `/opt/intel/oneapi/vtune/2025.0/lib64/runtime/libittnotify_collector.so'.
vtune: Warning: Cannot locate file `autofs4.ko'.
vtune: Executing actions 19 % Resolving information for `ld-linux-x86-64.so.2' 
vtune: Warning: Cannot locate debugging information for file `/lib64/ld-linux-x86-64.so.2'.
vtune: Executing actions 20 % Resolving information for `libsycl.so.8.0.0'     
vtune: Warning: Cannot locate debugging information for file `/usr/lib/x86_64-linux-gnu/libze_intel_gpu.so.1.6.32224'.
vtune: Executing actions 20 % Resolving information for `ld-linux-x86-64.so.2' 
vtune: Warning: Cannot locate debugging information for file `/usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2'.
vtune: Executing actions 20 % Resolving information for `libc.so.6'            
vtune: Warning: Cannot locate debugging information for file `/usr/lib/x86_64-linux-gnu/libc.so.6'.
vtune: Executing actions 20 % Resolving information for `libdwarf.so'          
vtune: Warning: Cannot locate debugging information for file `/usr/lib/x86_64-linux-gnu/intel-opencl/libigdrcl.so'.
vtune: Executing actions 20 % Resolving information for `libze_intel_vpu.so.1.1
vtune: Warning: Cannot locate debugging information for file `/usr/lib/x86_64-linux-gnu/libze_intel_vpu.so.1.13.0'.
vtune: Warning: Cannot locate debugging information for file `/usr/lib/x86_64-linux-gnu/intel-opencl/libigdrcl.so'.
vtune: Executing actions 21 % Resolving information for `libc.so.6'            
vtune: Warning: Cannot locate debugging information for file `/lib/x86_64-linux-gnu/libc.so.6'.
vtune: Executing actions 21 % Resolving information for `libpindwarf.so'       
vtune: Warning: Cannot locate file `vmlinux'.
vtune: Executing actions 21 % Resolving information for `vmlinux'              
vtune: Warning: Cannot locate file `xe.ko'.
vtune: Executing actions 22 % Resolving information for `libur_loader.so.0'    
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.
vtune: Warning: Cannot locate file `sep5.ko'.
vtune: Executing actions 22 % Resolving information for `libtpsstool.so'       
vtune: Warning: Cannot locate debugging information for file `/opt/intel/oneapi/vtune/2025.0/lib64/libtpsstool.so'.
vtune: Executing actions 75 % Generating a report                              Elapsed Time: 1.821s
    GPU Time: 0.079s
GPU Stack 0
    XVE Array Stalled/Idle: 30.7% of Elapsed time with GPU busy
     | The percentage of time when the XVEs were stalled or idle is high, which
     | has a negative impact on compute-bound applications.
     |
        Occupancy: 95.5% of peak value

            Hottest GPU Computing Tasks with Low Occupancy
            Computing Task  Total Time  SIMD Width  Peak XVE Threads Occupancy(%)  Occupancy(%)  SIMD Utilization(%)
            --------------  ----------  ----------  -----------------------------  ------------  -------------------
GPU Stack 1
Collection and Platform Info
    Application Command Line: /opt/intel/oneapi/vtune/latest/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp 
    User Name: user
    Operating System: 6.11.0-19-generic DISTRIB_ID=Ubuntu DISTRIB_RELEASE=24.10 DISTRIB_CODENAME=oracular DISTRIB_DESCRIPTION="Ubuntu 24.10"
    Computer Name: khadas
    Result Size: 18.9 MB 
    Collection start time: 09:03:17 19/03/2025 UTC
    Collection stop time: 09:03:19 19/03/2025 UTC
    Collector Type: Event-based sampling driver,User-mode sampling and tracing
    CPU
        Name: Intel(R) microarchitecture code named Lunarlake-M
        Frequency: 3.302 GHz
        Logical CPU Count: 8
    GPU
        Name: Lunar Lake [Intel Arc Graphics 130V / 140V]
        Vendor: Intel Corporation
        XVE Count: 64
        Max XVE Thread Count: 8
        Max Core Frequency: 1.950 GHz
        GPU OpenCL Info
            Version: OpenCL 3.0 NEO 
            Max Compute Units: 64
            Max Work Group Size: 1,024
            Local Memory: 131.1 KB 
            SVM Capabilities

If you want to skip descriptions of detected performance issues in the report,
enter: vtune -report summary -report-knob show-issues=false -r <my_result_dir>.
Alternatively, you may view the report in the csv format: vtune -report
<report_name> -format=csv.
vtune: Executing actions 100 % done      

[yuzhang3_intel]

Can you run self-check utility again and share the log file? 

[Hrishi2407]

This is the log file after running vtune self checker

[yuzhang3_intel]

Can you try the latest compute runtime driver?

https://github.com/intel/compute-runtime/releases

[Hrishi2407]

I tested it, still same issue.

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

[muhammadhammaf2424]

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Instructions to Disable PMT and Rebuild the Driver</title>
</head>
<body>
<h2>Instructions to Disable PMT and Rebuild the Driver:</h2>
<ol>
<li>Navigate to the directory: <code>/opt/intel/sep/sepdk/src/build-driver</code>.</li>
<li>Open the file and locate line 122.</li>
<li>Change the line from <code>BUILD_PMT="YES"</code> to <code>BUILD_PMT="NO"</code>.</li>
<li>Follow the usual procedure to build and load the driver.</li>
</ol>

<p><strong><a href="https://www.mariehansenproperties.com/">Best Hawaii Property Management Company</a></strong></p>
</body>
</html>

[damon467]

Thanks for sharing the details regarding the VTune self-check issue. It’s helpful to see this flagged, especially around the GPU Compute/Media Hotspots section. Hopefully, this gets addressed in the next update or someone from the Intel team can provide a workaround soon.

[yuzhang3_intel]

Please try the latest version 2025.1.

[Hrishi2407]

Installed the latest version

Intel(R) VTune(TM) Profiler 2025.1.0 (build 629847) Command Line Tool
Copyright (C) 2009 Intel Corporation. All rights reserved.

Updated "BUILD_PMT="YES" to "BUILD_PMT="NO"

"sudo ./build-driver":

C compiler to use: [ /bin/gcc ] 
C compiler version: 14.2.0

Make command to use: [ /bin/make ] 
Make version: 4.3

Kernel source directory: [ /lib/modules/6.11.0-19-generic/build ] 
Kernel version: 6.11.0-19-generic

Cleaning workspaces ... 
Done

Building socperf driver ... 
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: x86_64-linux-gnu-gcc-14 (Ubuntu 14.2.0-4ubuntu2) 14.2.0
  You are using:           gcc (Ubuntu 14.2.0-4ubuntu2) 14.2.0
Skipping BTF generation for /opt/intel/oneapi/vtune/2025.1/sepdk/src/socperf/src/socperf3.ko due to unavailability of vmlinux
Done

Building sep driver ... 
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: x86_64-linux-gnu-gcc-14 (Ubuntu 14.2.0-4ubuntu2) 14.2.0
  You are using:           gcc (Ubuntu 14.2.0-4ubuntu2) 14.2.0
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x35: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x36: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x37: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x3b: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x40: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x45: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x4a: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x4f: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x54: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x59: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x5e: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x63: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x68: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x6c: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x71: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x76: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x7b: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x80: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x85: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x8a: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x8c: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x8e: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x90: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x92: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x95: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x9a: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0x9d: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0xa2: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0xa3: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0xa5: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0xa7: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0xaa: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0xae: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0xb3: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0xb8: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0xbd: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0xc2: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0xc7: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0xcc: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0xd1: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0xd6: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0xdb: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0xe0: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0xe5: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0xea: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0xef: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0xf4: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0xf8: unreachable instruction
/opt/intel/oneapi/vtune/2025.1/sepdk/src/sys64.o: warning: objtool: .text+0xf9: unreachable instruction
Skipping BTF generation for /opt/intel/oneapi/vtune/2025.1/sepdk/src/sep5.ko due to unavailability of vmlinux
Done

Building pax driver ... 
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: x86_64-linux-gnu-gcc-14 (Ubuntu 14.2.0-4ubuntu2) 14.2.0
  You are using:           gcc (Ubuntu 14.2.0-4ubuntu2) 14.2.0
Skipping BTF generation for /opt/intel/oneapi/vtune/2025.1/sepdk/src/pax/pax.ko due to unavailability of vmlinux
Done

Building vtsspp driver ... 
make[1]: Entering directory '/opt/intel/oneapi/vtune/2025.1/sepdk/src/vtsspp'
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: x86_64-linux-gnu-gcc-14 (Ubuntu 14.2.0-4ubuntu2) 14.2.0
  You are using:           gcc (Ubuntu 14.2.0-4ubuntu2) 14.2.0
Skipping BTF generation for /opt/intel/oneapi/vtune/2025.1/sepdk/src/vtsspp/vtsspp.ko due to unavailability of vmlinux
make[1]: Leaving directory '/opt/intel/oneapi/vtune/2025.1/sepdk/src/vtsspp'
Done

Building socwatch driver ... 
Building drivers for Linux target
/lib/modules/6.11.0-19-generic/build will be used as the kernel build directory
Using alternate compiler '/bin/gcc'
Removing previously built driver and scripts from /opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/drivers
mkdir: cannot create directory ‘/opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/drivers’: File exists
'-c /bin/gcc -l -k /lib/modules/6.11.0-19-generic/build' options will be used to build the SoCWatch driver
-c /bin/gcc -l -k /lib/modules/6.11.0-19-generic/build
************ Building socwatch2_16-x32_64-6.11.0-19-genericsmp.ko driver ************
Using C compiler = /bin/gcc
Using kernel build dir = /lib/modules/6.11.0-19-generic/build
No module symvers file found
Using common inc dir = /opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/../common/include
"/lib/modules/6.11.0-19-generic/build/include/linux/cpufreq.h" exists!
"/lib/modules/6.11.0-19-generic/build/include/linux/device/class.h" exists!
Using file name sw_driver
Make args = KERNEL_SRC_DIR=/lib/modules/6.11.0-19-generic/build CPUFREQ_FIX_BACKPORTED=1 CLASSCREATE_CHANGE_BACKPORTED=1 DO_DEBUG_BUILD=0 DO_PROFILING=0 COMMON_INC_DIR=/opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/../common/include MODULE_SYMVERS_FILE= FILE_NAME=sw_driver 
make[1]: Entering directory '/opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver'
make -C /lib/modules/6.11.0-19-generic/build M=/opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver clean
make[2]: Entering directory '/usr/src/linux-headers-6.11.0-19-generic'
  CLEAN   /opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/Module.symvers
make[2]: Leaving directory '/usr/src/linux-headers-6.11.0-19-generic'
make[1]: Leaving directory '/opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver'
Using C compiler = /bin/gcc
Using kernel build dir = /lib/modules/6.11.0-19-generic/build
No module symvers file found
Using common inc dir = /opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/../common/include
"/lib/modules/6.11.0-19-generic/build/include/linux/cpufreq.h" exists!
"/lib/modules/6.11.0-19-generic/build/include/linux/device/class.h" exists!
Using file name sw_driver
Make args = KERNEL_SRC_DIR=/lib/modules/6.11.0-19-generic/build CPUFREQ_FIX_BACKPORTED=1 CLASSCREATE_CHANGE_BACKPORTED=1 DO_DEBUG_BUILD=0 DO_PROFILING=0 COMMON_INC_DIR=/opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/../common/include MODULE_SYMVERS_FILE= FILE_NAME=sw_driver 
make[1]: Entering directory '/opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver'
make -C /lib/modules/6.11.0-19-generic/build M=/opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver clean
make[2]: Entering directory '/usr/src/linux-headers-6.11.0-19-generic'
make[2]: Leaving directory '/usr/src/linux-headers-6.11.0-19-generic'
************************************************************
KERNEL_SRC_DIR=/lib/modules/6.11.0-19-generic/build
CPUFREQ_FIX_BACKPORTED=1
CLASSCREATE_CHANGE_BACKPORTED=1
MODULE_SYMVERS_FILE=
DO_DRIVER_PROFILING=0
INCDIR_1=/opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/../common/include
************************************************************
make -C /lib/modules/6.11.0-19-generic/build M=/opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver modules PWD=/opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver
make[2]: Entering directory '/usr/src/linux-headers-6.11.0-19-generic'
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: x86_64-linux-gnu-gcc-14 (Ubuntu 14.2.0-4ubuntu2) 14.2.0
  You are using:           gcc (Ubuntu 14.2.0-4ubuntu2) 14.2.0
  CC [M]  /opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/src/sw_driver.o
  CC [M]  /opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/src/sw_hardware_io.o
  CC [M]  /opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/src/sw_output_buffer.o
  CC [M]  /opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/src/sw_tracepoint_handlers.o
  CC [M]  /opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/src/sw_collector.o
  CC [M]  /opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/src/sw_mem.o
  CC [M]  /opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/src/sw_internal.o
  CC [M]  /opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/src/sw_file_ops.o
  CC [M]  /opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/src/sw_ops_provider.o
  CC [M]  /opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/src/sw_trace_notifier_provider.o
  CC [M]  /opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/src/sw_reader.o
  CC [M]  /opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/src/sw_telem.o
  CC [M]  /opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/src/sw_pmt.o
  CC [M]  /opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/src/sw_counter_list.o
  CC [M]  /opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/src/sw_pci.o
  LD [M]  /opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/socwatch2_16.o
  MODPOST /opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/Module.symvers
  CC [M]  /opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/socwatch2_16.mod.o
  LD [M]  /opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/socwatch2_16.ko
  BTF [M] /opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/socwatch2_16.ko
Skipping BTF generation for /opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver/socwatch2_16.ko due to unavailability of vmlinux
make[2]: Leaving directory '/usr/src/linux-headers-6.11.0-19-generic'
make[1]: Leaving directory '/opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/socwatch_driver'
************ Built drivers are copied to /opt/intel/oneapi/vtune/2025.1/sepdk/src/socwatch/drivers directory ************
Done

Done building the drivers

"sudo ./insmod-sep -r -g user":

PYTHON is set to python3

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.

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.
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-6.11.0-19-genericsmp.ko
Setting group ownership of devices to group "user" ... 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-6.11.0-19-genericsmp.ko
Setting group ownership of devices to group "user" ... done.
Setting file permissions on devices to "660" ... done.
The socperf3 driver has been successfully loaded.

---------------------    Loading SEP driver    --------------------- 
Executing: insmod ./sep5-x32_64-6.11.0-19-genericsmp.ko sym_lookup_func_addr="ffffffff9ca2bb90"
Setting group ownership of devices to group "user" ... 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-6.11.0-19-genericsmp.ko gid=1000 mode=0660 ksyms="ffffffff9ca2bb90"
The vtsspp driver has been successfully loaded.

--------------------- Loading SOCWATCH driver --------------------- 
Checking for socwatch driver ... not detected.

Executing: insmod ./socwatch/drivers/socwatch2_16-x32_64-6.11.0-19-genericsmp.ko
insmod: ERROR: could not insert module ./socwatch/drivers/socwatch2_16-x32_64-6.11.0-19-genericsmp.ko: Invalid parameters

Error: socwatch2_16-x32_64-6.11.0-19-genericsmp driver failed to load!

You may need to build socwatch2_16-x32_64-6.11.0-19-genericsmp driver for your kernel.
Please see the socwatch2_16-x32_64-6.11.0-19-genericsmp driver README for instructions.

Having the same driver and gpu compute issues in the new version

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

[samuelallen5]

It looks like your VTune setup is mostly functional, but there are some limitations, especially with GPU analysis. The key issues seem to be missing kernel debugging info, lack of precise event collection in driverless mode, and GPU profiling failures due to missing dependencies. You might need to install Intel GPU drivers, Level Zero runtime, and oneAPI DPC++ Runtime to fix this. Also, considering holiday hours, now might be a good time to troubleshoot and optimize your setup for future profiling sessions!