Bug 1327932 - Dual monitor system boots with only one monitor active with Kernel 4.4.x
Summary: Dual monitor system boots with only one monitor active with Kernel 4.4.x
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 23
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-18 04:07 UTC by Paul Loewenstein
Modified: 2016-06-14 11:00 UTC (History)
7 users (show)

Fixed In Version: 4.5.6 (or possibly earlier)
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-14 11:00:05 UTC
Type: Bug


Attachments (Terms of Use)
Output of journalctl -b > boot-4.4.6.txt (266.90 KB, text/plain)
2016-04-18 04:26 UTC, Paul Loewenstein
no flags Details

Description Paul Loewenstein 2016-04-18 04:07:05 UTC
Description of problem:

Intel Core-Duo CPU E8400 with Intel Q45/Q43 graphics and dual monitors comes up with just a single monitor with kernel 4.4.6 (and all other 4.4.x I've tested)

Version-Release number of selected component (if applicable):

4.4.6 and earlier 4.4.x

How reproducible:

100%

Steps to Reproduce:
1.  Boot graphical system with both monitors attached and switched on.

Actual results:

Comes up with only one monitor active

Expected results:

Come up with both monitors active.

Additional info:

Booting with kernel 4.3.5 on an otherwise up-to-date system comes up with both monitors active.  Hence I've filed this against the kernel.

I have performed a manual compare of the journals of the 4.3.5 boot and 4.4.x (at least 2 generations earlier than 4.4.6) and saw no obvious smoking gun.

Only one monitor shows building of the Fedora logo, so the issue must be at quite a low level.  With kernel 4.3.5, this shows on both monitors.

Comment 1 Paul Loewenstein 2016-04-18 04:26:50 UTC
Created attachment 1148104 [details]
Output of journalctl -b > boot-4.4.6.txt

Comment 2 Paul Loewenstein 2016-04-29 05:30:17 UTC
Same problem on kernel 4.4.8.

Comment 3 Paul Loewenstein 2016-06-14 05:38:57 UTC
Seems to be fixed in kernel 4.5.6.
I would close this bug, but I can't find a suitable status description.  "FIXED" does not appear to be a choice open to me!

Comment 4 Josh Boyer 2016-06-14 11:00:05 UTC
Thank you.


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