Bug 82763 - [drm:intel_dp_start_link_train] error on connecting an active DP-to-VGA converter
Summary: [drm:intel_dp_start_link_train] error on connecting an active DP-to-VGA conve...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-18 11:14 UTC by Daniele Pizzolli
Modified: 2017-07-24 22:52 UTC (History)
1 user (show)

See Also:
i915 platform: HSW
i915 features: display/DP, display/DP MST


Attachments

Description Daniele Pizzolli 2014-08-18 11:14:44 UTC
The hardware:

Dell Inc. Latitude E5440/08RCYC, BIOS A07 

lspci:
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)

On debian jessies with the latest stable kernel: Linux 3.16

While plugging in a VGA monitor I see a warning in dmesg output and
the monitor does not show up in the xrandr output.

dmesg:


[29593.764302] WARNING: CPU: 0 PID: 5715 at drivers/gpu/drm/i915/intel_dp.c:3122 intel_dp_complete_link_train+0xe9/0x330 [i915]()
[29593.764303] Modules linked in: btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs libcrc32c hid_generic usbhid hid pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic iTCO_wdt iTCO_vendor_support joydev nouveau dell_wmi sparse_keymap mxm_wmi ppdev arc4 dell_laptop dcdbas x86_pkg_temp_thermal intel_powerclamp intel_rapl coretemp kvm_intel kvm pcspkr evdev psmouse serio_raw ecb btusb bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media iwlmvm mac80211 iwlwifi cfg80211 ttm snd_hda_intel lpc_ich snd_hda_controller mfd_core rfkill snd_hda_codec i2c_i801 mei_me i915 snd_hwdep mei snd_pcm snd_timer snd soundcore shpchp parport_pc drm_kms_helper parport drm i2c_algo_bit wmi i2c_core video battery ac button processor loop fuse autofs4 ext4 crc16 mbcache jbd2 dm_crypt dm_mod sg sd_mod sr_mod crc_t10dif cdrom crct10dif_generic uas usb_storage crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd ahci libahci libata ehci_pci scsi_mod ehci_hcd xhci_hcd sdhci_pci sdhci e1000e mmc_core ptp usbcore pps_core usb_common thermal thermal_sys
[29593.764357] CPU: 0 PID: 5715 Comm: kworker/0:1 Tainted: G        W  O  3.16.0+ #1
[29593.764358] Hardware name: Dell Inc. Latitude E5440/08RCYC, BIOS A07 06/26/2014
[29593.764366] Workqueue: events i915_hotplug_work_func [i915]
[29593.764367]  0000000000000009 ffffffff814ef07d 0000000000000000 ffffffff81064c12
[29593.764369]  ffff8800cb1380d8 0000000000000006 0000000000000000 ffff8800cb138118
[29593.764372]  ffff8800cb1380f3 ffffffffa04ace39 8000000601000001 00000080777780d8
[29593.764374] Call Trace:
[29593.764377]  [<ffffffff814ef07d>] ? dump_stack+0x41/0x51
[29593.764380]  [<ffffffff81064c12>] ? warn_slowpath_common+0x72/0x90
[29593.764387]  [<ffffffffa04ace39>] ? intel_dp_complete_link_train+0xe9/0x330 [i915]
[29593.764395]  [<ffffffffa04ad641>] ? intel_dp_check_link_status+0xa1/0x180 [i915]
[29593.764402]  [<ffffffffa046c8e1>] ? i915_hotplug_work_func+0x1e1/0x330 [i915]
[29593.764405]  [<ffffffff8107e9ef>] ? process_one_work+0x16f/0x450
[29593.764408]  [<ffffffff8107f333>] ? worker_thread+0x63/0x540
[29593.764410]  [<ffffffff8107f2d0>] ? rescuer_thread+0x2d0/0x2d0
[29593.764413]  [<ffffffff8108534a>] ? kthread+0xca/0xe0
[29593.764415]  [<ffffffff81085280>] ? kthread_create_on_node+0x180/0x180
[29593.764417]  [<ffffffff814f4bfc>] ? ret_from_fork+0x7c/0xb0
[29593.764419]  [<ffffffff81085280>] ? kthread_create_on_node+0x180/0x180
[29593.764420] ---[ end trace 2feeb7f0c4f81b25 ]---
[29593.788656] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting

Let me know if you need further information.
Comment 1 Daniele Pizzolli 2014-08-19 07:34:04 UTC
With the kernel 3.16.1 the xrandr output is correct and I am able to use the display.

Sometimes (not reproducible) I got the following in the dmesg output:

[  205.455231] WARNING: CPU: 0 PID: 951 at drivers/gpu/drm/i915/intel_dp.c:3122 intel_dp_complete_link_train+0xe9/0x330 [i915]()
[  205.455233] Modules linked in: vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) joydev arc4 nouveau dell_wmi sparse_keymap mxm_wmi iTCO_wdt iTCO_vendor_support ppdev dell_laptop dcdbas x86_pkg_temp_thermal intel_powerclamp intel_rapl coretemp kvm_intel kvm pcspkr ecb iwlmvm btusb bluetooth mac80211 uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media psmouse evdev serio_raw snd_hda_codec_realtek snd_hda_codec_generic i2c_i801 iwlwifi cfg80211 ttm snd_hda_intel i915 rfkill lpc_ich snd_hda_controller mfd_core shpchp snd_hda_codec i2c_algo_bit snd_hwdep drm_kms_helper parport_pc parport wmi drm snd_pcm snd_timer video i2c_core battery snd ac mei_me soundcore button mei processor loop fuse autofs4 ext4 crc16 mbcache jbd2 dm_crypt dm_mod sg sd_mod sr_mod crc_t10dif cdrom crct10dif_generic uas usb_storage crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd ahci sdhci_pci sdhci libahci mmc_core libata ehci_pci ehci_hcd scsi_mod e1000e ptp pps_core xhci_hcd usbcore usb_common thermal thermal_sys
[  205.455287] CPU: 0 PID: 951 Comm: Xorg Tainted: G           O  3.16.1mine1+ #2
[  205.455289] Hardware name: Dell Inc. Latitude E5440/08RCYC, BIOS A07 06/26/2014
[  205.455290]  0000000000000009 ffffffff814dd60d 0000000000000000 ffffffff81064c12
[  205.455293]  ffff8802204a30d8 0000000000000001 0000000000000000 ffff8802204a3118
[  205.455295]  ffff8802204a30f3 ffffffffa04c3e39 8000000201000000 0000008000770001
[  205.455297] Call Trace:
[  205.455302]  [<ffffffff814dd60d>] ? dump_stack+0x41/0x51
[  205.455305]  [<ffffffff81064c12>] ? warn_slowpath_common+0x72/0x90
[  205.455313]  [<ffffffffa04c3e39>] ? intel_dp_complete_link_train+0xe9/0x330 [i915]
[  205.455320]  [<ffffffffa04bc399>] ? intel_ddi_pre_enable+0x189/0x1e0 [i915]
[  205.455328]  [<ffffffffa04a529c>] ? haswell_crtc_enable+0x39c/0xa30 [i915]
[  205.455336]  [<ffffffffa04bcd6b>] ? intel_ddi_pll_select+0x3b/0x3c0 [i915]
[  205.455343]  [<ffffffffa04a7b27>] ? __intel_set_mode+0x817/0x1660 [i915]
[  205.455346]  [<ffffffff81297832>] ? idr_get_empty_slot+0x192/0x3b0
[  205.455350]  [<ffffffff8117e975>] ? __kmalloc+0x1d5/0x4f0
[  205.455358]  [<ffffffffa04aaefd>] ? intel_set_mode+0xd/0x30 [i915]
[  205.455365]  [<ffffffffa04abf13>] ? intel_crtc_set_config+0xa23/0xd50 [i915]
[  205.455371]  [<ffffffffa039091a>] ? drm_mode_set_config_internal+0x5a/0xd0 [drm]
[  205.455377]  [<ffffffffa039424a>] ? drm_mode_setcrtc+0x25a/0x560 [drm]
[  205.455383]  [<ffffffffa03857f3>] ? drm_ioctl+0x1c3/0x5a0 [drm]
[  205.455386]  [<ffffffff811a9640>] ? do_vfs_ioctl+0x2d0/0x4a0
[  205.455389]  [<ffffffff8108272c>] ? task_work_run+0xac/0xe0
[  205.455391]  [<ffffffff811a9889>] ? SyS_ioctl+0x79/0x90
[  205.455393]  [<ffffffff814e34ea>] ? int_signal+0x12/0x17
[  205.455396]  [<ffffffff814e322d>] ? system_call_fastpath+0x1a/0x1f


Something strange: after a reboot into 3.16 I do see the monitor in xrandr,
and no more warning in dmesg.
Maybe is because of the warm reboot?

I available for testing various configurations, if you need.
Comment 2 Daniele Pizzolli 2014-08-25 10:13:26 UTC
I am not sure if the problem is the same.

With the same kernel of the latest comment 3.16, with a different screen
that support up to 1920x1200 modes, I was able only see the screen with
xrandr to get few of them working.

Modes and test results:

1920x1200 Warning in dmesg, not working: blank screen
1920x1080 Warning in dmesg, not working: blank screen
1600x1200 Warning in dmesg, not working: blank screen
1680x1050 Warning in dmesg, not working: blank screen
1280x1024 Working
1440x900  Working
1024x768  Not tested
800x600   Not tested
640x480   Not tested

Warning in dmesg:

[ 2727.529259] ------------[ cut here ]------------
[ 2727.529268] WARNING: CPU: 0 PID: 904 at drivers/gpu/drm/i915/intel_dp.c:3122 intel_dp_complete_link_train+0xe9/0x330 [i915]()
[ 2727.529269] Modules linked in: pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) snd_hda_codec_hdmi joydev arc4 dell_wmi sparse_keymap iTCO_wdt iTCO_vendor_support x86_pkg_temp_thermal dell_laptop intel_powerclamp dcdbas intel_rapl ecb iwlmvm coretemp mac80211 kvm_intel uvcvideo nouveau videobuf2_vmalloc videobuf2_memops btusb kvm videobuf2_core v4l2_common bluetooth videodev media mxm_wmi pcspkr evdev psmouse serio_raw loop fuse iwlwifi cfg80211 snd_hda_codec_realtek snd_hda_codec_generic lpc_ich i915 rfkill mfd_core ttm i2c_i801 battery snd_hda_intel snd_hda_controller drm_kms_helper wmi snd_hda_codec drm video snd_hwdep i2c_algo_bit snd_pcm ac snd_timer button mei_me i2c_core snd mei soundcore shpchp processor parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 dm_crypt dm_mod sg sd_mod sr_mod crc_t10dif cdrom crct10dif_generic mmc_block crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd ahci libahci libata scsi_mod sdhci_pci sdhci ehci_pci ehci_hcd mmc_core xhci_hcd e1000e ptp thermal usbcore pps_core thermal_sys usb_common
[ 2727.529316] CPU: 0 PID: 904 Comm: Xorg Tainted: G        W  O  3.16.0+ #1
[ 2727.529317] Hardware name: Dell Inc. Latitude E5440/08RCYC, BIOS A07 06/26/2014
[ 2727.529318]  0000000000000009 ffffffff814ef07d 0000000000000000 ffffffff81064c12
[ 2727.529320]  ffff8802232b18d8 0000000000000006 0000000000000000 ffff8802232b1918
[ 2727.529322]  ffff8802232b18f3 ffffffffa050ce39 8000000601000000 0000008077770001
[ 2727.529324] Call Trace:
[ 2727.529327]  [<ffffffff814ef07d>] ? dump_stack+0x41/0x51
[ 2727.529329]  [<ffffffff81064c12>] ? warn_slowpath_common+0x72/0x90
[ 2727.529337]  [<ffffffffa050ce39>] ? intel_dp_complete_link_train+0xe9/0x330 [i915]
[ 2727.529344]  [<ffffffffa0505399>] ? intel_ddi_pre_enable+0x189/0x1e0 [i915]
[ 2727.529352]  [<ffffffffa04ee29c>] ? haswell_crtc_enable+0x39c/0xa30 [i915]
[ 2727.529359]  [<ffffffffa0505d6b>] ? intel_ddi_pll_select+0x3b/0x3c0 [i915]
[ 2727.529366]  [<ffffffffa04f0b27>] ? __intel_set_mode+0x817/0x1660 [i915]
[ 2727.529369]  [<ffffffff81299e52>] ? idr_get_empty_slot+0x192/0x3b0
[ 2727.529371]  [<ffffffff81180c05>] ? __kmalloc+0x1d5/0x4f0
[ 2727.529378]  [<ffffffffa04f3efd>] ? intel_set_mode+0xd/0x30 [i915]
[ 2727.529385]  [<ffffffffa04f4f13>] ? intel_crtc_set_config+0xa23/0xd50 [i915]
[ 2727.529391]  [<ffffffffa041a91a>] ? drm_mode_set_config_internal+0x5a/0xd0 [drm]
[ 2727.529396]  [<ffffffffa041e24a>] ? drm_mode_setcrtc+0x25a/0x560 [drm]
[ 2727.529401]  [<ffffffffa040f7f3>] ? drm_ioctl+0x1c3/0x5a0 [drm]
[ 2727.529404]  [<ffffffff811abb20>] ? do_vfs_ioctl+0x2d0/0x4a0
[ 2727.529406]  [<ffffffff8108272c>] ? task_work_run+0xac/0xe0
[ 2727.529407]  [<ffffffff811abd69>] ? SyS_ioctl+0x79/0x90
[ 2727.529410]  [<ffffffff814f4f6a>] ? int_signal+0x12/0x17
[ 2727.529412]  [<ffffffff814f4cad>] ? system_call_fastpath+0x1a/0x1f
[ 2727.529413] ---[ end trace e99bbd501657ce98 ]---
[ 2727.553598] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting
Comment 3 Daniele Pizzolli 2014-09-05 16:10:28 UTC
Additional test on 3.17.0-rc3

This is worse than 3.16.  The screen remains black for all modes.

I used the following snippet:

MODES="1920x1200 1920x1080 1600x1200 1680x1050 1280x1024 1440x900 1280x960 1024x768 800x600 640x480"

sudo dmesg -c
for MODE in $MODES;
do
    printf "Trying mode: %s\n" "$MODE"
    xrandr --output DP4 --mode $MODE
    sudo dmesg -c
    sleep 2
done

To get the following output:

Trying mode: 1920x1200
[33982.971039] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR* uncleared fifo underrun on pipe B
[33982.971043] [drm:ivb_err_int_handler] *ERROR* Pipe B FIFO underrun
Trying mode: 1920x1080
Trying mode: 1600x1200
[33987.636507] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR* uncleared fifo underrun on pipe B
[33987.636512] [drm:ivb_err_int_handler] *ERROR* Pipe B FIFO underrun
Trying mode: 1680x1050
Trying mode: 1280x1024
[33992.076803] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR* uncleared fifo underrun on pipe B
[33992.076807] [drm:ivb_err_int_handler] *ERROR* Pipe B FIFO underrun
[33992.235904] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR* uncleared fifo underrun on pipe B
[33992.235908] [drm:ivb_err_int_handler] *ERROR* Pipe B FIFO underrun
Trying mode: 1440x900
Trying mode: 1280x960
[33996.655649] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR* uncleared fifo underrun on pipe B
[33996.655656] [drm:ivb_err_int_handler] *ERROR* Pipe B FIFO underrun
[33996.819414] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR* uncleared fifo underrun on pipe B
[33996.819418] [drm:ivb_err_int_handler] *ERROR* Pipe B FIFO underrun
Trying mode: 1024x768
[33999.101794] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR* uncleared fifo underrun on pipe B
[33999.101798] [drm:ivb_err_int_handler] *ERROR* Pipe B FIFO underrun
Trying mode: 800x600
[34001.302311] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR* uncleared fifo underrun on pipe B
[34001.302315] [drm:ivb_err_int_handler] *ERROR* Pipe B FIFO underrun
Trying mode: 640x480
[34003.634664] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR* uncleared fifo underrun on pipe B
[34003.634668] [drm:ivb_err_int_handler] *ERROR* Pipe B FIFO underrun

Maybe now the problem is a duplicate of 83180
Comment 4 Jesse Barnes 2014-12-04 21:47:37 UTC
Hm well things are changing at least.  Too bad it's for the worse. :(

What's the model of DP-VGA dongle you're using?  We've definitely seen issues with some of them due to our DP training code.

It might be worth trying and even newer kernel too, the drm-intel-nightly branch from git://anongit.freedesktop.org/drm-intel.
Comment 5 Daniele Pizzolli 2014-12-05 08:01:31 UTC
> Hm well things are changing at least.  Too bad it's for the worse. :(

Oh, I try to stay with the current (or -rc) kernel, and things were
getting better. With 3.18.0-rc3 sometimes I need only to restart X to
see all the monitors connected.

> What's the model of DP-VGA dongle you're using?  We've definitely seen
> issues with some of them due to our DP training code.

No dongle, I use the integrated VGA port (and sometimes the VGA port
on the dell docking station model pr02x, if it does matter).

It might be worth trying and even newer kernel too, the
drm-intel-nightly branch from git://anongit.freedesktop.org/drm-intel.

Ok, will give a try and add info to this bug.  Thanks.
Comment 6 Daniele Pizzolli 2014-12-21 20:32:55 UTC
> Ok, will give a try and add info to this bug.  Thanks.

Hello,

with the latest drm-intel-nightly (commit id
4fa23142a15526f4a4b5df61f26eacdd558a849a)

I see the monitor in xrandr only if it is connected at boot time:

Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
eDP1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 309mm x 174mm
   1600x900      59.99 +
   1440x900      59.89  
   1360x768      59.80    59.96  
   1152x864      60.00  
   1024x768      60.00* 
   800x600       60.32    56.25  
   640x480       59.94  
DP1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
DP4 connected 1024x768+0+0 (normal left inverted right x axis y axis) 518mm x 324mm
   1920x1200     59.88 +
   1920x1080     59.99  
   1600x1200     60.00  
   1680x1050     59.95  
   1280x1024     60.02  
   1440x900      59.89  
   1280x960      60.00  
   1024x768      60.00* 
   800x600       60.32  
   640x480       60.00  


If I start the laptop without the monitor attached xrandr shows only:

Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
eDP1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 309mm x 174mm
   1600x900      59.99 +
   1440x900      59.89  
   1360x768      59.80    59.96  
   1152x864      60.00  
   1024x768      60.00* 
   800x600       60.32    56.25  
   640x480       59.94  
DP1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)

A quick search in dmesg and /var/log/Xorg.0.log did not show
anomalies.

Let me know if you need further information.
Comment 7 Chris Wilson 2014-12-21 20:50:42 UTC
Interesting sounds like it is acting as a MST device as well. Could you please try xf86-video-intel-2.99.917.
Comment 8 Daniele Pizzolli 2014-12-22 08:38:07 UTC
> Interesting sounds like it is acting as a MST device as well. Could
> you please try xf86-video-intel-2.99.917.

Thanks, done, using the git sources and the and debian/rules binary in
the package xserver-xorg-video-intel-2.99.916+git20141119 to build a
deb package.

Since the debian packaging seems to not introduce any variation apart
of a new utility (intel-virtual-output) I guess the following is fine:

grep -si 2.99 /var/log/Xorg.0.log
[    46.446] 	compiled for 1.16.2.901, module version = 2.99.917
[    46.459] (II) intel(0): SNA compiled: xserver-xorg-video-intel 2:2.99.916+git20141119-1~exp1 (maximilian attems <hidden>)

Please correct me if I am wrong.

Unfortunately I do not have access to the monitor right now (will do
the test around Christmas), I see that the xrand output now shows
DP1-1 for the old DP2 and DP1-2 for the old DP-3 and DP1-3 for the old
DP-4:

Screen 0: minimum 8 x 8, current 1600 x 900, maximum 32767 x 32767
eDP1 connected 1600x900+0+0 (normal left inverted right x axis y axis) 309mm x 174mm
   1600x900      59.99*+
   1440x900      59.89  
   1360x768      59.80    59.96  
   1152x864      60.00  
   1024x768      60.00  
   800x600       60.32    56.25  
   640x480       59.94  
DP1 disconnected (normal left inverted right x axis y axis)
DP1-1 connected (normal left inverted right x axis y axis)
   1440x900      59.89 +  74.98  
   1280x1024     75.02    60.02  
   1280x800      59.91  
   1152x864      75.00  
   1024x768      75.08    70.07    60.00  
   832x624       74.55  
   800x600       72.19    75.00    60.32    56.25  
   640x480       75.00    72.81    66.67    60.00  
   720x400       70.08  
DP1-2 connected (normal left inverted right x axis y axis)
   1280x1024     60.02 +  75.02  
   1152x864      75.00  
   1024x768      75.08    60.00  
   800x600       75.00    60.32  
   640x480       75.00    60.00  
   720x400       70.08  
DP1-3 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
Comment 9 Daniele Pizzolli 2014-12-24 15:48:27 UTC
(In reply to Daniele Pizzolli from comment #8)

[]

> Unfortunately I do not have access to the monitor right now (will do
> the test around Christmas), I see that the xrand output now shows
> DP1-1 for the old DP2 and DP1-2 for the old DP-3 and DP1-3 for the old
> DP-4:

[]

Bad news.  After disconnecting the dock station I still see the olds
monitor as connected in xrandr output and not the new one connected
directly to the laptop.  The same monitor show up (and works) if I use
an HDMI cable.  This is the trace back I got:

[59717.527058] ------------[ cut here ]------------
[59717.527075] WARNING: CPU: 0 PID: 1055 at drivers/gpu/drm/drm_dp_mst_topology.c:1268 process_single_tx_qlock+0x5d0/0x640 [drm_kms_helper]()
[59717.527077] fail
[59717.527078] Modules linked in: md4 hmac nls_utf8 cifs dns_resolver fscache xt_nat xt_tcpudp sdhci_pci sdhci mmc_core veth xt_addrtype xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c iptable_filter ip_tables x_tables binfmt_misc pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) hid_generic usbhid hid joydev usb_storage snd_hda_codec_hdmi iTCO_wdt iTCO_vendor_support arc4 ppdev dell_wmi sparse_keymap ecb btusb bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media dell_laptop dcdbas iwlmvm mac80211 x86_pkg_temp_thermal intel_powerclamp intel_rapl coretemp kvm_intel kvm nouveau psmouse evdev iwlwifi
[59717.527119]  mxm_wmi pcspkr serio_raw ttm cfg80211 i2c_i801 lpc_ich mfd_core rfkill snd_hda_codec_realtek snd_hda_codec_generic battery i915 8250_fintek parport_pc parport snd_hda_intel snd_hda_controller wmi dell_smo8800 snd_hda_codec snd_hwdep drm_kms_helper snd_pcm drm video ac snd_timer snd xhci_pci i2c_algo_bit button soundcore shpchp xhci_hcd i2c_core mei_me mei processor loop fuse autofs4 ext4 crc16 mbcache jbd2 btrfs xor raid6_pq algif_skcipher af_alg dm_crypt dm_mod xts sg sr_mod cdrom sd_mod crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper ahci cryptd libahci ehci_pci libata ehci_hcd usbcore scsi_mod usb_common e1000e ptp pps_core thermal thermal_sys
[59717.527166] CPU: 0 PID: 1055 Comm: Xorg Tainted: G        W  O   3.18.0-2014y-12m-19d-14h-33m-07s+ #10
[59717.527167] Hardware name: Dell Inc. Latitude E5440/08RCYC, BIOS A07 06/26/2014
[59717.527169]  0000000000000000 0000000000000009 ffffffff8153e0a1 ffff88041914f908
[59717.527172]  ffffffff8106a137 0000000000000000 0000000000001000 0000000000000010
[59717.527175]  ffff88041870d608 000000000000000c ffffffff8106a19a ffffffffa0400b85
[59717.527178] Call Trace:
[59717.527183]  [<ffffffff8153e0a1>] ? dump_stack+0x41/0x51
[59717.527187]  [<ffffffff8106a137>] ? warn_slowpath_common+0x77/0x90
[59717.527191]  [<ffffffff8106a19a>] ? warn_slowpath_fmt+0x4a/0x50
[59717.527202]  [<ffffffffa03f4580>] ? process_single_tx_qlock+0x5d0/0x640 [drm_kms_helper]
[59717.527205]  [<ffffffff81541bae>] ? mutex_lock+0xe/0x30
[59717.527213]  [<ffffffffa03f4628>] ? process_single_down_tx_qlock+0x38/0x120 [drm_kms_helper]
[59717.527221]  [<ffffffffa03f476c>] ? drm_dp_queue_down_tx+0x5c/0x70 [drm_kms_helper]
[59717.527229]  [<ffffffffa03f6f7e>] ? drm_dp_mst_i2c_xfer+0x15e/0x270 [drm_kms_helper]
[59717.527241]  [<ffffffffa049a179>] ? drm_for_each_detailed_block+0x39/0x150 [drm]
[59717.527250]  [<ffffffffa040e23c>] ? __i2c_transfer+0x6c/0x200 [i2c_core]
[59717.527258]  [<ffffffffa040f5c7>] ? i2c_transfer+0x77/0xd0 [i2c_core]
[59717.527269]  [<ffffffffa049addc>] ? drm_do_probe_ddc_edid+0xcc/0x140 [drm]
[59717.527282]  [<ffffffffa049c46d>] ? drm_get_edid+0x2d/0x3f0 [drm]
[59717.527292]  [<ffffffffa03f5dcc>] ? drm_dp_mst_get_edid+0x6c/0x80 [drm_kms_helper]
[59717.527319]  [<ffffffffa05beb88>] ? intel_dp_mst_get_modes+0x28/0x50 [i915]
[59717.527328]  [<ffffffffa03f287a>] ? drm_helper_probe_single_connector_modes_merge_bits+0xea/0x450 [drm_kms_helper]
[59717.527331]  [<ffffffff81541bae>] ? mutex_lock+0xe/0x30
[59717.527343]  [<ffffffffa0496c19>] ? drm_mode_getconnector+0x339/0x3a0 [drm]
[59717.527356]  [<ffffffffa0488723>] ? drm_ioctl+0x1c3/0x5a0 [drm]
[59717.527360]  [<ffffffff811cdeb0>] ? do_vfs_ioctl+0x2d0/0x4a0
[59717.527364]  [<ffffffff811bf3b3>] ? SYSC_newfstat+0x23/0x30
[59717.527368]  [<ffffffff811ce101>] ? SyS_ioctl+0x81/0xa0
[59717.527372]  [<ffffffff81543e2d>] ? system_call_fastpath+0x16/0x1b
[59717.527374] ---[ end trace 873cfc9233e4a25f ]---

Please let me know if you need more info/test. Thanks and happy holidays.
Comment 10 Jani Nikula 2015-10-23 09:58:55 UTC
Timeout, presumed fixed upstream, closing. Please reopen if the problem persists with latest kernels.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.