wu errored at the same time as one system rebooted itself.


Advanced search

Message boards : Number crunching : wu errored at the same time as one system rebooted itself.
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Graham Middleton

Send message
Joined: 1 Sep 00
Posts: 1519
Credit: 86,815,638
RAC: 0
United Kingdom
Message 1770449 - Posted: 8 Mar 2016, 22:19:22 UTC

WU

26ja10aa.14296.20517.5.32.120_0

errored, WU info:-

Name 26ja10aa.14296.20517.5.32.120_0
Workunit 2086426879
Created 7 Mar 2016, 10:51:42 UTC
Sent 7 Mar 2016, 16:44:02 UTC
Report deadline 28 Mar 2016, 3:53:44 UTC
Received 8 Mar 2016, 22:11:35 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status -6 (0xfffffffffffffffa) Unknown error number
Computer ID 7578105
Run time 1 sec
CPU time
Validate state Invalid
Credit 0.00
Device peak FLOPS 521.75 GFLOPS
Application version SETI@home v8
Anonymous platform (NVIDIA GPU)
Peak disk usage 0.02 MB
Stderr output

<core_client_version>7.6.22</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code -6 (0xfffffffa)
</message>
<stderr_txt>
v8 task detected
setiathome_CUDA: Found 2 CUDA device(s):
nVidia Driver Version 361.91
Device 1: GeForce GTX 580, 1536 MiB, regsPerBlock 32768
computeCap 2.0, multiProcs 16
pciBusID = 1, pciSlotID = 0
clockRate = 1600 MHz
Device 2: GeForce GTX 570, 1280 MiB, regsPerBlock 32768
computeCap 2.0, multiProcs 15
pciBusID = 2, pciSlotID = 0
clockRate = 1604 MHz
In cudaAcc_initializeDevice(): Boinc passed DevPref 2
setiathome_CUDA: CUDA Device 2 specified, checking...
Device 2: GeForce GTX 570 is okay
SETI@home using CUDA accelerated device GeForce GTX 570
pulsefind: blocks per SM 4 (Fermi or newer default)
pulsefind: periods per launch 100 (default)
Priority of process set to BELOW_NORMAL (default) successfully
Priority of worker thread set successfully

setiathome enhanced x41zi (baseline v8), Cuda 4.20

setiathome_v8 task detected
Detected Autocorrelations as enabled, size 128k elements.
Work Unit Info:
...............
WU true angle range is : 3.976052
Preemptively acknowledging a safe Exit. ->
SETI@home error -6 Bad workunit header
!swi.data_type || !found || !swi.nsamples
File: ..\seti_header.cpp
Line: 245


</stderr_txt>
]]>


Is this a cause or an effect of a system prpblem???

I'm trying to sort out some issues.

CPU id = 7578105
Happy Crunching,

Graham

ID: 1770449 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15184
Credit: 4,362,181
RAC: 3
Netherlands
Message 1770450 - Posted: 8 Mar 2016, 22:22:07 UTC - in response to Message 1770449.  

What does Windows Event Viewer say about this reboot?
ID: 1770450 · Report as offensive
Profile Graham Middleton

Send message
Joined: 1 Sep 00
Posts: 1519
Credit: 86,815,638
RAC: 0
United Kingdom
Message 1770456 - Posted: 8 Mar 2016, 22:34:26 UTC

I think it is a hardware issue, but I just want to be sure before I strip the system down completely.

There's nothing in the event viewer before the system start without a shutdown, just the normal mix of neutral system messages I've seen in other running systems.
Happy Crunching,

Graham

ID: 1770456 · Report as offensive

Message boards : Number crunching : wu errored at the same time as one system rebooted itself.


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.