[Bug 71701] New: Regression, Dual-Head, i915 mode-setting driver, "pipe B stuck"

Fri Mar 7 14:31:51 PST 2014

https://bugzilla.kernel.org/show_bug.cgi?id=71701

            Bug ID: 71701
           Summary: Regression, Dual-Head, i915 mode-setting driver, "pipe
                    B stuck"
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.13.6
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - Intel)
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: bugs-a13 at moonlit-rail.com
                CC: intel-gfx-bugs at lists.freedesktop.org
        Regression: Yes

A regression introduced in mainline kernel 3.13.6 (not present in
simultaneously-released 3.10.33) has caused the i915 mode-setting driver to
fail to properly initialize, disabling one of two monitors in a dual-head
setup.

After X.org 1.14.3 takes over the display, the monitor remains disabled, even
though the X.org log says it found the monitor and EDID and ostensibly set it
up for use.  Using KDE's monitor-configuration tool, manually disabling the
monitor and re-enabling it will bring it back to life - temporarily, until the
next boot of course.

Chipset: Intel Core i7-3770 internal graphics controller.
         ("Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics
Controller (rev 09)")
Hardware: Dell OptiPlex 9010 SFF desktop, one VGA connector, two DisplayPort
Monitor 1 (left) : Port VGA1, unaffected by bug
Monitor 2 (right): Port DP2, affected by bug

As an aside, the machine boots to BIOS (or LILO prompt) with port DP2 (right
monitor) enabled, and VGA1 disabled.  After passing control to kernel 3.13.6,
left monitor powers up and right monitor enters sleep.

Kernel boot (dmesg) log says quite a bit about the issue:

Linux agpgart interface v0.103
[drm] Initialized drm 1.1.0 20060810
[drm] Memory usable by graphics device = 2048M
i915 0000:00:02.0: irq 40 for MSI/MSI-X
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] Driver supports precise vblank timestamp query.
vgaarb: device changed decodes:
PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+me
fbcon: inteldrmfb (fb0) is primary device
[drm:intel_dp_aux_native_write] *ERROR* too many retries, giving up
[drm:intel_dp_start_link_train] *ERROR* failed to enable link training
[drm:intel_dp_aux_native_write] *ERROR* too many retries, giving up
[drm:intel_dp_complete_link_train] *ERROR* failed to start channel equalization
[drm:cpt_verify_modeset] *ERROR* mode set failed: pipe B stuck
------------[ cut here ]------------
WARNING: CPU: 0 PID: 1 at drivers/gpu/drm/i915/intel_display.c:9226
intel_modese
encoder's hw state doesn't match sw tracking (expected 1, found 0)
Modules linked in:
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.13.6 #1
Hardware name: Dell Inc. OptiPlex 9010/051FJ8, BIOS A08 09/19/2012
 0000000000000009 ffffffff816bfa8b ffff88011929f7a8 ffffffff810883ed
 ffff88011929f810 ffff88011929f7f8 0000000000000001 ffff880118830b10
 ffff880118c71000 ffffffff81088457 ffffffff818766b8 ffff880100000028
Call Trace:
 [<ffffffff816bfa8b>] ? dump_stack+0x41/0x51
 [<ffffffff810883ed>] ? warn_slowpath_common+0x6d/0x90
 [<ffffffff81088457>] ? warn_slowpath_fmt+0x47/0x50
 [<ffffffff813931fd>] ? intel_modeset_check_state+0x5fd/0x750
 [<ffffffff813933dd>] ? intel_set_mode+0x1d/0x30
 [<ffffffff81393c4d>] ? intel_crtc_set_config+0x77d/0x970
 [<ffffffff8134bef5>] ? drm_mode_set_config_internal+0x55/0xd0
 [<ffffffff8133d2e6>] ? drm_fb_helper_set_par+0x66/0xe0
 [<ffffffff812d1f6c>] ? fbcon_init+0x50c/0x5a0
 [<ffffffff8131eb6e>] ? visual_init+0xae/0x110
 [<ffffffff81321125>] ? do_bind_con_driver+0x155/0x330
 [<ffffffff813218a3>] ? do_take_over_console+0xf3/0x1a0
 [<ffffffff812cdbe3>] ? do_fbcon_takeover+0x53/0xb0
 [<ffffffff810a74a4>] ? notifier_call_chain+0x44/0x70
 [<ffffffff810a7742>] ? __blocking_notifier_call_chain+0x42/0x60
 [<ffffffff812c5d95>] ? register_framebuffer+0x1d5/0x300
 [<ffffffff8133cfbd>] ? drm_fb_helper_initial_config+0x35d/0x530
 [<ffffffff8139635d>] ? intel_modeset_setup_hw_state+0x89d/0xb30
 [<ffffffff813c4c0d>] ? gen6_write32+0x1d/0x80
 [<ffffffff8135db68>] ? i915_driver_load+0xe38/0xe90
 [<ffffffff81346461>] ? drm_get_minor+0x181/0x1e0
 [<ffffffff81346556>] ? drm_dev_register+0x96/0x1d0
 [<ffffffff813480b4>] ? drm_get_pci_dev+0x84/0x130
 [<ffffffff812b4309>] ? local_pci_probe+0x19/0x60
 [<ffffffff812b507a>] ? pci_device_probe+0xca/0x120
 [<ffffffff813d01c1>] ? really_probe+0x51/0x200
 [<ffffffff813d0441>] ? __driver_attach+0x81/0x90
 [<ffffffff813d03c0>] ? __device_attach+0x50/0x50
 [<ffffffff813ce5e3>] ? bus_for_each_dev+0x53/0x90
 [<ffffffff813cf9d8>] ? bus_add_driver+0x168/0x220
 [<ffffffff819d350c>] ? drm_core_init+0x104/0x104
 [<ffffffff813d0a16>] ? driver_register+0x56/0xd0
 [<ffffffff819d350c>] ? drm_core_init+0x104/0x104
 [<ffffffff8100030a>] ? do_one_initcall+0xea/0x130
 [<ffffffff810a1da2>] ? parse_args+0x1f2/0x320
 [<ffffffff819b1e07>] ? kernel_init_freeable+0x106/0x188
 [<ffffffff819b17c5>] ? do_early_param+0x81/0x81
 [<ffffffff816b8120>] ? rest_init+0x70/0x70
 [<ffffffff816b8125>] ? kernel_init+0x5/0x120
 [<ffffffff816c767c>] ? ret_from_fork+0x7c/0xb0
 [<ffffffff816b8120>] ? rest_init+0x70/0x70
---[ end trace 5e14cc86efb031cf ]---
[drm:intel_pipe_config_compare] *ERROR* mismatch in has_dp_encoder (expected 1,
found 0)

The same BUG output as above repeats once more (elided here) before the kernel
finishes its boot sequence.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.