ls -alF `which mri_em_register_cuda` says
-rwxrwxr-x 1 6635 160 28831410 2010-08-18 13:56 /opt/medphys/freesurfer/5.0.0-amd64/bin/mri_em_register_cuda*
Adding a time shift of 6 hours (germany) the create time is 07:56 ...
ldd of the binary shows
ldd /opt/medphys/freesurfer/5.0.0-amd64/bin/mri_em_register_cuda linux-vdso.so.1 => (0x00007fff2b5a2000) libcuda.so.1 => /usr/lib/libcuda.so.1 (0x00007f6781e9b000) libcudart.so.3 => /opt/medphys/cuda/cuda-toolkit-current/lib64/libcudart.so.3 (0x00007f6781c68000) libz.so.1 => /lib/libz.so.1 (0x00007f6781a51000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x00007f6781818000) libdl.so.2 => /lib/libdl.so.2 (0x00007f6781614000) libpthread.so.0 => /lib/libpthread.so.0 (0x00007f67813f8000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007f67810e8000) libm.so.6 => /lib/libm.so.6 (0x00007f6780e64000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00007f6780c4d000) libc.so.6 => /lib/libc.so.6 (0x00007f67808dd000) librt.so.1 => /lib/librt.so.1 (0x00007f67806d5000) /lib64/ld-linux-x86-64.so.2 (0x00007f6782883000)
the libcuda.so.1 links to /usr/lib/libcuda.so.256.40 ... which version do you use at the center?
Daniel
Nick Schmansky nicks@nmr.mgh.harvard.edu 23.08.10 20.23 Uhr >>>
is the date on your mri_em_register_cuda 'Aug 18 07:56'?
to see this, type:
ls -alF `which mri_em_register_cuda`
i've just re-downloaded the fscudabins-linux-centos4_x86_64.tgz tarball and tested mri_em_register_cuda on a C1060 we have and it seems to work.
n.
On Mon, 2010-08-23 at 12:42 +0200, Daniel Guellmar wrote:
Hi Nick,
thank you for your quick reply and the explanation. Unfortunately the new binary still do not work. The error message changes now to ..
Acquiring CUDA device Using default device CUDA Error in file 'devicemanagement.cu' on line 46 : invalid argument.
This error occurs on a Tesla C1060 and on Tesla C2050. I haven't tried on regular GPU cards, but will manage to do so in the next days ...
Any ideas, what could be wrong?
Daniel
Nick Schmansky nicks@nmr.mgh.harvard.edu schrieb am 8/20/2010 um
9:55 in Nachricht 1282334139.31414.17.camel@terrier.nmr.mgh.harvard.edu:
CUDA users,
The problem with the _cuda binaries (message: CUDA Error in file 'devicemanagement.cu'...) has been fixed, and new binaries are
available
for download from here:
ftp://surfer.nmr.mgh.harvard.edu/pub/dist/freesurfer/misc/linux-centos4_x86_
64/
download the file 'fscudabins-linux-centos4_x86_64.tgz' and extract
it
(tar zxvf <filename>) into your $FREESURFER_HOME/bin directory.
This
is
for the 64b linux platform only (centos 4 and 5).
fyi, the problem was that the utility UPX, which is run on the
publicly
distributed freesurfer binaries to reduce their size, seemed to
cause
this strange problem.
Let us know how these utilities work. In particular we'd like to
get
a
sense of the type of NVIDIA GPU cards people are using.
Nick
On Thu, 2010-08-19 at 12:57 -0400, Nick Schmansky wrote:
hello cuda beta users! this problem 'all CUDA-capable devices are busy or unavailable.', seems to fall into the category
of
'post-release curse', because i am seeing this problem locally as
well,
but havent seen it in the months we've been using the gpu code. we
have
found rebooting the machine seems to work, but thats not a real solution. i suspect our detection scheme is tripping a flag in the driver thats not getting untripped or cleared the next time around.
when we find a better solution, we'll post new _cuda libs on our
site,
which i'm expecting will be a regular occurrence over the next few months. glad to see so many willing gpu users though!
n.
On Thu, 2010-08-19 at 17:08 +0200, Daniel Guellmar wrote:
Hi folks,
> I'm trying to employ the new cuda binaries, which come with
freesurfer
version 5.0.0, however, if I'm trying to execute a cuda binary
(e.g.
mri_ca_register_cuda) I get the following output:
Acquiring CUDA device Using default device CUDA Error in file 'devicemanagement.cu' on line 46 : all
CUDA-capable
devices are busy or unavailable.
This error occurs on two different systems which are cuda
capable.
Both
systems run with Ubuntu 9.10, both have the latest developer
driver for
linux (256.40) and the latest cuda toolkit (3.1) on it. The GPU Computing SDK code samples compile and work fine. The device
query
on
both hosts work fine ... see following output
Host 1:
CUDA Device Query (Runtime API) version (CUDART static linking)
There are 2 devices supporting CUDA
Device 0: "Tesla C2050" CUDA Driver Version: 3.10 CUDA Runtime Version: 3.10 CUDA Capability Major revision number: 2 CUDA Capability Minor revision number: 0 Total amount of global memory: 2817720320 bytes Number of multiprocessors: 14 Number of cores: 448 Total amount of constant memory: 65536 bytes Total amount of shared memory per block: 49152 bytes Total number of registers available per block: 32768 Warp size: 32 Maximum number of threads per block: 1024 Maximum sizes of each dimension of a block: 1024 x 1024 x 64 Maximum sizes of each dimension of a grid: 65535 x 65535 x
1
Maximum memory pitch: 2147483647 bytes Texture alignment: 512 bytes Clock rate: 1.15 GHz Concurrent copy and execution: Yes Run time limit on kernels: Yes Integrated: No Support host page-locked memory mapping: Yes Compute mode: Default
(multiple
host
threads can use this device simultaneously) Concurrent kernel execution: Yes Device has ECC support enabled: Yes
Device 1: "Tesla C2050" CUDA Driver Version: 3.10 CUDA Runtime Version: 3.10 CUDA Capability Major revision number: 2 CUDA Capability Minor revision number: 0 Total amount of global memory: 2817982464 bytes Number of multiprocessors: 14 Number of cores: 448 Total amount of constant memory: 65536 bytes Total amount of shared memory per block: 49152 bytes Total number of registers available per block: 32768 Warp size: 32 Maximum number of threads per block: 1024 Maximum sizes of each dimension of a block: 1024 x 1024 x 64 Maximum sizes of each dimension of a grid: 65535 x 65535 x
1
Maximum memory pitch: 2147483647 bytes Texture alignment: 512 bytes Clock rate: 1.15 GHz Concurrent copy and execution: Yes Run time limit on kernels: Yes Integrated: No Support host page-locked memory mapping: Yes Compute mode: > >> > threads can use this device simultaneously) Concurrent kernel execution: Yes Device has ECC support enabled: Yes
deviceQuery, CUDA Driver = CUDART, CUDA Driver Version = 3.10,
CUDA
Runtime Version = 3.10, NumDevs = 2, Device = Tesla C2050, Device
=
Tesla C2050
Host 2:
CUDA Device Query (Runtime API) version (CUDART static linking)
There is 1 device supporting CUDA
Device 0: "Tesla C1060" CUDA Driv CUDA Runtime Version: 3.10 CUDA Capability Major revision number: 1 CUDA Capability Minor revision number: 3 Total amount of global memory: 4294770688 bytes Number of multiprocessors: 30 Number of cores: 240 Total amount of constant memory: 65536 bytes Total amount of shared memory per block: 16384 bytes Total number of registers available per block: 16384 Warp size: 32 Maximum number of threads per block: 512 Maximum sizes of each dimension of a block: 512 x 512 x 64 Maximum sizes of each dimension of a grid: 65535 x 65535 x
1
Maximum memory pitch: 2147483647 bytes Texture alignment: 256 bytes Clock rate: 1.30 GHz Concurrent copy and execution: Yes Run time limit on kernels: No Integrated: No Support host page-locked memory mapping: Yes Compute mode: Default
(multiple
host
threads can use this device simultaneously) Concurrent kernel execution: No Device has ECC support enabled: No
deviceQuery, CUDA Driver = CUDART, CUDA Driver Version = 3.10,
CUDA
Runtime Version = 3.10, NumDevs = 1, Device = Tesla C1060
Any comments on that?
Regards and thanks in advance, Daniel
--
Dr.-Ing. Daniel Güllmar Medical Physics Group / IDIR I Jena University Hospital MRT-Gebäude am Steiger Philosophenweg 3 07743 Jena
Tel: +49-3641-9-35373 Fax: +49-3641-9-35081 www: http://ww.mrt.uni-jena.de ____________________ Universitätsklinikum Jena Körperschaft des öffentlichen Rechts und Teilkörperschaft der Friedrich-Schiller-Universität Jena Bachstraße 18, 07743 Jena Verwaltungsratsvorsitzender: Prof. Dr. Thomas Deufel;
Medizinischer
Vorstand: Prof. Dr. Klaus Höffken; Wissenschaftlicher Vorstand: Prof. Dr. Klaus Benndorf;
Kaufmännischer
Vorstand und Sprecher des Klinikumsvorstandes Rudolf Kruse Bankverbindung: Sparkasse Jena; BLZ: 830 530 30; Kto.: 221; Gerichtsstand Jena Steuernummer: 161/144/02978; USt.-IdNr. : DE 150545777 _______________________________________________ Freesurfer mailing list Freesurfer@nmr.mgh.harvard.edu https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
Freesurfer mailing list Freesurfer@nmr.mgh.harvard.edu https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
Universitätsklinikum Jena Körperschaft des öffentlichen Rechts und Teilkörperschaft der Friedrich-Schiller-Universität Jena Bachstraße 18, 07743 Jena Verwaltungsratsvorsitzender: Prof. Dr. Thomas Deufel; Medizinischer Vorstand: Prof. Dr. Klaus Hö> Wissenschaftlicher Vorstand: Prof. Dr. Klaus Benndorf; Kaufmännischer Vorstand und Sprecher des Klinikumsvorstandes Rudolf Kruse Bankverbindung: Sparkasse Jena; BLZ: 830 530 30; Kto.: 221; Gerichtsstand Jena Steuernummer: 161/144/02978; USt.-IdNr. : DE 150545777
____________________ Universitätsklinikum Jena Körperschaft des öffentlichen Rechts und Teilkörperschaft der Friedrich-Schiller-Universität Jena Bachstraße 18, 07743 Jena Verwaltungsratsvorsitzender: Prof. Dr. Thomas Deufel; Medizinischer Vorstand: Prof. Dr. Klaus Höffken; Wissenschaftlicher Vorstand: Prof. Dr. Klaus Benndorf; Kaufmännischer Vorstand und Sprecher des Klinikumsvorstandes Rudolf Kruse Bankverbindung: Sparkasse Jena; BLZ: 830 530 30; Kto.: 221; Gerichtsstand Jena Steuernummer: 161/144/02978; USt.-IdNr. : DE 150545777
freesurfer@nmr.mgh.harvard.edu
-
Daniel Guellmar