Created attachment 752402 [details] /var/log/messages, /var/log/X.org.0, and dmesg output Description of problem: I've got an NV44 graphics card in a dual head config on my desktop workstation. The display output sort of works, but performance is suboptimal, there is intermittent screen corruption, and gnome hangs in weird ways. Kernel dmesg shows some interesting stuff: [ 46.528555] nouveau E[ PFIFO][0000:01:00.0] CACHE_ERROR - ch 3 [gnome-shell[1677]] subc 7 mthd 0x1718 data 0x00000000 [ 46.528566] nouveau E[ PFIFO][0000:01:00.0] CACHE_ERROR - ch 3 [gnome-shell[1677]] subc 7 mthd 0x1718 data 0x00000000 [ 46.528578] nouveau E[ PFIFO][0000:01:00.0] CACHE_ERROR - ch 3 [gnome-shell[1677]] subc 7 mthd 0x1808 data 0x00000008 [ 46.528589] nouveau E[ PFIFO][0000:01:00.0] CACHE_ERROR - ch 3 [gnome-shell[1677]] subc 7 mthd 0x1814 data 0x03000000 And so on. Same message, same process (gnome-shell). There's a lot more of it though. Version-Release number of selected component (if applicable): kernel-3.9.3-301.fc19.x86_64 xorg-x11-fonts-Type1-7.5-8.fc19.noarch xorg-x11-drv-synaptics-1.7.1-2.fc19.x86_64 xorg-x11-drv-wacom-0.21.0-1.fc19.x86_64 xorg-x11-drv-mga-1.6.2-6.fc19.x86_64 xorg-x11-xauth-1.0.7-3.fc19.x86_64 abrt-addon-xorg-2.1.4-3.fc19.x86_64 xorg-x11-xinit-1.3.2-8.fc19.x86_64 xorg-x11-xkb-utils-7.7-7.fc19.x86_64 xorg-x11-drv-modesetting-0.6.0-7.fc19.x86_64 xorg-x11-drv-vmware-13.0.1-1.fc19.x86_64 xorg-x11-server-Xorg-1.14.1-2.fc19.x86_64 xorg-x11-drv-fbdev-0.4.3-9.fc19.x86_64 xorg-x11-drv-vesa-2.3.2-9.fc19.x86_64 xorg-x11-font-utils-7.5-13.fc19.x86_64 xorg-x11-drv-ati-7.1.0-5.20130408git6e74aacc5.fc19.x86_64 xorg-x11-fonts-ISO8859-1-100dpi-7.5-8.fc19.noarch xorg-x11-drv-vmmouse-13.0.0-5.fc19.x86_64 xorg-x11-server-common-1.14.1-2.fc19.x86_64 xorg-x11-glamor-0.5.0-5.20130401git81aadb8.fc19.x86_64 xorg-x11-drv-evdev-2.8.0-1.fc19.x86_64 xorg-x11-server-utils-7.7-1.fc19.x86_64 xorg-x11-drv-qxl-0.1.1-0.7.20130514git77a1594.fc19.x86_64 xorg-x11-drv-openchrome-0.3.2-1.fc19.x86_64 xorg-x11-resutils-7.5-7.fc19.x86_64 xorg-x11-utils-7.5-9.fc19.x86_64 xorg-x11-drv-nouveau-1.0.7-1.fc19.x86_64 xorg-x11-drv-intel-2.21.6-1.fc19.x86_64 If you need versions of anything else, let me know. I can also provide remote access to Red Hat employees. How reproducible: Happens all the time with the current software set. Steps to Reproduce: 1. login to gnome 2. try to use X 3 Actual results: screen corruption, artifacts, slow drawing Expected results: no screen corruption, no artifacts, fast drawing Additional info:
please check if the latest libdrm helps this.
Ack. I will give it a try in the next day or two.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.