AnsweredAssumed Answered

CodeXL segmentation fault on start - Ubuntu 14.04 - Radeon 390

Question asked by raymond.b on Nov 13, 2015
Latest reply on Dec 11, 2015 by cyhsu

I'm having what I believe is the same issue as CodeXL 1.8 Crashing - Debian. CodeXL crashes with a segmentation fault on Ubuntu 14.04 using a Radeon 390.

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffdf164700 (LWP 1405)]
[New Thread 0x7fffde963700 (LWP 1406)] 

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffde963700 (LWP 1406)]

0x00007fffece0ae2c in __GI___libc_free (mem=0x7fffffffe6f2) at malloc.c:2945 2945    
malloc.c: No such file or directory.

(gdb) bt
#0  0x00007fffece0ae2c in __GI___libc_free (mem=0x7fffffffe6f2) at malloc.c:2945
#1  0x00007ffff7e92acd in ?? () from /usr/lib64/libatiuki.so.1
#2  0x00007ffff7e92866 in ?? () from /usr/lib64/libatiuki.so.1
#3  0x00007ffff7e92590 in amdPcsGetStr () from /usr/lib64/libatiuki.so.1
#4  0x00007fffddfe05ba in ADL2_Graphics_Versions_Get () from /usr/lib/libatiadlxx.so
#5  0x00007ffff772602c in oaGetDriverVersion (driverError=@0x7fffde962ac0: -1) at /data/jenkins/workspace/CodeXL-1.8-Linux/release/CodeXL/1.8/CommonProjects/AMDTOSAPIWrappers/src/linux/oaDriver.cpp:130
#6  0x00007ffff6a3e155 in afSystemInformationCommand::getSystemInformationDataAsString (this=this@entry=0x7fffde962ba0, systemInformationStr=...)     at /data/jenkins/workspace/CodeXL-1.8-Linux/release/CodeXL/1.8/CommonProjects/AMDTApplicationFramework/commands/afSystemInformationCommand.cpp:3065
#7  0x00007ffff6a3e3c0 in afSystemInformationCommandThread::entryPoint (this=0x693fb0) at /data/jenkins/workspace/CodeXL-1.8-Linux/release/CodeXL/1.8/CommonProjects/AMDTApplicationFramework/commands/afSystemInformationCommand.cpp:51
#8  0x00007ffff7991887 in osThread::threadEntryPoint (pParam=0x693fb0) at /data/jenkins/workspace/CodeXL-1.8-Linux/release/CodeXL/1.8/CommonProjects/AMDTOSWrappers/src/linux/osThread.cpp:76
#9  0x00007fffec766182 in start_thread (arg=0x7fffde963700) at pthread_create.c:312 #10 0x00007fffece8247d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

 

I can't reply in the referenced thread but would like to provide more information (see attached system info dumps).

 

I'm also seeing a segmentation fault running the teapot example.

 

#0  0x0000000000000000 in ?? ()

#1  0x00007fffedb1f7af in ?? () from /usr/lib64/libamdocl64.so

#2  0x00007fffeda1eec4 in ?? () from /usr/lib64/libamdocl64.so

#3  0x00007fffeda1efd9 in ?? () from /usr/lib64/libamdocl64.so

#4  0x00007fffeda2ad0b in ?? () from /usr/lib64/libamdocl64.so

#5  0x00007fffed9ef19e in clCreateContext () from /usr/lib64/libamdocl64.so

#6  0x00000000004136fa in AMDTTeapotOCLSmokeSystem::initOpenCLResources (this=0x6c9590) at Examples/AMDTTeaPot/AMDTTeaPotLib/src/AMDTTeapotOCLSmokeSystem.cpp:1167

#7  0x0000000000414607 in AMDTTeapotOCLSmokeSystem::draw (this=0x6c9590, state=..., modelTransformation=..., deltaRot=0) at Examples/AMDTTeaPot/AMDTTeaPotLib/src/AMDTTeapotOCLSmokeSystem.cpp:1656

#8  0x000000000041cab9 in AMDTTeapotOGLCanvas::paintWindow (this=0x6d02b0) at Examples/AMDTTeaPot/AMDTTeaPotLib/src/AMDTTeapotOGLCanvas.cpp:438

#9  0x000000000041c2a4 in AMDTTeapotOGLCanvas::onPaint (this=0x6d02b0) at Examples/AMDTTeaPot/AMDTTeaPotLib/src/AMDTTeapotOGLCanvas.cpp:155

#10 0x000000000040cdda in GLWindow::draw (this=0x6c4a20) at Examples/AMDTTeaPot/AMDTTeaPot/src/GLWindow.cpp:98

#11 0x00000000004231cf in Fl_Gl_Window::flush() ()

#12 0x0000000000425c12 in Fl::flush() ()

#13 0x0000000000425e5d in Fl::wait(double) ()

#14 0x0000000000425fad in Fl::run() ()

#15 0x000000000040c29f in main (argc=1, argv=0x7fffffffe2e8) at Examples/AMDTTeaPot/AMDTTeaPot/src/Teapot.cpp:500

 

As can be seen in the 'glxinfo' the system previous had GTX 980s in. I'm not sure if that's related. We'll be re-imaging the server without the NVidia driver installation step to see if that gets us around the issues.

 

The box, as it's installed, executes our OpenCL kernels without issue.

Attachments

Outcomes