Failing wu on linux on arm device

log in

Advanced search

Message boards : Number crunching : Failing wu on linux on arm device

Author Message
Profile Eric_Kaiser
 
Send message
Joined: 4 Jun 13
Posts: 14
Credit: 2,055,093
RAC: 0
Total hours: 6,625,029
Message 2078 - Posted: 11 Mar 2014, 16:42:44 UTC

I'm running an arm device odroid u3 with ubuntu 13.10.

I've attached this device to wuprop and it downloaded data_collect_v3_3.52_arm-unknown-linux-gnueabihf__nci which is correct because the arm cpu supports hardfloat.
But every wu errors out immediately with the following error:

<core_client_version>7.2.7</core_client_version>
<![CDATA[
<message>
process exited with code 127 (0x7f, -129)
</message>
<stderr_txt>
../../projects/wuprop.boinc-af.org/data_collect_v3_3.52_arm-unknown-linux-gnueabihf__nci: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

</stderr_txt>
]]>

ldd results are:
libstdc++.so.6 => not found
libm.so.6 => /lib/arm-linux-gnueabi/libm.so.6 (0xb6e6a000)
libgcc_s.so.1 => /lib/arm-linux-gnueabi/libgcc_s.so.1 (0xb6e47000)
libpthread.so.0 => /lib/arm-linux-gnueabi/libpthread.so.0 (0xb6e2c000)
libc.so.6 => /lib/arm-linux-gnueabi/libc.so.6 (0xb6d47000)
/lib/ld-linux.so.3 (0xb6f0d000)

Seems that libstdc++.so.6 was not linked during compile of the executable.

I've downloaded the sources for v3.52 and compiled it myself. I put the compiled version in the project folder and renamed it to data_collect_v3_3.52_arm-unknown-linux-gnueabihf__nci.
Owner and access rights were set according to the original file.

On a first sight wu finish ok but they end in status "finished, but not valid".

stderr output:
<core_client_version>7.2.7</core_client_version>
<![CDATA[
<stderr_txt>
09:37:09 (7665): Nombre de GPU non conforme: 0
09:38:09 (7665): Nombre de GPU non conforme: 0
09:39:09 (7665): Nombre de GPU non conforme: 0
09:40:09 (7665): Nombre de GPU non conforme: 0
09:41:09 (7665): Nombre de GPU non conforme: 0
09:42:09 (7665): Nombre de GPU non conforme: 0
09:43:09 (7665): Nombre de GPU non conforme: 0
09:44:09 (7665): Nombre de GPU non conforme: 0
09:45:09 (7665): Nombre de GPU non conforme: 0
09:46:09 (7665): Nombre de GPU non conforme: 0
09:47:09 (7665): Nombre de GPU non conforme: 0
09:48:09 (7665): Nombre de GPU non conforme: 0
09:49:09 (7665): Nombre de GPU non conforme: 0
09:50:09 (7665): Nombre de GPU non conforme: 0
09:51:09 (7665): Nombre de GPU non conforme: 0
09:52:09 (7665): Nombre de GPU non conforme: 0
09:53:09 (7665): Nombre de GPU non conforme: 0
09:54:09 (7665): Nombre de GPU non conforme: 0
09:55:09 (7665): Nombre de GPU non conforme: 0
09:56:09 (7665): Nombre de GPU non conforme: 0
09:57:09 (7665): Nombre de GPU non conforme: 0
09:58:09 (7665): Nombre de GPU non conforme: 0
09:59:09 (7665): Nombre de GPU non conforme: 0
10:00:09 (7665): Nombre de GPU non conforme: 0
10:01:09 (7665): Nombre de GPU non conforme: 0
10:02:09 (7665): Nombre de GPU non conforme: 0
10:03:09 (7665): Nombre de GPU non conforme: 0
10:04:09 (7665): Nombre de GPU non conforme: 0
10:05:09 (7665): Nombre de GPU non conforme: 0
10:06:09 (7665): Nombre de GPU non conforme: 0
10:07:09 (7665): Nombre de GPU non conforme: 0
10:08:09 (7665): Nombre de GPU non conforme: 0
10:09:09 (7665): Nombre de GPU non conforme: 0
10:10:09 (7665): Nombre de GPU non conforme: 0
10:11:09 (7665): Nombre de GPU non conforme: 0
10:12:09 (7665): Nombre de GPU non conforme: 0
10:13:09 (7665): Nombre de GPU non conforme: 0
10:14:09 (7665): Nombre de GPU non conforme: 0
10:15:09 (7665): Erreur reception host_info
10:16:09 (7665): Nombre de GPU non conforme: 0
10:17:09 (7665): Nombre de GPU non conforme: 0
10:18:09 (7665): Nombre de GPU non conforme: 0
10:19:09 (7665): Nombre de GPU non conforme: 0
10:20:09 (7665): Nombre de GPU non conforme: 0
10:21:09 (7665): Nombre de GPU non conforme: 0
10:22:09 (7665): Nombre de GPU non conforme: 0
10:23:09 (7665): Nombre de GPU non conforme: 0
10:24:09 (7665): Nombre de GPU non conforme: 0
10:25:09 (7665): Nombre de GPU non conforme: 0
10:26:09 (7665): Nombre de GPU non conforme: 0
10:27:09 (7665): Nombre de GPU non conforme: 0
10:28:09 (7665): Nombre de GPU non conforme: 0
10:29:09 (7665): Nombre de GPU non conforme: 0
10:30:09 (7665): Nombre de GPU non conforme: 0
10:31:09 (7665): Nombre de GPU non conforme: 0
10:32:09 (7665): Nombre de GPU non conforme: 0
10:33:09 (7665): Nombre de GPU non conforme: 0
10:34:09 (7665): Nombre de GPU non conforme: 0
10:35:09 (7665): Nombre de GPU non conforme: 0
10:36:09 (7665): Nombre de GPU non conforme: 0
10:37:09 (7665): Nombre de GPU non conforme: 0
10:38:09 (7665): Nombre de GPU non conforme: 0
10:39:09 (7665): Nombre de GPU non conforme: 0
10:40:09 (7665): Nombre de GPU non conforme: 0
10:41:09 (7665): Nombre de GPU non conforme: 0
10:42:09 (7665): Nombre de GPU non conforme: 0
10:43:09 (7665): Nombre de GPU non conforme: 0
10:44:09 (7665): Nombre de GPU non conforme: 0
10:45:09 (7665): Nombre de GPU non conforme: 0
10:46:09 (7665): Nombre de GPU non conforme: 0
10:47:09 (7665): Erreur reception host_info
10:48:09 (7665): Nombre de GPU non conforme: 0
10:49:09 (7665): Nombre de GPU non conforme: 0
10:50:09 (7665): Erreur reception host_info
10:51:09 (7665): Erreur reception host_info
10:52:09 (7665): Erreur reception host_info
10:53:09 (7665): Erreur reception host_info
10:54:09 (7665): Erreur reception host_info
10:55:09 (7665): Erreur reception host_info
10:56:09 (7665): Erreur reception host_info
10:57:09 (7665): Erreur reception host_info
10:58:09 (7665): Erreur reception host_info
10:59:09 (7665): Erreur reception host_info
11:00:09 (7665): Nombre de GPU non conforme: 0
11:01:09 (7665): Nombre de GPU non conforme: 0
11:02:09 (7665): Nombre de GPU non conforme: 0
11:03:09 (7665): Nombre de GPU non conforme: 0
11:04:09 (7665): Nombre de GPU non conforme: 0
11:05:09 (7665): Nombre de GPU non conforme: 0
11:06:09 (7665): Nombre de GPU non conforme: 0
11:07:09 (7665): Nombre de GPU non conforme: 0
11:08:09 (7665): Nombre de GPU non conforme: 0
11:09:09 (7665): Nombre de GPU non conforme: 0
11:10:09 (7665): Nombre de GPU non conforme: 0
11:11:09 (7665): Nombre de GPU non conforme: 0
11:12:09 (7665): Nombre de GPU non conforme: 0
11:13:09 (7665): Nombre de GPU non conforme: 0
11:14:09 (7665): Nombre de GPU non conforme: 0
11:15:09 (7665): Nombre de GPU non conforme: 0
11:16:09 (7665): Nombre de GPU non conforme: 0
11:17:09 (7665): Nombre de GPU non conforme: 0
11:18:09 (7665): Nombre de GPU non conforme: 0
11:19:09 (7665): Nombre de GPU non conforme: 0
11:20:09 (7665): Nombre de GPU non conforme: 0
11:21:09 (7665): Nombre de GPU non conforme: 0
11:22:09 (7665): Nombre de GPU non conforme: 0
11:23:09 (7665): Nombre de GPU non conforme: 0
11:24:09 (7665): Erreur reception host_info
11:25:09 (7665): Erreur reception host_info
11:26:09 (7665): Erreur reception host_info
11:27:09 (7665): Nombre de GPU non conforme: 0
11:28:09 (7665): Nombre de GPU non conforme: 0
11:29:09 (7665): Erreur reception host_info
11:30:09 (7665): Nombre de GPU non conforme: 0
11:31:10 (7665): Nombre de GPU non conforme: 0
11:32:11 (7665): Nombre de GPU non conforme: 0
11:33:11 (7665): Nombre de GPU non conforme: 0
11:34:11 (7665): Nombre de GPU non conforme: 0
11:35:11 (7665): Nombre de GPU non conforme: 0
11:36:11 (7665): Nombre de GPU non conforme: 0
11:37:11 (7665): Nombre de GPU non conforme: 0
11:38:11 (7665): Nombre de GPU non conforme: 0
11:39:11 (7665): Nombre de GPU non conforme: 0
11:40:11 (7665): Nombre de GPU non conforme: 0
11:41:11 (7665): Nombre de GPU non conforme: 0
11:42:11 (7665): Nombre de GPU non conforme: 0
11:43:11 (7665): Nombre de GPU non conforme: 0
11:44:11 (7665): Nombre de GPU non conforme: 0
11:45:11 (7665): Nombre de GPU non conforme: 0
11:46:11 (7665): Nombre de GPU non conforme: 0
11:47:11 (7665): Nombre de GPU non conforme: 0
11:48:11 (7665): Nombre de GPU non conforme: 0
11:49:11 (7665): Nombre de GPU non conforme: 0
11:50:11 (7665): Nombre de GPU non conforme: 0
11:51:11 (7665): Nombre de GPU non conforme: 0
11:52:11 (7665): Nombre de GPU non conforme: 0
11:53:11 (7665): Nombre de GPU non conforme: 0
11:54:11 (7665): Nombre de GPU non conforme: 0
11:55:11 (7665): Nombre de GPU non conforme: 0
11:56:11 (7665): Nombre de GPU non conforme: 0
11:57:11 (7665): Nombre de GPU non conforme: 0
11:58:11 (7665): Nombre de GPU non conforme: 0
11:59:11 (7665): Nombre de GPU non conforme: 0
12:00:11 (7665): Nombre de GPU non conforme: 0
12:01:11 (7665): Nombre de GPU non conforme: 0
12:02:11 (7665): Nombre de GPU non conforme: 0
12:03:11 (7665): Nombre de GPU non conforme: 0
12:04:11 (7665): Nombre de GPU non conforme: 0
12:05:11 (7665): Nombre de GPU non conforme: 0
12:06:11 (7665): Nombre de GPU non conforme: 0
12:07:11 (7665): Nombre de GPU non conforme: 0
12:08:11 (7665): Nombre de GPU non conforme: 0
12:09:11 (7665): Nombre de GPU non conforme: 0
12:10:11 (7665): Nombre de GPU non conforme: 0
12:11:11 (7665): Nombre de GPU non conforme: 0
12:12:11 (7665): Nombre de GPU non conforme: 0
12:13:11 (7665): Nombre de GPU non conforme: 0
12:14:11 (7665): Nombre de GPU non conforme: 0
12:15:11 (7665): Nombre de GPU non conforme: 0
12:16:11 (7665): Nombre de GPU non conforme: 0
12:17:11 (7665): Nombre de GPU non conforme: 0
12:18:11 (7665): Nombre de GPU non conforme: 0
12:19:11 (7665): Nombre de GPU non conforme: 0
12:20:11 (7665): Nombre de GPU non conforme: 0
12:21:11 (7665): Nombre de GPU non conforme: 0
12:22:11 (7665): Nombre de GPU non conforme: 0
12:23:11 (7665): Nombre de GPU non conforme: 0
12:24:11 (7665): Nombre de GPU non conforme: 0
12:25:11 (7665): Nombre de GPU non conforme: 0
12:26:11 (7665): Nombre de GPU non conforme: 0
12:27:11 (7665): Nombre de GPU non conforme: 0
12:28:11 (7665): Nombre de GPU non conforme: 0
12:29:11 (7665): Nombre de GPU non conforme: 0
12:30:11 (7665): Nombre de GPU non conforme: 0
12:31:11 (7665): Nombre de GPU non conforme: 0
12:32:11 (7665): Nombre de GPU non conforme: 0
12:33:11 (7665): Nombre de GPU non conforme: 0
12:34:11 (7665): Nombre de GPU non conforme: 0
12:35:11 (7665): Nombre de GPU non conforme: 0
12:36:11 (7665): Nombre de GPU non conforme: 0
12:36:11 (7665): called boinc_finish

</stderr_txt>
]]>

Do you have any idea how I can solve this?

Kind Regards

Eric

PS: Link to all wu from this host: http://wuprop.boinc-af.org/results.php?hostid=66351

Profile [AF>WildWildWest] Sebastien
     
Dictator
Avatar
Send message
Joined: 28 Mar 10
Posts: 2678
Credit: 513,749
RAC: 95
Total hours: 1,427,528
Message 2080 - Posted: 11 Mar 2014, 20:06:13 UTC

WU are invalid because boinc client return empty value for p_model
You should modify source code and compile application.
File data_collect.cpp line 1276 replace

if (p_model=="" || hostid==0)

by

if (hostid==0)

____________

Profile Eric_Kaiser
 
Send message
Joined: 4 Jun 13
Posts: 14
Credit: 2,055,093
RAC: 0
Total hours: 6,625,029
Message 2082 - Posted: 11 Mar 2014, 21:32:25 UTC - in response to Message 2080.

Thank you very much for your assistance.
I made the suggested changes in the source code and compiled it. The first wu is now running.
I will report whether it was successfull or not.

Profile Eric_Kaiser
 
Send message
Joined: 4 Jun 13
Posts: 14
Credit: 2,055,093
RAC: 0
Total hours: 6,625,029
Message 2083 - Posted: 12 Mar 2014, 18:27:13 UTC

Ok, a couple of wu are calculated now. They are validated and credit was granted.

I'm not sure if the hrs for the active project on this device are counted correctly and added to the project at wuprop.

The stderr output is now:

<core_client_version>7.2.7</core_client_version>
<![CDATA[
<stderr_txt>
15:57:43 (10148): Erreur wu_terminee (wu deja reportee)
16:27:43 (10148): Erreur reception active_result
17:21:43 (10148): Erreur reception active_result
17:25:43 (10148): Erreur reception active_result
17:39:43 (10148): Erreur reception active_result
17:45:43 (10148): Erreur reception active_result
17:52:43 (10148): Erreur reception active_result
18:21:43 (10148): Erreur reception active_result
18:38:43 (10148): Erreur reception active_result
18:57:43 (10148): called boinc_finish

</stderr_txt>
]]>

Erkan Yilmaz
Send message
Joined: 2 Jun 16
Posts: 2
Credit: 40,043
RAC: 0
Total hours: 41,838
Message 3984 - Posted: 12 Jul 2016, 5:19:41 UTC - in response to Message 2078.

I've the same error on my ARM :-(

> I've downloaded the sources for v3.52 and compiled it myself.

From where did you get the sources ?

Erkan Yilmaz
Send message
Joined: 2 Jun 16
Posts: 2
Credit: 40,043
RAC: 0
Total hours: 41,838
Message 4050 - Posted: 23 Jul 2016, 15:23:22 UTC - in response to Message 3984.

problem solved!


Post to thread

Message boards : Number crunching : Failing wu on linux on arm device


Home | My Account | Message Boards | Results


Copyright © 2024 Sebastien