Thunderbolt hotplug causes system hang

Bug #1599476 reported by IbeeX
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Description: Ubuntu 16.04 LTS
Release: 16.04

Hot-plugging Dell's WD15 Thunderbolt cause a system panic with regular kernel 4.4.0-28. Using http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6.3-yakkety/ kernel. WD15 works if it is connected to laptop during boot time. Hot-plugg causes system hang

What you expected to happen:
Hot-plugg WD15 thunderbolt (http://www.dell.com/support/article/us/en/04/SLN301105) all features should work (USB, sound-card, port replication...)
What happened instead:
Display port on WD15 works, USB replication don't work sound-card don't work and eventually system hangs.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
DistroRelease: Ubuntu 16.04
InstallationDate: Installed on 2016-05-04 (63 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
Package: linux (not installed)
Tags: xenial
Uname: Linux 4.6.3-040603-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True

Revision history for this message
IbeeX (ibrkanac) wrote :
Revision history for this message
IbeeX (ibrkanac) wrote :
Revision history for this message
IbeeX (ibrkanac) wrote :
IbeeX (ibrkanac)
description: updated
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 1599476

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
IbeeX (ibrkanac) wrote : JournalErrors.txt

apport information

tags: added: apport-collected xenial
description: updated
Revision history for this message
IbeeX (ibrkanac) wrote : ProcEnviron.txt

apport information

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

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

1) Could you please provide the full computer model as noted on the sticker of the computer itself (not from the Bug Description)?

2) Please provide the output of the following terminal command (not perform an apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

3) 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.

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

Thank you for your help.

Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
IbeeX (ibrkanac) wrote :

Dell xps 15 9550 laptop,

sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
01.02.00
04/07/2016

I already tried http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc6-yakkety/
and it is worse then current kernel I am using http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6.3-yakkety/

4.6.3 WD15 works if it is plugged while boot, and it can be unplugged but not replugged
4.7.3 WD15 worked if it is plugged while boot, but when unplugged extended monitor was reported still connected

tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.6.3 kernel-bug-exists-upstream-4.7-rc6
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

IbeeX, as per http://www.dell.com/support/home/us/en/19/product-support/product/xps-15-9550-laptop/drivers?os=biosa an update to your computer's buggy, insecure, and outdated BIOS is available (01.02.10). When you update to this following https://help.ubuntu.com/community/BIOSUpdate how does this improve the situation?

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

Also, you don't have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible:
1) Please provide the output of the following terminal command (not perform an apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2) Please make a comment specifically advising on if there was an improvement or not.
3) Please mark this report Status Confirmed.

If it's not reproducible, please mark this as Invalid.

Thank you for your help.

tags: added: bios-outdated-01.02.10
removed: kernel-bug-exists-upstream-4.6.3
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
IbeeX (ibrkanac) wrote :

I installed new BIOS but I also noticed on WD15 page that there is firmawer update for dock also
http://www.dell.com/support/article/us/en/19/SLN301970 as stated there point 3 "Download and Install the Intel(R) Thunderbolt(TM) 3 Firmware Update."

sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
01.02.10
06/30/2016

For now preliminary testing is great hotplug works as expected, only I would test it for few more days.

Thx!

Revision history for this message
penalvch (penalvch) wrote :

IbeeX, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1599476/comments/10 regarding this being fixed with a BIOS update and dock firmware update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
importance: Low → Undecided
status: Incomplete → Invalid
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.