Indigo Benchmark segmentation fault using opencl-mesa (open-source ATI)

Come here for help & support.
Post Reply
3 posts • Page 1 of 1
jamespharvey20
Posts: 2
Joined: Sun Oct 07, 2018 1:16 pm

Indigo Benchmark segmentation fault using opencl-mesa (open-source ATI)

Post by jamespharvey20 » Tue Oct 09, 2018 8:31 pm

IndigoBenchmark_x64_v4.0.64 works fine on Arch Linux, if I use Arch's opencl-amd package. I'm running the open-source AMDGPU driver, not the proprietary AMDGPU-PRO one. The opencl-amd package extracts the OpenCL libraries only from AMDGPU-PRO, and allows them to run with the open-source AMDGPU driver.

If I switch from the opencl-amd proprietary package to opencl-mesa, IndigoBenchmark crashes. Part of what I'm interested in seeing is how the open-source and proprietary OpenCL packages compare. Furthermore, mesa development is continuing, and it looks like AMDGPU-PRO is somewhat being given up on as a failure and is going to be replaced with AMDVLK, which I don't even know if that's going to be pure Vulkan or if it does or will include OpenCL support.

I'm running: linux 4.18.12.arch1-1, xf86-video-amdgpu 18.1.0-1, mesa 18.2.2-1, opencl-mesa 18.2.2-1, xorg-server 1.20.1-1, and plasma-desktop 5.13.5-1.

I made a bugreport on opencl-mesa here: https://bugs.freedesktop.org/show_bug.cgi?id=108272

Attached there is output from clinfo, lspci, glxinfo, and a gdb backtrace of the crash which is: https://bugs.freedesktop.org/attachment.cgi?id=141935

The pertinent part seems to be:

-----
#0 0x00007ffff6465bb5 in __memmove_sse2_unaligned_erms () from /usr/lib/libc.so.6
...
#14 0x00007fffb403ec15 in clGetPlatformIDs () from /usr/lib/libOpenCL.so
#15 0x0000000000993a96 in OpenCL::queryDevices() ()
#16 0x000000000099773f in getGlobalOpenCL() ()
#17 0x000000000068d88e in Indigo::HardwareInfoDLLAPI::queryOpenCLDevices() ()
-----

They have (and will probably have more) questions about how IndigoBenchmark is linked. I started with them, but I'm not sure if the bug is actually in their code or Indigo's. I lean toward theirs since with the opencl-amd package, there's no crash.

What version of LLVM is this linked against? Arch has LLVM 7.0.0. Perhaps that leads toward what the issue is.

User avatar
OnoSendai
Developer
Posts: 6160
Joined: Sat May 20, 2006 6:16 pm
Location: Newcastle upon Tyne, UK
Contact:

Re: Indigo Benchmark segmentation fault using opencl-mesa (open-source ATI)

Post by OnoSendai » Thu Oct 11, 2018 10:32 pm

We're statically linking with LLVM 3.4 on Linux currently.

jamespharvey20
Posts: 2
Joined: Sun Oct 07, 2018 1:16 pm

Re: Indigo Benchmark segmentation fault using opencl-mesa (open-source ATI)

Post by jamespharvey20 » Thu Nov 01, 2018 4:06 pm

Do you guys think this is a problem running with LLVM 7.0.0, or do you think it's an opencl-mesa issue?

Is there any way to release a version statically linked against 7.0.0?

Again, IndigoBenchmark runs fine on up to date Arch Linux using LLVM 7.0.0, as long as the opencl-amd package is used. (Which is the extracted OpenCL libraries from AMDGPU-PRO, that runs on the opensource AMDGPU driver.)

It's only when attempting to use opencl-mesa that IndigoBenchmark crashes this way.

From the backtrace, it doesn't exactly look like it's an opencl-mesa caused crash. It almost does seem like IndigoBenchmark might be making an LLVM call in a different way with opencl-mesa, but maybe running 7.0.0 has nothing to do with it. Per their suggestion, I tried using an extremely short name string, and that didn't help.

Post Reply
3 posts • Page 1 of 1

Who is online

Users browsing this forum: No registered users and 1 guest