I'm using amplxe-cl to collect locksandwaits on a running process.

/opt/intel/vtune_amplifier/bin64/amplxe-cl -collect locksandwaits -target-pid=9929

I got the error:

amplxe: Warning: The analysis type 'locksandwaits' is deprecated. Use 'threading' analysis type instead. See more details with 'amplxe-cl -help collect threading'.
amplxe: Collection started. To stop the collection, either press CTRL-C or enter from another console window: amplxe-cl -r /data1/sunkaicheng/indigo/brec_indigo_recall/build/r002lw -command stop.
amplxe: Warning: Cannot stop posix timer: __NR_timer_settime() system call returned -1.
amplxe: Collection detached.
amplxe: Collection stopped.
amplxe: Using result path `/data1/sunkaicheng/indigo/brec_indigo_recall/build/r002lw'
amplxe: Executing actions 50 % done
amplxe: Error: 0x40000003 (Unexpected internal error / invalid state) -- locale::facet::_S_create_c_locale name not valid

system: ubuntu 16.04

kernal: 4.9.70-040970-generic

CPU: Intel(R) Xeon(R) Silver 4110 CPU @ 2.10GHz

Windows 10

Intel(R) VTune(TM) Amplifier 2019 Update 6

MS Visual Studio 2019

intel i5 750, 8gb ddr3

Hello! 

Even after reinstalling ms visual studio and parallel studio xe vtune doesnt run in visual studio ide. when execute vtune in his own gui by user mode sampling i get this error when is collecting results. i cant also run in hardware event mode sampling because vtune doesnt recognize my processor.

log of installation is attached.

thank you for your help

""""""""""""""""""

Exception]
Address: 0x00007ff9fed4fadd
Code: 0x00000000c0000094
CrashedPID: 7768
CrashedTID: 7772
Description: EXCEPTION_INT_DIVIDE_BY_ZERO
Module: 
Product: Intel(R) VTune(TM) Amplifier 2019 Update 6; 602217
ReportPath: C:\Users\HENRIQ~1\AppData\Local\Temp\amplxe-log-Henrique Gropelli\2019-11-21-14-28-46-683.amplxe-backend.exe\

[Process]
Process Name: amplxe-backend.exe
Virtual Memory Size: 4742360K
Working Set Size: 221460K

[Dump]
Path: C:\Users\HENRIQ~1\AppData\Local\Temp\amplxe-log-Henrique Gropelli\2019-11-21-14-28-46-683.amplxe-backend.exe\crash.dmp

[PremortalLog]
6709 [8000] ERROR apiservice <> - getStatus() == ServiceStatus::Running
C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp(199): apisvc1::Service::getHttpPort
, at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp:199
6772 [8000] ERROR apiservice <> - getStatus() == ServiceStatus::Running
C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp(199): apisvc1::Service::getHttpPort
, at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp:199
6834 [8000] ERROR apiservice <> - getStatus() == ServiceStatus::Running
C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp(199): apisvc1::Service::getHttpPort
, at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp:199
6897 [8000] ERROR apiservice <> - getStatus() == ServiceStatus::Running
C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp(199): apisvc1::Service::getHttpPort
, at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp:199
6959 [8000] ERROR apiservice <> - getStatus() == ServiceStatus::Running
C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp(199): apisvc1::Service::getHttpPort
, at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp:199
7022 [8000] ERROR apiservice <> - getStatus() == ServiceStatus::Running
C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp(199): apisvc1::Service::getHttpPort
, at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp:199
7084 [8000] ERROR apiservice <> - getStatus() == ServiceStatus::Running
C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp(199): apisvc1::Service::getHttpPort
, at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp:199
7134 [8000] ERROR apiservice <> - getStatus() == ServiceStatus::Running
C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp(199): apisvc1::Service::getHttpPort
, at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp:199
7212 [7544] ERROR cfgmgr <> - Cannot find context value: targetOS., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
7227 [7544] ERROR cfgmgr <> - Cannot find context value: targetOS., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
28099 [3556] ERROR cfgmgr <> - Cannot find context value: targetOS., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
28109 [3556] ERROR cfgmgr <> - Cannot find context value: targetOS., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
28340 [7368] ERROR cfgmgr <> - Errors happened during transformation
28340 [7368] ERROR cfgmgr <> - %ThisTargetTypeOnlyForADB
28341 [7368] ERROR cfgmgr <> - Errors happened during transformation
28341 [7368] ERROR cfgmgr <> - %ThisTargetTypeNotWorking
28378 [5280] ERROR cfgmgr <> - Errors happened during transformation
28378 [5280] ERROR cfgmgr <> - %ThisTargetTypeOnlyForADB
28379 [5280] ERROR cfgmgr <> - Errors happened during transformation
28379 [5280] ERROR cfgmgr <> - %ThisTargetTypeNotWorking
29535 [7368] ERROR cfgmgr <> - Errors happened during transformation
29535 [7368] ERROR cfgmgr <> - %ThisAnalysisTypeIsNotApplicable
29552 [7368] ERROR cfgmgr <> - Errors happened during transformation
29552 [7368] ERROR cfgmgr <> - %ThisAnalysisTypeIsOnlyForAndroidAndLinux
29559 [7368] ERROR cfgmgr <> - Errors happened during transformation
29559 [7368] ERROR cfgmgr <> - %ThisAnalysisTypeIsNotApplicable
29568 [7368] ERROR collectionapi <> - pSetting
C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\collectionapi1\src\collection_configuration_context.cpp(953): collectionapi_1::CollectionConfigurationContext::getCurrentCollectorId
, at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\collectionapi1\src\collection_configuration_context.cpp:953
29568 [7368] ERROR cctrl.exchange <> - (!collector.is_null()) && (!to.is_null()) 'gh2::error::IsNot.Valid.Argument:'
C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cctrl2\core\target_session.cpp(82): cctrl2::BaseTargetSession::putCollectorContext
, at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cctrl2\core\target_session.cpp:82
29624 [3556] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
29624 [3556] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
29626 [3556] ERROR cfgmgr <> - Cannot find context value: showInlinesByDefault., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
29662 [3556] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
29663 [3556] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
29666 [3556] ERROR cfgmgr <> - Cannot find context value: showInlinesByDefault., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
29714 [5280] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
29714 [5280] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
29716 [5280] ERROR cfgmgr <> - Cannot find context value: showInlinesByDefault., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
29742 [5280] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
29742 [5280] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
36626 [3556] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
36626 [3556] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
36628 [3556] ERROR cfgmgr <> - Cannot find context value: showInlinesByDefault., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
36654 [3556] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
36654 [3556] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
37867 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
37867 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
37868 [7772] ERROR cfgmgr <> - Cannot find context value: showInlinesByDefault., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
37920 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
37920 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
37938 [7772] ERROR cfgmgr <> - Cannot find context value: targetOS., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
37947 [7772] ERROR cfgmgr <> - Cannot find context value: targetOS., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
51850 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
51850 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
51900 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
51901 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
51961 [7772] ERROR cfgmgr <> - (outputBag != 0) && (inputBag != 0) && !m_ctx.is_null() 'gh2::error::FailedTo.Process.The.Parameter:'
C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp(1769): cfgmgr2::RuleProcessor::process
, at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:1769
51992 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
51992 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
52007 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
52007 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
52054 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
52054 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
52159 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
52159 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
52179 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
52179 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
52636 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
52636 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
52670 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
52671 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384

[Context.0x00001e5c]
EAX: 0x0000000000000000
EBP: 0x000000b5482f7ed0
EBX: 0x000000b5482f8490
ECX: 0x000002a1c39e0c48
EDI: 0x000000b5482f8768
EDX: 0x0000000000000000
EIP: 0x00007ff9fed4fadd
ESI: 0x0000000000000000
ESP: 0x000000b5482f7e90
R10: 0x0000000000008000
R11: 0x000000b5482f7d00
R12: 0x0000000000000001
R13: 0x0000000000000000
R14: 0x000000b5482f86c8
R15: 0x000000b5482f8f50
R8: 0x000002a1c39e0be8
R9: 0x000002a1c39e0be0

""""""""""""""

When using 2019 vtune to profile memory consumption. after attaching PID, it immediately errors out and crashes the process I try to profile. I'm using it in debian 9. wondering if anyboyd experienced such issue.

Hi, we're potentially looking to try VTune profiler (and Intel Advisor). Looking at the FAQ there is a free community support license which is fine for us, but what's not clear is if it's still free for commercial use under the community license - could you confirm if that's the case, or if there are any better links that explain this please.

Do Vtune and Advisor both come under the same free community license?

Hi,

I am working with Intel’s vtune performance analyser for various workloads in HPC.

Is there a way I can summarize my runtime analysis as a csv file for each thread ?

Currently I am summarizing vtune analysis to csv using

$ amplxe-cl -report hotspots -result-dir PATH/TO/DIR/ -format=csv -report-output /PATH/TO/SOMETHING.csv

But this command removes per-thread information and only gives me an overall view of the complete application. I want a per thread summary in csv format. I know this can be done on the gui but that’s a lot of manual work and a command line version could be very useful for automation.

Hello Intel Team,

I'm trying to run an academic license of VTune 2019 on a linux server with a simple Python file, test.py. I used the command line interface to collect data using: amplxe-cl -collect hotspots -r vtune_test_hotspots_results -run-pass-thru=--no-altstack python test.py I used the argument -run-pass-thru=--no-altstack based on multiple sources to remove an initial error about the stack size being too small

Source 1: http://hpc.ipp.ac.cn/wp-content/uploads/2015/12/documentation_2016/en/vt...

Source 2: https://scc.ustc.edu.cn/zlsc/tc4600/intel/2017.0.098/vtune_amplifier_xe/...

I used amplxe-gui with X11 forwarding to view the results on my local machine (MacOS). However, I can only view the assembly code, as shown in the screenshot below. Can you please help me understand what I must do to view the source code? For some reason, I was not allowed to upload a .py file so simply change the extension to test.py and run with Python 3.7 to reproduce my issue. The file takes ~10 seconds to run. The output displayed at the command line has also been included below. I'm wondering if the warning "amplxe: Warning: Cannot locate debugging information for file ..." is part of the issue. Please let me know how to resolve that.

From reading other forum posts, I found some potential options such as specifying a search path and using Intel’s JIT Profling API, but I am unsure how to implement these or if there is a better/easier way to approach this problem. Thank you for your help.

Hi,

I've tried several times in multiple browsers, but VTune Profiler is not downloading for me.

Best regards,

Stewart

Good day.

I'am new user of Vtunes. My main question is Why Vtunes hasn't it's own ssh client? Do I write understand that I should use Putty as ssh-client, not other application? What should I do if my ssh client is SecureCRT? Where could I read about mechanism of coworking with Vtunes and Putty? Now I has such problem: I have ssh connection with Putty with ssh-key with passphrase. When I type username@host_name, Vtunes answer: "Cannot communicate with target, Please check password-less authentication request". But when I type wrong_username@host_name, Vtunes answer "Server refused our key". Does problem in ssh-key passphrase?

Dear All,

I'm not able to get source code view for NetCore 3.1.100 application. Proof of concept app is compiled with full debug info. PDB and source file location is provided. VTune is launched with admin permissions. I'm trying to follow guidelines from https://devblogs.microsoft.com/dotnet/net-core-source-code-analysis-with... but no matter what options are selected I have no luck getting source code view.

Product versions:

• Inter VTune Amplifier 2019 Update 8
• Visual Studio 2019 16.4.1
• NetCore 3.1.100

VTune is not complaining about missing sources or PDBs (see screen). Can anyone point me in the right direction?

Best Regards & thanks in advance,

Marcin Ostrowski

I want to question about the meaning of -data-limit options.

I'm using the command line interface to profile the application with --data-limit=0 option.

The problem is that, the total size of result directory is too big. I have to measure metrics with different environment many times, but I cannot do it because of the limited storage. In documentation, default data-limit is enough in normal case. But I'm not sure about this because the application I'm profiling is the PyTorch python script training complex CNN models.

In has the data preprocessing, data loading, training(forward & backward), validating(only forward) code. And with default data-limit, the measurement ends too early and I don't think this result represents the overall characteristic of my Python script. Could you provide me any tip about this situation?

+) I have one more question about hardware event-based sampling in the collection mode threading. The elapsed time in this mode is about 20% longer than other mode (hotspots, memory access) Why it happened? And when I writes a report about this analysis, which elapsed time will be meaningful to readers do you think?

amplxe: Error: [Instrumentation Engine]: Pin is out of memory
amplxe: Collection failed.
amplxe: Internal Error

Environment:

• Ubuntu 18.04, both in VirtualBox and bare metal
• vtune_amplifier_2019.6.0.602217
• 128GB system RAM, not remotely close to exhausted

Source Code:

https://github.com/EOSIO/eos

Run

scripts/eosio_build.sh -o RelWithDebInfo

Run

scripts/eosio_install.sh

Run

H=`pwd`
DATE=`which date`
TIMESTAMP=`$DATE +"%Y-%m-%d-%H-%M-%S"`
NODEOS=~/eosio/2.0/bin/nodeos
NVER=`$NODEOS --version`
/opt/intel/vtune_amplifier/bin64/amplxe-cl -c hotspots -app-working-dir=$H -data-limit=2048 -finalization-mode=full \
  -inline-mode=on -mrte-mode=native -target-duration-type=veryshort \
  -r $H/hotspots-$NVER-$TIMESTAMP -- \
  ~/eosio/2.0/bin/nodeos --data-dir "$H/data" --config-dir "$H/config" \
  --wasm-runtime eos-vm --eos-vm-oc-enable --force-all-checks --disable-replay-opts \
  --terminate-at-block 1000 \
  > "$H/stdout.txt" 2> "$H/stderr.txt"

Hi 

I'm trying to profile my OpenCL application on PyOpenCL via Intel VTune profiler. I have Intel HD Graphics 630 installed in my machine. From my understanding, that can serve as a GPU to run my OpenCL computations on. 

I start the profiler via the launch application selection, pointing the profiler to the python script that I am executing. However, in the summary report generated, I noticed that the profiler picks up Nvidia GeForce as the GPU to profile. I have an Nvidia GeForce 1060 graphics card mounted into the system, just that the driver has not yet been installed in the OS. 

I would like to know if it is possible to select the GPU used in the profiling. Attaching a screen shot of the summary page here for debugging. 

Thanks

After capturing perf data using the command:

     /home/tools/intel/vtune_amplifier_2018.1.0.535340/bin64/amplxe-cl -collect hotspots -run-pass-thru=--no-altstack <my binary>

I'm getting:

amplxe: Error: Assertion failed: pytrace_collector710: thread_manager_result == tpss_thread_manager_op_err_ok || thread_manager_result == tpss_thread_manager_op_err_acquired : Cannot acquire tsd for current thread (tid = 42407), result = 8. Please contact the technical support. 
amplxe: Error: Assertion failed: pytrace_collector710: thread_manager_result == tpss_thread_manager_op_err_ok || thread_manager_result == tpss_thread_manager_op_err_acquired : Cannot acquire tsd for current thread (tid = 42412), result = 8. Please contact the technical support. 
amplxe: Error: Assertion failed: pytrace_collector710: thread_manager_result == tpss_thread_manager_op_err_ok || thread_manager_result == tpss_thread_manager_op_err_acquired : Cannot acquire tsd for current thread (tid = 42417), result = 8. Please contact the technical support. 
amplxe: Error: Assertion failed: pytrace_collector710: thread_manager_result == tpss_thread_manager_op_err_ok || thread_manager_result == tpss_thread_manager_op_err_acquired : Cannot acquire tsd for current thread (tid = 42422), result = 8. Please contact the technical support. 
amplxe: Collection stopped.
amplxe: Using result path `/home/scratch.mwoodpatrick_inf/fsa/fsf_trees/Cuda_Test/450489367/output_12_31_19__0434/r000hs'

What do these errors mean? Any suggestions what I'm doing wrong, the report is generated & viewable. I'm still learning my way around the viewer so I'm not sure if they make sense yet but at first glance they don't look unreasonable, is there some documentation that will help me understand what this error means

Operating system and version: CentOS release 6.8 (Final)

Tool version: vtune_amplifier_2018.1.0.535340

Compiler version: gcc-5.4.0

Hello,

During installation of OneAPI beta03 on Ubuntu 18.04, I encountered the failure of loading of vtsspp driver.

I attempted to recompile the vtune drivers. Although the modules can be compiled successfully, but the problem cannot be solved. The output of running ismod-sep is given as below:

$ sudo ./insmod-sep 
Checking for PMU arbitration service (PAX) ... not detected.
Attempting to start PAX service ...
Executing: insmod ./pax/pax-x32_64-5.0.0-37-genericsmp.ko
Setting group ownership of devices to group "vtune" ... done.
Setting file permissions on devices to "660" ... done.
The pax driver has been successfully loaded.
PAX service has been started.
Checking for socperf driver ... not detected.
Executing: insmod ./socperf/src/socperf3-x32_64-5.0.0-37-genericsmp.ko
Setting group ownership of devices to group "vtune" ... done.
Setting file permissions on devices to "660" ... done.
The socperf3 driver has been successfully loaded.
Executing: insmod ./sep5-x32_64-5.0.0-37-genericsmp.ko
Setting group ownership of devices to group "vtune" ... done.
Setting file permissions on devices to "660" ... done.
The sep5 driver has been successfully loaded.
Checking for vtsspp driver ... not detected.
Executing: insmod ./vtsspp/vtsspp-x32_64-5.0.0-37-genericsmp.ko gid=1001 mode=0660
insmod: ERROR: could not insert module ./vtsspp/vtsspp-x32_64-5.0.0-37-genericsmp.ko: Argument list too long

Error:  vtsspp driver failed to load!

You may need to build vtsspp driver for your kernel.
Please see the vtsspp driver README for instructions.

Checking for socwatch driver ... not detected.
Executing: insmod ./socwatch/drivers/socwatch2_10.ko
The socwatch driver has been successfully loaded.

I have already tried to increase the system stack limit to 65536, but the issue cannot be solved.

May anyone advise a solution?

Thank you and Regards,

Amon

Hi,

I am using VTune Profile for tuning my code and getting the following:

Retiring=45.4%, FrontenendBound=30%

The line here performs a modulus operation:

 currentSegmentIndex = marketDataTries%TOTAL_SEG;

Assembly code for this is :

movsxdl  0x238(%rbx), %rcx

xor %edx, %edx

movq  0xe8(%rbx), %rax

div %rcx

movl  %edx, 0x100(%rbx)

Anyone with some suggestions, what optimizations can I try here ?

Thanks and Regards 

Dipanker Singh

Hi,

Software version: Vtune Amplifier 2019 Update 8

As stated in the documentation, Vtune sgx hotspots analysis is deprecated in the GUI and only allowed via the CLI.

Question 1: Does this mean visualizing the result via the GUI is also deprecated? ie: can I collect sgx hotspots data via the CLI and pass the collected analysis data to amplxe-gui to accurately visualize sgx hotspots in the GUI? I tried doing so and could only find the `Hotspots` and `Hotspots by CPU utilization` panes in my GUI which made me question whether it was the right way to visualize the data.

Question 2: If visualization of sgx hotspots is not allowed via the GUI, is there a way to do the same via the command line? From what I have observed the CLI interface also does not allow a `sgx-hotspots` report type.

Thanks,

Anubhav

Hello,

VTune seems to be missing almost all hardware counters on my new Surface Laptop 3 and provides no information beyond what other sampling profilers like Visual Studio or Very Sleepy provide. I am running the recent VTune 2020 (downloaded today) through the standalone GUI interface. The new laptop has an i5-1035G7 processor running windows 10 version 1903 (OS Build 18362.592). Is the new CPU not supported yet? Can I expect it to work with a future update to VTune?

Note that I also have an older laptop that correctly samples HW counters with VTune and supplies information about the bandwidth, bottlenecks, branch mispredictions, etc. Because I can get things working on another machine I'm guessing it isn't a mistake that I am making. The older working laptop is an i7-6700HQ.

Thanks for your time!

Hello,

I realize this message is going to sound absolutely silly...

Visual Studio integration adds VTune at the very-top of per-Project context menu. I've got years of muscle memory right-clicking a Project and clicking Build (normally the 1st item) and this is throwing me off badly to the point where I'm uninstalling the extension because "right now" is not the right time for me to readjust for such commonly used action.

Could the menu item be added anywhere else, or some option (even undocumented) to move it?

Thank you.

I am trying to use Vtune 2020 to profile a python script. However, I am running into two problems. 

1. I am not finding the call stack tab on the right side of Bottom-Up

The example project that comes with Vtune has a view like this.

But I get something like this:

The call stack pane on the right side, which is mentioned in every tutorial, is nowhere to be seen,

The second problem is that I cannot see any Python source code file anywhere.  I set the Managed code profiling mode to Auto.

I am using Python 3.7.1 from Anaconda on Windows 10. 

Any help is appreciated. 

Hello,

I am try using VTune Profiler on FreeBSD target and got next errors:

# /opt/intel/bin64/vtune -collect hotspots -knob sampling-mode=hw /bin/ls
vtune: Warning: On some systems based on the Intel microarchitecture code name Nehalem / Westmere with C-states enabled, this analysis type may cause system hanging due to a known hardware issue (see errata AAJ134 in http://download.intel.com/design/processor/specupdt/320836.pdf). To avoid this situation, disable all "Cn(ACPI Cn) report to OS" BIOS options before sampling with VTune Profiler on such systems.
***ERROR: could not retrieve time stamp!
ERROR: CPU_CLK_UNHALTED.REF_P is not a valid event multiplexing trigger
ERROR: Success
ERROR: Success
ERROR: Success
ERROR: There are no valid events specified - Sampling aborted
Run parameters are not valid - Aborting sampling run ...
Options error
vtune: Error: ***ERROR: could not retrieve time stamp!
ERROR: CPU_CLK_UNHALTED.REF_P is not a valid event multiplexing trigger
ERROR: Success
ERROR: Success
ERROR: Success
ERROR: There are no valid events specified - Sampling aborted
Run parameters are not valid - Aborting sampling run ...
Options error

vtune: Collection failed.
vtune: Internal Error

What is a problem? How to resolve this?

My CPU is Intel(R) Xeon(R) CPU           X5675  @ 3.07GHz (3066.83-MHz K8-class CPU)

# /opt/intel/bin64/sep -platform-info
***ERROR: could not retrieve time stamp!
Sampling Enabling Product version: 5.14  built on Nov 26 2019 11:01:27
SEP User Mode Version: 5.14
SEP Driver Version: 5.14.3
PAX Driver Version: 1.0.2

Copyright(C) 2007-2019 Intel Corporation. All rights reserved.

total_number_of_processors  ...... 12
cpu_family ................ Intel(R) Xeon(R) Processor 980X series code named Westmere
cpu_model ................. 44 (0x2c)
cpu_stepping .............. 2 (0x2)
L1 Data Cache ............. 32KB, 8-way, 64-byte line size
                            2 HW threads share this cache, No SW Init Required
L1 Code Cache ............. 32KB, 4-way, 64-byte line size
                            2 HW threads share this cache, No SW Init Required
L2 Unified Cache .......... 256KB, 8-way, 64-byte line size
                            2 HW threads share this cache, No SW Init Required
L3 Unified Cache .......... 12MB, 16-way, 64-byte line size
                            No SW Init Required
Data TLB0 ................. 4-way, 2M/4M Pages, 32 entries
Data TLB .................. 4-way, 4K Pages, 64 entries
Instruction TLB ........... fully, 2M/4M Pages, 7 entries
Instruction TLB ........... 4-way, 4K Pages, 64 entries
64-byte Prefetching
Shared 2nd Level TLB ...... 4-way, 4K Pages, 512 entries

Device Type ............... Intel(R) Xeon(R) Processor 980X series code named Westmere
EMON Database ............. corei7wdp
number_of_selectors ....... 4
number_of_var_counters .... 4
number_of_fixed_ctrs....... 3
Fixed Counter Events:
counter 0 ................. INST_RETIRED.ANY
counter 1 ................. CPU_CLK_UNHALTED.THREAD
counter 2 ................. CPU_CLK_UNHALTED.REF
number of devices ......... 1
number_of_events .......... 788

Processor Features:
    (Thermal Throttling) (Enabled)
    (Hyper-Threading) (Enabled)
    (Number of Packages:    1)
    (Cores Per Package:    6)
    (Threads Per Package:  12)
    (Threads Per Core:      2)

TSC Freq .................. TBD MHz

CPU Freq (detected) ....... 3067.00 MHz