beew opened a new issue #18879:
URL: https://github.com/apache/incubator-mxnet/issues/18879


   ## Description
   When trying to create a nd array with the gpu context python appears to hang.
   
   ## To Reproduce
   just create an array
   
   ```
   import mxnet as mx
   
    a = mx.nd.ones((2, 3), mx.gpu())
   
   ```
   
   then it all stops as if it hangs, python was running in the background but 
no output.  Without the gpu context the process is immediate
   
   ## Environment
   
   We recommend using our script for collecting the diagnositc information. Run 
the following command and paste the outputs below:
   ```
   curl --retry 10 -s 
https://raw.githubusercontent.com/dmlc/gluon-nlp/master/tools/diagnose.py | 
python
   
   # paste outputs here
   ```
   ----------Python Info----------
   Version      : 3.7.8
   Compiler     : GCC 5.4.0 20160609
   Build        : ('default', 'Jul 28 2020 15:58:46')
   Arch         : ('64bit', 'ELF')
   ------------Pip Info-----------
   Version      : 20.2.1
   Directory    : /home/bernard/opt/python37/lib/python3.7/site-packages/pip
   ----------MXNet Info-----------
   Version      : 1.7.0
   Directory    : /home/bernard/opt/python37/lib/python3.7/site-packages/mxnet
   ```
   
   This is all I have since the script apparently takes forever to run, may be 
hanging too.
   
   System is Ubuntu Linux
   
   GPU Nvidia GTX 1070
   
   CUDA10.0, libcudnn7.6
   cmake 3.17
   
   mxnet build from source  as follows
   
   ```
   source /opt/intel/bin/compilervars.sh intel64
   
   git clone --recursive https://github.com/apache/incubator-mxnet.git
   
   cd incubator-mxnet && git checkout -b v1.7 origin/v1.7.x
   
   git submodule sync
   
   git submodule update --init --recursive
   
   make -j8 USE_OPENCV=1 USE_BLAS=mkl USE_CUDA=1 USE_CUDA_PATH=/usr/local/cuda 
USE_CUDNN=0 CUDA_ARCH=-gencode=arch=compute_61,code=sm_61 USE_JEMALLOC=1
   
   ```
   
   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to