I did not, but when I do I get the same error.
-eric
On Mar 12, 2009, at 11:24 AM, Latchesar Ionkov wrote:
I don't think that 0 signals an error when calling futex(...,
FUTEX_WAKE, ...). According to the man page it means that the call
didn't awake any processes that were waiting on that futex.
Did you run strace -f?
Thanks,
Lucho
On Mar 12, 2009, at 10:19 AM, Eric Van Hensbergen wrote:
A bit more detail:
-------------------
strace ./deviceQuery
...
futex(0x3e82c0d350, FUTEX_WAKE, 2147483647) = 0
write(2, "cudaSafeCall() Runtime API error"..., 101cudaSafeCall()
Runtime API error in file <deviceQuery.cu>, line 61 : feature is
not yet implemented.
) = 101
exit_group(-1) = ?
---------------------
Anyone know why futex would be incompatible with xcpu2?
-eric
On Mar 12, 2009, at 11:03 AM, Eric Van Hensbergen wrote:
And while I am at it, anyone use xcpu or xcpu2 with CUDA yet.
When using xcpu2 I'm getting:
% xrx 9.3.61.111 /bin/bash
/deviceQuery
dev count = 1
Querying device = 0
cudaSafeCall() Runtime API error in file <deviceQuery.cu>, line
61 : feature is not yet implemented.
(and it runs fine when run manually on the device)
Not sure what in the namespace is messing with it, debugging now,
but figured I'd post here in case someone has already ran into it.
-eric
