Git Product home page Git Product logo

Comments (6)

kmorel avatar kmorel commented on September 20, 2024

Is there a platform we can have access to to replicate this issue?

from spack.

wspear avatar wspear commented on September 20, 2024

Currently we're testing in a singularity image that provides the spack-installed software. I've pasted the contents of the test log file. We're running other cuda based tests built with this cuda version that are passing without the driver version error.

I'm looking into replication options. Please let me know if there's anything else diagnostic I can provide in the meantime.

Start testing: May 15 20:54 America
----------------------------------------------------------
1/1 Testing: SmokeTestInternal
1/1 Test: SmokeTestInternal
Command: "/home/users/wspear/.spack/test/azy74y34mqyn6rsjvcyhdjaxwlcsxnvd/vtk-m-2.1.0-wmxwujt/smoke_test_build/smoke_test"
Directory: /home/users/wspear/.spack/test/azy74y34mqyn6rsjvcyhdjaxwlcsxnvd/vtk-m-2.1.0-wmxwujt/smoke_test_build
"SmokeTestInternal" start time: May 15 20:54 America
Output:
----------------------------------------------------------
terminate called after throwing an instance of 'vtkm::cont::cuda::ErrorCuda'
  what():  CUDA Error: CUDA driver version is insufficient for CUDA runtime version
Unchecked asynchronous error @ /tmp/root/spack-stage/spack-stage-vtk-m-2.1.0-wmxwujtmduiulmxcalaznuz4cz3pymzv/spack-src/vtkm/cont/cuda/internal/RuntimeDeviceConfigurationCuda.h:40
(Stack trace unavailable)
<end of output>
Test time =   0.19 sec
----------------------------------------------------------
Test Failed.
"SmokeTestInternal" end time: May 15 20:54 America
"SmokeTestInternal" time elapsed: 00:00:00
----------------------------------------------------------

End testing: May 15 20:54 America

from spack.

wspear avatar wspear commented on September 20, 2024

If you have access to a system with a Tesla or newer gpu where you can run singularity, this is the image we used: https://oaciss.nic.uoregon.edu/e4s/images/24.05/e4s-cuda80-x86_64-24.05.sif (Running it with the -e and --nv flags should work). It's over 45gb in size so I understand if that's not an option for you.

This is the procedure that gets to the issue we're seeing over here:

wget https://oaciss.nic.uoregon.edu/e4s/images/24.05/e4s-cuda80-x86_64-24.05.sif
singularity run -e --nv e4s-cuda80-x86_64-24.05.sif
git clone https://github.com/E4S-Project/testsuite.git
cd testsuite/validation_tests/vtk-m-cuda
./run.sh
#to sanity check that cuda works in the container you can do
../cuda
./compile.sh
./run.sh

from spack.

vicentebolea avatar vicentebolea commented on September 20, 2024

I think that the error is that vtk-m only builds with the specified cuda_arch whereas the other app might build for older cuda_archs as well in the same binaries. Can you share the nvidia-smi of the target system?

from spack.

wspear avatar wspear commented on September 20, 2024

Here it is:

Singularity> nvidia-smi 
Thu May 23 05:14:14 2024       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 525.85.12    Driver Version: 525.85.12    CUDA Version: 12.0     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA H100 PCIe    On   | 00000000:25:00.0 Off |                    0 |
| N/A   45C    P0    80W / 310W |    123MiB / 81559MiB |      0%      Default |
|                               |                      |             Disabled |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A      5613      G   /usr/libexec/Xorg                  63MiB |
|    0   N/A  N/A      9552      G   /usr/bin/gnome-shell               59MiB |
+-----------------------------------------------------------------------------+

from spack.

vicentebolea avatar vicentebolea commented on September 20, 2024

The nvidia driver seems to be enough: https://docs.nvidia.com/deploy/cuda-compatibility/index.html

Another thing could be that the process is picking the integrated GPU. is this a jetson type machine?

from spack.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.