gdm[17077]: WARNING: gdm_slave_xioerror_handler : Fatal X error

Using a :
01:00.0 VGA compatible controller: nVidia Corporation GeForce 7600 GT (rev a2)

similar issue here:

X.Org X Server 1.6.0
Release Date: 2009-2-25
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-23-server i686 Ubuntu
Current Operating System: Linux ntp-dp 2.6.28-15-server #49-Ubuntu SMP Tue Aug 18 19:30:06 UTC 2009 i686
Build Date: 09 April 2009 02:10:02AM
xorg-server 2:1.6.0-0ubuntu14 (<email address hidden>)
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: Mon Aug 24 12:21:13 2009
(==) Using config file: "/etc/X11/xorg.conf"
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server

Backtrace:
0: /usr/X11R6/bin/X(xorg_backtrace+0x3b) [0x813518b]
1: /usr/X11R6/bin/X(xf86SigHandler+0x55) [0x80c7be5]
2: [0xb7f2a400]
Saw signal 11. Server aborting.
ddxSigGiveUp: Closing log
ddxSigGiveUp: re-raising 11

and

X.Org X Server 1.6.0
Release Date: 2009-2-25
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-23-server i686 Ubuntu
Current Operating System: Linux ntp-dp 2.6.28-11-server #42-Ubuntu SMP Fri Apr 17 02:48:10 UTC 2009 i686
Build Date: 09 April 2009 02:10:02AM
xorg-server 2:1.6.0-0ubuntu14 (<email address hidden>)
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.1.log", Time: Thu Apr 30 09:29:09 2009
(==) Using config file: "/etc/X11/xorg.conf.failsafe"
error setting MTRR (base = 0xd5000000, size = 0x00e00000, type = 1) Invalid argument (22)
(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
error setting MTRR (base = 0xd5000000, size = 0x00e00000, type = 1) Invalid argument (22)

Backtrace:
0: /usr/X11R6/bin/X(xorg_backtrace+0x3b) [0x813518b]
1: /usr/X11R6/bin/X(xf86SigHandler+0x55) [0x80c7be5]
2: [0xb7f59400]
3: /usr/lib/xorg/modules//libshadow.so(shadowRemove+0x4e) [0xb66fdeee]
4: /usr/lib/xorg/modules//libshadow.so [0xb66fe3a4]
5: /usr/X11R6/bin/X [0x80c6a07]
6: /usr/X11R6/bin/X [0x811289c]
7: /usr/X11R6/bin/X [0x811ec9c]
8: /usr/X11R6/bin/X [0x81254fc]
9: /usr/X11R6/bin/X [0x80cf45e]
10: /usr/lib/xorg/modules/drivers//vesa_drv.so [0xb688ebc2]
11: /usr/X11R6/bin/X [0x80c76db]
12: /usr/X11R6/bin/X [0x816272b]
13: /usr/X11R6/bin/X [0x80e1958]
14: /usr/X11R6/bin/X [0x80cc073]
15: /usr/X11R6/bin/X [0x814bb35]
16: /usr/X11R6/bin/X [0x817cd5c]
17: /usr/X11R6/bin/X [0x814589b]
18: /usr/X11R6/bin/X(main+0x44c) [0x807237c]
19: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7b2a775]
20: /usr/X11R6/bin/X [0x80717a1]
Saw signal 11. Server aborting.
ddxSigGiveUp: Closing log
ddxSigGiveUp: re-raising 11

Hardware:
Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
VGA compatible controller: nVidia Corporation Quadro NVS 140M (rev a1)
on Lenovo T61

news:
I haven't fixed it :( Pretty anoying

1st try
I deactivated compiz so only metacity was running.

xinit: connection to X server lost.

waiting for X server to shut down
Backtrace:
0: /usr/bin/X(xorg_backtrace+0x3b) [0x813518b]
1: /usr/bin/X(xf86SigHandler+0x55) [0x80c7be5]
2: [0xb7f90400]
3: /usr/lib/xorg/modules//libshadow.so(shadowRemove+0x4e) [0xb66daeee]
4: /usr/lib/xorg/modules//libshadow.so [0xb66db3a4]
5: /usr/bin/X [0x80c6a07]
6: /usr/bin/X [0x811289c]
7: /usr/bin/X [0x811ec9c]
8: /usr/bin/X [0x81254fc]
9: /usr/bin/X [0x80cf45e]
10: /usr/lib/xorg/modules/drivers//vesa_drv.so [0xb685ebc2]
11: /usr/bin/X [0x80c76db]
12: /usr/bin/X [0x816272b]
13: /usr/bin/X [0x80e1958]
14: /usr/bin/X [0x80cc073]
15: /usr/bin/X [0x814bb35]
16: /usr/bin/X [0x817cd5c]
17: /usr/bin/X [0x814589b]
18: /usr/bin/X(main+0x44c) [0x807237c]
19: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7b5d775]
20: /usr/bin/X [0x80717a1]
Saw signal 11. Server aborting.
ddxSigGiveUp: Closing log
ddxSigGiveUp: re-raising 11

xinit: unexpected signal 15.

2nd try
Now I installed the 185.18.36 driver.
Also activated compiz again, due to the previous error. Compiz seems not to be the issue.

(More infos on http://ubuntuforums.org/showthread.php?p=7864201)

Backtrace:
0: /usr/X11R6/bin/X(xorg_backtrace+0x3b) [0x813518b]
1: /usr/X11R6/bin/X(xf86SigHandler+0x55) [0x80c7be5]
2: [0xb7f67400]
Saw signal 11. Server aborting.
ddxSigGiveUp: Closing log
ddxSigGiveUp: re-raising 11

I had never such an unstable system like the ubuntu 9.04....

next crash

Backtrace:
0: /usr/X11R6/bin/X(xorg_backtrace+0x3b) [0x813518b]
1: /usr/X11R6/bin/X(xf86SigHandler+0x55) [0x80c7be5]
2: [0xb7f59400]
3: /usr/lib/xorg/modules//libshadow.so(shadowRemove+0x4e) [0xb66fdeee]
4: /usr/lib/xorg/modules//libshadow.so [0xb66fe3a4]
5: /usr/X11R6/bin/X [0x80c6a07]
6: /usr/X11R6/bin/X [0x811289c]
7: /usr/X11R6/bin/X [0x811ec9c]
8: /usr/X11R6/bin/X [0x81254fc]
9: /usr/X11R6/bin/X [0x80cf45e]
10: /usr/lib/xorg/modules/drivers//vesa_drv.so [0xb688ebc2]
11: /usr/X11R6/bin/X [0x80c76db]
12: /usr/X11R6/bin/X [0x816272b]
13: /usr/X11R6/bin/X [0x80e1958]
14: /usr/X11R6/bin/X [0x80cc073]
15: /usr/X11R6/bin/X [0x814bb35]
16: /usr/X11R6/bin/X [0x817cd5c]
17: /usr/X11R6/bin/X [0x814589b]
18: /usr/X11R6/bin/X(main+0x44c) [0x807237c]
19: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7b2a775]
20: /usr/X11R6/bin/X [0x80717a1]
Saw signal 11. Server aborting.
 ddxSigGiveUp: Closing log
 ddxSigGiveUp: re-raising 11

next crash also today see the log

yesterday two more crashes...

the log shows it's xorg crashing

ONE THING I'VE NOTICED IN MY CASE:

My laptop has a...breaking...power port. Therefore, it will come loose and show as charging / not charging (and switch between those over and over) in about .3 second intervals.

So if I have it plugged into the wall sometimes the screen will flicker like crazy and THEN it'll log me out (and then not allow me to type my login details...like it's locked up). If I catch it right at the beginning of the flickering (and jiggle the cord near the power port), it's alright. But could it be something to do with X receiving too many signals on the power source / status?

I don't know what has changed, it only recently started doing this crap. Possibly the power port getting worse, but...idk.

Thanks!

I am also having this problem (on karmic) . Xorg log says:

Backtrace:
0: /usr/bin/X(xorg_backtrace+0x3b) [0x8133d6b]
1: /usr/bin/X(xf86SigHandler+0x55) [0x80c7d35]
2: [0xa5a400]
Saw signal 11. Server aborting.
(II) Power Button: Close
(II) UnloadModule: "evdev"
(II) AT Translated Set 2 keyboard: Close
(II) UnloadModule: "evdev"
(II) Power Button: Close
(II) UnloadModule: "evdev"
(II) Macintosh mouse button emulation: Close
(II) UnloadModule: "evdev"
(II) Logitech USB-PS/2 Optical Mouse: Close
(II) UnloadModule: "evdev"
 ddxSigGiveUp: Closing log

on the syslog I find:

Nov 27 11:20:53 mogul acpid: client 1559[0:0] has disconnected
Nov 27 11:20:53 mogul acpid: client 1559[0:0] has disconnected
Nov 27 11:20:53 mogul acpid: client connected from 22729[0:0]
Nov 27 11:20:54 mogul acpid: client connected from 22729[0:0]
Nov 27 11:24:54 mogul acpid: client 22729[0:0] has disconnected
Nov 27 11:24:54 mogul acpid: client 22729[0:0] has disconnected
Nov 27 11:24:54 mogul acpid: client connected from 22729[0:0]
Nov 27 11:24:54 mogul acpid: client connected from 22729[0:0]

my video card:
01:00.0 VGA compatible controller: nVidia Corporation NV44 [Quadro NVS 285] (rev a1)
ii nvidia-glx-185 185.18.36-0ubuntu9 NVIDIA binary Xorg driver

When this happens, X crashes and then I am presented the login screen again...

Hi All,

Has the crash of vesa driver been fixed?
 I am facing the same crash when I press ctrl+alt+f1 after doing startx. My Xserver version is 1.6 and I am using a network mounted FS.
The Vesa driver version is xf86-video-vesa-2.1.0

Backtrace:
0: X(xorg_backtrace+0x34) [0x811c784]
1: X(xf86SigHandler+0x45) [0x80c0385]
2: [0xffffe420]
3: /usr/X11R6/lib/xorg/modules//libshadow.so(shadowRemove+0x44) [0xb7991e14]
4: /usr/X11R6/lib/xorg/modules//libshadow.so [0xb7992227]
5: X [0x80aaf05]
6: X [0x80fbab0]
7: X [0x8107121]
8: X [0x810da3e]
9: X [0x80b935b]
10: /usr/X11R6/lib/xorg/modules/drivers//vesa_drv.so [0xb7b247b1]
11: X [0x80c9063]
12: X [0x8144457]
13: X [0x80ab9b0]
14: X [0x80c8c25]
15: X [0x81309bf]
16: X [0x815cb07]
17: X [0x812b09b]
18: /usr/X11R6/lib/xorg/modules/extensions//libglx.so [0xb7b69682]
19: X(main+0x433) [0x806b8b3]
20: /lib/libc.so.6(__libc_start_main+0xd0) [0xb7c32120]
21: X [0x806ad21]

Fatal server error:
Caught signal 11. Server aborting

Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

Regards,
Vandana

I can confirm this bug. The error is showing in /var/log/syslog... and I have this:
Video card - 00:02.0 VGA compatible controller: Intel Corporation 82915G/GV/910GL Integrated Graphics Controller (rev 04)
Intel Xorg Driver version 2:2.2.10.0+git20100108.4902f546-0ubuntu0sarvatt~karmic

More info in the attached logs. Logs traced in Thursday 14 Jan, from 14:45 to 15:05 hrs. GMT-6 Mexico City Time

15 minutes Syslog. Traced today.
More logs in progress

X.org.old
Traced exactly at 15:02 hrs. GMT-6 Mexico City time, exactly at the moment of "gdm_slave_xioerror_handler: Fatal X error - Restarting :0"

Also, apport generated this file at the morning, when this problem rises.
I don't know why I can't send it through Apport daemon submit
Founded in /var/crash

Also, there are this lines, founded in the Syslog right now.

Jan 14 17:40:21 labbd-desktop kernel: [ 96.761082] [drm:i915_gem_object_bind_to_gtt] *ERROR* Invalid object alignment requested 4096
Jan 14 17:40:21 labbd-desktop gdm[1160]: WARNING: gdm_slave_xioerror_handler: ha ocurrido un error fatal de X - Reiniciando :0

Maybe the X crashes are results and protections due to a X intel driver bug concerning the objects align?

Recent crash. Timestamp in Syslog lines.
Same DRM:i915_gem_object_bind_to_gtt error.

[This is an automatic notification.]

Hi Sancho,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 412113

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 412113 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/412113

Hi, the bug is not present in my installation of Lucid. So, in my Intel Corporation 82915G/GV/910GL Integrated Graphics, it has been solved. I worked with the hardware from the Lucid release day to this day. For me, it is no longer relevant.

@the-analist-3d - thanks for providing that info, but we would like to see it from the original reporter. We may want to send this bug report upstream, but upstream has a hard and fast rule that logs from someone other than the original reporter are not acceptable. The reason for that is that quite often with X.org bug reports, two people may *think* they have the same issue based on commonality of symptoms and/or hardware, but in truth they have separate issues and mixing the report and the files can cause the developers some confusion.

If this bug report seems not to be getting attention, I would encourage you to file a new bug report with this data, and simply reference this bug report in your bug description.

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.