Re:Linpack for Windows fails with 'ordinal'

DG3 · ‎09-07-2022

This is for version 2022.0.2 of Linpack:

linpack_xeon64.exe on Windows 10 reports "The ordinal 270 could not be located in the dynamic link library D:\benchmarks_2022.0.2\windows\mkl\benchmarks\linpack\linpack_xeon64.exe".

Linpack 2021.2.0 has the same problem.

Linpack 2021.2.0 worked in December 2021 on the same system.

Probably linpack haven't been able to keep up with Windows 10 updates?

ShanmukhS_Intel · ‎09-09-2022

Hi,

Thank you for posting on Intel Communities. Meanwhile we look into your issue further, Could you please try downloading and using the Linpack available in the latest version of oneAPI for Windows environment.

Best Regards,

Shanmukh.SS

DG3 · ‎09-12-2022

Per

https://www.intel.com/content/www/us/en/download/721394/intel-oneapi-math-kernel-library-onemkl-benchmarks-suite-2022-for-windows.html

I used the latest Linpack available from Intel.

And, by the way, it fails not on one but on both of my computers.

While Linpack worked fine on both of them as recently as December 2021.

I presume that Microsoft changed something in Windows since then, but, effectively, most recent posted version of Intel Linpack doesn't reflect this change and is not compatible with it too. Apparently, it cannot be run on fully updated and current Windows 10.

Regards,

DG

ShanmukhS_Intel · ‎09-23-2022

Hi,

We have tried running the Linpack for Windows using 2022.1.0 version of oneMKL on Windows 10 Enterprise edition and we could see the executable getting executed without any issues..

Could you please let us know your OS environment details?

Best Regards,

Shanmukh.SS

DG3 · ‎09-23-2022

System #1:

Processor	Intel(R) Xeon(R) W-2295 CPU @ 3.00GHz   3.00 GHz
Installed RAM	512 GB (512 GB usable)
System type	64-bit operating system, x64-based processor
===
Edition	Windows 10 Pro
Version	21H2
Installed on	4/30/2021
OS build	19044.2006
Experience	Windows Feature Experience Pack 120.2212.4180.0

System #2:

Processor	Intel(R) Xeon(R) W-2155 CPU @ 3.30GHz   3.31 GHz
Installed RAM	256 GB (256 GB usable)
System type	64-bit operating system, x64-based processor
===
Edition	Windows 10 Pro for Workstations
Version	21H2
Installed on	8/1/2020
OS build	19044.2006
Experience	Windows Feature Experience Pack 120.2212.4180.0

Both have Norton 360 installed.

ShanmukhS_Intel · ‎09-29-2022

Hi,

Could you please try downloading the latest version of oneMKL available and let us know if the issue persists?

Best Regards,

Shanmukh.SS

DG3 · ‎09-29-2022

I debugged a problem and found why it all happened.

Step 1: Install latest oneAPI. (Windows, offline, offline, September 23, 2022)
https://www.intel.com/content/www/us/en/developer/tools/oneapi/base-toolkit-download.html

Step 2: Go to Git Bash and
cd "/c/Program Files (x86)/Intel/oneApi/mkl/2022.2.0/benchmarks/linpack/"
see dependencies of executable:

ldd linpack_xeon64.exe
ntdll.dll => /c/Windows/SYSTEM32/ntdll.dll (0x7ffa30530000)
KERNEL32.DLL => /c/Windows/System32/KERNEL32.DLL (0x7ffa2eb80000)
KERNELBASE.dll => /c/Windows/System32/KERNELBASE.dll (0x7ffa2df00000)
libiomp5md.dll => /c/miniconda3/Library/bin/libiomp5md.dll (0x7ff9cf9a0000)
ucrtbase.dll => /c/Windows/System32/ucrtbase.dll (0x7ffa2e490000)
VCRUNTIME140.dll => /c/Windows/SYSTEM32/VCRUNTIME140.dll (0x7ffa1d800000)

as no path set for oneAPI, path search "falls through" to the next one which has libiomp5md.dll and this is c:\miniconda3. (where mkl was installed as well at some point).

Step 3: looking into runme_xeon64.bat

This code there:
set PATH=..\..\..\redist\intel64\compiler;%PATH%
set PATH=..\..\..\redist\intel64_win\compiler;%PATH%

should set correct directories but given that the path is "C:\Program Files (x86)\Intel\oneAPI\mkl\2022.2.0\benchmarks\linpack" - it cannot and these directories are simply not there.

The correct code for runme_xeon64.bat is:
set PATH=..\..\redist\intel64;%PATH%
set PATH=..\..\..\..\compiler\2022.2.0\windows\redist\intel64_win\compiler;%PATH%

which in terms of Git Bash environment is equal to
export PATH="C:\Program Files (x86)\Intel\oneAPI\mkl\2022.2.0\redist\intel64":"C:\Program Files (x86)\Intel\oneAPI\compiler\2022.2.0\windows\redist\intel64_win\compiler":$PATH

after this command, as _these_ directories DO exist, ldd gives new result:

ldd linpack_xeon64.exe
ntdll.dll => /c/Windows/SYSTEM32/ntdll.dll (0x7ffa30530000)
KERNEL32.DLL => /c/Windows/System32/KERNEL32.DLL (0x7ffa2eb80000)
KERNELBASE.dll => /c/Windows/System32/KERNELBASE.dll (0x7ffa2df00000)
libiomp5md.dll => /c/Program Files (x86)/Intel/oneAPI/compiler/2022.2.0/windows/redist/intel64_win/compiler/libiomp5md.dll (0x7ff9db140000)
ucrtbase.dll => /c/Windows/System32/ucrtbase.dll (0x7ffa2e490000)
VCRUNTIME140.dll => /c/Windows/SYSTEM32/VCRUNTIME140.dll (0x7ffa1d800000)

so batch file, patched in this way, completely works.

Unpatched - doesn't work.

ShanmukhS_Intel · ‎10-05-2022

Hi,

Glad to know that your issue is resolved. If you need any additional information, please post a new question as this thread will no longer be monitored by Intel.

Best Regards,

Shanmukh.SS