Hide Forgot
Created attachment 475931 [details] X server log showing X server operations up to onset of crash & loop Description of problem: I'm running FC 14 on an IBM Lenovo T61p; Nvidia graphics card (. FC 14 fully up to date. KDE is desktop manager. All apps freeze, keyboard unresponsive, mouse still moves. ssh into system shows X running at 99% cpu. Kill X and startx works but all running apps are gone, as expected. Kernel at 2.6.35.10-74.fc14.i686; KDE at kdebase-4.5.5-1.fc14.i686 Version-Release number of selected component (if applicable): X.Org X Server 1.9.3 How reproducible: random but frequent recurrences of this problem; ktorrent was object of focus in ALL cases Steps to Reproduce: 1. Unknown 2. 3. Actual results: see description above Expected results: "normal" system operation Additional info: strace of loop is available gdb init msgs + where command output is available Xorg.0.log is available
Created attachment 475933 [details] tar.gz file containing defaultxserver.strace Xloop.strace Xorg.0.log.old xserver.gdbsyms This bug might be related to or a dup of 614958.
Created attachment 476188 [details] defaultxserver.strace from the archive
Created attachment 476189 [details] Xloop.strace from the archive
Created attachment 476190 [details] Xorg.0.log.old from the archive
Created attachment 476191 [details] xserver.gdbsyms from the archive
Looks like something wrong with nouveau driver, reassigning.
Ben, One more core file. :( George... Core was generated by `/usr/bin/X :0 -auth /root/.serverauth.29508'. Program terminated with signal 6, Aborted. #0 0x003a3416 in __kernel_vsyscall () (gdb) where #0 0x003a3416 in __kernel_vsyscall () #1 0x00b802f1 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #2 0x00b81d5e in abort () at abort.c:92 #3 0x080a8c2d in OsAbort () at utils.c:1274 #4 0x080b55f7 in ddxGiveUp () at xf86Init.c:951 #5 0x080b56b0 in AbortDDX () at xf86Init.c:997 #6 0x080a4c7e in AbortServer () at log.c:424 #7 0x080a4dbe in FatalError (f=0x81cf828 "Caught signal %d (%s). Server aborting\n") at log.c:552 #8 0x080a5db0 in OsSigHandler (signo=11, sip=0xbf85dc6c, unused=0xbf85dcec) at osinit.c:156 #9 <signal handler called> #10 0x00187995 in DrawableGone (glxPriv=0x8baf940, xid=0) at glxext.c:173 #11 0x0808e1bf in FreeClientResources (client=0x8787970) at resource.c:859 #12 0x0808e276 in FreeAllResources () at resource.c:876 #13 0x08062381 in main (argc=4, argv=0xbf85e194, envp=0xbf85e1a8) at main.c:305
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