Bug 9741 - X server repeatedly dying after receiving signal 11
Summary: X server repeatedly dying after receiving signal 11
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: 7.1 (2006.05)
Hardware: x86 (IA32) Linux (All)
: high major
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
Keywords: have-backtrace
Depends on:
Reported: 2007-01-22 18:58 UTC by John Guthrie
Modified: 2018-12-17 17:34 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

X org conf file (2.80 KB, text/plain)
2007-01-22 18:59 UTC, John Guthrie
no flags Details
Log file from the last crash. (52.13 KB, text/plain)
2007-01-22 19:03 UTC, John Guthrie
no flags Details

Description John Guthrie 2007-01-22 18:58:08 UTC
Recently, I have been seeing my X server die with the following error message:

0: X(xf86SigHandler+0x81) [0x80c9bd1]
1: [0xd4e420]
2: /usr/lib/xorg/modules/extensions/libGLcore.so [0x10ea56e]
3: /usr/lib/xorg/modules/extensions/libGLcore.so(_swrast_Line+0x23) [0x107fd73]
4: /usr/lib/xorg/modules/extensions/libGLcore.so [0x10855d0]
5: /usr/lib/xorg/modules/extensions/libGLcore.so(_tnl_RenderClippedLine+0x23) [0
6: /usr/lib/xorg/modules/extensions/libGLcore.so [0x109e643]
7: /usr/lib/xorg/modules/extensions/libGLcore.so [0x10a1f2a]
8: /usr/lib/xorg/modules/extensions/libGLcore.so [0x10a5b83]
9: /usr/lib/xorg/modules/extensions/libGLcore.so(_tnl_run_pipeline+0x145) [0x10a
10: /usr/lib/xorg/modules/extensions/libGLcore.so(_tnl_DrawArrays+0x131) [0x10b8
11: /usr/lib/xorg/modules/extensions/libglx.so [0x4352e3]
12: /usr/lib/xorg/modules/extensions/libglx.so(__glXRenderLarge+0x2ec) [0x4165ec
13: /usr/lib/xorg/modules/extensions/libglx.so [0x418d6a]
14: X(Dispatch+0x19a) [0x80880da]
15: X(main+0x485) [0x806fa65]
16: /lib/libc.so.6(__libc_start_main+0xdc) [0x2aaf2c]
17: X(FontFileCompleteXLFD+0x1e9) [0x806eda1]

Fatal server error:
Caught signal 11.  Server aborting

And then there are several complaints about connection to :0.0 being broken.

I actually saw one of the events just a little while ago.  A screensaver had
just started, and then the X server died.  I suspect the same thing happened
with the other times because they would happen after I had been absent for a while.

I am running this particular server via xinit, I don't know if that affects
anything.  I am also using the open nv driver.  This is on a FC6 machine with a
"nVidia Corporation NV5M64 [RIVA TNT2 Model 64/Model 64 Pro]" video card.

I have seen my X server die like this about three time in the last 3-5 days.  I
have managed to have the presence of mind to save the backtraces for the last
two crashes.

Note: I didn't quite know what to put as the version for X:

euler_1011% rpm -qf /usr/bin/X

and 1.1.1 is not listed as a valid version option.  However, several of the X
packages seem to have a version number of 7.1, e.g.:

euler_1012% rpm -q xorg-x11-drivers

so I am guessing that I have version 7.1 of the software.
Comment 1 John Guthrie 2007-01-22 18:59:30 UTC
Created attachment 8481 [details]
X org conf file

Here is my xorg.conf file.
Comment 2 John Guthrie 2007-01-22 19:03:50 UTC
Created attachment 8483 [details]
Log file from the last crash.

Here is the log file from the last crash.
Comment 3 John Guthrie 2007-01-22 19:06:16 UTC
I should also note that this is *not* a problem on startup.  Typically, the
server will be running for quite some time before crashing.
Comment 4 Daniel Stone 2007-02-27 01:35:54 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 5 GitLab Migration User 2018-12-17 17:34:38 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/618.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.