[nvidia] X crash in compPaintWindowBackground

[Niklas Vanhainen]

Binary package hint: xserver-xorg

X sometimes crashes at random. I get a console for a few seconds then it starts up again to the gdm login window.

This is what the /var/log/Xorg.0.log file reports about the crash, everything priror to this has to do with the X startup.

Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x81) [0x80c3971]
1: [0xffffe420]
2: /usr/X11R6/bin/X [0x81541bb]
3: /usr/X11R6/bin/X(compPaintWindowBackground+0x6d) [0x8191b0d]
4: /usr/X11R6/bin/X(miClearToBackground+0x1b5) [0x8122415]
5: /usr/X11R6/bin/X(ProcClearToBackground+0xb6) [0x80825e6]
6: /usr/X11R6/bin/X(Dispatch+0x18f) [0x808693f]
7: /usr/X11R6/bin/X(main+0x485) [0x806e715]
8: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7cf88cc]
9: /usr/X11R6/bin/X(FontFileCompleteXLFD+0xa1) [0x806da51]

Fatal server error:
Caught signal 11. Server aborting

I'm using Ubuntu Edgy 6.10, kernel 2.6.17-10-386
It might also be of interest that I'm using the nvidia driver (1.0-9629) on a GeForce 6600GT. (this also happened before I installed the new driver though)
lspci reports: 05:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600 GT] (rev a2)

The version of the X server is: X Window System Version 7.1.1

[Niklas Vanhainen (niklas-vanhainen)]

Here is my xorg.conf

[Niklas Vanhainen (niklas-vanhainen)]

And here is the entire xorg log file.

[[sellout] (sellout4him)]

Identical issue only i am using an nvidia geforce 5200

Backtrace is almost identical as well, and x dies randomly, and usually never lasts longer than 5 mins.

[edschofield (schofield)]

I can confirm this bug with an Intel G965 X3000 GMA. I'm using xorg-server-core-1.1.1-0ubuntu13 and linux-2.6.20-6-generic. My architecture is AMD64.

A backtrace from /var/log/Xorg.0.log.old is similar to that of the original reporter:

Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x71) [0x487521]
1: /lib/libc.so.6 [0x2b9400cdbd40]
2: /usr/lib/xorg/modules/extensions/libGLcore.so(_mesa_update_draw_buffer_bounds+0x59) [0x2b94039bf5e9]
3: /usr/lib/xorg/modules/extensions/libGLcore.so [0x2b9403ada09d]
4: /usr/lib/xorg/modules/extensions/libglx.so [0x2b940208683b]
5: /usr/X11R6/bin/X(compPositionWindow+0x62) [0x550382]
6: /usr/X11R6/bin/X(ResizeChildrenWinSize+0x1bb) [0x43d77b]
7: /usr/X11R6/bin/X(miSlideAndSizeWindow+0x1af) [0x4e129f]
8: /usr/X11R6/bin/X(compResizeWindow+0xad) [0x55119d]
9: /usr/X11R6/bin/X(ConfigureWindow+0xb08) [0x43d238]
10: /usr/X11R6/bin/X(ProcConfigureWindow+0x96) [0x44e5d6]
11: /usr/X11R6/bin/X(Dispatch+0x1ba) [0x44ed4a]
12: /usr/X11R6/bin/X(main+0x455) [0x4379d5]
13: /lib/libc.so.6(__libc_start_main+0xf4) [0x2b9400cc88e4]
14: /usr/X11R6/bin/X(FontFileCompleteXLFD+0x231) [0x436cd9]

Fatal server error:
Caught signal 11. Server aborting

My xorg.conf is attached. I'm using the 'vesa' driver with a 1024x768 screen resolution. (The 'i810' driver unfortunately gives a blank screen.)

[edschofield (schofield)]

(All of these Xorg crashes I've experienced so far (about two per day) have occurred while using Firefox.)

[Matthew L. Dailey (matthew-l-dailey)]

I just wanted to add a "me, too." We've now seen this on three different machines (two different hardware setups). It seems to occur during graphically-intensive operations. In our case, it has occured both during Matlab figure generation and Tecplot drawing. One machine has an Intel 945G, and the other two have an nVidia NV18, so it doesn't appear to be related to the graphics card or drivers. I've enabled core dumps on my machines, so when and if it happens again, I may be able to upload a core file. In the meantime, I'll attach a couple of the X backtraces, just for some more examples.

[Matthew L. Dailey (matthew-l-dailey)]

I think this may be a duplicate of https://launchpad.net/ubuntu/+source/xorg-server/+bug/60288

I'll try the patches in this bug later in the week and see if they make a difference...

[Timo Aaltonen (tjaalton)]

Matthew: have you tried the patch from the other bug?

[Matthew L. Dailey (matthew-l-dailey)]

Sorry for the delayed update...any dri patches I could find had no effect in our situation. Our crashes seem related to glx and libglcore rather than dri. Disabling dri in xorg.conf had no effect on our crashes, either, but disabling glx did fix the crashes - of course any sort of graphical performance was gone. :-)

For our machines, the only workable solution was to install the binary drivers from nVidia (many thanks to Alberto Milone and his "Envy" script). On both our GeForce MX 440's and our FX 5200's this eliminated all crashes, and also gave us a huge performance boost with 3D apps.

On our one Intel (i810 driver), we could not reliably reproduce the crashes (although we can on the nVidias with the nv driver), so I think this may be an entirely different bug.

This probably isn't much help for solving this bug, but I hope it at least helps a little. If I run into anything more definitive or helpful, I'll pass it along...

[Bryce Harrington (bryce)]

bug 91351 has the same backtrace, but occurs on login after the splash screen.

User reports that he was able to get it to work by removing the following directory from his /etc/X11/xorg.conf file:

# /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType

The specific font package causing the problem for him seemed to be "ttf-arabeyes".

[Matti Lindell (mlind)]

I wonder if this is the same issue I'm having with feisty with both opensource and proprietary ATI drivers. Happens only when the screensaver has been active for some time though (random mode)

Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x81) [0x80c5d91]
1: [0xffffe420]
2: /usr/X11R6/bin/X(miSetShape+0x2fe) [0x812999e]
3: /usr/X11R6/bin/X [0x8134ad7]
4: /usr/X11R6/bin/X [0x8134f14]
5: /usr/X11R6/bin/X [0x81424ce]
6: /usr/X11R6/bin/X(Dispatch+0x19f) [0x808c61f]
7: /usr/X11R6/bin/X(main+0x495) [0x8074785]
8: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7db2ebc]
9: /usr/X11R6/bin/X(FontFileCompleteXLFD+0x1e1) [0x8073ab1]

Fatal server error:
Caught signal 11. Server aborting

[Luke Plant (spookylukey)]

Another "me too" -- similar backtrace to 'mlind', but not identical. I'm using Ubuntu Feisty with ubuntu's NVidia drivers and a GeForce 5200 FX card. The crashes happen randomly -- the only common thing I've found is it tends to be when I'm using Yakuake (KDE terminal), or just switching away from it, usually at the same time as doing something reasonable system intensive e.g. saving lots of data. I can go days without seeing this, then will happen twice in half an hour. I'm using Beryl as my window manager, in case that is relevant.

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c5d91]
1: [0xffffe420]
2: /usr/bin/X [0x81623ad]
3: /usr/bin/X [0x815ea9f]
4: /usr/bin/X(CompositeGlyphs+0x9a) [0x814c0fa]
5: /usr/bin/X [0x8153c0c]
6: /usr/bin/X [0x814f145]
7: /usr/bin/X [0x81424ce]
8: /usr/bin/X(Dispatch+0x19f) [0x808c61f]
9: /usr/bin/X(main+0x495) [0x8074785]
10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7cf3ebc]
11: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8073ab1]

[Diego Gaustein (gregorovius)]

Another "me too" here. Crashes are a little random, but AFAIK it only happens with Beryl enabled. Using latest nvidia-glx-new. I'm not sure if this happens with Compiz as I haven't used it much. I think this bug should be marked as critical.

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c5d91]
1: [0xffffe420]
2: /usr/bin/X [0x81623ad]
3: /usr/bin/X [0x815ea9f]
4: /usr/bin/X(CompositeGlyphs+0x9a) [0x814c0fa]
5: /usr/bin/X [0x8153c0c]
6: /usr/bin/X [0x814f145]
7: /usr/bin/X [0x81424ce]
8: /usr/bin/X(Dispatch+0x19f) [0x808c61f]
9: /usr/bin/X(main+0x495) [0x8074785]
10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7d66ebc]
11: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8073ab1]

Fatal server error:
Caught signal 11. Server aborting

[TuxFan (make)]

I have the same problem now after I've upgraded to Feisty. Didn't have stability problems with Edgy as the original poster. But then again, I'm using Kubuntu.

More of my backtraces and other findings can be seen in bug #108829 but here's my latest backtrace:

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c5d91]
1: [0xffffe420]
2: /usr/bin/X(FreeClientResources+0x85) [0x8075e65]
3: /usr/bin/X(CloseDownClient+0x1a8) [0x80863e8]
4: /usr/bin/X(Dispatch+0x2c6) [0x808c746]
5: /usr/bin/X(main+0x495) [0x8074785]
6: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7d00ebc]
7: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8073ab1]

Fatal server error:
Caught signal 11. Server aborting

[TuxFan (make)]

I tried commenting out the one font row from xorg.conf that Bryce mentioned, but it didn't help.

This time X just hanged, but sshd was killed (gkrellmd was still running though). Just before the hang I was trying to close one firefox window.I was able to login from normal terminals (Ctrl-Alt-F1..). After logging in there was few rows of some high ASCII garbage and when I tried to halt or reboot I got these errors:

/dev/.initramfs/progress_state: 1: Syntax error: EOF in backquote substitution
error: '/etc/init.d/rc' exited outside the expected code flow.

[Diego Gaustein (gregorovius)]

Just a comment: I've tried CompComm from the SVN packages build by Evandro and the same thing happens. Since I've disabled Beryl it hasn't happened anymore, so it's definitely related, at least in my case. If anyone is following this bug, I think it should be marked in Gutsy Milestones, considering the composite-by-default spec. Cheers.

[TuxFan (make)]

In my case it's definately not because of Beryl, since I don't have it. (And I've never even tried it.) And since this crashing seems to happen on different manufacturers graphics cards I don't think the problem is in those driversl...

There are two upstream bugs having same kind of backtraces:

https://bugs.freedesktop.org/show_bug.cgi?id=10995
https://bugs.freedesktop.org/show_bug.cgi?id=10973

And in the first one there's a comment: "I think this is an ubuntu bug, or at least was fixed in upstream Mesa since
then, I see it in gutsy.."

The second one has a list of steps which should make GNOME to crash, but since I have KDE I can't test if that bug is related to this one...

[TuxFan (make)]

I finally got tired of the crashing (three times a day isn't so nice...) and upgraded to Gutsy last week. So far I haven't had a single crash, so I guess my problem is fixed in Gutsy.

[Bryce Harrington (bryce)]

Compiz has received a LOT of attention for Gutsy, including many bug fixes.

Can one other person confirm that this behavior stops happening when upgrading to Gutsy? If so, we can close this bug as fixed.

Unfortunately it's not likely that this will be backported to Feisty, however Gutsy's release is coming up in a few months. :-)

[Matti Lindell (mlind)]

Although my backtrace looks bit different in comment #14, xserver stopped crashing for me too when I upgraded to gutsy.

[Bryce Harrington (bryce)]

Thanks mlind. I'll go ahead and close the bug. If anyone spots this behavior again on Gutsy, please enter a new bug report.

[TuxFan (make)]

Just one more note: this wasn't a compiz problem, since I don't even have it installed.

[Diego Gaustein (gregorovius)]

In my case it only happened with Compiz or Beryl activated. I'll try
installing the Gutsy beta and see if it still happens.

[Magnes (magnesus2)]

I have something like this:

Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x81) [0x80c5d91]
1: [0xffffe420]
2: /usr/lib/xorg/modules//libfb.so(fbComposite+0x57d) [0xb706df3d]
3: /usr/lib/xorg/modules/drivers//nvidia_drv.so(_nv000729X+0x498) [0xb71407b8]

Fatal server error:
Caught signal 11. Server aborting

It's happening in random moments, mostly when I use Firefox. I don't use Compiz/Beryl when it happens.
Looks like this bug - https://launchpad.net/ubuntu/+source/xorg-server/+bug/60288 - again.
My xserver-xorg-core version is 2:1.2.0-3ubuntu8

[Diego Gaustein (gregorovius)]

Still happening on Gutsy Beta asof 11-oct, only when Compiz is on. I'm not sure how many people have this problem, but it makes Compiz unusable to me, so the composite-by-default spec is not really acomplished =/

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c9581]
1: [0xffffe420]
2: /usr/bin/X [0x817e39d]
3: /usr/bin/X [0x817a9ef]
4: /usr/bin/X(CompositeGlyphs+0x9a) [0x816129a]
5: /usr/bin/X [0x8168f19]
6: /usr/bin/X [0x8164315]
7: /usr/bin/X [0x815754e]
8: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
9: /usr/bin/X(main+0x495) [0x8076f05]
10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7dd9050]
11: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]

Fatal server error:
Caught signal 11. Server aborting

[Magnes (magnesus2)]

For me random crashes stopped when I replaced damaged capacitor on the main board and changed not working properly power supply! It looks it had something to do with the hardware malfunction.

[Diego Gaustein (gregorovius)]

Well, in my case, everything works perfectly, including games, so it'd be
quite odd if it was a hardware issue.

On 10/12/07, Magnes <email address hidden> wrote:
>
> For me random crashes stopped when I replaced damaged capacitor on the
> main board and changed not working properly power supply! It looks it
> had something to do with the hardware malfunction.
>
> --
> X crash: FontFileCompleteXLFD+0xa1
> https://bugs.launchpad.net/bugs/71913
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Luke Plant (spookylukey)]

Another "me too" for Gutsy RC, with nvidia-glx-new

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c9581]
1: [0xffffe420]
2: /usr/bin/X [0x817e39d]
3: /usr/bin/X [0x817a9ef]
4: /usr/bin/X(CompositeGlyphs+0x9a) [0x816129a]
5: /usr/bin/X [0x8168f19]
6: /usr/bin/X [0x8164315]
7: /usr/bin/X [0x815754e]
8: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
9: /usr/bin/X(main+0x495) [0x8076f05]
10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d6f050]
11: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]

[Diego Gaustein (gregorovius)]

I'm sorry, but at least two of us are still experiencing this issue on Gutsy RC, so I'm marking this as confirmed again.

[Eddie Hung (eddieh)]

New Note 5

I can confirm a similar problem - I'm not sure if this is the same bug as described here, but here goes - firefox has been completely crashing my computer since I upgraded from Feisty to Gutsy a week or so ago (i.e. I can't switch VTs to find out what's going on, can't reset Xorg using Ctrl+Alt+Backspace - I have to Alt+SysReq+B to reboot my computer. I've noticed it most whenever I've been writing into text boxes (e.g. gmail) - which makes it even more frustrating!

I have the flash plugin installed from the official repos, and my Xorg.conf is the default configuration, albeit with the VNC module loaded, and I'm running the latest Gutsy in dual head mode (ATI card - so using xrandr).
I have reproduced the crash using two different firefox profiles - my main one with a handful of extensions, and a basic profile with no extensions at all - so I think we can rule profiles out.

I have a crash log I found in /var/crash which I've submitted, and gedit-ing it seems to bring my computer grinding to a halt - and so far I can't find any mention of a backtrace like what some of you have included: The only mention is:
Stacktrace: #0 0xffffe410 in ?? ()
StacktraceTop: ?? ()
And is it also worth mentioning that it also says that firefox-bin crashed with SIGSEGV?

Does any of this information seem familiar to anyone else?

[Eddie Hung (eddieh)]

I also forgot to mention that I am not using compiz or beryl...

[carpelo (carpelo)]

Another "Me too", with Gutsy and official NVIDIA drivers
Same Backtrace:

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c9581]
1: [0xffffe420]
2: /usr/bin/X [0x817e39d]
3: /usr/bin/X [0x817a9ef]
4: /usr/bin/X(CompositeGlyphs+0x9a) [0x816129a]
5: /usr/bin/X [0x8168f19]
6: /usr/bin/X [0x8164315]
7: /usr/bin/X [0x815754e]
8: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
9: /usr/bin/X(main+0x495) [0x8076f05]
10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d63050]
11: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]

Fatal server error:
Caught signal 11. Server aborting

[carpelo (carpelo)]

I forgot to mention that i do use compiz-fusion

[Bas van Schaik (bas-tuxes)]

Just a "me too" here. I'm also using Kubunto with Compiz, but didn't try switching Compiz off yet.

I don't have a clue what's going on here, but it seems like it has something to do with the CPU or I/O load. Currently I've got a RAID resync running and a large rsync operation and I've encountered four crashes during these operations. Yesterday I had no crashes at all with my computer being almost idle.

I've got two almost identical backtraces from my X-logs:
> Backtrace:
> 0: /usr/bin/X(xf86SigHandler+0x81) [0x80c9581]
> 1: [0xffffe420]
> 2: /usr/bin/X [0x817e39d]
> 3: /usr/bin/X [0x817a9ef]
> 4: /usr/bin/X(CompositeGlyphs+0x9a) [0x816129a]
> 5: /usr/bin/X [0x8168f19]
> 6: /usr/bin/X [0x8164315]
> 7: /usr/bin/X [0x815754e]
> 8: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
> 9: /usr/bin/X(main+0x495) [0x8076f05]
> 10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d5e050]
> 11: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]
>
> Fatal server error:
> Caught signal 11. Server aborting

And:
> Backtrace:
> 0: /usr/bin/X(xf86SigHandler+0x81) [0x80c9581]
> 1: [0xffffe420]
> 2: /usr/bin/X [0x817e39d]
> 3: /usr/bin/X [0x817a9ef]
> 4: /usr/bin/X(CompositeGlyphs+0x9a) [0x816129a]
> 5: /usr/bin/X [0x8168f19]
> 6: /usr/bin/X [0x8164315]
> 7: /usr/bin/X [0x815754e]
> 8: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
> 9: /usr/bin/X(main+0x495) [0x8076f05]
> 10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7df9050]
> 11: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]
>
> Fatal server error:
> Caught signal 11. Server aborting

I'm using the latest Kubuntu (Gutsy Gibbon) and the latest NVidia drivers (v100.14.23). Apart from the NVidia-drivers, all software on my system is installed from packages.

[arnulfo.rodriguez (arnulfo)]

Another me too, I had this error before in Gutsy (beta), I reinstalled the final version and everything was working fine, then the last thing I did was install some devel packages to compile kmediafactory (xorg-devel included) ,and shutdown the computer. The next time I booted the computer, X failed to start with the same error. I have a gforce 7300 LE and I'm using the propietary drivers and compiz fusion.

[swoke (swoke)]

A "me too" under Kubuntu Gutsy with NVidia 100.14.19.

Same backtrace.

[Luke Plant (spookylukey)]

I just got exactly the same thing, but this time while not running Compiz or any OpenGL. It happened immediately after I entered my password to unlock KDE, immediately after resuming from 'Suspend'. This is a not a laptop, but I have got suspend and hibernate working fine on it (until this hiccough).

[miaviator278 (stormesi)]

If anyone from cannonical/ubuntu is willing to acknowlegde this issue I can reproduce it at will and provide strace logs of the crash.

I am using NVIDIA drivers and any GLX usage will cause a crash.

[Bas van Schaik (bas-tuxes)]

Actually I'm not using the nvidia driver from
linux-restricted-modules-2.6.22 anymore, but the one provided by NVidia
itself (v100.14.23). The problem still exists, which makes it either a
general NVidia issue (but then much more people should be complaining)
or an xorg issue. Since this is not clear yet, why did Timo change the
source package?

[Czikus (czikus)]

The same problem again with Kubutuntu Gutsy 7.10, Compiz Fusion and intel driver.

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c9581]
1: [0xffffe420]
2: /usr/bin/X [0x817e39d]
3: /usr/bin/X [0x817a9ef]
4: /usr/bin/X(CompositeGlyphs+0x9a) [0x816129a]
5: /usr/bin/X [0x8168f19]
6: /usr/bin/X [0x8164315]
7: /usr/bin/X [0x815754e]
8: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
9: /usr/bin/X(main+0x495) [0x8076f05]
10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d38050]
11: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]

Fatal server error:
Caught signal 11. Server aborting

[Bas van Schaik (bas-tuxes)]

Ah, the first report from a non-Nvidia user! This effectively rules out
the possibility that the problem lies within the nvidia driver, it
definitely seems to be a problem with Compiz or X...

[Luke Plant (spookylukey)]

As I mentioned above, I've had this crash when not running Compiz (only one though), so it seems more likely to be a bug with X, but one that is made much more common by Compiz (and usually by simultaneous intensive disk IO and CPU).

[Tormod Volden (tormodvolden)]

This bug report seems to have collected a lot of "me-too'ers". Many of the backtraces are completely different from the one in the original report, and are likely different issues. Please file new bugs. In the first place, file it on the package corresponding to the driver you are using (that is linux-restricted-* for the closed-source drivers like nvidia or fglrx).

[greenfog (greenfog)]

i also got a problem: when i try to run any fullscreen stuff like games on Ubuntu Studio x64 and the same NVidia driver --they work fine but i can't return to system because when i try to do so, the system crashes completely! please help! :-) thanx@

[Abhinay Mukunthan (lexxonnet)]

Hello everyone,

A lot of you have reported a backtrace containing the following error, or something similar.
/usr/bin/X(CompositeGlyphs+0x9a) [0x816129a]

Diego Gaustein has opened a new bug report to collate the occurrences of any error involving "CompositeGlyphs". So far, we have a confirmed report from Diego himself(using an nVidia card) and myself(using an ATi). It would be helpful if the others who are experiencing this bug, could migrate to the other thread, so that we can figure out which package the error lies in :) It would also hopefully bring the bug in this thread to a conclusion.

The aforementioned bug report is here:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.22/+bug/165093

[Diego Gaustein (gregorovius)]

I might add something:

I wanted to avoid all the "me too"s, as it happened in this thread, and as Tormod Volden pointed out. A slightly different backtrace might as well be a completely different bug. So, I'd appreciate, if you have the same backtrace as me and Abhinay Mukunthan, that you go and post your experience, but please double check you're having the same issue.

Cheers.

[Antony Jones (wrh)]

I am having the same problem with an integrated Intel card on a Dell GX620 Desktop machine:

The Xserver dissappears (crashes), turns my monitor to standby, and sends me back to the gdm login screen after a few seconds.

It has happened to me twice now, both times I have been un-minimizing Mozilla Firefox from the taskbar (by clicking it)

00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)

Xorg.0.log.old provides:

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c95d1]
1: [0xffffe420]
2: /usr/bin/X [0x817e389]
3: /usr/bin/X [0x817ad15]
4: /usr/bin/X(CompositePicture+0x153) [0x8161223]
5: /usr/bin/X [0x81674ff]
6: /usr/bin/X [0x8164425]
7: /usr/bin/X [0x815765e]
8: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
9: /usr/bin/X(main+0x495) [0x8076f05]
10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7dbf050]
11: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]

Fatal server error:
Caught signal 11. Server aborting

(II) AIGLX: Suspending AIGLX clients for VT switch
(II) intel(0): xf86UnbindGARTMemory: unbind key 0
(II) intel(0): xf86UnbindGARTMemory: unbind key 1
(II) intel(0): xf86UnbindGARTMemory: unbind key 2
(II) intel(0): xf86UnbindGARTMemory: unbind key 3
(II) intel(0): xf86UnbindGARTMemory: unbind key 4

My XOrg config is attached.

[Antony Jones (wrh)]

I too forgot to mention that I use compiz/beryl, in full fledged mode.

[Erik de Castro Lopo (erikd)]

I'm seeing this on a Dell X1 laptop with Intel graphics:

00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)

Here's the Xorg.0.log message:

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x7e) [0x80c780e]
1: [0xb7eea420]
2: /usr/bin/X [0x80da805]
3: /usr/lib/xorg/modules/extensions//libextmod.so(XvdiPutImage+0x178) [0xb7b4d608]
4: /usr/lib/xorg/modules/extensions//libextmod.so [0xb7b50476]
5: /usr/bin/X [0x81506de]
6: /usr/bin/X(Dispatch+0x2cf) [0x808d8df]
7: /usr/bin/X(main+0x48b) [0x807471b]
8: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7c76450]
9: /usr/bin/X(FontFileCompleteXLFD+0x201) [0x8073a91]

Fatal server error:
Caught signal 11. Server aborting

I don't use compviz or beryl. I don't even use Gnome/KDE. Running Enlightenment E17 compiled from source.

Crash usually happens during high X loading; youtube/TED flash videos inside Firefox, vlc etc.

[Erik de Castro Lopo (erikd)]

Ok, I now have a recipie that allows me to reproduce this reasonably reliably.

I've have a HD video in AVI format (Elephant Dreams) and a low res video (Johnny Cash - Hurt) in FLV format from youtube and I'm playing them using vlc.

My machine is not quite powerful enough to play the HD video so I get jumpy and mangle frames along with blue frames. If I then quit the HD video and play the low res video, X gets this signal 11.

What I need now is info on how to get some good debugging info. Should I run X under gdb? If so, how do I set this up the maximize the useful information?

[Erik de Castro Lopo (erikd)]

Ping!!!

I can reliably reproduce this. What do I need to do to collect enough info so this can be fixed?

[Erik de Castro Lopo (erikd)]

I am attempting to debug this using the information from here:

    http://www.x.org/wiki/Development/Documentation/ServerDebugging

After attaching gdb to the running /usr/bin/X process and then crashing it I get the following backtrace:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7c57a30 (LWP 6204)]
0xb7d699bc in memcpy () from /lib/tls/i686/cmov/libc.so.6
(gdb) bt
#0 0xb7d699bc in memcpy () from /lib/tls/i686/cmov/libc.so.6
#1 0xb7b351e8 in I830PutImage (pScrn=0x821aef8, src_x=<value optimized out>, src_y=<value optimized out>, drw_x=4, drw_y=106, src_w=384,
    src_h=288, drw_w=20, drw_h=15, id=842094169, buf=0xa2406000 '\ufffd' <repeats 200 times>..., width=384, height=288, sync=0, clipBoxes=0xbfb6e244,
    data=0x82589dc, pDraw=0x8587bf0) at ../../src/i830_video.c:1379
#2 0x080da805 in xf86XVPutImage (client=0x853a668, pDraw=0x8587bf0, pPort=0x82591b8, pGC=0x8587b58, src_x=<value optimized out>,
    src_y=<value optimized out>, src_w=<value optimized out>, src_h=<value optimized out>, drw_x=0, drw_y=0, drw_w=<value optimized out>,
    drw_h=<value optimized out>, format=0x8258f00, data=0xa2406000 '\ufffd' <repeats 200 times>..., sync=0, width=<value optimized out>,
    height=<value optimized out>) at ../../../../hw/xfree86/common/xf86xv.c:1777
#3 0xb7be3608 in XvdiPutImage (client=0x853a668, pDraw=0x8587bf0, pPort=0x82591b8, pGC=0x8587b58, src_x=<value optimized out>,
    src_y=<value optimized out>, src_w=<value optimized out>, src_h=<value optimized out>, drw_x=<value optimized out>,
    drw_y=<value optimized out>, drw_w=<value optimized out>, drw_h=<value optimized out>, image=0x8258f00,
    data=0xa2406000 '\ufffd' <repeats 200 times>..., sync=0, width=<value optimized out>, height=<value optimized out>) at ../../Xext/xvmain.c:730
#4 0xb7be6476 in ProcXvShmPutImage (client=0x853a668) at ../../Xext/xvdisp.c:1180
#5 0x081506ee in XaceCatchExtProc (client=0x853a668) at ../../Xext/xace.c:299
#6 0x0808d8df in Dispatch () at ../../dix/dispatch.c:502
#7 0x0807471b in main (argc=10, argv=0xbfb6e904, envp=Cannot access memory at address 0x68
) at ../../dix/main.c:452

[Sergio Zanchetta (primes2h)]

The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
linux-restricted-modules-2.6.22 task. It would be helpful if you could test the
new Jaunty Jackalope 9.04 release and confirm if this issue remains -
http://www.ubuntu.com/getubuntu/releasenotes/904overview. If the issue still exists with the Jaunty
release, please update this report by changing the Status of the "linux (Ubuntu)"
task from "Incomplete" to "New". Thanks in advance.

[Ariel Faigon (ariel.faigon)]

A very similar bug and stack trace starting at:

   /usr/bin/Xorg(FontFileCompleteXLFD ...)

and causing firefox to crash Xorg (both nvidia and intel drivers) with SEGV in a reproducible way on certain web pages.

Appears on this RedHat bugzilla:

   https://bugzilla.redhat.com/show_bug.cgi?id=498500

It suggest a workaround as follows:
--------------------------------------------
1) edit /etc/X11/xorg.conf

2) Add the following line to "Section "Device":
      Option "XaaNoOffscreenPixmaps"

3) restart Xorg

I'm not seeing this bug on Ubuntu (I was seeing it consistently and frequently on RHEL5, on different hardware though)

Just thought it may be helpful to mention it here.

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original bug reporter. However, if the issue still exists in the latest development version of Ubuntu and you are the original reporter please feel free to reopen with the requested information. If you are not the original reporter, please don't reopen this one but instead file a new bug and reference this one.