Try unplugging and replugging the dock after the system has booted. There is an open issue in the current kernels and how the system ACPI enumerates devices before the kernel is ready causing them to not get reset when the kernel does finally load.
Not sure about your wireless issues but for the wired you should run `ethtool -s speed 100 autoneg on duplex full` after the system has a wired connection reestablished to avoid the packer corruption issue that occurs during large transfers. It is related to the USB hub that the dock ethernet and usb ports go through not supporting scheduled interrupts and the future work is to implement floor control
Thanks for the reply. I have tried all those things, and because I'm 100% sure I haven't changed the kernel, this is not something related to kernel compatibility. Still thinking in terms of Secure Boot and permissions to peripherals over TB related to that. Unfortunately all my attempts with different configurations has been in vain :(
Did you happen to get a BIOS update that reset the Thunderbolt security to anything other than no security? There is a certain version of 4.10 that we've found tends to work more consistently than the latest.
Yes and no :) When this occurred I did not update the BIOS. A single reboot and everything on TB (except monitors) was gone. As part of the last days fiddling trying to sort this out I have updated the BIOS to latest version. Thunderbolt security has always, and is still, set to No Security.
I also never changed anything in the BIOS around the time the problem occurred. I mean, how often do you even enter the BIOS? :)
I have tried to boot the kernels I have been running the last 8 months, all show the exact same problem so it must be something with BIOS. I have also verified that I get the same problem with another TB15 dock.
To me, the only thing I did was the upgrade of say 30 deb packages where the grub-ufi asked something about secure boot.
To me it seems like TB Security is enabled but it isn't. Will try to reset BIOS to default and start over...
Note the missing "Intel Corporation Device 1575" in my listing. Why doesn't Linux detect the TB chipset? Again, somehow deeply disabled through BIOS (even though I never changed anything when it happened)?
Thanks for the heads-up on this as I was about to upgrade my ubuntu 16.04 with 4.8 kernel, but this is now on hold...
Have you tried an alternative USB-C connection eg the DA200 dongle?
I would suspect the thunderbolt firmware/driver. I wonder if it is not generating an event when you hot-plug in TB15 so the system does not know its there. Try refreshing these and check the install order as I seem to remember that that is important too.
I tried the DA200 adapter but that is USB-C, not Thunderbolt. It works fine.
The hotplug event is a clue, but I think the 1575 controller should be detected and listed even though no TB peripheral has been plugged in. I need to force my college to reboot his laptop and verify.
Does your new kernel happen to be signed? It would be part of the name. The signed kernels may cause issues because it changes how the system interacts with the hardware.
One (final?) update on the issue. I managed to get Tunderbolt and the TB15 back working in Linux. I messed around even more in the BIOS settings. Bear in mind that when the problem occurred:
1) Didn't change anything in the BIOS
2) Didn't change the kernel
After that I did a factory reset of the BIOS settings and changed settings to disable Secure Boot, enable TB and set TB Security to None. That didn't work.
What I did do to get it working again was to change TB Security to "ask permission" (or whatever that setting is called), save, reboot into Linux. Then reboot, BIOS, change TB Security back to None and boot up Linux. Everything back to normal.
Just to clearify: You said, now its working again. I don't share your opinion. The sad situation with the TB15, a Dell XPS 13 on all available kernel versions and linux for me is:
o No cold plug
o No Ethernet. (Just 100MB is a clear no)
o suspend2ram may trash the dual screen setup
o freezes after suspend2ram in rare cases
o Some USB devices are not working with USB ports on the dock
The device is a ridiculously expensive piece of paperweight.
I agree on all your items but for me the dock is good enough. There are ways around most of the problems, like know what steps work when plugging in/out, suspending etc. Not saying I never get it to hang my laptop but it gets me dual high-res monitors, audio, USB and charging through one single cable.
dragon_788
24 Posts
0
July 13th, 2017 09:00
Try unplugging and replugging the dock after the system has booted. There is an open issue in the current kernels and how the system ACPI enumerates devices before the kernel is ready causing them to not get reset when the kernel does finally load.
dragon_788
24 Posts
0
July 13th, 2017 09:00
Not sure about your wireless issues but for the wired you should run `ethtool -s speed 100 autoneg on duplex full` after the system has a wired connection reestablished to avoid the packer corruption issue that occurs during large transfers. It is related to the USB hub that the dock ethernet and usb ports go through not supporting scheduled interrupts and the future work is to implement floor control
vajper
12 Posts
0
July 13th, 2017 14:00
Thanks for the reply. I have tried all those things, and because I'm 100% sure I haven't changed the kernel, this is not something related to kernel compatibility. Still thinking in terms of Secure Boot and permissions to peripherals over TB related to that. Unfortunately all my attempts with different configurations has been in vain :(
dragon_788
24 Posts
0
July 13th, 2017 21:00
Did you happen to get a BIOS update that reset the Thunderbolt security to anything other than no security? There is a certain version of 4.10 that we've found tends to work more consistently than the latest.
vajper
12 Posts
0
July 14th, 2017 01:00
Well, full reset to BIOS factory defaults didn't help either. (Yes, I changed back Thunderbolt Security to No Security).
vajper
12 Posts
0
July 14th, 2017 01:00
Yes and no :) When this occurred I did not update the BIOS. A single reboot and everything on TB (except monitors) was gone. As part of the last days fiddling trying to sort this out I have updated the BIOS to latest version. Thunderbolt security has always, and is still, set to No Security.
I also never changed anything in the BIOS around the time the problem occurred. I mean, how often do you even enter the BIOS? :)
I have tried to boot the kernels I have been running the last 8 months, all show the exact same problem so it must be something with BIOS. I have also verified that I get the same problem with another TB15 dock.
To me, the only thing I did was the upgrade of say 30 deb packages where the grub-ufi asked something about secure boot.
To me it seems like TB Security is enabled but it isn't. Will try to reset BIOS to default and start over...
vajper
12 Posts
0
July 14th, 2017 03:00
More intriguing... Compared lspci -vt between my laptop and a college's (running slightly different kernel). TB on that laptop works fine:
-[0000:00]-+-00.0 Intel Corporation Sky Lake Host Bridge/DRAM Registers
+-02.0 Intel Corporation Sky Lake Integrated Graphics
+-04.0 Intel Corporation Skylake Processor Thermal Subsystem
+-14.0 Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller
+-14.2 Intel Corporation Sunrise Point-LP Thermal subsystem
+-15.0 Intel Corporation Sunrise Point-LP Serial IO I2C Controller
+-15.1 Intel Corporation Sunrise Point-LP Serial IO I2C Controller
+-16.0 Intel Corporation Sunrise Point-LP CSME HECI
+-17.0 Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode]
+-1c.0-[01-39]----00.0-[02-0b]--+-00.0-[03]----00.0 Intel Corporation Device 1575
| +-01.0-[04-0a]----00.0-[05-0a]--+-01.0-[06]--
| | \-04.0-[07-0a]----00.0-[08-0a]--+-01.0-[09]----00.0 ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller
| | \-04.0-[0a]--
| \-02.0-[0b]--
+-1c.4-[3a]----00.0 Broadcom Corporation BCM4350 802.11ac Wireless Network Adapter
+-1c.5-[3b]----00.0 Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader
+-1d.0-[3c]----00.0 Toshiba America Info Systems Device 010f
+-1f.0 Intel Corporation Sunrise Point-LP LPC Controller
+-1f.2 Intel Corporation Sunrise Point-LP PMC
+-1f.3 Intel Corporation Sunrise Point-LP HD Audio
\-1f.4 Intel Corporation Sunrise Point-LP SMBus
Mine:
-[0000:00]-+-00.0 Intel Corporation Sky Lake Host Bridge/DRAM Registers
+-02.0 Intel Corporation Sky Lake Integrated Graphics
+-04.0 Intel Corporation Skylake Processor Thermal Subsystem
+-14.0 Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller
+-14.2 Intel Corporation Sunrise Point-LP Thermal subsystem
+-15.0 Intel Corporation Sunrise Point-LP Serial IO I2C Controller
+-15.1 Intel Corporation Sunrise Point-LP Serial IO I2C Controller
+-16.0 Intel Corporation Sunrise Point-LP CSME HECI
+-17.0 Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode]
+-1c.0-[01-39]--
+-1c.4-[3a]----00.0 Intel Corporation Wireless 8260
+-1c.5-[3b]----00.0 Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader
+-1d.0-[3c]----00.0 Toshiba America Info Systems Device 010f
+-1f.0 Intel Corporation Sunrise Point-LP LPC Controller
+-1f.2 Intel Corporation Sunrise Point-LP PMC
+-1f.3 Intel Corporation Sunrise Point-LP HD Audio
\-1f.4 Intel Corporation Sunrise Point-LP SMBus
Note the missing "Intel Corporation Device 1575" in my listing. Why doesn't Linux detect the TB chipset? Again, somehow deeply disabled through BIOS (even though I never changed anything when it happened)?
RWHobbs
5 Posts
0
July 14th, 2017 04:00
Hi
Thanks for the heads-up on this as I was about to upgrade my ubuntu 16.04 with 4.8 kernel, but this is now on hold...
Have you tried an alternative USB-C connection eg the DA200 dongle?
I would suspect the thunderbolt firmware/driver. I wonder if it is not generating an event when you hot-plug in TB15 so the system does not know its there. Try refreshing these and check the install order as I seem to remember that that is important too.
vajper
12 Posts
0
July 14th, 2017 04:00
I tried the DA200 adapter but that is USB-C, not Thunderbolt. It works fine.
The hotplug event is a clue, but I think the 1575 controller should be detected and listed even though no TB peripheral has been plugged in. I need to force my college to reboot his laptop and verify.
dragon_788
24 Posts
0
July 15th, 2017 20:00
Does your new kernel happen to be signed? It would be part of the name. The signed kernels may cause issues because it changes how the system interacts with the hardware.
vajper
12 Posts
0
July 16th, 2017 13:00
Nope, it is not signed. I also didn't change it during the reboots when the problem occurred.
vajper
12 Posts
0
July 19th, 2017 23:00
One (final?) update on the issue. I managed to get Tunderbolt and the TB15 back working in Linux. I messed around even more in the BIOS settings. Bear in mind that when the problem occurred:
1) Didn't change anything in the BIOS
2) Didn't change the kernel
After that I did a factory reset of the BIOS settings and changed settings to disable Secure Boot, enable TB and set TB Security to None. That didn't work.
What I did do to get it working again was to change TB Security to "ask permission" (or whatever that setting is called), save, reboot into Linux. Then reboot, BIOS, change TB Security back to None and boot up Linux. Everything back to normal.
Verdellt
23 Posts
0
July 20th, 2017 00:00
Just to clearify: You said, now its working again. I don't share your opinion. The sad situation with the TB15, a Dell XPS 13 on all available kernel versions and linux for me is:
o No cold plug
o No Ethernet. (Just 100MB is a clear no)
o suspend2ram may trash the dual screen setup
o freezes after suspend2ram in rare cases
o Some USB devices are not working with USB ports on the dock
The device is a ridiculously expensive piece of paperweight.
Verdellt
23 Posts
0
July 20th, 2017 00:00
Do you know a workaround for the dual screen bug after suspend2ram? I think it would help a lot if the dual screen setup was stable after suspending.
In my case, after suspending a few times, only the internal screen of the notebook is working after waking up from suspend2ram and a reboot is needed.
vajper
12 Posts
0
July 20th, 2017 00:00
I agree on all your items but for me the dock is good enough. There are ways around most of the problems, like know what steps work when plugging in/out, suspending etc. Not saying I never get it to hang my laptop but it gets me dual high-res monitors, audio, USB and charging through one single cable.