Bug 813251 - *ERROR* displayport link status failed
Summary: *ERROR* displayport link status failed
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: xorg-x11-drv-ati
Version: 6.8
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Jérôme Glisse
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 842499
TreeView+ depends on / blocked
 
Reported: 2012-04-17 10:27 UTC by Tomas Pelka
Modified: 2017-12-06 11:37 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 11:37:48 UTC
Target Upstream Version:


Attachments (Terms of Use)
xorg log (83.98 KB, text/plain)
2012-04-17 10:31 UTC, Tomas Pelka
no flags Details
dmesg (237.07 KB, text/plain)
2012-04-17 10:31 UTC, Tomas Pelka
no flags Details

Description Tomas Pelka 2012-04-17 10:27:27 UTC
Description of problem:
Seeing this messages in VT when plugging/unplugging DP. Obviously the DP still working without visible problems. 


Version-Release number of selected component (if applicable):
xorg-x11-drv-ati-6.14.2-9.el6
kernel-2.6.32.262.el6

How reproducible:
100%

Steps to Reproduce:
1. just boot the system
2.
3.
  
Actual results:
[drm:radeon_dp_get_link_status] *ERROR* displayport link status failed

Expected results:


Additional info:
Saw it on Fire Pro V5800 so far

Comment 1 Tomas Pelka 2012-04-17 10:30:30 UTC
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI Juniper XT [FirePro 3D V5800] [1002:68a9] (prog-if 00 [VGA controller])
	Subsystem: Hewlett-Packard Company Device [103c:2306]
	Flags: bus master, fast devsel, latency 0, IRQ 28
	Memory at e0000000 (64-bit, prefetchable) [size=256M]
	Memory at f0000000 (64-bit, non-prefetchable) [size=128K]
	I/O ports at 1100 [size=256]
	[virtual] Expansion ROM at f0040000 [disabled] [size=128K]
	Capabilities: [50] Power Management version 3
	Capabilities: [58] Express Legacy Endpoint, MSI 00
	Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [100] Vendor Specific Information <?>
	Capabilities: [150] Advanced Error Reporting
	Capabilities: [240] Power Budgeting <?>
	Kernel driver in use: radeon
	Kernel modules: radeon

Comment 2 Tomas Pelka 2012-04-17 10:31:01 UTC
Created attachment 577987 [details]
xorg log

Comment 3 Tomas Pelka 2012-04-17 10:31:24 UTC
Created attachment 577988 [details]
dmesg

Comment 4 Tomas Pelka 2012-04-17 12:39:47 UTC
Can see it also on V7900.

Comment 5 Jérôme Glisse 2012-04-17 17:31:30 UTC
Does the monitor stay black ? or does it works ?

Comment 6 Tomas Pelka 2012-04-17 18:21:47 UTC
No everything works fine, that is why the bug is low/log.

Comment 7 RHEL Program Management 2012-05-03 04:40:39 UTC
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

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.

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

Comment 9 Jérôme Glisse 2014-10-30 19:41:06 UTC
This need to be tested again, this should definitly be fixed in 6.6

Comment 13 Jan Kurik 2017-12-06 11:37:48 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/


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