I’m finding that the histogram256 code in the SDK tends to cause an “unspecified launch failure” in the histogram256Kernel if the data all tends to fall in the same few bins. This is easy to replicate by simply replacing the random initialization of data with setting it to a constant value. This is happening on a GPU with compute capability 1.0 (no shared memory atomics). Often this error points to an out of bounds memory access but I’ve run it through valgrind using device emulation with no errors. Anyone else observed this or have ideas on what might be wrong?
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
Unspecified Launch error with histogram256 Unspecified launch error occurs in histogram256 sample. | 0 | 4886 | December 18, 2008 | |
8800 code fails on GTX 260 changes from cc 1.0 to 1.3? | 3 | 4730 | August 27, 2008 | |
unspecified launch failure What additional info about this error available? | 3 | 1178 | November 19, 2009 | |
histogram256 and cudaErrorUnknown | 4 | 5295 | August 27, 2010 | |
unspecified launch failure kernel fails sometimes not everytime | 6 | 6069 | February 2, 2010 | |
unspecified launch failure | 1 | 2216 | May 20, 2009 | |
"Unspecified Launch Failure" Error CUDA and GLSL issues | 0 | 2920 | February 27, 2008 | |
histogram algorithm problems with the SDK example | 7 | 20819 | November 3, 2010 | |
Random "Unspecified launch Failure" | 1 | 2435 | April 28, 2010 | |
Random Launch Failure | 2 | 1241 | March 1, 2010 |