[Lenovo Thinkpad T460] Ultra Dock external displays not detected after suspend/resume cycle

[Ryan]

Hello,
System is Thinkpad T460, Skylake graphics, Thinkpad Ultra dock. DVI and HDMI displays connected via dock. 4.4.0-18.

After a suspend-resume cycle, when the laptop is docked the dock connected external displays are not initialized/connected. If I disconnect the displays from the dock and connect them directly to the laptop, they are initialized successfully and can be configured via xrandr etc.

If the laptop is power cycled, the displays can be used normally until the next suspend-resume cycle.

Example from relevant dmesg:
[drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up
[drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up
[drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up
[drm:intel_dp_start_link_train [i915_bpo]] *ERROR* failed to train DP, aborting
[drm:intel_dp_set_idle_link_train [i915_bpo]] *ERROR* Timed out waiting for DP idle patterns
[drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up
[drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up
[drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many voltage retries, give up

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-18-generic 4.4.0-18.34
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ryan 1838 F.... pulseaudio
Date: Sun Apr 10 09:39:32 2016
HibernationDevice: RESUME=UUID=04e04e17-3976-4daa-a1dd-2dd369aee83d
InstallationDate: Installed on 2015-09-21 (201 days ago)
InstallationMedia: It
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20FNCTO1WW
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-18-generic root=/dev/mapper/it--vg-root ro quiet
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-18-generic N/A
 linux-backports-modules-4.4.0-18-generic N/A
 linux-firmware 1.157
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-02-24 (45 days ago)
dmi.bios.date: 03/09/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: R06ET35W (1.09 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FNCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FNCTO1WW:pvrThinkPadT460:rvnLENOVO:rn20FNCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20FNCTO1WW
dmi.product.version: ThinkPad T460
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.6 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc4-wily/

[Pontus Pihlgren (pontus-pihlgren)]

I see the same error message when either docking my laptop or attaching a monitor to a displayport on the dock. There are some differences. I use a Dell Latitude E7470 and a Dell dock (will have to look up the model). After the messaged shown in this bug my kernel freezes. If you think these differences warrants a separate bug, please let me know.

Here is someone else that is affected: https://ulikoenig.de/skylake-unter-linux-zum-laufen-kriegen-am-beispiel-eines-dell-latitude-e7270/

Here is my complete error message, I hade to transcribe it from a photo, the kernel freezes completely and doesn't reboot:

[drm:intel_dp_start_link_train [i915]] *ERROR* too many voltage retries, give up
[drm:indel_dp_complete_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns
Kernel panic - not syncing: Timeout: Not all CPUs entered broadcast exception handler
Shutting down cpus with NMI
Kernel Offset: disabled
drm_kms_helper: panic_occurred, switching back to text console
Rebooting in 30 seconds.._

[Pontus Pihlgren (pontus-pihlgren)]

My problems partially went away with the Dave Arlie's "drm-next" kernel. I've had one crash when I attached the second monitor to the dock. I was unable to record any output from the kernel. I rebooted and everything works fine. So far so good.

output from uname -r: 4.6.0-996-generic

downloaded from: http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-next/2016-04-15-wily/

Mainline does not work. I get a "soft lockup" warning from the NMI Watchdog and the boot goes nowhere.

[Pontus Pihlgren (pontus-pihlgren)]

Oh, I had to get new i915 firmware from here:

https://01.org/linuxgraphics/downloads

[Ryan (carbonfreeze)]

I attempted to test both 4.6-rc4 and 4.6.0.996 from drm-next. 4.6-rc4 was un-bootable, and 4.6 from drm-next also had issues with freezing when enabling dock connected displays.

[Jay Banyer (jbanyer)]

This problem also occurs reliably for me.

Laptop: Lenovo T450s
CPU: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz
Dock: ThinkPad Ultra Dock

To reproduce:

- laptop is not in the dock
- suspend the laptop
- put the laptop in the dock
- resume by pressing the power button on the dock

The external screens do not activate. The only way to get them working is to power-cycle the laptop.

Kernel log:

[10243.844260] thinkpad_acpi: docked into hotplug port replicator
[10244.652647] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
[10244.858757] usb 3-3: new SuperSpeed USB device number 4 using xhci_hcd
[10244.990316] usb 2-3: new high-speed USB device number 17 using xhci_hcd
[10245.113824] usb 3-3: New USB device found, idVendor=17ef, idProduct=1010
[10245.113827] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[10245.113829] usb 3-3: Product: Lenovo ThinkPad Dock
[10245.113831] usb 3-3: Manufacturer: LENOVO
[10245.116346] hub 3-3:1.0: USB hub found
[10245.116497] hub 3-3:1.0: 4 ports detected
[10245.173393] usb 2-3: New USB device found, idVendor=17ef, idProduct=1010
[10245.173396] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[10245.173398] usb 2-3: Product: Lenovo ThinkPad Dock
[10245.173399] usb 2-3: Manufacturer: LENOVO
[10245.173884] hub 2-3:1.0: USB hub found
[10245.174200] hub 2-3:1.0: 4 ports detected
[10245.350388] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
[10245.352442] thinkpad_acpi: EC reports that Thermal Table has changed
[10245.463919] usb 2-3.4: new high-speed USB device number 18 using xhci_hcd
[10245.564215] usb 2-3.4: New USB device found, idVendor=17ef, idProduct=100f
[10245.564219] usb 2-3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[10245.564221] usb 2-3.4: Product: Lenovo ThinkPad Dock
[10245.564223] usb 2-3.4: Manufacturer: Lenovo
[10245.564225] usb 2-3.4: SerialNumber: Rev1.2
[10245.564633] hub 2-3.4:1.0: USB hub found
[10245.564693] hub 2-3.4:1.0: 3 ports detected
[10245.835891] usb 2-3.4.1: new low-speed USB device number 19 using xhci_hcd
[10245.927700] usb 2-3.4.1: New USB device found, idVendor=046d, idProduct=c077
[10245.927703] usb 2-3.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[10245.927705] usb 2-3.4.1: Product: USB Optical Mouse
[10245.927707] usb 2-3.4.1: Manufacturer: Logitech
[10245.927869] usb 2-3.4.1: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
[10245.930157] input: Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.4/2-3.4.1/2-3.4.1:1.0/0003:046D:C077.0005/input/input21
[10245.930290] hid-generic 0003:046D:C077.0005: input,hidraw0: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-0000:00:14.0-3.4.1/input0
[10245.968042] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
[10246.131855] usb 2-3.4.2: new low-speed USB device number 20 using xhci_hcd
[10246.250840] usb 2-3.4.2: New USB device found, idVendor=03f0, idProduct=0024
[10246.250844] usb 2-3.4.2: New USB device strings: Mfr=1, Product=2, SerialNum...

[Pontus Pihlgren (pontus-pihlgren)]

 For what it's worth. I've tried drm-next 4.6.0.996 from the April 22:nd and 27:th. Both kernel boots and seemingly works well but does not detect my monitors. The kernel from April 15:th gives me output on all monitors but has kernel Oops:es and Panics simply from opening the display settings in gnome as well as docking and undocking.

[Adam Chasen (achasen)]

I am seeing similar behavior with other versions of linux as well (fedora 23 4.4.7-300.fc23.x86_64). I also have upgraded the DisplayPort Hub firmware in the ultra dock per http://www.thinkwiki.org/wiki/ThinkPad_Ultra_Dock

[Daniel (daniel-uhl-n)]

I have the same problem with an intel i7-6500U on the 4.4.0 from Apr 18th. The Kernel does not freeze when i plug the external display in before booting.

[Pontus Pihlgren (pontus-pihlgren)]

The drm-next kernel from today is working slightly better. It detects my display at boot but not after undocking/docking. And occational freezes when working with "display settings" under gnome.

[Ryan (carbonfreeze)]

I have been running the BIOS 1.10 since the day it was released. Behavior between 1.09 and 1.10 related to this bug did not change.

R06ET36W (1.10 )
03/23/2016

[Ryan (carbonfreeze)]

I have noticed fewer freezing issues on docking, and a complete resolve of this bug after installing the Intel SKL GuC firmware blob; along with running a drm-next or drm-next-intel kernel. The GuC blob seems to be missing from linux-firmware, I no longer receive error messages about missing i915 firmware when doing kernel upgrades or generating initrd. I managed to keep an uptime of almost 2 weeks without graphics crashes with a drm-next kernel, docking the laptop ~30 times over that period.

[penalvch (penalvch)]

Ryan, to help narrow this down, could you please test the latest mainline kernel (4.7-rc1) and advise to the results?

[Ryan (carbonfreeze)]

The 4.7-rc1 kernel was not bootable on my system. However, I have been testing with 4.6.0-996-generic #201605082201 from drm-next and the behavior is better. With the drm-next kernel, I am able to dock/undock the laptop multiple times without a freeze and the displays are recognized and can be setup. The configured display layout is applied successfully on docking, unlike with the 4.4.0-22 kernel. I do have one persistent issue with the drm-next kernel, I have to change to a VT and back to get display output after docking - but I don't think its related to this issue. This intel stuff sure seems like a mess.

[penalvch (penalvch)]

Ryan, to see if the improvements have already made it to mainline, could you please test the next most latest mainline kernel (4.6.1) and advise to the results?

[Ryan (carbonfreeze)]

I wasn't able to boot 4.6.1, but I was able to boot 4.6.0-040600-generic #201606030904. It does not seem to have the screen detection or freezing issues experienced in 4.4.0 when docking/un-docking (yet).

[penalvch (penalvch)]

Ryan, to follow up, did the 4.6.0 kernel show the issue?

Also, to keep this relevant to upstream, could you please test the latest mainline kernel (4.7-rc6) and advise to the results?

[Ryan (carbonfreeze)]

As per my previous comment, 4.6.0-040600-generic #201606030904 is not effected by this bug. I've been using it for a month without issue.

[Marcin Dylewski (marcin-dylewski-m)]

Exactly the same (and some more) problems are on my Lenovo X250 Broadwell machine with 4.4 kernel. I have tested 4.6.0, 4.6.3 and just now 4.7-rc6. All issues disapeared.

[red_hood (chris-red-hood)]

I am using a T460s with an external DVI monitor connected via a docking station, and experience the same issue. People here https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1522922 report it is fixed in mainline kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.9-xenial/. I will give it a try, and report back. I also propose to mark the other bug as duplicate.

[red_hood (chris-red-hood)]

I tried http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.14-xenial/ and just docking the notebook leads to kernel panic, after the same error message (Too many voltage retries...) appears. So, no luck with mainline kernel. Ill try vanilla and give feedback.

[red_hood (chris-red-hood)]

So, I tried http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6.4/ and switching to external display and back multiple times, including suspend/resume cycle works flawlessly. Unfortunatly, I am unable to remount my XFS root writable (had to change initrd option) and compile the ZFS DKMS files. So, for now this is also not a real solution...

[Simon Marlow (simonmar)]

I have the same problem with an Lenovo X1 Carbon 3 and Ultradock. Upgrading the kernel to 4.6.5 mainline fixed it, although the laptop refuses to suspend while attached to the dock.

[Arne (arne-quitschau)]

This issues seems to have the same source as bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376581

[Launchpad Janitor (janitor)]

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

[Eric Floehr (eric-intellovations)]

I have this problem as well on a new Thinkpad T460 with fresh 16.04.1 install with all update, dock, and a Dell displayport monitor.

[penalvch (penalvch)]

Eric Floehr (eric-intellovations), to track hardware, etc. it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

[Donjan Rodic (bryonak)]

Same problem here, made a new report:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651454