Red Hat Bugzilla – Bug 192200
IERR will occur with RenderAccel turned on with ATI's RN50
Last modified: 2010-10-22 00:58:53 EDT
Description of problem: If an individual turns on RenderAccel in the xorg.conf
file, it will access invalid 3d registers on the RN50 which will result in in an
IERR on Intel based chipsets.
Version-Release number of selected component (if applicable):
How reproducible: very (by using a cosmos (slideshow) program from a
Steps to Reproduce:
1. set RenderAccel to True in xorg.conf and restart X
2. ensure that radeon driver is used for RN50 on machine (can be add in card)
3. run slideshow program from gnome-screensaver
IERR and system lockup
no IERR - invalid registers should not be accessed by driver.
RenderAccel is not default on U3, so the exposure is low. And not all
appllications result in an IERR, however, using an analyzer we can see the
improper registers being accessed which is incorrect. Would like to get this
patched driver into next update (U5). ATI is submitting the patch to xorg. This
is not a problem on RHEL3 (Xfree does not have the code that implements RenderAccel)
Please escalate all RHEL issues through issue tracker.
(In reply to comment #0)
> Description of problem: If an individual turns on RenderAccel in the xorg.conf
> file, it will access invalid 3d registers on the RN50 which will result in in an
> IERR on Intel based chipsets.
> Version-Release number of selected component (if applicable):
> How reproducible: very (by using a cosmos (slideshow) program from a
> gnome-screensaver rpm).
> Steps to Reproduce:
> 1. set RenderAccel to True in xorg.conf and restart X
> 2. ensure that radeon driver is used for RN50 on machine (can be add in card)
> 3. run slideshow program from gnome-screensaver
> Actual results:
> IERR and system lockup
> Expected results:
> no IERR - invalid registers should not be accessed by driver.
> Additional info:
> RenderAccel is not default on U3, so the exposure is low. And not all
> appllications result in an IERR, however, using an analyzer we can see the
> improper registers being accessed which is incorrect. Would like to get this
> patched driver into next update (U5). ATI is submitting the patch to xorg. This
> is not a problem on RHEL3 (Xfree does not have the code that implements
Please have ATI submit a patch to Red Hat as well, relative to the latest
xorg-x11 released for RHEL4 which has been compile and runtime tested
Could you please provide me with a direct link to a source RPM for RHEL4 U5 on
your ftp site?
I will generate the patch for this bug.
FTP is no longer available on people.redhat.com, however
xorg-x11-6.8.2-1.EL.13.33 is now available for download via
http at the following URL: http://people.redhat.com/mharris/testing/4E
The sources are in the SRPMS directory.
This is the most recent RHEL4 build, which is what is currently
in the pending RHEL4U4 release, however RHEL4U5 does not yet exist.
Let me know if you encounter any downloading problems as I've just
recently transitioned from ftp to http and am not sure if the kinks
are all worked out yet.
Created attachment 130784 [details]
Disable render acceleration for RN50
Created attachment 130785 [details]
Disable 3D direct rendering support for RN50
Created attachment 130787 [details]
Concept approval, but nak on attachment #130785 [details], the proper fix is to disable
direct rendering entirely.
Similar solution is correct for 6.8.2, modulo diff fuzz, not really worth
bothering ATI with. Basically I just need PM ack to get this moving.
The component of this request is planned to be updated in Red Hat enterprise
This enhancement request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux maintenance release.
Product Management has requested further review of this enhancement by Red Hat
Engineering, for potential inclusion in a Red Hat Enterprise Linux Update
release for currently deployed products.
This enhancement is not yet committed for inclusion in an Update release.
From QE: Do we have "...specific hardware to test with"?
Dell responds that most of the 9G goodies they just gave us has the "ES1000"
video chip on-board. The systems are in Westford and Raleigh.
Per Fri, 4 Aug 2006 01:33:17, Jerry_Clement@Dell.com commented:
> Here is a list of all of the equipment that has shipped or is in
> ORDER NUMBER SERIAL NO. SYSTEM
> 167013831 19NFDB1 PE1950
> 168200833 CZXFDB1 PE1950
> 167019267 9F06HB1 PE1950 woodcrest cpu, extra mem
> 167024432 95FRHB1 PE1955 (qty = 2)
> 167038887 CK1JGB1 PE2900
> 168207507 JTDNGB1 PE2900
> 167113540 BKBPKB1 PE2900 woodcrest cpu, extra mem
> 167120636 G6K1DB1 PE2950
> 168191800 CTRFDB1 PE2950
> 167008104 JR0LKB1 PE2950 woodcrest cpu, extra mem
> 167449258 J332DB1 RH PWS490
> 181581706 4JXPKB1 RH PWS690
Ajax, are we waiting for an updated patch from ATI (firstname.lastname@example.org) per your
comment #10 and your private comment #11 above? If so, this bug needs to be in
NEEDINFO -- it looks like my comment on 2006-06-28 accidently changed the status
(In reply to comment #18)
> Ajax, are we waiting for an updated patch from ATI (email@example.com) per your
> comment #10 and your private comment #11 above?
No, per comment #12 this just needs a rediff and backport to 6.8.2, I already
have the patch written.
DRI is already turned off for RN50. The only thing missing here is to forcefully
turn off RenderAccel even if the user explicitly turns it on.
Bug report changed to ON_QA status by Errata System.
A QE request has been submitted for advisory RHBA-2007:9144-02.
None of the screensavers lock up the machine, even when RenderAccel is forced on.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.