Description of problem: Frequent (more than once every minute) random momentary black screen and it recovers after 2-3 seconds. Version-Release number of selected component (if applicable): How reproducible: It happens automatically by itself. Steps to Reproduce: 1. Just uses the pc to browse the internet 2. 3. Actual results: Momentary black screen but the system is still responsive. Expected results: Additional info: With nomodeset option in the kernel parameter, it reduce the frequency to once every 5-15 minutes. Turning off DRI in the xorg.conf seems to resolve the issue.
Created attachment 382604 [details] xorg.conf
Please attach Xorg log & kernel message. (/var/log/Xorg.0.log /var/log/dmesg)
I have similar issue so I want to join here. Random, once a day or more I have blank screen (somtimes cursor is visible but freezed). System looks like working but without video. I need to make reboot after this. This happens when I switch windows for example. I have tried turning off compiz, gnome animations, removing mesa-experimental - nothing works. I have hybrid ATI Radeon 3430 (laptop HP 6830s) and FC12. This is new problem, from something like one month or something like this. I have no problem on FC11, Ubuntu, and first updates on FC12.
Created attachment 389845 [details] dmesg
Created attachment 389846 [details] Xorg.log
Created attachment 389847 [details] kerneloops BUG: unable to handle kernel NULL pointer dereference at 00000018 IP: [<f800907d>] r600_kms_blit_copy+0x55/0x528 [radeon]
rpm -q xorg-x11-drv-ati xorg-x11-drv-ati-6.13.0-0.20.20091221git4b05c47ac.fc12.i686
Switching to radeonhd can help me?
Created attachment 389848 [details] kerneloops WARNING: at drivers/gpu/drm/radeon/r600_blit_kms.c:550 r600_blit_prepare_copy+0x2a/0x3b8 [radeon]() (Tainted: P W )
@Mariuz you don't have the same bug, you are experiencing GPU lockup like: https://bugzilla.redhat.com/show_bug.cgi?id=554424 https://bugzilla.redhat.com/show_bug.cgi?id=553279 https://bugzilla.redhat.com/show_bug.cgi?id=541387 @Purnomo do you still have this issue ? Did you updated to the lastest bits ? If you can't test anymore please just say so.
Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.