Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Wayland/GNOME session fails to start if Thunderbolt 5 dock attached #3233

Open
Aqua1ung opened this issue Dec 21, 2024 · 14 comments
Open

Wayland/GNOME session fails to start if Thunderbolt 5 dock attached #3233

Aqua1ung opened this issue Dec 21, 2024 · 14 comments
Assignees
@bwarden
Labels
bug

Comments

@Aqua1ung
Copy link

Aqua1ung commented Dec 21, 2024 •
edited
Loading

My laptop won't load the normal Wayland/Gnome session upon booting up if a Thunderbolt 5 dock is attached. Currently on 42790, running Gnome on Wayland. Interestingly, if I start the laptop with the dock turned off, and connect the dock after GNOME has finished loading, things work just fine!

I am attaching the log for the dock-connected-during-boot scenario.
log.txt
@Aqua1ung
Copy link
Author

Aqua1ung commented Dec 23, 2024 •
edited
Loading

Same sort of trouble happens with Thunderbolt 4 docks as well. Things were working fine one or two releases ago, so methinks the blame lies squarely with the new one or two CL releases--quite possibly the new kernel 6.12.4. Here's the log gathered during booting with a TB4 dock connected: dumpTB4.txt

I see something that might be relevant to this in both logs:

Dec 23 14:37:50 DadsGram gnome-shell[1992]: WL: error in client communication (pid 1992)
Dec 23 14:37:50 DadsGram gnome-shell[2530]: XWAYLAND: wl_display#1: error 3: Error getting DRM lease device fd
Dec 23 14:37:50 DadsGram gnome-shell[2530]: (EE) could not connect to wayland server

@ephut ephut removed the new label Jan 2, 2025
@bwarden
Copy link
Member

bwarden commented Jan 2, 2025

I'm wondering if this is related:
https://www.reddit.com/r/Fedora/comments/1hipnnh/usbc_dock_stopped_working_with_612_kernel_update/

@Aqua1ung
Copy link
Author

Aqua1ung commented Jan 2, 2025

I'm wondering if this is related: https://www.reddit.com/r/Fedora/comments/1hipnnh/usbc_dock_stopped_working_with_612_kernel_update/

All I can say for now is that my TB hubs do not rely on DisplayLink--at least not to my knowledge. (I make a point to stay away from DisplayLink devices.)

@bwarden
Copy link
Member

bwarden commented Jan 2, 2025

No new insights yet. Looks like you have these two devices, right?

@bwarden
Copy link
Member

bwarden commented Jan 2, 2025

Relevant info from log.txt:

Dec 21 16:48:57 hostname tbtacl[742]: 740: args: change /devices/pci0000:00/0000:00:0d.3/domain0/0-0
Dec 21 16:48:57 hostname tbtacl[756]: 740: no childs found
Dec 21 16:48:57 hostname (udev-worker)[472]: 0-0: Process '/usr/lib/udev/tbtacl change /devices/pci0000:00/0000:00:0d.3/domain0/0-0' failed with exit code 1.
Dec 21 16:48:57 hostname boltd[752]: bolt 0.9.8 starting up.
Dec 21 16:48:57 hostname boltd[752]: manager: initializing store
Dec 21 16:48:57 hostname boltd[752]: store: located at: /var/lib/boltd
Dec 21 16:48:57 hostname boltd[752]: config: loading user config
Dec 21 16:48:57 hostname boltd[752]: bouncer: initializing polkit
Dec 21 16:48:57 hostname dbus-daemon[519]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' requested by ':1.20' (uid=0 pid=752 comm="/usr/libexec/boltd")
Dec 21 16:48:57 hostname boltd[752]: watchdog: enabled [pulse: 90s]
Dec 21 16:48:57 hostname boltd[752]: udev: initializing udev
Dec 21 16:48:57 hostname boltd[752]: store: loading domains
Dec 21 16:48:57 hostname boltd[752]: store: loading devices
Dec 21 16:48:57 hostname boltd[752]: [80a78780-0071                            ] store: loading device
Dec 21 16:48:57 hostname boltd[752]: [d1030000-0091                            ] store: loading device
Dec 21 16:48:57 hostname boltd[752]: [ef9f8780-00d6                            ] store: loading device
Dec 21 16:48:57 hostname boltd[752]: [e0d78780-00c2                            ] store: loading device
Dec 21 16:48:57 hostname boltd[752]: power: state located at: /run/boltd/power
Dec 21 16:48:57 hostname boltd[752]: power: force power support: no
Dec 21 16:48:57 hostname boltd[752]: udev: enumerating devices
Dec 21 16:48:57 hostname boltd[752]: [b17d8780-01c2-domain0                    ] newly connected [iommu+user] (/sys/devices/pci0000:00/0000:00:0d.3/domain0/0-0)
Dec 21 16:48:57 hostname boltd[752]: security level set to 'user'
Dec 21 16:48:57 hostname boltd[752]: [b17d8780-01c2-domain0                    ] domain: registered (bootacl: 0/0)
Dec 21 16:48:57 hostname tbtacl[1046]: 1045: args: add /devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1
Dec 21 16:48:57 hostname boltd[752]: [b17d8780-01c2-domain0                    ] bootacl: bootacl not supported, no sync
Dec 21 16:48:57 hostname tbtacl[1058]: 1045: authorizing /sys/devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1
Dec 21 16:48:57 hostname boltd[752]: [b17d8780-01c2-domain0                    ] udev: failed to determine if uid is stable: unknown NHI PCI id '0xa76d'
Dec 21 16:48:57 hostname tbtacl[1060]: 1045: not in ACL
Dec 21 16:48:57 hostname boltd[752]: [b17d8780-01c2-domain0                    ] udev: uuid is stable: no (for NHI: 0xa76d)
Dec 21 16:48:57 hostname boltd[752]: global 'generation' set to '4'
Dec 21 16:48:57 hostname boltd[752]: [b17d8780-01c2-Gen12                      ] device added, status: authorized, at /sys/devices/pci0000:00/0000:00:0d.3/domain0/0-0
Dec 21 16:48:57 hostname boltd[752]: [b17d8780-01c2-Gen12                      ] labeling device: INTEL Gen12
Dec 21 16:48:58 hostname tbtacl[1100]: 1099: args: change /devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1
Dec 21 16:48:57 hostname boltd[752]: [b17d8780-01c2-domain0                    ] dbus: exported domain at /org/freedesktop/bolt/domains/b17d8780_01c2_a6f6_ffff_ffffffffffff
Dec 21 16:48:58 hostname tbtacl[1113]: 1099: no childs found
Dec 21 16:48:57 hostname boltd[752]: [80a78780-0071-Thunderbolt Dock G4        ] dbus: exported device at /org/freedesktop/bolt/devices/80a78780_0071...
Dec 21 16:48:57 hostname boltd[752]: [d1030000-0091-40Gbps                     ] dbus: exported device at /org/freedesktop/bolt/devices/d1030000_0091...
Dec 21 16:48:57 hostname boltd[752]: [ef9f8780-00d6-Element Hub                ] dbus: exported device at /org/freedesktop/bolt/devices/ef9f8780_00d6...
Dec 21 16:48:57 hostname boltd[752]: [e0d78780-00c2-107064                     ] dbus: exported device at /org/freedesktop/bolt/devices/e0d78780_00c2...
Dec 21 16:48:57 hostname boltd[752]: [b17d8780-01c2-Gen12                      ] dbus: exported device at /org/freedesktop/bolt/devices/b17d8780_01c2...
Dec 21 16:48:57 hostname (udev-worker)[499]: 0-1: Process '/usr/lib/udev/tbtacl add    /devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1' failed with exit code 1.
Dec 21 16:48:57 hostname boltd[752]: [e0d78780-00c2-107064                     ] parent is b17d8780-01c2...
Dec 21 16:48:57 hostname boltd[752]: [e0d78780-00c2-107064                     ] connected: connected (/sys/devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1)
Dec 21 16:48:57 hostname boltd[752]: [e0d78780-00c2-107064                     ] auto-auth: authmode: enabled, policy: iommu, iommu: yes -> ok
Dec 21 16:48:57 hostname boltd[752]: [e0d78780-00c2-107064                     ] auto-auth: security: iommu+user mode, key: no -> ok
Dec 21 16:48:57 hostname boltd[752]: probing: started [1000]
Dec 21 16:48:57 hostname boltd[752]: [e0d78780-00c2-107064                     ] authorize: authorization prepared for 'user' level
Dec 21 16:48:57 hostname boltd[752]: [e0d78780-00c2-107064                     ] udev: device changed: authorizing -> authorizing
Dec 21 16:48:57 hostname boltd[752]: [e0d78780-00c2-107064                     ] udev: device changed: authorizing -> authorizing
Dec 21 16:48:58 hostname boltd[752]: [e0d78780-00c2-107064                     ] authorize: finished: ok (status: authorized, flags: 0)
Dec 21 16:48:58 hostname boltd[752]: [e0d78780-00c2-107064                     ] auto-auth: authorization successful
Dec 21 16:48:58 hostname (udev-worker)[469]: 0-1: Process '/usr/lib/udev/tbtacl change /devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1' failed with exit code 1.
Dec 21 16:48:58 hostname boltd[752]: [e0d78780-00c2-107064                     ] udev: device changed: authorized -> authorized
Dec 21 16:49:00 hostname tbtacl[1184]: 1183: args: add /devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1/0-301
Dec 21 16:49:00 hostname tbtacl[1197]: 1183: authorizing /sys/devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1/0-301
Dec 21 16:49:00 hostname tbtacl[1199]: 1183: not in ACL
Dec 21 16:49:00 hostname (udev-worker)[468]: 0-301: Process '/usr/lib/udev/tbtacl add    /devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1/0-301' failed with exit code 1.
Dec 21 16:49:00 hostname boltd[752]: [ef9f8780-00d6-Element Hub                ] parent is e0d78780-00c2...
Dec 21 16:49:00 hostname boltd[752]: [ef9f8780-00d6-Element Hub                ] connected: connected (/sys/devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1/0-301)
Dec 21 16:49:00 hostname boltd[752]: [ef9f8780-00d6-Element Hub                ] auto-auth: authmode: enabled, policy: iommu, iommu: yes -> ok
Dec 21 16:49:00 hostname boltd[752]: [ef9f8780-00d6-Element Hub                ] auto-auth: security: iommu+user mode, key: no -> ok
Dec 21 16:49:00 hostname boltd[752]: [ef9f8780-00d6-Element Hub                ] authorize: authorization prepared for 'user' level
Dec 21 16:49:00 hostname boltd[752]: [ef9f8780-00d6-Element Hub                ] udev: device changed: authorizing -> authorizing
Dec 21 16:49:00 hostname boltd[752]: [ef9f8780-00d6-Element Hub                ] udev: device changed: authorizing -> authorizing
Dec 21 16:49:01 hostname boltd[752]: [ef9f8780-00d6-Element Hub                ] authorize: finished: ok (status: authorized, flags: 0)
Dec 21 16:49:01 hostname tbtacl[1205]: 1204: args: add /devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1/0-301/0-70301
Dec 21 16:49:01 hostname boltd[752]: [ef9f8780-00d6-Element Hub                ] auto-auth: authorization successful
Dec 21 16:49:01 hostname tbtacl[1222]: 1204: authorizing /sys/devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1/0-301/0-70301
Dec 21 16:49:01 hostname (udev-worker)[469]: 0-70301: Process '/usr/lib/udev/tbtacl add    /devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1/0-301/0-70301' failed with exit code 1.
Dec 21 16:49:01 hostname tbtacl[1224]: 1204: not in ACL
Dec 21 16:49:01 hostname boltd[752]: [d1030000-0091-40Gbps                     ] parent is ef9f8780-00d6...
Dec 21 16:49:01 hostname tbtacl[1227]: 1226: args: change /devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1/0-301
Dec 21 16:49:01 hostname boltd[752]: [d1030000-0091-40Gbps                     ] connected: connected (/sys/devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1/0-301/0-70301)
Dec 21 16:49:01 hostname tbtacl[1244]: 1226: authorizing /sys/devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1/0-301/0-70301
Dec 21 16:49:01 hostname boltd[752]: [d1030000-0091-40Gbps                     ] auto-auth: authmode: enabled, policy: iommu, iommu: yes -> ok
Dec 21 16:49:01 hostname tbtacl[1246]: 1226: not in ACL
Dec 21 16:49:01 hostname boltd[752]: [d1030000-0091-40Gbps                     ] auto-auth: security: iommu+user mode, key: no -> ok
Dec 21 16:49:01 hostname tbtacl[1248]: 1247: args: change /devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1/0-301/0-70301
Dec 21 16:49:01 hostname boltd[752]: [d1030000-0091-40Gbps                     ] authorize: authorization prepared for 'user' level
Dec 21 16:49:01 hostname boltd[752]: [d1030000-0091-40Gbps                     ] udev: device changed: authorizing -> authorizing
Dec 21 16:49:01 hostname boltd[752]: [d1030000-0091-40Gbps                     ] udev: device changed: authorizing -> authorizing
Dec 21 16:49:01 hostname boltd[752]: [d1030000-0091-40Gbps                     ] authorize: finished: ok (status: authorized, flags: 0)
Dec 21 16:49:01 hostname boltd[752]: [d1030000-0091-40Gbps                     ] auto-auth: authorization successful
Dec 21 16:49:01 hostname (udev-worker)[469]: 0-301: Process '/usr/lib/udev/tbtacl change /devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1/0-301' failed with exit code 1.
Dec 21 16:49:01 hostname boltd[752]: [ef9f8780-00d6-Element Hub                ] udev: device changed: authorized -> authorized
Dec 21 16:49:01 hostname tbtacl[1267]: 1247: no childs found
Dec 21 16:49:01 hostname (udev-worker)[469]: 0-70301: Process '/usr/lib/udev/tbtacl change /devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1/0-301/0-70301' failed with exit code 1.
Dec 21 16:49:01 hostname boltd[752]: [d1030000-0091-40Gbps                     ] udev: device changed: authorized -> authorized
Dec 21 16:49:03 hostname boltd[752]: probing: timeout, done: [2429049] (2000000)

@bwarden
Copy link
Member

bwarden commented Jan 2, 2025

Relevant info from dumpTB4.txt:

Dec 23 14:37:07 hostname tbtacl[682]: 680: args: change /devices/pci0000:00/0000:00:0d.3/domain0/0-0
Dec 23 14:37:07 hostname tbtacl[700]: 680: no childs found
Dec 23 14:37:07 hostname dbus-daemon[509]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' requested by ':1.18' (uid=0 pid=683 comm="/usr/libexec/boltd")
Dec 23 14:37:07 hostname (udev-worker)[478]: 0-0: Process '/usr/lib/udev/tbtacl change /devices/pci0000:00/0000:00:0d.3/domain0/0-0' failed with exit code 1.
Dec 23 14:37:07 hostname boltd[683]: bolt 0.9.8 starting up.
Dec 23 14:37:07 hostname boltd[683]: manager: initializing store
Dec 23 14:37:07 hostname boltd[683]: store: located at: /var/lib/boltd
Dec 23 14:37:07 hostname boltd[683]: config: loading user config
Dec 23 14:37:07 hostname boltd[683]: bouncer: initializing polkit
Dec 23 14:37:07 hostname boltd[683]: watchdog: enabled [pulse: 90s]
Dec 23 14:37:07 hostname boltd[683]: udev: initializing udev
Dec 23 14:37:07 hostname boltd[683]: store: loading domains
Dec 23 14:37:07 hostname boltd[683]: store: loading devices
Dec 23 14:37:07 hostname boltd[683]: [80a78780-0071                            ] store: loading device
Dec 23 14:37:07 hostname boltd[683]: [d1030000-0091                            ] store: loading device
Dec 23 14:37:07 hostname boltd[683]: [ef9f8780-00d6                            ] store: loading device
Dec 23 14:37:07 hostname boltd[683]: [e0d78780-00c2                            ] store: loading device
Dec 23 14:37:07 hostname boltd[683]: power: state located at: /run/boltd/power
Dec 23 14:37:07 hostname boltd[683]: power: force power support: no
Dec 23 14:37:07 hostname boltd[683]: udev: enumerating devices
Dec 23 14:37:07 hostname boltd[683]: [cb818780-0128-domain0                    ] newly connected [iommu+user] (/sys/devices/pci0000:00/0000:00:0d.3/domain0/0-0)
Dec 23 14:37:07 hostname boltd[683]: security level set to 'user'
Dec 23 14:37:07 hostname boltd[683]: [cb818780-0128-domain0                    ] domain: registered (bootacl: 0/0)
Dec 23 14:37:07 hostname boltd[683]: [cb818780-0128-domain0                    ] bootacl: bootacl not supported, no sync
Dec 23 14:37:07 hostname boltd[683]: [cb818780-0128-domain0                    ] udev: failed to determine if uid is stable: unknown NHI PCI id '0xa76d'
Dec 23 14:37:07 hostname boltd[683]: [cb818780-0128-domain0                    ] udev: uuid is stable: no (for NHI: 0xa76d)
Dec 23 14:37:07 hostname boltd[683]: global 'generation' set to '4'
Dec 23 14:37:07 hostname boltd[683]: [cb818780-0128-Gen12                      ] device added, status: authorized, at /sys/devices/pci0000:00/0000:00:0d.3/domain0/0-0
Dec 23 14:37:10 hostname tbtacl[1063]: 1062: args: add /devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1
Dec 23 14:37:07 hostname boltd[683]: [cb818780-0128-Gen12                      ] labeling device: INTEL Gen12
Dec 23 14:37:10 hostname tbtacl[1073]: 1062: authorizing /sys/devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1
Dec 23 14:37:07 hostname boltd[683]: [cb818780-0128-domain0                    ] dbus: exported domain at /org/freedesktop/bolt/domains/cb818780_0128_6204_ffff_ffffffffffff
Dec 23 14:37:10 hostname tbtacl[1075]: 1062: not in ACL
Dec 23 14:37:07 hostname boltd[683]: [80a78780-0071-Thunderbolt Dock G4        ] dbus: exported device at /org/freedesktop/bolt/devices/80a78780_0071...
Dec 23 14:37:11 hostname tbtacl[1082]: 1081: args: add /devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1/0-701
Dec 23 14:37:07 hostname boltd[683]: [d1030000-0091-40Gbps                     ] dbus: exported device at /org/freedesktop/bolt/devices/d1030000_0091...
Dec 23 14:37:11 hostname tbtacl[1095]: 1081: authorizing /sys/devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1/0-701
Dec 23 14:37:07 hostname boltd[683]: [ef9f8780-00d6-Element Hub                ] dbus: exported device at /org/freedesktop/bolt/devices/ef9f8780_00d6...
Dec 23 14:37:11 hostname tbtacl[1097]: 1081: not in ACL
Dec 23 14:37:07 hostname boltd[683]: [e0d78780-00c2-107064                     ] dbus: exported device at /org/freedesktop/bolt/devices/e0d78780_00c2...
Dec 23 14:37:11 hostname tbtacl[1099]: 1098: args: change /devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1
Dec 23 14:37:07 hostname boltd[683]: [cb818780-0128-Gen12                      ] dbus: exported device at /org/freedesktop/bolt/devices/cb818780_0128...
Dec 23 14:37:11 hostname tbtacl[1113]: 1098: authorizing /sys/devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1/0-701
Dec 23 14:37:11 hostname tbtacl[1115]: 1098: not in ACL
Dec 23 14:37:11 hostname tbtacl[1119]: 1117: args: change /devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1/0-701
Dec 23 14:37:11 hostname tbtacl[1136]: 1117: no childs found
Dec 23 14:37:10 hostname (udev-worker)[504]: 0-1: Process '/usr/lib/udev/tbtacl add    /devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1' failed with exit code 1.
Dec 23 14:37:10 hostname boltd[683]: [ef9f8780-00d6-Element Hub                ] parent is cb818780-0128...
Dec 23 14:37:10 hostname boltd[683]: [ef9f8780-00d6-Element Hub                ] connected: connected (/sys/devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1)
Dec 23 14:37:10 hostname boltd[683]: [ef9f8780-00d6-Element Hub                ] auto-auth: authmode: enabled, policy: iommu, iommu: yes -> ok
Dec 23 14:37:10 hostname boltd[683]: [ef9f8780-00d6-Element Hub                ] auto-auth: security: iommu+user mode, key: no -> ok
Dec 23 14:37:10 hostname boltd[683]: probing: started [1000]
Dec 23 14:37:10 hostname boltd[683]: [ef9f8780-00d6-Element Hub                ] authorize: authorization prepared for 'user' level
Dec 23 14:37:10 hostname boltd[683]: [ef9f8780-00d6-Element Hub                ] udev: device changed: authorizing -> authorizing
Dec 23 14:37:10 hostname boltd[683]: [ef9f8780-00d6-Element Hub                ] udev: device changed: authorizing -> authorizing
Dec 23 14:37:11 hostname (udev-worker)[504]: 0-701: Process '/usr/lib/udev/tbtacl add    /devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1/0-701' failed with exit code 1.
Dec 23 14:37:11 hostname boltd[683]: [d1030000-0091-40Gbps                     ] parent is ef9f8780-00d6...
Dec 23 14:37:11 hostname boltd[683]: [d1030000-0091-40Gbps                     ] connected: connected (/sys/devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1/0-701)
Dec 23 14:37:11 hostname boltd[683]: [d1030000-0091-40Gbps                     ] parent [ef9f8780-00d6-1074-ffff-ffffffffffff] not authorized
Dec 23 14:37:11 hostname boltd[683]: [d1030000-0091-40Gbps                     ] udev: device changed: connected -> connected
Dec 23 14:37:11 hostname boltd[683]: [d1030000-0091-40Gbps                     ] udev: device changed: connected -> connected
Dec 23 14:37:11 hostname boltd[683]: [ef9f8780-00d6-Element Hub                ] authorize: finished: ok (status: authorized, flags: 0)
Dec 23 14:37:11 hostname boltd[683]: [d1030000-0091-40Gbps                     ] auto-auth: authmode: enabled, policy: iommu, iommu: yes -> ok
Dec 23 14:37:11 hostname boltd[683]: [d1030000-0091-40Gbps                     ] auto-auth: security: iommu+user mode, key: no -> ok
Dec 23 14:37:11 hostname boltd[683]: [d1030000-0091-40Gbps                     ] authorize: authorization prepared for 'user' level
Dec 23 14:37:11 hostname boltd[683]: [ef9f8780-00d6-Element Hub                ] auto-auth: authorization successful
Dec 23 14:37:11 hostname (udev-worker)[504]: 0-1: Process '/usr/lib/udev/tbtacl change /devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1' failed with exit code 1.
Dec 23 14:37:11 hostname boltd[683]: [ef9f8780-00d6-Element Hub                ] udev: device changed: authorized -> authorized
Dec 23 14:37:11 hostname boltd[683]: [d1030000-0091-40Gbps                     ] authorize: finished: ok (status: authorized, flags: 0)
Dec 23 14:37:11 hostname boltd[683]: [d1030000-0091-40Gbps                     ] auto-auth: authorization successful
Dec 23 14:37:11 hostname (udev-worker)[475]: 0-701: Process '/usr/lib/udev/tbtacl change /devices/pci0000:00/0000:00:0d.3/domain0/0-0/0-1/0-701' failed with exit code 1.
Dec 23 14:37:11 hostname boltd[683]: [d1030000-0091-40Gbps                     ] udev: device changed: authorized -> authorized
Dec 23 14:37:14 hostname boltd[683]: probing: timeout, done: [2675374] (2000000)

@Aqua1ung
Copy link
Author

Aqua1ung commented Jan 3, 2025

No new insights yet. Looks like you have these two devices, right?

Yes. In the meantime I also acquired this. Same story.

@bwarden
Copy link
Member

bwarden commented Jan 3, 2025

Have you tried anything with security levels (/sys/bus/thunderbolt/devices/*/security)?
https://docs.kernel.org/admin-guide/thunderbolt.html

@Aqua1ung
Copy link
Author

Aqua1ung commented Jan 3, 2025

Have you tried anything with security levels (/sys/bus/thunderbolt/devices/*/security)? https://docs.kernel.org/admin-guide/thunderbolt.html

I didn't mess with any of that, if that's what you're asking. Here's what shows up in the settings:

Screenshot From 2025-01-03 13-03-26

As far as navigating to the location you indicated goes, the only security file I could find is as in the picture below, and contains only the word "user":

Screenshot From 2025-01-03 13-08-32

@bwarden
Copy link
Member

bwarden commented Jan 3, 2025

OK, with security set to user, can you try this process to explicitly authorized the connected devices?
https://docs.kernel.org/admin-guide/thunderbolt.html#authorizing-devices-when-security-level-is-user-or-secure

Specifically echo 1 > /sys/bus/thunderbolt/devices/<address>/authorized for each device address.

@Aqua1ung
Copy link
Author

Aqua1ung commented Jan 3, 2025 •
edited
Loading

OK, with security set to user, can you try this process to explicitly authorized the connected devices?

I just checked, and, except for the 0-0:3.1 device, all the other devices already have authorized=1:
Screenshot From 2025-01-03 13-52-48
Screenshot From 2025-01-03 13-54-19
Should I do that for the 0-0:3.1 device as well?

@bwarden
Copy link
Member

bwarden commented Jan 3, 2025

Should I do that for the 0-0:3.1 device as well?

I'm shooting in the dark (never used Thunderbolt myself and don't have hardware) but it's worth a shot. Trying to read up on Thunderbolt support to see if we're missing something, but I haven't found anything yet.

@Aqua1ung
Copy link
Author

Aqua1ung commented Jan 11, 2025 •
edited
Loading

I had some time to do some experimenting, and I have come across a major revelation: it appears that this sort of behavior also happens without(!) any dock attached whatsoever! As such, there is no need to delve into any Thunderbolt stuff whatever. Here are two logs in two scenarios: after reboot and after shutdown:

dump_no_dock_after_reboot.txt
dump_no_dock_after_shutdown.txt

This should hopefully make debugging simpler. Currently on 42840.

@Aqua1ung
Copy link
Author

Aqua1ung commented Jan 13, 2025 •
edited
Loading

I also see some reports that errors of the

Unable to change power state from D3hot to D0, device inaccessible

type might prevent boot up, and I happened upon something like that--see screenshot below.

com google Chrome

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bwarden bwarden

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@bwarden @Aqua1ung @ephut