[Bug 75246] New: [Biscted] HSW unable to work on two pipes

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=75246

          Priority: medium
            Bug ID: 75246
                CC: intel-gfx-bugs at lists.freedesktop.org
          Assignee: jbarnes at virtuousgeek.org
           Summary: [Biscted] HSW unable to work on two pipes
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: qingshuai.tian at intel.com
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: DRM/Intel
           Product: DRI

Created attachment 94410
  --> https://bugs.freedesktop.org/attachment.cgi?id=94410&action=edit
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 <jbarnes at virtuousgeek.org>
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 <jbarnes at virtuousgeek.org>
    Tested-by: Ville Syrjälä <ville.syrjala at linux.intel.com>
    [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 <daniel.vetter at ffwll.ch>

:040000 040000 dbe7ef821ba404c994fbc579461b7e0d4febf10a
1b40c56483f03c15ae495a85a78fe740beeeb0e9 M      drivers

I think this bug may be related to Bug 75077.

Test Step:
--------------------
1. connect HDMI&VGA
2. Boot up 
3. testdisplay -i 
4. testdisplay -a

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140220/40ad636e/attachment.html>