Created attachment 87891 [details] xorg log hardware: lenovo g505 / AMD A4-5000 / ChipID = 0x9832 system: xubuntu 13.10 / kernel 3.12-rc6 / stock xorg 1.14.3 / mesa10.0~git1310161456.6e444a+glvdpau~gd~r (oibaf) 1. without any conf files: (WW) RADEON(0): glamor requires Load "glamoregl" in Section "Module", disabling. (WW) RADEON(0): Direct rendering disabled (II) RADEON(0): Acceleration disabled and llvmpipe in glxinfo 2. with only the Load "glamoregl" in config - crash in libllvm: Loading extension GLX (II) [KMS] Kernel modesetting enabled. 'kabini' is not a recognized processor for this target (ignoring processor) 'kabini' is not a recognized processor for this target (ignoring processor) 'kabini' is not a recognized processor for this target (ignoring processor) 'kabini' is not a recognized processor for this target (ignoring processor) 'kabini' is not a recognized processor for this target (ignoring processor) Stack dump: 0. Running pass 'Function Pass Manager' on module 'tgsi'. 1. Running pass 'AMDGPU DAG->DAG Pattern Instruction Selection' on function '@main' (EE) (EE) Backtrace: (EE) 0: X (xorg_backtrace+0x3d) [0x7ffadfebb02d] (EE) 1: X (0x7ffadfd19000+0x1a5d99) [0x7ffadfebed99] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7ffadee19000+0xfbb0) [0x7ffadee28bb0] (EE) 3: /usr/lib/x86_64-linux-gnu/libLLVM-3.3.so.1 (_ZNK4llvm3EVT21getExtendedSizeInBitsEv+0x4) [0x7ffad7e93f44] Looks like this isn't #66359, since glx gets loaded after glamoregl (this wasn't the case with xorg-xserver 1.7 in xubuntu 13.04, but the crash was exactly the same)
Created attachment 87892 [details] gdb backtrace
A fix for this was recently pushed to the Mesa git repository. Can you fetch the latest version and re-test.
(In reply to comment #2) > A fix for this was recently pushed to the Mesa git repository. Can you > fetch the latest version and re-test. Today's git head works fine. I guess 9da4021626dd48a1cc25054d1d4009e098f4d97b did it, I should have retested with git head at once. Sorry for the noise.
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.