Description of problem:
In the middle of using my desktop my two displays will go black. Then one or two seconds later the displays will come back on and I can continue on working as normal.
Version-Release number of selected component (if applicable):
$ rpm -q xorg-x11-drv-ati
Happens at least once a day at my 9-5 job.
Steps to Reproduce:
1. login to gnome desktop
2. use computer
Screen goes black for a second every few hours.
Not to go black.
1. In /var/log/messages
Jun 25 15:53:28 jug kernel: [drm] Resetting GPU
Jun 25 15:53:31 jug kernel: [drm] Loading RV630 CP Microcode
Jun 25 15:53:31 jug kernel: [drm] Loading RV630 PFP Microcode
Jun 25 15:53:31 jug kernel: [drm] Resetting GPU
2. /etc/X11/xorg.conf is empty
3. $ lspci | grep ATI
01:00.0 VGA compatible controller: ATI Technologies Inc M76 [Radeon Mobility HD 2600 Series]
01:00.1 Audio device: ATI Technologies Inc RV630/M76 audio device [Radeon HD 2600 Series]
Those "kernel: [drm] Resetting GPU" messages are seem to be triggered by system suspend/resumes not my screen "blackout" problems. I will try to gather info that might be useful.
Similar, but probably different bug is bug 508513.
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.
Please attach your X server config file (/etc/X11/xorg.conf, if available), /var/log/dmesg, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
This looks like a duplicate of bug 501601
Created attachment 350991 [details]
dmesg taken a couple minutes after a screen blackout
Created attachment 350992 [details]
xorg log taken minutes after a screen blackout
And my xorg.conf is empty.
I've seen this on my desktop with an HD4850 card.
When it happened this morning, some vertical lines appeared on the main monitor once the display had resumed, which didn't go away until I rebooted.
*** This bug has been marked as a duplicate of bug 501601 ***
Just to be clear now that I've seen bug #501601, pressing a key or moving the mouse does indeed bring the screen back right away.
So it's not a duplicate isn't it?
(In reply to comment #11)
> So it's not a duplicate isn't it?
It's a duplicate in the sense that Adam Jackson (bug #501601#c42) had decided to use that one bug for both cases where the screen does and doesn't come back on with mouse/key input.
(In reply to comment #12)
> Adam Jackson