My ARM box has been failing the WUs in the last week. Some go through fine, some fail after a while and some fail immediately.

I have the impression that this has started about the time when badges were added.

Please, advise.

---

Have you updated NativeBOINC? There was an update to handle the new WUPorp code for Badges.

It doesn't run Android, but regular Linux on ARM. It continues to run Oproject just fine; there's this problem only with WUprop.

---

Even your 'Valid' tasks on this machine report some errors:
http://wuprop.boinc-af.org/result.php?resultid=23689917

Stderr output
<core_client_version>7.1.0</core_client_version>
<![CDATA[
<stderr_txt>
17:21:58 (9384): Nombre de GPU non conforme: 0
17:21:58 (9384): Erreur wu_terminee (wu deja reportee)
18:21:59 (9384): Erreur reception active_result
18:30:12 (9384): Erreur reception state
18:30:12 (9384): Erreur wu_terminee (chargement state)
20:21:58 (9384): called boinc_finish

</stderr_txt>
]]>


An 'Invalid' task (Credit 0.00 as obviously the result was 'empty' (no info returned about your other projects/apps)):
http://wuprop.boinc-af.org/result.php?resultid=23621481

Stderr output
<core_client_version>7.1.0</core_client_version>
<![CDATA[
<stderr_txt>
00:08:52 (14492): Nombre de GPU non conforme: 0
00:08:52 (14492): Erreur wu_terminee (wu deja reportee)
01:08:52 (14492): Erreur reception active_result
03:01:52 (14492): Erreur reception active_result
03:08:52 (14492): called boinc_finish

</stderr_txt>
]]>


'Error while computing'
http://wuprop.boinc-af.org/result.php?resultid=23637143

Stderr output
<core_client_version>7.1.0</core_client_version>
<![CDATA[
<message>
process got signal 11
</message>
<stderr_txt>
09:10:36 (26026): Nombre de GPU non conforme: 0
09:10:36 (26026): Erreur wu_terminee (wu deja reportee)
09:45:36 (26026): Erreur reception active_result
10:10:36 (26026): Erreur reception active_result
11:12:37 (26026): Erreur reception active_result

</stderr_txt>
]]>


(I think 'process got signal 11' means something killed the process)

---

- ALF - "Find out what you don't do well ..... then don't do it!" :)

Signal #11 is SIGSEGV, or segment violation, AKA "oh, $#!%".

I don't understand why some WUs work and others don't. In the past, most worked, now, apparently after the addition of badges, it seems that only a few work. Should the ARM application be updated like those of mainstream hosts?

TIA

---

The new version of the app has been failing consistently (e.g. http://bit.ly/XSXNG4).

Please, advise.

---

The new version of the app has been failing consistently (e.g. http://bit.ly/XSXNG4)..

---

My cell phones running nativeBOINC on Android are running fine. It must be the Linux app.

---

Augustine, have you checked the Boinc folder security?

This is a Linux ARM system, a NAS actually. WUProp used to run OK on it; some WUs would fail, but since the new version came out, almost all of them have failed.

Please, advise.

---

Here, check out my phone's vast amount of failures.

That IS an Android system on ARM. It's basically running Linux, only not really, because it's Android. I tried using the official Berkeley installer but all the projects said "nope no android-linux-gnu please okay bye"

I'm no expert on the ARM architecture, but has your system got ANY swap space at all? What kind of runtime settings are being used?

Beyond that, I think I'll just queue up behind you for answers...

---

Are these issues ever going to be given any attention???

---

I updated the application.
This should correct the problem.

---

Yes, it seems to be going on well. I'll let you know how it ends.

Thank you.

---

The WUs are now being completed and validated by my ARM Linux host too.

Thanks.

---

It seems that some WUs (~10%) fail without an obvious reason, like this one and this one.

Please, advise.

---

Bump!

I've been seeing about 30% of the WUs for this host failing with a segmentation fault (signal #11) and it quickly reaches its quota for the day.

Please, advise.

---

With so many errors, the daily quota for the host was decreased to just 3 and now almost 100% of the WUs fail and the host may go a whole day without getting any WU.

Please, advise.

PS: Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

---

For the device:- http://wuprop.boinc-af.org/show_host_detail.php?hostid=54606

Some WU's fail (*) and some show Completed but have also Validated errors (**) although they do have credit given.

*
Results for Task http://wuprop.boinc-af.org/result.php?resultid=30480624

<core_client_version>6.12.38</core_client_version>
<stderr_txt>
&#133;0W
&#128; Erreur reception host_info

&#128; Nombre de GPU non conforme: 0

&#128; Nombre de GPU non conforme: 0

&#128; Nombre de GPU non conforme: 0

&#128; Nombre de GPU non conforme: 0

&#128; Erreur reception host_info

&#128; Nombre de GPU non conforme: 0
... etc, etc

</stderr_txt>
<message>
upload failure: <file_xfer_error>
<file_name>wu_v3_1373905034_156447_0_0</file_name>
<error_code>-161</error_code>
</file_xfer_error>

---------------------------------------

**
Results for Task http://wuprop.boinc-af.org/result.php?resultid=30430344

<core_client_version>6.12.38</core_client_version>
<![CDATA[
<stderr_txt>
10:00:27 (505): Nombre de GPU non conforme: 0
10:00:27 (505): Erreur wu_terminee (wu deja reportee)
11:00:27 (505): Erreur reception active_result
13:00:27 (505): called boinc_finish

</stderr_txt>

Note this device has no GPU/coprocessor (!!!) as confirmed by ...
http://wuprop.boinc-af.org/show_host_detail.php?hostid=54606
Has anyone figured out what's going on?

Cheers, Ray