[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
I just started experiencing this issue again, last week. Same hardware: Precision 5520 with thunderbolt dock Dell TB-16. Kernel 5.11.0-22-generic on hirsute. ---8<--- Jun 27 14:53:11 vesho kernel: xhci_hcd :0e:00.0: ERROR unknown event type 15 Jun 27 14:53:16 vesho kernel: xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. Jun 27 14:53:16 vesho kernel: xhci_hcd :0e:00.0: USBSTS: Jun 27 14:53:16 vesho kernel: xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead Jun 27 14:53:16 vesho kernel: xhci_hcd :0e:00.0: HC died; cleaning up Jun 27 14:53:16 vesho kernel: usb 3-1: USB disconnect, device number 2 Jun 27 14:53:16 vesho kernel: usb 3-1.1: USB disconnect, device number 3 Jun 27 14:53:16 vesho kernel: usb 3-1.1.1: USB disconnect, device number 5 Jun 27 14:53:16 vesho kernel: usb 3-1.1.1.4: USB disconnect, device number 7 Jun 27 14:53:16 vesho kernel: usb 4-1: USB disconnect, device number 2 Jun 27 14:53:16 vesho kernel: usb 4-1.1: USB disconnect, device number 3 Jun 27 14:53:16 vesho kernel: usb 4-1.2: USB disconnect, device number 4 Jun 27 14:53:16 vesho kernel: usb 3-1.1.4: USB disconnect, device number 6 Jun 27 14:53:16 vesho kernel: usb 3-1.1.5: USB disconnect, device number 9 Jun 27 14:53:16 vesho kernel: usb 3-1.5: USB disconnect, device number 4 Jun 27 14:53:16 vesho kernel: usb 3-1.6: USB disconnect, device number 8 Jun 27 14:53:16 vesho kernel: usb 3-1.6.4: USB disconnect, device number 10 Jun 27 14:53:16 vesho kernel: usb 3-1.6.5: USB disconnect, device number 11 ---8<--- -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
#110 (Toumas) - I no longer experience this problem when running 20.10
with the latest kernel and the latest Dell firmware update (fwupdmgr
works reasonably well, but you can also just download the firmware file
from Dell, put it on a USB dok and the preboot screen lets you apply it
directly - no MS-Windows needed).
That being said, when I had the most serious problems, the small script
attached below would take care of things semi-automatically or
automatically (follow step 4 in the header doc for completely automated
recovery - when the dock crashes, wait a few seconds and it'll auto
recover).
#!/bin/bash
### Installation Instructions:
# 1. Install file into `/usr/local/bin/reset-tb`
#
# 2. Optional: allow password less sudo by creating a file
`/etc/sudoers.d/allow-reset-tb` with the following content:
# 8<-
# ALL = NOPASSWD: /usr/local/bin/reset-tb
# 8<-
#
# 3. Optional: allow easy access from the menu by creating a file
`$HOME/.local/share/applications/Reset Thunderbolt.desktop` with the following
content:
# 8<-
# [Desktop Entry]
# Exec=bash -c 'sudo -S /usr/local/bin/reset-tb'
# Icon=amarok_playlist_refresh
# Name=Reset Thunderbolt
# NoDisplay=false
# StartupNotify=false
# 8<-
#
# 4. Optional: run a service to automatically trigger the reset and send you an
email when "unknown event type 15" error is detected, by setting your email
# in this file below, then creating a file
`/etc/systemd/system/auto-reset-tb.service` with the following content:
# 8<-
# [Unit]
# Description=Automatically reset XHCI USB bus when detecting a Thunderbolt
dock error
# [Service]
# ExecStart=/usr/local/bin/reset-tb -l
# [Install]
# WantedBy=multi-user.target
# 8<-
# Then run:
# ```
# sudo systemctl daemon-reload
# sudo systemctl enable auto-reset-tb
# sudo systemctl start auto-reset-tb
# ```
EMAIL=o...@geek.co.il
SUBJECT="Detected Thunderbolt error in your system"
MESSAGE="
Check the logs, please.
"
function do_reset() {
tbtid="$(ls /sys/bus/pci/drivers/xhci_hcd/ | grep '[0-9]' | tail -n1)"
echo "Resetting thunderbolt bus">&2
for id in $tbtid; do
echo -n $id > /sys/bus/pci/drivers/xhci_hcd/unbind
done
sleep 1
for id in $tbtid; do
echo -n $id > /sys/bus/pci/drivers/xhci_hcd/bind
done
echo "Done resetting thunderbolt bus" >&2
}
function listen_for_reset() {
dmesg -w | while read line; do
[[ "$line" =~ "xHCI host controller not responding, assume
dead" ]] || continue
(
sleep 15 # let the busses settle
do_reset
sleep 90 # don't reset too much
)&
mail -s "$SUBJECT" $EMAIL <<< "$MESSAGE Date: $(date -R)"
done
}
[ "$1" == "-l" ] && listen_for_reset || do_reset
--
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/1766076
Title:
USB over thunderbolt turns off every once in a while
Status in Dell Sputnik:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
I'm using a USB hub in the Dell TB16 (240W) connected to a Dell
Precision 5520 using Thunderbolt 3.
Every so often (can be several times in an hour if I'm really unlucky,
some days it is less of a problem), the USB hub disconnects from the
computer and the devices connected to it lose power and stop
responding.
disconnecting and reconnecting the USB cables has no effect. I can
restore functionality by instructing the xhci_hcd driver to unbind
from the USB 3.0 Host Controller in the dock and to rebind to it using
the commands:
echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind
echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind
Here's the dmesg output when the USB hub disconnects:
279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15
[279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop
endpoint command.
[279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding,
assume dead
[279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108
[279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up
[279283.07] usb 3-1.5: Failed to suspend device, error -22
[279283.022234] usb 3-1: USB disconnect, device number 2
[279283.022235] usb 3-1.1: USB disconnect, device number 3
[279283.022236] usb 3-1.1.1: USB disconnect, device number 5
[279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8
[279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11
[279283.022326] usb 4-1: USB disconnect, device number 2
[279283.022328] usb 4-1.1: USB disconnect, device number 3
[279283.022329] usb 4-1.1.1: USB disconnect, device number 5
[279283.022998] usb 4-1.2: USB disconnect, device number 4
[279283.191217] usb 3-1.1.1.5:
[Kernel-packages] [Bug 1861395] Re: system hang: i915 Resetting rcs0 for hang on rcs0
@sanette - the problem you describe doesn't seem to be the same problem
originally reported in this ticket: that problem was with kernel 5.4 and
was causing a complete hang - not for a few seconds, but complete
failure with a graphical system reset the only resolution.
You may be experiencing an earlier version, and less severe, of the
reported issue, on the 5.3 kernel. Regardless -it's not the exact same
issue.
Regarding the kernel.org bugzila comments: the fix was applied in
version 5.5 and 5.6 in the upstream kernel. It was not applied to 5.4 as
if yet (even though 5.4 is an LTS kernel and this is an extreme
regression 路) - for the upstream kernel. But Ubuntu developers have
applied the fix to the Ubuntu 5.4 kernels, at least for focal.
I suggest to upgrade to the 5.4 kernel reported above to contain the fix
(5.4.0-17.21 or later) and see if it solves your problem.
If you are interested in continuing to run kernel 5.3 on bionic, then I
suggest you open another ticket for the specific issue you are
experiencing - as it is not this issue, and this issue was resolved.
--
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/1861395
Title:
system hang: i915 Resetting rcs0 for hang on rcs0
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Eoan:
Invalid
Status in linux source package in Focal:
Fix Released
Bug description:
System hangs, unknown cause, When this happens, the mouse pointer
still moves, but I can't do anything else with the keys or clicking in
the UI. Only recover I have found is a hard power-off
Last bit of kern.log below:
Jan 30 12:43:51 aries kernel: [ 6649.263031] i915 :00:02.0: GPU HANG:
ecode 9:1:0x, hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.263032] GPU hangs can indicate a bug
anywhere in the entire gfx stack, including userspace.
Jan 30 12:43:51 aries kernel: [ 6649.263033] Please file a _new_ bug report
on bugs.freedesktop.org against DRI -> DRM/Intel
Jan 30 12:43:51 aries kernel: [ 6649.263033] drm/i915 developers can then
reassign to the right component if it's not a kernel issue.
Jan 30 12:43:51 aries kernel: [ 6649.263034] The GPU crash dump is required
to analyze GPU hangs, so please always attach it.
Jan 30 12:43:51 aries kernel: [ 6649.263034] GPU crash dump saved to
/sys/class/drm/card0/error
Jan 30 12:43:51 aries kernel: [ 6649.264039] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.264778] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:51 aries kernel: [ 6649.265046] i915 :00:02.0: Resetting
chip for hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.267018] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:51 aries kernel: [ 6649.267764] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:59 aries kernel: [ 6657.262680] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:01 aries kernel: [ 6659.246609] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:09 aries kernel: [ 6667.246324] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:09 aries kernel: [ 6667.494008] show_signal_msg: 20 callbacks
suppressed
Jan 30 12:44:09 aries kernel: [ 6667.494011] GpuWatchdog[6827]: segfault at 0
ip 55fd01917ded sp 7f63043cc480 error 6 in chrome[55fcfd9dc000+7171000]
Jan 30 12:44:09 aries kernel: [ 6667.494017] Code: 48 c1 c9 03 48 81 f9 af 00
00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be
01 00 00 00 ff 50 30 04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d a4 03 01 80
7d 8f 00
Jan 30 12:44:23 aries kernel: [ 6681.265885] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:25 aries kernel: [ 6683.245838] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:27 aries kernel: [ 6685.261749] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:29 aries kernel: [ 6687.245641] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:31 aries kernel: [ 6689.261618] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:51 aries kernel: [ 6709.260901] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-12-generic 5.4.0-12.15
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 30 12:51:24 2020
InstallationDate: Installed on 2018-06-18 (591 days ago)
[Kernel-packages] [Bug 1861395] Re: system hang: i915 Resetting rcs0 for hang on rcs0
Sorry for the long delay in testing - I've been cooped up at home due to
illness, where my ability to test with different display configurations
in severely limited.
That being said, I've been running the canonical-kernel-team/unstable
5.4.0-17.21 for about a week now, including two days in the office where
I usually repro the problem, and no incidents so far.
I'm willing to call this "fixed".
--
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/1861395
Title:
system hang: i915 Resetting rcs0 for hang on rcs0
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Eoan:
Invalid
Status in linux source package in Focal:
Incomplete
Bug description:
System hangs, unknown cause, When this happens, the mouse pointer
still moves, but I can't do anything else with the keys or clicking in
the UI. Only recover I have found is a hard power-off
Last bit of kern.log below:
Jan 30 12:43:51 aries kernel: [ 6649.263031] i915 :00:02.0: GPU HANG:
ecode 9:1:0x, hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.263032] GPU hangs can indicate a bug
anywhere in the entire gfx stack, including userspace.
Jan 30 12:43:51 aries kernel: [ 6649.263033] Please file a _new_ bug report
on bugs.freedesktop.org against DRI -> DRM/Intel
Jan 30 12:43:51 aries kernel: [ 6649.263033] drm/i915 developers can then
reassign to the right component if it's not a kernel issue.
Jan 30 12:43:51 aries kernel: [ 6649.263034] The GPU crash dump is required
to analyze GPU hangs, so please always attach it.
Jan 30 12:43:51 aries kernel: [ 6649.263034] GPU crash dump saved to
/sys/class/drm/card0/error
Jan 30 12:43:51 aries kernel: [ 6649.264039] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.264778] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:51 aries kernel: [ 6649.265046] i915 :00:02.0: Resetting
chip for hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.267018] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:51 aries kernel: [ 6649.267764] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:59 aries kernel: [ 6657.262680] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:01 aries kernel: [ 6659.246609] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:09 aries kernel: [ 6667.246324] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:09 aries kernel: [ 6667.494008] show_signal_msg: 20 callbacks
suppressed
Jan 30 12:44:09 aries kernel: [ 6667.494011] GpuWatchdog[6827]: segfault at 0
ip 55fd01917ded sp 7f63043cc480 error 6 in chrome[55fcfd9dc000+7171000]
Jan 30 12:44:09 aries kernel: [ 6667.494017] Code: 48 c1 c9 03 48 81 f9 af 00
00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be
01 00 00 00 ff 50 30 04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d a4 03 01 80
7d 8f 00
Jan 30 12:44:23 aries kernel: [ 6681.265885] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:25 aries kernel: [ 6683.245838] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:27 aries kernel: [ 6685.261749] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:29 aries kernel: [ 6687.245641] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:31 aries kernel: [ 6689.261618] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:51 aries kernel: [ 6709.260901] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-12-generic 5.4.0-12.15
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 30 12:51:24 2020
InstallationDate: Installed on 2018-06-18 (591 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-5.4
UpgradeStatus: Upgraded to focal on 2020-01-22 (8 days ago)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dpb 115653 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2018-06-18 (604 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
[Kernel-packages] [Bug 1861395] Re: system hang: i915 Resetting rcs0 for hang on rcs0
Just had an i915 crash on 5.4.0-14-generic #17+lp1853044v1. There appear
to be 3 crashes right after the other, I'm not sure what it means. It
could be related to the fact that I have a script running that detects
these crashes, waits 30 seconds and then restarts the display manager -
but if it is related than that means that the additional crashes were
when there was just the display manager, and that never happened to me
before.
Kernel log:
8<
-- Logs begin at Thu 2020-02-20 17:15:40 IST, end at Tue 2020-03-03 12:31:08
IST. --
Mar 03 12:27:26 vesho kernel: i915 :00:02.0: GPU HANG: ecode
9:1:0x, hang on rcs0
Mar 03 12:27:26 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Mar 03 12:27:26 vesho kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0
reset request timed out: {request: 0001, RESET_CTL: 0001}
Mar 03 12:27:26 vesho kernel: i915 :00:02.0: Resetting chip for hang on rcs0
Mar 03 12:27:26 vesho kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0
reset request timed out: {request: 0001, RESET_CTL: 0001}
Mar 03 12:27:26 vesho kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0
reset request timed out: {request: 0001, RESET_CTL: 0001}
Mar 03 12:27:29 vesho kernel: Asynchronous wait on fence i915:Xorg[1819]:87b8c
timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915])
Mar 03 12:27:29 vesho kernel: Asynchronous wait on fence i915:Xorg[1819]:87b8e
timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915])
Mar 03 12:27:34 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Mar 03 12:27:35 vesho kernel: GpuWatchdog[14346]: segfault at 0 ip
561a55c29fa2 sp 7ff6edf3b4c0 error 6 in chrome[561a51ce3000+7287000]
Mar 03 12:27:35 vesho kernel: Code: 83 c3 e8 75 e9 41 8b 85 00 01 00 00 85 c0
0f 84 99 00 00 00 48 8d 3d f3 60 4b fb be 01 00 00 00 ba 03 00 00 00 e8 be 17
a6 fe 04 25 00 00 00 00 37 13 00 00 c6 05 fc 76 b9 03 01 80 7d 8f 00
Mar 03 12:27:38 vesho kernel: mce: CPU7: Core temperature above threshold, cpu
clock throttled (total events = 1)
Mar 03 12:27:38 vesho kernel: mce: CPU6: Package temperature above threshold,
cpu clock throttled (total events = 1)
Mar 03 12:27:38 vesho kernel: mce: CPU3: Core temperature above threshold, cpu
clock throttled (total events = 1)
Mar 03 12:27:38 vesho kernel: mce: CPU2: Package temperature above threshold,
cpu clock throttled (total events = 1)
Mar 03 12:27:38 vesho kernel: mce: CPU3: Package temperature above threshold,
cpu clock throttled (total events = 1)
Mar 03 12:27:38 vesho kernel: mce: CPU7: Package temperature above threshold,
cpu clock throttled (total events = 1)
Mar 03 12:27:38 vesho kernel: mce: CPU0: Package temperature above threshold,
cpu clock throttled (total events = 1)
Mar 03 12:27:38 vesho kernel: mce: CPU1: Package temperature above threshold,
cpu clock throttled (total events = 1)
Mar 03 12:27:38 vesho kernel: mce: CPU4: Package temperature above threshold,
cpu clock throttled (total events = 1)
Mar 03 12:27:38 vesho kernel: mce: CPU5: Package temperature above threshold,
cpu clock throttled (total events = 1)
Mar 03 12:27:38 vesho kernel: mce: CPU7: Core temperature/speed normal
Mar 03 12:27:38 vesho kernel: mce: CPU3: Core temperature/speed normal
Mar 03 12:27:38 vesho kernel: mce: CPU2: Package temperature/speed normal
Mar 03 12:27:38 vesho kernel: mce: CPU6: Package temperature/speed normal
Mar 03 12:27:38 vesho kernel: mce: CPU3: Package temperature/speed normal
Mar 03 12:27:38 vesho kernel: mce: CPU7: Package temperature/speed normal
Mar 03 12:27:38 vesho kernel: mce: CPU5: Package temperature/speed normal
Mar 03 12:27:38 vesho kernel: mce: CPU4: Package temperature/speed normal
Mar 03 12:27:38 vesho kernel: mce: CPU1: Package temperature/speed normal
Mar 03 12:27:38 vesho kernel: mce: CPU0: Package temperature/speed normal
Mar 03 12:27:44 vesho kernel: i915 :00:02.0: GPU HANG: ecode
9:1:0x, hang on rcs0
Mar 03 12:27:44 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Mar 03 12:27:46 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Mar 03 12:27:48 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Mar 03 12:27:50 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Mar 03 12:27:52 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Mar 03 12:27:54 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Mar 03 12:27:56 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Mar 03 12:27:58 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Mar 03 12:28:00 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Mar 03 12:28:02 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Mar 03 12:28:04 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Mar 03 12:28:05 vesho kernel: vetha609238: renamed from eth0
Mar 03 12:28:05 vesho kernel: docker0: port 1(veth5dacd92) entered disabled
state
[Kernel-packages] [Bug 1861395] Re: system hang: i915 Resetting rcs0 for hang on rcs0
The problem didn't reproduce with mainline PPA kernel 5.5.6. I'm now
running "5.4.0-14-generic #17+lp1853044v1", which is fine so far, but
due to the flu and extended weekend - I didn't have enough time to
properly stress test this. Likely will happen tomorrow.
--
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/1861395
Title:
system hang: i915 Resetting rcs0 for hang on rcs0
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Eoan:
Invalid
Status in linux source package in Focal:
Incomplete
Bug description:
System hangs, unknown cause, When this happens, the mouse pointer
still moves, but I can't do anything else with the keys or clicking in
the UI. Only recover I have found is a hard power-off
Last bit of kern.log below:
Jan 30 12:43:51 aries kernel: [ 6649.263031] i915 :00:02.0: GPU HANG:
ecode 9:1:0x, hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.263032] GPU hangs can indicate a bug
anywhere in the entire gfx stack, including userspace.
Jan 30 12:43:51 aries kernel: [ 6649.263033] Please file a _new_ bug report
on bugs.freedesktop.org against DRI -> DRM/Intel
Jan 30 12:43:51 aries kernel: [ 6649.263033] drm/i915 developers can then
reassign to the right component if it's not a kernel issue.
Jan 30 12:43:51 aries kernel: [ 6649.263034] The GPU crash dump is required
to analyze GPU hangs, so please always attach it.
Jan 30 12:43:51 aries kernel: [ 6649.263034] GPU crash dump saved to
/sys/class/drm/card0/error
Jan 30 12:43:51 aries kernel: [ 6649.264039] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.264778] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:51 aries kernel: [ 6649.265046] i915 :00:02.0: Resetting
chip for hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.267018] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:51 aries kernel: [ 6649.267764] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:59 aries kernel: [ 6657.262680] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:01 aries kernel: [ 6659.246609] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:09 aries kernel: [ 6667.246324] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:09 aries kernel: [ 6667.494008] show_signal_msg: 20 callbacks
suppressed
Jan 30 12:44:09 aries kernel: [ 6667.494011] GpuWatchdog[6827]: segfault at 0
ip 55fd01917ded sp 7f63043cc480 error 6 in chrome[55fcfd9dc000+7171000]
Jan 30 12:44:09 aries kernel: [ 6667.494017] Code: 48 c1 c9 03 48 81 f9 af 00
00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be
01 00 00 00 ff 50 30 04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d a4 03 01 80
7d 8f 00
Jan 30 12:44:23 aries kernel: [ 6681.265885] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:25 aries kernel: [ 6683.245838] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:27 aries kernel: [ 6685.261749] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:29 aries kernel: [ 6687.245641] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:31 aries kernel: [ 6689.261618] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:51 aries kernel: [ 6709.260901] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-12-generic 5.4.0-12.15
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 30 12:51:24 2020
InstallationDate: Installed on 2018-06-18 (591 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-5.4
UpgradeStatus: Upgraded to focal on 2020-01-22 (8 days ago)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dpb 115653 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2018-06-18 (604 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc.
Bus
[Kernel-packages] [Bug 1861395] Re: system hang: i915 Resetting rcs0 for hang on rcs0
Just got this triggered with 5.4.0-15-generic #18-Ubuntu from focal-
proposed.
Logs below.
If you want me to run another kernel, or try patched kernels, I can do
that.
Kernel log:
8<
Feb 25 10:08:08 vesho kernel: i915 :00:02.0: GPU HANG: ecode
9:1:0x, hang on rcs0
Feb 25 10:08:08 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 25 10:08:08 vesho kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0
reset request timed out: {request: 0001, RESET_CTL: 0001}
Feb 25 10:08:08 vesho kernel: i915 :00:02.0: Resetting chip for hang on rcs0
Feb 25 10:08:08 vesho kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0
reset request timed out: {request: 0001, RESET_CTL: 0001}
Feb 25 10:08:08 vesho kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0
reset request timed out: {request: 0001, RESET_CTL: 0001}
Feb 25 10:08:16 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 25 10:08:24 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 25 10:08:26 vesho kernel: GpuWatchdog[15034]: segfault at 0 ip
55af78399e32 sp 7f8b359414c0 error 6 in chrome[55af74453000+7287000]
Feb 25 10:08:26 vesho kernel: Code: 83 c3 e8 75 e9 41 8b 85 00 01 00 00 85 c0
0f 84 99 00 00 00 48 8d 3d 63 61 4b fb be 01 00 00 00 ba 03 00 00 00 e8 fe 17
a6 fe 04 25 00>
Feb 25 10:08:28 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
...
Feb 25 10:09:18 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 25 10:09:20 vesho kernel: i915 :00:02.0: GPU recovery timed out,
cancelling all in-flight rendering.
Feb 25 10:09:20 vesho kernel: i915 :00:02.0: Resetting chip for hang on rcs0
Feb 25 10:09:22 vesho kernel: i915 :00:02.0: GPU recovery timed out,
cancelling all in-flight rendering.
Feb 25 10:09:22 vesho kernel: i915 :00:02.0: Resetting chip for hang on rcs0
Feb 25 10:09:22 vesho kernel: fbcon: Taking over console
Feb 25 10:09:23 vesho kernel: Console: switching to colour frame buffer device
240x67
Feb 25 10:09:30 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 25 10:09:38 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
...
Feb 25 10:10:32 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 25 10:10:34 vesho kernel: i915 :00:02.0: GPU recovery timed out,
cancelling all in-flight rendering.
Feb 25 10:10:34 vesho kernel: i915 :00:02.0: Resetting chip for hang on rcs0
Feb 25 10:10:36 vesho kernel: i915 :00:02.0: GPU recovery timed out,
cancelling all in-flight rendering.
Feb 25 10:10:36 vesho kernel: i915 :00:02.0: Resetting chip for hang on rcs0
Feb 25 10:10:46 vesho kernel: GpuWatchdog[53827]: segfault at 0 ip
55f286b35e32 sp 7f396a9a24c0 error 6 in chrome[55f282bef000+7287000]
Feb 25 10:10:46 vesho kernel: Code: 83 c3 e8 75 e9 41 8b 85 00 01 00 00 85 c0
0f 84 99 00 00 00 48 8d 3d 63 61 4b fb be 01 00 00 00 ba 03 00 00 00 e8 fe 17
a6 fe 04 25 00>
Feb 25 10:10:56 vesho kernel: GpuWatchdog[53920]: segfault at 0 ip
555c042dee32 sp 7f446a7b24c0 error 6 in chrome[555c00398000+7287000]
Feb 25 10:10:56 vesho kernel: Code: 83 c3 e8 75 e9 41 8b 85 00 01 00 00 85 c0
0f 84 99 00 00 00 48 8d 3d 63 61 4b fb be 01 00 00 00 ba 03 00 00 00 e8 fe 17
a6 fe 04 25 00>
8<
/sys/class/drm/card0/error:
8<
GPU HANG: ecode 9:1:0x, hang on rcs0
Kernel: 5.4.0-15-generic x86_64
Driver: 20190822
Time: 1582618088 s 331762 us
Boottime: 57363 s 47980 us
Uptime: 834 s 211397 us
Epoch: 4297439752 jiffies (250 HZ)
Capture: 4297439752 jiffies; 8224 ms ago, 0 ms after epoch
Reset count: 0
Suspend count: 1
Platform: KABYLAKE
Subplatform: 0x0
PCI ID: 0x591b
PCI Revision: 0x04
PCI Subsystem: 1028:07bf
IOMMU enabled?: 1
DMC loaded: yes
DMC fw version: 1.4
GT awake: yes
RPM wakelock: yes
PM suspended: no
EIR: 0x
IER: 0x0808
GTIER[0]: 0x01010101
GTIER[1]: 0x01010101
GTIER[2]: 0x0070
GTIER[3]: 0x0101
PGTBL_ER: 0x
FORCEWAKE: 0x00010001
DERRMR: 0x2077efef
CCID: 0x
fence[0] =
fence[1] =
fence[2] =
fence[3] =
fence[4] =
fence[5] = a43f097074c0001
fence[6] =
fence[7] =
fence[8] =
fence[9] =
fence[10] =
fence[11] =
fence[12] =
fence[13] =
fence[14] =
fence[15] =
fence[16] =
fence[17] =
fence[18] =
fence[19] =
fence[20] =
fence[21] =
fence[22] =
fence[23] =
fence[24] =
fence[25] =
fence[26] =
fence[27] =
fence[28] =
fence[29] =
fence[30] =
fence[31] =
ERROR: 0x
DONE_REG: 0x
FAULT_TLB_DATA: 0x0019 0xf4bbf313
Num Pipes: 3
Pipe [0]:
Power: on
SRC: 077f0437
STAT:
Plane [0]:
CNTR: c4042400
STRIDE: 0026
[Kernel-packages] [Bug 1861395] Re: system hang: i915 Resetting rcs0 for hang on rcs0
@David - as far as I know, before reporting kernel issues, Ubuntu users
are expected to try a repro with a mainline kernel. I've read (some of)
the discussion in the Freedesktop bug report where people have proposed
that various patches have possibly solved the problem, so I hit the
mainline PPA and got the newest 5.4 :-). And it looked promising for a
while.
Currently running 5.4.0-15-generic #18-Ubuntu from focal-proposed, and
so far so good.
--
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/1861395
Title:
system hang: i915 Resetting rcs0 for hang on rcs0
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Eoan:
Invalid
Status in linux source package in Focal:
Incomplete
Bug description:
System hangs, unknown cause, When this happens, the mouse pointer
still moves, but I can't do anything else with the keys or clicking in
the UI. Only recover I have found is a hard power-off
Last bit of kern.log below:
Jan 30 12:43:51 aries kernel: [ 6649.263031] i915 :00:02.0: GPU HANG:
ecode 9:1:0x, hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.263032] GPU hangs can indicate a bug
anywhere in the entire gfx stack, including userspace.
Jan 30 12:43:51 aries kernel: [ 6649.263033] Please file a _new_ bug report
on bugs.freedesktop.org against DRI -> DRM/Intel
Jan 30 12:43:51 aries kernel: [ 6649.263033] drm/i915 developers can then
reassign to the right component if it's not a kernel issue.
Jan 30 12:43:51 aries kernel: [ 6649.263034] The GPU crash dump is required
to analyze GPU hangs, so please always attach it.
Jan 30 12:43:51 aries kernel: [ 6649.263034] GPU crash dump saved to
/sys/class/drm/card0/error
Jan 30 12:43:51 aries kernel: [ 6649.264039] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.264778] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:51 aries kernel: [ 6649.265046] i915 :00:02.0: Resetting
chip for hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.267018] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:51 aries kernel: [ 6649.267764] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:59 aries kernel: [ 6657.262680] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:01 aries kernel: [ 6659.246609] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:09 aries kernel: [ 6667.246324] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:09 aries kernel: [ 6667.494008] show_signal_msg: 20 callbacks
suppressed
Jan 30 12:44:09 aries kernel: [ 6667.494011] GpuWatchdog[6827]: segfault at 0
ip 55fd01917ded sp 7f63043cc480 error 6 in chrome[55fcfd9dc000+7171000]
Jan 30 12:44:09 aries kernel: [ 6667.494017] Code: 48 c1 c9 03 48 81 f9 af 00
00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be
01 00 00 00 ff 50 30 04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d a4 03 01 80
7d 8f 00
Jan 30 12:44:23 aries kernel: [ 6681.265885] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:25 aries kernel: [ 6683.245838] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:27 aries kernel: [ 6685.261749] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:29 aries kernel: [ 6687.245641] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:31 aries kernel: [ 6689.261618] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:51 aries kernel: [ 6709.260901] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-12-generic 5.4.0-12.15
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 30 12:51:24 2020
InstallationDate: Installed on 2018-06-18 (591 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-5.4
UpgradeStatus: Upgraded to focal on 2020-01-22 (8 days ago)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dpb 115653 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2018-06-18 (604 days ago)
InstallationMedia: Ubuntu 18.04
[Kernel-packages] [Bug 1861395] Re: system hang: i915 Resetting rcs0 for hang on rcs0
I just got the same freeze with the mainline 5.4.22. I'm trying the
proposed kernel.
--
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/1861395
Title:
system hang: i915 Resetting rcs0 for hang on rcs0
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Eoan:
Invalid
Status in linux source package in Focal:
Incomplete
Bug description:
System hangs, unknown cause, When this happens, the mouse pointer
still moves, but I can't do anything else with the keys or clicking in
the UI. Only recover I have found is a hard power-off
Last bit of kern.log below:
Jan 30 12:43:51 aries kernel: [ 6649.263031] i915 :00:02.0: GPU HANG:
ecode 9:1:0x, hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.263032] GPU hangs can indicate a bug
anywhere in the entire gfx stack, including userspace.
Jan 30 12:43:51 aries kernel: [ 6649.263033] Please file a _new_ bug report
on bugs.freedesktop.org against DRI -> DRM/Intel
Jan 30 12:43:51 aries kernel: [ 6649.263033] drm/i915 developers can then
reassign to the right component if it's not a kernel issue.
Jan 30 12:43:51 aries kernel: [ 6649.263034] The GPU crash dump is required
to analyze GPU hangs, so please always attach it.
Jan 30 12:43:51 aries kernel: [ 6649.263034] GPU crash dump saved to
/sys/class/drm/card0/error
Jan 30 12:43:51 aries kernel: [ 6649.264039] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.264778] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:51 aries kernel: [ 6649.265046] i915 :00:02.0: Resetting
chip for hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.267018] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:51 aries kernel: [ 6649.267764] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:59 aries kernel: [ 6657.262680] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:01 aries kernel: [ 6659.246609] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:09 aries kernel: [ 6667.246324] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:09 aries kernel: [ 6667.494008] show_signal_msg: 20 callbacks
suppressed
Jan 30 12:44:09 aries kernel: [ 6667.494011] GpuWatchdog[6827]: segfault at 0
ip 55fd01917ded sp 7f63043cc480 error 6 in chrome[55fcfd9dc000+7171000]
Jan 30 12:44:09 aries kernel: [ 6667.494017] Code: 48 c1 c9 03 48 81 f9 af 00
00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be
01 00 00 00 ff 50 30 04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d a4 03 01 80
7d 8f 00
Jan 30 12:44:23 aries kernel: [ 6681.265885] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:25 aries kernel: [ 6683.245838] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:27 aries kernel: [ 6685.261749] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:29 aries kernel: [ 6687.245641] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:31 aries kernel: [ 6689.261618] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:51 aries kernel: [ 6709.260901] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-12-generic 5.4.0-12.15
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 30 12:51:24 2020
InstallationDate: Installed on 2018-06-18 (591 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-5.4
UpgradeStatus: Upgraded to focal on 2020-01-22 (8 days ago)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dpb 115653 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2018-06-18 (604 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc.
Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated
Camera
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux
[Kernel-packages] [Bug 1861395] Re: system hang: i915 Resetting rcs0 for hang on rcs0
After updating to kernel mainline build 5.4.22-050422-generic
#202002240833, I couldn't immediately trigger the problem (including
scrubbing through a YouTube video on Chrome, as mentioned in upstream
freedesktop ticket), even though previously I could usually get the
problem triggered within a few minutes of logging in, without a YouTube
video.
If this changes, I will update.
--
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/1861395
Title:
system hang: i915 Resetting rcs0 for hang on rcs0
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Eoan:
Invalid
Status in linux source package in Focal:
Incomplete
Bug description:
System hangs, unknown cause, When this happens, the mouse pointer
still moves, but I can't do anything else with the keys or clicking in
the UI. Only recover I have found is a hard power-off
Last bit of kern.log below:
Jan 30 12:43:51 aries kernel: [ 6649.263031] i915 :00:02.0: GPU HANG:
ecode 9:1:0x, hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.263032] GPU hangs can indicate a bug
anywhere in the entire gfx stack, including userspace.
Jan 30 12:43:51 aries kernel: [ 6649.263033] Please file a _new_ bug report
on bugs.freedesktop.org against DRI -> DRM/Intel
Jan 30 12:43:51 aries kernel: [ 6649.263033] drm/i915 developers can then
reassign to the right component if it's not a kernel issue.
Jan 30 12:43:51 aries kernel: [ 6649.263034] The GPU crash dump is required
to analyze GPU hangs, so please always attach it.
Jan 30 12:43:51 aries kernel: [ 6649.263034] GPU crash dump saved to
/sys/class/drm/card0/error
Jan 30 12:43:51 aries kernel: [ 6649.264039] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.264778] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:51 aries kernel: [ 6649.265046] i915 :00:02.0: Resetting
chip for hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.267018] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:51 aries kernel: [ 6649.267764] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:59 aries kernel: [ 6657.262680] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:01 aries kernel: [ 6659.246609] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:09 aries kernel: [ 6667.246324] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:09 aries kernel: [ 6667.494008] show_signal_msg: 20 callbacks
suppressed
Jan 30 12:44:09 aries kernel: [ 6667.494011] GpuWatchdog[6827]: segfault at 0
ip 55fd01917ded sp 7f63043cc480 error 6 in chrome[55fcfd9dc000+7171000]
Jan 30 12:44:09 aries kernel: [ 6667.494017] Code: 48 c1 c9 03 48 81 f9 af 00
00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be
01 00 00 00 ff 50 30 04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d a4 03 01 80
7d 8f 00
Jan 30 12:44:23 aries kernel: [ 6681.265885] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:25 aries kernel: [ 6683.245838] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:27 aries kernel: [ 6685.261749] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:29 aries kernel: [ 6687.245641] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:31 aries kernel: [ 6689.261618] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:51 aries kernel: [ 6709.260901] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-12-generic 5.4.0-12.15
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 30 12:51:24 2020
InstallationDate: Installed on 2018-06-18 (591 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-5.4
UpgradeStatus: Upgraded to focal on 2020-01-22 (8 days ago)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dpb 115653 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2018-06-18 (604 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
Bus 002
[Kernel-packages] [Bug 1861395] Re: system hang: i915 Resetting rcs0 for hang on rcs0
I think I'm triggering this problem with focal 5.4.0-14-generic
#17-Ubuntu.
Kernel log says:
8<
Feb 24 15:27:53 vesho kernel: Asynchronous wait on fence i915:Xorg[2401]:1d16c
timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915])
Feb 24 15:27:53 vesho kernel: Asynchronous wait on fence i915:Xorg[2401]:1d170
timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915])
Feb 24 15:27:53 vesho kernel: Asynchronous wait on fence i915:Xorg[2401]:1d16e
timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915])
Feb 24 15:27:57 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:05 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:07 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:09 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:11 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:13 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:15 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:17 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:19 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:21 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:23 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:25 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:27 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:29 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:31 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:33 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:35 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:37 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:39 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:41 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:42 vesho kernel: GpuWatchdog[9598]: segfault at 0 ip
560157086e32 sp 7f17aaa944c0 error 6 in chrome[56015314+7287000]
Feb 24 15:28:42 vesho kernel: Code: 83 c3 e8 75 e9 41 8b 85 00 01 00 00 85 c0
0f 84 99 00 00 00 48 8d 3d 63 61 4b fb be 01 00 00 00 ba 03 00 00 00 e8 fe 17
a6 fe 04 25 00>
Feb 24 15:28:43 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:45 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:47 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:49 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:51 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:53 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:55 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:57 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:28:59 vesho kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0
Feb 24 15:29:01 vesho kernel: i915 :00:02.0: GPU recovery timed out,
cancelling all in-flight rendering.
Feb 24 15:29:01 vesho kernel: i915 :00:02.0: Resetting chip for hang on rcs0
Feb 24 15:29:02 vesho kernel: fbcon: Taking over console
Feb 24 15:29:02 vesho kernel: Console: switching to colour frame buffer device
240x67
Feb 24 15:29:03 vesho kernel: i915 :00:02.0: GPU recovery timed out,
cancelling all in-flight rendering.
Feb 24 15:29:03 vesho kernel: i915 :00:02.0: Resetting chip for hang on rcs0
Feb 24 15:29:13 vesho kernel: GpuWatchdog[17771]: segfault at 0 ip
55f174f88e32 sp 7f5f101404c0 error 6 in chrome[55f171042000+7287000]
Feb 24 15:29:13 vesho kernel: Code: 83 c3 e8 75 e9 41 8b 85 00 01 00 00 85 c0
0f 84 99 00 00 00 48 8d 3d 63 61 4b fb be 01 00 00 00 ba 03 00 00 00 e8 fe 17
a6 fe 04 25 00>
Feb 24 15:29:23 vesho kernel: GpuWatchdog[18031]: segfault at 0 ip
55e12a17ee32 sp 7f2bfbe2a4c0 error 6 in chrome[55e126238000+7287000]
Feb 24 15:29:23 vesho kernel: Code: 83 c3 e8 75 e9 41 8b 85 00 01 00 00 85 c0
0f 84 99 00 00 00 48 8d 3d 63 61 4b fb be 01 00 00 00 ba 03 00 00 00 e8 fe 17
a6 fe 04 25 00>
8<-
("fbcon" because I switch to a text vt to recover)
`/sys/class/drm/card0/error` has:
8<
GPU HANG: ecode 9:1:0x, hang on rcs0
Kernel: 5.4.0-14-generic x86_64
Driver: 20190822
Time: 1582550869 s 450292 us
Boottime: 917 s 861996 us
Uptime: 916 s 761786 us
Epoch: 4295121736 jiffies (250 HZ)
Capture: 4295121736 jiffies; 2568 ms ago, 0 ms after epoch
Reset count: 0
Suspend count: 0
Platform: KABYLAKE
Subplatform: 0x0
PCI ID: 0x591b
PCI Revision: 0x04
PCI Subsystem: 1028:07bf
IOMMU enabled?: 1
DMC loaded: yes
DMC fw version: 1.4
GT awake: yes
RPM wakelock: yes
PM suspended: no
EIR: 0x
IER: 0x0808
[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices
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 succeeded. ** Attachment added: "lp1856161-thunderbolt-debug.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856161/+attachment/5322120/+files/lp1856161-thunderbolt-debug.log -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Confirmed Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream
[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices
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.net/ubuntu/+source/linux/+bug/1856161/+attachment/5317699/+files/okconnect.log -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Confirmed Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor:
[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices
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 mouse that travels with the laptop, and that doesn't do this behavior, it just looks like this (w/o debug logs): Dec 31 17:11:42 vesho kernel: usb 1-1: New USB device found, idVendor=046d, idProduct=c52b, bcdDevice=12.10 Dec 31 17:11:42 vesho kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Dec 31 17:11:42 vesho kernel: usb 1-1: Product: USB Receiver Dec 31 17:11:42 vesho kernel: usb 1-1: Manufacturer: Logitech Dec 31 17:11:42 vesho kernel: logitech-djreceiver 0003:046D:C52B.0090: hiddev0,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-:00:14.0-1/input2 Dec 31 17:11:42 vesho kernel: logitech-hidpp-device 0003:046D:4026.0091: HID++ 2.0 device connected. Dec 31 17:11:42 vesho kernel: input: Logitech T400 as /devices/pci:00/:00:14.0/usb1/1-1/1-1:1.2/0003:046D:C52B.0090/0003:046D:4026.0091/input/input115 Dec 31 17:11:42 vesho kernel: logitech-hidpp-device 0003:046D:4026.0091: input,hidraw2: USB HID v1.11 Keyboard [Logitech T400] on usb-:00:14.0-1/input2:1 According to fwupdmgr, they are both running an up to date firmware (both got updated recently, though they have a different "VersionBootloader" where the OK one has "BOT01.02_B0014" and the problematic one has "BOT01.02_B0015". Interestingly enough, at one point I got the "unknown event type 15" error from lp1766076 immediately when plugging in the problematic receiver to the dock, but I didn't manage to reproduce that. I'm going to try to work without the problematic receiver for a bit and see if things improve. -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Confirmed Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin:
[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices
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 of the USB chain - this is log 6 that successfully completed setup. ** Attachment added: "lp1856161-dyndbg-logs-connect-fail.tar.gz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856161/+attachment/5316692/+files/lp1856161-dyndbg-logs-connect-fail.tar.gz -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Confirmed Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid:
[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices
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: "lp1856161-dyndbg-xhci-dead-failed-to-recover.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856161/+attachment/5316690/+files/lp1856161-dyndbg-xhci-dead-failed-to-recover.log -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Confirmed Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream
[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices
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 already connected. There are things there that seemed to me like error messages that might be interesting regardless? I'll continue using the `dyndbg` flag and will report later this week if the problem has been reproduced (I connect the dock a could of times a day, usually when the computer is already on, but sometimes when it is suspended or off), or whether enabling the debug flag is a workaround :-p ** Attachment added: "lp1856161-dyndbg-logs.tar.gz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856161/+attachment/5316687/+files/lp1856161-dyndbg-logs.tar.gz -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Confirmed Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell
[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices
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 log for when trying to reset the xhci bus while all devices are connected to the dock. Currently my recovery procedure is either: - reset the bus again (manually) and pray for it to work (it does every 5-6 times) - or manually disconnect the USB chain (I've moved it to the front port so its more accessible); reset the bus; wait for everything to settle; count to 5; reconnect the USB chain. The counting part is important as if I attach the chain too early after the last xhci message in dmesg, it fails to setup with the same error as if it was connected during the reset. ** Attachment added: "reset-xhci-failure.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856161/+attachment/5316520/+files/reset-xhci-failure.log -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Confirmed Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
Just had the "unknown event type 15" error happen again, with the lp1766076 kernel and current firmware: ---8<--- Dec 25 11:19:34 vesho kernel: xhci_hcd :0e:00.0: ERROR unknown event type 15 Dec 25 11:19:39 vesho kernel: xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. Dec 25 11:19:39 vesho kernel: xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead Dec 25 11:19:39 vesho kernel: xhci_hcd :0e:00.0: HC died; cleaning up Dec 25 11:19:39 vesho kernel: usb 4-1.3.1: Failed to suspend device, error -22 Dec 25 11:19:39 vesho kernel: usb 3-1: USB disconnect, device number 2 Dec 25 11:19:39 vesho kernel: usb 3-1.3: USB disconnect, device number 4 Dec 25 11:19:39 vesho kernel: usb 3-1.3.1: USB disconnect, device number 5 Dec 25 11:19:39 vesho kernel: usb 3-1.3.1.4: USB disconnect, device number 9 Dec 25 11:19:39 vesho kernel: usb 4-1: USB disconnect, device number 2 Dec 25 11:19:39 vesho kernel: usb 4-1.2: USB disconnect, device number 3 Dec 25 11:19:39 vesho kernel: usb 3-1.3.1.5: USB disconnect, device number 11 Dec 25 11:19:39 vesho kernel: usb 3-1.3.2: USB disconnect, device number 6 Dec 25 11:19:39 vesho kernel: usb 3-1.3.2.4: USB disconnect, device number 8 Dec 25 11:19:39 vesho kernel: usb 4-1.3: USB disconnect, device number 4 Dec 25 11:19:39 vesho kernel: usb 4-1.3.1: USB disconnect, device number 5 Dec 25 11:19:39 vesho kernel: usb 3-1.3.4: USB disconnect, device number 7 Dec 25 11:19:39 vesho kernel: usb 3-1.3.5: USB disconnect, device number 10 Dec 25 11:19:39 vesho kernel: usb 3-1.5: USB disconnect, device number 3 ---8<--- Firmware versions: [Dell] Precision 5520 System Firmware: 0.1.16.0 [Dell] Precision M5520 Thunderbolt Controller: 26.01 [Dell] Dell TB16 Thunderbolt Cable: 0.0.3.18 [Dell] Dell TB16 Port Controller 1: 0.1.2.17 [Dell] Dell TB16 Port Controller 2: 0.1.2.50 [Synaptics] Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock: 3.10.002 [Dell] Dell Thunderbolt Dock: 16.00 [Dell] Dell Thunderbolt Cable: 16.00 [Dell] Dell TB16: 0.0.0.0 -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd
[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices
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 how the dock's USB controller tree looks after everything is plugged in: 8< /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/7p, 480M ID 0424:2807 Standard Microsystems Corp. Hub |__ Port 3: Dev 4, If 0, Class=Hub, Driver=hub/5p, 480M ID 0424:2734 Standard Microsystems Corp. |__ Port 4: Dev 7, If 2, Class=Audio, Driver=snd-usb-audio, 480M ID 03f0:a707 HP, Inc |__ Port 4: Dev 7, If 0, Class=Video, Driver=uvcvideo, 480M ID 03f0:a707 HP, Inc |__ Port 4: Dev 7, If 3, Class=Audio, Driver=snd-usb-audio, 480M ID 03f0:a707 HP, Inc |__ Port 4: Dev 7, If 1, Class=Video, Driver=uvcvideo, 480M ID 03f0:a707 HP, Inc |__ Port 2: Dev 6, If 0, Class=Hub, Driver=hub/4p, 480M ID 05e3:0608 Genesys Logic, Inc. Hub |__ Port 4: Dev 8, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M ID 04d9:2013 Holtek Semiconductor, Inc. Keyboard [Das Keyboard] |__ Port 4: Dev 8, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M ID 04d9:2013 Holtek Semiconductor, Inc. Keyboard [Das Keyboard] |__ Port 5: Dev 10, If 0, Class=Human Interface Device, Driver=usbhid, 480M ID 0424:274c Standard Microsystems Corp. |__ Port 1: Dev 5, If 0, Class=Hub, Driver=hub/5p, 480M ID 0424:2734 Standard Microsystems Corp. |__ Port 4: Dev 9, If 2, Class=Human Interface Device, Driver=usbhid, 12M ID 046d:c52b Logitech, Inc. Unifying Receiver |__ Port 4: Dev 9, If 0, Class=Human Interface Device, Driver=usbhid, 12M ID 046d:c52b Logitech, Inc. Unifying Receiver |__ Port 4: Dev 9, If 1, Class=Human Interface Device, Driver=usbhid, 12M ID 046d:c52b Logitech, Inc. Unifying Receiver |__ Port 5: Dev 11, If 0, Class=Human Interface Device, Driver=usbhid, 480M ID 0424:274c Standard Microsystems Corp. |__ Port 5: Dev 3, If 0, Class=Audio, Driver=snd-usb-audio, 480M ID 0bda:4014 Realtek Semiconductor Corp. |__ Port 5: Dev 3, If 1, Class=Audio, Driver=snd-usb-audio, 480M ID 0bda:4014 Realtek Semiconductor Corp. |__ Port 5: Dev 3, If 2, Class=Audio, Driver=snd-usb-audio, 480M ID 0bda:4014 Realtek Semiconductor Corp. |__ Port 5: Dev 3, If 3, Class=Audio, Driver=snd-usb-audio, 480M ID 0bda:4014 Realtek Semiconductor Corp. 8< -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Confirmed Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId:
[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices
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 connected without the additional USB devices, as that is not my use case (I don't usually shut down or reboot my computer), but I can try that later today. -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Confirmed Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin:
[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices
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 dmesg log of a failing boot with no (additional) kernel command line flags - xhci_hcd assumes the controller died on timestamp 27, after which none of the USB things on the dock work. ** Attachment added: "lp1766076-boot-dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856161/+attachment/5314569/+files/lp1766076-boot-dmesg.log -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Confirmed Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20
[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices
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/ubuntu/+source/linux/+bug/1856161/+attachment/5314567/+files/lp1766076-boot-dmesg-tbconnected.log -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Confirmed Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:
[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices
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/ubuntu/+source/linux/+bug/1856161/+attachment/5314568/+files/lp1766076-tb-reconnect-success.log -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Confirmed Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:
[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices
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 attached dmesg log of this process. All of my devices are on the cable connected to the back of the dock - anything else listed in the log before timestamp 342 is internal to the dock (i.e. the built-in hub, audio device and NIC). ** Attachment added: "lp1766076-tb-reconnect-without-usb-chain.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856161/+attachment/5314557/+files/lp1766076-tb-reconnect-without-usb-chain.log -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Confirmed Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId:
[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices
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/5314556/+files/lp1766076-tb-reconnect-fail-dmesg.log -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Confirmed Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics
[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices
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 running after the first boot), boot with the thunderbolt connected, xhci fails. I Attached dmesg log of that. ** Attachment added: "lp1766076-boot-dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856161/+attachment/5314555/+files/lp1766076-boot-dmesg.log -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Confirmed Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid:
[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices
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-1.6.2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 247.388288] usb 3-1.6.2.4: Product: USB Keyboard [ 247.388289] usb 3-1.6.2.4: Manufacturer: [ 247.454042] usb 3-1.6.5: new high-speed USB device number 10 using xhci_hcd [ 247.511444] input: USB Keyboard as /devices/pci:00/:00:1d.6/:06:00.0/:07:01.0/:09:00.0/:0a:04.0/:0c:00.0/:0d:01.0/:0e:00.0/usb3/3-1/3-1.6/3-1.6.2/3-1.6.2.4/3-1.6.2.4:1.0/0003:04D9:2013.0014/input/input44 [ 247.570426] hid-generic 0003:04D9:2013.0014: input,hidraw4: USB HID v1.00 Keyboard [ USB Keyboard] on usb-:0e:00.0-1.6.2.4/input0 [ 247.583572] input: USB Keyboard System Control as /devices/pci:00/:00:1d.6/:06:00.0/:07:01.0/:09:00.0/:0a:04.0/:0c:00.0/:0d:01.0/:0e:00.0/usb3/3-1/3-1.6/3-1.6.2/3-1.6.2.4/3-1.6.2.4:1.1/0003:04D9:2013.0015/input/input45 [ 247.613793] usb 3-1.6.5: New USB device found, idVendor=0424, idProduct=274c, bcdDevice= 2.00 [ 247.613796] usb 3-1.6.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 247.613797] usb 3-1.6.5: Product: Hub Controller [ 247.613799] usb 3-1.6.5: Manufacturer: Microchip Tech [ 247.642290] input: USB Keyboard Consumer Control as /devices/pci:00/:00:1d.6/:06:00.0/:07:01.0/:09:00.0/:0a:04.0/:0c:00.0/:0d:01.0/:0e:00.0/usb3/3-1/3-1.6/3-1.6.2/3-1.6.2.4/3-1.6.2.4:1.1/0003:04D9:2013.0015/input/input46 [ 247.642466] hid-generic 0003:04D9:2013.0015: input,hidraw5: USB HID v1.00 Device [ USB Keyboard] on usb-:0e:00.0-1.6.2.4/input1 [ 247.703468] hid-generic 0003:0424:274C.0016: hiddev2,hidraw6: USB HID v1.10 Device [Microchip Tech Hub Controller] on usb-:0e:00.0-1.6.5/input0 [ 249.085573] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13 [ 249.085576] xhci_hcd :0e:00.0: Looking for event-dma fffa2040 trb-start fffa2020 trb-end fffa2020 seg-start fffa2000 seg-end fffa2ff0 [ 249.086506] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13 [ 249.086509] xhci_hcd :0e:00.0: Looking for event-dma fffa2050 trb-start fffa2020 trb-end fffa2020 seg-start fffa2000 seg-end fffa2ff0 [ 249.087505] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13 [ 249.087509] xhci_hcd :0e:00.0: Looking for event-dma fffa2060 trb-start fffa2020 trb-end fffa2020 seg-start fffa2000 seg-end fffa2ff0 [ 249.088504] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13 [ 249.088506] xhci_hcd :0e:00.0: Looking for event-dma fffa2070 trb-start fffa2020 trb-end fffa2020 seg-start fffa2000 seg-end fffa2ff0 [ 249.089505] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13 [ 249.089506] xhci_hcd :0e:00.0: Looking for event-dma fffa2080 trb-start fffa2030 trb-end fffa2030 seg-start fffa2000 seg-end fffa2ff0 [ 249.090504] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13 [ 249.090507] xhci_hcd :0e:00.0: Looking for event-dma fffa2090 trb-start fffa2030 trb-end fffa2030 seg-start fffa2000 seg-end fffa2ff0 [ 249.091507] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13 [ 249.091511] xhci_hcd :0e:00.0: Looking for event-dma fffa20a0 trb-start fffa2030 trb-end fffa2030 seg-start fffa2000 seg-end fffa2ff0 [ 249.092507] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13 [ 249.092510] xhci_hcd :0e:00.0: Looking for event-dma fffa20b0 trb-start fffa2030 trb-end fffa2030 seg-start fffa2000 seg-end fffa2ff0 [ 249.093505] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13 [ 249.093509] xhci_hcd :0e:00.0: Looking for event-dma fffa20c0 trb-start fffa2030 trb-end fffa2030 seg-start fffa2000 seg-end fffa2ff0 [ 249.094507] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13 [ 249.094512] xhci_hcd :0e:00.0: Looking for event-dma fffa20d0 trb-start fffa2030 trb-end
[Kernel-packages] [Bug 1856161] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311958/+files/ProcEnviron.txt -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock
[Kernel-packages] [Bug 1856161] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311963/+files/UdevDb.txt -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock DeviceId:
[Kernel-packages] [Bug 1856161] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311960/+files/ProcModules.txt -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock
[Kernel-packages] [Bug 1856161] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311959/+files/ProcInterrupts.txt -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock
[Kernel-packages] [Bug 1856161] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311961/+files/PulseList.txt -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock DeviceId:
[Kernel-packages] [Bug 1856161] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311957/+files/ProcCpuinfoMinimal.txt -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired
[Kernel-packages] [Bug 1856161] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311956/+files/ProcCpuinfo.txt -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock
[Kernel-packages] [Bug 1856161] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311962/+files/RfKill.txt -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock DeviceId:
[Kernel-packages] [Bug 1856161] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311964/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => New -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12
[Kernel-packages] [Bug 1856161] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311954/+files/Lspci.txt -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock DeviceId:
[Kernel-packages] [Bug 1856161] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311951/+files/CRDA.txt -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock DeviceId:
[Kernel-packages] [Bug 1856161] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311953/+files/IwConfig.txt -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock DeviceId:
[Kernel-packages] [Bug 1856161] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311952/+files/CurrentDmesg.txt -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock
[Kernel-packages] [Bug 1856161] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311955/+files/Lsusb.txt -- 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock DeviceId:
[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices
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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock DeviceId: d83854e8c81f5d47b0b99c8a3b42ae5127c75eb8 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: c0f73159-4fc0-509b-80f8-5f871f3751a8 Guid: be025b25-ca5c-546c-97c6-ee2160ba489d Guid: 190e8d7c-6bcf-5fab-94e7-4f8739eb90aa Summary:
[Kernel-packages] [Bug 1856161] [NEW] Thunderbolt dock fails to connect USB devices
Public bug reported: 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 at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock DeviceId: d83854e8c81f5d47b0b99c8a3b42ae5127c75eb8 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: c0f73159-4fc0-509b-80f8-5f871f3751a8 Guid: be025b25-ca5c-546c-97c6-ee2160ba489d Guid: 190e8d7c-6bcf-5fab-94e7-4f8739eb90aa Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created:
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
The delay to connect the USB devices seems to be a feature of the new firmware or something - on MS-Windows it takes even longer, about 30 seconds for all the devices to finish connecting. Could it be that the xhci_hcd failure is caused by the fact that the dock is now so slow to respond? Anyway, that problem doesn't seem related to the "unknown event type 15" issue that this ticket is probably about, even though they both show "xHCI host not responding to stop endpoint command" - which is probably a symptom and not a cause. I'll be opening a new report for the thunderbolt connection issue. -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
I just went back to using my Precision 5520 with the TB16 dock, after that duo was benched for a few months while I waited for a replacement battery to be shipped, and now the situation is similar but worse: Every time I connect the dock cable, Linux tries to attached the USB hub, fails and disconnects the XHcI bus. Running the reset script details above (basically running "unbind" and the "bind" with the dock's bus address) allows the bus to be usable, though often it takes a couple of tries. Attached is the dmesg log from connection through the error and the reset (timepoint documented in the log itself). Interesting things that may or may not be related: 1. it takes a *very*long*time* for the system to connect the USB devices: the reset command occurred at 455, all the devices except the mouse got connected by 458 (13 seconds), with the mouse waiting until 471 (there were a few errors in the log specific to the logitech-hidpp-device, probably related). 2. I see a lot of `BAR 13: no space for [io size 0x]` in dmesg, followed by `BAR 13: failed to assign [io size 0x]`. I'm running eoan full updated with kernel 5.3.0-24-generic. I have ran all the BIOS firmware updates and the MS-Windows "Dell Precision Optimizer" system updates including the Thunderbolt controller driver update. Here's the fwupdmgr report: ``` Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-09 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-09 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-09 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(de646f75ada7857150e2c6263dc59b1e51b944a8) Checksum: SHA256(384c7594f033f64900148798be55939cdabfe502f8458febeb02884b920cf460) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-09 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-09 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock DeviceId: d83854e8c81f5d47b0b99c8a3b42ae5127c75eb8 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: c0f73159-4fc0-509b-80f8-5f871f3751a8 Guid: be025b25-ca5c-546c-97c6-ee2160ba489d Guid: 190e8d7c-6bcf-5fab-94e7-4f8739eb90aa Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-09 Dell TB16 Thunderbolt Cable DeviceId: f8194a42320518472a2e67c1d89018c7a5219841 ParentDeviceId:
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
My current complete workaround is documented here: https://gist.github.com/guss77/1356e5f3be4f2acbc73053cc6d3c0b1c -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
I haven't had that issue for a while, since kernel 4.20, I think, but I just had this issue again, on up to date 19.04 with kernel 5.0.0-13: [376539.800632] xhci_hcd :0e:00.0: ERROR unknown event type 15 [376544.914548] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [376544.914869] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [376544.914937] xhci_hcd :0e:00.0: HC died; cleaning up [376544.914941] usb 3-1.5: Failed to suspend device, error -22 [376544.914948] usb 4-1.1.1: Failed to suspend device, error -22 [376544.914956] usb 3-1: USB disconnect, device number 2 [376544.914957] usb 3-1.1: USB disconnect, device number 3 [376544.914958] usb 3-1.1.1: USB disconnect, device number 5 [376544.914959] usb 3-1.1.1.4: USB disconnect, device number 8 [376544.915173] usb 4-1: USB disconnect, device number 2 [376544.915174] usb 4-1.1: USB disconnect, device number 3 [376544.915175] usb 4-1.1.1: USB disconnect, device number 5 [376544.915595] usb 4-1.2: USB disconnect, device number 4 [376544.958908] usb 3-1.1.1.5: USB disconnect, device number 11 [376544.959744] usb 3-1.1.2: USB disconnect, device number 7 [376544.959746] usb 3-1.1.2.4: USB disconnect, device number 10 [376545.175240] usb 3-1.1.5: USB disconnect, device number 9 [376545.175890] usb 3-1.5: USB disconnect, device number 6 [376545.176578] usb 3-1.6: USB disconnect, device number 12 Then the USB hub died while DP over Thunderbolt monitors continue to work. Firmware versions: Precision M5520 Thunderbolt Controller: 26.01 Dell Thunderbolt Dock: 16.00 Precision 5520 System Firmware: 0.1.13.0 This has happened a few times already - as I was writing up this report - and I worked around them by either power cycling the dock (pulling the power cable - the power button on the dock powers down the laptop), or running the XHCI reset script I'm pasting below. Regarding other workarounds - at no point did I boot to MS-Windows (or at least not in the last half a year). This is the XHCI reset script I'm using - it lists XHCI devices and runs the unbind-rebind process specified in the original bug report. The next step would be a SystemD service that monitors the kernel log for the "xHCI assume dead" line and triggers the rebind automatically :-/ ``` #!/bin/bash tbtid="$(ls /sys/bus/pci/drivers/xhci_hcd/ | grep '[0-9]')" echo "Resetting thunderbolt bus">&2 for id in $tbtid; do echo -n $id > /sys/bus/pci/drivers/xhci_hcd/unbind done sleep 1 for id in $tbtid; do echo -n $id > /sys/bus/pci/drivers/xhci_hcd/bind done echo "Done resetting thunderbolt bus">&2 ``` -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset:
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
I've been running disco for a while with `generic` Ubuntu kernel 5.0.0 (currently 5.0.0-8), and I haven't experienced that problem for a while. I still get some USB issues from time to time with the Dell dock - where the USB does not connect when I plug the dock to the laptop, at which point I pull the TB plug out and connect it again and it is usually OK (sometimes it takes a couple of tries), but I no longer see "unknown event" errors and the USB no longer dies in the middle of a work day. I never booted into Windows at any point - neither for a firmware upgrade nor for the "reset workaround". I'm updating firmware using the BIOS update facility and I'm currently running Firmware version 1.12.0 which comes with TB controller firmware version 26.01. -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
BTW, I think this is a problem specifically with Dell custom thunderbolt docs - they do a bit more than straight forward TB3 docs, at the minimum they have overspeced power output to handle Precisions' huge power budget, but maybe they do more stuff? I also run my Precision with a standard TB3 dock with no bells and whistles and just a standard USB-PD 60W power - where I never have this problem. -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3:
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
Ah, in addition to the USB port, I'm also using: - 2 display ports (to the screens), though these continue to work even when xhci break. - The gigabit ethernet port - The audio out port I'm attaching the kernel log that includes the discovery of the dock during resume from suspend (minus a lot of noise, mostly from colord and kscreen). Hopefully it'll be useful - it has some failures which I don't understand. ** Attachment added: "test.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/+attachment/5210877/+files/test.log -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
I'm using the USB port at the back on the TB16, chained through a couple of Dell U2718Q to a Logitech unified receiver and a Das Keyboard (original) and a few USB cables that get attached to various Android and iOS devices from time to time, though most issues occur when no phone device is connected. For me, I can get by usually a week or two before I start experiencing problems, which once it starts the problem repeats itself through the day (where I have to reset the xhci module as described above, after which I have some minutes of usage), after which I disconnect the computer and go home and the problem usually does not repeat itself by the next day. If there are some tests you want me to run, I'm comfortable doing so up to and including building and running test kernels. Though regarding recurrence, here's a history of recurrences on my system for the last few months: Jul-22: 2 time(s) Jul-29: 17 time(s) Aug-02: 12 time(s) Aug-05: 4 time(s) Aug-07: 7 time(s) Aug-08: 6 time(s) Aug-22: 9 time(s) Aug-23: 11 time(s) Aug-30: 5 time(s) Sep-27: 16 time(s) Oct-02: 16 time(s) Oct-03: 6 time(s) Oct-11: 1 time(s) Oct-14: 5 time(s) Oct-15: 5 time(s) Oct-28: 2 time(s) Oct-29: 15 time(s) Nov-07: 11 time(s) So as you can see, it takes time to reproduce. -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
Just got hit with the problem again, after the 1.11.0 firmware upgrade, on Cosmic: [428188.916420] xhci_hcd :0e:00.0: ERROR unknown event type 15 [428193.955247] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [428193.955570] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [428193.955670] usb 3-1.5: Failed to suspend device, error -22 [428193.955707] xhci_hcd :0e:00.0: HC died; cleaning up [428193.955710] usb 4-1.1.1: Failed to suspend device, error -22 [428193.955768] usb 3-1: USB disconnect, device number 2 [428193.955770] usb 3-1.1: USB disconnect, device number 3 [428193.955773] usb 3-1.1.1: USB disconnect, device number 5 [428193.955776] usb 3-1.1.1.1: USB disconnect, device number 7 [428193.955779] usb 3-1.1.1.1.4: USB disconnect, device number 9 [428193.955923] usb 4-1: USB disconnect, device number 2 [428193.955926] usb 4-1.1: USB disconnect, device number 3 [428193.955927] usb 4-1.1.1: USB disconnect, device number 5 [428193.956974] usb 4-1.2: USB disconnect, device number 4 [428194.196633] usb 3-1.1.1.3: USB disconnect, device number 8 [428194.277991] usb 3-1.1.1.5: USB disconnect, device number 10 [428194.278531] usb 3-1.1.5: USB disconnect, device number 6 [428194.279067] usb 3-1.5: USB disconnect, device number 4 $ uname -a Linux vesho 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
On my system, the Precision 5520 is powered by the TB16 dock. I have updated the firmware to 1.11.0 a couple of days ago, and so far no crashes - though there have been stretches of weeks in the past without a crash. I'll update the next time it does stop working. -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
The last TB firmware was released 2018-04, and it is up to date (also according to fwupdmgr). -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
I had to downgrade the BIOS back to 1.10.1 (fwupdmgr installed 1.11) as under the new firmware suspend to RAM caused the system to completely power off (i.e. boot from scratch when powering on). I'll try to update again when the new update is released on Dell's website (the current version on the website is 1.10.1, so I can't even report an bug about the firmware update). But I doubt this issue will be resolved by a firmware update - as mentioned in my previous comment, this bug has survived numerous firmware update: the original bug report was using BIOS 1.7 and it still happens in 1.10.1. -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
Apparently there's a firmware update (I was running 1.10, which is about a month old - I've updated the firmware several times during the life time of this bug). I'll update and wait for it to happen again. BTW - the behavior is usually that after this disconnect happens once, I can reset the USB controller (using sysfs API to unbind and re-bind xhci_hcd), but then it will get the problem again and again, several times an hour (its not very predictable, sometimes I get 2 in a row and sometimes half an hour can pass before it breaks again). I thought this can be temperature related, so I pushed the computer to low power mode after the first event of the day, and reset the bus, but it happened again. -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
Just got the issue again with latest Bionic kernel (Precision 5520 + TB16): [253938.395439] xhci_hcd :0e:00.0: ERROR unknown event type 15 [253943.344375] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [253943.344704] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [253943.344865] xhci_hcd :0e:00.0: HC died; cleaning up [253943.344953] usb 3-1: USB disconnect, device number 2 [253943.344955] usb 3-1.1: USB disconnect, device number 3 [253943.344957] usb 3-1.1.1: USB disconnect, device number 6 [253943.344960] usb 3-1.1.1.1: USB disconnect, device number 8 [253943.344963] usb 3-1.1.1.1.4: USB disconnect, device number 10 [253943.345081] usb 4-1: USB disconnect, device number 2 [253943.345083] usb 4-1.1: USB disconnect, device number 3 [253943.345086] usb 4-1.1.1: USB disconnect, device number 5 [253943.346372] usb 4-1.2: USB disconnect, device number 4 [253943.489086] usb 3-1.1.1.3: USB disconnect, device number 13 [253943.556882] usb 3-1.1.1.5: USB disconnect, device number 12 [253943.557415] usb 3-1.1.2: USB disconnect, device number 11 [253943.557687] usb 3-1.1.5: USB disconnect, device number 7 [253943.558220] usb 3-1.3: USB disconnect, device number 4 [253943.558465] usb 3-1.5: USB disconnect, device number 5 uname: Linux vesho 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
Sorry, I missed the important line from the dmesg log. It should be: [72735.678702] xhci_hcd :0e:00.0: ERROR unknown event type 15 [72740.609531] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [72740.609850] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [72740.609882] usb 4-1.1.1: Failed to suspend device, error -22 [72740.609882] xhci_hcd :0e:00.0: HC died; cleaning up [72740.609926] usb 3-1: USB disconnect, device number 2 [72740.609930] usb 3-1.1: USB disconnect, device number 3 [72740.609932] usb 3-1.1.1: USB disconnect, device number 5 [72740.609935] usb 3-1.1.1.1: USB disconnect, device number 7 [72740.609938] usb 3-1.1.1.1.4: USB disconnect, device number 9 [72740.609994] usb 4-1: USB disconnect, device number 2 [72740.609996] usb 4-1.1: USB disconnect, device number 3 [72740.609997] usb 4-1.1.1: USB disconnect, device number 5 [72740.610718] usb 4-1.2: USB disconnect, device number 4 [72740.846065] usb 3-1.1.1.3: USB disconnect, device number 11 [72740.910812] usb 3-1.1.1.5: USB disconnect, device number 10 [72740.911322] usb 3-1.1.5: USB disconnect, device number 6 [72740.912038] usb 3-1.5: USB disconnect, device number 4 -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in linux package in Ubuntu: Expired Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
I've been running a few days now with the main line kernel 4.18.3 (from Ubuntu's main line kernel downloads), and I just got this again: [72740.609531] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [72740.609850] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [72740.609882] usb 4-1.1.1: Failed to suspend device, error -22 [72740.609882] xhci_hcd :0e:00.0: HC died; cleaning up [72740.609926] usb 3-1: USB disconnect, device number 2 [72740.609930] usb 3-1.1: USB disconnect, device number 3 [72740.609932] usb 3-1.1.1: USB disconnect, device number 5 [72740.609935] usb 3-1.1.1.1: USB disconnect, device number 7 [72740.609938] usb 3-1.1.1.1.4: USB disconnect, device number 9 [72740.609994] usb 4-1: USB disconnect, device number 2 [72740.609996] usb 4-1.1: USB disconnect, device number 3 [72740.609997] usb 4-1.1.1: USB disconnect, device number 5 [72740.610718] usb 4-1.2: USB disconnect, device number 4 [72740.846065] usb 3-1.1.1.3: USB disconnect, device number 11 [72740.910812] usb 3-1.1.1.5: USB disconnect, device number 10 [72740.911322] usb 3-1.1.5: USB disconnect, device number 6 [72740.912038] usb 3-1.5: USB disconnect, device number 4 I'll change to the latest Bionic kernel and let you know if I can repro that. -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in linux package in Ubuntu: Expired Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
I had this issue previously under Zesty and I think it was gone under Artful (though I'm not sure - the dock started having hardware issues at that point). I just upgraded to Bionic *and* got a new dock, and almost immediately started having these issues. I'll try the mainline build tomorrow. -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd
[Kernel-packages] [Bug 1766076] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1766076/+attachment/5125531/+files/RfKill.txt -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0
[Kernel-packages] [Bug 1766076] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1766076/+attachment/5125532/+files/UdevDb.txt -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0
[Kernel-packages] [Bug 1766076] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1766076/+attachment/5125530/+files/PulseList.txt -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0
[Kernel-packages] [Bug 1766076] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1766076/+attachment/5125533/+files/WifiSyslog.txt -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0
[Kernel-packages] [Bug 1766076] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1766076/+attachment/5125528/+files/ProcInterrupts.txt -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0
[Kernel-packages] [Bug 1766076] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1766076/+attachment/5125522/+files/CurrentDmesg.txt -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0
[Kernel-packages] [Bug 1766076] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1766076/+attachment/5125527/+files/ProcEnviron.txt -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0
[Kernel-packages] [Bug 1766076] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1766076/+attachment/5125524/+files/Lspci.txt -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0
[Kernel-packages] [Bug 1766076] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1766076/+attachment/5125521/+files/CRDA.txt -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0
[Kernel-packages] [Bug 1766076] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1766076/+attachment/5125526/+files/ProcCpuinfoMinimal.txt -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0
[Kernel-packages] [Bug 1766076] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1766076/+attachment/5125525/+files/ProcCpuinfo.txt -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0
[Kernel-packages] [Bug 1766076] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1766076/+attachment/5125523/+files/IwConfig.txt -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0
[Kernel-packages] [Bug 1766076] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1766076/+attachment/5125529/+files/ProcModules.txt -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
apport information ** Tags added: apport-collected ** Description changed: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0 [279389.950117] hub 3-0:1.0: USB hub found [279389.950135] hub 3-0:1.0: 2 ports detected
[Kernel-packages] [Bug 1766076] [NEW] USB over thunderbolt turns off every once in a while
Public bug reported: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0 [279389.950117] hub 3-0:1.0: USB hub found [279389.950135] hub 3-0:1.0: 2 ports detected [279389.950310] xhci_hcd :0e:00.0: xHCI Host Controller
[Kernel-packages] [Bug 1422283] Re: [Dell Inc. Latitude E5440] suspend/resume failure
This seems to be a firmware / hardware issue with Dell Laptops - the BIOS reports ASF2 force off events when these shutdown happens, which is a problem experienced by many other Dell customers, as can be seen here - http://en.community.dell.com/support- forums/laptop/f/3518/t/19612919 - and several other Dell community forum posts. I've closed this ticket as invalid. ** Changed in: linux (Ubuntu) Status: Incomplete = Invalid -- 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/1422283 Title: [Dell Inc. Latitude E5440] suspend/resume failure Status in linux package in Ubuntu: Invalid Bug description: After some time in sleep mode, the laptop turns off completely and the session lost with all program crashed. When the laptop starts again, I have to log in to a new session. This may be related to the fact that the laptop dual-boots Windows 8.1 pro that is configured to hybrid sleep (sleep for a pre-determined time than hibernate), though the length of time it takes to turn off does not seem constant - it may take an hour or several. ProblemType: KernelOops DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-13-generic 3.18.0-13.14 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: odeda 3163 F pulseaudio /dev/snd/controlC0: odeda 3163 F pulseaudio CRDA: country IL: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 40), (N/A, 23), (N/A), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 23), (0 ms), NO-OUTDOOR, DFS Date: Mon Feb 16 10:31:06 2015 DuplicateSignature: suspend/resume:Dell Inc. Latitude E5440:A06 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=24405171-f0ac-4b13-817a-068a95eb189c InstallationDate: Installed on 2015-01-09 (37 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150109) InterpreterPath: /usr/bin/python3.4 MachineType: Dell Inc. Latitude E5440 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-13-generic root=UUID=459f4711-4cd2-4fa9-a676-67ce56f74979 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.18.0-13-generic N/A linux-backports-modules-3.18.0-13-generic N/A linux-firmware 1.141 SourcePackage: linux Title: [Dell Inc. Latitude E5440] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 08RCYC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn08RCYC:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1422283/+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
[Kernel-packages] [Bug 1422283] Re: [Dell Inc. Latitude E5440] suspend/resume failure
I've tried running the mainline 3.19, and it exhibits the same problem - though when the system comes up after a failed sleep, the error reporter says that I can't report problems with mainline kernels and opens up the kernel bug tracker :-) -- 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/1422283 Title: [Dell Inc. Latitude E5440] suspend/resume failure Status in linux package in Ubuntu: Incomplete Bug description: After some time in sleep mode, the laptop turns off completely and the session lost with all program crashed. When the laptop starts again, I have to log in to a new session. This may be related to the fact that the laptop dual-boots Windows 8.1 pro that is configured to hybrid sleep (sleep for a pre-determined time than hibernate), though the length of time it takes to turn off does not seem constant - it may take an hour or several. ProblemType: KernelOops DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-13-generic 3.18.0-13.14 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: odeda 3163 F pulseaudio /dev/snd/controlC0: odeda 3163 F pulseaudio CRDA: country IL: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 40), (N/A, 23), (N/A), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 23), (0 ms), NO-OUTDOOR, DFS Date: Mon Feb 16 10:31:06 2015 DuplicateSignature: suspend/resume:Dell Inc. Latitude E5440:A06 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=24405171-f0ac-4b13-817a-068a95eb189c InstallationDate: Installed on 2015-01-09 (37 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150109) InterpreterPath: /usr/bin/python3.4 MachineType: Dell Inc. Latitude E5440 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-13-generic root=UUID=459f4711-4cd2-4fa9-a676-67ce56f74979 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.18.0-13-generic N/A linux-backports-modules-3.18.0-13-generic N/A linux-firmware 1.141 SourcePackage: linux Title: [Dell Inc. Latitude E5440] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 08RCYC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn08RCYC:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1422283/+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
[Kernel-packages] [Bug 1422283] [NEW] [Dell Inc. Latitude E5440] suspend/resume failure
Public bug reported: After some time in sleep mode, the laptop turns off completely and the session lost with all program crashed. When the laptop starts again, I have to log in to a new session. This may be related to the fact that the laptop dual-boots Windows 8.1 pro that is configured to hybrid sleep (sleep for a pre-determined time than hibernate), though the length of time it takes to turn off does not seem constant - it may take an hour or several. ProblemType: KernelOops DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-13-generic 3.18.0-13.14 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: odeda 3163 F pulseaudio /dev/snd/controlC0: odeda 3163 F pulseaudio CRDA: country IL: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 40), (N/A, 23), (N/A), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 23), (0 ms), NO-OUTDOOR, DFS Date: Mon Feb 16 10:31:06 2015 DuplicateSignature: suspend/resume:Dell Inc. Latitude E5440:A06 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=24405171-f0ac-4b13-817a-068a95eb189c InstallationDate: Installed on 2015-01-09 (37 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150109) InterpreterPath: /usr/bin/python3.4 MachineType: Dell Inc. Latitude E5440 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-13-generic root=UUID=459f4711-4cd2-4fa9-a676-67ce56f74979 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.18.0-13-generic N/A linux-backports-modules-3.18.0-13-generic N/A linux-firmware 1.141 SourcePackage: linux Title: [Dell Inc. Latitude E5440] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 08RCYC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn08RCYC:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops resume suspend vivid -- 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/1422283 Title: [Dell Inc. Latitude E5440] suspend/resume failure Status in linux package in Ubuntu: New Bug description: After some time in sleep mode, the laptop turns off completely and the session lost with all program crashed. When the laptop starts again, I have to log in to a new session. This may be related to the fact that the laptop dual-boots Windows 8.1 pro that is configured to hybrid sleep (sleep for a pre-determined time than hibernate), though the length of time it takes to turn off does not seem constant - it may take an hour or several. ProblemType: KernelOops DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-13-generic 3.18.0-13.14 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: odeda 3163 F pulseaudio /dev/snd/controlC0: odeda 3163 F pulseaudio CRDA: country IL: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 40), (N/A, 23), (N/A), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 23), (0 ms), NO-OUTDOOR, DFS Date: Mon Feb 16 10:31:06 2015 DuplicateSignature: suspend/resume:Dell Inc. Latitude E5440:A06 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=24405171-f0ac-4b13-817a-068a95eb189c InstallationDate: Installed on 2015-01-09 (37 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150109) InterpreterPath: /usr/bin/python3.4 MachineType: Dell Inc. Latitude E5440 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine:
