• The Intel® VTune™ Performance Analyzer cannot recognize module names for applications built with the Intel® Fortran Compiler for Linux* 8.1 using Red Hat* Fedora* Core 2 on IA-32. The work-around for this issue is to use the newer version of the Intel Fortran Compiler for Linux*, version 9.0. [ SCR #24720]

• When performing a remote sampling session for a Java* application, make sure that vtserver is up and running on the remote host before analyzing the collected data. Otherwise, Eclipse may crash when displaying the source view for this Activity results. [SCR# 22141]

• In order for sampling to work on a Linux 2.6 kernel, Oprofile must be enabled in the kernel. Some IA-32 UP kernels, such as those in Red Hat* Red Hat Fedora* Core 2 and Core 3 distributions and in Red Hat* Enterprise Linux* 4.0 do not have Oprofile enabled by default. If you are using such a kernel, we recommend that you use the IA-32 SMP kernel instead since Oprofile is enabled there. The IA-32 SMP kernel is usually provided on the Linux vendor’s install CDs. Once you’re booted into the kernel, you may either use the default sampling driver (if it is available) or build one using the VTune analyzer driver kit. See /opt/intel/vtune/vdk/src/README for details.

• Remote sampling on the Intel® Itanium® 2 processor may fail to collect IA64_INST_RETIRED-THIS event if vtserver is run in verbose mode. Do not run vtserver with -v option as a work-around for the issue. [SCR #23877]

• By default, the duration of data collection is 20 seconds. To change the default duration, use one of the following configuration options:
  • Set the Stop Collection setting in the integrated Eclipse platform environment wizard.
  • Set the duration of the Activity using the vtl activity -d option.
  • Set the default duration using the vtl global-options activity-duration option.

• The Sampling usage model is one user at a time. Multiple users may not configure and run concurrent sampling activities on the same system.

• Interactive console applications can create issues when used with the vtl command. The following conditions should be avoided:
  • Running more than one interactive console application started for the same Activity.
  • Running an interactive console application and selecting the Don't terminate when done collecting option.
  • Running any interactive console application that does not properly clean up terminal settings when terminated by vtl.
  • Running any interactive console application that does not terminate on receipt of SIGTERM.

• If your sampling collection Activity is stuck, check whether there is still space available on the disk where the VTune analyzer project resides. If there is no more space available, the VTune analyzer hangs without notice. You need to clean up some disk space and run your Activity again.

• If you created the project using the integrated Eclipse platform environment, the default location of the project files is in a /workspace subdirectory, located within the directory where you invoked vtlec. [SCR #20136]

• Per CPU buffering in sampling collection has been tested for operation on the following Linux distributions: SuSE* Linux* Enterprise Server (SLES) 9.0 Service Pack 1, SGI Pro Pack* 4.0.

• The number of samples from the application may be less than expected on heavily loaded systems when per CPU buffering is on. For more control over the samples collected, follow the procedure Sampling resolution vs. the VTune analyzer overhead described in the Using per CPU buffering in an Activity Collecting Sampling data section of these Release Notes. [SCR #24910]

• The default kernel that comes with MontaVista Linux Carrier Grade Edition* 3.1 on IA-32 systems has mismatched kernel sources. This results in some symbols not being exported correctly, which in turn causes problems with building VTune analyzer driver kit driver for that kernel. The work-around is for customers to rebuild their kernel and then build a sampling driver for that kernel. The exact steps are described in the following document:
  http://www.intel.com/design/intarch/applnots/305022.htm

• Although this document specifically mentions version 7.2 of the analyzer, the same methodology applies for this version as well. [SCR #24779]

• Eclipse may crash if you have insufficient disk space when you run a sampling activity. Be sure you have sufficient disk space before running your activity, as specified in the disk space requirements section of these Release Notes. [SCR #25239]

• You may not be able to open up sampling results if you do not have sufficient free disk space. Be sure you have sufficient disk space before running your activity, as specified in the disk space requirements section of these Release Notes. [SCR #25240]

• Sampling with BEA JRockit 1.4.2 incurs overhead > 50%. Add the following command line options to the java program to solve the problem. This is not needed for BEA JRockit 5.0. [SCR #22551]

  -Xjvmpi:allocs=off,monitors=off,entryexit=off

• In some cases when a binary is compiled with a high optimization level (-O3) there may be a problem displaying sampling event statistics for inlined functions (SCRs# 23257, 24924). The sum of events in the hotspot view and in the source view may differ. If you use the Intel compiler version 9.0 you should explicitly set the mIPOPT_ninl_debug_info=F compilation option.

• When performing remote data collection on a kernel 2.6.9-based SMP system (for example, Red Hat Enterprise Linux 4.0), if an application is launched by the VTune analyzer , “/bin/bash” may appear in Process View results instead of the application’s name. If the results are opened in Module View, the application’s name should appear and subsequent drilldown to source should work. [SCR #24977]

This applies to:

Intel® VTune™ Performance Analyzer 8.0 for Linux*