WARNING: This website is obsolete! Please follow this link to get to the new Albert@Home website!
Posts by Alez |
|
1)
Message boards :
Problems and Bug Reports :
AMD card doing intel_gpu tasks
(Message 112741)
Posted 16 Oct 2013 by  Alez
Post: I just tried the exact same on Einstein and there it works, exclude NVIDIA excludes the nVidia 0 and exclude ATI excludes the ATI 0 but allows the intel_gpu to work. |
|
2)
Message boards :
Problems and Bug Reports :
AMD card doing intel_gpu tasks
(Message 112740)
Posted 16 Oct 2013 by Alez
Post: ok, I have the same but not quite the same. The problem is not with the Boinc client I think but the open_cl class part. I have 3 discrete gpu's and the IGPU enabled. To control then I use a cc_config. If I set exclude gpu flag for NVIDIA it will exclude nVidia GPU 0 as it should. However if I exclude gpu ATI it excludes both the ATI GPU 0 and the intel_gpu. It would appear that here both open cl class apps for the different gpu's are being treated as the same. |
|
3)
Message boards :
Problems and Bug Reports :
FGRP application v 1.07 (OPENCL) feedback thread
(Message 112626)
Posted 18 Jun 2013 by Alez
Post: No, nothing changed my side as far as I'm aware. I believe that signal 11 errors are usually memory related ( unlikely as the card in question runs primegrid and gpugrid no problem ), problem with 64bit system running 32 bit apps ( have checked 32 bit libs are still installed ) or bad work units. Am I missing anything obvious ? |
|
4)
Message boards :
Problems and Bug Reports :
FGRP application v 1.07 (OPENCL) feedback thread
(Message 112623)
Posted 18 Jun 2013 by Alez
Post: Recently all the tasks for this app on this computer https://albert.phys.uwm.edu/show_host_detail.php?hostid=6867 have started error-ing after @ 2 sec with an Exit status 11 (0xb). Previously had no problems running. Has anything changed on your side or is the error code reflecting something that has changed on my side ? Have tried resetting the project but again it just throws errors. Everything was fine up until 13/6/13 by which time I had completed a few 100 units, but haven’t managed a single successful unit since. Any ideas I can try ? |
|
5)
Message boards :
Problems and Bug Reports :
Wrong GPU reported in output file.
(Message 112425)
Posted 12 Apr 2013 by Alez
Post: That would explain the zero load on the GTX 650. I wonder if the issue could be compounded by the different device enumerations. For Boinc GTX 660ti is 0, GT610 is 1 and GTX 650 is 2, however as the display is ran from the GT610 then windows would regard that as the primary device. Could this be causing a conflict with the app accessing the windows device listing rather than the Boinc device enumeration ? If it was trying to run on the 610 then I'm actually surprised that the card didn't crash as it's not a very powerful card and the run times on the units ( milkyway) running on the card didn't indicate another project running simultaneously. Also would trying to run on a card already running a different app not cause a lock file error ? or is that only when projects try to use the same slots in the boinc folder ? If Albert was trying to access the GT610 it never actually managed to run on the card.It may have thought it was, but it was never physically running on the card. Let me know if you require me to try the tests app again. Alex |
|
6)
Message boards :
Problems and Bug Reports :
Wrong GPU reported in output file.
(Message 112421)
Posted 11 Apr 2013 by Alez
Post: Hi! The GT 610 is used to run the display plus run milkyway and seti. I use cc_config.xml file to control what runs on which GPU and these are the only two projects running, and truth be told the only 2 projects that it can run. During the tests conducted all GPU's were being used. The split was as follows GTX 660ti - Primegrid GTX 650 - Albert / Einstein GT 610 - Seti / Milkyway. The display is also connected to this GPU I'm running 7.0.60 (x64) boinc under window 7 home premium x64 , SP1 I noticed the failures on the OpenCL apps and have suspended them just now. All the Cuda apps work correctly. |
|
7)
Message boards :
Problems and Bug Reports :
Wrong GPU reported in output file.
(Message 112416)
Posted 10 Apr 2013 by Alez
Post: I noticed on this computer of mine running Albert http://albert.phys.uwm.edu/show_host_detail.php?hostid=6816 that the cuda tasks running ie Binary Radio Pulsar Search v1.33 (BRP4cuda32nv301) example task here http://albert.phys.uwm.edu/result.php?resultid=727451 correctly reports that it is running on a nVidia GTX 650. the openCL tasks however ie. Gamma-ray pulsar search #2 v1.05 (FGRPopencl-nvidia) example task here http://albert.phys.uwm.edu/result.php?resultid=725134 reports that it is running on a nVidia GT 610, which they are not. That card is present in the system but is not used to run Albert, only the GTX 650 is presently doing that work. in the output file it also reports the GT 610 as device 0 whilst in fact device 0 is a nVidia GTX 660ti. The 610 is device 1 and the GTX 650 is device 2 as reported by Boinc. I have also noticed that these units run for a little bit, then seem to stop doing any work with 0% load on the GPU but they keep running and the percentage complete slowly rises. |
This material is based upon work supported by the National Science Foundation (NSF) under Grant PHY-0555655 and by the Max Planck Gesellschaft (MPG). Any opinions, findings, and conclusions or recommendations expressed in this material are those of the investigators and do not necessarily reflect the views of the NSF or the MPG.
Copyright © 2024 Bruce Allen for the LIGO Scientific Collaboration