Posts by Ian&Steve C.

1) Message boards : Number crunching : Nvidia Tesla P100 Problems (Message 9781)
Posted 19 Mar 2024 by Ian&Steve C.

your cuda100 app P100s are now failing with this:

./mfaktc.exe: error while loading shared libraries: libcudart.so.10.1: cannot open shared object file: No such file or directory

maybe you removed the cuda toolkit?

2) Message boards : Number crunching : Nvidia Tesla P100 Problems (Message 9771)
Posted 18 Mar 2024 by Ian&Steve C.

you need to add support for every cc level explicitly.

the whole section would be something like this:

--generate-code arch=compute_50,code=sm_50 --generate-code arch=compute_52,code=sm_52 --generate-code arch=compute_60,code=sm_60 --generate-code arch=compute_61,code=sm_61 --generate-code arch=compute_70,code=sm_70 --generate-code arch=compute_75,code=sm_75 --generate-code arch=compute_72,code=sm_72 --generate-code arch=compute_80,code=sm_80 --generate-code arch=compute_86,code=sm_86 --generate-code arch=compute_89,code=sm_89

plus whatever other flags you have there

3) Message boards : Number crunching : Nvidia Tesla P100 Problems (Message 9769)
Posted 18 Mar 2024 by Ian&Steve C.

was v31 compiled with explicit support for CC_6.0 in the NVCCFLAGS section of your makefile or build script?

the argument should be something similar to this:

--generate-code arch=compute_60,code=sm_60

this was what I was suggesting when I mentioned recompiling it to add 6.0 support.

4) Message boards : Number crunching : Nvidia Tesla P100 Problems (Message 9752)
Posted 14 Mar 2024 by Ian&Steve C.

there also appears to be a problem with the cuda100 package.

the mfaktc-linux64-v10.zip contains Windows files (mfaktc.exe and .ini files). it should contain linux binaries and the cuda10 libcudart.so.10 shared object libraries like the cuda11 package does.

the libcudart.so.10 file you can find in FAQs. If the app was dynamically compiled you dont need them in package. The .exe in linux was also compiled so but running under linux. The .ini file is fixed.

when I run ldd mfaktc.exe on the binary it says libcudart.so.10.1 is missing.

in your cuda111 and cuda120 packages you include this file.

I see nothing in the FAQ that references this file. can you link to it? Is your intended workaround for this to create a symlink from libcudart.so.10->libcudart.so.10.1 ?

5) Message boards : Number crunching : Nvidia Tesla P100 Problems (Message 9750)
Posted 14 Mar 2024 by Ian&Steve C.

there also appears to be a problem with the cuda100 package.

the mfaktc-linux64-v10.zip contains Windows files (mfaktc.exe and .ini files). it should contain linux binaries and the cuda10 libcudart.so.10 shared object libraries like the cuda11 package does.

6) Message boards : Number crunching : Nvidia Tesla P100 Problems (Message 9748)
Posted 14 Mar 2024 by Ian&Steve C.

cuda 12+ still supports CC 6.0 devices. why not just recompile the cuda120 app with CC 6.0 support?

otherwise, the only real solution is to transition to Anonymous Platform, and force the cuda100 app to run on everything with an app_info.xml file.

cuda12 app support cc6.1, see 1070ti I dont know why the Tesla doesnt run cuda120 WUs, anonymous patform is not allowed.

i know your app supports 6.1. but CUDA 12 from nvidia still supports down to CC 5.0

I'm saying you should recompile it to add support for 6.0 also. Tesla P100 has CC level 6.0.

6.1 is used on the mainstream pascal GPUs (GTX 10-series, Quadro P-series)

7) Message boards : Number crunching : Nvidia Tesla P100 Problems (Message 9746)
Posted 14 Mar 2024 by Ian&Steve C.

cuda 12+ still supports CC 6.0 devices. why not just recompile the cuda120 app with CC 6.0 support?

otherwise, the only real solution is to transition to Anonymous Platform, and force the cuda100 app to run on everything with an app_info.xml file.