Bug 66871 - Radeon multi-screen intermittent display failure
Summary: Radeon multi-screen intermittent display failure
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-11 02:42 UTC by Erik Edwards
Modified: 2016-03-23 18:57 UTC (History)
3 users (show)

See Also:
Kernel Version: 3.13.0-rc3
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg (68.94 KB, text/plain)
2013-12-11 17:40 UTC, Erik Edwards
Details
Xorg.log (50.60 KB, text/plain)
2013-12-11 17:40 UTC, Erik Edwards
Details
System messages (137.27 KB, text/plain)
2013-12-11 17:41 UTC, Erik Edwards
Details

Description Erik Edwards 2013-12-11 02:42:34 UTC
In this kernel the 3rd display only comes on for a few partial frames every 20 to 40 seconds. Three displays attached to motherboard.

Under kernel 3.11.10, Radeon driver operates correctly. 


Using:
 ASRock FM2A85X-ITX MB
 AMD A10-6800k (Not overclocked)
 8 GB DDR3
 VGA montitor   - Dell flat screen - 19" 
 HDMI0 montitor - (via DVI connector) - Acer 23" flat.
 HDMI1 montitor - (via HDMI connector) - Acer 22" flat 

VGA is 1   - on an the left.
HDMI1 is 2 - in the center.
HDMI0 is 3 - on the right.
Comment 1 Michel Dänzer 2013-12-11 04:08:26 UTC
Can you bisect?
Comment 2 Alex Deucher 2013-12-11 13:33:54 UTC
Please attach your xorg log and dmesg output as well.
Comment 3 Erik Edwards 2013-12-11 17:35:00 UTC
I'm not sure what you mean.
Comment 4 Erik Edwards 2013-12-11 17:40:37 UTC
Created attachment 118061 [details]
dmesg
Comment 5 Erik Edwards 2013-12-11 17:40:56 UTC
Created attachment 118071 [details]
Xorg.log
Comment 6 Erik Edwards 2013-12-11 17:41:21 UTC
Created attachment 118081 [details]
System messages
Comment 7 Erik Edwards 2014-02-25 16:59:25 UTC
Fedora released 3.13.3 (kernel.x86_64 0:3.13.3-201.fc20) and this is still happening; though, it doesn't happen with 3.12.10 (kernel-3.12.10-300.fc20.x86_64).
Comment 8 Alex Deucher 2014-02-25 17:11:53 UTC
Can you use git to bisect what commit caused the regression?  Google for git bisect howto.
Comment 9 Erik Edwards 2014-06-02 16:17:12 UTC
(In reply to Alex Deucher from comment #8)
> Can you use git to bisect what commit caused the regression?  Google for git
> bisect howto.

3.12.5

Found a workaround:

Allow nromal boot to graphical environment with all monitors powered on. After GUI login is displayed and DVI connected monitor is blank do <ctrl><alt>F2 to switch to text console. Wait until all working displayas are stable then power off and power on non-fucntional display via its power button. Wait until all displays are stable then return to GUI.

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