[Bug 62564] New: [HD 4000] triple monitor configuration - resolutions above 1024x768 hangs/locks kernel and/or xserver

[bugzilla-daemon at freedesktop.org]

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

          Priority: medium
            Bug ID: 62564
          Assignee: intel-gfx-bugs at lists.freedesktop.org
           Summary: [HD 4000] triple monitor configuration - resolutions
                    above 1024x768 hangs/locks kernel and/or xserver
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
          Severity: major
    Classification: Unclassified
                OS: Linux (All)
          Reporter: ipejic at gmail.com
          Hardware: x86 (IA32)
            Status: NEW
           Version: unspecified
         Component: DRM/Intel
           Product: DRI

Created attachment 76831
  --> https://bugs.freedesktop.org/attachment.cgi?id=76831&action=edit
xrandr --verbose

System environment:
-- chipset: QM77
-- system architecture: i686
-- xf86-video-intel: 2.20.0
-- xserver: 1.11.3
-- mesa: 9.0.1
-- libdrm version: 2.4.32-1ubuntu1
-- kernel version: 3.5.0-26-generic
-- Linux distribution: Ubuntu 12.04.2
-- Motherboard: kino-qm770-r10
-- Display connector: DVI, HDMI, HDMI

Setting native monitor resolutions above 1024x768 for all three monitors always
produce this continuously repeating error:
...
[drm:intel_dp_start_link_train], training pattern 1 signal levels 00000000
[drm:intel_dp_start_link_train], training pattern 1 signal levels 02000000
[drm:intel_dp_start_link_train], training pattern 1 signal levels 04000000
...

Kernel 3.2.x hangs during boot.
Kernel 3.5.x - 3.9 will boot fine by automatically setting resolution to
1024x768
However, no matter which combination of connectors I use issuing commands such
as:
xrandr --output VGA1 --auto --output DP2 --auto --output DP3 --auto
or
xrandr --output HDMI1 --auto --output DP2 --auto --output DP3 --auto
will always trigger this error.

Same monitor configuration works fine in Win7 so I assume that hardware is ok.
:|

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20130320/c5653f68/attachment-0001.html>