22.10.2018 22:24, Paul Groves пишет:
On 22/10/2018 19:25, Andrei Borzenkov wrote:
This is Debian specific patch. Number is kernel interface index. "rename%u" is supposed to be temporary until interface got renamed to final name.
Well this at least explains why I have never seen this. Normally use SUSE so never come across this before.
Output from udev rules: paul@s34:~$ cat /lib/udev/rules.d/80-net-setup-link.rules # do not edit this file, it will be overwritten on update
SUBSYSTEM!="net", GOTO="net_setup_link_end"
IMPORT{builtin}="path_id"
ACTION!="add", GOTO="net_setup_link_end"
IMPORT{builtin}="net_setup_link"
NAME=="", ENV{ID_NET_NAME}!="", NAME="$env{ID_NET_NAME}"
LABEL="net_setup_link_end"
Streetlight effect ...
Almost... As I said, already posted to Ubuntu forum. Is there an Ubuntu list like this one? I am please to say that the OpenSUSE list has never failed me so far :)
I usually start with checking logs. udev fails to rename interface; logs should contain error message with error number (or error string) which may give some starting point. Booting with "debug" on kernel command line (or enabling it specifically for udevd) could be helpful too.
OK, so I assume you are saying that udev is what is configuring my NICs at boot?
Where did I say it? udev is responsible for creating device aliases and renaming network interfaces. In your case renaming of network interface fails for whatever reason.
How do I check the udev log?
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. Or you simply upload "journalctl -b" output to let others to look at it.
I have tried the following. Where do I check the udev log? When I disable the secondary NIC in the BIOS everything is normal. When it is enabled booting takes about 3 mins longer.
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.
I had a look at dmesg.
Only the very early messages before journald is started may appear in dmesg. dmesg is kernel and we speak about user space.
See the output relevant to intel drive below.
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.
The weird thing is, in the BIOS ASPM OS control is on. But dmesg still says it does not have access. Strange...
So now I have disabled ASPM in the BIOS. Those two lines have gone from dmesg but the rest of the messages are still the same. So it is not that.
Also, you can see where the NICs are renamed from eth0 and eth1 to eno0 and rename3. So it doesn't appear to have failed to rename them at that stage.
Output from Dmesg: paul@s34:~$ dmesg | grep e1000e [ 0.958274] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k [ 0.958362] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [ 0.958595] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 1.055224] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock [ 1.143128] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 7c:05:07:0f:11:c4 [ 1.143189] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection [ 1.143261] e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF [ 1.143337] e1000e 0000:03:00.0: Disabling ASPM L1 [ 1.143379] e1000e 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control [ 1.143629] e1000e 0000:03:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 1.198213] e1000e 0000:03:00.0 0000:03:00.0 (uninitialized): registered PHC clock [ 1.251840] e1000e 0000:03:00.0 eth1: (PCI Express:2.5GT/s:Width x1) 7c:05:07:0f:11:c5 [ 1.251844] e1000e 0000:03:00.0 eth1: Intel(R) PRO/1000 Network Connection [ 1.251930] e1000e 0000:03:00.0 eth1: MAC: 3, PHY: 8, PBA No: FFFFFF-0FF [ 1.252554] e1000e 0000:00:19.0 eno1: renamed from eth0 [ 1.280245] e1000e 0000:03:00.0 rename3: renamed from eth1 [ 107.974069] e1000e: eno1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx [ 107.974072] e1000e 0000:00:19.0 eno1: 10/100 speed: disabling TSO
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org