[Bug 1079607] New: 15.0B & TW20180203 Xorg terminates with error on Intel Eaglelake
http://bugzilla.opensuse.org/show_bug.cgi?id=1079607 Bug ID: 1079607 Summary: 15.0B & TW20180203 Xorg terminates with error on Intel Eaglelake Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs@forge.provo.novell.com Reporter: mrmazda@earthlink.net QA Contact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Blocker: --- Created attachment 759043 --> http://bugzilla.opensuse.org/attachment.cgi?id=759043&action=edit /var/lib/systemd/coredump/core.X.0....lz4 from TW host big41 TW20180102 worked as expected. Same failure with 3 installations across two machines, one with Q45, the other with G41. Same problem whether startx or KDM or KDM3 initializing X, or with xf86-video-intel installed. Xorg.0.log excerpt from G41 host big41. [ 4437.424] X.Org X Server 1.19.6 Release Date: 2017-12-20 [ 4437.427] X Protocol Version 11, Revision 0 [ 4437.428] Build Operating System: openSUSE SUSE LINUX [ 4437.429] Current Operating System: Linux big41 4.14.9-1-default #1 SMP PREEMPT Mon Dec 25 15:42:48 UTC 2017 (9423ca2) x86_64 [ 4437.429] Kernel command line: root=LABEL=sTWp23sv5 ipv6.disable=1 net.ifnames=0 noresume vga=791 video=1280x720@60 video=1024x768@60 video=1440x900@60 3 [ 4437.492] (EE) Failed to load module "intel" (module does not exist, 0) [ 4438.369] (II) modeset(0): Output HDMI-1 connected [ 4438.537] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects [ 4438.537] (EE) Backtrace: [ 4438.537] (EE) 0: X (xorg_backtrace+0x65) [0x561d49c94585] [ 4438.537] (EE) 1: X (0x561d49adf000+0x1b9339) [0x561d49c98339] [ 4438.537] (EE) 2: /lib64/libpthread.so.0 (0x7f0a6d869000+0x12270) [0x7f0a6d87b270] [ 4438.537] (EE) 3: /lib64/libc.so.6 (gsignal+0x110) [0x7f0a6d4e50d0] [ 4438.537] (EE) 4: /lib64/libc.so.6 (abort+0x151) [0x7f0a6d4e66b1] [ 4438.537] (EE) 5: /lib64/libc.so.6 (0x7f0a6d4af000+0x2e6fa) [0x7f0a6d4dd6fa] [ 4438.537] (EE) 6: /lib64/libc.so.6 (0x7f0a6d4af000+0x2e772) [0x7f0a6d4dd772] [ 4438.537] (EE) 7: X (0x561d49adf000+0x3ffe7) [0x561d49b1efe7] [ 4438.537] (EE) 8: X (0x561d49adf000+0xe354f) [0x561d49bc254f] [ 4438.537] (EE) 9: /usr/lib64/xorg/modules/extensions/libglx.so (0x7f0a6b0d8000+0x29307) [0x7f0a6b101307] [ 4438.537] (EE) 10: /usr/lib64/xorg/modules/extensions/libglx.so (0x7f0a6b0d8000+0x30246) [0x7f0a6b108246] [ 4438.537] (EE) 11: /usr/lib64/xorg/modules/extensions/libglx.so (0x7f0a6b0d8000+0x27db5) [0x7f0a6b0ffdb5] [ 4438.537] (EE) 12: X (InitExtensions+0x3d) [0x561d49ba5edd] [ 4438.537] (EE) 13: X (0x561d49adf000+0x5809f) [0x561d49b3709f] [ 4438.537] (EE) 14: /lib64/libc.so.6 (__libc_start_main+0xea) [0x7f0a6d4cff4a] [ 4438.537] (EE) 15: X (_start+0x2a) [0x561d49b20f3a] Fatal server error: [ 4438.537] (EE) Caught signal 6 (Aborted). Server aborting [ 4438.556] (EE) Server terminated with error (1). Closing log file. Partial package status on host gx780: | Mesa-demo | package | 8.3.0-3.3 | x86_64 | OSS | Mesa-dri-nouveau | package | 18.0.0-185.1| x86_64 | OSS | Mesa-libGLESv1_CM1 | package | 18.0.0-185.1| x86_64 | OSS | Mesa-libOpenCL | package | 18.0.0-185.1| x86_64 | OSS | Mesa-libd3d | package | 18.0.0-185.1| x86_64 | OSS | Mesa-libva | package | 18.0.0-185.1| x86_64 | OSS | glxosd | package | 3.2.2-2.1 | x86_64 | OSS | glxosd-nvidia-plugin | package | 3.2.2-2.1 | noarch | OSS | glxosd-sensors-plugin | package | 3.2.2-2.1 | noarch | OSS | libOSMesa8 | package | 18.0.0-185.1| x86_64 | OSS | libva-glx2 | package | 2.0.0-2.1 | x86_64 | OSS | libva-utils | package | 2.0.0-2.1 | x86_64 | OSS | libva-vdpau-driver | package | 0.7.4-4.1 | x86_64 | OSS | libvacuumutils37 | package | 1.3.0+git151| x86_64 | OSS | libvala-0_38-0 | package | 0.38.6-1.1 | x86_64 | OSS | libvaladoc-0_38-0 | package | 0.38.6-1.1 | x86_64 | OSS | libvamp-hostsdk3 | package | 2.7.1-1.2 | x86_64 | OSS | libvamp-sdk2 | package | 2.7.1-1.2 | x86_64 | OSS | libvarnishapi1 | package | 5.1.2-2.2 | x86_64 | OSS | rss-glx | package | 0.9.1-21.2 | x86_64 | OSS i | Mesa | package | 18.0.0-185.1| x86_64 | OSS i | Mesa-demo-x | package | 8.3.0-3.3 | x86_64 | OSS i | Mesa-dri | package | 18.0.0-185.1| x86_64 | OSS i | Mesa-gallium | package | 18.0.0-185.1| x86_64 | OSS i | Mesa-libEGL1 | package | 18.0.0-185.1| x86_64 | OSS i | Mesa-libGL1 | package | 18.0.0-185.1| x86_64 | OSS i | Mesa-libGLESv2-2 | package | 18.0.0-185.1| x86_64 | OSS i | Mesa-libglapi0 | package | 18.0.0-185.1| x86_64 | OSS i | libva-drm2 | package | 2.0.0-2.1 | x86_64 | OSS i | libva-wayland2 | package | 2.0.0-2.1 | x86_64 | OSS i | libva-x11-2 | package | 2.0.0-2.1 | x86_64 | OSS i | libva2 | package | 2.0.0-2.1 | x86_64 | OSS i | libvapoursynth | package | R38-3.3 | x86_64 | Packman i | libvapoursynth-40 | package | 40-1.2 | x86_64 | OSS i | libvapoursynth-script0| package | 40-1.2 | x86_64 | OSS i | libxcb-glx0 | package | 1.12-4.1 | x86_64 | OSS v | libvapoursynth-script0| package | R38-3.3 | x86_64 | Packman -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1079607
http://bugzilla.opensuse.org/show_bug.cgi?id=1079607#c1
Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=1079607
http://bugzilla.opensuse.org/show_bug.cgi?id=1079607#c2
Felix Miata
http://bugzilla.opensuse.org/show_bug.cgi?id=1079607
http://bugzilla.opensuse.org/show_bug.cgi?id=1079607#c3
--- Comment #3 from Felix Miata
http://bugzilla.opensuse.org/show_bug.cgi?id=1079607
http://bugzilla.opensuse.org/show_bug.cgi?id=1079607#c4
--- Comment #4 from Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=1079607
http://bugzilla.opensuse.org/show_bug.cgi?id=1079607#c5
Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=1079607
http://bugzilla.opensuse.org/show_bug.cgi?id=1079607#c6
--- Comment #6 from Michal Srb
This looks like X dectects two Intel GPUs. We had the issue, that with the automatic setup of two graphics drivers, where one is not a native one (like fbdev or modeset), this can lead to X crashes - *if* I remember correctly.
Michal may remember more. He investigated this.
That was bug #1068961. But that happens only if two drivers, one using RandR < 1.2 and other using RandR >= 1.2, are combined together. The crash would originate from some of the RandR functions. This seems to be different problem. I don't know if it is somehow caused/related to the two GPUs. I have checked the core dump and it is crashing during the GLX extension initialization. It calls `compIsAlternateVisual` to get some information from the Composite extension, but that eventually aborts because the `CompScreenPrivateKey` was never initialized. It was not initialized because the Composite extension is disabled: [ 4437.486] (**) Extension "Composite" is disabled First of all I wonder why is the Composite extension disabled. Is it intentional? But in any case, disabling it is a valid usage and X server should not crash. It seems that since commit f84e59a4f4 the GLX depends on Composite. So disabling Composite should disable GLX or it should skip the calls into Composite. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1079607
http://bugzilla.opensuse.org/show_bug.cgi?id=1079607#c7
Michal Srb
http://bugzilla.opensuse.org/show_bug.cgi?id=1079607
http://bugzilla.opensuse.org/show_bug.cgi?id=1079607#c8
Michal Srb
http://bugzilla.opensuse.org/show_bug.cgi?id=1079607
http://bugzilla.opensuse.org/show_bug.cgi?id=1079607#c9
--- Comment #9 from Felix Miata
http://bugzilla.opensuse.org/show_bug.cgi?id=1079607
http://bugzilla.opensuse.org/show_bug.cgi?id=1079607#c12
--- Comment #12 from Felix Miata
participants (1)
-
bugzilla_noreply@novell.com