dunk, 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. -- 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/1654214 Title: Belkin Thunderbolt 2 Express Dock HD display port hot plug not supported. Status in linux package in Ubuntu: Incomplete Bug description: MachineType: Apple Inc. MacBookPro12,5 Peripheral: Belkin Thunderbolt 2 Express Dock HD. Model: F4U085 [Text copied from bug/1551712] 1. When booted without the dock connected, connecting the dock only allows USB and Ethernet to work, it does not support HDMI or DisplayPort monitors. Re-seating the dock from here does not stop USB and Ethernet from working. 2. When booted with the device connected, while the device works fine, reseating the dock causes no adapters to work (No USB, Ethernet, HDMI and DisplayPort) This bug was generated with the Thunderbolt IO expander connected at boot time and therefore all IO is working as intended. Also (manually) attached is a copy of syslog, lsmod and lspci where the dock is removed then re-attached. (search for the annotation "Removing Thunderbolt" and "Inserting Thunderbolt".) The 3rd state where the system is booted without the doc is not accounted for in the attached logs. Please let me know if you want any more information. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-32-generic 4.8.0-32.34 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC3: duncan 2524 F.... pulseaudio /dev/snd/controlC2: duncan 2524 F.... pulseaudio /dev/snd/controlC0: duncan 2524 F.... pulseaudio /dev/snd/controlC1: duncan 2524 F.... pulseaudio CurrentDesktop: Unity Date: Thu Jan 5 10:18:15 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=33476504-147f-4970-8a3b-969e4dac63c9 InstallationDate: Installed on 2016-12-30 (5 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Apple Inc. MacBookPro11,5 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic.efi.signed root=UUID=ae7e8674-a8e6-4de5-a469-a0ae717af319 ro libata.force=noncq quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-32-generic N/A linux-backports-modules-4.8.0-32-generic N/A linux-firmware 1.161.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B09.1602151732 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B09.1602151732:bd02/15/2016:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5: dmi.product.name: MacBookPro11,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1654214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
