When does cublasInit() return a NOT_INITIALIZED status?

Question

during my cublas initialization, i get an error, i.e. not the wanted CUBLAS_STATUS_SUCCESS.

Checking the returned status, i figured out that the returned status is CUBLAS_STATUS_NOT_INITIALIZED which is not listed as possible returns of that function.

Does anyone have an idea what may have caused that behavior?

Answer 1

The CUBLAS 4.x documentation mentions CUBLAS_STATUS_NOT_INITIALIZED as error code for cublasCreate with the meaning "the CUDA Runtime initialization failed". Can you verify that you have a valid CUDA context?

If so, did you create a valid CUBLAS context? For CUBLAS 3.x and CUBLAS 4.x using the legacy API: did you call cublasInit while there is a CUDA context in the current thread active, and did it return CUBLAS_STATUS_SUCCESS? For CUBLAS 4.x with new API: did you call cublasCreate and did it return CUBLAS_STATUS_SUCCESS? Are you using the handle created when calling cublas..._v2 methods?