Manycore Testing Lab – Cloud computing on 32 cores for Academia Bringing students a competitive advantage through access to manycore computing.
See original here:
Intel Manycore Testing Lab
Symptom : When the user ran Call graph to statically instrument EXE or some DLLs, met error message such as ” Error in module ###.dll – Module is an instrumented module ” Cause : Call graph copies (saves) original user’s EXE/DLLs to Call graph’s cache directory first, then put instrumented EXE/ DLLs in their original directories respectively. After doing data collection, copies original modules from cache directory to original directories, and keeps instrumented modules to Call graph’s cache directory. Next time to run Call graph again, user’s modules will not be instrumented (assume that source code are not changed, and don’t rebuild modules), get them from Call graph’s cache to save time.
Read the original here:
Get error message “Module is an instrumented module” when using Call graph data collector
Reference Number: DPD200090099 Version: Intel® MKL 10.2 ( all updates 1,..4) Operating Systems: Windows (64 bit) and Linux (64 bit) Problem Description : If the program contains calls to any function from the VML library (for example vdSub (n, a, b, y) which performs element by element subtraction of vector b from vector a) and it runs on Intel(R) Core(TM)2 Duo CPU E8400 or Intel Core2 Duo T9600 the program causes signal SIGILL, Illegal instruction.
View original post here:
Illegal instruction Intel(R) Core(TM)2 Duo CPU E8400
Version : Intel® MKL 10.* Product : Intel® Math Kernel Library Operating System : All supported OS’s – Microsoft Windows*, Linux* and Mac OS X Problem Description : When iparm[59] is set 1 and – memory required for the task solution is less then MKL_PARDISO_OOC_MAX_CORE_SIZE and – RAM available in the system > = MKL_PARDISO_OOC_MAX_CORE_SIZE PARDISO reports the following message: “=== PARDISO is running in Out-Of-Core mode, because iparam(60)=1 and there is not enough RAM for In-Core ===”.
More:
PARDISO: incorrect behavior in deciding whether to use in-Core or out-of-core (OOC)
Reference Number : DPD200087222 Version : Intel® MKL 10.2 Product : Intel(R) Math Kernel Library (Intel MKL) Operating System : Red Hat Enterprise Linux* 5 Microsoft Windows Problem Description : PARDISO returns the erroneous result or throws an exceptions in the following cases: 1) input matrix type == 11: real and unsymmetric, with multiple right-hand sides ( nhrs > 1 ) and when CGS iteration replaces the computation of LU ( iparm(4) == 31,61) or 2) input matrix’s type == 13: complex and unsymmetric matrix, with one right-hand side (nhrs ==1) and iparm(4) == 31,61 Resolution Status : The problem has been already fixed in the version Intel(R) MKL 10.2 Update 4. [DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site
Here is the original:
PARDISO returns the erroneous results or throws an exception.
Background The Intel® Cluster Checker clean_ipc test module is used to verify that facilities available in the X/Open System Interface (XSI) Inter-Process Communication (IPC) subsystem are not in use. This is a “housekeeping” check used to evaluate that unnecessary IPC facilities are not active and that the cluster is ready for use
See the original post:
How to configure the clean_ipc test module
Reference Number : DPD200083817 Version : Intel® MKL 10.2 Product : Intel® Math Kernerl Library Operating System : Microsoft Windows* Problem Description : When VML function vdCdfNorm from Intel® MKL is given minus zero (-0), it reports wrong answer 1.5 instead of 0.5 Resolution Status : This bug is fixed in Intel® MKL 10.2 update 2 version onwards. [DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers
Here is the original post:
VML vdCdfNorm produces wrong answer at minus zero (-0)
Reference Number : DPD200148269 Version : 11.1 Product : Intel Fortran Compiler Operating System : All Problem Description : A valid pointer assignment to type-bound procedure returning a pointer may fail to compile.
Original post:
error #6678: compiler defect with pointer assignment to a type-bound procedure returning a pointer
Symptom Intel® Cluster Checker hangs during the execution of the mflops_intel_mkl test module on clusters running Penguin Computing* Scyld Clusterware* 5.4. In addition, inactive or zombie processes named dgemm_mflops may be present on the nodes. The dgemm_mflops binary is a DGEMM benchmark optimized with the Intel® Math Kernel library. It is packaged with Intel® Cluster Checker. Debug output provides no other information
Here is the original:
The mflops_intel_mkl test module hangs during execution on Scyld Clusterware 5.4
Reference Number : DPD200149092 Version : v11.1 Product : Intel Fortran Compiler Operating System : All Problem Description : Inheritance in Intel Fortran has the following defect. An extended public type with PRIVATE components cannot be accessed if the parent component is referenced
Read more:
error #6292: compiler defect accessing extended type if parent component is referenced