All failing quickly today.
log in

Advanced search

Message boards : Number crunching : All failing quickly today.

Author Message
adrianxw
Send message
Joined: 5 Dec 12
Posts: 46
Credit: 9,438,120
RAC: 0
Message 4984 - Posted: 21 Sep 2016, 17:37:20 UTC

Since about 06:30, all wu's have instantly failed.

keputnam
Send message
Joined: 24 Jun 14
Posts: 16
Credit: 15,314,880
RAC: 7,700
Message 4985 - Posted: 21 Sep 2016, 18:41:35 UTC
Last modified: 21 Sep 2016, 18:42:40 UTC

Yup

and all PS-1619 series WUs

all sse3

UBT - Timbo
Send message
Joined: 19 Jun 12
Posts: 2
Credit: 10,861,920
RAC: 0
Message 4993 - Posted: 25 Sep 2016, 10:38:34 UTC - in response to Message 4985.

I've had a load of "ps_160915" (sse2) series WU's fail with the code "Abandoned". (44 in total)

There's nothing in the Stderr Out either - not sure what's caused it.

I've also suffered over 80 "Error while computing" the same series tasks.

This time Stderr Out says:

<core_client_version>7.4.23</core_client_version> <![CDATA[ <message> process exited with code 193 (0xc1, -63) </message> <stderr_txt> SIGSEGV: segmentation violation Stack trace (8 frames): ../../projects/asteroidsathome.net_boinc/period_search_10210_x86_64-pc-linux-gnu__sse2(boinc_catch_signal+0x47)[0x422b97] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0)[0x7fe8824878d0] ../../projects/asteroidsathome.net_boinc/period_search_10210_x86_64-pc-linux-gnu__sse2[0x40ad00] ../../projects/asteroidsathome.net_boinc/period_search_10210_x86_64-pc-linux-gnu__sse2[0x4078c1] ../../projects/asteroidsathome.net_boinc/period_search_10210_x86_64-pc-linux-gnu__sse2[0x407475] ../../projects/asteroidsathome.net_boinc/period_search_10210_x86_64-pc-linux-gnu__sse2[0x40e596] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fe8820eeb45] ../../projects/asteroidsathome.net_boinc/period_search_10210_x86_64-pc-linux-gnu__sse2[0x4057a1] Exiting... </stderr_txt> ]]>


But, the same PC has generated credits on other "ps_160915" series tasks both before and afterwards without an issue.

Maybe a bad batch ?

regards
Tim

Arivald Ha'gel
Send message
Joined: 30 Jul 14
Posts: 1
Credit: 6,743,040
RAC: 24,148
Message 5005 - Posted: 29 Sep 2016, 22:34:01 UTC

It's still instant computation error for me...

[TA]Assimilator1
Avatar
Send message
Joined: 24 Aug 13
Posts: 107
Credit: 30,008,400
RAC: 7,330
Message 5007 - Posted: 1 Oct 2016, 15:27:04 UTC

Looking at some of my errored WUs as well as this thread, I'm glad to see it isn't just me!

Looking at this WU http://asteroidsathome.net/boinc/workunit.php?wuid=53532331 ,it seems to happen with different extensions, but of the last 6 I looked at all were ps_160922 WUs
____________
Team AnandTech - SETI@H, Muon1 DPAD, Folding@H, MilkyWay@H, Asteroids@H, LHC@H, POGS, Rosetta@H, Einstein@H.

Main rig - i7 4930k @4.1 GHz, 16GB DDR3 1866, RX 580 8GB
2nd rig - Q9550 @3.6 GHz, 8GB DDR2 1066, HD 7870 XT 3GB(DS), Win 7

adrianxw
Send message
Joined: 5 Dec 12
Posts: 46
Credit: 9,438,120
RAC: 0
Message 5012 - Posted: 4 Oct 2016, 7:17:16 UTC

Many quick fails here. This looks relevent:

Reason: Access Violation (0xc0000005) at address 0x00D021CB read attempt to address 0x00000000

I scanned a few of the error logs, the address is constant. Bad pointer setting perhaps?

[TA]Assimilator1
Avatar
Send message
Joined: 24 Aug 13
Posts: 107
Credit: 30,008,400
RAC: 7,330
Message 5050 - Posted: 9 Nov 2016, 9:49:24 UTC

No word from the staff on this???

Seems my last failed WUs were on the 24/10, fingers crossed that was the last of them!........
____________
Team AnandTech - SETI@H, Muon1 DPAD, Folding@H, MilkyWay@H, Asteroids@H, LHC@H, POGS, Rosetta@H, Einstein@H.

Main rig - i7 4930k @4.1 GHz, 16GB DDR3 1866, RX 580 8GB
2nd rig - Q9550 @3.6 GHz, 8GB DDR2 1066, HD 7870 XT 3GB(DS), Win 7


Post to thread

Message boards : Number crunching : All failing quickly today.


Main page · Your account · Message boards


Copyright © 2020 Asteroids@home