Closed jaycedowell closed 1 year ago
Hey Jayce,
Could be related this this tale from Matt: "Long story short, this was failing in the hashpipe rawspec thread and the solution was we had to downgrade from cuda 11.8 to 11.7 - thanks to Luigi (who happened to also be traveling here at GB) for pointing out that 11.8 has bugs that would cause CUFFT failures. Once Dave downgraded, we were recording data again."
Not sure what "bugs" are however, but CUDA 11.8 is forsaken...
Interesting.
I was reading some of the CUDA documentation and there is mention of using __launch_bounds()__
to help guide the compiler on not overutilizing registers. I don't know if that will help in this case but it might be worth looking into at some point.
Since we are working on CUDA 12 support trying to fight with 11.8 isn't worth it. If this pops up again then maybe we add a catch to configure
to throw an error if 11.8 is found.
I was testing under CUDA 11.8 and I kept running into a:
This error disappears under CUDA 11.6 and everything acts the way it should.