Bug 651362 - KMS:RV680:HD3870 "radeon 0000:03:00.0: ffff88014b6e8400 reserve failed for wait" (Compiz+X stop responding)
Summary: KMS:RV680:HD3870 "radeon 0000:03:00.0: ffff88014b6e8400 reserve failed for wa...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 14
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Jérôme Glisse
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-09 11:56 UTC by Daniel Rowe
Modified: 2018-04-11 10:09 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-08-16 18:24:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
lspci -vv (68.55 KB, text/plain)
2010-11-09 11:56 UTC, Daniel Rowe
no flags Details
dmesg output (93.66 KB, text/plain)
2010-11-23 14:31 UTC, Daniel Rowe
no flags Details
Xorg.0.log (147.73 KB, text/plain)
2010-11-23 14:32 UTC, Daniel Rowe
no flags Details

Description Daniel Rowe 2010-11-09 11:56:52 UTC
Created attachment 459084 [details]
lspci -vv

Description of problem:

With Compiz running X locks hard after a while. This does not happen if Compiz is not running. This is on a system with a ATI 3870 card running the Fedora default Open Source driver with a i7 CPU 12gig of RAM. 

Note the machine is not locked and I am able to switch VTs and kill Xorg with SIGTERM. Killing Compiz does not unlock Xorg. The Compiz process does kill with SIGTERM fine as well. 

The Xorg process is not using lots of CPU or does not appear different than normal when it has locked up nor does the Compiz process.

When running Fedora 13 with all update every is fine and this machine as very long up times, only being rebooted for kernel updates.

When running with Fedora 14 this happen after a couple of hours. Nothing in dmesg or logs.

Version-Release number of selected component (if applicable):

compiz-fusion-extras-gnome-0.8.6-1.fc14.x86_64
compiz-0.8.6-3.fc14.x86_64
compiz-fusion-unsupported-0.8.4-4.fc14.x86_64
compizconfig-python-0.8.4-3.fc14.x86_64
compiz-fusion-gnome-0.8.6-1.fc14.x86_64
compiz-gnome-0.8.6-3.fc14.x86_64
compiz-fusion-extras-0.8.6-1.fc14.x86_64
libcompizconfig-0.8.4-3.fc14.x86_64
compiz-fusion-0.8.6-1.fc14.x86_64
xorg-x11-drv-ati-6.13.1-0.3.20100705git37b348059.fc14.x86_64

How reproducible:

Every time

Steps to Reproduce:

1. Login to X with Compiz running
2. Leave Machine idle
3. Come back after a while and machine is locked
  
Actual results:

Xorg lock up every time when Compiz is running.

Expected results:

Does not do this.

Additional info:

See attached.

Comment 1 Matěj Cepl 2010-11-09 15:00:02 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, wait until the crash happens, collect logs and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.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 2 Daniel Rowe 2010-11-23 14:30:18 UTC
I have work out it is the screen saver that causing this.

Disable the screen saver and no problem, I still have turn monitors off after 30 mins enabled. As soon as the screen saver is enabled I get this where the screen is frozen. 

Looks like the ATI DRM driver or Xorg is not crashing in anyway and programs are running in the desktop, just the output is frozen.

Will the drm.debug=0x04 still be useful if this is the case?

When the screen is frozen there is nothing in the logs or dmesg that is different than normal. Seems to be an interaction between Compiz and the screen saver which is just plain black screen.

Comment 3 Daniel Rowe 2010-11-23 14:31:10 UTC
Created attachment 462344 [details]
dmesg output

Comment 4 Daniel Rowe 2010-11-23 14:32:06 UTC
Created attachment 462345 [details]
Xorg.0.log

Comment 5 Jérôme Glisse 2010-11-23 17:20:14 UTC
Might be related to upstream bug need to check it out

Comment 6 Stuart D Gathman 2011-07-07 03:00:16 UTC
Getting that message with Fedora 14, updated.  It is not the screen saver, because I can be simply scrolling firefox, and it locks up.  Just like the original poster, I can switch VTs and kill Xorg with SIGTERM.

Comment 7 Fedora End Of Life 2012-08-16 18:24:52 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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" (top right of this page) 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


Note You need to log in before you can comment on or make changes to this bug.