BRP4 Intel GPU app feedback thread

Bernd Machenschalk
Bernd Machenschalk
Moderator
Administrator
Joined: 15 Oct 04
Posts: 4308
Credit: 249847377
RAC: 32438

RE: OpenCL GPU RAM required

Quote:
OpenCL GPU RAM required min: 536870912.000000, supplied: 134217728

Well, yes. Too small memory. Nothing the project can do about that.

BM

Edit: but Beignet looks like an interesting idea. Is anybody else willing to try?

BM

Stef
Stef
Joined: 8 Mar 05
Posts: 206
Credit: 110568193
RAC: 0

Ah I see, debian testing

Ah I see, debian testing provides an old version of beignet that doesn't support Haswell. I'll test a recent version tomorrow.

Thank you.

Stef
Stef
Joined: 8 Mar 05
Posts: 206
Credit: 110568193
RAC: 0

Let's assume it's tomorrow

Let's assume it's tomorrow already.

http://einsteinathome.org/task/491322700

Claggy
Claggy
Joined: 29 Dec 06
Posts: 560
Credit: 2699403
RAC: 0

RE: I've installed beignet

Quote:

I've installed beignet and it is even detected by boinc!
OpenCL: Intel GPU 0: Intel(R) HD Graphics Haswell M (driver version 0.8.0, device version OpenCL 1.1 beignet 0.8.0, 128MB, 128MB available, 512 GFLOPS peak)

Now how do I get einstein running on this? :)


Urs at Lunatics got Boinc to detect his Intel GPU with beignet 1.1 on openSUSE 13.1:

Quote:
Mi 01 Apr 2015 06:30:06 CEST | | OpenCL: Intel GPU 0: Intel(R) HD Graphics IvyBridge GT2 (driver version 1.1, device version OpenCL 1.2 beignet 1.1, 2048MB, 2048MB available, 128 GFLOPS peak)

But it wasn't all good news:

Quote:
No luck with Luxmark and intel_beignet, some basics like clGetDeviceIDs(-1) or clBuildProgramm(-3) fail

Claggy

Claggy
Claggy
Joined: 29 Dec 06
Posts: 560
Credit: 2699403
RAC: 0

RE: Let's assume it's

Quote:

Let's assume it's tomorrow already.

http://einsteinathome.org/task/491322700

The stderr.txt for info:

Quote:

7.4.23

process exited with code 255 (0xff, -1)

../../projects/einstein.phys.uwm.edu/einsteinbinary_BRP6_1.52_x86_64-pc-linux-gnu__BRP6-Beta-opencl-intel_gpu: /usr/lib/x86_64-linux-gnu/libOpenCL.so.1: no version information available (required by ../../projects/einstein.phys.uwm.edu/einsteinbinary_BRP6_1.52_x86_64-pc-linux-gnu__BRP6-Beta-opencl-intel_gpu)
[23:05:30][2388][INFO ] Application startup - thank you for supporting Einstein@Home!
[23:05:30][2388][INFO ] Starting data processing...
/dev/dri/card0 not authenticated
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
open("/dev/dri/card2", O_RDWR) failed: No such file or directory
open("/dev/dri/card3", O_RDWR) failed: No such file or directory
open("/dev/dri/card4", O_RDWR) failed: No such file or directory
open("/dev/dri/card5", O_RDWR) failed: No such file or directory
open("/dev/dri/card6", O_RDWR) failed: No such file or directory
open("/dev/dri/card7", O_RDWR) failed: No such file or directory
open("/dev/dri/card8", O_RDWR) failed: No such file or directory
open("/dev/dri/card9", O_RDWR) failed: No such file or directory
open("/dev/dri/card10", O_RDWR) failed: No such file or directory
open("/dev/dri/card11", O_RDWR) failed: No such file or directory
open("/dev/dri/card12", O_RDWR) failed: No such file or directory
open("/dev/dri/card13", O_RDWR) failed: No such file or directory
open("/dev/dri/card14", O_RDWR) failed: No such file or directory
open("/dev/dri/card15", O_RDWR) failed: No such file or directory
/dev/dri/card0 not authenticated
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
open("/dev/dri/card2", O_RDWR) failed: No such file or directory
open("/dev/dri/card3", O_RDWR) failed: No such file or directory
open("/dev/dri/card4", O_RDWR) failed: No such file or directory
open("/dev/dri/card5", O_RDWR) failed: No such file or directory
open("/dev/dri/card6", O_RDWR) failed: No such file or directory
open("/dev/dri/card7", O_RDWR) failed: No such file or directory
open("/dev/dri/card8", O_RDWR) failed: No such file or directory
open("/dev/dri/card9", O_RDWR) failed: No such file or directory
open("/dev/dri/card10", O_RDWR) failed: No such file or directory
open("/dev/dri/card11", O_RDWR) failed: No such file or directory
open("/dev/dri/card12", O_RDWR) failed: No such file or directory
open("/dev/dri/card13", O_RDWR) failed: No such file or directory
open("/dev/dri/card14", O_RDWR) failed: No such file or directory
open("/dev/dri/card15", O_RDWR) failed: No such file or directory
GPU not found: type=intel_gpu, opencl_device_index=0, device_num=0
[23:05:30][2388][ERROR] Failed to get OpenCL platform/device info from BOINC (error: -1)!
[23:05:30][2388][ERROR] Demodulation failed (error: -1)!
23:05:30 (2388): called boinc_finish(-1)

]]>

Claggy

MPW
MPW
Joined: 1 Oct 12
Posts: 8
Credit: 3761682
RAC: 0

RE: Edit: but Beignet

Quote:

Edit: but Beignet looks like an interesting idea. Is anybody else willing to try?

Yes, me.

Ubuntu 14.04 64bit on an Intel(R) Core(TM) i7-3537U CPU. It's just a laptop, but should be fine for testing.

I manged to compile Beignet and Boinc detects the GPU:

Sa 04 Apr 2015 15:51:14 CEST |  | OpenCL: Intel GPU 0: Intel(R) HD Graphics IvyBridge M GT2 (driver version 1.1, device version OpenCL 1.2 beignet 1.1 (git-89bc765), 2048MB, 2048MB available, 128 GFLOPS peak)

Question 1: Beignet only supports OpenCL 1.1 right now, is that enough for Einstein@Home or does it need OpenCL 1.2?

Question 2: If 1.1 is enough, how do I proceed to try it out?

Greetings
MPW

Bernd Machenschalk
Bernd Machenschalk
Moderator
Administrator
Joined: 15 Oct 04
Posts: 4308
Credit: 249847377
RAC: 32438

OpenCL 1.1 should be fine in

OpenCL 1.1 should be fine in principle. However I think the current project plan class won't deliver work, as "Intel(R) HD Graphics IvyBridge" isn't recognized. You'll need an app_info.xml file.

However Claggy's post shows that something doesn't work in the way that the device information is passed from the BOINC Client to the BOINC API in the application, the application can't find or access the device.

BM

BM

Bernd Machenschalk
Bernd Machenschalk
Moderator
Administrator
Joined: 15 Oct 04
Posts: 4308
Credit: 249847377
RAC: 32438

RE: /dev/dri/card0 not

Quote:
/dev/dri/card0 not authenticated

This might be an issue with permissions of the device node. Try something like

sudo chmod a+rw /dev/dri/card0

BM

BM

Stef
Stef
Joined: 8 Mar 05
Posts: 206
Credit: 110568193
RAC: 0

Permissions are ok. I just

Permissions are ok.

I just found this in the beignet documentation:
"Some unit test cases, maybe 20 to 30, fail on 4th Generation (HSW) platform. The 4th Generation Intel Core Processors's support requires some Linux kernel modification."
I don't know if that's what's missing.

And then there's:
"Almost all unit tests fail on Linux kernel 3.15/3.16"
uname: Debian 3.16.7-ckt7-1 (2015-03-01) x86_64 GNU/Linux

The driver itself seems to be fine:
clinfo: http://pastebin.com/5kjWezP1

So maybe I need to try a newer kernel?

Stef
Stef
Joined: 8 Mar 05
Posts: 206
Credit: 110568193
RAC: 0

I've installed a recent

I've installed a recent kernel and it seems to work one step further, but I get an other error message.
Seems to be a bug in beignet.

(Link?)

Quote:

7.4.23

process exited with code 255 (0xff, -1)

../../projects/einstein.phys.uwm.edu/einsteinbinary_BRP6_1.52_x86_64-pc-linux-gnu__BRP6-Beta-opencl-intel_gpu: /usr/lib/x86_64-linux-gnu/libOpenCL.so.1: no version information available (required by ../../projects/einstein.phys.uwm.edu/einsteinbinary_BRP6_1.52_x86_64-pc-linux-gnu__BRP6-Beta-opencl-intel_gpu)
[21:47:29][28122][INFO ] Application startup - thank you for supporting Einstein@Home!
[21:47:29][28122][INFO ] Starting data processing...
[21:47:29][28122][INFO ] Using OpenCL platform provided by: Intel
[21:47:29][28122][INFO ] Using OpenCL device "Intel(R) HD Graphics Haswell GT2 Desktop" by: Intel
store float %345, float addrspace(1)* %379, align 4, !tbaa !58
Illegal pointer which is not from a valid memory space.
Aborting...

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.