When corrupted results get validated...

[Richard Haselgrove]

Thanks. I've now set it to run live on the main project - host 2901600. No problem fetching work - just a shortlist for the moment, because (a) I run a short cache, and (b) DCF hasn't settled yet - still estimating three hours!

All those pseudo -9s that we started this thread with will have driven DCF way low. I think we may have encountered another of BOINC's safety features - IIRC BOINC cuts down on work fetch if DCF ever gets into 'insane' territory, either high or low. There's a lot of very sound engineering practice in the original BOINC design, but I fear we're in danger of losing it with all these hurried, on-the-fly, bodges to cope with evovling technologies like GPUs.

[Raistmer]

Yeah, life too fast to properly think about it, BOINC not escaped this But some block with fast reaction time to stop invalid overflows would be good thing IMO.
They damage project in too many ways.

[Richard Haselgrove]

Already got a wingmate to add to Claggy's list:

Pieter hostid=5431046 NVIDIA GeForce 9800 GT (1005MB) driver: 19745

Host created today, downloaded 564 tasks, got two of them to validate at 0.01 credits, I'm too depressed to look-see how many pages-full he's wasted.

[Josef W. Segur]

Already got a wingmate to add to Claggy's list:

Pieter hostid=5431046 NVIDIA GeForce 9800 GT (1005MB) driver: 19745

Host created today, downloaded 564 tasks, got two of them to validate at 0.01 credits, I'm too depressed to look-see how many pages-full he's wasted.

220 pending, 2 validated, all teensie claims.

One of the two "valid" is good evidence, text captures attached as WU619984348.7z, also attaching text captures for paired 4xx case noted by Sutaru as WU619465291.7z.
                                                                                    Joe

[Richard Haselgrove]

A cuda_fermi application, v6.10, was loaded about 30 minutes ago. No-one will have any WUs yet, of course, because the splitters haven't been restarted.

I'd prefer not to test the stock download process myself if I can avoid it, because I'm rigged with an app_info and still have some VLARs waiting for optimised CPU handling. But if we could keep an eye on Claggy's list, and see if the Fermis start producing valid work, that would be good news.

[Jason G]

Please check md5 (binary equivalent) of exe against beta ones

[Richard Haselgrove]

Please check md5 (binary equivalent) of exe against beta ones

E448A1489782723161EFAF99B9494661

in both cases. Binary FC says the same, too.

So this will be the one which describes itself as 6.09 in stderr, then

[Jason G]

LoL, thanks. 

[_heinz]

berkeley switched off all data distribution, a message is on the front site. --->
"We are experiencing a problem such that some GPU platforms are quickly overflowing on all workunits that they receive. Rather than burn through a great deal of data that we would have to redistribute, we are turning off data distribution until we get this debugged."

08.06.2010 09:27:38   SETI@home   update requested by user
08.06.2010 09:27:41   SETI@home   Fetching scheduler list
08.06.2010 09:27:43   SETI@home   Master file download succeeded
08.06.2010 09:27:48   SETI@home   Sending scheduler request: Requested by user.
08.06.2010 09:27:48   SETI@home   Reporting 6 completed tasks, requesting new tasks for CPU and GPU
08.06.2010 09:27:51      Project communication failed: attempting access to reference site
08.06.2010 09:27:51   SETI@home   Scheduler request failed: Couldn't connect to server
08.06.2010 09:27:53      Internet access OK - project servers may be temporarily down.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

thats good, so they are working on it.

heinz

[Claggy]

Eric reports in the 'Scheduler problems' News thread:

"We're having difficulty getting a new scheduler running that handles cuda_fermi applications properly. We'll be down until we get it sorted out."

Claggy

[Richard Haselgrove]

This may be considered a case of "be careful what you wish for" - I sent Eric an email just as the lab opened yesterday, drawing attention to the scale of the problem and the list in this thread. Probably not what he wanted to read on a Monday morning, and deploying a new scheduler probably wan't his plan for the day either.

But it had to be done - shame it didn't go smoothly.

[Raistmer]

LoL, I did the same and recived answer that they worked on it right now (about the time 6.10 was spotted on main). Interesting, what was wrong with 6.10 ?...

[Josef W. Segur]

LoL, I did the same and recived answer that they worked on it right now (about the time 6.10 was spotted on main). Interesting, what was wrong with 6.10 ?...

Perhaps a host which got in a bad state trying to run 6.08 on a GTX 4xx will need a reboot to clear the problem. If so, automatically updating a host to 6.10 wouldn't help.

...I sent Eric an email just as the lab opened yesterday, drawing attention to the scale of the problem and the list in this thread.
...

User "korpela" has not been active in the last 24 hours, though this thread is visible to all and he might have viewed it as a guest.
                                                                                      Joe

[Richard Haselgrove]

Perhaps a host which got in a bad state trying to run 6.08 on a GTX 4xx will need a reboot to clear the problem. If so, automatically updating a host to 6.10 wouldn't help.

I've not seen anything like that, and my GTX 470 has tried them all (6.09, 6.08, v12b). They just fail in their various ways, and move on to the next task. It's very different from the 'sporadic error state' on older GPUs, where the failure persists from task to task until reboot.

[Claggy]

I started going through my resends again this morning, no new Fermi's, just these hosts:

Sigurd G.Schinke hostid=5372764 NVIDIA GeForce GTX 260 (881MB) driver: 19713

Marc Jarry hostid=4247889 NVIDIA GeForce 9600 GT (511MB) driver: 19745

BabelAbu hostid=5374194 NVIDIA GeForce GTX 260 (1792MB) driver: 19732

malycc hostid=5386713 NVIDIA GeForce 9500 GT (511MB) driver: 19745

The Beef hostid=5289552 [2] NVIDIA GeForce GTX 295 (896MB) driver: 19562

Anonymous hostid=5049618 [2] NVIDIA GeForce GTX 295 (895MB) driver: 19038

k.pieschl hostid=3192436 NVIDIA GeForce 9800 GT (1023MB) driver: 18634

Claggy