log in

All S2m941 err out ?

Message boards : Questions/Problems/Bugs : All S2m941 err out ?
Message board moderation

To post messages, you must log in.

AuthorMessage
WimTea

Send message
Joined: 11 Sep 09
Posts: 4
Credit: 969,391
RAC: 0
Message 223 - Posted: 16 Nov 2009, 12:25:27 UTC

On my xp 64 box, host #581, all these units err out after around 1m15. Anyone else?
Aborted the few left in cache, but can't keep an eye on it 16x7.
ID: 223 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Greg
Project administrator

Send message
Joined: 26 Jun 08
Posts: 591
Credit: 242,172,928
RAC: 5,505
Message 224 - Posted: 16 Nov 2009, 18:13:16 UTC - in response to Message 223.  

The 2m941 work units use much more memory, about 1 GB per task, than the others. BOINC should not be starting them if there is not sufficient memory for them, but it seems to be in some cases anyway. You can disable them entirely by deselecting lasievef in NFS@Home preferences in your account.
ID: 224 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Bijo Alex Thomas

Send message
Joined: 5 Nov 09
Posts: 1
Credit: 292,866
RAC: 0
Message 225 - Posted: 17 Nov 2009, 1:44:48 UTC - in response to Message 224.  

It errors out in my machine as well. With the below error message. Is it the same case? I had done lasievef work units previously in the same machine. Had few troubles earlier also though.

<core_client_version>6.2.28</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
boinc initialized
work files resolved, now working
-> projects/escatter11.fullerton.edu_nfs/lasievef_1.07_windows_intelx86.exe
-> -r
-> -f
-> 205106000
-> -c
-> 1000
-> -R
-> ../../projects/escatter11.fullerton.edu_nfs/S2m941.poly
-> -o
-> ../../projects/escatter11.fullerton.edu_nfs/S2m941_205106_r_0_0
xmalloc: m
called boinc_finish

</stderr_txt>
]]>
ID: 225 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Greg
Project administrator

Send message
Joined: 26 Jun 08
Posts: 591
Credit: 242,172,928
RAC: 5,505
Message 227 - Posted: 17 Nov 2009, 2:24:01 UTC

Yes, xmalloc errors indicate that there was not enough contiguous memory available for the workunit. These 2m941 workunits use much more memory than the R269 workunits. It's fine to just allow them to error out or to manually abort them as they get automatically reissued. But if you wish, you can disable lasievef until these clear. I'll post a notice in this thread when they're gone.
ID: 227 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
M0CZY
Avatar

Send message
Joined: 14 Sep 09
Posts: 2
Credit: 122,231
RAC: 17
Message 237 - Posted: 20 Nov 2009, 11:04:47 UTC - in response to Message 227.  

If it helps, all the S2m941 work units I have received under Windows (on 2 different machines) all failed with "computation error", whereas when run under Linux, all my S2m941 work units have completed successfully.
The biggest threat to public safety and security is not terrorism, it is Government abuse of authority.

Bitcoin Donations: 1Le52kWoLz42fjfappoBmyg73oyvejKBR3
ID: 237 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Greg
Project administrator

Send message
Joined: 26 Jun 08
Posts: 591
Credit: 242,172,928
RAC: 5,505
Message 256 - Posted: 29 Nov 2009, 3:04:42 UTC - in response to Message 227.  

I'll post a notice in this thread when they're gone.

All but a handful of 2m941 workunits have now been completed, so it is unlikely that you will see any more of them. If you have disabled lasievef in your NFS@Home preferences due to these high-memory workunits, then you can now enable it again. We are now working on 10,268+, which uses about 500 MB per workunit.
ID: 256 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Questions/Problems/Bugs : All S2m941 err out ?


Home | My Account | Message Boards