<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [Biscted] HSW unable to work on two pipes"
href="https://bugs.freedesktop.org/show_bug.cgi?id=75246">75246</a>
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Assignee</th>
<td>jbarnes@virtuousgeek.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>[Biscted] HSW unable to work on two pipes
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Reporter</th>
<td>qingshuai.tian@intel.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=94410" name="attach_94410" title="dmesg after boot up with two pipes (HDMI&VGA)">attachment 94410</a> <a href="attachment.cgi?id=94410&action=edit" title="dmesg after boot up with two pipes (HDMI&VGA)">[details]</a></span>
dmesg after boot up with two pipes (HDMI&VGA)
Environment:
-------------------
Kernel: (drm-intel-next-queued) 4c0e552882114d1edb588242d45035246ab078a0
Description:
------------------------
When the desktop is booted up with HDMI and VGA connected, only the HDMI
monitor lighted up normally. But when run "testdisplay -i", it showed that both
VGA and HDMI are connected,and "testdisplay -a" also works well on both of
them.
When plugged in HDMI or VGA separately at one time, they all work well.
This is a regression. I bisected it and it showed:
eb1bfe807cb7b62a326fa20df5e3118a32c6f923 is the first bad commit
commit eb1bfe807cb7b62a326fa20df5e3118a32c6f923
Author: Jesse Barnes <<a href="mailto:jbarnes@virtuousgeek.org">jbarnes@virtuousgeek.org</a>>
Date: Wed Feb 12 12:26:25 2014 -0800
drm/i915: allow re-use BIOS connector config for initial fbdev config v3
The BIOS or boot loader will generally create an initial display
configuration for us that includes some set of active pipes and
displays. This routine tries to figure out which pipes and connectors
are active and stuffs them into the crtcs and modes array given to us by
the drm_fb_helper code.
The overall sequence is:
intel_fbdev_init - from driver load
intel_fbdev_init_bios - initialize the intel_fbdev using BIOS data
drm_fb_helper_init - build fb helper structs
drm_fb_helper_single_add_all_connectors - more fb helper structs
intel_fbdev_initial_config - apply the config
drm_fb_helper_initial_config - call ->probe then register_framebuffer()
drm_setup_crtcs - build crtc config for fbdev
intel_fb_initial_config - find active connectors etc
drm_fb_helper_single_fb_probe - set up fbdev
intelfb_create - re-use or alloc fb, build out fbdev structs
v2: use BIOS connector config unconditionally if possible (Daniel)
check for crtc cloning and reject (Daniel)
fix up comments (Daniel)
v3: use command line args and preferred modes first (Ville)
Signed-off-by: Jesse Barnes <<a href="mailto:jbarnes@virtuousgeek.org">jbarnes@virtuousgeek.org</a>>
Tested-by: Ville Syrjälä <<a href="mailto:ville.syrjala@linux.intel.com">ville.syrjala@linux.intel.com</a>>
[danvet: Re-add the WARN_ON for a missing encoder crtc - the state
sanitizer should take care of this. And spell-ocd the comments.]
Signed-off-by: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>
:040000 040000 dbe7ef821ba404c994fbc579461b7e0d4febf10a
1b40c56483f03c15ae495a85a78fe740beeeb0e9 M drivers
I think this bug may be related to <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [Bisected] Apple miniDP-to-DP and HDMI can be detected but can't light up"
href="show_bug.cgi?id=75077">Bug 75077</a>.
Test Step:
--------------------
1. connect HDMI&VGA
2. Boot up
3. testdisplay -i
4. testdisplay -a</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>