Bug 749048

Summary: [RS880] Monitor says "no signal" when gnome-shell is started
Product: [Fedora] Fedora Reporter: t12345 <t12345>
Component: xorg-x11-drv-atiAssignee: Jérôme Glisse <jglisse>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 16CC: mcepl, xgl-maint
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-14 01:20:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
xorg log
none
second xorg log none

Description t12345 2011-10-25 23:10:50 UTC
#### Description of problem:
After logging-in via gdm the screen goes blank, monitor says "no signal".
Switching between text-console and X allows to see the gnome-shell (without graphical errors), but e.g. moving the mouse to activities (top-left) results again in the blank screen ("no signal").

Relevant cut-out from xorg log:
[   196.538] (II) RADEON(0): radeon_dri2_schedule_flip:655 fevent[0xa37f418]
[   196.538] (WW) RADEON(0): flip queue failed: Device or resource busy
[   196.571] (WW) RADEON(0): Page flip failed: Invalid argument

### Version-Release number of selected component (if applicable):
Fedora 16 Beta
X.Org X Server 1.11.1
Release Date: 2011-09-24
radeon version = 6.14.99
Chipset: "ATI Radeon HD 4200" (ChipID = 0x9710)

### How reproducible:
Always reproducible, monitor says "no signal" after logging in via gdm.

### Steps to Reproduce:
1. Log in via gdm results in "no signal" of the monitor.

### Additional info:
Starting gnome-fallback (from console via startx) works normally.

Comment 1 t12345 2011-10-25 23:12:21 UTC
Created attachment 530201 [details]
xorg log

Comment 2 t12345 2011-10-26 14:42:08 UTC
Bug occured after updating via preupgrade from Fedora 14 to Fedora 16 Beta.

New updates (~236, among others a new kernel) installed today solved the problem.

Comment 3 t12345 2011-10-27 11:51:50 UTC
Sry, I was a bit rash to say it was solved.

Yesterday it worked the whole day without problems but today there's the same error as described at the top.


Upon logon and each time a window is opened or active windows is switched via Alt-Tab the monitor says "no signal". Switching to and back from the console allows to work with the active window until an operation triggers a page flip and the monitor goes off again.

The xorg log (second attachment) shows the same warnings as described above:
[   611.011] (II) RADEON(0): radeon_dri2_schedule_flip:655 fevent[0x9ffaee0]
[   611.011] (WW) RADEON(0): flip queue failed: Device or resource busy
[   611.011] (WW) RADEON(0): Page flip failed: Invalid argument


Sadly the Gnome-fallback ("Gnome with Compiz") shows the same error now.

Comment 4 t12345 2011-10-27 11:53:34 UTC
Created attachment 530465 [details]
second xorg log

Comment 5 Matěj Cepl 2011-10-29 23:05:45 UTC
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 add drm.debug=0x04 to the kernel command line, restart computer, reproduce the issue, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* fresh X server log file (/var/log/Xorg.*.log*; check with grep Backtrace /var/log/Xorg* which logs might be the most interesting ones, send us at least Xorg.0.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 6 Fedora End Of Life 2013-01-16 22:48:56 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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

Comment 7 Fedora End Of Life 2013-02-14 01:20:53 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.