The first Einstein@home CUDA App for Linux is available for Beta Test at Beta Test Page.
This is a big package to download (26MB), as it contains both applications (S5R5 and ABP1).
We are still new to writing app_info.xml files for CUDA applications. The one contained in this package should allow to run one ABP1 task per CUDA device, occupying a full CPU core for support, and run S5R5 tasks on the remaining CPU cores.
There are no entries for older than the latest App versions 1.06 / 1.07 in the app_info.xml, tasks already assigned to older Apps will error out.
The ABP1 CUDA App has undergone limited testing with a BOINC CC 6.6.36 and a 181.20 NVidia Driver on a Debian Lenny x86 system. We can confirm that the App doesn't crash immediately on such a setup, but not much more. We already ran into some mysteries of the CC scheduler, though.
Again, this is our very first experience with CUDA Applications, please bear with us and don't expect everything to work right away.
Please test and report, and please include important information (like the NVIdia Driver and Core Client version) in your posts.
BM
BM
Copyright © 2024 Einstein@Home. All rights reserved.
First CUDA App for Linux available for Beta Test
)
Hi Bernd,
this is great news!
But will it run on x86_64 (with 32Bit libs installed)?
Michael
Team Linux Users Everywhere
RE: Hi Bernd, this is
)
I think so - it's running on such a machine here.
BM
BM
it's really nice to see the
)
it's really nice to see the progress in CUDA apps development!
unfortunately I couldn't run the applications yet, I got the following error:
[23:04:47][3963][INFO ] Seed for random number generator is 1015765544.
[23:04:47][3963][WARN ] Couldn't allocate 25165824 bytes of CUDA pinned host memory for resampled time series! Trying fallback...
[23:04:47][3963][WARN ] Couldn't allocate 25165832 bytes of CUDA pinned host memory for resampled time series FFT! Trying fallback...
[23:04:47][3963][ERROR] Error allocating CUDA device memory: 25165832 bytes (feature is not yet implemented)
[23:04:47][3963][ERROR] Demodulation failed (error: 3)!
http://einsteinathome.org/task/136044781
http://einsteinathome.org/task/136044303
my system is Ubuntu 9.04 x86_64, Boinc 6.4.5
tried different versions of the drivers - 180.60, 190.16
P.S. Do you plan a release of cuda-able S5R5 application ?
RE: it's really nice to see
)
Thanks for the report. May I ask you what kind of graphics card you are using? (e.g. integrated on motherboard on a regular PCIe board (which model)?
Thanks very much,
Bikeman
EDIT: PS: As Bernd has stated, a CUDA S5R5 app is planned as well, and the beta test of the ABP1 CUDA apps will be extremely useful for this .
Wonderful, a long time of
)
Wonderful, a long time of waiting comes to an end :-D
I tried the app on my main box, Nvidia 8800GTS 512, Ubuntu 9.04 x64, BOINC 6.6.36, Nvidia driver 190.18 from some Ubuntu PPA. The system was so far processing workunits from GPUGRID and latest SETI CUDA apps, no issues...
The work units start, they show 1 second of time, then the progress bar is set to 100%, but the unit remains active. Process monitors show no CPU load nor does the GPU heat up. Somehow the CUDA process is just sitting there and doing nothing...
I can stop them, start another one, switch back to the first unit, they still show the same behaviour and will not start to compute. Though "leave application in memory while suspended/paused" is disabled, the other work units stay alive on the system, their processes don't terminate.
Very strange...
RE: RE: http://einstein.p
)
I have two Nvidia GTX 295 running - 4 GPUs
Hi mat, RE: I have
)
Hi mat,
Are the two cards running in SLI mode? AFAIK, this causes problems when it comes to CUDA but I need to verify that again.
Thanks,
Oliver
Einstein@Home Project
RE: Hi mat, RE: I have
)
Not any longer, when using the newest drivers (according to some threads on the SETI fora, e.g. Nvidia drivers 190.38 and SLI).
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
Hi mat, RE: Not any
)
Hi mat,
Ok, I suppose you have an additional on-board NVIDIA device, right? We also observed problems with early CUDA-supporting BOINC clients, such that they had problems indentifying usable devices. If you want you may try to use the latest Linux client (6.6.36) that can be found here. It'd be very interesting to see if it solves the problem.
Cheers,
Oliver
Einstein@Home Project
RE: RE: Not any longer,
)
"Not any longer" was referring to "Are the two cards running in SLI mode? AFAIK, this causes problems when it comes to CUDA".
I don't have any CUDA-enabled device in my laptop. I only read about it on the SETI boards.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)