Bug 89564

Summary: Xorg server crashed with AMD Radeon R2 Graphics
Product: xorg Reporter: Alex <alexisborychowski>
Component: Driver/RadeonAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED INVALID QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Xorg Log file
none
Xorg configuration file
none
dmesg
none
Xorg Crash none

Description Alex 2015-03-13 07:04:07 UTC
Created attachment 114268 [details]
Xorg Log file

Hello,

Startx crashed with Radeon driver.

The workaround is to disable in xorg.conf the following option :

Option     "Accel" "False"

However by doing this, Xserver is running far too slow.
 
Thanks for your help in advance

Alexis
Comment 1 Alex 2015-03-13 07:06:05 UTC
Created attachment 114269 [details]
Xorg configuration file
Comment 2 smoki 2015-03-13 08:47:42 UTC
 Post output from 'dmesg' command.
Comment 3 Alex 2015-03-13 09:09:33 UTC
Created attachment 114278 [details]
dmesg

There you go, thanks !
Comment 4 Michel Dänzer 2015-03-13 09:37:08 UTC
The attached Xorg log file doesn't contain any trace of a crash. Can you attach another one corresponding to a crash?
Comment 5 Alex 2015-03-13 09:43:44 UTC
Created attachment 114280 [details]
Xorg Crash
Comment 6 Michel Dänzer 2015-03-13 09:57:03 UTC
Looks like Mesa wasn't built with --with-egl-platforms=[...,]drm[,...] .
Comment 7 Alex 2015-03-13 11:06:45 UTC
I tried to rebuild Mesa with the following parameters :
./configure --disable-llvm-shared-libs --with-dri-driverdir=/opt/xorg/lib/dri --prefix=/opt/xorg --with-egl-platforms=x11

Result is still the same

Result of configure is underneath.

Regards,
Alex

prefix: /opt/xorg
exec_prefix: ${prefix}
libdir: ${exec_prefix}/lib
includedir: ${prefix}/include


OpenGL: yes (ES1: no ES2: no)
OpenVG: no


OSMesa: no


DRI platform: drm
DRI drivers: i915 i965 nouveau r200 radeon swrast
DRI driver dir: /opt/xorg/lib/dri
GLX: DRI-based


EGL: yes
EGL platforms: x11
EGL drivers: builtin:egl_dri2


llvm: yes
llvm-config: /usr/local/bin/llvm-config
llvm-version: 3.3


Gallium: yes


Shader cache: yes
With SHA1 from: libgcrypt


Shared libs: yes
Static libs: no
Shared-glapi: yes


CFLAGS: -g -O2 -Wall -std=gnu99 -Werror=implicit-function-declaration -Werror=missing-prototypes -fno-strict-aliasing -fno-builtin-memcmp
CXXFLAGS: -g -O2 -Wall -fno-strict-aliasing -fno-builtin-memcmp
Macros: -DUSE_EXTERNAL_DXTN_LIB=1 -D_GNU_SOURCE -DUSE_SSE41 -DNDEBUG -DUSE_X86_64_ASM -DHAVE_XLOCALE_H -DHAVE_STRTOF -DHAVE_DLOPEN -DHAVE_POSIX_MEM
ALIGN -DHAVE_LIBDRM -DGLX_USE_DRM -DHAVE_LIBUDEV -DGLX_INDIRECT_RENDERING -DGLX_DIRECT_RENDERING -DHAVE_ALIAS -DHAVE_DRI3 -DHAVE_MINCORE -DHAVE_LLVM=0x0303 -DLLVM_V
ERSION_PATCH=0


LLVM_CFLAGS: -I/usr/local/include -D_DEBUG -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS
LLVM_CXXFLAGS: -I/usr/local/include -D_DEBUG -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -fno-rtti
LLVM_CPPFLAGS: -I/usr/local/include -D_DEBUG -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS


PYTHON2: python2


Run 'make' to build Mesa
Comment 8 Alex 2015-03-13 18:56:06 UTC
Problem fixed !

I actually have to create glamor.conf on /opt/xorg/share/X11/xorg.conf.d

And add the following lines :

Section "Module"
        Load  "dri2"
        Load  "glamoregl"
EndSection
Section "Device"

    Identifier "radeon"
    Driver "radeon"
    Option "AccelMethod" "glamor"

EndSection

Best regards,
Alex
Comment 9 Michel Dänzer 2015-03-14 06:43:54 UTC
(In reply to Alex from comment #8)
> I actually have to create glamor.conf on /opt/xorg/share/X11/xorg.conf.d
> 
> And add the following lines :

That isn't necessary if you use glamor from xserver instead of from the obsolete standalone glamor tree. As a bonus, you'll get much better performance. :)

Anyway, no bug here, resolving.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.