[root@localhost rpms]# rpm -qa xorg-x11\* | egrep "(server-Xorg)|(nouveau)" xorg-x11-drv-nouveau-debuginfo-0.0.12-11.20090313git79d23d8.fc11.i586 xorg-x11-server-Xorg-1.6.0-13.fc11.i586 xorg-x11-drv-nouveau-0.0.12-11.20090313git79d23d8.fc11.i586 01:00.0 VGA compatible controller: nVidia Corporation NV35GL [Quadro FX 3000] (rev a1) Twice now (not long after reboot) X hangs. The mouse still moves, but nothing else happens. I am able to ssh into the machine and see that X is running at 100% cpu. Strace showed almost no activity other than a couple sigalarm. Ran gdb against Xorg and grabbed a backtrace, the top couple lines are: LOCAL_GET (dma=<value optimized out>, val=<value optimized out>, dma=<value optimized out>, val=<value optimized out>) at nouveau_dma.c:60 60 if (get >= dma->base && get <= (dma->base + (dma->max << 2))) { Missing separate debuginfos, use: debuginfo-install libselinux-2.0.79-1.fc11.i586 (gdb) bt #0 LOCAL_GET (dma=<value optimized out>, val=<value optimized out>, dma=<value optimized out>, val=<value optimized out>) at nouveau_dma.c:60 #1 nouveau_dma_wait (dma=<value optimized out>, val=<value optimized out>, dma=<value optimized out>, val=<value optimized out>) at nouveau_dma.c:104 #2 0x00e8f0ea in nouveau_dma_space (size=<value optimized out>, chan=<value optimized out>) at nouveau_dma.h:111 #3 nouveau_pushbuf_flush_nomm (size=<value optimized out>, chan=<value optimized out>) at nouveau_pushbuf.c:211 #4 nouveau_pushbuf_flush (size=<value optimized out>, chan=<value optimized out>) at nouveau_pushbuf.c:244 #5 0x00f634c9 in WAIT_RING (size=<value optimized out>, chan=<value optimized out>) at /usr/include/nouveau/nouveau_pushbuf.h:79 #6 BEGIN_RING (size=<value optimized out>, chan=<value optimized out>) at /usr/include/nouveau/nouveau_pushbuf.h:90 #7 NV04EXAUploadIFC (size=<value optimized out>, chan=<value optimized out>) at nv04_exa.c:343 I will attach a complete bt output and the Xorg.0.log output.
Created attachment 335266 [details] 3 different backtraces from gdb while the server is spinning
Created attachment 335267 [details] Xorg.0.log of the hanging xserver
Do you see any messages from nouveau in /var/log/messages after X gets stuck waiting for the GPU?
Looks like the answer is yes: Mar 14 18:07:11 localhost kernel: [drm] PFIFO_DMA_PUSHER - Ch 1 2.6.29-0.247.rc8.fc11.i686.PAE
Thanks, that would explain why X is spinning. Just to rule out any weirdness first, are you able to either load the nouveau module with noagp=1 or add: Option "CBLocation" "VRAM" to the nouveau device section and xorg.conf and see if this is repeatable. Either option will be fine, the latter will just disable AGP use for command buffers, the former will disable AGP completely.
Sorry, I'm over 2 full days without a problem with Option "CBLocation" "VRAM"
Fantastic, just what I feared - AGP.. Thanks! There's some bugs on the upstream bugzilla which appear to be the same issue, and I'm fairly certain I can reproduce on at least one of my cards here. I'll look at this over the next couple of days and see if I can find something.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command yum upgrade --enablerepo='*-updates-testing' Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD . Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you. If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. [This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
Ben, is there any motion on this bug from your end? Eric, have you been able to update your distribution, per Comment #9? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Not really, it's kinda hard to fix as it's a combination of that *exact* card, and that *exact* chipset.
eric, up for a trip to Australia? :) -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Absolutely! I haven't powered this system on in months, so I have no idea where it stands today. If someone who can fix it really cares I could make it available (aka ship to you?) to someone, if not, feel free to close with not enough info.
Ben is the guy who can fix it, and I'm sure he would be able to work on it if you got the system to him. If it's a laptop I guess that'd help =) we're all RH, I'm sure we can work something out - just expense the shipping? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
It's a gigantic heavy as a tank IBM x225. I'll try to install something recent over the weekend and see how it runs.
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. 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 '11'. 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 11'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 11 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.