[Regression] Thinkpad dock: External monitors not recognized after 15.04 upgrade

Bug #1530171 reported by aexl
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

External monitors are not recognized in display settings when plugged into any dock port.

They *are* recognized after a reboot (not after logout).
After plugging out and the in again they are not recognized.

A monitor plugged in and out of the non-dock VGA is recognized instantly.
After plugging in or out of the non-dock VGA, monitors plugged to dock ports are recognized (which serves as a crazy workaround for me now)
(update: this works sometimes, sometimes not).

Everything used to work with 14.10, but stopped with 15.04.

A recent test with 1510 live CD did not fix this.
---
.tmp.unity.support.test.0:

ApportVersion: 2.17.2-0ubuntu1.8
Architecture: amd64
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
DistUpgraded: 2016-01-04 01:09:49,649 DEBUG enabling apt cron job
DistroCodename: vivid
DistroRelease: Ubuntu 15.04
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:501e]
InstallationDate: Installed on 2015-03-05 (311 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: LENOVO 20AUS00N00
Package: xorg 1:7.7+7ubuntu4
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-43-generic root=UUID=82cd15d9-7510-4d2f-a698-28fa51216e13 ro rootflags=subvol=@ quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.19.0-43.49-generic 3.19.8-ckt10
Tags: vivid ubuntu compiz-0.9
Uname: Linux 3.19.0-43-generic x86_64
UpgradeStatus: Upgraded to vivid on 2016-01-04 (6 days ago)
UserGroups: adm cdrom dip lp lpadmin plugdev sambashare saned sudo
_MarkForUpload: True
dmi.bios.date: 08/13/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: J4ET67WW(1.67)
dmi.board.asset.tag: Not Available
dmi.board.name: 20AUS00N00
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrJ4ET67WW(1.67):bd08/13/2014:svnLENOVO:pn20AUS00N00:pvrThinkPadL540:rvnLENOVO:rn20AUS00N00:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20AUS00N00
dmi.product.version: ThinkPad L540
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.1+15.04.20150922-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1
xserver.bootTime: Wed Jan 6 15:29:10 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 5568
 vendor CMN
xserver.version: 2:1.17.1-0ubuntu3.1

Revision history for this message
aexl (aexl) wrote :
Revision history for this message
aexl (aexl) wrote :

Updated summary with new findings.

no longer affects: nvidia-graphics-drivers-304-updates (Ubuntu)
aexl (aexl)
no longer affects: udev
affects: ubuntu → unity-control-center (Ubuntu)
aexl (aexl)
description: updated
affects: unity-control-center (Ubuntu) → xserver-xorg-video-intel (Ubuntu)
Revision history for this message
penalvch (penalvch) wrote :

aexl, thank you for reporting this and helping make Ubuntu better.

Could you please run the following command once from a terminal as it will automatically gather and attach updated debug information to this report:
apport-collect -p xorg 1530171

Please ensure you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

When reporting xorg related bugs in the future, please do so via the above method. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

affects: xserver-xorg-video-intel (Ubuntu) → xorg (Ubuntu)
Changed in xorg (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
aexl (aexl) wrote :

Thanks christopher for taking care of this! I'll do this in an instant.

tags: added: apport-collected compiz-0.9 ubuntu vivid
description: updated
Revision history for this message
aexl (aexl) wrote : BootLog.txt

apport information

Revision history for this message
aexl (aexl) wrote : CurrentDmesg.txt

apport information

Revision history for this message
aexl (aexl) wrote : Dependencies.txt

apport information

Revision history for this message
aexl (aexl) wrote : DkmsStatus.txt

apport information

Revision history for this message
aexl (aexl) wrote : DpkgLog.txt

apport information

Revision history for this message
aexl (aexl) wrote : GconfCompiz.txt

apport information

Revision history for this message
aexl (aexl) wrote : JournalErrors.txt

apport information

Revision history for this message
aexl (aexl) wrote : LightdmDisplayLog.txt

apport information

Revision history for this message
aexl (aexl) wrote : LightdmGreeterLog.txt

apport information

Revision history for this message
aexl (aexl) wrote : LightdmGreeterLogOld.txt

apport information

Revision history for this message
aexl (aexl) wrote : LightdmLog.txt

apport information

Revision history for this message
aexl (aexl) wrote : Lspci.txt

apport information

Revision history for this message
aexl (aexl) wrote : Lsusb.txt

apport information

Revision history for this message
aexl (aexl) wrote : MonitorsUser.xml.txt

apport information

Revision history for this message
aexl (aexl) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
aexl (aexl) wrote : ProcEnviron.txt

apport information

Revision history for this message
aexl (aexl) wrote : ProcInterrupts.txt

apport information

Revision history for this message
aexl (aexl) wrote : ProcModules.txt

apport information

Revision history for this message
aexl (aexl) wrote : UdevDb.txt

apport information

Revision history for this message
aexl (aexl) wrote : UdevLog.txt

apport information

Revision history for this message
aexl (aexl) wrote : UnitySupportTest.txt

apport information

Revision history for this message
aexl (aexl) wrote : XorgLog.txt

apport information

Revision history for this message
aexl (aexl) wrote : XorgLogOld.txt

apport information

Revision history for this message
aexl (aexl) wrote : Xrandr.txt

apport information

Revision history for this message
aexl (aexl) wrote : xdpyinfo.txt

apport information

Revision history for this message
aexl (aexl) wrote : xserver.devices.txt

apport information

Revision history for this message
aexl (aexl) wrote : xserver.errors.txt

apport information

description: updated
Revision history for this message
aexl (aexl) wrote : BootLog.txt

apport information

Revision history for this message
aexl (aexl) wrote : CurrentDmesg.txt

apport information

Revision history for this message
aexl (aexl) wrote : Dependencies.txt

apport information

Revision history for this message
aexl (aexl) wrote : DkmsStatus.txt

apport information

Revision history for this message
aexl (aexl) wrote : DpkgLog.txt

apport information

Revision history for this message
aexl (aexl) wrote : GconfCompiz.txt

apport information

Revision history for this message
aexl (aexl) wrote : JournalErrors.txt

apport information

Revision history for this message
aexl (aexl) wrote : LightdmDisplayLog.txt

apport information

Revision history for this message
aexl (aexl) wrote : LightdmGreeterLog.txt

apport information

Revision history for this message
aexl (aexl) wrote : LightdmGreeterLogOld.txt

apport information

Revision history for this message
aexl (aexl) wrote : LightdmLog.txt

apport information

Revision history for this message
aexl (aexl) wrote : Lspci.txt

apport information

Revision history for this message
aexl (aexl) wrote : Lsusb.txt

apport information

Revision history for this message
aexl (aexl) wrote : MonitorsUser.xml.txt

apport information

Revision history for this message
aexl (aexl) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
aexl (aexl) wrote : ProcEnviron.txt

apport information

Revision history for this message
aexl (aexl) wrote : ProcInterrupts.txt

apport information

Revision history for this message
aexl (aexl) wrote : ProcModules.txt

apport information

penalvch (penalvch)
tags: added: wily
description: updated
Revision history for this message
aexl (aexl) wrote :

Thanks christopher, i'll go on like this!

Revision history for this message
aexl (aexl) wrote :

Thank you christopher for this reminder, i did not knw that BIOS had to be updated.

Unfortunately the BIOS update did not change anything.

(Note: On the linked page the current BIOS is labeled 1.82, but the bootable ISO as well as its README (and the readme of the windows BIOS updater) announce 1.81, as does my updated BIOS. So Lenovo seems to have it got wrong. See https://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/j4uj65wd.txt )

xl@thinker:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
[sudo] password for xl:
J4ET81WW(1.81)
08/14/2015

Note to the above apport data:
I did the aport twice.
The first config was WITH 2 external monitors over the dock.
The second WITHOUT these monitors.
Guessing this might help.

(but some stuff may be broken as i had a strange 503 exception on the command line, containing:
    At least 4 queries/external actions issued in 0.06 seconds OOPS-4ade3bac7cd0be6540a006ad87bf530b
)

Changed in xorg (Ubuntu):
status: Incomplete → New
description: updated
Revision history for this message
penalvch (penalvch) wrote :

aexl, if you boot with a kernel from 14.10 (3.16.x), does the issue go away?

tags: added: latest-bios-1.81
tags: added: regression-release
Changed in xorg (Ubuntu):
importance: Low → Medium
status: New → Incomplete
Revision history for this message
aexl (aexl) wrote :

YES, booting with 3.16.44 makes this go away.
Every plugging in and out of monitors (or (un)connecting the dock) is reflected instantly by display settings.

Changed in xorg (Ubuntu):
status: Incomplete → New
Revision history for this message
penalvch (penalvch) wrote :

aexl, at your earliest convenience, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

affects: xorg (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
aexl (aexl) wrote :

Yes this is fixed upstream, Yay!

Given that vivid is end of life, i think you can close this, but leave it up to you.
In any case: Thanks for guiding me through this!

tags: added: kernel-fixed-upstream kernel-fixed-upstream-4.4
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

aexl, while Vivid is EOL as per https://wiki.ubuntu.com/Releases, the release you would be upgrading to isn't.

Hence, to see if this is already resolved in Ubuntu, could you please upgrade to either Wily or Xenial, and advise if this is still reproducible?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: needs-reverse-bisect
Revision history for this message
Robert Schetterer (rschetterer) wrote :

I am 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. Any idea what to look next ?
Regards

Revision history for this message
penalvch (penalvch) wrote :

Robert Schetterer, 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.

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

i vote this as a bug from the dock ,you may contact lenovo developers for more info to fix
i wrote a blog to workaround with systemd xrandr see
https://sys4.de/de/blog/2016/03/09/external-displays-thinkpad-pro-dock-90w-stay-switched-after-resume/
perhaps someone will find a better way with xranrdr and systemd more dynamical and no additional needs for insert username etc

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.