Page 1 of 1
Project: 6701 (Run 26, Clone 5, Gen 7)
Posted: Mon Jun 28, 2010 5:03 am
by ikerekes
This project failed with c0000029 twice at the same place;
Code: Select all
00:26:47] Completed 1660000 out of 2000000 steps (83%)
[00:26:47] - Autosending finished units... [June 28 00:26:47 UTC]
[00:26:47] Trying to send all finished work units
[00:26:47] + No unsent completed units remaining.
[00:26:47] - Autosend completed
[00:40:14] Completed 1680000 out of 2000000 steps (84%)
[00:53:44] Completed 1700000 out of 2000000 steps (85%)
[01:07:11] Completed 1720000 out of 2000000 steps (86%)
[01:20:37] Completed 1740000 out of 2000000 steps (87%)
[01:33:58] Completed 1760000 out of 2000000 steps (88%)
[01:47:19] Completed 1780000 out of 2000000 steps (89%)
[02:00:40] Completed 1800000 out of 2000000 steps (90%)
[04:48:26] CoreStatus = C0000029 (-1073741783)
[04:48:26] Client-core communications error: ERROR 0xc0000029
[04:48:26] Deleting current work unit & continuing...
[04:48:42] Trying to send all finished work units
[04:48:42] + No unsent completed units remaining.
[04:48:42] - Preparing to get new work unit...
[04:48:42] Cleaning up work directory
Re: Project: 6701 (Run 26, Clone 5, Gen 7)
Posted: Mon Jun 28, 2010 5:47 am
by bruce
Windows? Linux? MacOS?
Which version of FahCore_a3.exe is running?
How many SMP cores are running?
Re: Project: 6701 (Run 26, Clone 5, Gen 7)
Posted: Mon Jun 28, 2010 2:23 pm
by ikerekes
bruce wrote:Windows? Linux? MacOS?
Which version of FahCore_a3.exe is running?
How many SMP cores are running?
windows xp-sp3 32bit
Q6600 @3.3Ghz with 2G memory, thousands of successful WU's, running 4 core core 2.22
Here is a more complete log of the failure:
Code: Select all
[00:40:14] Completed 1680000 out of 2000000 steps (84%)
[00:53:44] Completed 1700000 out of 2000000 steps (85%)
[01:07:11] Completed 1720000 out of 2000000 steps (86%)
[01:20:37] Completed 1740000 out of 2000000 steps (87%)
[01:33:58] Completed 1760000 out of 2000000 steps (88%)
[01:47:19] Completed 1780000 out of 2000000 steps (89%)
[02:00:40] Completed 1800000 out of 2000000 steps (90%)
[04:48:26] CoreStatus = C0000029 (-1073741783)
[04:48:26] Client-core communications error: ERROR 0xc0000029
[04:48:26] Deleting current work unit & continuing...
[04:48:42] Trying to send all finished work units
[04:48:42] + No unsent completed units remaining.
[04:48:42] - Preparing to get new work unit...
[04:48:42] Cleaning up work directory
[04:48:42] + Attempting to get work packet
[04:48:42] Passkey found
[04:48:42] - Will indicate memory of 2046 MB
[04:48:42] - Detect CPU. Vendor: GenuineIntel, Family: 6, Model: 15, Stepping: 11
[04:48:42] - Connecting to assignment server
[04:48:42] Connecting to http://assign.stanford.edu:8080/
[04:48:43] Posted data.
[04:48:43] Initial: 40AB; - Successful: assigned to (171.64.65.54).
[04:48:43] + News From Folding@Home: Welcome to Folding@Home
[04:48:43] Loaded queue successfully.
[04:48:43] Connecting to http://171.64.65.54:8080/
[04:48:44] Posted data.
[04:48:44] Initial: 0000; - Receiving payload (expected size: 1778482)
[04:48:47] - Downloaded at ~578 kB/s
[04:48:47] - Averaged speed for that direction ~373 kB/s
[04:48:47] + Received work.
[04:48:47] + Closed connections
[04:48:52]
[04:48:52] + Processing work unit
[04:48:52] Core required: FahCore_a3.exe
[04:48:52] Core found.
[04:48:52] Working on queue slot 01 [June 28 04:48:52 UTC]
[04:48:52] + Working ...
[04:48:52] - Calling '.\FahCore_a3.exe -dir work/ -nice 19 -suffix 01 -np 4 -nocpulock -checkpoint 15 -forceasm -verbose -lifeline 3376 -version 629'
[04:48:52]
[04:48:52] *------------------------------*
[04:48:52] Folding@Home Gromacs SMP Core
[04:48:52] Version 2.22 (Mar 12, 2010)
[04:48:52]
[04:48:52] Preparing to commence simulation
[04:48:52] - Assembly optimizations manually forced on.
[04:48:52] - Not checking prior termination.
[04:48:53] - Expanded 1777970 -> 2058129 (decompressed 115.7 percent)
[04:48:53] Called DecompressByteArray: compressed_data_size=1777970 data_size=2058129, decompressed_data_size=2058129 diff=0
[04:48:53] - Digital signature verified
[04:48:53]
[04:48:53] Project: 6025 (Run 1, Clone 58, Gen 157)
[04:48:53]
[04:48:53] Assembly optimizations on if available.
[04:48:53] Entering M.D.
[04:48:59] Completed 0 out of 500000 steps (0%)
[04:55:04] Completed 5000 out of 500000 steps (1%)
[05:01:06] Completed 10000 out of 500000 steps (2%)
[05:07:11] Completed 15000 out of 500000 steps (3%)
[05:13:09] Completed 20000 out of 500000 steps (4%)
[05:18:52] Completed 25000 out of 500000 steps (5%)
[05:24:35] Completed 30000 out of 500000 steps (6%)
[05:30:16] Completed 35000 out of 500000 steps (7%)
[05:35:57] Completed 40000 out of 500000 steps (8%)
BTW. this is not the first CoreStatus = C0000029 what I and many others reported, and especially not the first with Project 6701.
I figured why report? Nobody cares anyways...
Re: Project: 6701 (Run 26, Clone 5, Gen 7)
Posted: Mon Jun 28, 2010 2:42 pm
by PantherX
ikerekes wrote:...I figured why report? Nobody cares anyways...
Ahem.. by not reporting, you are causing multiple copies of the same WU to be distributed. This will have a negative effect on Project 6701 which will effect everyone. BTW some people do care enough to make this:
WU Listings For Project 6013 [Good & Bad] 
Re: Project: 6701 (Run 26, Clone 5, Gen 7)
Posted: Mon Jun 28, 2010 3:24 pm
by kasson
The log I see there is for project 6025.
[04:48:53] Project: 6025 (Run 1, Clone 58, Gen 157)
[04:48:53]
[04:48:53] Assembly optimizations on if available.
[04:48:53] Entering M.D.
[04:48:59] Completed 0 out of 500000 steps (0%)
We certainly do care; unfortunately the automatic error reporting isn't as robust as we'd like (by a long shot) in the current client. We're hoping to fix this in the new client under development.
Re: Project: 6701 (Run 26, Clone 5, Gen 7)
Posted: Mon Jun 28, 2010 3:35 pm
by mdk777
The log I see there is for project 6025.
That's the subsequent WU, the one above EUE at 90%
Re: Project: 6701 (Run 26, Clone 5, Gen 7)
Posted: Mon Jun 28, 2010 3:44 pm
by ikerekes
PantherX wrote:ikerekes wrote:...I figured why report? Nobody cares anyways...
Ahem.. by not reporting, you are causing multiple copies of the same WU to be distributed. This will have a negative effect on Project 6701 which will effect everyone. BTW some people do care enough to make this:
WU Listings For Project 6013 [Good & Bad]
Just a FYI, I was the first who reported the first problem with Project 6013.
http://foldingforum.org/viewtopic.php?f ... 27#p138590
The only reaction what I got for my report and arrogant threatening NO YOU CAN NOT DELETE a DEFECTED WU NO MATTER WHAT.
PantherX I know it is hard to understand but if I can not complete the WU it will be redistributed Do I report it or not,
Re: Project: 6701 (Run 26, Clone 5, Gen 7)
Posted: Mon Jun 28, 2010 3:52 pm
by PantherX
ikerekes wrote:...PantherX I know it is hard to understand but if I can not complete the WU it will be redistributed Do I report it or not,
Hopefully this recommendation will help you to decide:
kasson wrote:It's hard to say what's making the WU slow (bad WU vs. unusual interesting WU). But if it won't make the deadline on a machine that usually finishes that project with time to spare, delete and move on.
Personally, I would report any WU that is deviating from "normal" behavior on my system. Sometimes these are false positives but it is better to play safe (IMHO).