Red Hat Bugzilla – Bug 505853
Display corruption after using Fedora 13 nouveau driver for some time
Last modified: 2018-04-11 11:48:46 EDT
Created attachment 347810 [details]
Xorg log attached after display corruption
Description of problem:
Display gets corrupted and full of horizontal lines with rainbow colors after some minutes of using Fedora 11 with nouveau driver
Version-Release number of selected component (if applicable):
Name : xorg-x11-drv-nouveau
Arch : i586
Epoch : 1
Version : 0.0.12
Release : 36.20090514git9656762.fc11
Size : 350 k
Repo : installed
Summary : Xorg X11 nouveau video driver for NVIDIA graphics chipsets
URL : http://www.x.org
License : MIT
Description: X.Org X11 nouveau video driver.
Steps to Reproduce:
1. Launch Fedora 11 (after installation or from live cd (i686 or x86-64)) on a system having nvidia card so that it will use nouveau driver
2. Keep using the system for some time (say 10 mins or more), browse firefox, use terminal and so on
3. After some time, the entire screen looks like horizontal lines of rainbow colors and the screen is unreadable.
4. But Fedora still works and can be connected through telnet or ssh
Display/Screen gets corrupted and full of artifacts and we cant proceed with Fedora without restarting
No display corruption after using Fedora 11 over a period of time (say some minutes or hours of use)
Nvidia card: MSI 9800 GT 1 GB
saved log /var/log/Xorg.0.log is attached
Display corruption does not occur after disabling PCIe L0 and L1 ASPM (Active State Power Management) states in bios.
Board is Intel Desktop Board DX58SO
Now nouveau working like a charm
After disabling active state power management in bios, display corruption did not occur for more time, but it occurs at some point of time.
To easily simulate the display corruption run futuremark browser benchmark from firefox (http://service.futuremark.com/peacekeeper/run.action)
Display corruption does not happen when nouveau.modeset=1 is passed as kernel boot param! even after running the futuremark browser benchmark and the graphics card is stressed
Can we get Xorg.0.log from the nouveau.modeset=1 case? Thanks!
Fedora Bugzappers volunteer triage team
Created attachment 356698 [details]
Contains Xorg.0.log after display corruption when running livecd with nouveau.modeset=1
Created attachment 356699 [details]
dmesg output after display corruption
got the dmesg output by giving dmesg | tail -1024
Created attachment 356700 [details]
Some messages which got printed in the system where I ran ssh to the box running livecd of Fedora 11
Display corruption happening every time when I run graphics intensive browser benchmark. This even happens when nouveau.modeset=1 is given at boot param
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.]
Created attachment 370292 [details]
Xorg log of Fedora 12 with screen corruption
Created attachment 370293 [details]
dmesg after display corruption
Display corruption still happening in Fedora 12, here is the dmesg output
Created attachment 370294 [details]
lsmod showing Fedora 12 using nouveau even after trying to boot with vesa
Created attachment 370295 [details]
lsmod showing Feodora 12 using nouveau driver
Created attachment 370296 [details]
Photo of corrupted screen taken using digicam
I took the photo of the corrupted screen using digicam as nothing worked after the corruption. Even the logs I captured are copied and pasted as file transfer was not working. Sometimes, even before logging into Fedora 12 itself the screen corruption happens.
I tried nomodeset, but the display corruption still happens. Once it happens, nothing works except rebooting or existing ssh session. Even in existing ssh session, not able to transfer files
The corruption happens in 64 bit Fedora 12 also. As requested I have attached logs and info as attachments from comment 9 to comment 13, hope this helps
Same problem here (KNMI):
It seems to occur mostly in combination with GNOME - nouveau...
Using an second screen (DVI) with the noveau driver also infects the performance ;((
Created attachment 406899 [details]
Xorg.0.log for screen corruption happening in Fedora 13 with nouveau driver
Created attachment 406901 [details]
dmesg output after screen corruption due to nouveau driver in Fedora 13
Created attachment 406902 [details]
output of dmesg pipe tail, uname -a and free -m after nouveau screen corruption in Fedora 13
Created attachment 406904 [details]
Digicam image of Fedora 13 noveau image corruption
could not save files or take screenshot as screen was unresponsive after screen corruption. Fortunately, ssh session worked and able to take dmesg log
Created attachment 406905 [details]
Digicam image of nouveau screen corruption happening in Fedora 13 beta with camera flash
I've suffered from this problem in F12, thought it would be fixed in F13, but it it not :-( It is quite annoying to constantly have corrupted display. For me it happens very very often. I'll attach 2 pictures to demonstrate the corruptions.
Created attachment 423617 [details]
Example of corrupted desktop 1
Created attachment 423618 [details]
Example of corrupted desktop 2
Fedora 13 display corruption while booting. It worked for some time. After 5 or 6 boots this display corruption problem occurred. The same happened in Fedora 11. I think still it not got fixed. Any time if we change some BIOS update or even saving the BIOS with different settings this problem happens.
Once it happens, nothing works except rebooting.
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. 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 '13'.
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 13'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 13 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:
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.