← Back to team overview

desktop-packages team mailing list archive

[Bug 1104230] Re: DisplayPort 1.2 MST support is missing in the Intel driver

 

Same thing, unfortunately:
[   37.881345] ------------[ cut here ]------------
[   37.881363] WARNING: CPU: 0 PID: 1850 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_ddi.c:850 intel_ddi_pll_select+0x7f/0x3c0 [i915]()
[   37.881364] Invalid DDI encoder type 11
[   37.881365] Modules linked in: ctr ccm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core btusb v4l2_common videodev media arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel iwlmvm mac80211 kvm iwlwifi joydev snd_seq_midi snd_seq_midi_event serio_raw cfg80211 snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_rawmidi snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep rtsx_pci_ms lpc_ich thinkpad_acpi memstick nvram snd_pcm shpchp bnep rfcomm mei_me mei snd_seq bluetooth 6lowpan_iphc snd_seq_device snd_timer snd soundcore mac_hid intel_smartconnect parport_pc ppdev binfmt_misc lp parport dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel i915 aes_x86_64
[   37.881392]  lrw gf128mul glue_helper ablk_helper cryptd psmouse i2c_algo_bit drm_kms_helper e1000e ahci drm libahci rtsx_pci ptp pps_core wmi video
[   37.881401] CPU: 0 PID: 1850 Comm: Xorg Tainted: G        W  OE 3.16.0-25-generic #33hf73386v20141106b1-Ubuntu
[   37.881402] Hardware name: LENOVO 20AQ005YUS/20AQ005YUS, BIOS GJET75WW (2.25 ) 03/28/2014
[   37.881403]  0000000000000009 ffff880211cefaf0 ffffffff8178015c ffff880211cefb38
[   37.881406]  ffff880211cefb28 ffffffff8106fd7d ffff880212aaf000 000000000000000b
[   37.881408]  ffff88020ed80000 0000000000083d60 ffff88020f6d8c00 ffff880211cefb88
[   37.881410] Call Trace:
[   37.881422]  [<ffffffff8178015c>] dump_stack+0x45/0x56
[   37.881425]  [<ffffffff8106fd7d>] warn_slowpath_common+0x7d/0xa0
[   37.881428]  [<ffffffff8106fdec>] warn_slowpath_fmt+0x4c/0x50
[   37.881444]  [<ffffffffc0250c4f>] intel_ddi_pll_select+0x7f/0x3c0 [i915]
[   37.881458]  [<ffffffffc022cd62>] haswell_crtc_mode_set+0x12/0x40 [i915]
[   37.881472]  [<ffffffffc023c176>] __intel_set_mode+0x6d6/0xab0 [i915]
[   37.881487]  [<ffffffffc023f456>] intel_set_mode+0x16/0x30 [i915]
[   37.881500]  [<ffffffffc024056a>] intel_crtc_set_config+0xa9a/0xe30 [i915]
[   37.881512]  [<ffffffffc00f9571>] drm_mode_set_config_internal+0x61/0xe0 [drm]
[   37.881523]  [<ffffffffc00fd503>] drm_mode_setcrtc+0x283/0x580 [drm]
[   37.881531]  [<ffffffffc00eda4f>] drm_ioctl+0x1df/0x680 [drm]
[   37.881535]  [<ffffffff811f4c28>] do_vfs_ioctl+0x2c8/0x4a0
[   37.881537]  [<ffffffff811e3201>] ? __sb_end_write+0x31/0x60
[   37.881540]  [<ffffffff811e0d72>] ? vfs_write+0x1b2/0x1f0
[   37.881542]  [<ffffffff811f4e81>] SyS_ioctl+0x81/0xa0
[   37.881544]  [<ffffffff817881ad>] system_call_fastpath+0x1a/0x1f
[   37.881546] ---[ end trace a3c6b6c6a37433c4 ]---
[   37.881548] [drm:intel_crtc_set_config] failed to set mode on [CRTC:9], err = -22
[   37.881550] [drm:intel_modeset_affected_pipes] set mode pipe masks: modeset: 0, prepare: 0, disable: 2
[   37.881555] [drm:intel_connector_check_state] [CONNECTOR:15:eDP-1]
[   37.881558] [drm:check_encoder_state] [ENCODER:14:TMDS-14]
[   37.881559] [drm:check_encoder_state] [ENCODER:22:TMDS-22]
[   37.881561] [drm:check_encoder_state] [ENCODER:24:DP MST-24]
[   37.881562] [drm:check_encoder_state] [ENCODER:25:DP MST-25]
[   37.881563] [drm:check_encoder_state] [ENCODER:26:DP MST-26]
[   37.881564] [drm:check_encoder_state] [ENCODER:28:TMDS-28]
[   37.881565] [drm:check_encoder_state] [ENCODER:30:DP MST-30]
[   37.881566] [drm:check_encoder_state] [ENCODER:31:DP MST-31]
[   37.881568] [drm:check_encoder_state] [ENCODER:32:DP MST-32]
[   37.881569] [drm:check_crtc_state] [CRTC:6]
[   37.881574] [drm:check_crtc_state] [CRTC:9]
[   37.881576] [drm:check_crtc_state] [CRTC:12]
[   37.881602] [drm:drm_mode_getresources] CRTC[3] CONNECTORS[7] ENCODERS[9]


Just in case I've done something wrong, here's all my versions of things again:
Linux dib 3.16.0-25-generic #33hf73386v20141106b1-Ubuntu SMP Thu Nov 6 14:20:03 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
➜  log  cat Xorg.0.log
[    11.322] 
X.Org X Server 1.16.1.901 (1.16.2 RC 1)
Release Date: 2014-11-02
[    11.322] X Protocol Version 11, Revision 0
[    11.322] Build Operating System: Linux 3.13.0-39-generic x86_64 Ubuntu
[    11.322] Current Operating System: Linux dib 3.16.0-25-generic #33hf73386v20141106b1-Ubuntu SMP Thu Nov 6 14:20:03 UTC 2014 x86_64
[    11.322] Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash drm.debug=0x06 vt.handoff=7
<snip>
[    11.343] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20080730
[    11.343] (II) intel(0): SNA compiled: xserver-xorg-video-intel 2:2.99.916+git20141120.0f15b8b4-0ubuntu0sarvatt (Robert Hooker <sarvatt@xxxxxxxxxx>)
[    11.343] (II) intel(0): SNA compiled for use with valgrind

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1104230

Title:
  DisplayPort 1.2 MST support is missing in the Intel driver

Status in X.org xf86-video-intel:
  Unknown
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Confirmed

Bug description:
  SRU Justification:

  Impact: Many users expect the possibility to use the DP1.2 MST feature which
  enables them to use a number of different display setups: daisy-chaining
  DP1.2 displays, some 4K displays appearing as 2 separate displays, 3D displays.
  This however is not supported in Ubuntu stable kernel.

  Fix: A series of 18 cherry-picks from v3.17 kernel backported to v3.16 by
  the original author of the feature: David Airlie.

  Regression Potential: These patches were merged upstream in v3.17 without any
  reported regressions.

  Original description:

  I have two recent DisplayPort monitors, both supporting the 1.2
  version of the standard and one containing an MST hub (DELL 2913WM).

  I have an Intel Haswell based NUC connected over mini-displayport to
  the display containing the hub, then the second display is plugged in
  that one over DisplayPort.

  DisplayPort 1.2 is enabled on the display containing the hub and the
  second display lights up fine but just works as a clone of the first
  display, without ever showing up in xrandr, dmesg or any other useful
  logs I could find.

  My understanding of MST is that the second display should show up as
  DP2 on my laptop so I can configure it as I would any other display.

  UPDATE: Updated the bug report after it was pointed out that the
  original test hardware, a Lenovo x230 isn't DP 1.2 capable. The same
  test on hardware also fails, due to missing support for MST in the
  driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1104230/+subscriptions