[Lenovo ThinkPad Yoga Type 20C0] Laptop sometimes doesn't detect external monitor when docked into ThinkPad OneLink Pro Dock

[vik]

Lenovo Thinkpad Yoga S1 sometimes doesn't detect external monitor when docked with a Onelink Pro dock. Problem has also occurred on a non-Pro OneLink dock.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
.tmp.unity_support_test.0:

ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
BootLog: /dev/sda1: clean, 860723/30769152 files, 38024704/123073521 blocks
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed May 4 11:47:20 2016
DistUpgraded: 2016-04-23 16:11:36,997 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed
 virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:2217]
InstallationDate: Installed on 2015-12-02 (153 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: LENOVO 20C0S1CWAU
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=bbf6846f-7622-4638-8e7e-286b6badb71d ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-04-23 (10 days ago)
dmi.bios.date: 01/14/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: GQET48WW (1.28 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20C0S1CWAU
dmi.board.vendor: LENOVO
dmi.board.version: 0B98417 PRO
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrGQET48WW(1.28):bd01/14/2016:svnLENOVO:pn20C0S1CWAU:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S1CWAU:rvr0B98417PRO:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20C0S1CWAU
dmi.product.version: ThinkPad S1 Yoga
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed May 4 08:27:55 2016
xserver.configfile: default
xserver.errors:
 Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device.
 Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device.
 Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 1079
 vendor LGD
xserver.version: 2:1.18.3-1ubuntu2

[vik (askvictor)]

Unfortunately the sticker has rubbed off; why would it be any different to the DMI data?

[Launchpad Janitor (janitor)]

[Expired for xorg (Ubuntu) because there has been no activity for 60 days.]

[vik (askvictor)]

I can try to update the BIOS, but given that the BIOS release notes (see below) don't mention anything regarding this, it's not likely to fix anything. The issue disappeared for a while, but has returned in the past month or so; I'm guess a kernel driver update fixed it, then regressed.

BIOS 1.29 release notes:
[Important updates]
  Nothing.

[New functions or enhancements]
- Updated Realtek v2.06 PXE rom and v2.016 UNDI driver.

[Problem fixes]
  Nothing.

[vik (askvictor)]

Currently showing the following errors in syslog:
Jul 11 11:50:46 vikyoga kernel: [268224.347720] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
Jul 11 11:50:47 vikyoga kernel: [268224.963062] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
Jul 11 11:50:47 vikyoga kernel: [268225.579131] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
Jul 11 11:50:48 vikyoga kernel: [268226.194219] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
Jul 11 11:50:49 vikyoga kernel: [268226.809386] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
Jul 11 11:50:49 vikyoga kernel: [268226.809626] [drm:intel_dp_link_training_channel_equalization [i915]] *ERROR* failed to train DP, aborting
Jul 11 11:50:49 vikyoga kernel: [268226.820982] [drm:intel_dp_link_training_channel_equalization [i915]] *ERROR* Timed out waiting for DP idle patterns
Jul 11 11:50:49 vikyoga kernel: [268227.420776] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
Jul 11 11:50:50 vikyoga kernel: [268228.035941] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
Jul 11 11:50:51 vikyoga kernel: [268228.651115] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
Jul 11 11:50:51 vikyoga kernel: [268229.266199] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
Jul 11 11:50:52 vikyoga kernel: [268229.881361] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
Jul 11 11:50:52 vikyoga kernel: [268230.496507] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
Jul 11 11:50:53 vikyoga kernel: [268231.111673] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
Jul 11 11:50:53 vikyoga kernel: [268231.111912] [drm:intel_dp_link_training_channel_equalization [i915]] *ERROR* failed to train DP, aborting
Jul 11 11:50:53 vikyoga kernel: [268231.122223] [drm:intel_dp_link_training_channel_equalization [i915]] *ERROR* Timed out waiting for DP idle patterns

[vik (askvictor)]

Updated BIOS, and also updated firmware on the dock. Problem persists (in fact, may now be slightly worse, but not quite certain)

[vik (askvictor)]

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
GQET49WW (1.29 )
04/29/2016

[vik (askvictor)]

Attached another syslog of errors when connecting dock

[vik (askvictor)]

Hmm; under certain conditions, is now crashing the computer entirely when I connect the dock.

[penalvch (penalvch)]

vik, to clarify your comment:
>"The issue disappeared for a while, but has returned in the past month or so; I'm guess a kernel driver update fixed it, then regressed."

Could you please advise after which update specifically did this issue start happening with?

[vik (askvictor)]

I don't know; I don't typically pay too much attention to updates.

[red_hood (chris-red-hood)]

According to the error messages, might this be a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568573 ? Do you need any further information to hunt down this bug?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[red_hood (chris-red-hood)]

A short update on that: I am running 4.4.0-31-generic now, and although i can not see from the changelog what would have changed in that regard, recognizing an external display connected to a docking station is no problem anymore. But after asuspend/resume-Cycle, the internal monitor will not switch on again anymore, and kernel seems non-responding to requests via sysrq. As such, I currently can not help with any kernel output in that case. If you could give me any advice in how to collect kernel output in that case, I'd be happy to deliver it.
Attached is a kernel warning, which happens after unplugging from the docking station:

Jul 24 21:06:03 synlap01 kernel: [84597.934350] ------------[ cut here ]------------
Jul 24 21:06:03 synlap01 kernel: [84597.934388] WARNING: CPU: 2 PID: 21878 at /build/linux-dcxD3m/linux-4.4.0/ubuntu/i915/intel_dp_mst.c:522 intel_dp_destroy_mst_connector+0xec/0x100 [i915_
bpo]()
Jul 24 21:06:03 synlap01 kernel: [84597.934390] Disabling mst crtc failed with -22
Jul 24 21:06:03 synlap01 kernel: [84597.934392] Modules linked in: hid_logitech_hidpp hid_logitech_dj hid_generic usbhid snd_usb_audio hid snd_usbmidi_lib ctr ccm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ip6t_REJECT nf_reject_ipv6 xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_addrtype br_netfilter bridge stp llc aufs iptable_nat nf_nat_ipv4 nf_nat xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter iptable_mangle ip_tables x_tables rfcomm bnep binfmt_misc zfs(PO) zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zavl(PO) arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_hda_codec_realtek snd_hda_codec_generic snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine dw_dmac_core joydev input_leds snd_hda_intel cdc_mbim serio_raw iwlmvm cdc_wdm snd_hda_codec cdc_ncm snd_hda_core usbnet snd_hwdep mii mac80211 btusb btrtl btbcm btintel qcserial usb_wwan bluetooth usbserial snd_pcm iwlwifi rtsx_pci_ms memstick cfg80211 thinkpad_acpi nvram snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore mac_hid shpchp mei_me mei kvm_intel kvm irqbypass parport_pc ppdev lp parport autofs4 xfs btrfs drbg ansi_cprng algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i915_bpo intel_ips rtsx_pci i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea libahci sysfillrect sysimgblt e1000e fb_sys_fops drm ptp pps_core wmi video fjes
Jul 24 21:06:03 synlap01 kernel: [84597.934597] CPU: 2 PID: 21878 Comm: kworker/2:3 Tainted: P OE 4.4.0-31-generic #50-Ubuntu
Jul 24 21:06:03 synlap01 kernel: [84597.934599] Hardware name: LENOVO 20FAS05Q00/20FAS05Q00, BIOS N1CET37W (1.05 ) 01/15/2016
Jul 24 21:06:03 synlap01 kernel: [84597.934610] Workqueue: events drm_dp_destroy_connector_work [drm_kms_hel...

[red_hood (chris-red-hood)]

It seems also just switching displays makes the kernel upset, please see attached dmesg output. Also, please consider making https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568573 a duplicate, as it seems to involve the same cases and error messages.

[penalvch (penalvch)]

vik:

1) As per the sticker of the monitor itself (not from the Bug Description, or the result of a terminal command), could you please provide the full monitor manufacturer and model?

2) Regarding how you have the monitor connected, is it plugged into the dock's DVI-I, or DisplayPort port? If you switch the port is this still reproducible?

3) Regarding the connection of the monitor to the dock, is this via straight DVI-I cord, using dongle/adapter, etc.?

4) If you instead undock the computer, and plug the monitor directly into the computer, is this still reproducible?

5) Regarding the Lenovo ThinkPad OneLink Pro Dock, have you applied the latest firmware to it?

[Launchpad Janitor (janitor)]

[Expired for xorg (Ubuntu) because there has been no activity for 60 days.]