About a week ago I upgraded my zen kernel from 5.12.15 to 5.13.1 on an Arch system (hope it is alright to post about it here) and noticed that a service won’t start on this system. I posted about it on Arch forum: https://bbs.archlinux.org/viewtopic.php?id=267977
Today I installed linux-5.13.4 in the hope that the issue would have been resolved but unfortunately the issue still seems to be there. I don’t know if this is Arch-specific or has to do with the kernel upstream.
I have a Fedora install on the same machine and I’m waiting for the kernel upgrade to 5.13 to know if the issue is presented there as well.
I wonder if anyone else has stumbled upon this as well.
I don’t use anything Thunderbolt, and I’m not sure how to interpret the following output, but it seems different from yours:
$ systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
0 loaded units listed.
$ systemctl status bolt
○ bolt.service - Thunderbolt system service
Loaded: loaded (/usr/lib/systemd/system/bolt.service; static)
Active: inactive (dead)
Docs: man:boltd(8)
Regular kernel, I don’t have linux-zen installed, sorry.
I have never needed to enable and start bolt.service since it was on by default. It got started at boot with 5.12.xx kernels and it does so with the LTS kernel as well. I suspect there might be a “bug” in the 5.13 series or something of the sort. Trying to restart the service will fail as well:
sudo systemctl restart bolt.service
Job for bolt.service failed because a fatal signal was delivered causing the control process to dump core.
See "systemctl status bolt.service" and "journalctl -xeu bolt.service" for details.
systemctl status bolt.service
× bolt.service - Thunderbolt system service
Loaded: loaded (/usr/lib/systemd/system/bolt.service; static)
Active: failed (Result: core-dump) since Wed 2021-07-21 21:31:27 CEST; 1min 26s ago
Docs: man:boltd(8)
Process: 10242 ExecStart=/usr/lib/boltd (code=dumped, signal=SEGV)
Main PID: 10242 (code=dumped, signal=SEGV)
CPU: 39ms
journalctl -xeu bolt.service
Jul 21 21:31:27 arch-gnome boltd[10242]: probing: adding /sys/devices/pci0000:00/0000:00:1d.0/0000:03:00.0 to roots
Jul 21 21:31:27 arch-gnome boltd[10242]: [d2030000-0080-domain0 ] bootacl: synchronizing journal
Jul 21 21:31:27 arch-gnome boltd[10242]: security level set to 'user'
Jul 21 21:31:27 arch-gnome boltd[10242]: [d2030000-0080-domain0 ] connected: as domain0 [user] (/sys/devices/pci0000:00/0000:00:1d.0/0000:03:00.0/0000:04:00.0/0000:05:00.0/domain0)
Jul 21 21:31:27 arch-gnome boltd[10242]: [d2030000-0080-XPS 9380 ] udev: failed to get device info: could not read 'authorized': No such file or directory
Jul 21 21:31:27 arch-gnome systemd[1]: bolt.service: Main process exited, code=dumped, status=11/SEGV
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit bolt.service has exited.
░░
░░ The process' exit code is 'dumped' and its exit status is 11.
Jul 21 21:31:27 arch-gnome systemd[1]: bolt.service: Failed with result 'core-dump'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit bolt.service has entered the 'failed' state with result 'core-dump'.
Jul 21 21:31:27 arch-gnome systemd[1]: Failed to start Thunderbolt system service.
░░ Subject: A start job for unit bolt.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit bolt.service has finished with a failure.
░░
░░ The job identifier is 4874 and the job result is failed.
Jul 21 21:31:27 arch-gnome systemd[1]: bolt.service: Scheduled restart job, restart counter is at 10.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ Automatic restarting of the unit bolt.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Jul 21 21:31:27 arch-gnome systemd[1]: Stopped Thunderbolt system service.
░░ Subject: A stop job for unit bolt.service has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit bolt.service has finished.
░░
░░ The job identifier is 4995 and the job result is done.
Jul 21 21:31:27 arch-gnome systemd[1]: bolt.service: Start request repeated too quickly.
Jul 21 21:31:27 arch-gnome systemd[1]: bolt.service: Failed with result 'core-dump'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit bolt.service has entered the 'failed' state with result 'core-dump'.
Jul 21 21:31:27 arch-gnome systemd[1]: Failed to start Thunderbolt system service.
░░ Subject: A start job for unit bolt.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit bolt.service has finished with a failure.
░░
░░ The job identifier is 4995 and the job result is failed.
sudo dmesg | grep boltd
[35848.815330] boltd[10117]: segfault at 20 ip 00007fca3a921547 sp 00007ffe5c27d8c8 error 4 in libc-2.33.so[7fca3a7e7000+14b000]
[35848.815458] audit: type=1701 audit(1626895867.426:270): auid=4294967295 uid=0 gid=0 ses=4294967295 subj==unconfined pid=10117 comm="boltd" exe="/usr/lib/boltd" sig=11 res=1
[35854.969314] boltd[10149]: segfault at 20 ip 00007f0955746547 sp 00007ffcef982508 error 4 in libc-2.33.so[7f095560c000+14b000]
[35854.969429] audit: type=1701 audit(1626895873.580:296): auid=4294967295 uid=0 gid=0 ses=4294967295 subj==unconfined pid=10149 comm="boltd" exe="/usr/lib/boltd" sig=11 res=1
[35861.155769] boltd[10178]: segfault at 20 ip 00007f220ee45547 sp 00007ffd430726b8 error 4 in libc-2.33.so[7f220ed0b000+14b000]
[35861.155837] audit: type=1701 audit(1626895879.766:320): auid=4294967295 uid=0 gid=0 ses=4294967295 subj==unconfined pid=10178 comm="boltd" exe="/usr/lib/boltd" sig=11 res=1
[35867.769888] boltd[10217]: segfault at 20 ip 00007f2848650547 sp 00007ffc00b13d08 error 4 in libc-2.33.so[7f2848516000+14b000]
[35867.770008] audit: type=1701 audit(1626895886.380:356): auid=4294967295 uid=0 gid=0 ses=4294967295 subj==unconfined pid=10217 comm="boltd" exe="/usr/lib/boltd" sig=11 res=1
I suspect that. This is a dual-boot system Arch-Fedora. I haven’t checked on Fedora today to see if the update to 5.13 has arrived. Then we could perhaps know if the issue is in Arch or in 5.13 in general. I’ll report when Fedora gets the 5.13 kernel.
I got my kernel updated to Linux fedora 5.13.4-200.fc34.x86_64 #1 SMP Tue Jul 20 20:27:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
om my Fedora 34 on the same machine as above. The bolt.service starts at boot and runs as normally:
systemctl status bolt.service
● bolt.service - Thunderbolt system service
Loaded: loaded (/usr/lib/systemd/system/bolt.service; static)
Active: active (running) since Sat 2021-07-24 14:26:01 CEST; 7min ago
Docs: man:boltd(8)
Main PID: 821 (boltd)
Status: "authmode: enabled, force-power: unset"
Tasks: 4 (limit: 9058)
Memory: 2.3M
CPU: 120ms
CGroup: /system.slice/bolt.service
└─821 /usr/libexec/boltd
Jul 24 14:26:01 fedora boltd[821]: [d2030000-0080-domain0 ] bootacl: synchronizing journal
Jul 24 14:26:01 fedora boltd[821]: security level set to 'user'
Jul 24 14:26:01 fedora boltd[821]: [d2030000-0080-domain0 ] connected: as domain0 [user] (/sys/devices/pci0000:00/0000:00:1d.0/0>
Jul 24 14:26:01 fedora boltd[821]: [d2030000-0080-XPS 9380 ] udev: failed to get device info: could not read 'authorized': No suc>
Jul 24 14:26:01 fedora boltd[821]: [d2030000-0080-XPS 9380 ] parent is (null)...
Jul 24 14:26:01 fedora boltd[821]: [d2030000-0080-XPS 9380 ] store: updating device
Jul 24 14:26:01 fedora boltd[821]: [d2030000-0080-XPS 9380 ] connected: unknown (/sys/devices/pci0000:00/0000:00:1d.0/0000:03:00.>
Jul 24 14:26:01 fedora boltd[821]: [d2030000-0080-domain0 ] dbus: exported domain at /org/freedesktop/bolt/domains/d2030000_0080>
Jul 24 14:26:01 fedora boltd[821]: [d2030000-0080-XPS 9380 ] dbus: exported device at /org/freedesktop/bolt/devices/d2030000_0080>
Jul 24 14:26:01 fedora systemd[1]: Started Thunderbolt system service.
So the problem seems to be on the Arch side (cannot speak for other distros using 5.13 kernel).
Welcome to EnOS forum @mercibe and thanks for your reply!
What puzzles me is the fact that bolt.service starts and runs as normal with bolt 0.9.1-1 on LTS kernel. However there seems to be some recent development on the 5.13 kernel front. See the last comment by @loqs at https://bugs.archlinux.org/task/71569