I just noticed I'm getting errors in computing on all my WU's that run on my laptop. They are all cpu WU's as i dont run any gpu tasks on this machine. I rebooted but it made no difference.
I'm running Linux
How can i debug what is gong wrong?

It appears to be related to one particular application.

SETI@home v8 v8.00 x86_64-pc-linux-gnu

SIGSEGV: segmentation violation

The other application
SETI@home v8 v8.05 i686-pc-linux-gnu
is returning valid work.

Has this system been running OK & this is something that's just started, or is this a system you've recently started crunching with?

---

Grant
Darwin NT

Looking at your task results, the last successful one was using app SetiatHome V8 version 8.05, Then Boinc started using SetiatHome V8 version 8.00 which have errered out. Googling "Process got signal 11" and scanning the results, there was a mention of adding the ia32 library from an Einstein post or doing a project reset to solve the problem. I am a Windows person, so you may want to wait for the Linux gurus to chime in.

Hey Grant - Based on your post I setup an app_info.xml to run the 8.05 app (32bit) and it works, but I'm a bit mystified, I was running the x86_64 app for a long time and it was working fine. I must be missing an x86_64 library or something, but how to identify which on is apparently missing?

Hey Grant - Update - I switched to MBv8_8.05r3345_avx_linux64 and that’s working fine so far, I don’t know how i got off that but i must have done something and removed the original app_info.xml i had there. Its been quite awhile since i looked at the BOINC directories i just didn’t see the issue there until after I read your post.
I appear to be set now - thanks for your help!

Hey Grant - Based on your post I setup an app_info.xml to run the 8.05 app (32bit) and it works, but I'm a bit mystified, I was running the x86_64 app for a long time and it was working fine. I must be missing an x86_64 library or something, but how to identify which on is apparently missing?

As Darrell suggested, detaching and then reattaching to t he project would get it to re-download all the necessary files as you were running stock (although you lose all your present work). Running stock, the manager will try different applications to find out which one is fastest.

Running with the app_info.xml means you'll use just the specified application, but in the future when they upgrade the application again you'll need to manually download it & enter the correct details in to the app_info.xml. Running stock, the manager takes care of that for you.

If you're going to run with the app_info.xml it would be worth considering the Lunatics applications. AFAIK their CPU application is faster than the stock one, and there is a CUDA application under development that is much faster than any of the current stock applications.

---

Grant
Darwin NT

I run lunatics apps on my other two systems, but the laptop has an intel gpu (no gpu app as far as i know) so I only run cpu apps on that.

I run lunatics apps on my other two systems, but the laptop has an intel gpu (no gpu app as far as i know) so I only run cpu apps on that.

According to the applications list there is an application for your system.
Linux/x86_64 8.22 (opencl_intel_gpu_sah)
It looks like you would need to find a driver that supports OpenCL. As BOINC is not currently detecting the iGPU.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Interesting. I did a quick check and found this on my system
/usr/lib64/libOpenCL.so
/usr/lib64/libOpenCL.so.1
/usr/lib64/libOpenCL.so.1.2
I wonder if its just my boincmgr as the version is 7.1.0?

I run lunatics apps on my other two systems, but the laptop has an intel gpu (no gpu app as far as i know) so I only run cpu apps on that.

Generally it's not worth using the iGPU.
The iGPU and CPU share the same package, so the heat from one impacts on the other. They also share the same caches. Generally the output from a system with a iGPU is greatest when just crunching with the CPU, the slowdown of the CPU & iGPU due to thermal & cache issues results in less work being done than by the CPU alone. And the current iGPU hardware/drivers don't result in nearly enough computing ability to use just the iGPU and still get more work than the CPU alone can produce.

---

Grant
Darwin NT