Version-Release number of selected component: bolt-0.9.1-2.fc34 Additional info: reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/system.slice/bolt.service cmdline: /usr/libexec/boltd crash_function: __strlen_avx2 executable: /usr/libexec/boltd journald_cursor: s=6d9c0fa9b8b441d6a5b2681b3dbc3ff2;i=9776;b=efdbe3c70ed74318a34503c82d05feed;m=56c88e;t=5c62100ed2bed;x=4f45ba0291444a2f kernel: 5.13.0-58.fc35.x86_64 rootdir: / runlevel: unknown type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 __strlen_avx2 at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 #1 g_strdup at ../glib/gstrfuncs.c:363 #2 value_collect_string at ../gobject/gvaluetypes.c:293 #3 g_object_set_valist at ../gobject/gobject.c:2454 #4 g_object_set at ../gobject/gobject.c:2635 #5 bolt_device_connected at ../boltd/bolt-device.c:1330 #6 handle_udev_device_attached at ../boltd/bolt-manager.c:1971 #7 handle_udev_device_event at ../boltd/bolt-manager.c:1845 #8 bolt_manager_initialize at ../boltd/bolt-manager.c:579 #9 g_initable_new_valist at ../gio/ginitable.c:248
Created attachment 1798870 [details] File: backtrace
Created attachment 1798871 [details] File: core_backtrace
Created attachment 1798872 [details] File: cpuinfo
Created attachment 1798873 [details] File: dso_list
Created attachment 1798874 [details] File: environ
Created attachment 1798875 [details] File: exploitable
Created attachment 1798876 [details] File: limits
Created attachment 1798877 [details] File: maps
Created attachment 1798878 [details] File: mountinfo
Created attachment 1798879 [details] File: open_fds
Created attachment 1798880 [details] File: proc_pid_status
Created attachment 1798881 [details] File: var_log_messages
I'm also seeing this, using a Caldigit thunderbolt dock with my XPS 13 9360.
*** Bug 1983248 has been marked as a duplicate of this bug. ***
I think I see the problem why it is crashing but the underlying problem is that apparently the host does not have an `authorized` attribute: Jul 02 19:58:55 localhost.localdomain boltd[993]: [d4030000-0090-ThinkPad X1 Yoga ] udev: failed to get device info: could not read 'authorized': No such file or directory Mika, I was under the assumption that we would always have that attribute for all devices. Did that change?
It got changed with 6f3badead6a078cf3c71f381f9d84ac922984a00 ("thunderbolt: Hide authorized attribute if router does not support PCIe tunnels"). Is bolt relying that it exists with all devices? In that case I need to queue revert.
I posted a revert here: https://lore.kernel.org/linux-usb/20210727142501.27476-1-mika.westerberg@linux.intel.com/ please check if that fixes the issue.
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle. Changing version to 35.
(In reply to Mika Westerberg from comment #17) > I posted a revert here: > https://lore.kernel.org/linux-usb/20210727142501.27476-1-mika. > westerberg.com/ please check if that fixes the issue. This revert has made it into the 5.13.10 kernel, which is available in updates-testing now. So if you are seeing this bug, please run: "sudo dnf update --enablerepo=updates-testing 'kernel*'", reboot into the new kernel and then let us know if the problem is fixed.
I also fixed the crash in bolt that was the result of an uninitialised variable which in turn got triggered by that kernel change (fix upstream as MR !245). I will cut a bolt release soon (0.9.2) but since meson 0.59.0 is broken (bug 1994006) I cannot get bolt into Fedora until this is fixed.
(In reply to Hans de Goede from comment #19) I have updated to that kernel yesterday with worries, but so far it was without crashes (but I have not replugged my LP into dock yet (isn't it replugging dock into LP these days? :D) and that was problematic recently, not sure if related or not).
(In reply to Vít Ondruch from comment #21) > (In reply to Hans de Goede from comment #19) > I have updated to that kernel yesterday with worries, but so far it was > without crashes (but I have not replugged my LP into dock yet (isn't it > replugging dock into LP these days? :D) and that was problematic recently, > not sure if related or not). If you are having troubles after replugging the thunderbolt dock you are likely hitting bug 1951372, also check dmesg for similar errors as reported in that bug. I could really use some help with debugging that bug (because of -ENOTIME from my side) see bug 1951372#c35 for how you can help (if you have time).
(In reply to Hans de Goede from comment #22) 1) I was able to replug my Dock without issues, so the new kernel fixes the boltd crash as far as I can tell. 2) I am aware of bug 1951372 and I'll comment there, while the last "crash after plug" seems different.
Yes, no further problems here
This happened to me today at boot. Am I missing an update? bolt-0.9.1-4.fc35.x86_64 Linux 5.15.16-200.fc35.x86_64 #1 SMP Thu Jan 20 15:38:18 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux PID: 9346 (boltd) UID: 0 (root) GID: 0 (root) Signal: 11 (SEGV) Timestamp: Fri 2022-01-28 14:15:17 CST (38min ago) Command Line: /usr/libexec/boltd Executable: /usr/libexec/boltd Control Group: /system.slice/bolt.service Unit: bolt.service Slice: system.slice Boot ID: c99ada0bc269433393f630b070947e66 Machine ID: 12e7d721b767413e8c1a18d9aa8f83a4 Hostname: Storage: /var/lib/systemd/coredump/core.boltd.0.c99ada0bc269433393f630b070947e66.9346.1643400917000000.zst (inaccessible) Message: Process 9346 (boltd) of user 0 dumped core. Found module linux-vdso.so.1 with build-id: 5adf6bc52f5c51e10c5d1229124d27eebdae3b02 Found module libgpg-error.so.0 with build-id: 081975d0a3416374b4883b2f1639fd3c9df42390 Found module libgcrypt.so.20 with build-id: 711d41580c5a8649a79a8430a985dac3e25b5ba2 Found module libcap.so.2 with build-id: 0214aa9cc6a8646eb9ec27ab7dda6a2219da6500 Found module liblz4.so.1 with build-id: fd02c4542a1ce1ad6c503b958447be1c37a4afee Found module libzstd.so.1 with build-id: 7984add4b0ab24869c30e19cfba3637ca295dd7b Found module liblzma.so.5 with build-id: 7fec53ce7cba9489f130c99cfd3ace82e9dde0ee Found module libpcre2-8.so.0 with build-id: 67d78ee981939e51fee33d8885ff8000552e7a3d Found module libblkid.so.1 with build-id: 4466c6926409d89ee7c02c3b0161d4ea12e7f547 Found module libsystemd.so.0 with build-id: b61753e8440ecf39624b3e37f855941c18a69e9b Found module ld-linux-x86-64.so.2 with build-id: 524f5518285687402d801b9c3b1e61d435e6780b Found module libffi.so.6 with build-id: 0129f72b58e11d59546f7f207d2c90af7ebd9a5e Found module libselinux.so.1 with build-id: f805394f993c704b949315b56c344d22dfad801f Found module libmount.so.1 with build-id: bb1678722017ce732c01331b49abb50f9a4835b4 Found module libz.so.1 with build-id: 5903f5c355c264403e4e7cdc66779584425ca3b8 Found module libgmodule-2.0.so.0 with build-id: 634542167d122d8d1aa3b44542dced7bc40d2eb6 Found module libpcre.so.1 with build-id: fcbdb4731e50f20a47b62341a6841dd616fe495d Found module libc.so.6 with build-id: d7e3e120ff5fafc298666927c6475567348588ef Found module libgcc_s.so.1 with build-id: 88564abce789aa42536da1247a57ff6062d61dcb Found module libpolkit-gobject-1.so.0 with build-id: 81b19cfa68a22335c1488868333e6d3033e06b99 Found module libudev.so.1 with build-id: 4a00048d488bd5a48980577f23fcaced551223c3 Found module libgobject-2.0.so.0 with build-id: ead2bc31b68d342e8a9a6a87148862f08dce1bd1 Found module libgio-2.0.so.0 with build-id: 8be4eeb5ab3e02714b03629052528cdecab1ccfc Found module libglib-2.0.so.0 with build-id: 3720108994016259cac8f61f174ea32513518152 Found module boltd with build-id: 24897920824eb153482cc142a2c66782ea0f4815 Stack trace of thread 9346: #0 0x00007f9b9fe8ba9d __strlen_avx2 (libc.so.6 + 0x17fa9d) #1 0x00007f9ba02244a8 g_strdup (libglib-2.0.so.0 + 0x6e4a8) #2 0x00007f9b9ffb38f5 value_collect_string (libgobject-2.0.so.0 + 0x338f5) #3 0x00007f9b9ffa4c5c g_object_set_valist (libgobject-2.0.so.0 + 0x24c5c) #4 0x00007f9b9ffa4f34 g_object_set (libgobject-2.0.so.0 + 0x24f34) #5 0x00005613d7ad9c4b handle_udev_device_event (boltd + 0x12c4b) #6 0x00005613d7ae0ddb bolt_manager_initialize (boltd + 0x19ddb) #7 0x00007f9ba005623a g_initable_new_valist (libgio-2.0.so.0 + 0x7a23a) #8 0x00007f9ba00562ed g_initable_new (libgio-2.0.so.0 + 0x7a2ed) #9 0x00005613d7ad59ec on_bus_acquired (boltd + 0xe9ec) #10 0x00007f9ba00ef046 connection_get_cb.lto_priv.0 (libgio-2.0.so.0 + 0x113046) #11 0x00007f9ba008d19a g_task_return_now (libgio-2.0.so.0 + 0xb119a) #12 0x00007f9ba008d39b g_task_return (libgio-2.0.so.0 + 0xb139b) #13 0x00007f9ba00eb092 bus_get_async_initable_cb (libgio-2.0.so.0 + 0x10f092) #14 0x00007f9ba008d19a g_task_return_now (libgio-2.0.so.0 + 0xb119a) #15 0x00007f9ba008d1dd complete_in_idle_cb (libgio-2.0.so.0 + 0xb11dd) #16 0x00007f9ba020747b g_idle_dispatch (libglib-2.0.so.0 + 0x5147b) #17 0x00007f9ba020b130 g_main_context_dispatch (libglib-2.0.so.0 + 0x55130) #18 0x00007f9ba0260208 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xaa208) #19 0x00007f9ba020a853 g_main_loop_run (libglib-2.0.so.0 + 0x54853) #20 0x00005613d7ad4aa4 main (boltd + 0xdaa4) #21 0x00007f9b9fd39560 __libc_start_call_main (libc.so.6 + 0x2d560) #22 0x00007f9b9fd3960c __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2d60c) #23 0x00005613d7ad4da5 _start (boltd + 0xdda5) Stack trace of thread 9349: #0 0x00007f9b9fe16ecd syscall (libc.so.6 + 0x10aecd) #1 0x00007f9ba025b90c g_cond_wait_until (libglib-2.0.so.0 + 0xa590c) #2 0x00007f9ba01db071 g_async_queue_pop_intern_unlocked (libglib-2.0.so.0 + 0x25071) #3 0x00007f9ba01db1f6 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x251f6) #4 0x00007f9ba02381b9 g_thread_pool_thread_proxy.lto_priv.0 (libglib-2.0.so.0 + 0x821b9) #5 0x00007f9ba0235842 g_thread_proxy (libglib-2.0.so.0 + 0x7f842) #6 0x00007f9b9fd99b1a start_thread (libc.so.6 + 0x8db1a) #7 0x00007f9b9fe1e650 __clone3 (libc.so.6 + 0x112650) Stack trace of thread 9350: #0 0x00007f9b9fe1179f __poll (libc.so.6 + 0x10579f) #1 0x00007f9ba026019c g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xaa19c) #2 0x00007f9ba020a853 g_main_loop_run (libglib-2.0.so.0 + 0x54853) #3 0x00007f9ba00efc0a gdbus_shared_thread_func.lto_priv.0 (libgio-2.0.so.0 + 0x113c0a) #4 0x00007f9ba0235842 g_thread_proxy (libglib-2.0.so.0 + 0x7f842) #5 0x00007f9b9fd99b1a start_thread (libc.so.6 + 0x8db1a) #6 0x00007f9b9fe1e650 __clone3 (libc.so.6 + 0x112650) Stack trace of thread 9348: #0 0x00007f9b9fe16ecd syscall (libc.so.6 + 0x10aecd) #1 0x00007f9ba025b343 g_cond_wait (libglib-2.0.so.0 + 0xa5343) #2 0x00007f9ba01db08b g_async_queue_pop_intern_unlocked (libglib-2.0.so.0 + 0x2508b) #3 0x00007f9ba023759a g_thread_pool_spawn_thread (libglib-2.0.so.0 + 0x8159a) #4 0x00007f9ba0235842 g_thread_proxy (libglib-2.0.so.0 + 0x7f842) #5 0x00007f9b9fd99b1a start_thread (libc.so.6 + 0x8db1a) #6 0x00007f9b9fe1e650 __clone3 (libc.so.6 + 0x112650) Stack trace of thread 9347: #0 0x00007f9b9fe1179f __poll (libc.so.6 + 0x10579f) #1 0x00007f9ba026019c g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xaa19c) #2 0x00007f9ba0208933 g_main_context_iteration (libglib-2.0.so.0 + 0x52933) #3 0x00007f9ba0208981 glib_worker_main (libglib-2.0.so.0 + 0x52981) #4 0x00007f9ba0235842 g_thread_proxy (libglib-2.0.so.0 + 0x7f842) #5 0x00007f9b9fd99b1a start_thread (libc.so.6 + 0x8db1a) #6 0x00007f9b9fe1e650 __clone3 (libc.so.6 + 0x112650)
I see this in the journal too: Jan 28 14:15:17 boltd[9346]: [d3010000-0080-ThinkPad P1 Gen2 ] udev: failed to get device info: could not read 'authorized': No such file or directory