On 23/10/2018 05:40, Andrei Borzenkov wrote:
On every systemd-based system the first place to check is journal. If the question is "how do I recognize udev messages" - "journalctl -u systemd-udevd.service" filters only messages that come from processes spawned by udev.
OK here is the output from that command: -- Reboot -- Oct 23 15:13:53 media systemd[1]: Starting udev Kernel Device Manager... Oct 23 15:13:54 media systemd[1]: Started udev Kernel Device Manager. Oct 23 15:13:56 media systemd-udevd[487]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Oct 23 15:13:56 media systemd-udevd[479]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Oct 23 15:13:56 media systemd-udevd[484]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Or you simply upload "journalctl -b" output to let others to look at it.
I has a scan through journalctl -b Here are all the things I think are relevant. I can always upload the full output if required. The hardware id of the secondary NIC is 03:00.0 It is initially named eth1 then renamed to rename3 paul@s34:~$ journalctl -b | grep -E 'e10001e|eth0|eth1|eno1|rename3|03:00.0|network' Oct 23 15:13:52 media kernel: pci 0000:03:00.0: [8086:10d3] type 00 class 0x020000 Oct 23 15:13:52 media kernel: pci 0000:03:00.0: reg 0x10: [mem 0xf7e00000-0xf7e1ffff] Oct 23 15:13:52 media kernel: pci 0000:03:00.0: reg 0x18: [io 0xd000-0xd01f] Oct 23 15:13:52 media kernel: pci 0000:03:00.0: reg 0x1c: [mem 0xf7e20000-0xf7e23fff] Oct 23 15:13:52 media kernel: pci 0000:03:00.0: PME# supported from D0 D3hot D3cold Oct 23 15:13:52 media kernel: e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 7c:05:07:0f:11:c4 Oct 23 15:13:52 media kernel: e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection Oct 23 15:13:52 media kernel: e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF Oct 23 15:13:52 media kernel: e1000e 0000:03:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode Oct 23 15:13:52 media kernel: e1000e 0000:03:00.0 0000:03:00.0 (uninitialized): registered PHC clock Oct 23 15:13:52 media kernel: e1000e 0000:03:00.0 eth1: (PCI Express:2.5GT/s:Width x1) 7c:05:07:0f:11:c5 Oct 23 15:13:52 media kernel: e1000e 0000:03:00.0 eth1: Intel(R) PRO/1000 Network Connection Oct 23 15:13:52 media kernel: e1000e 0000:03:00.0 eth1: MAC: 3, PHY: 8, PBA No: FFFFFF-0FF Oct 23 15:13:52 media kernel: e1000e 0000:00:19.0 eno1: renamed from eth0 Oct 23 15:13:52 media kernel: e1000e 0000:03:00.0 rename3: renamed from eth1 Oct 23 15:14:05 media systemd-networkd[787]: Enumeration completed Oct 23 15:14:05 media systemd-networkd[787]: lo: Link is not managed by us Oct 23 15:14:05 media systemd-networkd[787]: rename3: Link is not managed by us Oct 23 15:14:05 media systemd-networkd[787]: eno1: IPv6 successfully enabled Oct 23 15:14:05 media kernel: IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready Oct 23 15:14:07 media systemd-networkd[787]: eno1: Gained carrier Oct 23 15:14:07 media kernel: e1000e: eno1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx Oct 23 15:14:07 media kernel: e1000e 0000:00:19.0 eno1: 10/100 speed: disabling TSO Oct 23 15:14:07 media kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready Oct 23 15:14:07 media systemd-networkd[787]: eno1: DHCPv4 address 192.168.0.164/24 via 192.168.0.1 Oct 23 15:14:07 media systemd-networkd[787]: Not connected to system bus, not setting hostname. Oct 23 15:14:08 media systemd-networkd[787]: eno1: Gained IPv6LL Oct 23 15:14:08 media systemd-networkd[787]: eno1: Configured Oct 23 15:14:08 media systemd-networkd-wait-online[811]: managing: eno1 Oct 23 15:14:08 media systemd-networkd-wait-online[811]: ignoring: lo Oct 23 15:14:09 media dbus-daemon[917]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.0' (uid=100 pid=787 comm="/lib/systemd/systemd-networkd " label="unconfined") Oct 23 15:14:10 media systemd[1]: Starting Dispatcher daemon for systemd-networkd... Oct 23 15:14:11 media networkd-dispatcher[1036]: No valid path found for iwconfig Oct 23 15:14:12 media systemd[1]: Started Dispatcher daemon for systemd-networkd. Oct 23 15:14:30 media systemd[2180]: Listening on GnuPG network certificate management daemon.
If you see "renameX" interface name, the initial attempt to name interface failed and udev will retry for 90 seconds. This may account for at least half of this time.
Maybe it is trying multiple times? Just a guess.
Only the very early messages before journald is started may appear in dmesg. dmesg is kernel and we speak about user space.
OK
My usual reaction - if you knew what is relevant, you would not need to ask in the first place.
Boot with "debug printk.devkmsg=on" and upload "journalctl -b" output.
Where do I add the option "debug printk.devkmsg=on" ? If I remember correctly you can do this in GRUB at boot time but that was 2010 when I last looked into that. Is this right? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org