*** This bug is a duplicate of bug 1717431 ***
https://bugs.launchpad.net/bugs/1717431
** Tags removed: kernel-da-key
--
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/1697395
Title:
*** This bug is a duplicate of bug 1717431 ***
https://bugs.launchpad.net/bugs/1717431
Looks like those made it to artful too:
https://bugs.launchpad.net/intel/+bug/1717431
** This bug has been marked a duplicate of bug 1717431
[Bug] Thunderbolt-patches: Fixes the issue regarding the
Those 3 patches were backported to 4.13.13.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.13.y=dcd2b010f17d64f19ac6a1f7cc77d85faf29196a
FYI, the patches that Mario mentioned above landed Linus' tree for v4.14-rc1
and hopefully will be backported to 4.13.
See details here:
https://github.com/01org/thunderbolt-software-user-space/issues/24#issuecomment-328011428
** Bug watch added:
I wonder if we need to sleep a second between the unbind and the rebind?
I still haven't restarted but I will test that while monitoring with
`journalctl -xf` in another terminal.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Yea, I ran it as root.
--
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/1697395
Title:
Thunderbolt devices don't work if connected during boot
Status in linux package in Ubuntu:
Kai-Heng, did you run the command as root? Otherwise you may want to
`sudo su` and run the loop or "prime" your sudo by running `sudo echo`
(to get prompted for you password once) and then use the same loop but
instead of `> /path/to/file` use `| tee /path/to/file` and see if you
get different
Probably physical intervention is the only viable workaround now...
--
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/1697395
Title:
Thunderbolt devices don't work if connected during boot
# for i in $(lspci -nn | grep Alpine | awk '{print $1}'); do
i=":$i"; echo $i
echo "$i" > /sys/bus/pci/drivers/pcieport/unbind
echo "$i" > /sys/bus/pci/drivers/pcieport/bind
done
:06:00.0
:07:00.0
:07:01.0
:07:02.0
:08:00.0
echo: write error: no such device
Something like this:
for i in $(lspci -nn | grep Alpine | awk '{print $1}'); do
i=":$i"
echo "$i" > /sys/bus/pci/drivers/pcieport/unbind
echo "$i" > /sys/bus/pci/drivers/pcieport/bind
done
--
You received this bug notification because you are a member of Kernel
Packages, which
@Kai-Heng: How do I unbind/bind all devices? Never did this before :/
echo ":00:1d.6" > /sys/bus/pci/drivers/pcieport/unbind
Seems to unbind all usb devices, at least they stop working :D ... but
echo ":00:1d.6" > /sys/bus/pci/drivers/pcieport/bind
has no effect.
lspci | grep Alpine
Hi, i am using Dell XPS 9360 Developer Edition (with ubuntu 16.04
(kernel 4.4.0)) together with TB16 docking station. I have the same
issue, if TB16 is plugged before booting, the peripherals such as the
USB port, ethernet port, USB-C port, etc. works fine. But they are not
detected once the TB16
Hmm, maybe try go to /sys/bus/pci/drivers/pcieport, then unbind & bind
all Alpine Ridge devices?
--
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/1697395
Title:
Thunderbolt devices don't
nope, does not help. Only reconnecting helps :-/
--
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/1697395
Title:
Thunderbolt devices don't work if connected during boot
Status in linux
@Mario
Thanks for the info.
@Andre
Does doing a PCI rescan work for you?
$ sudo -s
# echo 1 > /sys/bus/pci/rescan
--
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/1697395
Title:
@Kai Heng:
It should not be machine/chipset specific, but may have some BIOS
component to this due to BIOS sends the hotplug event. If the hotplug
event comes too soon (before enumeration is done) you should see this
behavior.
It's specific to PCIe tunnels of TBT devices. You won't for example
I could reproduce this issue on my old TB15 dock with my XP15 9550, too.
@Kai-Heng Feng: Dell is replacing the TB15 with the TB16 for free,
because of heat problems and other issues especially if you use two 4k
monitors. But you need to call the service center and they do not want
the old TB15
Thanks for the info, Mario.
Is it machine/chipset specific? I didn't see this issue on Latitude E7370
though.
--
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/1697395
Title:
Thunderbolt
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Tags added: kernel-da-key
--
You received this bug notification because you are a member
Mika has already consulted with the ACPI guys and has an idea, but it's
going to require changes outside of Linux first in ACPICA. So it
shouldn't be a very quick fix.
>There is also another PCI/ACPI related issue that Mario reported where
>we execute _INI() methods before the initial PCI scan
@Mario, thanks for this additional information. Could you image a way to
influence this order, to let the pci_scan happen before ACPI is
initialized?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
21 matches
Mail list logo
