Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid Device Ordinal when CUDA_VISIBLE_DEVICES=1 #54

Closed
natevm opened this issue Jun 6, 2020 · 1 comment
Closed

Invalid Device Ordinal when CUDA_VISIBLE_DEVICES=1 #54

natevm opened this issue Jun 6, 2020 · 1 comment

Comments

@natevm
Copy link
Contributor

natevm commented Jun 6, 2020

Simplest way to reproduce is to run the interactive sample like this: CUDA_VISIBLE_DEVICES=1 ./int01-simpleTriangles . This Invalid Denice Ordinal error occurs in groupBuildAccel in DeviceGroup.cpp

I don't seem to run into the same issue with CUDA_VISIBLE_DEVICES=1 ./sample01-simpleTriangles. However, I do see the above exception with ViSII

@ingowald
Copy link
Contributor

Bug has been root-caused to the display context running on different GPU than OWL; ie, this is not a bug in owl, but in the display/viewer code. Finally (in 1.0.2) fixed in owl's owlViewer helper library (which also fixes it in all owl samples and all owl apps that build on owlViewer), but apps that do their own display and cuda/gl resource sharing code will need their own fixes.

ingowald added a commit that referenced this issue Oct 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants