Bug 1265682

Summary:	Test case failure: Screen - Resolution after no Screen Boot on ATI Kaveri [1002:1304]
Product:	Red Hat Enterprise Linux 7	Reporter:	Vasiliy Sharapov <vsharapo>
Component:	xorg-x11-drv-ati	Assignee:	Michel Dänzer <mdaenzer>
Status:	CLOSED WONTFIX	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	lyude, tpelka
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-12-15 07:36:59 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1380674

Description Vasiliy Sharapov 2015-09-23 13:19:02 UTC

Filed from caserun (https://tcms.engineering.redhat.com/run/260130/#caserun_10820297)

Version-Release number of selected component (if applicable):
RHEL-7.2-20150820.0
xorg-x11-server-Xorg-1.17.2-7.el7.x86_64
xorg-x11-drv-ati-7.5.0-3.el7.x86_64
kernel-3.10.0-306.0.1.el7.x86_64
linux-firmware-20150727-41.git75cc3ef.el7.noarch
mesa-dri-drivers-10.6.0-1.20150616.el7.x86_64

Steps to Reproduce: 
 1. reboot machine
 2. disconnect monitor while machine is shutting down
 3. wait until machine is rebooted to GD


 1. connect display back to the machine



Actual results: 
Monitors get no signal after being connected
`DISPLAY=:0 xrandr' over SSH shows that monitors are detected and modes avaliable but no mode is set

Expected results:
Screen should be correectly powered on with native resolution

Comment 2 Lyude 2016-06-14 17:20:45 UTC

Would you be able to retest this? Last time I checked I could reproduce this on 7.2 but it seemed fixed on 7.3

Comment 3 Tomas Pelka 2016-09-23 18:06:40 UTC

No HW available, Vasiliy can't confirm. We can go sanityonly eventually.

Comment 6 RHEL Program Management 2020-12-15 07:36:59 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.