Message boards :
Number crunching :
SETI@home v8.22/23 Windows GPU applications support thread
Message board moderation
Previous · 1 · 2 · 3
Author | Message |
---|---|
marmot Send message Joined: 15 May 99 Posts: 144 Credit: 1,220,664 RAC: 0 |
Interesting about that computer TBar linked with 5072 in progress tasks Thankyou for uncovering this information. This laptop got some WU's yesterday that were to be 8.23 but there is no setiathome_8.23_windows_intelx86__opencl_ati_xxx.exe in the project folder to process them. The thing I don't understand is if no work is being done why is the server reporting 4GFLOPS of work?
|
marmot Send message Joined: 15 May 99 Posts: 144 Credit: 1,220,664 RAC: 0 |
So the server isn't sending an 8.23 application but it's sending 8.23 work units. ^ Hence the easiest way to express this is to use the application version as a descriptive adjective in front of the WU and call it an 8.23 WU = a work unit designated to be used by the 8.23 application. The underlying data is just data that can be processed by whatever application that is desired. Yes, I don't understand exactly the mechanism that the data packet is being assigned to CPU/GPU and version application once it's getting to the client but my usage was easily understood and this did turn out to be a server side issue. EDIT: Oh, the revert to an older script probably going to be the heart of the problem. plan_class_spec.xml was reverted |
Graham Thomas Send message Joined: 19 May 99 Posts: 32 Credit: 3,880,875 RAC: 4 |
It's been days since the bulk of the discussion about the missing 8.23 app for ATI GPUs, but I'm still getting several messages each day like this: 11/01/2017 05:17:59 | SETI@home | [error] No app version found for app setiathome_v8 platform windows_intelx86 ver 823 class opencl_ati5_SoG_cat132; discarding 05mr09aa.28271.2526.10.37.36_2 Has the cause of the problem been found, and has anything been done about it? It's not urgent for me - I've got lots of other work units to process - but it may not be good for the project as a whole to have this mismatch. Graham Thomas |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
It's up to Eric now. No response from him still. SETI apps news We're not gonna fight them. We're gonna transcend them. |
Eric Korpela Send message Joined: 3 Apr 99 Posts: 1382 Credit: 54,506,847 RAC: 60 |
I've checked the database entries for the 8.23 versions and everything checks out. My guess at this point is that we've reached some limit on number of app versions that's present in the BOINC code. Looking into it now. @SETIEric@qoto.org (Mastodon) |
Eric Korpela Send message Joined: 3 Apr 99 Posts: 1382 Credit: 54,506,847 RAC: 60 |
I've cleaned up some unused app_versions from the database. Did that fix the problem? @SETIEric@qoto.org (Mastodon) |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
I'm afraid not: 1/11/2017 9:42:50 PM | SETI@home | Sending scheduler request: Requested by user. SETI apps news We're not gonna fight them. We're gonna transcend them. |
Eric Korpela Send message Joined: 3 Apr 99 Posts: 1382 Credit: 54,506,847 RAC: 60 |
I've temporarily disabled those plan classes while I debug the problem. @SETIEric@qoto.org (Mastodon) |
Eric Korpela Send message Joined: 3 Apr 99 Posts: 1382 Credit: 54,506,847 RAC: 60 |
|
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
Can't check with own PC until tomorrow but app statistics look suspicious right now: Windows/x86 8.24 (opencl_ati5_SoG_cat132) 28 Dec 2016, 23:34:07 UTC 342 GigaFLOPS Windows/x86 8.24 (opencl_ati5_SoG_nocal) 28 Dec 2016, 23:34:07 UTC 342 GigaFLOPS Same value has one of 8.22 plan classes. Looks like 342 was initial value and it remains the same. That would mean no real results returned still. Also, wrong date of release. Usually new app version has currrent date, 8.24 both have date of 8.22 release... SETI apps news We're not gonna fight them. We're gonna transcend them. |
Grant (SSSF) Send message Joined: 19 Aug 99 Posts: 13727 Credit: 208,696,464 RAC: 304 |
I notice Windows 8.22 (opencl_ati5_SoG_cat132) & 8.22 (opencl_ati5_SoG_nocal) both have release dates of 13th Jan this year, and 27 & 59GFLOPS respectively for the work done by them. Issue solved? Grant Darwin NT |
ext2097 Send message Joined: 17 Aug 99 Posts: 6 Credit: 50,808,502 RAC: 29 |
My R9 Nano host downloaded 8.22 (opencl_ati5_SoG_nocal) works, but I had to abort those workunits because they were repeating 'postponed' and 'waiting to run'. ERROR: OpenCL kernel/call 'Quering NV device abilities' call failed (-30) in file ..\..\..\src\GPU_lock.cpp near line 417. |
Grant (SSSF) Send message Joined: 19 Aug 99 Posts: 13727 Credit: 208,696,464 RAC: 304 |
My R9 Nano host downloaded 8.22 (opencl_ati5_SoG_nocal) works, but I had to abort those workunits because they were repeating 'postponed' and 'waiting to run'. Something odd going on here, Info: BOINC provided OpenCL device ID used ERROR: OpenCL kernel/call 'Quering NV device abilities' call failed (-30) in file ..\..\..\src\GPU_lock.cpp near line 417. Waiting 30 sec before restart... Did that application run OK on Beta for you? Grant Darwin NT |
Graham Thomas Send message Joined: 19 May 99 Posts: 32 Credit: 3,880,875 RAC: 4 |
I suspect this doesn't add anything significant, but as confirmation I got this message about a few 8.24 units yesterday. For instance: 13/01/2017 18:31:40 | SETI@home | [error] No app version found for app setiathome_v8 platform windows_intelx86 ver 824 class opencl_ati5_SoG_cat132; discarding 26no15ad.9508.20549.11.38.220_0 Looking back, I had similar messages about 8.24 units at around 13.00 and 03.00 yesterday. (All times are UTC in case that's not clear.) Graham Thomas |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
AFAIK R9 Nano is AMD, not NV GPU so app shouldn't ask NV device capabilities. I need first dozen of lines of stderr. WEB result has only 64k of last lines, first are lost. My own Kalindi-based netbook received setiathome_8.22_windows_intelx86__opencl_ati5_SoG.exe (8.22 opencl_ati5_SoG_nocal) app. Seems it started processing OK: Running on device number: 0 So, right binary released under this plan class. Issues with R9 Nano are host config dependend. First lines from stderr still needed for troubleshooting. SETI apps news We're not gonna fight them. We're gonna transcend them. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
This thread happened to be more about deployment process support instead of support of app itself. So I'll ask of locking this thread and start refreshed one. Deployment looks OK now. SETI apps news We're not gonna fight them. We're gonna transcend them. |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.