Am 23.06.2015 um 01:28 schrieb Andrei Karas: >> We switched to the new persistent interface naming scheme in 220-7. >> >> Can you tell use, what interface names you had before the upgrade (via >> >> and what you get after the upgrade? >> >> What's the ifconfig -a output before and after the upgrade? >> > ifconfig -a with 215-18 > > eth1 Link encap:Ethernet HWaddr 00:40:f4:5a:22:14 > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > eth3 Link encap:Ethernet HWaddr bc:5f:f4:b0:ce:33 > inet addr:x.x.x.x Bcast:x.x.x.x Mask:255.255.255.224 > inet6 addr: fe80::be5f:f4ff:feb0:ce33/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:17357982 errors:0 dropped:0 overruns:0 frame:0 > TX packets:10333457 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:23770406556 (22.1 GiB) TX bytes:1305235119 (1.2 GiB) > Interrupt:20 Memory:f0500000-f0520000 > > eth3.10 Link encap:Ethernet HWaddr bc:5f:f4:b0:ce:33 > inet6 addr: fe80::be5f:f4ff:feb0:ce33/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:2843 errors:0 dropped:0 overruns:0 frame:0 > TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:378119 (369.2 KiB) TX bytes:738 (738.0 B) > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:65536 Metric:1 > RX packets:18 errors:0 dropped:0 overruns:0 frame:0 > TX packets:18 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:1030 (1.0 KiB) TX bytes:1030 (1.0 KiB) > > Now cant install new udev and reboot, but in ifconfig -a was "eth1" and > "renamed" or "renamed1" > >> >> Is this a virtual machine? > No, this is real hardware > >> >> Can you attach your /etc/udev/rules.d/70-persistent-net.rules >> > > Also while i boot with 220-7, boot was very slow, and in console was message > something like network slow or not working. > > grep "eth" from dmesg boot with 215-18: > [ 1.347094] 8139too 0000:03:01.0 eth0: RealTek RTL8139 at > 0xffffc90003148000, 00:40:f4:5a:22:14, IRQ 19 > [ 6.217538] e1000e 0000:00:19.0 eth1: registered PHC clock > [ 6.217539] e1000e 0000:00:19.0 eth1: (PCI Express:2.5GT/s:Width x1) > bc:5f:f4:b0:ce:33 > [ 6.217539] e1000e 0000:00:19.0 eth1: Intel(R) PRO/1000 Network Connection > [ 6.217587] e1000e 0000:00:19.0 eth1: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF > [ 11.331006] [drm:intel_opregion_setup] Public ACPI methods supported > [ 11.336695] [drm:intel_dsm_pci_probe] no _DSM method for intel device > [ 13.315529] 8139too 0000:03:01.0 rename2: renamed from eth0 > [ 13.324942] systemd-udevd[560]: renamed network interface eth0 to rename2 > [ 13.518739] e1000e 0000:00:19.0 eth3: renamed from eth1 > [ 13.526391] 8139too 0000:03:01.0 eth1: renamed from rename2 > [ 13.526394] systemd-udevd[568]: renamed network interface eth1 to eth3 > [ 13.535314] systemd-udevd[560]: renamed network interface eth0 to eth1 > [ 21.082465] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready > [ 21.083235] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready > [ 22.496925] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready > [ 23.515636] IPv6: ADDRCONF(NETDEV_UP): eth3.10: link is not ready > [ 26.113628] e1000e: eth3 NIC Link is Up 1000 Mbps Full Duplex, Flow > Control: None > [ 26.114409] IPv6: ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready > [ 26.115256] IPv6: ADDRCONF(NETDEV_CHANGE): eth3.10: link becomes ready > > and grep "eth" from dmesg boot with 220-7 > [ 1.345592] 8139too 0000:03:01.0 eth0: RealTek RTL8139 at > 0xffffc90008190000, 00:40:f4:5a:22:14, IRQ 19 > [ 1.481367] e1000e 0000:00:19.0 eth1: registered PHC clock > [ 1.481368] e1000e 0000:00:19.0 eth1: (PCI Express:2.5GT/s:Width x1) > bc:5f:f4:b0:ce:33 > [ 1.481368] e1000e 0000:00:19.0 eth1: Intel(R) PRO/1000 Network Connection > [ 1.481405] e1000e 0000:00:19.0 eth1: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF > [ 10.739090] [drm:intel_opregion_setup] Public ACPI methods supported > [ 10.744202] [drm:intel_dsm_pci_probe] no _DSM method for intel device > [ 12.181475] 8139too 0000:03:01.0 rename2: renamed from eth0 > [ 107.297643] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
I think the only real solution for this is to switch to the new network interface naming scheme. The old one (based on 70-persistent-net.rules) is susceptible to such breakage. To switch to the new interface naming scheme, see /usr/share/doc/udev/README.Debian.gz -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
