Been setting up another SDCard with Jessie on it, but with 3.10.25+ kernel, still ongoing when I was there last,

Browsing Github, I've found the ticket for our Bug:

https://github.com/raspberrypi/linux/issues/600

I do have a serial cable, although I've never used it before, I'm able to do the last request without problem,
and I can reimage my new SDCard with Wheezy and the lastest firmware if necessary, and put Boinc on it.

Claggy

Yup, I raised that bug :)

Advice from the kernel gurus is that it's probably an upstream bug i.e. not a kernel bug - perhaps the BOINC client (or project executables) calling an unsupported floating point instruction.

The full trace I managed to obtain is available on that GitHub ticket, so if that's enlightening to anyone / if anyone can interpret from it which part of the BOINC system tripped the error, that would be most useful.

Did a dist-upgrade last week and noticed the kernel says is 3.12.20+ now. Its also locked up a couple of times running e@h work so maybe still an issue. I will try doing a rpi-update and see if there is a more recent one.

---

MarkJ

My Pi that was running kernel 3.10.37 on Raspbian Wheezy also updated to 3.12.20+ just by use of sudo apt-get update && sudo apt-get upgrade,
It's still running without a problem through, the difference is, it's running a self compiled Boinc 7.2.47, rather than the Raspbian repository Boinc 7.2.47/7.3.19
So I reckon there's a problem between the Debian source, the Raspbian source and the actual compiling for the Pi, along with perhaps kernel or compiler Bug.

Claggy

Did another update and now have one Pi on:
3.12.22+ #691 PREEMPT Wed Jun 18 18:29:58 BST 2014 armv6l

Its locked up twice today. The other 4 that are running 3.12.20+ are working fine. They all have BOINC 7.3.19 from the repo and are all running Jessie.

This Pi has a 16Gb SD card, the others have 8Gb and it has a fan hanging off the USB port. Neither should make any difference but this is the only one that keeps locking up. It possibly could be different firmware version as this one has had a few updates the others haven't.

---

MarkJ

The two installation of Jessie I have with 3.12.22+ and Boinc 7.3.19 don't lockup any longer, Both on updating to Boinc 7.3.19 error their Wu's instead:

http://setiathome.berkeley.edu/results.php?hostid=7285452

http://setiathome.berkeley.edu/results.php?hostid=7299597

<core_client_version>7.3.19</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
boinc-app-seti is invoked with the following arguments:
--start
--end.
I: boinc_parse_init_data_file
I: boinc_get_init_data
I: boinc_init
I: worker
I: worker() - common_init
I: worker() - read_wu_state
SIGSEGV: segmentation violation
Stack trace (9 frames):
/usr/lib/libboinc.so.7(boinc_catch_signal+0xd8)[0xb6e42990]
/lib/arm-linux-gnueabihf/libc.so.6(__default_sa_restorer_v2+0x0)[0xb690e5b0]
../../projects/setiathome.berkeley.edu/setiathome_v7(+0x6ad68)[0xb6f63d68]
../../projects/setiathome.berkeley.edu/setiathome_v7(+0x27498)[0xb6f20498]
../../projects/setiathome.berkeley.edu/setiathome_v7(+0x22b78)[0xb6f1bb78]
../../projects/setiathome.berkeley.edu/setiathome_v7(+0x293cc)[0xb6f223cc]
../../projects/setiathome.berkeley.edu/setiathome_v7(+0x29724)[0xb6f22724]
../../projects/setiathome.berkeley.edu/setiathome_v7(main+0x21c)[0xb6f00508]
/lib/arm-linux-gnueabihf/libc.so.6(__libc_start_main+0x114)[0xb68f7294]

Exiting...

</stderr_txt>
]]>

Claggy