Hide Forgot
Description of problem: After running yum update command to get the latest FC14 updates to my system I rebooted my system. When I startx, I get a segfault in the x11 server. The system is unusable now so I'm having trouble getting debug information. I have several core files and several Xorg.0.log files. Version-Release number of selected component (if applicable): unknown at this time How reproducible: Happens every time, during startx. Steps to Reproduce: 1.see description 2. 3. Actual results: see description Expected results: see description Additional info:
Hi, I'm stuck in line mode now on xterms, is there an ftp site where I can send my debug information? George...
(In reply to comment #1) > Hi, > > I'm stuck in line mode now on xterms, is there an ftp site where I can send my > debug information? what about saving the files to USB key? Thanks for trying
Created attachment 528415 [details] tar.gz file of a directory containing core files and logs. Contents of this file are: -rw------- 1 root root 1798144 Oct 13 23:23 core.3549 -rw------- 1 root root 1798144 Oct 13 23:39 core.3616 -rw------- 1 root root 1798144 Oct 13 23:14 core.4035 -rw------- 1 root root 1798144 Oct 13 23:18 core.4115 -rw-r--r-- 1 root root 103 Oct 13 23:22 uname-a.output -rw-r--r-- 1 root root 73177 Oct 13 23:18 Xorg.0.log -rw-r--r-- 1 root root 73125 Oct 13 23:14 Xorg.0.log.old -rw-r--r--. 1 root root 51498 Apr 7 2011 Xorg.9.log -rw------- 1 root root 343400 Oct 13 23:18 yum.log
Backtrace: [ 93.212] 0: /usr/bin/X (xorg_backtrace+0x3c) [0x80e835c] [ 93.212] 1: /usr/bin/X (0x8048000+0x5dec6) [0x80a5ec6] [ 93.212] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0x8fd40c] [ 93.212] Segmentation fault at address (nil) [ 93.212] Fatal server error: [ 93.212] Caught signal 11 (Segmentation fault). Server aborting This kind of backtrace usually means that the crash is actually somewhere in the kernel-land. Would you be able to get us also output of the program dmesg, please? dmesg >dmesg.out and attach here (only) dmesg.out, please. Thank you
Created attachment 528509 [details] /var/log/dmesg I'm in the process of re-installing this system as fc14-x86_64 and have made backup tar files of all the "current" partitions. Here's /var/log/dmesg from those tar files.
Created attachment 528510 [details] /var/log/dmesg.old Here's /var/log/dmesg.old from the same system, extracted from a tar backup of that systems /var partition.
Created attachment 528790 [details] uname-a.output from the archive
Created attachment 528791 [details] Xorg.0.log from the archive
Created attachment 528792 [details] Xorg.0.log.old from the archive
Created attachment 528793 [details] Xorg.9.log from the archive
Created attachment 528794 [details] yum.log from the archive
We don't support UMS, remove vga=794 nomodeset drm.debug=0x04 From your kernel command line
Jerome, What is UMS? I'm a little confused about what you don't support. You don't support the vga= parameter any more either? You don't support nomodeset? You don't support drm.debug=0x04? Thanks, George...
(In reply to comment #13) > Jerome, > > What is UMS? > > I'm a little confused about what you don't support. > > You don't support the vga= parameter any more either? > > You don't support nomodeset? > > You don't support drm.debug=0x04? We have never really supported vga= much, we really don't care much about nomodeset, you could leave drm.debug there. Please, post requested logs. Thank you
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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" (top right of this page) 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