VTune Profiler cannot recognize the processor

damili_1990 · ‎09-21-2025

Hello Intel Support,

I am using Intel VTune Profiler version 2025.5.0 on a server equipped with Intel Xeon Platinum 8255C @ 2.50GHz (Cascade Lake-SP, 24C/48T, custom SKU).

When I run VTune analysis (e.g. Top-down Microarchitecture Analysis or Memory Access), I get the following error:

vtune: Error: This analysis type is not applicable to the system because VTune Profiler cannot recognize the processor. CPU_NAME: Unknown

The sep5 driver is installed and loaded correctly, but VTune still fails to map the processor microarchitecture. Software-based analysis (Hotspots, user-mode sampling) works, but hardware event-based sampling does not.

This appears to be caused by the fact that VTune’s internal CPUID/microarchitecture database does not include the custom SKU 8255C, even though the underlying microarchitecture is identical to Cascade Lake-SP.

System information:

CPU: Intel Xeon Platinum 8255C (Cascade Lake-SP, Custom SKU)
VTune Profiler: 2025.5.0
OS: [fill in, e.g. RHEL 9.3, kernel 6.6.34-1.el9.x86_64]
SEP driver: loaded successfully (insmod-sep -q shows OK)
CPUID dump: [attach cpuid or lscpu output if possible]

Request:

Could you please provide an updated VTune/driver package that supports the CPUID of this processor?
If available, an NDA package or microarchitecture database update would also be acceptable.
Alternatively, please advise a workaround to enable hardware event-based sampling for this CPU.

Thank you for your support.

damili_1990 · ‎09-21-2025

add sh vtune-self-checker.sh log

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

Ignored warnings: ['To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location.', 'To enable hardware event-based sampling, PRODUCT_LEGAL_SHORT_NAME has disabled the NMI watchdog timer. The watchdog timer will be re-enabled after collection completes.']
Check of files: Ok
================================================================================
Context values:
Command line:
/opt/intel/oneapi/vtune/2025.5/bin64/amplxe-runss --context-value-list
Stdout:
targetOS: Linux
OS: Linux
OSBuildNumber: 92
OSBitness: 64
RootPrivileges: true
isPtraceScopeLimited: false
isCATSupportedByCPU: true
isL3CATAvailable: true
L3CATDetails: COS=16;ways=11
isL2CATAvailable: false
isL3MonitoringSupportedByCPU: true
LLCSize: 37486592
cacheMonitoringUpscalingFactor: 106496
isL3CacheOccupancyAvailable: true
isL3TotalBWAvailable: true
isL3LocalBWAvailable: true
isTSXAvailable: false
isPTAvailable: true
isHTEnabled: true
fpgaOnBoard: None
omniPathOnBoard: None
genArchOnBoard: 0
pciClassParts:
tidValuesForIO:
populatedIoParts:
populatedIoUnits:
populatedTidValuesForIO:
memoryType: Unknown
isSGXAvailable: false
LinuxRelease: 6.6.92-34.1.tl4.x86_64
is3DXPPresent: false
is3DXP2LMMode: false
is3DXPAppDirectMode: false
IsNUMANodeWithoutCPUsPresent: false
Hypervisor: None
PerfmonVersion: 4
isMaxDRAMBandwidthMeasurementSupported: true
preferedGpuAdapter: none
isEHFIAvailable: false
isPtraceAvailable: true
i915Status: MissingDriver
GPUUserGroups:
isFtraceAvailable: yes
isMdfEtwAvailable: false
isCSwitchAvailable: yes
isGpuBusynessAvailable: unsupportedHardware
isGpuWaitAvailable: no
isFunctionTracingAvailable: yes
isIowaitTracingAvailable: yes
isVSyncAvailable: yes
HypervisorType: None
isDeviceOrCredentialGuardEnabled: false
isSEPDriverAvailable: true
SEPDriverVersion: 5.55
isPAXDriverLoaded: true
PAXDriverVersion: 1.0
platformType: 0
CPU_NAME: Unknown
PMU:
referenceFrequency: 2500000000
isPStateAvailable: true
isVTSSPPDriverAvailable: true
isNMIWatchDogTimerRunning: true
LinuxPerfCredentials: Unlimited
LinuxPerfCapabilities: breakpoint:raw;cpu:raw,format,events,ldlat,frontend,offcore_rsp;cstate_core:raw,format,events;cstate_pkg:raw,format,events;intel_bts:raw;intel_pt:raw,format;kprobe:raw,format;msr:raw,format,events;power:raw,format,events;software:raw;tracepoint:raw;uncore_cha:26,raw,format;uncore_iio:6,raw,format;uncore_iio_free_running:6,raw,format,events;uncore_imc:6,raw,format,events;uncore_irp:6,raw,format;uncore_m2m:2,raw,format;uncore_m2pcie:3,raw,format;uncore_m3upi:3,raw,format;uncore_pcu:raw,format;uncore_ubox:raw,format;uncore_upi:3,raw,format;uprobe:raw,format
LinuxPerfStackCapabilities: fp,dwarf,lbr
areKernelPtrsRestricted: no
LinuxPerfMuxIntervalMs: 1
isPerfPCIeMappingAvailable: true
isAOCLAvailable: false
isTPSSAvailable: true
isPytraceAvailable: true
forceShowInlines: false
isEnergyCollectionSupported: true
isSocwatchDriverLoaded: true
isCPUSupportedBySocwatch: true
isCpuThrottlingAvailable: true
l0LoaderStatus: LibNotFound
l0DevicesAvailable: false
l0VPUDevicesAvailable: false
l0GPUDevicesAvailable: false
isXelinkAvailable: false
l0LoaderStatus: LibNotFound

Getting context values: OK
================================================================================
Check driver:
isSEPDriverAvailable: true
isPAXDriverLoaded: true
Command line:
lsmod
Stdout:
sep5 3579904 0

Is SEP in lsmod: True
Ok
================================================================================
SEP version:
Command line:
/opt/intel/oneapi/vtune/2025.5/bin64/sep -version
Stdout:
Sampling Enabling Product Version: 5.55 built on Aug 11 2025 05:52:23
SEP Driver Version: 5.55 (public)
PAX Driver Version: 1.0
Platform type: 0
CPU name: Unknown
PMU:
Driver configs: Non-Maskable Interrupt, REGISTER CHECK ON
Copyright(C) 2007 Intel Corporation. All rights reserved.

Check driver with sep -version: Ok
================================================================================
HW event-based analysis (counting mode)...
Command line:
/opt/intel/oneapi/vtune/2025.5/bin64/vtune -collect performance-snapshot -r /tmp/vtune-tmp-root/self-checker-2025.09.19_21.10.26/result_ps -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2025.5/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2025.5/samples/en/C++/matrix/matrix
Stderr:
vtune: Error: This analysis type is not applicable to the system because VTune Profiler cannot recognize the processor. If this is an old Intel processor, please refer to the minimum hardware requirements in the release note. If this is a new Intel processor, please check for an updated version of VTune Profiler. If this is an unreleased Intel processor, please contact Online Service Center for an NDA product package.
vtune: Error: This analysis type is not applicable to the current machine microarchitecture.

Cannot find 'runsa.options' by path: /tmp/vtune-tmp-root/self-checker-2025.09.19_21.10.26/result_ps/config/runsa.options
HW event-based analysis (counting mode)
Example of analysis types: Performance Snapshot
Collection: Fail
vtune: Error: This analysis type is not applicable to the system because VTune Profiler cannot recognize the processor. If this is an old Intel processor, please refer to the minimum hardware requirements in the release note. If this is a new Intel processor, please check for an updated version of VTune Profiler. If this is an unreleased Intel processor, please contact Online Service Center for an NDA product package.
vtune: Error: This analysis type is not applicable to the current machine microarchitecture.

================================================================================
Instrumentation based analysis check...
Command line:
/opt/intel/oneapi/vtune/2025.5/bin64/vtune -collect hotspots -r /tmp/vtune-tmp-root/self-checker-2025.09.19_21.10.26/result_tpss -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2025.5/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2025.5/samples/en/C++/matrix/matrix
Stderr:
vtune: Error: Option 'pmu-type' received value from the next argument: '--event-config=CPU_CLK_UNHALTED.THREAD,CPU_CLK_UNHALTED.REF_TSC:sample:sa=2500000,INST_RETIRED.ANY:sample:sa=2500000,CPU_CLK_UNHALTED.DISTRIBUTED,UOPS_RETIRED.RETIRE_SLOTS:sample:sa=2000003', but it seems to be an option. Use '-option=value' declaration form or make sure that value is not missed

Instrumentation based analysis check
Example of analysis types: Hotspots and Threading with user-mode sampling
Collection: Fail
vtune: Error: Option 'pmu-type' received value from the next argument: '--event-config=CPU_CLK_UNHALTED.THREAD,CPU_CLK_UNHALTED.REF_TSC:sample:sa=2500000,INST_RETIRED.ANY:sample:sa=2500000,CPU_CLK_UNHALTED.DISTRIBUTED,UOPS_RETIRED.RETIRE_SLOTS:sample:sa=2000003', but it seems to be an option. Use '-option=value' declaration form or make sure that value is not missed

================================================================================
HW event-based analysis check...
Command line:
/opt/intel/oneapi/vtune/2025.5/bin64/vtune -collect hotspots -knob sampling-mode=hw -r /tmp/vtune-tmp-root/self-checker-2025.09.19_21.10.26/result_ah -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2025.5/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2025.5/samples/en/C++/matrix/matrix
Stderr:
vtune: Error: This analysis type is not applicable to the system because VTune Profiler cannot recognize the processor. If this is an old Intel processor, please refer to the minimum hardware requirements in the release note. If this is a new Intel processor, please check for an updated version of VTune Profiler. If this is an unreleased Intel processor, please contact Online Service Center for an NDA product package.

Cannot find 'runsa.options' by path: /tmp/vtune-tmp-root/self-checker-2025.09.19_21.10.26/result_ah/config/runsa.options
HW event-based analysis check
Example of analysis types: Hotspots with HW event-based sampling, HPC Performance Characterization, etc.
Collection: Fail
vtune: Error: This analysis type is not applicable to the system because VTune Profiler cannot recognize the processor. If this is an old Intel processor, please refer to the minimum hardware requirements in the release note. If this is a new Intel processor, please check for an updated version of VTune Profiler. If this is an unreleased Intel processor, please contact Online Service Center for an NDA product package.

================================================================================
HW event-based analysis check...
Command line:
/opt/intel/oneapi/vtune/2025.5/bin64/vtune -collect uarch-exploration -r /tmp/vtune-tmp-root/self-checker-2025.09.19_21.10.26/result_ge -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2025.5/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2025.5/samples/en/C++/matrix/matrix
Stderr:
vtune: Error: This analysis type is not applicable to the current machine microarchitecture.

Cannot find 'runsa.options' by path: /tmp/vtune-tmp-root/self-checker-2025.09.19_21.10.26/result_ge/config/runsa.options
HW event-based analysis check
Example of analysis types: Microarchitecture Exploration
Collection: Fail
vtune: Error: This analysis type is not applicable to the current machine microarchitecture.

================================================================================
HW event-based analysis with uncore events...
Command line:
/opt/intel/oneapi/vtune/2025.5/bin64/vtune -collect memory-access -r /tmp/vtune-tmp-root/self-checker-2025.09.19_21.10.26/result_ma -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2025.5/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2025.5/samples/en/C++/matrix/matrix
Stderr:
vtune: Error: This analysis type is not applicable to the system because VTune Profiler cannot recognize the processor. If this is an old Intel processor, please refer to the minimum hardware requirements in the release note. If this is a new Intel processor, please check for an updated version of VTune Profiler. If this is an unreleased Intel processor, please contact Online Service Center for an NDA product package.
vtune: Error: This analysis type is not applicable to the current machine microarchitecture.
vtune: Error: Cannot collect memory bandwidth data. Make sure the sampling driver is installed and enabled on your system. See the Sampling Drivers help topic for more details. Note that memory bandwidth collection is not possible if you are profiling inside a virtualized environment.

Cannot find 'runsa.options' by path: /tmp/vtune-tmp-root/self-checker-2025.09.19_21.10.26/result_ma/config/runsa.options
HW event-based analysis with uncore events
Example of analysis types: Memory Access
Collection: Fail
vtune: Error: This analysis type is not applicable to the system because VTune Profiler cannot recognize the processor. If this is an old Intel processor, please refer to the minimum hardware requirements in the release note. If this is a new Intel processor, please check for an updated version of VTune Profiler. If this is an unreleased Intel processor, please contact Online Service Center for an NDA product package.
vtune: Error: This analysis type is not applicable to the current machine microarchitecture.
vtune: Error: Cannot collect memory bandwidth data. Make sure the sampling driver is installed and enabled on your system. See the Sampling Drivers help topic for more details. Note that memory bandwidth collection is not possible if you are profiling inside a virtualized environment.

================================================================================
HW event-based analysis with stacks...
Command line:
/opt/intel/oneapi/vtune/2025.5/bin64/vtune -collect hotspots -knob sampling-mode=hw -knob enable-stack-collection=true -r /tmp/vtune-tmp-root/self-checker-2025.09.19_21.10.26/result_ah_with_stacks -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2025.5/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2025.5/samples/en/C++/matrix/matrix
Stderr:
vtune: Error: This analysis type is not applicable to the system because VTune Profiler cannot recognize the processor. If this is an old Intel processor, please refer to the minimum hardware requirements in the release note. If this is a new Intel processor, please check for an updated version of VTune Profiler. If this is an unreleased Intel processor, please contact Online Service Center for an NDA product package.

Cannot find 'runsa.options' by path: /tmp/vtune-tmp-root/self-checker-2025.09.19_21.10.26/result_ah_with_stacks/config/runsa.options
HW event-based analysis with stacks
Example of analysis types: Hotspots with HW event-based sampling and call stacks
Collection: Fail
vtune: Error: This analysis type is not applicable to the system because VTune Profiler cannot recognize the processor. If this is an old Intel processor, please refer to the minimum hardware requirements in the release note. If this is a new Intel processor, please check for an updated version of VTune Profiler. If this is an unreleased Intel processor, please contact Online Service Center for an NDA product package.

================================================================================
HW event-based analysis with context switches...
Command line:
/opt/intel/oneapi/vtune/2025.5/bin64/vtune -collect threading -knob sampling-and-waits=hw -knob enable-stack-collection=false -r /tmp/vtune-tmp-root/self-checker-2025.09.19_21.10.26/result_th -data-limit 0 -finalization-mode none -source-search-dir /opt/intel/oneapi/vtune/2025.5/samples/en/C++/matrix/src -- /opt/intel/oneapi/vtune/2025.5/samples/en/C++/matrix/matrix
Stderr:
vtune: Error: This analysis type is not applicable to the system because VTune Profiler cannot recognize the processor. If this is an old Intel processor, please refer to the minimum hardware requirements in the release note. If this is a new Intel processor, please check for an updated version of VTune Profiler. If this is an unreleased Intel processor, please contact Online Service Center for an NDA product package.
vtune: Error: This analysis type is not applicable to the current machine microarchitecture.

Cannot find 'runsa.options' by path: /tmp/vtune-tmp-root/self-checker-2025.09.19_21.10.26/result_th/config/runsa.options
HW event-based analysis with context switches
Example of analysis types: Threading with HW event-based sampling
Collection: Fail
vtune: Error: This analysis type is not applicable to the system because VTune Profiler cannot recognize the processor. If this is an old Intel processor, please refer to the minimum hardware requirements in the release note. If this is a new Intel processor, please check for an updated version of VTune Profiler. If this is an unreleased Intel processor, please contact Online Service Center for an NDA product package.
vtune: Error: This analysis type is not applicable to the current machine microarchitecture.

Getting available devices:
Command line:
sycl-ls
Exception: [Errno 2] No such file or directory: 'sycl-ls'
Checking DPC++ application as prerequisite for GPU analyses...
Setting envirnoment variable:
ONEAPI_DEVICE_SELECTOR=opencl:gpu
Command line:
/opt/intel/oneapi/vtune/2025.5/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp
Stderr:
/opt/intel/oneapi/vtune/2025.5/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp: error while loading shared libraries: libsycl.so.8: cannot open shared object file: No such file or directory

Setting envirnoment variable:
ONEAPI_DEVICE_SELECTOR=level_zero:gpu
Command line:
/opt/intel/oneapi/vtune/2025.5/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp
Stderr:
/opt/intel/oneapi/vtune/2025.5/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp: error while loading shared libraries: libsycl.so.8: cannot open shared object file: No such file or directory

Setting envirnoment variable:
ZES_ENABLE_SYSMAN=1
Command line:
/opt/intel/oneapi/vtune/2025.5/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp
Stderr:
/opt/intel/oneapi/vtune/2025.5/bin64/self_check_apps/matrix.dpcpp/matrix.dpcpp: error while loading shared libraries: libsycl.so.8: cannot open shared object file: No such file or directory

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 check observed a product failure on your system.
Review errors in the output above to fix a problem or contact Intel technical support.

The following analyses have failed on the system:
* 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 Compute/Media Hotspots (characterization mode)
* GPU Compute/Media Hotspots (source analysis mode)

Log location: /tmp/vtune-tmp-root/self-checker-2025.09.19_21.10.26/log.txt

damili_1990 · ‎09-21-2025