We have encountered an odd behavior.
Software that uses MKL runs on a HP620 E5-1650 (C602 chipset).
It closes the application (TerminateProcess) when run on a HP640 E5-1650v3 (C612 chipset).
We tried the newest MKL DLLs, but the behavior was not changed.
Considered resolved: The E5-1650v2 and the E5-1650v3 require different MKL support files.
链接已复制
Additional details:
Our program is x64 using VisualStudio 2013 to build.
It was shown to TerminateProcess (exit) on two different HP 640 PCs (only two devices of that type were tested), but pass on any HP 620 PCs.
Neil, how can we reproduce this issue? Can you get us the example to check the problem on our side? What version of MKL do you use?
Which MKL's functions do you call into your application?
Gennady Fedorov (Intel) wrote:
Neil, how can we reproduce this issue? Can you get us the example to check the problem on our side? What version of MKL do you use?
Which MKL's functions do you call into your application?
Thank you for your reply. We are eager to hear any suggestions.
Some of these details are third hand information. We use the tuxfamily eigen software version 3.2.2.
Eigen::CholmodSupernodalLLT<Eigen::SparseMatrix<double> > solverA;
solverA.compute(A);
In Eigen::CholmodBase::factorize. it calls SuiteSparse cholmod_factorize_p which is where the debugger says it encounters terminateprocess. Those are currently using MKL 11.2.0.1 versions of DLLs.
This combination has been quite functional and reliable on a good number of HP620 PCs. There are some reports that this combination is successful on some apple MAC hardware. It has failed on the two HP 640 PCs we tried it on. On one of the HP 640 PCs, we performed the debugging. We tried the MKL 11.3.1.1 versions of DLLs (no change in behavior).
Thank You again for looking into this problem.
this is an unknown for that moment with 11.3.1 version of MKL. Could you get isolated case which may help to investigate the problem on our side?
Gennady Fedorov (Intel) wrote:
this is an unknown for that moment with 11.3.1 version of MKL. Could you get isolated case which may help to investigate the problem on our side?
Does it match some known problem on 11.2.0? that we should not be seeing with 11.3.1?
I will try to prepare a simple test case to recreate what we are seeing.