IzanCatalan opened a new issue, #21179: URL: https://github.com/apache/mxnet/issues/21179
## Description When loading any mxnet (as mx in the picture) function, mx.nd.ones or mx.gpu(0) for example, I get a warning about cudnn mismatch after an error in cublas. This cublas error is solved when instead of executing mx.gpu(0), i execute mx.gpu(). In both cases, GPU is detected. When the error did not appear, I noticed an underutilisation of the GPU. I wonder if this underutilization is due to the mismatching. In that case, is there any solution to eliminate the warning without installing another version of cudnn or cuda? Also, I execute onnxruntime-gp, but it looks like mxnet throws the warning. Thanks! Izan. ## Environment Mxnet-cu112 version 1.9.1 python version 3.8 cuda version 11.2 cudnn version 8.2.1 onnxruntime-gpu version 1.12   -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
