I'm running boinc 6.2.14 on Ubuntu hardy heron on an old AMD Duron box with 115mb free RAM. I'm running kernel 2.6.24-26-generic. Two SETI@Home workunits have returned "error while computing" now. Where should I be looking to debug this?

I tried Googling, but not very hard; I've probably missed some forum posts. I see people having trouble with jaunty and newer kernels, but not hardy and 2.6.24. The Debian package page was not very helpful. Let me know if you have any suggestions.

skildude, those threads seem to be talking about server-side problems, which I'm pretty sure is not what's happening -- the error appears to be located with the boinc client or with my hardware. Am I missing something?

I hadn't seen the sig11 advice, Gundolf; thanks for the link, Jord.

I loaded up memtest86 and it's run seven passes over the last couple hours without incident. I'll leave it on overnight and try upgrading the boinc client if that doesn't flag any problems... though would that make a difference? All of the processing is done by the SETI component, which should have automatically retrieved the most recent version, right?

Guess I'll take a closer look at the issues people were reporting with jaunty; maybe something got backported into the hardy security updates or something.

To do so correctly, Tim will have to exit BOINC, then remove the app_info.xml file in his \BOINC\projects\setiathome.berkeley.edu\ directory, followed by a restart of BOINC and then resetting the project.

Else his BOINC will only go complain it cannot find the 5.12 application and try to download it (fruitlessly) from Seti. Jord

Ancient Astronaut Theorists can tell you that I do not help with tech questions via private message. Please use the forums for that.