[Bug 97204] New: Can't enable a third monitor even with 3 CRTCs available (1 LVDS, 1 VGA, 1 HDMI/VGA)

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Aug 4 15:50:27 UTC 2016


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

            Bug ID: 97204
           Summary: Can't enable a third monitor even with 3 CRTCs
                    available (1 LVDS, 1 VGA, 1 HDMI/VGA)
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: nick.diego at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 125534
  --> https://bugs.freedesktop.org/attachment.cgi?id=125534&action=edit
dmesg output with drm.debug enabled

I'm running Arch Linux - kernel 4.6.4 and also tested with 4.4.16 - on a laptop
Lenovo Ideapad Z400, which has 2 GPUs, 1 NVIDEA (disabled) and 1 Intel.
Connected 2 external monitors, 1 via VGA and the other via HDMI using a
HDMI/DVI connector. The problem occurs when I try to enable a third display,
xrandr fails with the message "Configure crtc 2 failed". Already checked and it
seems to have 3 CRTCs hardware available. Running kernel with "drm.debug=0xe"
(dmesg attached) it shows "[  339.630668] [drm:ironlake_crtc_compute_clock]
failed to find PLL for pipe C" at some point.
This seems to be similar or a regression of
https://bugs.freedesktop.org/show_bug.cgi?id=68485, not sure.

Thanks for your help. Please let me know if there's anything I can do to help
in debugging/testing.

-- 
You are receiving this mail because:
You are the assignee for the bug.
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: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160804/327b34ae/attachment-0001.html>


More information about the intel-gfx-bugs mailing list