Bug 768027

Summary: X server crashes daily
Product: [Fedora] Fedora Reporter: Kevin T. Likes <kevin.likes>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 16CC: airlied, ajax, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Other   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 08:06:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
X log file
none
Log from today's crash
none
Last log before 2/19 crash.
none
GDB backtrace output none

Description Kevin T. Likes 2011-12-15 14:53:20 UTC
Created attachment 547297 [details]
X log file

Description of problem: My X session keeps dying nightly while the screen is locked.


Version-Release number of selected component (if applicable):
xorg-x11-drv-tdfx-1.4.3-9.fc16.i686
xorg-x11-fonts-ISO8859-1-100dpi-7.5-4.fc15.noarch
xorg-x11-drv-aiptek-1.4.1-2.fc16.i686
xorg-x11-fonts-misc-7.5-4.fc15.noarch
xorg-x11-drv-vesa-2.3.0-9.fc16.i686
xorg-x11-server-Xephyr-1.11.2-3.fc16.i686
xorg-x11-fonts-ISO8859-9-100dpi-7.5-4.fc15.noarch
xorg-x11-drv-fpit-1.4.0-2.fc16.i686
xorg-x11-drv-mach64-6.9.0-2.fc16.i686
xorg-x11-font-utils-7.5-6.fc15.i686
xorg-x11-drv-ast-0.91.10-7.fc16.i686
xorg-x11-drv-glint-1.2.5-2.fc16.i686
xorg-x11-drv-vmmouse-12.7.0-2.fc16.i686
xorg-x11-drv-rendition-4.2.4-7.fc16.i686
xorg-x11-drv-apm-1.2.3-8.fc16.i686
xorg-x11-drv-r128-6.8.1-11.fc16.i686
xorg-x11-server-utils-7.5-7.fc16.i686
xorg-x11-drv-voodoo-1.2.4-7.fc16.i686
xorg-x11-server-common-1.11.2-3.fc16.i686
xorg-x11-drv-wacom-0.11.99-4.20110527.fc16.i686
xorg-x11-drv-sis-0.10.3-7.fc16.i686
xorg-x11-drv-fbdev-0.4.2-2.fc16.i686
xorg-x11-xkb-utils-7.5-5.fc16.i686
xorg-x11-drv-geode-2.11.12-2.fc16.i686
xorg-x11-drv-ati-6.14.3-3.20111125git534fb6e41.fc16.i686
xorg-x11-drv-hyperpen-1.4.1-2.fc16.i686
xorg-x11-drv-i128-1.3.4-9.fc16.i686
xorg-x11-fonts-Type1-7.5-4.fc15.noarch
xorg-x11-drv-savage-2.3.3-1.fc16.i686
xorg-x11-drv-nouveau-0.0.16-27.20110720gitb806e3f.fc16.i686
xorg-x11-fonts-ISO8859-1-75dpi-7.5-4.fc15.noarch
xorg-x11-drv-siliconmotion-1.7.5-2.fc16.i686
xorg-x11-drv-qxl-0.0.21-8.fc16.i686
xorg-x11-drv-v4l-0.2.0-14.fc16.i686
xorg-x11-drv-vmware-11.0.3-6.fc16.i686
xorg-x11-drv-cirrus-1.3.2-10.fc16.i686
xorg-x11-proto-devel-7.6-12.fc16.noarch
xorg-x11-xauth-1.0.6-1.fc16.i686
xorg-x11-drv-acecad-1.5.0-2.fc16.i686
xorg-x11-drv-evdev-2.6.99-3.20110601giteaf202531.fc16.i686
xorg-x11-drv-i740-1.3.2-9.fc16.i686
xorg-x11-fonts-100dpi-7.5-4.fc15.noarch
xorg-x11-drivers-7.4-2.fc15.i686
xorg-x11-drv-keyboard-1.6.0-2.fc16.i686
xorg-x11-drv-mga-1.4.13-8.fc16.i686
xorg-x11-xinit-1.3.1-1.fc16.i686
xorg-x11-utils-7.5-3.fc16.i686
xorg-x11-drv-void-1.4.0-2.fc16.i686
xorg-x11-drv-synaptics-1.5.0-2.fc16.i686
xorg-x11-drv-openchrome-0.2.904-16.fc16.i686
xorg-x11-drv-intel-devel-2.17.0-1.fc16.i686
xorg-x11-server-Xorg-1.11.2-3.fc16.i686
xorg-x11-apps-7.6-2.fc15.i686
xorg-x11-drv-penmount-1.5.0-3.fc16.i686
xorg-x11-drv-dummy-0.3.4-7.fc16.i686
xorg-x11-drv-mouse-1.7.1-2.fc16.i686
xorg-x11-drv-s3virge-1.10.4-9.fc16.i686
xorg-x11-drv-neomagic-1.2.5-2.fc15.i686
xorg-x11-drv-elographics-1.3.0-2.fc16.i686
xorg-x11-drv-nv-2.1.18-8.fc16.i686
xorg-x11-drv-trident-1.3.4-7.fc16.i686
xorg-x11-drv-intel-2.17.0-1.fc16.i686
xorg-x11-drv-sisusb-0.9.4-7.fc16.i686
xorg-x11-resutils-7.5-2.fc15.i686
xorg-x11-drv-mutouch-1.3.0-2.fc16.i686



How reproducible:

Leave running overnight.

Actual results:

Session is logged out

Expected results:

Should still be logged in in the morning

Additional info:

Comment 1 Dave Airlie 2012-02-12 19:55:51 UTC
can you try with latest server/intel from f16

Comment 2 Kevin T. Likes 2012-02-13 15:31:19 UTC
I do updates pretty much daily. I haven't seen this in the last couple of days, but I know it happened as of last weekend. I'll update this ticket the next time it happens. What information do you want when I do?

Comment 3 Kevin T. Likes 2012-02-13 20:22:57 UTC
Created attachment 561667 [details]
Log from today's crash

Comment 4 Kevin T. Likes 2012-02-13 20:23:35 UTC
Today's crash happened after a yum update and reboot.

Comment 5 Kevin T. Likes 2012-02-20 14:22:46 UTC
I haven't been on the machine since Wednesday, and things were okay when I left. I'm loading the latest crash log, which appears to be from yesterday.There's not any backtrace information, which is different from the last one I can find.

Comment 6 Kevin T. Likes 2012-02-20 14:23:41 UTC
Created attachment 564441 [details]
Last log  before 2/19 crash.

Comment 7 Kevin T. Likes 2012-02-27 19:37:07 UTC
Quick update. It crashed again over the weekend. And again, shotly after I had logged in. If it matters, the crash today was when I was trying to unlock the screensaver. This is something I have seen before.

Comment 8 Adam Jackson 2012-02-27 20:33:05 UTC
Ugh.  Truncated backtrace like that usually means we're calling some function pointer that happens to be NULL.  Which really shouldn't ever happen, but it's possible.

If you happen to have two machines, you can debug this by installing the debuginfo for xorg-x11-server and xorg-x11-drv-intel, ssh'ing into the Intel machine from the other, and running

$ sudo gdb `which Xorg` `pidof Xorg`

You'll want to issue at least the following commands to gdb:

set height 0
handle SIGPIPE nostop
handle SIGALRM nostop
handle SIGUSR1 nostop
# any other configuration you like
continue

And then wait until the crash happens.  This should manifest as a freeze not a crash, since gdb will catch the signal and halt execution.  When it does freeze, the gdb command 'bt full' will print a huge pile of output, which you'd want to save to a file and attach here.  To finish the recovery process just give gdb the 'detach' command.

Comment 9 Kevin T. Likes 2012-03-05 20:04:44 UTC
The server has been running for quite some time now. One thing I am seeing is a lot of SIGPIPE signals. Would those normally be crashing the server, but aren't now because of the "nostop" in gdb?

Comment 10 Adam Jackson 2012-03-05 22:03:17 UTC
(In reply to comment #9)
> The server has been running for quite some time now. One thing I am seeing is a
> lot of SIGPIPE signals. Would those normally be crashing the server, but aren't
> now because of the "nostop" in gdb?

No.  SIGPIPE is a normal condition, generated when a client disconnects.  It's not fatal.

Comment 11 Kevin T. Likes 2012-03-06 14:19:39 UTC
Created attachment 567963 [details]
GDB backtrace output

Comment 12 Kevin T. Likes 2012-04-12 19:59:21 UTC
There were two more crashes today. Is there any more information I can send you that would help this get fixed?

Comment 13 Kevin T. Likes 2012-05-11 18:58:57 UTC
Just to let you know, this is still happening. Not as frequently, but nothing has fixed it.

Comment 14 Fedora End Of Life 2013-01-16 09:59:57 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 15 Fedora End Of Life 2013-02-13 08:06:53 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.