Posts by Eric B


log in
1) Message boards : Number crunching : vlar running over 21hrs on cpu (Message 1398760)
Posted 383 days ago by Profile Eric B
Just a follow up - using my locally compiled version of boinc 7.0.65 and the 2 executable files:

MBv7_7.05r1848_sse3_linux64 (Seti V7.05)
setiathome_x41g_x86_64-pc-linux-gnu_cuda32 (seti v7.00 cuda32)

has worked fine, I can crunch both CPU MB and NVidia Cuda WU's with no apparent issues.
My OS is OpenSuse 12.3 kernel 3.7.10-1.16-desktop, on a SNB-E 6 Core/HT with Nvidia GTX-460 using the proprietary Nvidia Driver 319.32
I'm posting this info in case any one else has similar problems and could benefit from my resolution.
2) Message boards : Number crunching : vlar running over 21hrs on cpu (Message 1395930)
Posted 390 days ago by Profile Eric B
sorry its taken me so long t reply here. I ended up reformatting and re-installing. It didn’t help, the MB v7 stock app gets stuck. So, i am now running x41g cuda and MBv7_7.05r1848_sse3_linux64 which i just started up about 20 minutes ago. It looks promising, I'm crunching mb v7 cpu and nvidia cuda. I will know more in a day or so.
The root cause of the previously posted problems is something in the stock seti app that just doesn’t sit well with this OpenSuse 12.3 installation.
3) Message boards : Number crunching : vlar running over 21hrs on cpu (Message 1394666)
Posted 393 days ago by Profile Eric B
God idea on ownership, but its all ok. Could it be a library outside of boinc that its using? BTW: I don’t have the ability to run native, so to speak, the change to use a new glibc 2.3.2 or higher really screwed me, its not practical to try to upgrade glibc either, too much depends on it. I have to compile boinc in order to use it. Maybe its related to that somehow. But, is ti boinc? or is it the seti executable? How far back can i go with boinc versions and still run seti v7?
4) Message boards : Number crunching : vlar running over 21hrs on cpu (Message 1394517)
Posted 393 days ago by Profile Eric B
Even with a completely fresh install of boinc, i have issues with cpu mb, They seem to get stuck and make no fwd progress, this happens about every 4 hours or so. If i restart boinc they take off like they should until the next few WU's then I'm back in the same boat, the WU runs but makes no fwd progress at all. When I do restart boinc, i also notice that every WU that was in progress is reset back to 0%. I have another system with the same OS, well, sorta the same. One is OpenSuse 12.1 with 3.1 kernel the other is OpenSuse 12.3 with 3.8 kernel I don’t have trouble on OpenSuse 12.1 for some reason.
5) Message boards : Number crunching : vlar running over 21hrs on cpu (Message 1393478)
Posted 396 days ago by Profile Eric B
I also have need of some instruction on these app_info.xml files. Is it just me or are these an absolute abomination? I don’t see the order there. When i try to run the app_info.xml i ONLY get nvidia work never any cpu work. I tried removing the setiathome_enhanced sections but no change.
Basically i have 2 apps:
setiathome_7.01_x86_64-pc-linux-gnu
setiathome_x41g_x86_64-pc-linux-gnu_cuda32
How do i get a proper app_info.xml written?


<app_info>
<app>
<name>setiathome_v7</name>
</app>
<file_info>
<name>setiathome_7.01_x86_64-pc-linux-gnu</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>701</version_num>
<platform>x86_64-pc-linux-gnu</platform>
<avg_ncpus>1.000000</avg_ncpus>
<max_ncpus>1.000000</max_ncpus>
<file_ref>
<file_name>setiathome_7.01_x86_64-pc-linux-gnu</file_name>
<main_program/>
</file_ref>
</app_version>
<file_info>
<name>setiathome_x41g_x86_64-pc-linux-gnu_cuda32</name>
<executable/>
</file_info>
<file_info>
<name>libcudart.so.3</name>
<executable/>
</file_info>
<file_info>
<name>libcufft.so.3</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
<platform>x86_64-pc-linux-gnu</platform>
<plan_class>cuda32</plan_class>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>1.0</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1.0</count>
</coproc>
<file_ref>
<file_name>setiathome_x41g_x86_64-pc-linux-gnu_cuda32</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libcudart.so.3</file_name>
</file_ref>
<file_ref>
<file_name>libcufft.so.3</file_name>
</file_ref>
</app_version>
</app_info>

6) Message boards : Number crunching : vlar running over 21hrs on cpu (Message 1393471)
Posted 396 days ago by Profile Eric B
Tbar: I ran a bunch of open browser windows, some graphics and a series of cuda apps and watched the remaining free gpu-ram. It never dropped below 600M, so I don't think I am dong anything outside of seti that would cause gpu-ram to get used up, in fact most of the time the computer is just crunching and not much else running.
7) Message boards : Number crunching : vlar running over 21hrs on cpu (Message 1393470)
Posted 396 days ago by Profile Eric B
juan BFB, I think you are on to something there. But I am not sure how to do this as ldd shows it needs the older version. I tried creating links libcudart.so.3 and libcufft.so.3 pointing to to the respective cuda 5.0 libs and setting the LD_LIBRARY_PATH appropriately but it fails. It must examine the links themselves and realize I lied.
Do you know what other linux users are running for their nvidia gpu crunching?


# ldd setiathome_x41g_x86_64-pc-linux-gnu_cuda32
linux-vdso.so.1 (0x00007fffa03fb000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f2b13d79000)
libcudart.so.3 => xxx/libcudart.so.3 (0x00007f2b13b2c000)
libcufft.so.3 => xxx/libcufft.so.3 (0x00007f2b11d76000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f2b11a70000)
libm.so.6 => /lib64/libm.so.6 (0x00007f2b11772000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f2b1155c000)
libc.so.6 => /lib64/libc.so.6 (0x00007f2b111af000)
/lib64/ld-linux-x86-64.so.2 (0x00007f2b13f95000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f2b10fab000)
librt.so.1 => /lib64/librt.so.1 (0x00007f2b10da3000)
# ldd lib*
libcudart.so.3:
linux-vdso.so.1 (0x00007fffd2621000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f3043507000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f30432ea000)
librt.so.1 => /lib64/librt.so.1 (0x00007f30430e2000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f3042ddc000)
libm.so.6 => /lib64/libm.so.6 (0x00007f3042add000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f30428c7000)
libc.so.6 => /lib64/libc.so.6 (0x00007f304251a000)
/lib64/ld-linux-x86-64.so.2 (0x00007f3043982000)
libcufft.so.3:
linux-vdso.so.1 (0x00007fffc5517000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f7092866000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f7092649000)
libcudart.so.3 => xxx/libcudart.so.3 (0x00007f70923fc000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f70920f6000)
libm.so.6 => /lib64/libm.so.6 (0x00007f7091df7000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f7091be1000)
libc.so.6 => /lib64/libc.so.6 (0x00007f7091834000)
/lib64/ld-linux-x86-64.so.2 (0x00007f709484a000)
librt.so.1 => /lib64/librt.so.1 (0x00007f709162b000)


8) Message boards : Number crunching : vlar running over 21hrs on cpu (Message 1393397)
Posted 397 days ago by Profile Eric B
I have compiled the cuda 5 samples and they run ok, maybe i can take the src of one of those as an example and be able to get a free ram figure. If so i can set up a monitor to log some info about what was running and what the free gpu ram was.
9) Message boards : Number crunching : vlar running over 21hrs on cpu (Message 1393365)
Posted 397 days ago by Profile Eric B
I have 4 more (3 ordinary and 1 vlar) WU's that were not showing any percent done or remaining time, i restarted boinc again and they now look proper. I am concerned this is going to be a continuing problem, Is there anything that can be done to avoid it?
10) Message boards : Number crunching : vlar running over 21hrs on cpu (Message 1393057)
Posted 398 days ago by Profile Eric B
My computers are visible now. I do run kde 4 on 2 monitors but that's what I was doing before V7 came out. I just opened up nvidia-settings, if I am reading this right i am only using 226M of the 1024M ram on the card. "Used dedicated memory: 226M" I googled around and found 2 items where they had similar failures but they're old. In those cases it looks like it was due to the gpu app not releasing all its memory and the next did the same, and the next until it finally couldn't support the GPU app. Is there any way to tell if people are already running linux 64 bit and with Seti V7 using nvidia and successfully processing GPU tasks? If that turns out to be the case then i should compare my setup with a successful one, maybe I'm not holding my mouth right
11) Message boards : Number crunching : vlar running over 21hrs on cpu (Message 1393009)
Posted 398 days ago by Profile Eric B
The typical error using "Multibeam x41g Preview, Cuda 3.20" is:

Cuda error 'cudaMalloc((void**) &dev_t_funct_cache' in file 'cuda/cudaAcc_pulsefind.cu' in line 851 : out of memory.
PulseFind Init failed...
setiathome_CUDA: CUDA runtime ERROR in device memory allocation... initiating boinc temporary exit (180 secs)...


08jn09ab.5493.11051.7.12.225
application SETI@home v7
created 9 Jul 2013, 21:41:20 UTC
minimum quorum 2
initial replication 2
max # of error/total/success tasks 5, 10, 5

I see the same task farmed out to Windows using a nvidia on cud22 also failed
I can unhide my computers for awhile if you like
12) Message boards : Number crunching : vlar running over 21hrs on cpu (Message 1392981)
Posted 398 days ago by Profile Eric B
That fixed things, its now showing Percent 1.279% and climbing Elapsed 3:49 Remaining is 2:58:44 - thanks

What about the GPU? Is there a nvidia cuda/openCL program for 64 bit linux? I had a fermi gpu executable which worked great until the switch to V7 but under V7 it creates way to many errors so I removed it
13) Message boards : Number crunching : vlar running over 21hrs on cpu (Message 1392973)
Posted 398 days ago by Profile Eric B
I have a vlar running on a cpu over 21 hours and it still doesn't show any percentage done, "Progress" is still 0.000%. and "Remaining" is "---".
I'm running OpenSuse 12.3 Linux on a 6core/HT 3960 with a Nvidia GTX460/1G (but there isn't a Nvidia GPU program yet for Linux is there)? Boinc is 7.0.65
Is this normal to be running so long?

Here is the pertinent vlar data:

<workunit_header>
<name>22oc08ac.9463.11115.3.12.24.vlar</name>
<group_info>
<tape_info>
<name>22oc08ac</name>
<start_time>2454762.4252491</start_time>
<last_block_time>2454762.4252491</last_block_time>
<last_block_done>11115</last_block_done>
<missed>0</missed>
<tape_quality>0</tape_quality>
<beam>0</beam>
</tape_info>
<name>22oc08ac</name>
<data_desc>
<start_ra>19.116034178315</start_ra>
<start_dec>10.033974364501</start_dec>
<end_ra>19.1160411811</end_ra>
<end_dec>10.034132742991</end_dec>
<true_angle_range>0.0080150689258589</true_angle_range>
<time_recorded>Wed Oct 22 22:12:21 2008</time_recorded>
<time_recorded_jd>2454762.4252479</time_recorded_jd>
<nsamples>1048576</nsamples>
14) Message boards : Number crunching : SNB-E not using all threads as it should (Message 1296822)
Posted 672 days ago by Profile Eric B

Thanks for the tags tip! The [] part kinda threw me for a minute and made me wonder why <tag></tag> didn’t
do anything, then i realized the format was not standard and i would assume it's to prevent attacks.
Yeh post this is better looking now. also i re-wrapped some stuff for easier reading.

> ps aux|grep AK|grep -v grep |wc -l
11
From boinc mgr msgs:
Sun 14 Oct 2012 03:15:10 AM PDT Starting BOINC client version 6.10.58 for x86_64-pc-linux-gnu Sun 14 Oct 2012 03:15:10 AM PDT Config: GUI RPC allowed from: Sun 14 Oct 2012 03:15:10 AM PDT Config: 192.168.1.17 Sun 14 Oct 2012 03:15:10 AM PDT Config: 192.168.1.103 Sun 14 Oct 2012 03:15:10 AM PDT log flags: file_xfer, sched_ops, task Sun 14 Oct 2012 03:15:10 AM PDT Libraries: libcurl/7.18.0 OpenSSL/0.9.8g zlib/1.2.5 c-ares/1.5.1 Sun 14 Oct 2012 03:15:10 AM PDT Data directory: /home/erbenton/BOINC Sun 14 Oct 2012 03:15:10 AM PDT Processor: 12 GenuineIntel Intel(R) Core(TM) i7-3960X CPU @ 3.30GHz [Family 6 Model 45 Stepping 7] Sun 14 Oct 2012 03:15:10 AM PDT Processor: 15.00 MB cache Sun 14 Oct 2012 03:15:10 AM PDT Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni Sun 14 Oct 2012 03:15:10 AM PDT OS: Linux: 3.1.10cstm-1.16-cstm Sun 14 Oct 2012 03:15:10 AM PDT Memory: 15.63 GB physical, 512.00 MB virtual Sun 14 Oct 2012 03:15:10 AM PDT Disk: 52.87 GB total, 19.04 GB free Sun 14 Oct 2012 03:15:10 AM PDT Local time is UTC -7 hours Sun 14 Oct 2012 03:15:10 AM PDT NVIDIA GPU 0: GeForce GTX 460 (driver version unknown, CUDA version 4020, compute capability 2.1, 1024MB, 641 GFLOPS peak) Sun 14 Oct 2012 03:15:10 AM PDT SETI@home Found app_info.xml; using anonymous platform Sun 14 Oct 2012 03:15:10 AM PDT SETI@home URL http://setiathome.berkeley.edu/; Computer ID 4520457; resource share 100 Sun 14 Oct 2012 03:15:10 AM PDT General prefs: from http://milkyway.cs.rpi.edu/milkyway/ (last modified 29-May-2011 00:31:18) Sun 14 Oct 2012 03:15:10 AM PDT Host location: none Sun 14 Oct 2012 03:15:10 AM PDT General prefs: using your defaults Sun 14 Oct 2012 03:15:10 AM PDT Reading preferences override file Sun 14 Oct 2012 03:15:10 AM PDT Preferences: Sun 14 Oct 2012 03:15:10 AM PDT max memory usage when active: 8002.02MB Sun 14 Oct 2012 03:15:10 AM PDT max memory usage when idle: 12803.23MB Sun 14 Oct 2012 03:15:10 AM PDT max disk usage: 4.00GB Sun 14 Oct 2012 03:15:10 AM PDT (to change preferences, visit the web site of an attached project, or select Preferences in the Manager)


Could it be that Milkyway at home entry? i have not been able to figure out how to get fully rid of it.
e.g it never shows in the boinc mgr but its in various files. How do i completely clean that thing out
of there? It seems a likely candidate for trouble in my case so it would be good to clean that out and
see if it clears up the missing instance problem.

I wonder if its safe to just go delete all these references?
>grep milkyway * |less Sun 14 Oct 2012 03:15:10 AM PDT Starting BOINC client version 6.10.58 for x86_64-pc-linux-gnu Sun 14 Oct 2012 03:15:10 AM PDT Config: GUI RPC allowed from: Sun 14 Oct 2012 03:15:10 AM PDT Config: 192.168.1.17 Sun 14 Oct 2012 03:15:10 AM PDT Config: 192.168.1.103 Sun 14 Oct 2012 03:15:10 AM PDT log flags: file_xfer, sched_ops, task Sun 14 Oct 2012 03:15:10 AM PDT Libraries: libcurl/7.18.0 OpenSSL/0.9.8g zlib/1.2.5 c-ares/1.5.1 Sun 14 Oct 2012 03:15:10 AM PDT Data directory: /home/erbenton/BOINC Sun 14 Oct 2012 03:15:10 AM PDT Processor: 12 GenuineIntel Intel(R) Core(TM) i7-3960X CPU @ 3.30GHz [Family 6 Model 45 Stepping 7] Sun 14 Oct 2012 03:15:10 AM PDT Processor: 15.00 MB cache Sun 14 Oct 2012 03:15:10 AM PDT Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni Sun 14 Oct 2012 03:15:10 AM PDT OS: Linux: 3.1.10cstm-1.16-cstm Sun 14 Oct 2012 03:15:10 AM PDT Memory: 15.63 GB physical, 512.00 MB virtual Sun 14 Oct 2012 03:15:10 AM PDT Disk: 52.87 GB total, 19.04 GB free Sun 14 Oct 2012 03:15:10 AM PDT Local time is UTC -7 hours Sun 14 Oct 2012 03:15:10 AM PDT NVIDIA GPU 0: GeForce GTX 460 (driver version unknown, CUDA version 4020, compute capability 2.1, 1024MB, 641 GFLOPS peak) Sun 14 Oct 2012 03:15:10 AM PDT SETI@home Found app_info.xml; using anonymous platform Sun 14 Oct 2012 03:15:10 AM PDT SETI@home URL http://setiathome.berkeley.edu/; Computer ID 4520457; resource share 100 Sun 14 Oct 2012 03:15:10 AM PDT General prefs: from http://milkyway.cs.rpi.edu/milkyway/ (last modified 29-May-2011 00:31:18) Sun 14 Oct 2012 03:15:10 AM PDT Host location: none Sun 14 Oct 2012 03:15:10 AM PDT General prefs: using your defaults Sun 14 Oct 2012 03:15:10 AM PDT Reading preferences override file Sun 14 Oct 2012 03:15:10 AM PDT Preferences: Sun 14 Oct 2012 03:15:10 AM PDT max memory usage when active: 8002.02MB Sun 14 Oct 2012 03:15:10 AM PDT max memory usage when idle: 12803.23MB Sun 14 Oct 2012 03:15:10 AM PDT max disk usage: 4.00GB Sun 14 Oct 2012 03:15:10 AM PDT (to change preferences, visit the web site of an attached project, or select Preferences in the Manager)


15) Message boards : Number crunching : SNB-E not using all threads as it should (Message 1296785)
Posted 672 days ago by Profile Eric B
oh, i missed answering one of your questions - yeh i have plenty of cpu and gpu tasks on both machines, according to the boinc manager anyway (hand counted well over 25 each of cpu and gpu bfore i stopped counting). I wrote a script to track some things and while i dont claim its 100% accurate (the estimates of "available" work are only estimates based on what i see as how the average work progresses so they could be off a bit, but its darn close) here is its output. My stats come from analyzing the client_state.xml file and deducing what things meant by looking the boinc manager for clues, eg. find WU xx_yy and see what its state was in the manager then go find it in client_state.xml and see what i could learn. I think I have the id's of most of the states pretty well nailed down. There are actually 2 other states i haven’t worked into my script yet and they are called "active_task_states" : state 0 "started but currently suspended" and state 1 "actually executing" and I'm always on the hunt for more info i can ferret out of that file and add to my script.
I do network upload/downloads once a day and run this script via cron about 5 minutes before that, I'm watching for errors and so forth because i find if you try to do 3 cuda tasks you start to see some errors, maybe 7 out of 50 completed fermi tasks or so, could just be the fermi SW as its the only linux fermi app out there that i know of anyway)


./boinc_stats.sh

Current BOINC info Thu Oct 18 20:06:50 PDT 2012
Active Tasks: sys1 13 sys2 12
Position by Avg Credit: 118 Position In USA: 78
RAC: 65,852.15 Position Based on Total Cedit: 180
sys1 Computation Errors MB: 0 CUDA: 0 Freq msr: 0x2600 Act: 3.8 GHz
sys2 Computation Errors MB: 0 CUDA: 0 Freq msr: 0x2900 Act: 4.1 GHz

CUDA CUDA MB MB MB
Total CUDA MB MB Ready CUDA Rdy Ready to Uploads Ready to Uploads Downloads Available Available Average
System WUs WUs WUs to Start to Start Report Pending Report Pending Pending CUDA Work MB Work Credit
------------------------------------------------------------------------------------------------------------------------------
sys1 1966 677 668 507 489 1 97 1 138 0 3.7 days 5.0 days 27154
sys2 1962 1397 574 443 1261 10 13 42 84 0 4.1 days 10.1 days 15541
------------------------------------------------------------------------------------------------------------------------------


sys1 is the 16 thread snb and snb2 is the quad core HT system
sorry for the formatting, there doesn’t seem to be a way to get the script output to space out properly. You can try to copy and paste it into an editor with fixed spacing and it should be more readable
16) Message boards : Number crunching : SNB-E not using all threads as it should (Message 1296772)
Posted 672 days ago by Profile Eric B
I did find that the SNB-E has this cc_config.xml file in the BOINC/projects directory (but its named cc_config.xml.off) which i assume means it wont be read and there is no corresponding file in the the other system. Other than that both are set to use 100% processors and at most use xx processors is set at 192 due to there are a few rare occasions i can get to play with a very big server and 192 more than covers the number of threads that thing has.
I checked these settings on website and also on he manager preferences menu,

Cold this be causing the problem even tho its name is cc_config.xml.off?
Is there any config file in ~/BOINC i can examine to help determine why it only runs 11 cpu tasks? All threads seem fully occupied if i go by the gkrellm display
cat ~/BOINC/cc_config.xml.off
<cc_config>
<log_flags>
<cpu_sched>1</cpu_sched>
<debt_debug>1</debt_debug>
<cpu_sched_debug>1</cpu_sched_debug>
<coproc_debug>1</coproc_debug>
<cpu_sched>1</cpu_sched>
<file_xfer>0</file_xfer>
<file_xfer_debug>0</file_xfer_debug>
<app_msg_send>1</app_msg_send>
<app_msg_receive>1</app_msg_receive>
<unparsed_xml>1</unparsed_xml>
<work_fetch_debug>1</work_fetch_debug>
</log_flags>
</cc_config>
17) Message boards : Number crunching : SNB-E not using all threads as it should (Message 1296597)
Posted 673 days ago by Profile Eric B
I have 2 OpenSuse 12.1 x64 Linux systems: a 4 Core-HT Sandy Bridge system with a Nvidia GTX460, and 8G DRAM - on that system the total is 14 boinc threads - 8 cpu and 2 gpu. OK, thats great and what i would expect.
I also have an SNB-E system which is 6 core HT (12 threads) and it also has an Nidia GTX460, but 16G DRAM. On that system i get only 11 cpu and 2 cuda tasks running at a time.

Both systems are using seti boinc version 6.10.58

The app_info.xml is virtually identical on both systems. and both are using Alex's AK_V* optimized linux fermi apps

e.g the SNB-E system:
cat ~/BOINC/projects/setiathome.berkeley.edu/app_info.xml
<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_V8_linux64_ssse3</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<file_ref>
<file_name>AK_V8_linux64_ssse3</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>setiathome-6.11.x86_64-pc-linux-gnu__cuda32</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>611</version_num>
<plan_class>cuda_fermi</plan_class>
<avg_ncpus>0.250</avg_ncpus>
<max_ncpus>0.50</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.50</count>
</coproc>
<file_ref>
<file_name>setiathome-6.11.x86_64-pc-linux-gnu__cuda32</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>
ldd AK_V8_linux64_ssse3
linux-vdso.so.1 => (0x00007fff563aa000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fa3a5570000)
libc.so.6 => /lib64/libc.so.6 (0x00007fa3a51e0000)
/lib64/ld-linux-x86-64.so.2 (0x00007fa3a578d000)
libm.so.6 => /lib64/libm.so.6 (0x00007fa3a4f89000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fa3a4d73000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fa3a4b6f000)
locate libcuda:
BOINC/projects/setiathome.berkeley.edu/libcudart.so.3

/usr/lib/libcuda.so
/usr/lib/libcuda.so.1
/usr/lib/libcuda.so.304.43
/usr/lib64/libcuda.so
/usr/lib64/libcuda.so.1
/usr/lib64/libcuda.so.304.43
/usr/local/cuda/lib/libcudart.so
/usr/local/cuda/lib/libcudart.so.4
/usr/local/cuda/lib/libcudart.so.4.1.28
/usr/local/cuda/lib64/libcudart.so
/usr/local/cuda/lib64/libcudart.so.4
/usr/local/cuda/lib64/libcudart.so.4.1.28



And on the 8 thread SNB system it looks like this:

cat ~/BOINC/projects/setiathome.berkeley.edu/app_info.xml
<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_V8_linux64_ssse3</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<file_ref>
<file_name>AK_V8_linux64_ssse3</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>setiathome-6.11.x86_64-pc-linux-gnu__cuda32</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>611</version_num>
<plan_class>cuda_fermi</plan_class>
<avg_ncpus>0.250</avg_ncpus>
<max_ncpus>0.50</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.50</count>
</coproc>
<file_ref>
<file_name>setiathome-6.11.x86_64-pc-linux-gnu__cuda32</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>
and:
ldd AK_V8_linux64_ssse3
linux-vdso.so.1 => (0x00007fff129c6000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007feb1d660000)
libc.so.6 => /lib64/libc.so.6 (0x00007feb1d2d0000)
/lib64/ld-linux-x86-64.so.2 (0x00007feb1d87d000)
libm.so.6 => /lib64/libm.so.6 (0x00007feb1d079000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007feb1ce63000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007feb1cc5f000)
libcuda seeems to be 4.1.28
BOINC/projects/setiathome.berkeley.edu/libcudart.so.3
usr/lib/libcuda.so
/usr/lib/libcuda.so.1
/usr/lib/libcuda.so.304.43
/usr/lib64/libcuda.so
/usr/lib64/libcuda.so.1
/usr/lib64/libcuda.so.304.43
/usr/local/cuda/lib/libcudart.so
/usr/local/cuda/lib/libcudart.so.4
/usr/local/cuda/lib/libcudart.so.4.1.28
/usr/local/cuda/lib64/libcudart.so
/usr/local/cuda/lib64/libcudart.so.4
/usr/local/cuda/lib64/libcudart.so.4.1.28
18) Questions and Answers : Unix/Linux : boinc 6.10.17 requests CUDA tasks but cant get any (Message 976575)
Posted 1629 days ago by Profile Eric B
The problem was in app_info.xml, and contributing to the confusion were the very misleading behavior/error messages from BOINC, they are almost meaningless. it wasnt calling for gpu & cpu apps to run, now I have setiathome-CUDA-6.08.x86_64-pc-linux-gnu running the CUDA stuff and AK_V8_linux64_ssse3 running Seti MB. The app_info.xml below works. anyone know where the app_info.xml is documented? I'd like to understand why the file_info information has to be repeated in the app_name section. I can think of a much simpler format, anyway, I'm running.


app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_V8_linux64_ssse3</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<file_ref>
<file_name>AK_V8_linux64_ssse3</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>setiathome-CUDA-6.08.x86_64-pc-linux-gnu</name>
<executable/>
</file_info>
<file_info>
<name>libcudart.so.2</name>
<executable/>
</file_info>
<file_info>
<name>libcufft.so.2</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<plan_class>cuda</plan_class>
<avg_ncpus>0.350000</avg_ncpus>
<max_ncpus>0.350000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>setiathome-CUDA-6.08.x86_64-pc-linux-gnu</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libcudart.so.2</file_name>
</file_ref>
<file_ref>
<file_name>libcufft.so.2</file_name>
</file_ref>
</app_version>
</app_info>
[/code]
19) Questions and Answers : Unix/Linux : boinc 6.10.17 requests CUDA tasks but cant get any (Message 976309)
Posted 1630 days ago by Profile Eric B
I installed crunch3r's app and now CUDA is processing happily away.
HOWEVER. . . on first boinc run all my WU's got discarded. Boinc downloaded
some cuda work and has been trying to get CPU work now for awhile, but like
before with CUDA, now the CPU cant ever get work.
Here's some selected output:

Sat 06 Mar 2010 11:46:02 AM PST SETI@home Sending scheduler request: To fetch work.
Sat 06 Mar 2010 11:46:02 AM PST SETI@home Requesting new tasks for CPU
Sat 06 Mar 2010 11:46:07 AM PST SETI@home Scheduler request completed: got 0 new tasks
Sat 06 Mar 2010 11:46:07 AM PST SETI@home Message from server: No work sent
Sat 06 Mar 2010 11:47:22 AM PST SETI@home Sending scheduler request: To fetch work.
Sat 06 Mar 2010 11:47:22 AM PST SETI@home Requesting new tasks for CPU
Sat 06 Mar 2010 11:47:25 AM PST Project communication failed: attempting access to reference site
Sat 06 Mar 2010 11:47:27 AM PST SETI@home Scheduler request failed: Server returned nothing (no headers, no data)
Sat 06 Mar 2010 11:47:31 AM PST Internet access OK - project servers may be temporarily down.
Sat 06 Mar 2010 11:48:27 AM PST SETI@home Sending scheduler request: To fetch work.
Sat 06 Mar 2010 11:48:27 AM PST SETI@home Requesting new tasks for CPU
Sat 06 Mar 2010 11:48:30 AM PST Project communication failed: attempting access to reference site
Sat 06 Mar 2010 11:48:32 AM PST SETI@home Scheduler request failed: Server returned nothing (no headers, no data)
Sat 06 Mar 2010 11:48:36 AM PST Internet access OK - project servers may be temporarily down.
Sat 06 Mar 2010 11:49:32 AM PST SETI@home Sending scheduler request: To fetch work.
Sat 06 Mar 2010 11:49:32 AM PST SETI@home Requesting new tasks for CPU
Sat 06 Mar 2010 11:49:37 AM PST SETI@home Scheduler request completed: got 0 new tasks
Sat 06 Mar 2010 11:49:37 AM PST SETI@home Message from server: No work sent
20) Questions and Answers : Unix/Linux : boinc 6.10.17 requests CUDA tasks but cant get any (Message 976136)
Posted 1630 days ago by Profile Eric B
I installed boinc yesterday on a newly built system. Boinc seems to recognize my nvidia card is cuda capable, it even requests CUDA tasks but i never get any. Its been trying for the last 20 hours.
I do get regular seti MB tasks ok
I'm running mandriva 64 bit 2010 with a slightly modified kernel.
This fresh boinc install shows:
~/BOINC >file libcudart.so
libcudart.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, stripped

and from the Messages tab i see:

Thu 04 Mar 2010 11:30:53 PM PST OS: Linux: 2.6.31.12-1mnbX
Thu 04 Mar 2010 11:30:53 PM PST Memory: 3.87 GB physical, 0 bytes virtual
Thu 04 Mar 2010 11:30:53 PM PST Disk: 70.33 GB total, 59.15 GB free
Thu 04 Mar 2010 11:30:53 PM PST Local time is UTC -8 hours
Thu 04 Mar 2010 11:30:53 PM PST NVIDIA GPU 0: GeForce GT 220 (driver version unknown, CUDA version 2030, compute capability 1.2, 1024MB, 131 GFLOPS peak)

[snip]

Fri 05 Mar 2010 07:14:04 PM PST SETI@home Requesting new tasks for GPU
Fri 05 Mar 2010 07:14:09 PM PST SETI@home Scheduler request completed: got 0 new tasks
Fri 05 Mar 2010 07:14:09 PM PST SETI@home Message from server: No work sent

I'm running this nvidia driver;
NVIDIA-Linux-x86_64-190.53-pkg2.run


Next 20

Copyright © 2014 University of California