Created attachment 1267938 [details] coredump On Fedora 25 server with 4.10.6-200 kernel every desktop manager, LightDM, SDDM, XDM, KDM & GDM won't open, and seg fault. From /var/log/messages: Mar 31 13:59:49 systemd-coredump: Process 6407 (Xorg) of user 0 dumped core.#012#012Stack trace of thread 6407:#012#0 0x00000000b777ccf9 __kernel_vsyscall (linux-gate.so.1)#012#1 0x00000000b70c29a0 raise (libc.so.6)#012#2 0x00000000b70c4067 abort (libc.so.6)#012#3 0x0000000008205e2a OsAbort (Xorg)#012#4 0x00000000080c4aac ddxGiveUp (Xorg)#012#5 0x00000000080c4b4b AbortDDX (Xorg)#012#6 0x000000000820c5b2 AbortServer (Xorg)#012#7 0x000000000820cfcf FatalError (Xorg)#012#8 0x0000000008202aa8 OsSigHandler (Xorg)#012#9 0x00000000b777cd10 __kernel_rt_sigreturn (linux-gate.so.1)#012#10 0x00000000b74a0290 pci_device_next (libpciaccess.so.0)#012#11 0x00000000b74a0358 pci_device_find_by_slot (libpciaccess.so.0)#012#12 0x00000000b74a27a7 pci_device_vgaarb_init (libpciaccess.so.0)#012#13 0x00000000080e0575 xf86VGAarbiterInit (Xorg)#012#14 0x00000000080b7818 xf86BusConfig (Xorg)#012#15 0x00000000080c690d InitOutput (Xorg)#012#16 0x000000000807ea7a dix_main (Xorg)#012#17 0x0000000008066b4f main (Xorg)#012#18 0x00000000b70ac1c6 __libc_start_main (libc.so.6)#012#19 0x0000000008066b75 _start (Xorg) Mar 31 13:59:49 systemd: lightdm.service: Main process exited, code=exited, status=1/FAILURE Mar 31 13:59:49 systemd: lightdm.service: Unit entered failed state. Mar 31 13:59:49 systemd: lightdm.service: Failed with result 'exit-code'. Mar 31 13:59:49 systemd-coredump: Process 6421 (Xorg) of user 0 dumped core.#012#012Stack trace of thread 6421:#012#0 0x00000000b7791cf9 __kernel_vsyscall (linux-gate.so.1)#012#1 0x00000000b70d79a0 raise (libc.so.6)#012#2 0x00000000b70d9067 abort (libc.so.6)#012#3 0x0000000008205e2a OsAbort (Xorg)#012#4 0x00000000080c4aac ddxGiveUp (Xorg)#012#5 0x00000000080c4b4b AbortDDX (Xorg)#012#6 0x000000000820c5b2 AbortServer (Xorg)#012#7 0x000000000820cfcf FatalError (Xorg)#012#8 0x0000000008202aa8 OsSigHandler (Xorg)#012#9 0x00000000b7791d10 __kernel_rt_sigreturn (linux-gate.so.1)#012#10 0x00000000b74b5290 pci_device_next (libpciaccess.so.0)#012#11 0x00000000b74b5358 pci_device_find_by_slot (libpciaccess.so.0)#012#12 0x00000000b74b77a7 pci_device_vgaarb_init (libpciaccess.so.0)#012#13 0x00000000080e0575 xf86VGAarbiterInit (Xorg)#012#14 0x00000000080b7818 xf86BusConfig (Xorg)#012#15 0x00000000080c690d InitOutput (Xorg)#012#16 0x000000000807ea7a dix_main (Xorg)#012#17 0x0000000008066b4f main (Xorg)#012#18 0x00000000b70c11c6 __libc_start_main (libc.so.6)#012#19 0x0000000008066b75 _start (Xorg) Mar 31 13:59:49 systemd: lightdm.service: Main process exited, code=exited, status=1/FAILURE Mar 31 13:59:49 systemd: lightdm.service: Unit entered failed state. Mar 31 13:59:49 systemd: lightdm.service: Failed with result 'exit-code'. Mar 31 13:59:49 systemd: lightdm.service: Start request repeated too quickly. Mar 31 13:59:49 systemd: Failed to start Light Display Manager. Mar 31 13:59:49 systemd: lightdm.service: Unit entered failed state. Mar 31 13:59:49 systemd: lightdm.service: Failed with result 'start-limit-hit'. X.Org X Server 1.19.1 Release Date: 2017-01-11 [ 4041.272] X Protocol Version 11, Revision 0 [ 4041.273] Build Operating System: 4.10.0-0.rc4.git0.2.fc26.x86_64 [ 4041.273] Current Operating System: Linux curie.dsm.fordham.edu 4.10.6-200.fc25.i686+PAE #1 SMP Mon Mar 27 14:24:47 UTC 2017 i686 [ 4041.273] Kernel command line: BOOT_IMAGE=/vmlinuz-4.10.6-200.fc25.i686+PAE root=/dev/mapper/vg_curie-lv_root ro rd.md=0 rd.dm=0 SYSFONT=True KEYTABLE=us rd.lvm.lv=vg_curie/lv_swap rd.luks=0 rd.lvm.lv=vg_curie/lv_root LANG=en_US.UTF-8 rhgb quiet elevator=noop zswap.enabled=1 transparent_hugepage=madvise [ 4041.273] Build Date: 01 February 2017 02:03:59AM [ 4041.273] Build ID: xorg-x11-server 1.19.1-3.fc25 [ 4041.273] Current version of pixman: 0.34.0 [ 4041.273] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 4041.273] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 4041.273] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Mar 31 13:59:49 2017 [ 4041.274] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 4041.274] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 4041.275] (==) No Layout section. Using the first Screen section. [ 4041.275] (==) No screen section available. Using defaults. [ 4041.275] (**) |-->Screen "Default Screen Section" (0) [ 4041.275] (**) | |-->Monitor "<default monitor>" [ 4041.275] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 4041.275] (==) Automatically adding devices [ 4041.275] (==) Automatically enabling devices [ 4041.275] (==) Automatically adding GPU devices [ 4041.275] (==) Automatically binding GPU devices [ 4041.275] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 4041.275] (==) FontPath set to: catalogue:/etc/X11/fontpath.d, built-ins [ 4041.275] (==) ModulePath set to "/usr/lib/xorg/modules" [ 4041.275] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 4041.275] (II) Loader magic: 0x828c720 [ 4041.275] (II) Module ABI versions: [ 4041.275] X.Org ANSI C Emulation: 0.4 [ 4041.275] X.Org Video Driver: 23.0 [ 4041.275] X.Org XInput driver : 24.1 [ 4041.275] X.Org Server Extension : 10.0 [ 4041.278] (++) using VT number 1 [ 4041.278] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 4041.280] (II) xfree86: Adding drm device (/dev/dri/card0) [ 4041.281] (II) no primary bus or device found [ 4041.281] falling back to /sys/devices/pci0000:00/0000:00:1e.0/0000:09:0d.0/drm/card0 [ 4041.281] (II) LoadModule: "glx" [ 4041.282] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 4041.286] (II) Module glx: vendor="X.Org Foundation" [ 4041.286] compiled for 1.19.1, module version = 1.0.0 [ 4041.286] ABI class: X.Org Server Extension, version 10.0 [ 4041.286] (==) Matched modesetting as autoconfigured driver 0 [ 4041.286] (==) Matched fbdev as autoconfigured driver 1 [ 4041.286] (==) Matched vesa as autoconfigured driver 2 [ 4041.286] (==) Assigned the driver to the xf86ConfigLayout [ 4041.286] (II) LoadModule: "modesetting" [ 4041.287] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [ 4041.287] (II) Module modesetting: vendor="X.Org Foundation" [ 4041.287] compiled for 1.19.1, module version = 1.19.1 [ 4041.287] Module class: X.Org Video Driver [ 4041.287] ABI class: X.Org Video Driver, version 23.0 [ 4041.287] (II) LoadModule: "fbdev" [ 4041.288] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so [ 4041.288] (II) Module fbdev: vendor="X.Org Foundation" [ 4041.288] compiled for 1.18.99.901, module version = 0.4.3 [ 4041.288] Module class: X.Org Video Driver [ 4041.288] ABI class: X.Org Video Driver, version 23.0 [ 4041.288] (II) LoadModule: "vesa" [ 4041.288] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so [ 4041.288] (II) Module vesa: vendor="X.Org Foundation" [ 4041.288] compiled for 1.18.99.901, module version = 2.3.2 [ 4041.288] Module class: X.Org Video Driver [ 4041.288] ABI class: X.Org Video Driver, version 23.0 [ 4041.288] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 4041.289] (II) FBDEV: driver for framebuffer: fbdev [ 4041.289] (II) VESA: driver for VESA chipsets: vesa [ 4041.289] (II) modeset(0): using drv /dev/dri/card0 [ 4041.289] (WW) Falling back to old probe method for fbdev [ 4041.289] (II) Loading sub module "fbdevhw" [ 4041.289] (II) LoadModule: "fbdevhw" [ 4041.290] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so [ 4041.290] (II) Module fbdevhw: vendor="X.Org Foundation" [ 4041.290] compiled for 1.19.1, module version = 0.0.2 [ 4041.290] ABI class: X.Org Video Driver, version 23.0 [ 4041.290] (WW) Falling back to old probe method for vesa [ 4041.290] (EE) [ 4041.290] (EE) Backtrace: [ 4041.291] (EE) 0: /usr/libexec/Xorg (OsLookupColor+0x136) [0x8202b46] [ 4041.292] (EE) 1: ? (?+0x136) [0xb7791e45] [ 4041.292] (EE) 2: /lib/libpciaccess.so.0 (pci_device_next+0xf0) [0xb74b5290] [ 4041.293] (EE) 3: /lib/libpciaccess.so.0 (pci_device_find_by_slot+0x58) [0xb74b5358] [ 4041.293] (EE) 4: /lib/libpciaccess.so.0 (pci_device_vgaarb_init+0xd7) [0xb74b77a7] [ 4041.294] (EE) 5: /usr/libexec/Xorg (xf86ConfigPciEntity+0x4265) [0x80e47c5] [ 4041.294] (EE) 6: /usr/libexec/Xorg (xf86BusConfig+0xe8) [0x80b7818] [ 4041.294] (EE) 7: /usr/libexec/Xorg (InitOutput+0xabd) [0x80c690d] [ 4041.295] (EE) 8: /usr/libexec/Xorg (InitFonts+0x2aa) [0x807eaca] [ 4041.295] (EE) 9: /usr/libexec/Xorg (miPolyFillRect+0x2db) [0x8066dfb] [ 4041.296] (EE) 10: /lib/libc.so.6 (__libc_start_main+0xf6) [0xb70c11c6] [ 4041.296] (EE) 11: /usr/libexec/Xorg (_start+0x21) [0x8066b96] [ 4041.296] (EE) [ 4041.296] (EE) Segmentation fault at address 0x0 [ 4041.296] (EE) Fatal server error: [ 4041.296] (EE) Caught signal 11 (Segmentation fault). Server aborting
From mailing list thread https://lists.freedesktop.org/archives/xorg/2017-April/058693.html and upstream bug: lspci -v -s 09:0d.0 09:0d.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV100 [Radeon 7000 / Radeon VE] (prog-if 00 [VGA controller]) Subsystem: Dell PowerEdge 1850 Embedded Radeon 7000/VE Flags: bus master, VGA palette snoop, stepping, medium devsel, latency 32, IRQ 18
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.