Bug 474052

Summary: fc10 + r300 driver (AGP) + compiz == random glitches, hard locks
Product: [Fedora] Fedora Reporter: Paul <paul14075>
Component: xorg-x11-drv-atiAssignee: Dave Airlie <airlied>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 10CC: cra, fdc, tony.cochran, xgl-maint
Target Milestone: ---Keywords: Reopened, Triaged
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-12-18 07:05:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Xorg.0.log
none
lspci -vvv none

Description Paul 2008-12-01 21:11:28 UTC
Description of problem:

Thinkpad T42 w/ Radeon Mobility 9600 128 MB AGP
ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] (prog-if 00 [VGA controller])

In FC9 compiz worked great w/ both EXA and XAA.  After upgrading to fc10, the following happened:  System boots to black screen.  Using nomodeset allows X/kde to load, but using compiz or kde/kwin's desktop effects results in frequent and seemingly random video glitches and hard lockups (system will crash hard within 10 minutes of use).  If I use metacity system is very stable.

Version-Release number of selected component (if applicable):
xorg-x11-drv-ati-6.9.0-54.fc10.i386


How reproducible:  VERY


Steps to Reproduce:
1.  Boot into fc10, use compiz or kwin+desktop effects
2.  Use system for a few minutes
3.  System will lock up.
  
Actual results:
glitches and lock ups


Expected results:
system stability


Additional info:  I thought perhaps the fedora modesetting kernel patches could be responsible, so I tried using a kernel.org kernel (2.6.27.7) which I used in fc9 that was very stable....but got same results with that kernel in fc10.

Comment 1 Paul 2008-12-01 21:14:07 UTC
Created attachment 325299 [details]
Xorg.0.log

X server log

Comment 2 Paul 2008-12-01 21:14:40 UTC
Created attachment 325300 [details]
lspci -vvv

lspci -vvv

Comment 3 François Cami 2009-02-21 00:23:15 UTC
Paul,

Could you test the latest kernel and xorg-x11-drv-ati in updates, without KMS (i.e. please use "nomodeset" in kernel command line) ?

---
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 4 Paul 2009-02-23 09:02:34 UTC
OK, I'm using:

kernel-2.6.27.15-170.2.24.fc10.i686
xorg-x11-drv-ati-6.10.0-2.fc10.i386

with nomodeset.

As far as I can tell, the bug does seem to be fixed.  I've been using the system w/ compiz for a few hours now, and no crashes or glitches.  Performance is FANTASTIC, everything seems very smooth, and very much better than it was in f9 w/ same hardware.

But I do have a new problem now.  The system does not wake up from suspend to ram.  With a kernel.org kernel I compiled myself, it works correctly, but w/ the f10 kernel, it fails to wakeup.  It will turn on, and the LED's will come on, and the network/wifi light will start flashing as if its working, but the screen is filled random garbage and is hung, does not respond to ctrl-alt-bksp or ctrl-alt-del.

When will whatever made this kernel stable for me be included in the mainline kernel?

Comment 5 François Cami 2009-02-23 19:03:24 UTC
Thank-you for the follow-up.
As the particular bug you reported was fixed by a published update,
I will close this one as CLOSED/CURRENTRELEASE.

Please feel free to open another bug about the suspend/resume issue.

---
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 6 Paul 2009-02-23 22:10:23 UTC
Sorry, I spoke too soon.

I *do* still get random lockups when using newest f10 kernel.  Took maybe 3 hours of use before I got it to lockup.  Happened while using xchat.

Comment 7 Bug Zapper 2009-11-18 10:15:49 UTC
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  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 '10'.

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 10'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 10 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

Comment 8 Bug Zapper 2009-12-18 07:05:30 UTC
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.