You are not logged in.

#1 2021-07-15 12:09:34

pebcak
Member
Registered: 2020-08-11
Posts: 9

[Solved] Update to linux-zen 5.13.1: failed to start bolt.service

I just updated the kernel from linux-zen 5.12.15 to linux-zen 5.13.1 and noticed a failure in starting a service on my system. With 5.12.15 there are no failures.

$ systemctl --failed 
  UNIT         LOAD   ACTIVE SUB    DESCRIPTION               
● bolt.service loaded failed failed Thunderbolt system service

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
1 loaded units listed.

$ systemctl status bolt.service 
× bolt.service - Thunderbolt system service
     Loaded: loaded (/usr/lib/systemd/system/bolt.service; static)
     Active: failed (Result: core-dump) since Thu 2021-07-15 13:33:16 CEST; 1min 20s ago
       Docs: man:boltd(8)
    Process: 1417 ExecStart=/usr/lib/boltd (code=dumped, signal=SEGV)
   Main PID: 1417 (code=dumped, signal=SEGV)
        CPU: 29ms

Warning: some journal files were not opened due to insufficient permissions.
systemd-coredump[1422]: Process 1417 (boltd) of user 0 dumped core.
                                                   
                                                   Found module linux-vdso.so.1 with build-id: c687576581e9295af19e5db86a12af10cabf3c3d
                                                   Found module libnss_files.so.2 with build-id: 1a36dfc01d3a1010b2ee79766a24a8090a3266d5
                                                   Found module libgpg-error.so.0 with build-id: ba85170c2d9343ea05eea8fa2048c212ff4ef552
                                                   Found module libgcrypt.so.20 with build-id: 4a114f6a371dee16ad6e01023b0b3c654b8582a3
                                                   Found module libcap.so.2 with build-id: d3d0ddf2f54f554fb280d7eb41a06dd39173009e
                                                   Found module liblz4.so.1 with build-id: e63600ab23b2f6997f42fac2fa56e1f02ce159a1
                                                   Found module libzstd.so.1 with build-id: 4b10444c1560ebc574af4d5f488b7408b22d450e
                                                   Found module liblzma.so.5 with build-id: f8d607153b2b315f1aaa1c8e12553d544e661f2d
                                                   Found module libblkid.so.1 with build-id: c8025d3fd3c6cb96954e815c81ab398a5f1cf7b9
                                                   Found module libdl.so.2 with build-id: 5abc547e7b0949f89f3c0e21ab0c8331a7440a8a
                                                   Found module libsystemd.so.0 with build-id: 15e863a1804ee74d4dd4c79ada848c6f1facb2d2
                                                   Found module ld-linux-x86-64.so.2 with build-id: 040cc3dd10461562f177df39e3be2f3704258c3c
                                                   Found module librt.so.1 with build-id: 75484da2d6f1515189eefa076e0a40328834cd16
                                                   Found module libffi.so.7 with build-id: de60e99f39569d11d09160bbdcd486cedc87d2b6
                                                   Found module libresolv.so.2 with build-id: c915c72668282861a813f7ea3c0780f37b681dc0
                                                   Found module libmount.so.1 with build-id: 03cb4d49246c496b0809aa7ad71a017bd671a80d
                                                   Found module libz.so.1 with build-id: 81bf6e728a6d6f5b105b0f8b25f6c614ce10452a
                                                   Found module libgmodule-2.0.so.0 with build-id: 1c305e1a08706be35604a78f8d99a567274a0217
                                                   Found module libpthread.so.0 with build-id: 07c8f95b4f3251d08550217ad8a1f31066229996
                                                   Found module libpcre.so.1 with build-id: 845483dd0acba86de9f0313102bebbaf3ce52767
                                                   Found module libc.so.6 with build-id: 4b406737057708c0e4c642345a703c47a61c73dc
                                                   Found module libpolkit-gobject-1.so.0 with build-id: 167c64cb461caead0591ef8eae0faa82a375f9d7
                                                   Found module libudev.so.1 with build-id: 880e57f50a36ddbfe80dbe5f62d43860f960c797
                                                   Found module libgobject-2.0.so.0 with build-id: a6d338dd0fd6bb335a4010b838f5173c6cbf953a
                                                   Found module libgio-2.0.so.0 with build-id: 451ca85a17a8e53e563a4a878f7f44901bd5a1e1
                                                   Found module libglib-2.0.so.0 with build-id: 1683975c11bffb530743825149325e84765311ab
                                                   Found module boltd with build-id: 70a3e3469971fdaab318b886e0db665ef234a3df
                                                   Stack trace of thread 1417:
                                                   #0  0x00007efdeb34d547 __strlen_avx2 (libc.so.6 + 0x160547)
                                                   #1  0x00007efdeb688495 g_strdup (libglib-2.0.so.0 + 0x71495)
                                                   #2  0x00007efdeb431e5e n/a (libgobject-2.0.so.0 + 0x31e5e)
                                                   #3  0x00007efdeb42306c g_object_set_valist (libgobject-2.0.so.0 + 0x2306c)
                                                   #4  0x00007efdeb423355 g_object_set (libgobject-2.0.so.0 + 0x23355)
                                                   #5  0x00005570967a968a n/a (boltd + 0xd68a)
                                                   #6  0x00005570967b057a n/a (boltd + 0x1457a)
                                                   #7  0x00007efdeb4c8de1 g_initable_new_valist (libgio-2.0.so.0 + 0x6ede1)
                                                   #8  0x00007efdeb4c8e9a g_initable_new (libgio-2.0.so.0 + 0x6ee9a)
                                                   #9  0x00005570967a52f3 n/a (boltd + 0x92f3)
                                                   #10 0x00007efdeb55aac5 n/a (libgio-2.0.so.0 + 0x100ac5)
                                                   #11 0x00007efdeb4fa934 n/a (libgio-2.0.so.0 + 0xa0934)
                                                   #12 0x00007efdeb4fe629 n/a (libgio-2.0.so.0 + 0xa4629)
                                                   #13 0x00007efdeb557903 n/a (libgio-2.0.so.0 + 0xfd903)
                                                   #14 0x00007efdeb4fa934 n/a (libgio-2.0.so.0 + 0xa0934)
                                                   #15 0x00007efdeb4fa969 n/a (libgio-2.0.so.0 + 0xa0969)
                                                   #16 0x00007efdeb66b015 g_main_context_dispatch (libglib-2.0.so.0 + 0x54015)
                                                   #17 0x00007efdeb6beb99 n/a (libglib-2.0.so.0 + 0xa7b99)
                                                   #18 0x00007efdeb66a693 g_main_loop_run (libglib-2.0.so.0 + 0x53693)
                                                   #19 0x00005570967a445d n/a (boltd + 0x845d)
                                                   #20 0x00007efdeb214b25 __libc_start_main (libc.so.6 + 0x27b25)
                                                   #21 0x00005570967a46ce n/a (boltd + 0x86ce)
                                                   
                                                   Stack trace of thread 1418:
                                                   #0  0x00007efdeb2e0b2f __poll (libc.so.6 + 0xf3b2f)
                                                   #1  0x00007efdeb6beb29 n/a (libglib-2.0.so.0 + 0xa7b29)
                                                   #2  0x00007efdeb668871 g_main_context_iteration (libglib-2.0.so.0 + 0x51871)
                                                   #3  0x00007efdeb6688c2 n/a (libglib-2.0.so.0 + 0x518c2)
                                                   #4  0x00007efdeb6992c1 n/a (libglib-2.0.so.0 + 0x822c1)
                                                   #5  0x00007efdeb15c259 start_thread (libpthread.so.0 + 0x9259)
                                                   #6  0x00007efdeb2eb5e3 __clone (libc.so.6 + 0xfe5e3)
                                                   
                                                   Stack trace of thread 1419:
                                                   #0  0x00007efdeb2e618d syscall (libc.so.6 + 0xf918d)
                                                   #1  0x00007efdeb6b904b g_cond_wait_until (libglib-2.0.so.0 + 0xa204b)
                                                   #2  0x00007efdeb63a7d3 n/a (libglib-2.0.so.0 + 0x237d3)
                                                   #3  0x00007efdeb69bfcb n/a (libglib-2.0.so.0 + 0x84fcb)
                                                   #4  0x00007efdeb6992c1 n/a (libglib-2.0.so.0 + 0x822c1)
                                                   #5  0x00007efdeb15c259 start_thread (libpthread.so.0 + 0x9259)
                                                   #6  0x00007efdeb2eb5e3 __clone (libc.so.6 + 0xfe5e3)
                                                   
                                                   Stack trace of thread 1420:
                                                   #0  0x00007efdeb2e0b2f __poll (libc.so.6 + 0xf3b2f)
                                                   #1  0x00007efdeb6beb29 n/a (libglib-2.0.so.0 + 0xa7b29)
                                                   #2  0x00007efdeb66a693 g_main_loop_run (libglib-2.0.so.0 + 0x53693)
                                                   #3  0x00007efdeb55b8c8 n/a (libgio-2.0.so.0 + 0x1018c8)
                                                   #4  0x00007efdeb6992c1 n/a (libglib-2.0.so.0 + 0x822c1)
                                                   #5  0x00007efdeb15c259 start_thread (libpthread.so.0 + 0x9259)
                                                   #6  0x00007efdeb2eb5e3 __clone (libc.so.6 + 0xfe5e3)
$ inxi -Fxxxz
System:    Kernel: 5.13.1-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0 Desktop: GNOME 40.3 tk: GTK 3.24.30 
           wm: gnome-shell dm: GDM 40.0 Distro: Arch Linux 
Machine:   Type: Laptop System: Dell product: XPS 13 9380 v: N/A serial: <filter> Chassis: type: 10 serial: <filter> 
           Mobo: Dell model: 0KTDY6 v: A00 serial: <filter> UEFI: Dell v: 1.13.1 date: 03/25/2021 
Battery:   ID-1: BAT0 charge: 39.5 Wh (92.5%) condition: 42.7/52.0 Wh (82.2%) volts: 8.6 min: 7.6 
           model: LGC-LGC6.73 DELL H754V8C type: Li-ion serial: <filter> status: Charging 
CPU:       Info: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP arch: Kaby Lake note: check rev: B cache: 
           L2: 8 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31999 
           Speed: 800 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 800 2: 800 3: 2852 4: 2284 5: 1690 6: 1066 7: 800 8: 800 
Graphics:  Device-1: Intel WhiskeyLake-U GT2 [UHD Graphics 620] vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 
           chip-ID: 8086:3ea0 class-ID: 0300 
           Device-2: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-5:2 chip-ID: 0c45:6723 class-ID: 0e02 
           Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver: loaded: i915 
           note: n/a (using device driver) - try sudo/root resolution: 1920x1080~60Hz s-dpi: 96 
           OpenGL: renderer: Mesa Intel UHD Graphics 620 (WHL GT2) v: 4.6 Mesa 21.1.4 direct render: Yes 
Audio:     Device-1: Intel Cannon Point-LP High Definition Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 
           chip-ID: 8086:9dc8 class-ID: 0403 
           Sound Server-1: ALSA v: k5.13.1-zen1-1-zen running: yes 
           Sound Server-2: JACK v: 1.9.19 running: no 
           Sound Server-3: PulseAudio v: 14.99.2-1-g36fcf running: no 
           Sound Server-4: PipeWire v: 0.3.31 running: yes 
Network:   Device-1: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter vendor: Rivet Networks Killer 1435 Wireless-AC 
           driver: ath10k_pci v: kernel port: efa0 bus-ID: 02:00.0 chip-ID: 168c:003e class-ID: 0280 
           IF: wlp2s0 state: up mac: <filter> 
Bluetooth: Device-1: Foxconn / Hon Hai type: USB driver: btusb v: 0.8 bus-ID: 1-7:3 chip-ID: 0489:e0a2 class-ID: e001 
           Report: rfkill ID: hci0 rfk-id: 1 state: up address: see --recommends 
Drives:    Local Storage: total: 465.76 GiB used: 54.15 GiB (11.6%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO 500GB size: 465.76 GiB speed: 31.6 Gb/s lanes: 4 
           rotation: SSD serial: <filter> rev: 2B2QEXE7 scheme: GPT 
Partition: ID-1: / size: 50 GiB used: 18.58 GiB (37.2%) fs: btrfs dev: /dev/nvme0n1p5 
           ID-2: /boot/efi size: 126 MiB used: 550 KiB (0.4%) fs: vfat dev: /dev/nvme0n1p4 
           ID-3: /home size: 50 GiB used: 18.58 GiB (37.2%) fs: btrfs dev: /dev/nvme0n1p5 
           ID-4: /var/log size: 50 GiB used: 18.58 GiB (37.2%) fs: btrfs dev: /dev/nvme0n1p5 
Swap:      ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p7 
           ID-2: swap-2 type: zram size: 1024 MiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0 
Sensors:   System Temperatures: cpu: 49.0 C mobo: N/A 
           Fan Speeds (RPM): cpu: 0 fan-2: 0 
Info:      Processes: 276 Uptime: 9m wakeups: 952 Memory: 7.42 GiB used: 1.89 GiB (25.5%) Init: systemd v: 249 Compilers: 
           gcc: 11.1.0 Packages: 947 pacman: 936 flatpak: 11 Shell: Bash v: 5.1.8 running-in: gnome-terminal inxi: 3.3.04 

Please tell me if you need more info in order to help to troubleshoot this issue or if I need to report this somewhere else.

Last edited by pebcak (2021-08-16 13:17:25)

Offline

#2 2021-07-24 12:44:26

pebcak
Member
Registered: 2020-08-11
Posts: 9

Re: [Solved] Update to linux-zen 5.13.1: failed to start bolt.service

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

on a Fedora 34 system 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.

I would appreciate any advise on how I can take this from here in order to fix the issue. Do I need to file a bug report at https://bugs.archlinux.org/ ?

Last edited by pebcak (2021-07-24 12:47:29)

Offline

#3 2021-07-24 14:51:51

sabroad
Member
Registered: 2015-05-24
Posts: 206

Re: [Solved] Update to linux-zen 5.13.1: failed to start bolt.service

I think there's already an issue for this.

Looks like this is a known issue with bolt: https://gitlab.freedesktop.org/bolt/bolt/-/issues/174

Last edited by sabroad (2021-07-24 14:52:53)


--
saint_abroad

Offline

#4 2021-07-26 05:53:58

brody
Member
Registered: 2019-07-19
Posts: 1

Re: [Solved] Update to linux-zen 5.13.1: failed to start bolt.service

I can confirm that the issue is gone after a rebuild of bolt like Ola Theander who has posted this in https://gitlab.freedesktop.org/bolt/bolt/-/issues/174 yesterday.

Last edited by brody (2021-07-26 05:54:20)

Offline

#5 2021-07-26 12:33:05

pebcak
Member
Registered: 2020-08-11
Posts: 9

Re: [Solved] Update to linux-zen 5.13.1: failed to start bolt.service

Thanks @sabroad and @brody for your replies!
What puzzles me is the fact that bolt.service starts fine with bolt 0.9.1-1 on the LTS kernel.

Last edited by pebcak (2021-07-26 12:34:11)

Offline

#6 2021-07-29 09:57:52

pebcak
Member
Registered: 2020-08-11
Posts: 9

Re: [Solved] Update to linux-zen 5.13.1: failed to start bolt.service

Still unresolved in 5.13.6-zen1-1-zen (in Testing at the time of writing).

Offline

#7 2021-08-05 15:49:54

Delvien
Member
Registered: 2010-08-29
Posts: 4

Re: [Solved] Update to linux-zen 5.13.1: failed to start bolt.service

Still failing even on 5.13.8-arch1-1,

I read there was a fix out, but not sure what version its coming.

Offline

#8 2021-08-16 13:16:55

pebcak
Member
Registered: 2020-08-11
Posts: 9

Re: [Solved] Update to linux-zen 5.13.1: failed to start bolt.service

Working again on: 5.13.10-zen1-1-zen

Comment by Steve Balboa (steveb) - Friday, 13 August 2021, 20:19 GMT
Problem solved with 5.13.10-arch1-1
https://bugs.archlinux.org/task/71569

Offline

Board footer

Powered by FluxBB