You are not logged in.
- Topics: Active | Unanswered
#1 2024-05-05 20:53:16
- GigaYoshi
- Member
- Registered: 2024-02-16
- Posts: 11
"xHCI host controller not responding, assume dead" after latest update
I just updated my Arch system via yay and after a reboot I see this message on boot: "xHCI host controller not responding, assume dead".
My Caldigit TS3 Plus Thunderbolt 3 dock, connected via USB 4 to my AMD PC, doesn't work anymore.
I restored a system backup via Clonezilla and everything is working, the backup is circa 20 days old. I'm pretty sure that some recent update is responsible for this, does anybody have any suggestion about how can I identify the responsible package and investigate the ploblem?
Offline
#2 2024-05-05 20:55:01
- loqs
- Member
- Registered: 2014-03-06
- Posts: 18,045
Re: "xHCI host controller not responding, assume dead" after latest update
What was in the last update? (Check /var/log/pacman.log)
Offline
#3 2024-05-05 20:59:27
- GigaYoshi
- Member
- Registered: 2024-02-16
- Posts: 11
Re: "xHCI host controller not responding, assume dead" after latest update
As I said I had to restore a 20 days old backup, so the list of available updates is quite long, I'm sorry about it:
224 core/archlinux-keyring 20240313-1 -> 20240429-1
223 core/audit 4.0.1-2 -> 4.0.1-3
222 core/binutils 2.42-2 -> 2.42-3
221 core/brotli 1.1.0-1 -> 1.1.0-2
220 core/btrfs-progs 6.8-2 -> 6.8.1-1
219 core/curl 8.7.1-5 -> 8.7.1-6
218 core/db5.3 5.3.28-4 -> 5.3.28-5
217 core/dbus-broker 36-1 -> 36-2
216 core/dbus-broker-units 36-1 -> 36-2
215 core/gcc 13.2.1-5 -> 13.2.1-6
214 core/gcc-libs 13.2.1-5 -> 13.2.1-6
213 core/glib2 2.80.0-2 -> 2.80.0-4
212 core/glib2-docs 2.80.0-2 -> 2.80.0-4
211 core/glibc 2.39-1 -> 2.39-4
210 core/gpgme 1.23.2-1 -> 1.23.2-4
209 core/hwdata 0.381-1 -> 0.382-1
208 core/iproute2 6.8.0-1 -> 6.8.0-2
207 core/jansson 2.14-3 -> 2.14-4
206 core/libarchive 3.7.3-1 -> 3.7.4-1
205 core/libcap-ng 0.8.5-1 -> 0.8.5-2
204 core/libelf 0.191-1 -> 0.191-2
203 core/libgpg-error 1.48-1 -> 1.49-1
202 core/libisl 0.26-1 -> 0.26-2
201 core/libldap 2.6.7-1 -> 2.6.7-2
200 core/libpsl 0.21.2-1 -> 0.21.5-1
199 core/libseccomp 2.5.5-2 -> 2.5.5-3
198 core/libxml2 2.12.6-1 -> 2.12.6-2
197 core/linux 6.8.7.arch1-1 -> 6.8.9.arch1-1
196 core/minizip 1:1.3.1-1 -> 1:1.3.1-2
195 core/mkinitcpio 38.1-1 -> 39-1
194 core/nano 7.2-1 -> 8.0-1
193 core/ncurses 6.4_20230520-1 -> 6.4_20230520-3
192 core/openssh 9.7p1-1 -> 9.7p1-2
191 core/openssl 3.2.1-1 -> 3.3.0-1
190 core/pcre2 10.43-3 -> 10.43-4
189 core/python 3.11.8-1 -> 3.12.3-1
188 core/systemd 255.4-2 -> 255.5-4
187 core/systemd-libs 255.4-2 -> 255.5-4
186 core/systemd-sysvcompat 255.4-2 -> 255.5-4
185 core/tzdata 2024a-1 -> 2024a-2
184 core/util-linux 2.40-2 -> 2.40-3
183 core/util-linux-libs 2.40-2 -> 2.40-3
182 core/zlib 1:1.3.1-1 -> 1:1.3.1-2
181 extra/abseil-cpp 20240116.1-1 -> 20240116.2-1
180 extra/accountsservice 23.13.9-1 -> 23.13.9-2
179 extra/aom 3.8.2-1 -> 3.9.0-1
178 extra/apache 2.4.58-1 -> 2.4.59-1
177 extra/appstream 1.0.2-1 -> 1.0.3-1
176 extra/avahi 1:0.8+r194+g3f79789-1 -> 1:0.8+r194+g3f79789-2
175 extra/barrier 2.4.0-2 -> 2.4.0-3
174 extra/barrier-headless 2.4.0-2 -> 2.4.0-3
173 extra/bolt 0.9.7-1 -> 0.9.7-2
172 extra/brltty 6.6-6 -> 6.6-7
171 extra/cups 1:2.4.7-2 -> 1:2.4.8-1
170 extra/dbus-python 1.3.2-2 -> 1.3.2-3
169 extra/ell 0.64-2 -> 0.65-1
168 extra/evince 46.0-1 -> 46.1-1
167 extra/evolution-data-server 3.52.0-2 -> 3.52.1-1
166 extra/exiv2 0.28.2-3 -> 0.28.2-4
165 extra/fftw 3.3.10-6 -> 3.3.10-7
164 extra/flatpak 1:1.15.7-1 -> 1:1.15.8-1
163 extra/freerdp 2:3.5.0-1 -> 2:3.5.1-1
162 extra/fribidi 1.0.13-2 -> 1.0.14-1
161 extra/gdk-pixbuf2 2.42.10-2 -> 2.42.11-2
160 extra/git 2.44.0-1 -> 2.45.0-1
159 extra/glslang 14.0.0-2 -> 14.1.0-1
158 extra/gnome-calendar 46.0-2 -> 46.1-2
157 extra/gnome-color-manager 3.36.0+r51+gcf7ee2b5-1 -> 3.36.0+r62+g82000f1d-1
156 extra/gnome-connections 46.0-2 -> 46.0-3
155 extra/gnome-control-center 46.0.1-2 -> 46.1-2
154 extra/gnome-maps 46.0-1 -> 46.10-1
153 extra/gnome-music 1:46.0-1 -> 1:46.0-2
152 extra/gnome-shell 1:46.0-1 -> 1:46.1-1
151 extra/gnome-shell-extension-appindicator 1:57-3 -> 1:58-1
150 extra/gnome-shell-extensions 46.0-1 -> 46.1-1
149 extra/gnome-software 46.0-1 -> 46.1-1
148 extra/gnome-terminal 3.52.0-1 -> 3.52.1-1
147 extra/gnome-tweaks 46.0-2 -> 46.1-1
146 extra/gnome-user-docs 46.0-1 -> 46.1-1
145 extra/gobject-introspection-runtime 1.80.1-1 -> 1.80.1-3
144 extra/gom 0.4-7 -> 0.5.1-1
143 extra/graphviz 10.0.1-1 -> 11.0.0-1
142 extra/gst-editing-services 1.24.1-2 -> 1.24.3-1
141 extra/gst-plugin-gtk 1.24.1-2 -> 1.24.3-1
140 extra/gst-plugins-bad 1.24.1-2 -> 1.24.3-1
139 extra/gst-plugins-bad-libs 1.24.1-2 -> 1.24.3-1
138 extra/gst-plugins-base 1.24.1-2 -> 1.24.3-1
137 extra/gst-plugins-base-libs 1.24.1-2 -> 1.24.3-1
136 extra/gst-plugins-good 1.24.1-2 -> 1.24.3-1
135 extra/gstreamer 1.24.1-2 -> 1.24.3-1
134 extra/gtk-update-icon-cache 1:4.14.2-1 -> 1:4.14.4-1
133 extra/gtk4 1:4.14.2-1 -> 1:4.14.4-1
132 extra/harfbuzz 8.4.0-1 -> 8.4.0-2
131 extra/harfbuzz-icu 8.4.0-1 -> 8.4.0-2
130 extra/htop 3.3.0-1 -> 3.3.0-2
129 extra/imagemagick 7.1.1.30-2 -> 7.1.1.32-1
128 extra/imath 3.1.11-1 -> 3.1.11-2
127 extra/js115 115.9.0-1 -> 115.10.0-1
126 extra/kodi 21.0-1 -> 21.0-4
125 extra/ldb 2:2.9.0-2 -> 2:2.9.0-3
124 extra/libavif 1.0.4-2 -> 1.0.4-3
123 extra/libblockdev 3.1.1-1 -> 3.1.1-2
122 extra/libblockdev-crypto 3.1.1-1 -> 3.1.1-2
121 extra/libblockdev-fs 3.1.1-1 -> 3.1.1-2
120 extra/libblockdev-loop 3.1.1-1 -> 3.1.1-2
119 extra/libblockdev-mdraid 3.1.1-1 -> 3.1.1-2
118 extra/libblockdev-nvme 3.1.1-1 -> 3.1.1-2
117 extra/libblockdev-part 3.1.1-1 -> 3.1.1-2
116 extra/libblockdev-swap 3.1.1-1 -> 3.1.1-2
115 extra/libbsd 0.12.2-1 -> 0.12.2-2
114 extra/libbytesize 2.8-2 -> 2.8-3
113 extra/libcaca 0.99.beta20-2 -> 0.99.beta20-4
112 extra/libcec 6.0.2-4 -> 6.0.2-5
111 extra/libcups 1:2.4.7-2 -> 1:2.4.8-1
110 extra/libedataserverui4 3.52.0-2 -> 3.52.1-1
109 extra/libftdi 1.5-5 -> 1.5-6
108 extra/libgexiv2 0.14.2-1 -> 0.14.2-2
107 extra/libgirepository 1.80.1-1 -> 1.80.1-3
106 extra/libgtop 2.41.3-1 -> 2.41.3-2
105 extra/libgusb 0.4.8-1 -> 0.4.8-2
104 extra/libibus 1.5.29-4 -> 1.5.30-1
103 extra/libieee1284 0.2.11-15 -> 0.2.11-16
102 extra/libimobiledevice 1.3.0-11 -> 1.3.0-13
101 extra/libiptcdata 1.0.5-2 -> 1.0.5-3
100 extra/liblc3 1.1.0-1 -> 1.1.1-1
99 extra/liblouis 3.29.0-1 -> 3.29.0-3
98 extra/libnautilus-extension 46.0-1 -> 46.1-1
97 extra/libnewt 0.52.24-1 -> 0.52.24-2
96 extra/libnvme 1.8-1 -> 1.8-2
95 extra/libosinfo 1.11.0-1 -> 1.11.0-2
94 extra/libpeas 1.36.0-4 -> 1.36.0-5
93 extra/libplacebo 6.338.2-4 -> 6.338.2-6
92 extra/libplist 2.4.0-1 -> 2.5.0-1
91 extra/libproxy 0.5.5-1 -> 0.5.6-1
90 extra/libpwquality 1.4.5-3 -> 1.4.5-5
89 extra/libshumate 1.2.0-1 -> 1.2.1-1
88 extra/libspeechd 0.11.5-1 -> 0.11.5-2
87 extra/libsysprof-capture 46.0-1 -> 46.0-2
86 extra/liburing 2.5-1 -> 2.6-1
85 extra/libvpl 2.10.2-1 -> 2.11.0-1
84 extra/libwbclient 4.20.0-2 -> 4.20.0-3
83 extra/libwireplumber 0.5.1-2 -> 0.5.2-1
82 extra/libxmlb 0.3.18-1 -> 0.3.19-1
81 extra/libxslt 1.1.39-1 -> 1.1.39-2
80 extra/lilv 0.24.24-1 -> 0.24.24-2
79 extra/lirc 1:0.10.2-3 -> 1:0.10.2-4
78 extra/llvm-libs 17.0.6-2 -> 17.0.6-4
77 extra/mesa 1:24.0.5-1 -> 1:24.0.6-2
76 extra/meson 1.4.0-2 -> 1.4.0-5
75 extra/mobile-broadband-provider-info 20230416-1 -> 20240407-1
74 extra/mpg123 1.32.5-1 -> 1.32.6-1
73 extra/mutter 46.0-3 -> 46.1-1
72 extra/nautilus 46.0-1 -> 46.1-1
71 extra/net-snmp 5.9.4-2 -> 5.9.4-3
70 extra/nextcloud-client 2:3.12.3-2 -> 2:3.13.0-2
69 extra/ninja 1.11.1-3 -> 1.12.0-2
68 extra/orca 46.1-1 -> 46.1-2
67 extra/patchelf 0.18.0-2 -> 0.18.0-3
66 extra/pcsclite 2.1.0-2 -> 2.2.0-1
65 extra/protobuf 25.3-3 -> 25.3-4
64 extra/python-autocommand 2.2.2-4 -> 2.2.2-6
63 extra/python-cairo 1.26.0-1 -> 1.26.0-2
62 extra/python-evdev 1.7.0-2 -> 1.7.0-3
61 extra/python-fastjsonschema 2.19.1-1 -> 2.19.1-3
60 extra/python-gobject 3.48.1-2 -> 3.48.2-1
59 extra/python-inflect 7.2.0-1 -> 7.2.1-2
58 extra/python-jaraco.context 4.3.0-3 -> 4.3.0-4
57 extra/python-jaraco.functools 4.0.0-1 -> 4.0.1-1
56 extra/python-jaraco.text 3.12.0-1 -> 3.12.0-3
55 extra/python-lxml 5.1.0-1 -> 5.1.0-3
54 extra/python-more-itertools 10.2.0-1 -> 10.2.0-2
53 extra/python-ordered-set 4.1.0-4 -> 4.1.0-5
52 extra/python-packaging 23.2-1 -> 23.2-3
51 extra/python-pillow 10.2.0-2 -> 10.3.0-2
50 extra/python-platformdirs 4.2.0-1 -> 4.2.0-3
49 extra/python-psutil 5.9.8-1 -> 5.9.8-4
48 extra/python-pycryptodomex 3.12.0-2 -> 3.12.0-3
47 extra/python-pygments 2.17.2-1 -> 2.17.2-3
46 extra/python-pyudev 0.24.1-2 -> 0.24.1-4
45 extra/python-pyxdg 0.28-2 -> 0.28-3
44 extra/python-setproctitle 1.3.3-1 -> 1.3.3-2
43 extra/python-setuptools 1:69.0.3-4 -> 1:69.0.3-6
42 extra/python-simplejson 3.19.2-2 -> 3.19.2-4
41 extra/python-six 1.16.0-8 -> 1.16.0-9
40 extra/python-tomli 2.0.1-3 -> 2.0.1-4
39 extra/python-tqdm 4.66.2-1 -> 4.66.4-1
38 extra/python-trove-classifiers 2024.3.25-1 -> 2024.4.10-1
37 extra/python-typeguard 4.2.1-1 -> 4.2.1-2
36 extra/python-typing_extensions 4.10.0-1 -> 4.11.0-1
35 extra/python-validate-pyproject 0.13-1 -> 0.16-1
34 extra/python-xlib 0.33-2 -> 0.33-3
33 extra/python-yaml 6.0.1-2 -> 6.0.1-3
32 extra/qtkeychain-qt5 0.14.2-1 -> 0.14.3-1
31 extra/rsync 3.3.0-1 -> 3.3.0-2
30 extra/sdl2 2.30.2-1 -> 2.30.3-1
29 extra/shaderc 2023.8-1 -> 2024.0-1
28 extra/smbclient 4.20.0-2 -> 4.20.0-3
27 extra/solaar 1.1.11-4 -> 1.1.12-1
26 extra/spdlog 1.13.0-1 -> 1.14.1-1
25 extra/speech-dispatcher 0.11.5-1 -> 0.11.5-2
24 extra/spirv-tools 2023.6-1 -> 2024.1-1
23 extra/talloc 2.4.2-1 -> 2.4.2-2
22 extra/tdb 1.4.10-2 -> 1.4.10-3
21 extra/tevent 1:0.16.1-2 -> 1:0.16.1-3
20 extra/tracker3 3.7.1-2 -> 3.7.3-1
19 extra/tracker3-miners 3.7.1-2 -> 3.7.3-1
18 extra/vala 0.56.16-1 -> 0.56.17-1
17 extra/vapoursynth R66-1 -> R66-2
16 extra/vim 9.1.0252-1 -> 9.1.0380-1
15 extra/vim-runtime 9.1.0252-1 -> 9.1.0380-1
14 extra/volume_key 0.3.12-8 -> 0.3.12-9
13 extra/vte-common 0.76.0-2 -> 0.76.1-1
12 extra/vte3 0.76.0-2 -> 0.76.1-1
11 extra/wget 1.24.5-1 -> 1.24.5-2
10 extra/wildmidi 0.4.5-2 -> 0.4.6-1
9 extra/wireplumber 0.5.1-2 -> 0.5.2-1
8 extra/xcb-proto 1.17.0-1 -> 1.17.0-2
7 extra/xdg-desktop-portal 1.18.3-1 -> 1.18.4-1
6 extra/xdg-desktop-portal-gnome 46.0-1 -> 46.1-1
5 extra/xdg-desktop-portal-gtk 1.15.1-1 -> 1.15.1-2
4 extra/xorg-xwayland 23.2.6-1 -> 23.2.6-2
3 extra/zbarLast edited by GigaYoshi (2024-05-05 21:09:52)
Offline
#4 2024-05-05 21:06:16
- loqs
- Member
- Registered: 2014-03-06
- Posts: 18,045
Re: "xHCI host controller not responding, assume dead" after latest update
197 core/linux 6.8.7.arch1-1 -> 6.8.9.arch1-1If you update just the kernel does the issue return? Please use code tags
Offline
#5 2024-05-05 21:17:35
- GigaYoshi
- Member
- Registered: 2024-02-16
- Posts: 11
Re: "xHCI host controller not responding, assume dead" after latest update
This is what happens when I only update the kernel, could this warning:
==> WARNING: Possibly missing firmware for module: 'xhci_pci'be connected to my issue? I'm rebooting the system and I may loose my mouse and keyboard, that's why I'm replying before trying. I'll report back immediately, thank you very much for your help.
[xxxxxxxxxxxxxxxx ~]$ sudo pacman -S linux
[sudo] password for xxxxxxxxx:
resolving dependencies...
looking for conflicting packages...
Packages (1) linux-6.8.9.arch1-1
Total Download Size: 132.27 MiB
Total Installed Size: 132.52 MiB
Net Upgrade Size: 0.11 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages...
linux-6.8.9.arch1-1-x86_64 132.3 MiB 63.6 MiB/s 00:02 [########################################] 100%
(1/1) checking keys in keyring [########################################] 100%
(1/1) checking package integrity [########################################] 100%
(1/1) loading package files [########################################] 100%
(1/1) checking for file conflicts [########################################] 100%
(1/1) checking available disk space [########################################] 100%
:: Running pre-transaction hooks...
(1/1) Removing linux initcpios...
:: Processing package changes...
(1/1) upgrading linux [########################################] 100%
:: Running post-transaction hooks...
(1/3) Arming ConditionNeedsUpdate...
(2/3) Updating module dependencies...
(3/3) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img
==> Starting build: '6.8.9-arch1-1'
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
-> Running build hook: [keymap]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: '6.8.9-arch1-1'
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
-> Running build hook: [keymap]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'bfa'
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
==> Initcpio image generation successfulOffline
#6 2024-05-05 21:21:28
- loqs
- Member
- Registered: 2014-03-06
- Posts: 18,045
Re: "xHCI host controller not responding, assume dead" after latest update
GigaYoshi wrote:
This is what happens when I only update the kernel, could this warning:
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
That warning is expected and you should be able to find it in pacman.log for previous kernel updates.
Offline
#7 2024-05-05 21:31:51
- GigaYoshi
- Member
- Registered: 2024-02-16
- Posts: 11
Re: "xHCI host controller not responding, assume dead" after latest update
You were right! It is the kernel update that's responsible for my problem! I guess I should try to exclude it from updating and I should wait for a future update, right?
Offline
#8 2024-05-05 21:37:25
- loqs
- Member
- Registered: 2014-03-06
- Posts: 18,045
Re: "xHCI host controller not responding, assume dead" after latest update
Please try 6.8.8 from the ALA
# pacman -U https://archive.archlinux.org/packages/l/linux/linux-6.8.8.arch1-1-x86_64.pkg.tar.zstOffline
#9 2024-05-05 22:12:12
- GigaYoshi
- Member
- Registered: 2024-02-16
- Posts: 11
Re: "xHCI host controller not responding, assume dead" after latest update
I run into the same issue with kernel 6.8.8, so for me the last working kernel is 6.8.7.
I wanted to report this bug in the Arch Gitlab, but I see that due to spam issues it is not currently possible to create an account.
Offline
#10 2024-05-05 23:36:01
- loqs
- Member
- Registered: 2014-03-06
- Posts: 18,045
Re: "xHCI host controller not responding, assume dead" after latest update
$ git bisect start
status: waiting for both good and bad commits
$ git bisect bad v6.8.8
status: waiting for good commit(s), bad commit known
$ git bisect good v6.8.7
Bisecting: 79 revisions left to test after this (roughly 6 steps)
[115554862294397590088ba02f11f2aba6d5016c] clk: Get runtime PM before walking tree during disable_unused
$ git describe
v6.8.7-80-g115554862294The folder Linux bisection 6.8.6 to 6.8.7 contains 6.8.7 built with 6.8.8's config this should be good and linux-6.8.7.r80.g115554862294-1-x86_64.pkg.tar.zst the first bisection kernel to test.
Last edited by loqs (2024-05-05 23:40:26)
Offline
#11 2024-05-06 12:31:27
- GigaYoshi
- Member
- Registered: 2024-02-16
- Posts: 11
Re: "xHCI host controller not responding, assume dead" after latest update
I'm not familiar with bisection, I'll try to document myself and report back.
I was able to report the bug on Gitlab and I was told that this looks like an upstream regression in the linux kernel.
My issue looks very similat to this one: https://lore.kernel.org/lkml/wL3vtEh_zT … icha.zone/
Offline
#12 2024-05-06 14:02:29
- loqs
- Member
- Registered: 2014-03-06
- Posts: 18,045
Re: "xHCI host controller not responding, assume dead" after latest update
6.8.9-arch1 with https://git.kernel.org/pub/scm/linux/ke … a91b568735 applied:
https://drive.google.com/file/d/1gHMeLA … sp=sharing linux-6.8.9.arch1-1.2-x86_64.pkg.tar.zst
https://drive.google.com/file/d/1YcIOMv … sp=sharing linux-headers-6.8.9.arch1-1.2-x86_64.pkg.tar.zst
If that does not fix the issue you will probably have to perform the bisection.
Offline
#13 2024-05-20 09:24:42
- GigaYoshi
- Member
- Registered: 2024-02-16
- Posts: 11
Re: "xHCI host controller not responding, assume dead" after latest update
My thunderbolt dock is now working with the latest 6.9.1 kernel if I use the kernel parameter thunderbolt.host_reset=false
Offline
#14 2024-05-20 13:38:35
- bboehmke
- Member
- Registered: 2024-05-20
- Posts: 3
Re: "xHCI host controller not responding, assume dead" after latest update
I have a very similar issue with a CalDigit USB-C Pro Dock (Thunderbolt 3).
In my case the kernel after 6.8.7 cause my second external monitor to be disconnected.
I was able to identify the first bad commit (via bisecting) as
thunderbolt: Reset topology created by the boot firmware (cc4c94a5f6c4dc86b784fee463ef0ada46592925)
Sadly I don't have an account for the issue tracker, otherwise I would add this information there too.
Let me know if I can do anything else to help fixing this issue.
BTW: the parameter thunderbolt.host_reset=false does also solve the issue on my end
Offline
#15 2024-05-20 13:55:00
- gromit
- Package Maintainer (PM)
- From: Germany
- Registered: 2024-02-10
- Posts: 663
- Website
Re: "xHCI host controller not responding, assume dead" after latest update
@bboehmke, good job on the bisection! I was about to get started with the reporter in https://gitlab.archlinux.org/archlinux/ … ote_186702 aswell 
Do you want to put togehther a report to the linux-kernel regressions list or should I report it on your behalf?
Offline
#16 2024-05-20 14:03:09
- loqs
- Member
- Registered: 2014-03-06
- Posts: 18,045
Re: "xHCI host controller not responding, assume dead" after latest update
Bisection results:
$ git bisect good
cc4c94a5f6c4dc86b784fee463ef0ada46592925 is the first bad commit
commit cc4c94a5f6c4dc86b784fee463ef0ada46592925
Author: Sanath S <Sanath.S@amd.com>
Date: Sat Jan 13 11:52:48 2024 +0200
thunderbolt: Reset topology created by the boot firmware
commit 59a54c5f3dbde00b8ad30aef27fe35b1fe07bf5c upstream.
Boot firmware (typically BIOS) might have created tunnels of its own.
The tunnel configuration that it does might be sub-optimal. For instance
it may only support HBR2 monitors so the DisplayPort tunnels it created
may limit Linux graphics drivers. In addition there is an issue on some
AMD based systems where the BIOS does not allocate enough PCIe resources
for future topology extension. By resetting the USB4 topology the PCIe
links will be reset as well allowing Linux to re-allocate.
This aligns the behavior with Windows Connection Manager.
We already issued host router reset for USB4 v2 routers, now extend it
to USB4 v1 routers as well. For pre-USB4 (that's Apple systems) we leave
it as is and continue to discover the existing tunnels.
Suggested-by: Mario Limonciello <mario.limonciello@amd.com>
Signed-off-by: Sanath S <Sanath.S@amd.com>
Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/thunderbolt/domain.c | 5 +++--
drivers/thunderbolt/icm.c | 2 +-
drivers/thunderbolt/nhi.c | 19 +++++++++++++------
drivers/thunderbolt/tb.c | 26 +++++++++++++++++++-------
drivers/thunderbolt/tb.h | 4 ++--
5 files changed, 38 insertions(+), 18 deletions(-)$ git bisect log
git bisect start
# status: waiting for both good and bad commits
# good: [12dadc409c2bd8538c6ee0e56e191efde6d92007] Linux 6.8.7
git bisect good 12dadc409c2bd8538c6ee0e56e191efde6d92007
# bad: [9fbb5fcb41e7e96fb8769a9f5a12a35a984c23bd] Linux 6.8.8
git bisect bad 9fbb5fcb41e7e96fb8769a9f5a12a35a984c23bd
# bad: [115554862294397590088ba02f11f2aba6d5016c] clk: Get runtime PM before walking tree during disable_unused
git bisect bad 115554862294397590088ba02f11f2aba6d5016c
# good: [52854101180beccdb9dc2077a3bea31b6ad48dfa] tun: limit printing rate when illegal packet received by tun dev
git bisect good 52854101180beccdb9dc2077a3bea31b6ad48dfa
# good: [dc69cd17aef2dfd639fcef571574e3f4ad976212] s390/qdio: handle deferred cc1
git bisect good dc69cd17aef2dfd639fcef571574e3f4ad976212
# bad: [cc4c94a5f6c4dc86b784fee463ef0ada46592925] thunderbolt: Reset topology created by the boot firmware
git bisect bad cc4c94a5f6c4dc86b784fee463ef0ada46592925
# good: [6bf32da0e288008bbee72036ebf2c68b9f66bc1e] drm/v3d: Don't increment `enabled_ns` twice
git bisect good 6bf32da0e288008bbee72036ebf2c68b9f66bc1e
# good: [ddab682b1a52426ccc0de70d9061920454aa385a] thunderbolt: Introduce tb_port_reset()
git bisect good ddab682b1a52426ccc0de70d9061920454aa385a
# good: [11371caa92dbb6cfcc1fa3658c7e523a748b9b00] thunderbolt: Make tb_switch_reset() support Thunderbolt 2, 3 and USB4 routers
git bisect good 11371caa92dbb6cfcc1fa3658c7e523a748b9b00
# first bad commit: [cc4c94a5f6c4dc86b784fee463ef0ada46592925] thunderbolt: Reset topology created by the boot firmwareOffline
#17 2024-05-20 14:08:27
- bboehmke
- Member
- Registered: 2024-05-20
- Posts: 3
Re: "xHCI host controller not responding, assume dead" after latest update
@gromit
Yeah it would be great if you can put the report together as this is the first time I am involved in such kind of troubleshooting.
For sure if I will try my best to support.
Offline
#18 2024-05-20 14:29:32
- loqs
- Member
- Registered: 2014-03-06
- Posts: 18,045
Re: "xHCI host controller not responding, assume dead" after latest update
@bboehmke upstream would also like some logs:
https://lore.kernel.org/lkml/9659dd5d-a … 7@amd.com/
Mario Limonciello wrote:
Can we please get some kernel logs for these two cases on the command line?
thunderbolt.dyndbg=+p
thunderbolt.dyndbg=+p thunderbolt.host_reset=falseAlso what is the value for:
$ cat /sys/bus/thunderbolt/devices/domain0/iommu_dma_protection
That won't change in the two cases, but it will be really helpful to
understand this issue.
Offline
#19 2024-05-20 14:35:40
- bboehmke
- Member
- Registered: 2024-05-20
- Posts: 3
Re: "xHCI host controller not responding, assume dead" after latest update
yeah I can try to collect some logs.
Is there a preferred kernel version I should use? 6.9.1 or 6.8.8?
Should I put the logs to the the open issue in archlinux issue tracker?
Offline
#20 2024-05-20 14:40:34
- gromit
- Package Maintainer (PM)
- From: Germany
- Registered: 2024-02-10
- Posts: 663
- Website
Re: "xHCI host controller not responding, assume dead" after latest update
Generally I'd say the closer to upstream the better, so feel free to use 6.9.1 for further debugging.
Feel free to put the logs either in the issue tracker or to the mail thread I've CC'ed you in.
Offline