Donjan Rodic, thank you for reporting this and helping make Ubuntu
better.
In order to allow additional upstream developers to examine the issue, at your
earliest convenience, could you please test the latest upstream kernel
available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please
keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the
daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was
released upstream.
4) Install instructions are available at
https://wiki.ubuntu.com/Kernel/MainlineBuilds .
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.
Also, you don't need to apport-collect further unless specifically
requested to do so.
It is most helpful that after testing of the latest upstream kernel is
complete, you mark this report Status Confirmed.
Lastly, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.
Thank you for your help.
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1651454
Title:
[Lenovo Thinkpad T460p] Ultra Dock external displays not detected
after suspend/resume cycle
Status in linux package in Ubuntu:
Incomplete
Bug description:
The bug is identical to the expired
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568573 where a
new report was requested.
This time around with a fresh install of 16.10 amd64 on a Thinkpad
T460p and a Lenovo Ultra Dock with two external monitors.
The setup does work when freshly booting with the laptop on the dock.
Suspending undocked, docking, resuming doesn't light up the external monitors.
Neither does just docking awake.
The relevant error messages seem to be these:
Dec 20 13:21:50 talas kernel: [265391.482117]
[drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage
retries, give up
Dec 20 13:21:50 talas kernel: [265391.498583] [drm:intel_wait_ddi_buf_idle
[i915]] *ERROR* Timeout waiting for DDI BUF D idle bit
Other relevant bug reports might be:
https://bugzilla.redhat.com/show_bug.cgi?id=1316877
https://bbs.archlinux.org/viewtopic.php?id=209791
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-30-generic 4.8.0-30.32
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: donjan 2341 F.... pulseaudio
/dev/snd/pcmC1D0p: donjan 2341 F...m pulseaudio
/dev/snd/controlC1: donjan 2341 F.... pulseaudio
CurrentDesktop: GNOME-Flashback:Unity
Date: Tue Dec 20 15:36:08 2016
InstallationDate: Installed on 2016-10-25 (56 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: LENOVO 20FXS0Y200
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic
root=UUID=104820cc-7d87-46d1-a1aa-e650ff221603 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.8.0-30-generic N/A
linux-backports-modules-4.8.0-30-generic N/A
linux-firmware 1.161
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/26/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: R07ET71W (2.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FXS0Y200
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR07ET71W(2.11):bd09/26/2016:svnLENOVO:pn20FXS0Y200:pvrThinkPadT460p:rvnLENOVO:rn20FXS0Y200:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20FXS0Y200
dmi.product.version: ThinkPad T460p
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651454/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
