Xorg.bin Segfault in OsLookupColor

[Bidski]

Just tried booting into F21 on my laptop today and found that I had no login screen, the screen with the Fedora logo shows up then nothing, just a grey speckled screen (the background for the login screen). Using <ctrl>+<alt>+2 produces no response.

I rebooted and edited the grub command so that it would boot into a tty. Then I tried to run startx, at which point I got a stacktrace in which there was a segfault in /usr/libexec/Xprg.bin (OsLookupColor+0x119).

Here is a link to the outputs of

journalctl --this-boot --priority=err &> journalctl.txt
dmesg --level=err,warn &> dmesg.txt
systemctl --failed &> systemctl.txt
startx

along with Xorg.0.log

I am running Fedora 21 with kernel 3.18.7-200.fc21.x86_64 (same error also happens on 3.18.6-200.fc21.x86_64) on a Dell Inspiron 5737.

Can anyone tell me what is happening here?

Thanks
Bidski

[Bidski]

Does anyone have any ideas about this?

I have seen other reports of a similar/the same issue on bugzilla.redhat here and here, but I havent seen anything yet that resembles a solution to this.

I have the following VGA controller

$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Intergrated Graphics Controller (rev 09)
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M / R9 M270X] (rev ff)

and Xorg versions

$ rpm -qa | grep xorg-x11
xorg-x11-drv-wacom-0.25.0-2.fc21.x86_64
xorg-x11-drv-nouveau-1.0.11-1.fc21.x86_64
xorg-x11-drv-ati-7.5.0-1.fc21.x86_64
xorg-x11-drv-qxl-0.1.2-1.fc21.x86_64
xorg-x11-drv-synaptics-1.8.1-4.fc21.x86_64
xorg-x11-xkb-utils-7.7-12.fc21.x86_64
xorg-x11-xauth-1.0.9-2.fc21.x86_64
xorg-x11-server-Xorg-1.16.3-2.fc21.x86_64
xorg-x11-xinit-1.3.4-3.fc21.x86_64
xorg-x11-server-Xwayland-1.16.3-2.fc21.x86_64
xorg-x11-drv-vmware-13.0.2-5.20140613git82c9b0c.fc21.x86_64
xorg-x11-server-utils-7.7-10.fc21.x86_64
xorg-x11-server-common-1.16.3-2.fc21.x86_64
xorg-x11-drv-vmmouse-13.0.0-13.fc21.x86_64
xorg-x11-utils-7.5-16.fc21.x86_64
xorg-x11-drv-vesa-2.3.2-19.fc21.x86_64
xorg-x11-fonts-ISO8859-1-100dpi-7.5-14.fc21.noarch
xorg-x11-drv-openchrome-0.3.3-12.fc21.x86_64
xorg-x11-drv-fbdev-0.4.3-19.fc21.x86_64
xorg-x11-proto-devel-7.7-12.fc21.noarch
xorg-x11-drv-evdev-2.9.0-3.fc21.x86_64
xorg-x11-font-utils-7.5-25.fc21.x86_64
xorg-x11-drv-intel-2.99.916-3.20141117.fc21.x86_64
xorg-x11-drv-modesetting-0.9.0-2.fc21.x86_64

Bidski

[Bidski]

Does anyone have any ideas here?

Is there a better place I could be asking about this problem?

Is there more/better diagnostic information I could be providing?

Would really like to get Fedora running on my laptop again.

Bidski

[Bidski]

Ok, I just added "nomodeset" to the boot line from the grub menu and everything boots well now.

Bidski

[zimon]

Maybe many did not look at your error logs because they were in Dropbox and one needs dropbox account to see them.

Next time, maybe use http://fpaste.org/ (I did not know about that either just last week.)

[Bidski]

Maybe many did not look at your error logs because they were in Dropbox and one needs dropbox account to see them.

Next time, maybe use http://fpaste.org/ (I did not know about that either just last week.)

Good point, thanks for that.

[Bidski]

Ok, so I am reviving this thread because this issue still exists.

When I used nomodeset I was able to boot and use Fedora except there were a couple of other issues that this raised that I was not happy with. For instance, the power management was poor (CPU fan remained off until temperature threshold was reached then the fan went on full blast for a while then back to off), the other issue was that the laptop would not go to sleep when lid was closed.

I have included links to the output of the following commands

journalctl --this-boot --priority=err &> journalctl.txt
dmesg --level=err,warn &> dmesg.txt
systemctl --failed &> systemctl.txt
rpm -qa | grep xorg-x11

As well as Xorg.0.log

The current installed kernel version is 4.0.4-202.fc21.x86_64.

Can anyone provide some insight into this issue please? I would really like to find a solution to this.

dmesg
systemctl
journalctl
Xorg.0.log
Xorg installed versions

Best Regards
Bidski

[skeet70]

Having a similar/the same issue here. On 4.0.4-303.fc22.x86_64.

Jun 24 12:23:33 compname google-chrome-beta.desktop[16594]: [16594:16627:0624/122333:ERROR:socket_stream.cc(208)] Closing stream with result -100
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE)
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE) Backtrace:
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE) 0: /usr/libexec/Xorg (OsLookupColor+0x139) [0x59a489]
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE) 1: /lib64/libc.so.6 (__restore_rt+0x0) [0x7fb54d7f4b1f]
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE) 2: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0xa834) [0x7fb548402c44]
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE) 3: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0xbc4f) [0x7fb54840545f]
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE) 4: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x1a86f) [0x7fb548422c1f]
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE) 5: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x1aac9) [0x7fb548423179]
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE) 6: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x28ada) [0x7fb54843ecfa]
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE) 7: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x2b74b) [0x7fb54844477b]
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE) 8: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x3f6a2) [0x7fb54846c802]
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE) 9: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x3fbc2) [0x7fb54846d132]
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE) 10: /usr/libexec/Xorg (DamageRegionAppend+0x3783) [0x525333]
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE) 11: /usr/libexec/Xorg (SendGraphicsExpose+0xeb3) [0x437d53]
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE) 12: /usr/libexec/Xorg (SendErrorToClient+0x2ff) [0x43a4ff]
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE) 13: /usr/libexec/Xorg (remove_fs_handlers+0x41b) [0x43e5fb]
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE) 14: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x7fb54d7e0790]
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE) 15: /usr/libexec/Xorg (_start+0x29) [0x4289c9]
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE) 16: ? (?+0x29) [0x29]
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE)
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE) Segmentation fault at address 0x7fb562e84f60
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE)
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: Fatal server error:
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE) Caught signal 11 (Segmentation fault). Server aborting
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE)
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE)
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: Please consult the Fedora Project support
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: at http://wiki.x.org
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: for help.
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE) Please also check the log file at "/home/xxx/.local/share/xorg/Xorg.0.log" for additional informati
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (EE)
Jun 24 12:24:11 compname /usr/libexec/gdm-x-session[14871]: (II) AIGLX: Suspending AIGLX clients for VT switch
Jun 24 12:24:12 compname /usr/libexec/gdm-x-session[14871]: (EE) Server terminated with error (1). Closing log file.

Followed by a few lines of everything else panicking because the xserver is gone. I'm able to boot, but I'll randomly get this crash throughout the day, which will kick me back to the login screen and I'll lose all my work.

[funkioto]

I have a similar thing, 4.0.8-300.fc22.x86_64

/usr/libexec/gdm-x-session: (EE)
/usr/libexec/gdm-x-session: (EE) Backtrace:
/usr/libexec/gdm-x-session: (EE) 0: /usr/libexec/Xorg (OsLookupColor+0x139) [0x59a489]
/usr/libexec/gdm-x-session: (EE) 1: /lib64/libc.so.6 (__restore_rt+0x0) [0x3621a34a4f]
/usr/libexec/gdm-x-session: (EE) 2: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x719e0
) [0x7f30183e4fa0]
/usr/libexec/gdm-x-session: (EE) 3: /usr/libexec/Xorg (AddTraps+0x4d72) [0x519f82]
/usr/libexec/gdm-x-session: (EE) 4: /usr/libexec/Xorg (SendErrorToClient+0x2ff) [0x43a4ff]
/usr/libexec/gdm-x-session: (EE) 5: /usr/libexec/Xorg (remove_fs_handlers+0x41b) [0x43e5fb]
/usr/libexec/gdm-x-session: (EE) 6: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x3621a20700]
/usr/libexec/gdm-x-session: (EE) 7: /usr/libexec/Xorg (_start+0x29) [0x4289c9]
/usr/libexec/gdm-x-session: (EE) 8: ? (?+0x29) [0x29]
/usr/libexec/gdm-x-session: (EE)
/usr/libexec/gdm-x-session: (EE) Segmentation fault at address 0x20028888
/usr/libexec/gdm-x-session: (EE)
/usr/libexec/gdm-x-session: Fatal server error:
/usr/libexec/gdm-x-session: (EE) Caught signal 11 (Segmentation fault). Server aborting
/usr/libexec/gdm-x-session: (EE)
/usr/libexec/gdm-x-session: (EE)
/usr/libexec/gdm-x-session: Please consult the Fedora Project support
/usr/libexec/gdm-x-session: at http://wiki.x.org
/usr/libexec/gdm-x-session: for help.
/usr/libexec/gdm-x-session: (EE) Please also check the log file at "/home/user/.local/share/xo
rg/Xorg.0.log" for additional information.
/usr/libexec/gdm-x-session: (EE)
/usr/libexec/gdm-x-session: (II) AIGLX: Suspending AIGLX clients for VT switch
/usr/libexec/gdm-x-session: (EE) Server terminated with error (1). Closing log file.

[greglarson]

I was able to work-around this problem by blacklisting a kernel module for the unused GPU in my configuration.

The bug at: https://bugzilla.redhat.com/show_bug.cgi?id=1172232 claims to be fixed, however, I am still seeing the Segmentation fault in OsLookupColor on an up-to-date Fedora 21. I think the problem still occurs on hardware configurations that have a multiple GPU, but with one disabled. For example on my system:

$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series]

Note that the Radeon GPU is disabled on my system.

By blacklisting the radeon kernel module, I was able to get my X server to start. This might also work for multi-GPU configurations with Nvidia.

There several ways to blacklist a kernel module. I used radeon.blacklist=yes on my kernel command line, as well as putting:
blacklist radeon
in /etc/modprobe.d/blacklist.conf

To check that the unwanted module is NOT there after a reboot, do: lsmod | grep radeon

Replace radeon with nvidia if that is your extra GPU.

[greglarson]

FYI: I re-tested on the same hardware with Fedora 22 (xorg-x11-server-Xorg-1.17.2-2.fc22.x86_64) and the problem no longer appears (with radeon kernel module loaded).

[nsnbm]

My experience with having two VGA controllers on one machine, an intel built into the motherboard, and an nvidia card on pci-e, in my case, resulted in no X at all on boot. The solution here was to enter the BIOS, (which was uefi though I was running a 32 bit f22) and turn off the intel card which was on the motherboard. Then X acted as expected. I realise this might be a different issue to the OP's but I mention it anyway.