Bug 690489 - [RV770] GPU Lockup on 4870 (GPU lockup (waiting for 0x01E6AE9B last fence id 0xFFFFFFFF))
Summary: [RV770] GPU Lockup on 4870 (GPU lockup (waiting for 0x01E6AE9B last fence id...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 14
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Jérôme Glisse
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-24 13:35 UTC by Daniel Rowe
Modified: 2012-08-16 13:32 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 13:32:31 UTC
Type: ---


Attachments (Terms of Use)
Dmesg cut of kernel messages (8.65 KB, text/plain)
2011-03-24 13:35 UTC, Daniel Rowe
no flags Details
dmesg of after reboot with drm.debug=0x04 on the kernel line (217.32 KB, text/plain)
2011-03-24 13:38 UTC, Daniel Rowe
no flags Details
Xorg log file (147.75 KB, text/plain)
2011-03-24 13:40 UTC, Daniel Rowe
no flags Details
lspci -vv (68.57 KB, text/plain)
2011-03-24 13:40 UTC, Daniel Rowe
no flags Details

Description Daniel Rowe 2011-03-24 13:35:38 UTC
Created attachment 487332 [details]
Dmesg cut of kernel messages

Description of problem:

Once or twice a week I get a GPU lockup (waiting for 0x01E6AE9B last fence id 0xFFFFFFFF) see attached dmesg.

I can't say for sure but I seem to be getting this since the last xorg-x11-drv-ati update.

The display all go off and the GPU fan runs at 100%. I am able to log into the box via ssh from another host and can reboot the box.

This box is running a desktop with Compiz and dual screens, nothing special. Card has lots of power and cooling. When it happen the card is not hot to touch.

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

xorg-x11-drv-ati-6.13.1-0.4.20100705git37b348059.fc14.x86_64

How reproducible:

It is doing this quite often around twice a week but I can't seems to trigger it to happen.

Comment 1 Daniel Rowe 2011-03-24 13:38:16 UTC
Created attachment 487333 [details]
dmesg of after reboot with drm.debug=0x04 on the kernel line

Comment 2 Daniel Rowe 2011-03-24 13:40:01 UTC
Created attachment 487334 [details]
Xorg log file

Comment 3 Daniel Rowe 2011-03-24 13:40:50 UTC
Created attachment 487335 [details]
lspci -vv

Comment 4 Fedora End Of Life 2012-08-16 13:32:34 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.