Showing results for 
Search instead for 
Did you mean: 

Archives Discussions

Journeyman III

Catalyst 12.1 and Opencl

Hi I have 2 Radeon 6990's which I use mainly for bitmining. I just tried updating to 12.1 and I am having issues with OpenCL. I get segmentation faults with all the SDK 2.6 examples except for HelloCL. All the programs quit with error 6. Can anyone help to troubleshoot this issue as I really like the 3D performance gain from this driver compared to the 11.5 + SDK 2.4 I just upgraded from.

ImageBandwidth[7537]: segfault at fffffffffffffff8 ip 00007fa049346006 sp 00007fa043405df0 error 6 in[7fa0492a9000+e8000]

2 Replies

Re: Catalyst 12.1 and Opencl

what is your distro? and can you try backtrace it with gdb?

also it look similiar to this

Journeyman III

Re: Catalyst 12.1 and Opencl

Thanks for the quick response nou and yes it does look very similar to the link you provided but I think you understand when I say formatting is not the option I am looking for. My Distro is Ubuntu 11.04. Here is my gdb backtrace:

(gdb) run

Starting program: /opt/AMDAPP/samples/opencl/bin/x86_64/SimpleGL

[Thread debugging using libthread_db enabled]

Platform 0 : Advanced Micro Devices, Inc.

Platform found : Advanced Micro Devices, Inc.

Selected Platform Vendor : Advanced Micro Devices, Inc.

Device 0 : Cayman Device ID is 0x10b3860

Device 1 : Cayman Device ID is 0x10b60b0

Device 2 : Cayman Device ID is 0x10b8980

Device 3 : Cayman Device ID is 0x10bb240

Number of displays 4

glXCreateContextAttribsARB 0x7ffff7354080

Number of interoperable devices 1

Interop Device ID is 0x10b3860

[New Thread 0x7fffed8f9700 (LWP 10744)]

Program received signal SIGSEGV, Segmentation fault.

[Switching to Thread 0x7fffed8f9700 (LWP 10744)]

0x00007ffff6c3d006 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() () from /usr/lib/x86_64-linux-gnu/

All examples seen to segfault at this point. Thanks!

I removed the old SDK environment variable from my .bashrc so I am at a loss as to what is wrong.

Here is a backtrace as well as was requested on the other similar link.

(gdb) backtrace

#0  0x00007ffff6c3d006 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() () from /usr/lib/x86_64-linux-gnu/

#1  0x00007ffff37eae61 in ?? () from /home/hair/AMD-APP-SDK-v2.4-lnx64/lib/x86_64/

#2  0x00007ffff37eb539 in ?? () from /home/hair/AMD-APP-SDK-v2.4-lnx64/lib/x86_64/

#3  0x00007ffff37f3af5 in ?? () from /home/hair/AMD-APP-SDK-v2.4-lnx64/lib/x86_64/

#4  0x00007ffff37f6777 in ?? () from /home/hair/AMD-APP-SDK-v2.4-lnx64/lib/x86_64/

#5  0x00007ffff37bfa0d in ?? () from /home/hair/AMD-APP-SDK-v2.4-lnx64/lib/x86_64/

#6  0x00007ffff3810c47 in ?? () from /home/hair/AMD-APP-SDK-v2.4-lnx64/lib/x86_64/

#7  0x00007ffff37d3ef7 in ?? () from /home/hair/AMD-APP-SDK-v2.4-lnx64/lib/x86_64/

#8  0x00007ffff37d5d29 in ?? () from /home/hair/AMD-APP-SDK-v2.4-lnx64/lib/x86_64/

#9  0x00007ffff3800d96 in ?? () from /home/hair/AMD-APP-SDK-v2.4-lnx64/lib/x86_64/

#10 0x00007ffff37df0be in ?? () from /home/hair/AMD-APP-SDK-v2.4-lnx64/lib/x86_64/

#11 0x00007ffff380d04d in ?? () from /home/hair/AMD-APP-SDK-v2.4-lnx64/lib/x86_64/

#12 0x00007ffff381508c in ?? () from /home/hair/AMD-APP-SDK-v2.4-lnx64/lib/x86_64/

#13 0x00007ffff381319d in ?? () from /home/hair/AMD-APP-SDK-v2.4-lnx64/lib/x86_64/

#14 0x00007ffff7bc4d8c in start_thread () from /lib/x86_64-linux-gnu/

#15 0x00007ffff645704d in clone () from /lib/x86_64-linux-gnu/

#16 0x0000000000000000 in ?? ()

Ok seems that the older SDK is still pointed to by my environment. Where can I look to find the offending environment variable?

Edit: Sorry I guess only the second is a backtrace. I new to gdb 😉

Edit 2: Hardinfo shows that AMDAPPSDKROOT=/opt/AMDAPP is set and this is SDK 2.6. I dont understand why opencl programs are being pointed to the old SDK 2.4.