Message boards : GPUs : Client wont start Getting Stuck at OpenCL
Message board moderation
Author | Message |
---|---|
Send message Joined: 16 Jul 19 Posts: 1 |
The client seems to lockup and never finish starting up after it gets to the OpenCL line in the log. 16-Jul-2019 01:07:01 [---] cc_config.xml not found - using defaults 16-Jul-2019 01:07:01 [---] Starting BOINC client version 7.14.2 for windows_x86_64 16-Jul-2019 01:07:01 [---] log flags: file_xfer, sched_ops, task 16-Jul-2019 01:07:01 [---] Libraries: libcurl/7.47.1 OpenSSL/1.0.2g zlib/1.2.8 16-Jul-2019 01:07:01 [---] Data directory: C:\ProgramData\BOINC 16-Jul-2019 01:07:01 [---] Running under account eric 16-Jul-2019 01:07:01 [---] OpenCL: AMD/ATI GPU 0: Radeon RX 580 Series (driver version 2906.8, device version OpenCL 2.0 AMD-APP (2906.8), 4096MB, 4096MB available, 6295 GFLOPS peak) If I start the boinc.exe app from the command line I see the same output, but after I press CTRL+C a couple of times I can get past this, and stream the startup. After it checks the status of all my tasks ANd it is trying to request its first new data I get an [---] Exiting status and the program terminates. 16-Jul-2019 01:15:20 [---] Read account data file 16-Jul-2019 01:15:20 [---] Doing token lookup RPC to Science United 16-Jul-2019 01:15:20 [---] Using account manager Science United 16-Jul-2019 01:15:21 [---] Account manager login: erenken 16-Jul-2019 01:15:21 [---] Setting up GUI RPC socket 16-Jul-2019 01:15:21 [---] Checking presence of 429 project files 16-Jul-2019 01:15:21 Initialization completed 16-Jul-2019 01:15:21 [---] Running CPU benchmarks 16-Jul-2019 01:15:21 [---] Suspending computation - CPU benchmarks in progress 16-Jul-2019 01:15:21 [World Community Grid] Aborting task MCM1_0152061_0985_1; not started and deadline has passed 16-Jul-2019 01:15:21 [GPUGRID] Sending scheduler request: Requested by project. 16-Jul-2019 01:15:21 [GPUGRID] Requesting new tasks for CPU 16-Jul-2019 01:15:21 [---] Exiting Any help would be appreciated. I haven't been able to run this for a while. I have the latest drivers installed for my RX580. |
Send message Joined: 27 Jun 08 Posts: 641 |
What I see looks ok. I have slightly newer driver (2906.9) but it should make difference. Something else is happening. Bring up the Event Viewer and look for anything suspicious in Applications and also in "System". Was this working before? If you installed as a service that could be a problem. 1 7/22/2019 10:45:10 AM Starting BOINC client version 7.14.2 for windows_x86_64 2 7/22/2019 10:45:10 AM log flags: file_xfer, sched_ops, task 3 7/22/2019 10:45:10 AM Libraries: libcurl/7.47.1 OpenSSL/1.0.2g zlib/1.2.8 4 7/22/2019 10:45:10 AM Data directory: C:\ProgramData\BOINC 5 7/22/2019 10:45:10 AM Running under account JStateson 6 7/22/2019 10:45:11 AM OpenCL: AMD/ATI GPU 0: Radeon RX 580 Series (driver version 2906.9, device version OpenCL 2.0 AMD-APP (2906.9), 8192MB, 8192MB available, 6474 GFLOPS peak) 7 7/22/2019 10:45:11 AM Host name: StatesonFamily 8 7/22/2019 10:45:11 AM Processor: 12 GenuineIntel Intel(R) Xeon(R) CPU X5690 @ 3.47GHz [Family 6 Model 44 Stepping 2] 9 7/22/2019 10:45:11 AM 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 htt tm pni ssse3 cx16 sse4_1 sse4_2 popcnt aes syscall nx lm vmx smx tm2 dca pbe 10 7/22/2019 10:45:11 AM OS: Microsoft Windows 10: Professional x64 Edition, (10.00.18362.00) 11 7/22/2019 10:45:11 AM Memory: 11.99 GB physical, 23.99 GB virtual |
Send message Joined: 30 Aug 19 Posts: 1 |
How you resolved that? Same issue is happening with me. |
Send message Joined: 27 Jun 08 Posts: 641 |
How you resolved that? Same issue is happening with me. never heard back from original poster, be nice to know even if the answer seems "stupid". The saying "the only stupid question is the one that is not asked" can apply to the answer. OTOH the post had been up almost a week maybe they gave up and left. my suggestion was to look in the windows event log for errors. the point where the client got hung up appears to be where it is asking for hardware info which it gets from the OS: 16-Jul-2019 01:07:01 pressing ctrl-c a couple of times could actually cause that exit at 16-Jul-2019 01:15:21 there are debug flags that can provide help but i am not not familiar with how to use them or how to interpret the results. what problem are you yourself seeing? |
Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.