[Bug 96344] X locks up on start since commit e8b38ca202fbe8c28

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Bug ID 96344
Summary X locks up on start since commit e8b38ca202fbe8c28
Product Mesa
Version git
Hardware Other
OS All
Status NEW
Severity major
Priority medium
Component Drivers/Gallium/radeonsi
Assignee dri-devel@lists.freedesktop.org
Reporter EoD@xmw.de
QA Contact dri-devel@lists.freedesktop.org

My X-server (soft-)locks up after commit e8b38ca202fbe8c28. I used startx to
start the server.

X.Org X Server 1.17.4
Release Date: 2015-10-28
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.6.0-gentoo x86_64 Gentoo
Current Operating System: Linux 4.6.0-gentoo #1 SMP Fri May 20 11:29:35 CEST
2016 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.6.0-gentoo root=/dev/sda3 ro
loglevel=4
Build Date: 02 June 2016  08:03:28PM

Current version of pixman: 0.32.8
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Jun  2 22:49:56 2016
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(II) [KMS] Kernel modesetting enabled.
Require Open GLES2.0 or later.
X: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion
`key->initialized' failed.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
Couldn't get a file descriptor referring to the console


After bisecting, the following commits seems to be the cause:

e8b38ca202fbe8c281aeb81a4b64256983f185e0 is the first bad commit
commit e8b38ca202fbe8c281aeb81a4b64256983f185e0
Author: Plamena Manolova <plamena.manolova@intel.com>
Date:   Tue May 31 17:32:38 2016 +0100

    egl: Check if API is supported when using eglBindAPI.

    According to the EGL specifications before binding an API
    we must check whether it's supported first. If not eglBindAPI
    should return EGL_FALSE and generate a EGL_BAD_PARAMETER error.

    Signed-off-by: Plamena Manolova <plamena.manolova@intel.com>
    Reviewed-by: Brian Paul <brianp@vmware.com>


I have two dGPUs in my system:
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Tonga XT / Amethyst XT [Radeon R9 380X / R9 M295X Mac Edition]
[1002:6938] (rev f1)
02:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Barts XT [Radeon HD 6870] [1002:6738]

If you need any more specific information, just let me know.


You are receiving this mail because:
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[Index of Archives]     [Linux DRI Users]     [Linux Intel Graphics]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux