topic MKL ERROR: Parameter 1 was incorrect on entry to vsl_VSL_INTERF in Intel® oneAPI Math Kernel Library

MKL ERROR: Parameter 1 was incorrect on entry to vsl_VSL_INTERFACE_NA

Sanhita_Yeolekar — Mon, 25 Jul 2011 13:13:31 GMT

Hi,

I am getting the following error when I use the MKL VSL and print something to a console.

MKL ERROR: Parameter 1 was incorrect on entry to vsl_VSL_INTERFACE_NA

Is there any way to disable this? Read about the xerbla, but not very clear about how to use it.

Can you please guide?

Thanks,

Sanhita

MKL ERROR: Parameter 1 was incorrect on entry to vsl_VSL_INTERF

Gennady_F_Intel — Mon, 25 Jul 2011 15:10:15 GMT

Can you give us the example of the code to check what's going wrong?

MKL ERROR: Parameter 1 was incorrect on entry to vsl_VSL_INTERF

Andrey_N_Intel — Mon, 25 Jul 2011 15:21:02 GMT

Hi Sanhita,
This status returned by the functionindicatesan error in the initialization of Intel MKL VSL function you call in your code. It makes sense to root-cause the reason of this status asits disabling would not help you to continue the computations in the correct way.
Please, provide some hints about this use of the MKL routine (how you call it, which parameters you pass into the function etc);or,as Gennady suggests, please provide the short test case that demonstrates the issue with short description of your environment (OS, CPU, compiler, mode, link line etc).
Thanks,
Andrey

MKL ERROR: Parameter 1 was incorrect on entry to vsl_VSL_INTERF

Sanhita_Yeolekar — Tue, 26 Jul 2011 13:13:39 GMT

Hi Gennady and Andrey,

Thanks for your prompt response. The issue seems to be resolved.

I got to the root of this. I would like to share this.

I was using the function vslSaveStreamF(const VSLStreamStatePtr, const char*) to save the stream state to some user temp file, but the second argument was not set to NULL when there is no file path specified in certain cases. It considered the const char * argument as a bad pointer and hence threw the mentioned error. Basically the error code returned by vslSaveStreamF was -3 which stands for "VSL_RNG_ERROR_BAD_STREAM" which I then found in one of your documentations.

The issue is resolved by checking if the file name is present or not and setting the character pointer to NULL before calling the vslsaveStreamF function of the MKL.

Thanks,

Sanhita