-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Segmentation fault when running demo_ivfpq_indexing_gpu #8
Comments
Hi, ldd gpu/test/demo_ivfpq_indexing_gpu Thanks |
Here you are:
|
Looks correct. Could you do a backtrace as well? gdb gpu/test/demo_ivfpq_indexing_gpu then thanks |
unfortunately that command triggers a "ImportError: This package should not be accessible on Python 3. Either you are trying to run from the python-future src folder or your installation of python-future is corrupted." - I might have to recompile gdb from source first. |
You may want to move ~/.gdbinit aside and run /usr/bin/gdb directly to make sure it is not running some exotic startup scripts. |
Clearing my PYTHONPATH variable fixed it - looks like Python 2 and 3 are using the same. Okay, here is the debug trace (I left out the parts where no error occured):
|
Hi, Can you run It will print out a lot of this, which is expected (basically it pops up when we test a CPU pointer to see what address space it lives in):
but I'm interested in anything that is not that. I attempted and failed to repro locally by restricting memory on my GPU to 4 GB, but didn't get anywhere near the limit; this shouldn't be using that much memory anyways. Internally I've only run this on K40, Maxwell Titan X, Maxwell M40 and Pascal P100, so maybe there's something weird with GeForce GTX 970. |
I'm running into a similar issue with a similar setup: Ubuntu 16.04, single GTX 970, nvidia driver version 375.26, cuda 8. I'm able to run the code with Here are the last few lines of the output from
|
Continuing on the prev post. The output of some of the other commands @mdouze mentioned
|
I got same problem, one more problems when i install on AWS g2.x2large instance.
|
Hi |
@mdouze thank you, I got it. With newer GPU, I got them same problem as @Quasimondo and @danielhauagge. |
@ck196 Can you repro this on an AWS instance with a newer GPU? If so, what type of instance (P2?) |
@wickedfoo No, I gave up on AWS instances, I tried newer GPU on my personal computer. |
nvidia Quadro K1200 - same segfault. |
Closing issue now. If similar problems arise, please open a new issue. |
@danielhauagge See here: |
After compiling both the CPU and the GPU version, the CPU test completed successfully, but the GPU test fails with a Segmentation fault when "Adding the vectors to the index". Unfortunately the error message is not very verbose:
I've got a Ubuntu 16.04 system with 2 GeForce GTX 970, both have 4Gb of memory. Any idea what I am doing wrong?
The text was updated successfully, but these errors were encountered: