[Bug 1188428] New: udev: failed to get device info: could not read 'authorized': No such file or directory
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1188428 Bug ID: 1188428 Summary: udev: failed to get device info: could not read 'authorized': No such file or directory Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: opensuse@mike.franken.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Starting with kernel 5.13.0-1 (Jul 09) on boot I always get an error message (see subject) from boltd regarding device cd010000-0060-XPS 9370. All messages from boltd: boltd[1189]: bolt 0.9.1 starting up. boltd[1189]: manager: initializing store boltd[1189]: store: located at: /var/lib/boltd boltd[1189]: config: loading user config boltd[1189]: bouncer: initializing polkit boltd[1189]: watchdog: enabled [pulse: 90s] boltd[1189]: udev: initializing udev boltd[1189]: store: loading domains boltd[1189]: [cd010000-0060-domain? ] store: loading domain boltd[1189]: journal: opened for 'cd010000-0060'; size: 0 bytes boltd[1189]: [cd010000-0060-domain? ] domain: registered (bootacl: 16/16) boltd[1189]: store: loading devices boltd[1189]: [00cd30c8-3205 ] store: loading device boltd[1189]: [cd010000-0060 ] store: loading device boltd[1189]: global 'generation' set to '3' boltd[1189]: [da010000-0070 ] store: loading device boltd[1189]: power: state located at: /run/boltd/power boltd[1189]: power: force power support: yes boltd[1189]: udev: found 1 domain boltd[1189]: udev: enumerating devices boltd[1189]: probing: adding /sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0 to roots boltd[1189]: [cd010000-0060-domain0 ] bootacl: synchronizing journal boltd[1189]: security level set to 'user' boltd[1189]: [cd010000-0060-domain0 ] connected: as domain0 [user] (/sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0/0000:04:00.0/0000:05:00.0/domain0) boltd[1189]: [cd010000-0060-XPS 9370 ] udev: failed to get device info: could not read 'authorized': No such file or directory boltd[1189]: [cd010000-0060-XPS 9370 ] parent is (null)... boltd[1189]: [cd010000-0060-XPS 9370 ] store: updating device boltd[1189]: [cd010000-0060-XPS 9370 ] connected: unknown (/sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0/0000:04:00.0/0000:05:00.0/domain0/0-0) boltd[1189]: [00cd30c8-3205-TS3 Plus ] parent is cd010000-0060... boltd[1189]: [00cd30c8-3205-TS3 Plus ] connected: authorized (/sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0/0000:04:00.0/0000:05:00.0/domain0/0-0/0-3) boltd[1189]: [cd010000-0060-domain0 ] dbus: exported domain at /org/freedesktop/bolt/domains/cd010000_0060_6d18_a364_e809ccc32820 boltd[1189]: [00cd30c8-3205-TS3 Plus ] dbus: exported device at /org/freedesktop/bolt/devices/00cd30c8_3205... boltd[1189]: [cd010000-0060-XPS 9370 ] dbus: exported device at /org/freedesktop/bolt/devices/cd010000_0060... boltd[1189]: [da010000-0070-XPS 13 9370 ] dbus: exported device at /org/freedesktop/bolt/devices/da010000_0070... boltd[1189]: probing: started [1000] boltd[1189]: [00cd30c8-3205-TS3 Plus ] udev: device changed: authorized -> authorized boltd[1189]: probing: timeout, done: [2974874] (2000000) System info: Operating System: openSUSE Tumbleweed 20210715 KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.13.1-1-default (64-bit) Graphics Platform: X11 Processors: 8 �� Intel�� Core��� i7-8550U CPU @ 1.80GHz Memory: 15,0 GiB of RAM Graphics Processor: Mesa DRI Intel�� UHD Graphics 620 This is a DELL XPS 9370 notebook. -- You are receiving this mail because: You are the assignee for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1188428
https://bugzilla.suse.com/show_bug.cgi?id=1188428#c1
Takashi Iwai
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1188428
https://bugzilla.suse.com/show_bug.cgi?id=1188428#c2
--- Comment #2 from Michael Hirmke
The device still works as expected, or does it fail, too?
I'm not sure, because I don't even know excactly, which device this is. I have problems with my thunderbolt ports for a long time now, but if this has anything to do with this message, I don't know. -- You are receiving this mail because: You are the assignee for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1188428
https://bugzilla.suse.com/show_bug.cgi?id=1188428#c3
Takashi Iwai
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1188428
https://bugzilla.suse.com/show_bug.cgi?id=1188428#c4
--- Comment #4 from Michael Hirmke
Yes, that's something to do with thunderbolt port, judging from the error log.
Adding Oliver to Cc as it's about TB.
Really with the ports or with thunderbolt at all? It is clear to me, that boltd is the thunderbolt daemon, so that there might be a thunderbolt problem, but where do you find a hint regarding the ports? But just in case: I also have the problems again, that both thunderbolt ports are not completely usable. 1. The system does not recognize all power supplies (even the original DELL ones), when connected to one of the two thunderbolt ports on the left side of the notebook. It works for all power supplies connected to the USB-C port on the right side. 2. All non thunderbolt and some of the thunderbolt devices with whatever cable connected to one of the two thunderbolt ports won't work or at least won't work fully. I often get the message "bad cable" - but I tried about 10 or 12 different cables specified for thunderbolt and high speed data transfers. 3. Everything works when booting Windows 10 - it even boots from a disk connected to one of the thunderbolt ports with an adapter. Not a single error message is found in the Windows eventlog. -- You are receiving this mail because: You are the assignee for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1188428
https://bugzilla.suse.com/show_bug.cgi?id=1188428#c5
--- Comment #5 from Oliver Neukum
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1188428
https://bugzilla.suse.com/show_bug.cgi?id=1188428#c6
--- Comment #6 from Oliver Neukum
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1188428
https://bugzilla.suse.com/show_bug.cgi?id=1188428#c7
--- Comment #7 from Michael Hirmke
1. You are operating under the assumption that all Type C ports of a system need to be equal. That is just not the case. It is perfectly possible and in accordance with the specifications to build a Type C port that does not support USB Power Delivery or does not support the voltages or amperages needed to power the system. Power supplies working only on some ports is not a bug.
I know that, but on this notebook with two thunderbolt ports and one USB-C port all three ports are capable to power the system. And - as I wrote - for the thunderbolt ports it works with some power supplies (for example my docking station) and doesn't work with others (for example two out of three DELL power supplies). For the USB-C port it always works. Same with many devices - always works connected to USB-C, often doesn't work connected to thunderbolt. And it always works on windows.
2. That is a different issue. Please make a separate bugzilla entry for it.
Ok. -- You are receiving this mail because: You are the assignee for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1188428
https://bugzilla.suse.com/show_bug.cgi?id=1188428#c8
--- Comment #8 from Michael Hirmke
Could you revert
6f3badead6a078cf3c71f381f9d84ac922984a00 ("thunderbolt: Hide authorized attribute if router does not support PCIe tunnels")
or do you need a test kernel?
A test kernel would be great. -- You are receiving this mail because: You are the assignee for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1188428
https://bugzilla.suse.com/show_bug.cgi?id=1188428#c9
Michael Hirmke
participants (1)
-
bugzilla_noreply@suse.com