external displays thinkpad pro dock 90w stay switched after resume

Bug #1555078 reported by Robert Schetterer
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

external-displays-thinkpad-pro-dock-90w-stay-switched-after-resume

from bug

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530171

I tested wily ,xenial, kubuntu, kernels 4.2 , 4.4 on brand new thinkpad t450s with thinkpad pro dock 90w.
The laptop and the dock has latest fimware !
Intel graphics driver is at latest state too.
Also tested latest 4.5 drm intel nightly. All external displays work always when directly attached to the laptop.
But with laptop docked, external displays are only running after boot, but fail when wake up from sleep mode configured in kde
closing lid. This is a very common user powersetting an is awaited to work. Most of the times external displays could reconfigured i.e by script produced from arandr ( gtk gui wrapper for xrandr ). But a universal script workaround seems complicated with acpi, systemd in userland for all thinkable combinations of possible displays ( up to three include lcd on laptop are possible).

It should simply work out of the box.

Additional info i invested a lot of time in kernel logs and trying grub start parameter, cause there were other ugly bug with intel 915 driver ( pci lied SDE etc fixed in 4.5 ) , there is also a point in the bios configure 10s to wait for notice external displays. Also 2014 the dock had a bug ( also on windows with external displays which was fixed by new firmware ).
It seems simply the dock does not pass external displays connected after laptop and external displays got sleep mode after wake up, prove is made by plug/unplugging external display and reenable it in kde. Also open windows were only reconstructed
after awake with kernel 4.4 /4.5 after manual reenable, with kernel 4.2 most of the time also plasma crashes and simply undock
crash x-server too.

I vote this as a bug from the lenovo dock, contact their developers may help
My Woraround solution find here

https://sys4.de/de/blog/2016/03/09/external-displays-thinkpad-pro-dock-90w-stay-switched-after-resume/
---
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: rschetterer 1395 F.... pulseaudio
 /dev/snd/controlC0: rschetterer 1395 F.... pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=98d32426-2e0d-4b74-8a22-37ba6ebb8cbb
MachineType: LENOVO 20BX0049GE
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-11-generic root=UUID=91b76f4b-d581-4589-bbfd-3057220745e3 ro splash quiet vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
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-11-generic N/A
 linux-backports-modules-4.4.0-11-generic N/A
 linux-firmware 1.156
Tags: xenial
Uname: Linux 4.4.0-11-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 12/23/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: JBET55WW (1.20 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BX0049GE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40705 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrJBET55WW(1.20):bd12/23/2015:svnLENOVO:pn20BX0049GE:pvrThinkPadT450s:rvnLENOVO:rn20BX0049GE:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20BX0049GE
dmi.product.version: ThinkPad T450s
dmi.sys.vendor: LENOVO

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1555078

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Robert Schetterer (rschetterer) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected xenial
description: updated
Revision history for this message
Robert Schetterer (rschetterer) wrote : CRDA.txt

apport information

Revision history for this message
Robert Schetterer (rschetterer) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Robert Schetterer (rschetterer) wrote : IwConfig.txt

apport information

Revision history for this message
Robert Schetterer (rschetterer) wrote : JournalErrors.txt

apport information

Revision history for this message
Robert Schetterer (rschetterer) wrote : Lspci.txt

apport information

Revision history for this message
Robert Schetterer (rschetterer) wrote : Lsusb.txt

apport information

Revision history for this message
Robert Schetterer (rschetterer) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Robert Schetterer (rschetterer) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Robert Schetterer (rschetterer) wrote : ProcModules.txt

apport information

Revision history for this message
Robert Schetterer (rschetterer) wrote : RfKill.txt

apport information

Revision history for this message
Robert Schetterer (rschetterer) wrote : UdevDb.txt

apport information

Revision history for this message
Robert Schetterer (rschetterer) wrote : WifiSyslog.txt

apport information

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.5 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.5-rc7-wily/

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Robert Schetterer (rschetterer) wrote :

i allready tested

linux-image-4.5.0-994-generic_4.5.0-994. ... amd64.deb , two days ago
from
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/current/

until there is no diff patch which really relates to the problem a recent new test makes no sense at all.

Revision history for this message
Robert Schetterer (rschetterer) wrote :

tested latest from

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-rc7-wily/

on xenial dev 16.04

Problem is not solved as awaited

Revision history for this message
Robert Schetterer (rschetterer) wrote :

looks like there should be a better workaround is possible with kde powerdevil
described here

https://bugs.kde.org/show_bug.cgi?id=360766

Revision history for this message
Robert Schetterer (rschetterer) wrote :

Update: Due a lot of testing, my best speculate is, that the Thinkpad pro dock 90 w acts as MST-DP Hub ( Display Port 1.2 Hub )
After Docking the Kernel renames DP Ports, this is needed in use with real DP 1.2 Displays. But from then ( docked in ) the resume code in DRM is not longer working ( it works if the displays are attached directly to the laptop ).
So the resume bug should be somewhere in the Intel DRM / MST-DP code.

After all i found some easy workaround ( not with xrandr, cause it dont works with more the one external display )
and updated
https://sys4.de/de/blog/2016/03/09/external-displays-thinkpad-pro-dock-90w-stay-switched-after-resume/

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.