What is with this WU? It says "Redundant result".

---

Manned mission to Mars in 2019 Petition <-- Sign this, please.

What is with this WU? It says "Redundant result".

pending credit, but other task cancelled due to redundant result

2) Questions and Answers : Web site : pending credit, but other task cancelled due to redundant result (Message 713193)
Posted 4 days ago by OzzFan
--------------------------------------------------------------------------------

Thanks. I'm still curious as to why something was declared Redundant when it wasn't....

Maria


Well it was declared Redundant on Feb. 12th, which was four days before you returned your result. Any more than two workunits out and the server will declare the extras "Redundant".

hope that helps Henri . . .

---

BOINC Wiki . . .

Science Status Page . . .

Hmmm... Henri's got an odd one here. Only two workunits were sent out, one was returned already (pending credit), the second was canceled as redundant. The third never made it out the door. How will it get validated with only one result? That third one is going to have to be sent out.

---

Hmmm... Henri's got an odd one here. Only two workunits were sent out, one was returned already (pending credit), the second was canceled as redundant. The third never made it out the door. How will it get validated with only one result? That third one is going to have to be sent out.

. . . you looked at these Task Details right?

odd

aborted by project - no longer usable

---

BOINC Wiki . . .

Science Status Page . . .

I see what the problem is: the person with the 'redundant' result is using BOINC v6.1.8 which is in alpha testing, and apparently something screwed up during processing. I'm sure the third result was created due to this error.

---

I see what the problem is: the person with the 'redundant' result is using BOINC v6.1.8 which is in alpha testing, and apparently something screwed up during processing. I'm sure the third result was created due to this error.

. . . keep wonderin' WHY somebody would be usin' such ol' BOINCies - doesn't make any sense eh? ;)

---

BOINC Wiki . . .

Science Status Page . . .

Actually, it looks like Henri's task should not have 221'ed. It appears it aborted on the restart.

So the question is why did the project unconditionally abort it? Maybe there's a problem with the 6x CC.

@ Dr CETI: Agreed, it would seem there's a bug in the way 6x CC's interpret the meaning of a 221 command.

Alinator

I see what the problem is: the person with the 'redundant' result is using BOINC v6.1.8 which is in alpha testing, and apparently something screwed up during processing. I'm sure the third result was created due to this error.

. . . keep wonderin' WHY somebody would be usin' such ol' BOINCies - doesn't make any sense eh? ;)

I suppose some people like to "live dangerously". Such is the life on the cutting edge. I don't mind running beta software from time to time, but alpha is just too unstable for me.

---

Actually, it looks like Henri's task should not have 221'ed. It appears it aborted on the restart.

So the question is why did the project unconditionally abort it? Maybe there's a problem with the 6x CC.

Alinator

. . . sendin' this thread off to Eric right now ;)

---

BOINC Wiki . . .

Science Status Page . . .

Actually, it looks like Henri's task should not have 221'ed. It appears it aborted on the restart.

So the question is why did the project unconditionally abort it? Maybe there's a problem with the 6x CC.

@ Dr CETI: Agreed, it would seem there's a bug in the way 6x CC's interpret the meaning of a 221 command.

Alinator

Ahh, it's Henri that's using the 6.x client! LOL Yeah, I think it may be a bug with BOINC v6.

---

Actually, it looks like Henri's task should not have 221'ed. It appears it aborted on the restart.

So the question is why did the project unconditionally abort it? Maybe there's a problem with the 6x CC.

@ Dr CETI: Agreed, it would seem there's a bug in the way 6x CC's interpret the meaning of a 221 command.

Alinator

Ahh, it's Henri that's using the 6.x client! LOL Yeah, I think it may be a bug with BOINC v6.

yep: <core_client_version>6.1.8

and using w/ Optimizers: Ben Herndon, Josef Segur, Alex Kan, Simon Zadra
Version: Windows SSE3 32-bit based on seti V5.15 'Ni!'
Rev: (R-2.4|xP|FFT:IPP_SSE3|Ben-Joe)

---

BOINC Wiki . . .

Science Status Page . . .

Hmmm... looking at it more, something is really screwy here. I don't see a reason why the project would have even thought about sending a 221 in the first place.

Moral of story: One should not expect 6x to behave properly, and can fail anytime for no apparent reason. ;-)

Alinator

Hmmm... looking at it more, something is really screwy here. I don't see a reason why the project would have even thought about sending a 221 in the first place.

Moral of story: One should not expect 6x to behave properly, and can fail anytime for no apparent reason. ;-)

Alinator

We've also seen listings on the website for multiple 221s, where the actual event is clearly something different. Note that the 221 is on a P4D/XP created today, which may or may not be the same hardware as one or both of the P4Ds Henri has been running XP_64 on. Only Henri can answer that one: his message log will have the answer to the 221, too.

We've also seen listings on the website for multiple 221s, where the actual event is clearly something different. Note that the 221 is on a P4D/XP created today, which may or may not be the same hardware as one or both of the P4Ds Henri has been running XP_64 on. Only Henri can answer that one: his message log will have the answer to the 221, too.

Ah yes....

Looking over the account summary, my best guess at this point is this is a spontaneous HID respawn of 4098221.

I can't say for sure since it isn't clear how 3390945 fits into the picture.

Alinator

Sorry for spamming, but here are all the messages:

20.2.2008 19:37:13||Starting BOINC client version 6.1.8 for windows_intelx86
20.2.2008 19:37:13||log flags: task, file_xfer, sched_ops
20.2.2008 19:37:13||Libraries: libcurl/7.17.1 OpenSSL/0.9.8e zlib/1.2.3
20.2.2008 19:37:13||Data directory: G:\\Documents and Settings\\All Users\\Application Data\\BOINC
20.2.2008 19:37:15|SETI@home|Found app_info.xml; using anonymous platform
20.2.2008 19:37:17||Processor: 2 GenuineIntel Intel(R) Pentium(R) D CPU 2.80GHz [x86 Family 15 Model 6 Stepping 2]
20.2.2008 19:37:17||Processor features: fpu tsc pae sse sse2 mmx
20.2.2008 19:37:17||OS: Microsoft Windows XP: Home Edition, Service Pack 2, (05.01.2600.00)
20.2.2008 19:37:17||Memory: 2.00 GB physical, 2.04 GB virtual
20.2.2008 19:37:17||Disk: 44.66 GB total, 9.60 GB free
20.2.2008 19:37:17||Local time is UTC +2 hours
20.2.2008 19:37:18|Project TANPAKU|URL: http://issofty17.is.noda.tus.ac.jp/; Computer ID: 50554; location: home; project prefs: default
20.2.2008 19:37:18|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 4098221; location: home; project prefs: default
20.2.2008 19:37:18|SETI@home Beta Test|URL: http://setiweb.ssl.berkeley.edu/beta/; Computer ID: 8908; location: home; project prefs: default
20.2.2008 19:37:18||General prefs: from http://qcn.stanford.edu/qcnalpha/ (last modified 11-Feb-2008 13:33:30)
20.2.2008 19:37:18||Host location: none
20.2.2008 19:37:18||General prefs: using your defaults
20.2.2008 19:37:18||Preferences limit memory usage when active to 1842.74MB
20.2.2008 19:37:18||Preferences limit memory usage when idle to 1945.11MB
20.2.2008 19:37:18||Preferences limit disk usage to 9.60GB
20.2.2008 19:37:22|SETI@home Beta Test|Restarting task 11oc06aa.29289.546255.11.10.220_2 using setiathome_enhanced version 600
20.2.2008 19:37:26|SETI@home Beta Test|Restarting task 11oc06aa.29289.547073.11.10.50_2 using setiathome_enhanced version 600
20.2.2008 19:45:23|SETI@home Beta Test|Sending scheduler request: To fetch work. Requesting 49 seconds of work, reporting 0 completed tasks
20.2.2008 19:45:29|SETI@home Beta Test|Scheduler request succeeded: got 1 new tasks
20.2.2008 19:45:29|SETI@home Beta Test|Generated new host CPID: edcd41e7d63b5f34ffaf0edce1385bf0
20.2.2008 19:45:31|SETI@home Beta Test|Started download of 11oc06aa.18041.528668.12.10.239
20.2.2008 19:45:31|SETI@home Beta Test|Computation for task 11oc06aa.29289.546255.11.10.220_2 finished
20.2.2008 19:45:31|SETI@home Beta Test|Computation for task 11oc06aa.29289.547073.11.10.50_2 finished
20.2.2008 19:45:31|Project TANPAKU|Restarting task pep5_7666_31_1_1_1 using BD version 1500
20.2.2008 19:45:31|SETI@home|Restarting task 22fe07af.6162.481.6.7.209_1 using setiathome_enhanced version 527
20.2.2008 19:45:39|SETI@home Beta Test|Sending scheduler request: To fetch work. Requesting 12328 seconds of work, reporting 3 completed tasks
20.2.2008 19:45:42|SETI@home Beta Test|Finished download of 11oc06aa.18041.528668.12.10.239
20.2.2008 19:45:44|SETI@home Beta Test|Scheduler request succeeded: got 1 new tasks
20.2.2008 19:45:44|SETI@home Beta Test|Message from server: Completed result 11oc06aa.29289.548709.11.10.137_2 refused: result already reported as success
20.2.2008 19:45:46|SETI@home Beta Test|Started download of 11oc06aa.18041.528668.12.10.203
20.2.2008 19:45:57|SETI@home Beta Test|Finished download of 11oc06aa.18041.528668.12.10.203
20.2.2008 20:12:58|SETI@home|Sending scheduler request: To fetch work. Requesting 11 seconds of work, reporting 0 completed tasks
20.2.2008 20:13:03|SETI@home|Scheduler request succeeded: got 1 new tasks
20.2.2008 20:13:03|SETI@home|Generated new host CPID: 61ff167123d4550adc0b6b8fff119b38
20.2.2008 20:13:04|SETI@home|Computation for task 22fe07af.6162.481.6.7.209_1 finished
20.2.2008 20:13:04|SETI@home Beta Test|Starting 11oc06aa.18041.528668.12.10.239_2
20.2.2008 20:13:04|SETI@home Beta Test|Starting task 11oc06aa.18041.528668.12.10.239_2 using setiathome_enhanced version 600
20.2.2008 20:13:06|SETI@home|Started download of 13dc06ad.28126.2526.9.7.24
20.2.2008 20:13:17|SETI@home|Finished download of 13dc06ad.28126.2526.9.7.24
20.2.2008 20:13:54|SETI@home|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 1 completed tasks
20.2.2008 20:14:04|SETI@home|Scheduler request succeeded: got 0 new tasks
20.2.2008 20:20:37||Fetching configuration file from http://www.worldcommunitygrid.org/get_project_config.php
20.2.2008 20:20:56|World Community Grid|Master file download succeeded
20.2.2008 20:21:01|World Community Grid|Sending scheduler request: Project initialization. Requesting 1 seconds of work, reporting 0 completed tasks
20.2.2008 20:21:02||Project communication failed: attempting access to reference site
20.2.2008 20:21:04||Internet access OK - project servers may be temporarily down.
20.2.2008 20:21:06|World Community Grid|Scheduler request failed: Peer certificate cannot be authenticated with known CA certificates
20.2.2008 20:22:07|World Community Grid|Sending scheduler request: Project initialization. Requesting 1 seconds of work, reporting 0 completed tasks
20.2.2008 20:22:08||Project communication failed: attempting access to reference site
20.2.2008 20:22:10||Internet access OK - project servers may be temporarily down.
20.2.2008 20:22:12|World Community Grid|Scheduler request failed: Peer certificate cannot be authenticated with known CA certificates
20.2.2008 20:23:13|World Community Grid|Sending scheduler request: Project initialization. Requesting 1 seconds of work, reporting 0 completed tasks
20.2.2008 20:23:14||Project communication failed: attempting access to reference site
20.2.2008 20:23:17||Internet access OK - project servers may be temporarily down.
20.2.2008 20:23:18|World Community Grid|Scheduler request failed: Peer certificate cannot be authenticated with known CA certificates
20.2.2008 20:24:18|World Community Grid|Sending scheduler request: Project initialization. Requesting 1 seconds of work, reporting 0 completed tasks
20.2.2008 20:24:19||Project communication failed: attempting access to reference site
20.2.2008 20:24:23||Internet access OK - project servers may be temporarily down.
20.2.2008 20:24:23|World Community Grid|Scheduler request failed: Peer certificate cannot be authenticated with known CA certificates
20.2.2008 20:25:24|World Community Grid|Sending scheduler request: Project initialization. Requesting 1 seconds of work, reporting 0 completed tasks
20.2.2008 20:25:25||Project communication failed: attempting access to reference site
20.2.2008 20:25:29||Internet access OK - project servers may be temporarily down.
20.2.2008 20:25:29|World Community Grid|Scheduler request failed: Peer certificate cannot be authenticated with known CA certificates
20.2.2008 20:26:44|World Community Grid|Sending scheduler request: Project initialization. Requesting 1 seconds of work, reporting 0 completed tasks
20.2.2008 20:26:45||Project communication failed: attempting access to reference site
20.2.2008 20:26:49|World Community Grid|Scheduler request failed: Peer certificate cannot be authenticated with known CA certificates
20.2.2008 20:26:52||Internet access OK - project servers may be temporarily down.
20.2.2008 20:32:56|World Community Grid|Sending scheduler request: Project initialization. Requesting 1 seconds of work, reporting 0 completed tasks
20.2.2008 20:32:57||Project communication failed: attempting access to reference site
20.2.2008 20:33:00||Internet access OK - project servers may be temporarily down.
20.2.2008 20:33:02|World Community Grid|Scheduler request failed: Peer certificate cannot be authenticated with known CA certificates
20.2.2008 20:34:42|World Community Grid|Sending scheduler request: Project initialization. Requesting 1 seconds of work, reporting 0 completed tasks
20.2.2008 20:34:43||Project communication failed: attempting access to reference site
20.2.2008 20:34:46||Internet access OK - project servers may be temporarily down.
20.2.2008 20:34:48|World Community Grid|Scheduler request failed: Peer certificate cannot be authenticated with known CA certificates
20.2.2008 20:46:46|SETI@home Beta Test|Starting 11oc06aa.18041.528668.12.10.203_2
20.2.2008 20:46:46|SETI@home Beta Test|Starting task 11oc06aa.18041.528668.12.10.203_2 using setiathome_enhanced version 600
20.2.2008 20:49:40|World Community Grid|Sending scheduler request: Project initialization. Requesting 1 seconds of work, reporting 0 completed tasks
20.2.2008 20:49:42||Project communication failed: attempting access to reference site
20.2.2008 20:49:43||Internet access OK - project servers may be temporarily down.
20.2.2008 20:49:46|World Community Grid|Scheduler request failed: Peer certificate cannot be authenticated with known CA certificates
20.2.2008 21:36:46|World Community Grid|Sending scheduler request: Project initialization. Requesting 1 seconds of work, reporting 0 completed tasks
20.2.2008 21:36:48||Project communication failed: attempting access to reference site
20.2.2008 21:36:50||Internet access OK - project servers may be temporarily down.
20.2.2008 21:36:52|World Community Grid|Scheduler request failed: Peer certificate cannot be authenticated with known CA certificates
20.2.2008 21:46:55|SETI@home|Starting 13dc06ad.28126.2526.9.7.24_1
20.2.2008 21:46:55|SETI@home|Starting task 13dc06ad.28126.2526.9.7.24_1 using setiathome_enhanced version 527
20.2.2008 21:55:18|World Community Grid|Sending scheduler request: Requested by user. Requesting 4539 seconds of work, reporting 0 completed tasks
20.2.2008 21:55:21||Project communication failed: attempting access to reference site
20.2.2008 21:55:23|World Community Grid|Scheduler request failed: Peer certificate cannot be authenticated with known CA certificates
20.2.2008 21:55:25||Internet access OK - project servers may be temporarily down.
20.2.2008 21:56:23|World Community Grid|Fetching scheduler list
20.2.2008 21:56:29|World Community Grid|Master file download succeeded
20.2.2008 21:56:34|World Community Grid|Sending scheduler request: Requested by user. Requesting 4537 seconds of work, reporting 0 completed tasks
20.2.2008 21:56:35||Project communication failed: attempting access to reference site
20.2.2008 21:56:36||Internet access OK - project servers may be temporarily down.
20.2.2008 21:56:40|World Community Grid|Scheduler request failed: Peer certificate cannot be authenticated with known CA certificates
20.2.2008 21:57:40|World Community Grid|Sending scheduler request: Requested by user. Requesting 4537 seconds of work, reporting 0 completed tasks
20.2.2008 21:57:41||Project communication failed: attempting access to reference site
20.2.2008 21:57:45||Internet access OK - project servers may be temporarily down.
20.2.2008 21:57:45|World Community Grid|Scheduler request failed: Peer certificate cannot be authenticated with known CA certificates
20.2.2008 21:58:45|World Community Grid|Sending scheduler request: Requested by user. Requesting 4536 seconds of work, reporting 0 completed tasks
20.2.2008 21:58:47||Project communication failed: attempting access to reference site
20.2.2008 21:58:50|World Community Grid|Scheduler request failed: Peer certificate cannot be authenticated with known CA certificates
20.2.2008 21:58:51||Internet access OK - project servers may be temporarily down.
20.2.2008 21:59:51|World Community Grid|Sending scheduler request: Requested by user. Requesting 4536 seconds of work, reporting 0 completed tasks
20.2.2008 21:59:52||Project communication failed: attempting access to reference site
20.2.2008 21:59:53||Internet access OK - project servers may be temporarily down.
20.2.2008 21:59:56|World Community Grid|Scheduler request failed: Peer certificate cannot be authenticated with known CA certificates
20.2.2008 22:00:57|World Community Grid|Sending scheduler request: Requested by user. Requesting 4535 seconds of work, reporting 0 completed tasks
20.2.2008 22:00:59||Project communication failed: attempting access to reference site
20.2.2008 22:01:00||Internet access OK - project servers may be temporarily down.
20.2.2008 22:01:02|World Community Grid|Scheduler request failed: Peer certificate cannot be authenticated with known CA certificates
20.2.2008 22:02:58|World Community Grid|Sending scheduler request: Requested by user. Requesting 4534 seconds of work, reporting 0 completed tasks
20.2.2008 22:02:59||Project communication failed: attempting access to reference site
20.2.2008 22:03:03|World Community Grid|Scheduler request failed: Peer certificate cannot be authenticated with known CA certificates
20.2.2008 22:03:04||Internet access OK - project servers may be temporarily down.
20.2.2008 22:08:45|World Community Grid|Sending scheduler request: Requested by user. Requesting 4530 seconds of work, reporting 0 completed tasks
20.2.2008 22:08:46||Project communication failed: attempting access to reference site
20.2.2008 22:08:49||Internet access OK - project servers may be temporarily down.
20.2.2008 22:08:51|World Community Grid|Scheduler request failed: Peer certificate cannot be authenticated with known CA certificates
20.2.2008 22:09:29|SETI@home Beta Test|Computation for task 11oc06aa.18041.528668.12.10.239_2 finished
20.2.2008 22:09:29|SETI@home Beta Test|Resuming task 11oc06aa.18041.528668.12.10.203_2 using setiathome_enhanced version 600
20.2.2008 22:09:31|SETI@home Beta Test|Started upload of 11oc06aa.18041.528668.12.10.239_2_0
20.2.2008 22:09:47|SETI@home Beta Test|Finished upload of 11oc06aa.18041.528668.12.10.239_2_0
20.2.2008 22:15:08|World Community Grid|Sending scheduler request: Requested by user. Requesting 4526 seconds of work, reporting 0 completed tasks
20.2.2008 22:15:12||Project communication failed: attempting access to reference site
20.2.2008 22:15:13|World Community Grid|Scheduler request failed: Peer certificate cannot be authenticated with known CA certificates
20.2.2008 22:15:14||Internet access OK - project servers may be temporarily down.
20.2.2008 22:25:41|World Community Grid|Sending scheduler request: Requested by user. Requesting 4518 seconds of work, reporting 0 completed tasks
20.2.2008 22:25:42||Project communication failed: attempting access to reference site
20.2.2008 22:25:44||Internet access OK - project servers may be temporarily down.
20.2.2008 22:25:47|World Community Grid|Scheduler request failed: Peer certificate cannot be authenticated with known CA certificates
20.2.2008 22:28:07|SETI@home Beta Test|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 1 completed tasks
20.2.2008 22:28:13|SETI@home Beta Test|Scheduler request succeeded: got 0 new tasks

---

Manned mission to Mars in 2019 Petition <-- Sign this, please.

And here are all the task info:

Task details

HOME PARTICIPATE ABOUT COMMUNITY ACCOUNT STATISTICS

Task ID 757559161
Name 22fe07af.6162.481.6.7.209_1
Workunit 225270612
Created 19 Feb 2008 12:30:11 UTC
Sent 20 Feb 2008 6:05:05 UTC
Received 20 Feb 2008 18:13:44 UTC
Server state Over
Outcome Redundant result
Client state Cancelled by server
Exit status -221 (0xffffffffffffff23)
Computer ID 4222695
Report deadline 17 Apr 2008 8:45:48 UTC
CPU time 10795.25
stderr out <core_client_version>6.1.8</core_client_version>
<![CDATA[
<message>
aborted by project - no longer usable
</message>
<stderr_txt>
Optimized SETI@Home Enhanced application

Optimizers: Ben Herndon, Josef Segur, Alex Kan, Simon Zadra
Version: Windows SSE3 32-bit based on seti V5.15 'Ni!'
Rev: (R-2.4|xP|FFT:IPP_SSE3|Ben-Joe)
CPUID: 'Intel PD Pentium D (Presler)'
cpus: 1 cores: 2 threads: 1 cache: L1=16K L2=2048K L3=0K
features: mmx sse sse2 sse3
speed: 2813 MHz -- read megs/sec: L1=9876, L2=6676, RAM=4279

Work Unit Info
True angle range: 0.381609
Restarted at 66.15 percent.


Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Breakpoint Encountered (0x80000003) at address 0x7C901230

Engaging BOINC Windows Runtime Debugger...



********************


BOINC Windows Runtime Debugger Version 5.5.0


Dump Timestamp : 02/20/08 20:13:04
LoadLibraryA( symsrv.dll ): GetLastError = 126
LoadLibraryA( srcsrv.dll ): GetLastError = 126
Debugger Engine : 4.0.5.0
Symbol Search Path: G:\\Documents and Settings\\All Users\\Application Data\\BOINC\\slots\\3;G:\\Documents and Settings\\All Users\\Application Data\\BOINC\\projects\\setiathome.berkeley.edu;srv*G:\\DOCUME~1\\HENRIH~1\\LOCALS~1\\Temp\\symbols*http://msdl.microsoft.com/download/symbols;srv*G:\\DOCUME~1\\HENRIH~1\\LOCALS~1\\Temp\\symbols*http://boinc.berkeley.edu/symstore


ModLoad: 00400000 001b5000 G:\\Documents and Settings\\All Users\\Application Data\\BOINC\\projects\\setiathome.berkeley.edu\\KWSN_2.4_SSE3-Intel-P4_MB.pdb (symtype=7 Symbols Loaded)
ModLoad: 7c900000 000af000 (-exported- Symbols Loaded)
ModLoad: 7c800000 000f5000 (-exported- Symbols Loaded)
ModLoad: 77dc0000 000aa000 (-exported- Symbols Loaded)
ModLoad: 77e70000 00091000 (-exported- Symbols Loaded)
ModLoad: 77f10000 00047000 (-exported- Symbols Loaded)
ModLoad: 7e360000 00090000 (-exported- Symbols Loaded)
ModLoad: 76370000 0001d000 (-exported- Symbols Loaded)
ModLoad: 62f30000 00009000 (-exported- Symbols Loaded)
ModLoad: 75550000 0006b000 (-exported- Symbols Loaded)
ModLoad: 77c00000 00058000 (-exported- Symbols Loaded)
ModLoad: 59f80000 000a1000 (-exported- Symbols Loaded)
ModLoad: 77bf0000 00008000 (-exported- Symbols Loaded)


*** Dump of the Process Statistics: ***

- I/O Operations Counters -
Read: 112, Write: 0, Other 157

- I/O Transfers Counters -
Read: 0, Write: 6152, Other 0

- Paged Pool Usage -
QuotaPagedPoolUsage: 31652, QuotaPeakPagedPoolUsage: 31652
QuotaNonPagedPoolUsage: 2304, QuotaPeakNonPagedPoolUsage: 3304

- Virtual Memory Usage -
VirtualSize: 60370944, PeakVirtualSize: 85458944

- Pagefile Usage -
PagefileUsage: 29122560, PeakPagefileUsage: 65142784

- Working Set Size -
WorkingSetSize: 29327360, PeakWorkingSetSize: 41558016, PageFaultCount: 76239

*** Dump of the Worker thread (2e0): ***

- Information -
Status: Running, Base Priority: Above Normal, Priority: Above Normal, Kernel Time: 12031250.000000, User Time: 14232343552.000000, Wait Time: 155439.000000

- Registers -
eax=00ca1020 ebx=0012eef4 ecx=00000036 edx=00ca2704 esi=00d5d0c0 edi=00000040
eip=004a7555 esp=0012ee68 ebp=0012ee80
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000212

- Callstack -
ChildEBP RetAddr Args to Child
0012ee80 0040d9b8 00d5d0c0 00000040 0000002b 3f8ba29e KWSN_2.4_SSE3-Intel-P4_MB!opt_f_GetChiSq+0x2 (.\\opt_FPU.cpp:510)
0012ef2c 00404dc5 00d5d0c0 00004000 00000966 968ce9e6 KWSN_2.4_SSE3-Intel-P4_MB!GaussFit+0x6 (..\\gaussfit.cpp:541)
0012f15c 00402312 01fc0040 00100000 03498c20 9fbaa1a0 KWSN_2.4_SSE3-Intel-P4_MB!analyze_pot+0x5 (..\\analyzePoT.cpp:213)
0012fab8 0049c27b 61732e74 00010068 00000000 0000000f KWSN_2.4_SSE3-Intel-P4_MB!seti_analyze+0x1f (..\\analyzeFuncs.cpp:783)
0012faf8 004a15cf 00000000 00000000 00000000 00000000 KWSN_2.4_SSE3-Intel-P4_MB!seti_do_work+0xa (..\\seti.cpp:898) FPO: [0,0,1]
0012fbf8 0040f9ce 00000000 7ffdc000 0040f9ce 00000000 KWSN_2.4_SSE3-Intel-P4_MB!worker+0x5 (..\\worker.cpp:282)
0012fcf4 0040f7a0 00000001 0012fd0c 00142418 0012fd0c KWSN_2.4_SSE3-Intel-P4_MB!main+0x0 (..\\main.cpp:286)
0012fe98 004c2f99 00400000 00000000 00142457 0000000a KWSN_2.4_SSE3-Intel-P4_MB!WinMain+0xb (..\\main.cpp:307) FPO: [4,100,0]
0012feb0 00000005 00000001 00000a28 00000002 76726553 KWSN_2.4_SSE3-Intel-P4_MB!WinMainCRTStartup+0x1d (f:\\vs70builds\\6030\\vc\\crtbld\\crt\\src\\crt0.c:251)

StackWalk(): GetLastError = 5

*** Dump of the Timer thread (bf8): ***

- Information -
Status: Waiting, Wait Reason: UserRequest, Kernel Time: 0.000000, User Time: 0.000000, Wait Time: 155439.000000

- Unhandled Exception Record -
Reason: Breakpoint Encountered (0x80000003) at address 0x7C901230

- Registers -
eax=00000000 ebx=003c6ec0 ecx=0052fec2 edx=00c9613c esi=003c6ec0 edi=00000000
eip=7c901230 esp=00c9f1fc ebp=00c9ff78
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246

- Callstack -
ChildEBP RetAddr Args to Child
00c9ff78 004d2755 003c6ec0 004f5933 00000000 00000000 ntdll!DbgBreakPoint+0x0
00c9ffb4 7c80b683 003c6ec0 00000000 00000000 003c6ec0 KWSN_2.4_SSE3-Intel-P4_MB!timer_thread+0x0
00c9ffec 00000000 004f58c4 003c6ec0 00000000 00000008 kernel32!GetModuleFileNameA+0x0


*** Debug Message Dump ****


*** Foreground Window Data ***
Window Name : 2008-01-11_1.pdf - Adobe Reader
Window Class : AcrobatSDIWindow
Window Process ID: 3f8
Window Thread ID : fb4

Exiting...

</stderr_txt>
]]>

Validate state Not necessary
Claimed credit 57.9302379417363
Granted credit 0
application version 5.27


HOME PARTICIPATE ABOUT COMMUNITY ACCOUNT STATISTICS
Copyright © 2008 University of California

---

Manned mission to Mars in 2019 Petition <-- Sign this, please.

Workunit info:

Workunit details

HOME PARTICIPATE ABOUT COMMUNITY ACCOUNT STATISTICS

application SETI@home Enhanced
created 19 Feb 2008 12:30:09 UTC
name 22fe07af.6162.481.6.7.209
minimum quorum 2
initial replication 2
max # of error/total/success tasks 5, 10, 5
Task ID
click for details Computer Sent Time reported
or deadline
explain Server state
explain Outcome
explain Client state
explain CPU time (sec) claimed credit granted credit
758919321 --- --- --- Unsent Unknown New --- --- ---
757559160 3713077 20 Feb 2008 6:05:04 UTC 20 Feb 2008 12:25:02 UTC Over Success Done 10,912.11 75.42 pending
757559161 4222695 20 Feb 2008 6:05:05 UTC 20 Feb 2008 18:13:44 UTC Over Redundant result Cancelled by server 10,795.25 --- ---


HOME PARTICIPATE ABOUT COMMUNITY ACCOUNT STATISTICS
Copyright © 2008 University of California

---

Manned mission to Mars in 2019 Petition <-- Sign this, please.

LOL....

No problemo, a lengthy log snippet can sometimes do more good that about 100 back and forth posts. ;-)

One question though before I start plowing through the log.

Are the three HID's listed as PD's separate machines?

<edit>

From log snippet:

.
.
.
20.2.2008 20:13:03|SETI@home|Generated new host CPID: 61ff167123d4550adc0b6b8fff119b38
.
.
.

So it would seem that you did suffer a spontaneous HID repawn for the host, and that the task marked redundant was actually dumped since it was linked to the old HID (as far as the project was concerned).

Alinator

What other info do you need?

---

Manned mission to Mars in 2019 Petition <-- Sign this, please.

I think we're getting to the bottom of it now. See my edit to the previous post.

Alinator