Bug 488216 - compiz/3d/radeon R500 regression? - broken by .179 (ok in .176)
Summary: compiz/3d/radeon R500 regression? - broken by .179 (ok in .176)
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-03 09:19 UTC by Nigel Jones
Modified: 2009-03-06 10:40 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-03-06 10:40:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Nigel Jones 2009-03-03 09:19:07 UTC
Description of problem:

compiz fails to render correctly. Once compiz is loaded (by fusion-icon) screen turns totally white.

I had this working yesterday with the .76 kernel (and the mass update) through multiple reboots. Overnight I applied the latest RH updates, rebooted & had this failure. Rebooted several times, same symptom.

Then without changing any RPMs I opted to boot the old (176) kernel. Compiz works perfectly. Back to 179 -- fails. This is with no other config changes/ rpm installs/removes

I see the change history for -179 has some kms fixes. I believe these may have caused a regression in my scenario. I use "nomodeset" currently on the kernel command line.

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

kernel-PAE-2.6.29-0.176.rc6.git5.fc11.i686
kernel-PAE-2.6.29-0.179.rc6.git5.fc11.i686
compiz-0.7.8-14.fc11.i586
xorg-x11-drv-ati-6.11.0-1.fc11.i586
xorg-x11-server-Xorg-1.6.0-2.fc11.i586


How reproducible:

Every time

Steps to Reproduce:
1.boot 176 kernel
2.enable compiz
3.works ok
4. boot 179 kernel
 
Actual results:
white screen

Expected results:
works fine. windows appear normal.

Additional info:
Have debug log (just regular syslog) and X logs -- couldn't see anything unique.
I should have run compiz/fusion-icon at command line to capture the error, but forgot to do so. I can do so if required.
However given the problem may be a regression in 176->179 I thought I should raise this in a timely manner.

Comment 1 Nigel Jones 2009-03-06 10:40:55 UTC
Fixed in -197


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