no, I never solved this problem. It only appeared intermittently. My
only solution was to reboot the machine once a card got "locked up". I
never did find any part of my code that was obviously segfaulting or
causing other offense.
On Wed, Feb 24, 2010 at 10:18 AM, Waldemar Kornewald
Michael Rule <mrule7404@...> writes:
I'm getting this error. My suspicion is that _something_ is
writing to some part of card memory that it shouldn't, in a
way that doesn't immediately cause a
segfault.LaunchError: cuMemcpyDtoH failed: launch timeout
The general behavior is that I can launch my kernel, it will
finish, but I can't get my data back to the host. After doing
this several times the whole card seems to lock up and become
useless.I'll just keep investigating, but I thought I should
put this out there in case someone else sees the same problem.
Did you find out what caused that bug?
I'm getting this every few executions. When I compile the same code
on the CPU in emulation mode and run it everything works flawlessly.
PyCUDA mailing list