Use at your own risk

Message boards : News : Use at your own risk
Message board moderation

To post messages, you must log in.

Previous · 1 . . . 4 · 5 · 6 · 7 · 8 · 9 · 10 . . . 19 · Next

AuthorMessage
Senilix

Send message
Joined: 30 Jul 09
Posts: 4
Credit: 559,529,710
RAC: 3
Message 323 - Posted: 12 May 2018, 21:44:13 UTC - in response to Message 321.  

12.05.2018 23:43:09 | | OpenCL: NVIDIA GPU 0: GeForce GTX 1060 3GB (driver version 391.35, device version OpenCL 1.2 CUDA, 3072MB, 2487MB available, 4111 GFLOPS peak)

12.05.2018 23:36:25 | collatz | update requested by user
12.05.2018 23:36:28 | collatz | sched RPC pending: Requested by user
12.05.2018 23:36:28 | collatz | [sched_op] Starting scheduler request
12.05.2018 23:36:28 | collatz | Sending scheduler request: Requested by user.
12.05.2018 23:36:28 | collatz | Requesting new tasks for NVIDIA GPU
12.05.2018 23:36:28 | collatz | [sched_op] CPU work request: 0.00 seconds; 0.00 devices
12.05.2018 23:36:28 | collatz | [sched_op] Miner ASIC work request: 0.00 seconds; 0.00 devices
12.05.2018 23:36:28 | collatz | [sched_op] NVIDIA GPU work request: 82632.46 seconds; 1.00 devices
12.05.2018 23:36:28 | collatz | [sched_op] Intel GPU work request: 0.00 seconds; 0.00 devices
12.05.2018 23:36:29 | collatz | Scheduler request completed: got 0 new tasks
12.05.2018 23:36:29 | collatz | [sched_op] Server version 711
12.05.2018 23:36:29 | collatz | Project requested delay of 121 seconds
12.05.2018 23:36:29 | collatz | [sched_op] Deferring communication for 00:02:01
12.05.2018 23:36:29 | collatz | [sched_op] Reason: requested by project

I don't think it's a driver issue, as all nVidia GPU users report they are unable to receive work.

Regards
Senilix
ID: 323 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Anthony Ayiomamitis

Send message
Joined: 21 Jan 15
Posts: 13
Credit: 7,340,425,178
RAC: 13,590,959
Message 324 - Posted: 12 May 2018, 23:58:04 UTC

A number of hours ago I updated my driver to the latest version (397.64) and suddenly I also have the same problem and where I cannot download any tasks.

I will sit down tomorrow and reload my previous driver (388.13).
ID: 324 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
BarryAZ

Send message
Joined: 21 Aug 09
Posts: 47
Credit: 30,422,037,797
RAC: 57,168,355
Message 325 - Posted: 13 May 2018, 0:37:06 UTC - in response to Message 324.  
Last modified: 13 May 2018, 0:38:05 UTC

Andy -- it is not a driver issue -- I've plenty of workstations -- none of which updated drivers -- the issue at the moment as far as I can tell is simply that no nvidia work units are being produced.

Alternatively there was another server change on Friday.

So we can wait for Slicker to let us know what's next.

I will note at least one other project reported issues with the latest nvidia driver -- one of the reasons I have not done a driver update.
ID: 325 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Martin Orpen

Send message
Joined: 30 May 17
Posts: 107
Credit: 21,998,068,419
RAC: 42,894,536
Message 326 - Posted: 13 May 2018, 0:50:51 UTC - in response to Message 199.  

I get the same for NVIDIA on reset -- empty data folder... no apps.

Backdated the driver to a November 2017 version, still nothing.
ID: 326 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Slicker
Project administrator

Send message
Joined: 11 Jun 09
Posts: 56
Credit: 933,049,453
RAC: 763,400
Message 327 - Posted: 13 May 2018, 1:08:57 UTC - in response to Message 323.  

12.05.2018 23:43:09 | | OpenCL: NVIDIA GPU 0: GeForce GTX 1060 3GB (driver version 391.35, device version OpenCL 1.2 CUDA, 3072MB, 2487MB available, 4111 GFLOPS peak)

12.05.2018 23:36:25 | collatz | update requested by user
12.05.2018 23:36:28 | collatz | sched RPC pending: Requested by user
12.05.2018 23:36:28 | collatz | [sched_op] Starting scheduler request
12.05.2018 23:36:28 | collatz | Sending scheduler request: Requested by user.
12.05.2018 23:36:28 | collatz | Requesting new tasks for NVIDIA GPU
12.05.2018 23:36:28 | collatz | [sched_op] CPU work request: 0.00 seconds; 0.00 devices
12.05.2018 23:36:28 | collatz | [sched_op] Miner ASIC work request: 0.00 seconds; 0.00 devices
12.05.2018 23:36:28 | collatz | [sched_op] NVIDIA GPU work request: 82632.46 seconds; 1.00 devices
12.05.2018 23:36:28 | collatz | [sched_op] Intel GPU work request: 0.00 seconds; 0.00 devices
12.05.2018 23:36:29 | collatz | Scheduler request completed: got 0 new tasks
12.05.2018 23:36:29 | collatz | [sched_op] Server version 711
12.05.2018 23:36:29 | collatz | Project requested delay of 121 seconds
12.05.2018 23:36:29 | collatz | [sched_op] Deferring communication for 00:02:01
12.05.2018 23:36:29 | collatz | [sched_op] Reason: requested by project

I don't think it's a driver issue, as all nVidia GPU users report they are unable to receive work.

Regards
Senilix


The scheduler log is reporting: "received old code sign key"
Per the BOINC source code:
// if the client has an old code sign public key,
// send it the new one, with a signature based on the old one.
// If they don't have a code sign key, send them one.
// Return false if they have a key we don't recognize
// (in which case we won't send them work).
//

I think the latter is true since it isn't sending any work. Try disconnecting and then re-joining the project and see if that works. That should cause it to get all new info including any code signing keys.
ID: 327 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Slicker
Project administrator

Send message
Joined: 11 Jun 09
Posts: 56
Credit: 933,049,453
RAC: 763,400
Message 328 - Posted: 13 May 2018, 1:22:05 UTC - in response to Message 325.  

the issue at the moment as far as I can tell is simply that no nvidia work units are being produced.


There's actually no such thing. The WUs can be sent to any platform (PC, MAC, Linux) and any plan class (cpu, nvidia gpu, amd gpu (a.k.a. ati) or intel gpu). Note that there are no CUDA workunits as there are no CUDA apps. Only OpenCL. The ATI, Intel, and nVidia apps are the exact same app (just renamed to allow for seperate collatz config files).

I've not seen the "old code signing key" error before so I'm not sure how one goes about fixing it other than to disconnect and then re-connect to the project which should get all new project info including any code signing keys.
ID: 328 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Daniel

Send message
Joined: 29 Oct 10
Posts: 8
Credit: 2,000,378,687
RAC: 292,184
Message 329 - Posted: 13 May 2018, 1:53:08 UTC - in response to Message 328.  
Last modified: 13 May 2018, 1:53:53 UTC

Hi Slicker,

I've just tried disconnecting and re-connecting to the project again but I still don't get any Nvidia GPU tasks ...

13/05/2018 11:47:59 AM | collatz | update requested by user
13/05/2018 11:48:01 AM | collatz | sched RPC pending: Requested by user
13/05/2018 11:48:01 AM | collatz | [sched_op] Starting scheduler request
13/05/2018 11:48:01 AM | collatz | Sending scheduler request: Requested by user.
13/05/2018 11:48:01 AM | collatz | Requesting new tasks for NVIDIA GPU
13/05/2018 11:48:01 AM | collatz | [sched_op] CPU work request: 0.00 seconds; 0.00 devices
13/05/2018 11:48:01 AM | collatz | [sched_op] Miner ASIC work request: 0.00 seconds; 0.00 devices
13/05/2018 11:48:01 AM | collatz | [sched_op] NVIDIA GPU work request: 286864.66 seconds; 3.00 devices
13/05/2018 11:48:01 AM | collatz | [sched_op] Intel GPU work request: 0.00 seconds; 0.00 devices
13/05/2018 11:48:05 AM | collatz | Scheduler request completed: got 0 new tasks
ID: 329 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
BarryAZ

Send message
Joined: 21 Aug 09
Posts: 47
Credit: 30,422,037,797
RAC: 57,168,355
Message 330 - Posted: 13 May 2018, 2:37:05 UTC - in response to Message 327.  
Last modified: 13 May 2018, 2:38:50 UTC

Slicker, seriously -- that is not the issue from what I can see -- on or about 11AM on Friday I stopped receiving new work for any of around 20 NVidia and AMD video workstations.

Nothing was changed on the workstations.

I have, in response to your suggestions done a full disconnect from Collatz and a new connect -- that has not worked.

I think others have reported this.

So I wonder if something at the server side changed on Friday -- if not, perhaps some other factor has interrupted the process of sending units from the server.

But is NOT as a result of user changes -- the problem is far too broadly reported for that to be the case.

5/12/2018 7:31:01 PM | collatz | Detaching from project
5/12/2018 7:31:17 PM | | Fetching configuration file from https://boinc.thesonntags.com/collatz/get_project_config.php
5/12/2018 7:32:03 PM | collatz | Master file download succeeded
5/12/2018 7:32:08 PM | collatz | Sending scheduler request: Project initialization.
5/12/2018 7:32:08 PM | collatz | Requesting new tasks for CPU and NVIDIA GPU
5/12/2018 7:32:10 PM | collatz | Scheduler request completed: got 0 new tasks
5/12/2018 7:32:10 PM | collatz | No tasks sent
ID: 330 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
BarryAZ

Send message
Joined: 21 Aug 09
Posts: 47
Credit: 30,422,037,797
RAC: 57,168,355
Message 331 - Posted: 13 May 2018, 2:51:33 UTC

Slicker note -- I just detatched, and then a full reboot of the computer. I reconfigured on the Collatz site to accept CPU work.

I was able to download CPU work (1 work unit on the reconnect to Collatz) -- but NO Nvidia work units.

I am pretty sure that *something* has changed on the server side -- possibly on Friday morning.
ID: 331 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile nedmanjo
Avatar

Send message
Joined: 7 Feb 16
Posts: 35
Credit: 3,183,984,590
RAC: 2,027
Message 332 - Posted: 13 May 2018, 3:04:14 UTC - in response to Message 330.  

Having same issue as others have reported. No WU's are dropping. Been using the same NVidia driver v391.24, not the recently reported version that had an issue v397.31. For GP's performed a reset, no change, and detached, reattached the project, again no change. GPUGrid has been running since without issue.
ID: 332 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Slicker
Project administrator

Send message
Joined: 11 Jun 09
Posts: 56
Credit: 933,049,453
RAC: 763,400
Message 333 - Posted: 13 May 2018, 3:39:46 UTC

OK guys, you have convinced me that something changed and it may not be on your end. At present, I don't think it was on mine either since I didn't upgrade the BOINC server code or anything else on the server since before Friday. So.... I now need to check if there are any Linus automatic security updates that may have screwed it up and/or anything else. As I said, I've never experienced a "code signing:" error before so I'm not sure what to do to fix it.

I am working on both 1.4 CPU and 1.4 CPU w/ intrinsic apps to reduce any cpu errors on older machines. Results are looking good, but that doesn't help those with GPU issues.
ID: 333 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Gero-T

Send message
Joined: 9 Oct 16
Posts: 9
Credit: 57,231,987,399
RAC: 0
Message 334 - Posted: 13 May 2018, 4:03:55 UTC - in response to Message 333.  

Possibly last microsoft update?
ID: 334 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
BarryAZ

Send message
Joined: 21 Aug 09
Posts: 47
Credit: 30,422,037,797
RAC: 57,168,355
Message 335 - Posted: 13 May 2018, 5:35:40 UTC - in response to Message 333.  

Slicker -- OK - I figure you might be able to figure things out from your side.

For what its worth, my collection of systems runs mostly Windows 7, with one or two Windows 8,1 and one or two Windows 10 systems.

The video cards are a spread on the Nvidea side from GT 750ti to GT 950 to GT 1050 to GT 1050ti

Drivers are a few months old

BOINC version is mostly 7.8.3
ID: 335 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Martin Orpen

Send message
Joined: 30 May 17
Posts: 107
Credit: 21,998,068,419
RAC: 42,894,536
Message 336 - Posted: 13 May 2018, 7:58:39 UTC - in response to Message 330.  

I think the the problem would have started on Thursday. I tried to get the project working on a Windows 10 box about 10pm GMT and it would only do CPU stuff.

Take your time over this one Slicker --give us Mac/NVIDIA users time to catch up ;-)
ID: 336 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Cautilus

Send message
Joined: 29 Jul 14
Posts: 4
Credit: 4,630,342,826
RAC: 16,005
Message 337 - Posted: 13 May 2018, 8:20:13 UTC

Yeah to provide some more details, my two NVIDIA GPUs that aren't receiving work are:

GTX 1080 Ti - Driver Version 391.01 (marked as having OpenCL 1.2 by BOINC), Windows 10 Pro 64-bit
TITAN V - Driver Version 391.35 (marked as having OpenCL 1.2 by BOINC), Windows 7 SP1 64-bit

I have checked on both systems that BOINC is actually requesting work using the sched_ops logs.
ID: 337 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
BarryJ

Send message
Joined: 15 Jul 14
Posts: 7
Credit: 26,457,321,165
RAC: 37,635,740
Message 338 - Posted: 13 May 2018, 11:23:20 UTC - in response to Message 335.  

To add more fuel to the fire -- I have five machines running either W10 pro or 7 pro, with a mix of GTX1080s or 1070s. All GPUs are using Nvidia driver 388.31.

Four machines have stopped getting WUs a few days ago, But one still is! That one is a Win10pro/GTX1080mini box. I need to determine the difference.

Barry
ID: 338 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Anthony Ayiomamitis

Send message
Joined: 21 Jan 15
Posts: 13
Credit: 7,340,425,178
RAC: 13,590,959
Message 339 - Posted: 13 May 2018, 12:27:20 UTC - in response to Message 338.  

To add more fuel to the fire -- I have five machines running either W10 pro or 7 pro, with a mix of GTX1080s or 1070s. All GPUs are using Nvidia driver 388.31.

Four machines have stopped getting WUs a few days ago, But one still is! That one is a Win10pro/GTX1080mini box. I need to determine the difference.

I was fine with 388.31 and until I upgraded to 397.64 and this was with both a GTX 1060 and GTX 1080.
ID: 339 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Martin Orpen

Send message
Joined: 30 May 17
Posts: 107
Credit: 21,998,068,419
RAC: 42,894,536
Message 340 - Posted: 13 May 2018, 12:48:00 UTC

From the logs of my solitary Windows machine that was processing work units on Thursday -- UK BST times

10-May-2018 16:59:16 [collatz] Requesting new tasks for NVIDIA GPU
10-May-2018 16:59:19 [collatz] Scheduler request completed: got 2 new tasks

10-May-2018 18:31:45 [collatz] Requesting new tasks for NVIDIA GPU
10-May-2018 18:31:47 [collatz] Scheduler request completed: got 0 new tasks

So something changed between 5pm and 6.30pm
ID: 340 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Renato

Send message
Joined: 19 Apr 11
Posts: 14
Credit: 4,984,753,129
RAC: 0
Message 341 - Posted: 13 May 2018, 12:52:38 UTC

strange, one PC can still receive WUs, all others do not receive WUs
well, there are other projects.
ID: 341 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Anthony Ayiomamitis

Send message
Joined: 21 Jan 15
Posts: 13
Credit: 7,340,425,178
RAC: 13,590,959
Message 342 - Posted: 13 May 2018, 12:58:24 UTC - in response to Message 339.  
Last modified: 13 May 2018, 12:59:43 UTC

I was fine with 388.31 and until I upgraded to 397.64 and this was with both a GTX 1060 and GTX 1080.

I just loaded 388.31 and the problem still persists. Back to reloading 397.64.
ID: 342 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Previous · 1 . . . 4 · 5 · 6 · 7 · 8 · 9 · 10 . . . 19 · Next

Message boards : News : Use at your own risk


©2019 Jon Sonntag; All rights reserved