Message boards :
Sixtrack Application :
Computation errors on Android (31 (0x0000001F) Unknown error code)
Message board moderation
Author | Message |
---|---|
Send message Joined: 26 Sep 17 Posts: 6 Credit: 1,190,866 RAC: 0 |
Been getting these compute errors immediately on my smartphone: https://lhcathome.cern.ch/lhcathome/result.php?resultid=251147453 Any ideas? <core_client_version>7.4.53</core_client_version> <![CDATA[ <message> process got signal 31 </message> <stderr_txt> </stderr_txt> ]]> |
Send message Joined: 15 Jun 08 Posts: 2564 Credit: 257,218,945 RAC: 113,926 |
In another post James Molson stated: James Molson wrote: The arm/android executable is aarch64, your host is armv7, which is 32bit arm You may check if this is also applicable to your android device. |
Send message Joined: 26 Sep 17 Posts: 6 Credit: 1,190,866 RAC: 0 |
Right, I checked the kernel version and it seems to be a 32-bit system. Thanks. |
Send message Joined: 25 Jan 17 Posts: 27 Credit: 3,258,853 RAC: 0 |
Been getting these compute errors immediately on my smartphone: https://lhcathome.cern.ch/lhcathome/result.php?resultid=251147453 Any ideas? What you are seeing is this: https://android-developers.googleblog.com/2017/07/seccomp-filter-in-android-o.html The current "android" executable is just a big statically linked linux executable, built on a linux machine. The newer versions of android do not like this. We put a filter in on the android version to stop this executable being sent to the newer versions of android, but it does not seem to work due to a bug in boinc itself, which I hope will be fixed at some point. Perhaps Nils or Laurence can comment on that last bit since it is out of my hands :) Eventually I will make a real android executable if I get the time - the annoying part is making a fortran compiler that will work with the android libraries. |
©2025 CERN