Bug 727278

Summary: KMS:RV670 FireGL V7700 computer reset on radeon kernel module loading
Product: Red Hat Enterprise Linux 6 Reporter: Jérôme Glisse <jglisse>
Component: xorg-x11-drv-atiAssignee: Jérôme Glisse <jglisse>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.8CC: lyude, tpelka
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-06 10:19:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jérôme Glisse 2011-08-01 17:55:26 UTC
Description of problem:
Computer either reset or hard freeze when radeon kms module is loaded on rv670 aka firegl v7700. Issue is with cpu access to vram through pci aperture. Fast write to vram through that path trigger the issue

Comment 1 Jérôme Glisse 2011-08-01 17:56:17 UTC
We need to fix this upstream first

Comment 4 Jérôme Glisse 2011-10-24 21:13:58 UTC
No fix upstream yet moving to 6.3

Comment 6 Suzanne Logcher 2012-02-14 23:12:06 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 7 RHEL Program Management 2013-10-14 05:15:43 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 8 Jérôme Glisse 2014-03-19 22:02:34 UTC
Moving to 6.6 so it has a chance of being retested there and close consequently

Comment 13 Lyude 2015-10-26 19:09:04 UTC
Still no fix upstream, reproducible in 6.8 and with the upstream kernel

Comment 15 Jan Kurik 2017-12-06 10:19:53 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/