After an update to 5.3.0-26-generic (and then some time passed), got a
connection fail when unsuspending.
The attached log is from journalctl -b -k with dyndbg enabled, from
suspending (Jan 21, 23:58) through complete failure of the connection at
09:08:16 and a disconnect and reconnect that succee
With the current setup, I didn't manage to reproduce the problem yet
today. Here's the debug log that you asked that includes booting with
the thunderbolt connected, then disconnecting and reconnecting - all
completing successfully.
** Attachment added: "okconnect.log"
https://bugs.launchpad.n
Can you please attach full dmesg, like `journalctl -b -k`? Also please
don't tar it so I can view it directly in the browser.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856161
Title:
Thunderbolt
The `logitech-hidpp-device` is the Logitech unified receiver I have
connected to the dock. It always generates lots of error messages like
this, even when connected directly to the computer's built-in USB port.
There's another Logitech unified receiver connected to the computer
itself, for the mou
I can see tons of logitech-hidpp-device errors and then xhci_hcd dies:
Dec 31 13:33:19 vesho kernel: logitech-hidpp-device 0003:046D:402D.0029: error
in parameter
Dec 31 13:33:19 vesho kernel: xhci_hcd :0e:00.0: ep 0x83 - asked for 32
bytes, 17 bytes untransferred
Dec 31 13:33:19 vesho kernel
And now, I managed to get a repro of the stated problem: USB controller
fails to complete initialization when connecting the thunderbolt cable.
This was 100% reproduceable for a few runs (logs 1 through 5), and only
stopped reproducing when I removed an Android device that was sitting at
the end o
Attached kernel log of trying to recover from lp1766076 and failing.
The log starts at the point where we do `echo -n $id >
/sys/bus/pci/drivers/xhci_hcd/bind` at 13:05:44, and the driver gives up
at 13:05:55.
I'm actually not sure how relevant this is to this issue...
** Attachment added: "lp18
With the `dyndbg` flag, I can't seem to reproduce the problem: I tried
to connect and disconnect the cable a few times as well as rebooting
(which was almost 100% guaranteed to cause this issue).
I attached logs of the successful thunderbolt connection while running
and a boot log with the dock al
Can you please boot with kernel parameter "dyndbg='file drivers/usb/*
+p'" and attach dmesg once you reproduce the issue. The xhci reset part
shouldn't be included.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Since I started getting the bug 1766076 xhci failure, this problem has
become more acute as the automatic workaround described in 1766076 no
longer works - when resetting the xhci bus, the bus fails to be set up
properly due to this issue and I'm left with a non-functioning system.
See attached lo
Tries booting with the chain disconnected from the dock, and as expected
- the system boots correctly with the dock attached and built-in USB
devices present, after which plugging the USB cable in works well.
The problem seems to only be when external USB devices are connected to
the dock.
Here's
As I mentioned in comment 22, connecting the thunderbolt dock without
any additional USB devices plugged in, works well. After the controller
initializes, I can plug in the rest of the devices and they get set up
properly.
Comment 22 has a dmesg log off that.
I haven't tried booting with the dock
Does this happen when nothing is plugged to the dock?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856161
Title:
Thunderbolt dock fails to connect USB devices
To manage notifications about this b
Sorry, the joy was (relatively) short-lived: Even with
`/etc/default/grub` `GRUB_CMDLINE_LINUX_DEFAULT` setting set to empty, I
can still reproduce this problem with the lp1766076 kernel: it
definitely happens less - maybe 1 in 3 times instead of almost always -
but it still happens.
Here's a boot
Also connect/disconnect succeeds. See attached logs.
There are other problems now, which the kernel flags were supposed to
solve. I'd need to reboot a few times to figure out which flag causes
the problem.
** Attachment added: "lp1766076-tb-reconnect-success.log"
https://bugs.launchpad.net/ub
with the lp1766076 kernel, removing all the parameters after "quiet"
(I'm thinking the ones before that are required for successful boot),
the thunderbolt connects successfully on boot.
Attached dmesg log.
** Attachment added: "lp1766076-boot-dmesg-tbconnected.log"
https://bugs.launchpad.net/
Please remove all the kernel parameters.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856161
Title:
Thunderbolt dock fails to connect USB devices
To manage notifications about this bug go to:
htt
What I currently do, is to detach the USB cable from the dock, connect
the thunderbolt cable to the computer, wait for everything to settle
(either by looking at the dmesg log or just waiting for the dock audio
device to be registered - which shows on the OSD), then connecting the
USB cable. See at
Additionaly, with the lp1766076 kernel, after disconnecting the
thunderbolt cable, reconnecting it again fails - attached a short dmesg
log of just that.
** Attachment added: "lp1766076-tb-reconnect-fail-dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856161/+attachment/531455
The current situation is that I can't use the thunderbolt dock's USB hub
normally: it almost always fails to connect - with the generic Ubuntu
kernel or with the "5.3.0-25-generic #27~lp1766076" kernel suggested in
the comment above.
Trying to boot with the lp1766076 kernel (which I'm currently ru
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/90
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856161
Title:
Thunderbolt dock fails to connect USB devices
To manage notific
I also just saw this during a forced XHCI reset (after the USB bus
failed to connect):
8<
[ 247.130032] usb 3-1.6.2.4: new low-speed USB device number 9 using xhci_hcd
[ 247.388286] usb 3-1.6.2.4: New USB device found, idVendor=04d9,
idProduct=2013, bcdDevice= 1.03
[ 247.388287] usb 3-
apport information
** Tags added: apport-collected
** Description changed:
Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell
Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB
bus connects very slowly (15~20 seconds) and sometimes does not connect
23 matches
Mail list logo
