LTT Folding Team's Emergency Response to Covid-19

[LU0P10]

The side effect of our friendly ddos to the F@H servers is that stats cannot keep up with us... but definitely every point will be counted... eventually... 

[ffbr]

1 minute ago, LFreeman said:

I stand behind my Car Bomb recommendation.

Only if followed by a jagerbomb 

[LFreeman]

Just now, ffbr said:

Only if followed by a jagerbomb 

Then another Car Bomb.

[Favebook]

29 minutes ago, SlurmWorm said:

Corrupt WU?  I have a WU that died immediately once it started.  If I restart the client it dies again.  If I leave it alone it starts and dies.

 

Anyway to clear it?  Does it die because it can't send data to F@H?

"Corrupt WU" can happen for few resons:

1. Unstable OC

2. Bad configuration in Advanced client

3. Using expert flags with unstable OC

 

What you are describing looks like no. 2, so I would go in Advanced Client, delete all slots and restart F@H, that should fix it. And please do not use Web Client, it's buggy AF most of the times and you have much more control and info in Advanced Client

[WaldorfMan]

2 minutes ago, ffbr said:

Jack on the rock it is then (liquor cabinet is starting to look empty with a month of confinement... no more decent whiskey) 

Evan Williams.  Cheaper than Jim Beam, but just as good for us simple folk. 

 

[LFreeman]

Just now, Favebook said:

"Corrupt WU" can happen for few resons:

1. Unstable OC

2. Bad configuration in Advanced client

3. Using expert flags with unstable OC

 

What you are describing looks like no. 2, so I would go in Advanced Client, delete all slots and restart F@H, that should fix it. And please do not use Web Client, it's buggy AF most of the times and you have much more control and info in Advanced Client

Or you could be unlucky like me and can't find an F'n reason...

[mack1080]

[hydrochloric]

1 hour ago, Ghost.Hunterzz said:

 

for me 6pm and 9pm on 04.02; then 6am and 9am today 04.03 is 0 points. Whats wrong with these 69 clocks?

You actually got one more than me.

[Xaiux]

Anyone know what the REV. A designation means with my 2070? 

[MVKirner]

1 hour ago, Xaiux said:

Anyone know what the REV. A designation means with my 2070? 

I would guess that REV is short for revision- so revision / issue A

[leadeater]

7 minutes ago, mack1080 said:

Forum software has been updated, it goes from page 419 to 421 now.

[leadeater]

7 minutes ago, Xaiux said:

Anyone know what the REV. A designation means with my 2070? 

It's probably the die quality, Nvidia has two versions of the GPU die for the RTX 2070 and the more expensive factory OC AIB cards use the A die.

[Favebook]

14 minutes ago, LFreeman said:

Or you could be unlucky like me and can't find an F'n reason...

There is always a reason to be found if you are persistent enough. But what I noted above is 75% of possible reasons.

[J1mjam]

13 minutes ago, Favebook said:

"Corrupt WU" can happen for few resons:

1. Unstable OC

2. Bad configuration in Advanced client

3. Using expert flags with unstable OC

 

What you are describing looks like no. 2, so I would go in Advanced Client, delete all slots and restart F@H, that should fix it. And please do not use Web Client, it's buggy AF most of the times and you have much more control and info in Advanced Client

I just got a WU (Project: 13877 (Run 0, Clone 1368, Gen 0)) that just 'Interrupted' repeatedly on my Google box running a P100, for the past hour.  No reason as far as I can tell.  Had to delete the slot and re-add it to kill the WU   The other P100 in that machine was chugging away just fine.
 

15:49:50:WU02:FS01:Starting
15:49:50:WU02:FS01:Running FahCore: /usr/bin/FAHCoreWrapper /var/lib/fahclient/cores/cores.foldingathome.org/v7/lin/64bit/Core_22.fah/FahCore_22 -dir 02 -suffix 01 -version 705 -lifeline 25535 -checkpoint 25 -gpu-vendor nvidia -opencl-platform 0 -opencl-device 0 -cuda-device 0 -gpu 0
15:49:50:WU02:FS01:Started FahCore on PID 25569
15:49:50:WU02:FS01:Core PID:25573
15:49:50:WU02:FS01:FahCore 0x22 started
15:49:51:WU02:FS01:0x22:*********************** Log Started 2020-04-03T15:49:51Z ***********************
15:49:51:WU02:FS01:0x22:*************************** Core22 Folding@home Core ***************************
15:49:51:WU02:FS01:0x22:       Type: 0x22
15:49:51:WU02:FS01:0x22:       Core: Core22
15:49:51:WU02:FS01:0x22:    Website: https://foldingathome.org/
15:49:51:WU02:FS01:0x22:  Copyright: (c) 2009-2018 foldingathome.org
15:49:51:WU02:FS01:0x22:     Author: John Chodera <john.chodera@choderalab.org> and Rafal Wiewiora
15:49:51:WU02:FS01:0x22:             <rafal.wiewiora@choderalab.org>
15:49:51:WU02:FS01:0x22:       Args: -dir 02 -suffix 01 -version 705 -lifeline 25569 -checkpoint 25
15:49:51:WU02:FS01:0x22:             -gpu-vendor nvidia -opencl-platform 0 -opencl-device 0 -cuda-device
15:49:51:WU02:FS01:0x22:             0 -gpu 0
15:49:51:WU02:FS01:0x22:     Config: <none>
15:49:51:WU02:FS01:0x22:************************************ Build *************************************
15:49:51:WU02:FS01:0x22:    Version: 0.0.2
15:49:51:WU02:FS01:0x22:       Date: Dec 6 2019
15:49:51:WU02:FS01:0x22:       Time: 21:20:17
15:49:51:WU02:FS01:0x22: Repository: Git
15:49:51:WU02:FS01:0x22:   Revision: f87d92b58abdf7e6bf2e173cfbc4dc3e837c7042
15:49:51:WU02:FS01:0x22:     Branch: core22
15:49:51:WU02:FS01:0x22:   Compiler: GNU 4.8.2 20140120 (Red Hat 4.8.2-15)
15:49:51:WU02:FS01:0x22:    Options: -std=gnu++98 -O3 -funroll-loops
15:49:51:WU02:FS01:0x22:   Platform: linux2 4.9.87-linuxkit-aufs
15:49:51:WU02:FS01:0x22:       Bits: 64
15:49:51:WU02:FS01:0x22:       Mode: Release
15:49:51:WU02:FS01:0x22:************************************ System ************************************
15:49:51:WU02:FS01:0x22:        CPU: Intel(R) Xeon(R) CPU @ 2.00GHz
15:49:51:WU02:FS01:0x22:     CPU ID: GenuineIntel Family 6 Model 85 Stepping 3
15:49:51:WU02:FS01:0x22:       CPUs: 2
15:49:51:WU02:FS01:0x22:     Memory: 1.74GiB
15:49:51:WU02:FS01:0x22:Free Memory: 1.42GiB
15:49:51:WU02:FS01:0x22:    Threads: POSIX_THREADS
15:49:51:WU02:FS01:0x22: OS Version: 5.0
15:49:51:WU02:FS01:0x22:Has Battery: false
15:49:51:WU02:FS01:0x22: On Battery: false
15:49:51:WU02:FS01:0x22: UTC Offset: 0
15:49:51:WU02:FS01:0x22:        PID: 25573
15:49:51:WU02:FS01:0x22:        CWD: /var/lib/fahclient/work
15:49:51:WU02:FS01:0x22:         OS: Linux 5.0.0-1033-gcp x86_64
15:49:51:WU02:FS01:0x22:    OS Arch: AMD64
15:49:51:WU02:FS01:0x22:********************************************************************************
15:49:51:WU02:FS01:0x22:Project: 13877 (Run 0, Clone 1368, Gen 0)
15:49:51:WU02:FS01:0x22:Unit: 0x0000000034e06d4a5e80cfea99fa3d67
15:49:51:WU02:FS01:0x22:Reading tar file core.xml
15:49:51:WU02:FS01:0x22:Reading tar file integrator.xml
15:49:51:WU02:FS01:0x22:Reading tar file state.xml
15:49:51:WU02:FS01:0x22:Reading tar file system.xml
15:49:54:WU02:FS01:0x22:Digital signatures verified
15:49:54:WU02:FS01:0x22:Folding@home GPU Core22 Folding@home Core
15:49:54:WU02:FS01:0x22:Version 0.0.2
15:50:01:WU02:FS01:FahCore returned: INTERRUPTED (102 = 0x66)

 

[LU0P10]

2 minutes ago, leadeater said:

It's probably the die quality, Nvidia has two versions of the GPU die for the RTX 2070 and the more expensive factory OC AIB cards use the A die.

Yes https://www.guru3d.com/articles-pages/msi-geforce-rtx-2070-gaming-z-review,5.html

[Kilrah]

18 minutes ago, mack1080 said:

I wanted to put a "404 - THREAD NOT FOUND" on top of page 404, but it was still at 402 at 1am

[LU0P10]

5 minutes ago, Kilrah said:

I wanted to put a "404 - THREAD NOT FOUND" on top of page 404, but it was still at 402 at 1am

Are you claiming that we need scheduled posts feature here?

 

[Macaw2000]

Crawled my way up to #5 but I expect to plummet hard today. WUs are not flowing freely. 

[Butwhy292]

Did anyone else have a blue screen error last night? 
 

I had the stop code; IRLQ_NOT_LESS_OR_EQUAL

 

The only way to resolve was to delete FOH completely. 

[LU0P10]

4 minutes ago, Macaw2000 said:

Crawled my way up to #5 but I expect to plummet hard today. WUs are not flowing freely. 

I am sorry to hear that... but cannot say nothing more that I´ve had very steady flow of WUs... I guess I´ve worshipped the WUs gods right way... 

...only some technical difficulties yesterday with badly seated graphics card...

...I assume you´re using Advanced flag? 

[Kilrah]

7 minutes ago, Butwhy292 said:

Did anyone else have a blue screen error last night? 
 

I had the stop code; IRLQ_NOT_LESS_OR_EQUAL

 

The only way to resolve was to delete FOH completely. 

BSOD would have nothing to do with presence of the software, just your hardware crashed.

[Butwhy292]

1 minute ago, Kilrah said:

BSOD would have nothing to do with presence of the software, just your hardware crashed.

So would you have any clue as to why the problem resolved after deleting f@h?  

[Macaw2000]

5 minutes ago, LU0P10 said:

I am sorry to hear that... but cannot say nothing more that I´ve had very steady flow of WUs... I guess I´ve worshipped the WUs gods right way... 

...only some technical difficulties yesterday with badly seated graphics card...

...I assume you´re using Advanced flag? 

 

I'm not using the advanced flag. I toyed with in my devbox but it didn't seem to offer any point benefits. Grabbing the WU early seems to be the only benefit but at scale (e.g. 60 concurrent containers running), it doesn't seem to solve the issue. Would flip it on if I'm wrong here but yesterday's discussion seemed to confirm.

[Kilrah]

4 minutes ago, Butwhy292 said:

So would you have any clue as to why the problem resolved after deleting f@h?  

Coincidence, or just that - well once you deleted F@H you were not running F@H anymore, and thus stopped stressing your hardware.

[LU0P10]

12 minutes ago, Macaw2000 said:

 

I'm not using the advanced flag. I toyed with in my devbox but it didn't seem to offer any point benefits. Grabbing the WU early seems to be the only benefit but at scale (e.g. 60 concurrent containers running, it doesn't seem to solve the issue. Would flip it on if I'm wrong here but yesterday's discussion seemed to confirm.

I haven´t thought about possible points benefits... just that you would´be been assigned from much larger pool of WUs when using Advanced flag... thus shorter downtime should yield some plus side on total production?