Bug 38916 - Segmentation fault: X server for display :0 terminated unexpectedly
Summary: Segmentation fault: X server for display :0 terminated unexpectedly
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: 7.6 (2010.12)
Hardware: x86-64 (AMD64) Linux (All)
: high major
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard: 2011BRB_Reviewed
Keywords: have-backtrace
Depends on:
Blocks:
 
Reported: 2011-07-02 10:52 UTC by Ettore Atalan
Modified: 2018-06-12 18:44 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
Xorg.0.log + kdm.log (8.15 KB, application/zip)
2011-07-02 10:52 UTC, Ettore Atalan 		no flags Details
kdm.log, Xorg.0.log, syslog (10.22 KB, application/zip)
2011-12-03 08:01 UTC, Ettore Atalan 		no flags Details
View All

Description Ettore Atalan 2011-07-02 10:52:16 UTC 
Created attachment 48688 [details]
Xorg.0.log + kdm.log

Hi

While using Firefox 5, the screen freezes and CPU usage goes up to 100%. A little later the console appears in fullscreen mode and the KDE Desktop gets restarted automatically. I didn't do anything.


syslog:
kdm[946]: X server for display :0 terminated unexpectedly
Comment 1 Chris Wilson 2011-07-02 11:31:54 UTC 
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x26) [0x4a2656]
1: /usr/bin/X (0x400000+0x621ca) [0x4621ca]
2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fe96976d000+0xfc60) [0x7fe96977cc60]
3: /usr/bin/X (0x400000+0x3d7e5) [0x43d7e5]
4: /usr/bin/X (ProcUngrabKeyboard+0xd4) [0x43b4d4]
5: /usr/bin/X (0x400000+0x2e2a9) [0x42e2a9]
6: /usr/bin/X (0x400000+0x21a7e) [0x421a7e]
7: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xff) [0x7fe9686b6eff]
8: /usr/bin/X (0x400000+0x21629) [0x421629]
Segmentation fault at address 0x211

For once this doesn't immediately seem driver related.
Comment 2 Ettore Atalan 2011-12-03 08:01:00 UTC 
Created attachment 54090 [details]
kdm.log, Xorg.0.log, syslog

X.Org X Server 1.10.4 crashed while watching a flash video in Firefox.
Comment 3 Jeremy Huddleston Sequoia 2012-01-02 12:51:01 UTC 
I don't see a backtrace in your second set of logs.  Did it really crash?  Also, what makes you think that this is the same issue rather than a different crash?  Is it reproducible; if so, how?
Comment 4 Adam Jackson 2018-06-12 18:44:12 UTC 
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please file a new report if you continue to experience issues with a current server.

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.