- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I'm running vtune on
OS: ubuntu22.04
vtune: 2023.1.0
CPU: Intel i7-12700H
GPU: Intel iris Xe Gen12
When running vtune-self-checker.sh:
root@ubuntu2204:/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: 625246
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
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
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 (Intel driver)
Example of analysis types: Memory Access
Collection: Ok
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
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
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-root/self-checker-2023.06.08_16.19.44/log.txt
Drivers are already loaded properly:
root@ubuntu2204:/opt/intel/oneapi/vtune/latest/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".
socwatch2_15 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".
When running vtune-gui:
root@ubuntu2204:/opt/intel/oneapi/vtune/latest/bin64# ./vtune-gui
[36953:0608/163730.647467:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
[36925:0608/163731.099072:ERROR:cert_verify_proc_builtin.cc(670)] CertVerifyProcBuiltin for 127.0.0.1 failed:
----- Certificate i=0 (CN=ubuntu2204) -----
ERROR: No matching issuer found
No error message on vtune-gui analysis configuration:
The analyzing process always stuck in finalizing result:
Could you please help me fix this issue? I know there are similar posts. But those solutions cannot solve my issue. Thanks in advance.
Link Copied
- « Previous
-
- 1
- 2
- Next »
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It looks like you didn't install oneAPI toolkit, so there is no sycl library found, we need to check if your NEO runtime is ready, like the output below:
C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\self_check_apps\matrix.dpcpp>matrix.dpcpp.exe
Address of buf1 = 00000145643CA040
Offset of buf1 = 00000145643CA180
Address of buf2 = 0000014564BD9040
Offset of buf2 = 0000014564BD91C0
Address of buf3 = 00000145653EA040
Offset of buf3 = 00000145653EA100
Address of buf4 = 0000014565BF7040
Offset of buf4 = 0000014565BF7140
Using multiply kernel: multiply1
Available devices:
Intel(R) Iris(R) Xe Graphics
Intel(R) Iris(R) Xe Graphics
*****
* Running on Intel(R) Iris(R) Xe Graphics
*****
No subdevices available, using the whole device
*****
* Running on Intel(R) Iris(R) Xe Graphics
*****
No subdevices available, using the whole device
************
* Finished *
************
Elapsed Time: 0.545026s

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- « Previous
-
- 1
- 2
- Next »