Folding Forum

Today's:

7520 (R 51, C 5, G 229)
7520 (R 52, C 4, G 392)
7520 (R 59, C 4, G 246)
7520 (R 79, C 4, G 225)
7520 (R 112, C 3, G 233)

You've been running v6 too long to remember to change the Machine ID value in the config after deleting the WU info to force a new WU in Windows. Or to delete the ID .dat file in Linux to affect the same change. I'm about to have to start back on ID one from having done this with these 7520 WU's. I...

Leonardo, thanks for the heads up. I hope PG does something with this problem quickly.

This WU hasn't failed yet, but my rig is taking 30 minutes per frame longer than normal for a 6903. I've restarted the machine with no change in this behavior.

After watching two of my folders download and dump for about an hour, I took the -bigadv flag off so they could get work. I guess this isn't a big deal to some since these i7's aren't going to be eligible for -bigadv soon anyway.

And this is still occurring: 18:38:51] Folding@Home Gromacs SMP Core [18:38:51] Version 2.27 (Mar 12, 2010) [18:38:51] [18:38:51] Preparing to commence simulation [18:38:51] - Looking at optimizations... [18:38:51] - Created dyn [18:38:51] - Files status OK [18:38:51] Couldn't Decompress [18:38:51] ...

More of the same: [18:10:54] + Attempting to get work packet [18:10:54] Passkey found [18:10:54] - Connecting to assignment server [18:10:55] - Successful: assigned to (130.237.232.141). [18:10:55] + News From Folding@Home: Welcome to Folding@Home [18:10:55] Loaded queue successfully. [18:10:55] + C...

This has happened on 2 of my machines today too.

Thanks.

Same problem here. Been trying to upload to these servers since before 6 this morning.

I've had this problem on 3 different machines now.

Is there anyone who can do anything about it, reading these posts? I deleted this WU this morning, downloaded a different one, came home this evening, and was back to this one. Roughly another 6 hours lost today. The same machine has been given this WU ten times. With the same result.

I've gotten this WU twice more since I posted this last night.

I delete it, do another WU, and then it's back to this one again.

This about the 6th time, on the same machine, with this result: 23:54:06] [23:54:06] Project: 2671 (Run 49, Clone 67, Gen 13) [23:54:06] [23:54:06] Assembly optimizations on if available. [23:54:06] Entering M.D. [23:54:14] Completed 0 out of 250000 steps (0%) [23:54:25] CoreStatus = FF (255) [23:54...

Thanks. I just watched the same gpu get this WU 5 times in a row. There should be some workable mechanism to weed these WU's out after a moderate amount of failures.