LHC@home

The 32bit arm exe (i.e. arm v6 and v7) has not been pushed out yet...

got 4 sixtracktest tasks on my armv7 device and they all finished without an error and validated ok.

Just added a couple of Raspberry Pi's. Hope there will be more work soon ...

Tom

Due to limitations in the way the BOINC client software is compiled for FreeBSD, I don't believe FreeBSD clients would be offered the AVX version of the sixtracktest software. I believe it would require an app_info or app_config file. I have written one up quickly and am wondering if it looks ok to try and work with the lhc@home servers...


<app_info>
<app>
<name>sixtracktest</name>
</app>
<file_info>
<name>sixtracktest_freeBSD64_4630_avx.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>sixtracktest</app_name>
<version_num>4630</version_num>
<plan_class>avx</plan_class>
<api_version>7.7.0</api_version>
</app_version>
</app_info>


Thank you very much for your time. BTW, so far the FreeBSD sse2 binary looks like its working like a charm.

The FreeBSD app_info.xml file seems to be ok, but there is/are missing entries on how to open or handle the data (zip) file... maybe a missing command line or something. It did download some workunits and tried to run the AVX binary, but the app just hung, probably since no data files were opened.

But the sse2 binary seems to work (but no validations yet).

Add the <file_ref> section:

<app_info>
<app>
<name>sixtracktest</name>
</app>
<file_info>
<name>sixtracktest_freeBSD64_4630_avx.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>sixtracktest</app_name>
<version_num>4630</version_num>
<plan_class>avx</plan_class>
<file_ref>
<file_name>sixtracktest_freeBSD64_4630_avx.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

Add the <file_ref> section:

Thanks so much for the advice! Thats exactly what it needed, and now the AVX program is being used for workunits.

Regards

Added two Raspberry Pi model 2B's and one Raspberry Pi model 3B.
Tasks take appr. 8 hours on the model 2B and appr. 4 hours on the model 3B.
There is a problem with memory usage however. Running one tasks at the time is fine, but when running multiple tasks pretty soon one of them will be in 'Waiting for memory' state and for some reason Boinc does not start a task from another project.
Here is a list of the 4 Boinc tasks running on one of my Pi's.
There are two BHspin tasks (Universe@home), one SETI@home task and one sixtracktest task. The universe@home tasks take 2.3 Mb, the seti@home task 36.6 Mb, while the sixtracktest task takes 330.2 Mb (RESident set size column).

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND

907 boinc 39 19 457016 330288 1988 R 99.5 34.9 1:09.98 sixtracktest_ar
910 boinc 39 19 38216 36692 2852 R 99.5 3.9 1:05.03 setiathome_8.06
912 boinc 39 19 3780 2372 2120 R 99.5 0.3 0:57.29 BHspin2_1_arm-u
914 boinc 39 19 3780 2312 2060 R 98.2 0.2 0:54.73 BHspin2_1_arm-u

One one of my Pi's (it had another sixtracktest task 'Waiting for memory') I was unable to start BOINC manager (probably because there was not enough memory).

I don't know if this is feasible, but an application using less memory would be useful here ...

Tom

I have 4 tasks that have been running for 1.75day, this seems unsual.

wTest_hllhc10BaseB1_t02_BOINC__27__s__62.31_60.32__4_5__5__88.5_1_sixvf_boinc45673
wTest_hllhc10BaseB1_t02_BOINC__22__s__62.31_60.32__8_9__5__4.5_1_sixvf_boinc43198

wTest_hllhc10BaseB1_t02_BOINC__17__s__62.31_60.32__5_6__5__30_1_sixvf_boinc40383

wTest_hllhc10BaseB1_t02_BOINC__29__s__62.31_60.32__5_6__5__60_1_sixvf_boinc46775

https://lhcathome.cern.ch/lhcathome/workunit.php?wuid=74450224
https://lhcathome.cern.ch/lhcathome/workunit.php?wuid=74447279
https://lhcathome.cern.ch/lhcathome/workunit.php?wuid=74442633

Hello,
My CPU supports AVX but my Boinc Client is receiving only SSE2 apps/task. Is there any setting I must apply to receive AVX tasks ?
Thanks

it's just random, nothing to do on your side. Only 10% are AVX

If I understand it correctly the scheduler should send the application that performs best on the volunteer's host.
To make the right decision it sends other apps for a crosscheck from time to time.

Unfortunately this does not work proper here as sixtrack tasks have a wide range of different runtimes.
It may be necessary to send well known test tasks together with the test app to get valid data.

And if you don't get anything else but the sse2 tasks the server can't even try to evaluate the application speed. This is what is happening with 46.30 application.

---

Valid (555) Validation pending (220) Invalid (0) · Error (0)
In progress (113)

---

Volunteer Mad Scientist For Life

Thanks for the explanation and happy crunching.

The 32bit arm exe (i.e. arm v6 and v7) has not been pushed out yet...

got 4 sixtracktest tasks on my armv7 device and they all finished without an error and validated ok.

did you have to do anything special to get them running on your device? is it an android device?
im currently having trouble getting any tasks at all on my android device, armv7 cpu. i read the latest notice about sixtrack tasks only being for the "main" operating systems for now, but is there anything that will run on android?
i signed up for einstein@home on my device and dont have any trouble getting tasks and completing them, but nothing for lhc@home.
i have set my preferences to accept all tasks and to accept other work if certain tasks are not available. ive tried updating, resetting but still nothing. it communicates successfully but does not give me any tasks.

is this normal or am i doing something wrong?

---

did you have to do anything special to get them running on your device? is it an android device?

its a banana pi with debian on it. nothing special, just installed it following the standard debian way and boinc was working.

im currently having trouble getting any tasks at all on my android device, armv7 cpu. i read the latest notice about sixtrack tasks only being for the "main" operating systems for now, but is there anything that will run on android?

right now the applications for arm (android) etc. are in testing. so to get work for your device, sixtracktest tasks have to be in queue. at the moment this is not the case and thats why you dont get any work.

is this normal or am i doing something wrong?

since the sixtracktest task queue is empty (and also the sixtrack task queue) at the moment, you wont get any tasks on your android device (as on any other) and this is normal behaviour.
To check if there is work available, go here and look for "unsent":
https://lhcathome.cern.ch/lhcathome/server_status.php

ah ok, thanks for the clarification and info.

---

Hi!

I just noticed many (about 200) failed WUs on my account since beginning of September.
The new executable sixtrack_lin32_4630_sse2.linux (sixtrack version 4630) segfaults with the message

FATAL: kernel too old

The previous version 45107 was running normally.

What is the minimum expected kernel version?

> uname -r
2.6.31.14-0.8-default

Thanks!

---

Hi, the minimum is 2.6.32:


ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked, for GNU/Linux 2.6.32

That kernel has not been supported for about 7 years (2.6.31).

Hi, it is dear to my heart to be as inclusive as possible.
I'll see if I can build on an old Linux system of mine,
and especially for my "dear old" 32-bit systems.
No promises, but I should have news in a week or so.
(There might be compiler problems/bugs on these ancient
platforms. I am aware of the horrible bind between new hardware
requiring new software and new software requiring new hardware!
I am against the "throw away" culture to the limits of
the possible.) . Eric.

---