* Reordered network interface names
@ 2014-02-03 9:47 Arkadiusz Bubała
2014-02-03 12:44 ` Arkadiusz Bubała
0 siblings, 1 reply; 2+ messages in thread
From: Arkadiusz Bubała @ 2014-02-03 9:47 UTC (permalink / raw)
To: linux-hotplug
[-- Attachment #1: Type: text/plain, Size: 1741 bytes --]
Hello,
I have server with S5520UR motherboard running Debian Etch (with the
latest mainline kernel 3.4). This motherboard has two integrated ports:
01:00.0 Ethernet controller [0200]: Intel Corporation 82575EB Gigabit
Network Connection [8086:10a7] (rev 02)
01:00.1 Ethernet controller [0200]: Intel Corporation 82575EB Gigabit
Network Connection [8086:10a7] (rev 02)
There also additional network adapters attached:
03:00.0 Ethernet controller [0200]: Intel Corporation 82599ES 10-Gigabit
SFI/SFP+ Network Connection [8086:10fb] (rev 01)
03:00.1 Ethernet controller [0200]: Intel Corporation 82599ES 10-Gigabit
SFI/SFP+ Network Connection [8086:10fb] (rev 01)
07:00.0 Ethernet controller [0200]: Intel Corporation 82576 Gigabit
Network Connection [8086:10c9] (rev 01)
07:00.1 Ethernet controller [0200]: Intel Corporation 82576 Gigabit
Network Connection [8086:10c9] (rev 01)
0a:00.0 Ethernet controller [0200]: Intel Corporation 82576 Gigabit
Network Connection [8086:10c9] (rev 01)
0a:00.1 Ethernet controller [0200]: Intel Corporation 82576 Gigabit
Network Connection [8086:10c9] (rev 01)
Rarely after reboot interfaces are reordered and one of them is named
eth1_rename (about 20 reboots is needed to reproduce this issue). I
tried to update udev but this didn't resolve this issue. I also tried
running udev with debug-trace but it caused that only eth0 didn't have
"_rename" suffix.
I attached udev rules file, udevinfo output. I also have full logs from
udevmonitor if needed (I have problems with attaching this file it has
1MB uncompressed and 100kB compressed).
Could you give me any advices how to solve this issue?
Thank you in advance.
PS I can't reproduce this issue on Linux kernel 2.6.35.
Best regards,
Arkadiusz
[-- Attachment #2: eth.rules --]
[-- Type: text/plain, Size: 1198 bytes --]
# This file was automatically generated by the /lib/udev/write_net_rules
# program, probably run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.
# MAC addresses must be written in lowercase.
# PCI device 0x8086:0x10fb (ixgbe)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:21:6e:6c:10", NAME="eth1"
# PCI device 0x8086:0x10fb (ixgbe)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:21:6e:6c:11", NAME="eth3"
# PCI device 0x8086:0x10a7 (igb)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:15:17:aa:eb:e8", NAME="eth0"
# PCI device 0x8086:0x10c9 (igb)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:15:17:ba:4f:30", NAME="eth4"
# PCI device 0x8086:0x10c9 (igb)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:15:17:ba:4f:31", NAME="eth5"
# PCI device 0x8086:0x10c9 (igb)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:15:17:ba:4f:32", NAME="eth6"
# PCI device 0x8086:0x10c9 (igb)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:15:17:ba:4f:33", NAME="eth7"
# PCI device 0x8086:0x10a7 (igb)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:15:17:aa:eb:e9", NAME="eth2"
[-- Attachment #3: eth0.log --]
[-- Type: text/x-log, Size: 2570 bytes --]
Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/pci0000:00/0000:00:01.0/0000:01:00.1/net/eth0':
KERNEL=="eth0"
SUBSYSTEM=="net"
DRIVER==""
ATTR{mtu}=="1500"
ATTR{type}=="1"
ATTR{netdev_group}=="0"
ATTR{flags}=="0x1003"
ATTR{speed}=="1000"
ATTR{dormant}=="0"
ATTR{addr_assign_type}=="0"
ATTR{dev_id}=="0x0"
ATTR{duplex}=="full"
ATTR{iflink}=="6"
ATTR{addr_len}=="6"
ATTR{address}=="00:15:17:aa:eb:e9"
ATTR{operstate}=="up"
ATTR{broadcast}=="ff:ff:ff:ff:ff:ff"
ATTR{tx_queue_len}=="1000"
ATTR{ifalias}==""
ATTR{ifindex}=="6"
ATTR{link_mode}=="0"
ATTR{carrier}=="1"
looking at parent device '/devices/pci0000:00/0000:00:01.0/0000:01:00.1/net':
KERNELS=="net"
SUBSYSTEMS==""
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:01.0/0000:01:00.1':
KERNELS=="0000:01:00.1"
SUBSYSTEMS=="pci"
DRIVERS=="igb"
ATTRS{irq}=="28"
ATTRS{subsystem_vendor}=="0x8086"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x020000"
ATTRS{consistent_dma_mask_bits}=="64"
ATTRS{modalias}=="pci:v00008086d000010A7sv00008086sd000034DEbc02sc00i00"
ATTRS{dma_mask_bits}=="64"
ATTRS{local_cpus}=="00000000,00000000,00000000,0000ffff"
ATTRS{device}=="0x10a7"
ATTRS{enable}=="1"
ATTRS{msi_bus}==""
ATTRS{local_cpulist}=="0-15"
ATTRS{vendor}=="0x8086"
ATTRS{subsystem_device}=="0x34de"
ATTRS{numa_node}=="-1"
looking at parent device '/devices/pci0000:00/0000:00:01.0':
KERNELS=="0000:00:01.0"
SUBSYSTEMS=="pci"
DRIVERS=="pcieport"
ATTRS{irq}=="64"
ATTRS{subsystem_vendor}=="0x8086"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x060400"
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{modalias}=="pci:v00008086d00003408sv00008086sd000034DEbc06sc04i00"
ATTRS{dma_mask_bits}=="32"
ATTRS{local_cpus}=="00000000,00000000,00000000,0000ffff"
ATTRS{device}=="0x3408"
ATTRS{enable}=="2"
ATTRS{msi_bus}=="1"
ATTRS{local_cpulist}=="0-15"
ATTRS{vendor}=="0x8086"
ATTRS{subsystem_device}=="0x34de"
ATTRS{numa_node}=="-1"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
ATTRS{uevent}==""
[-- Attachment #4: eth1.log --]
[-- Type: text/x-log, Size: 2573 bytes --]
Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/pci0000:00/0000:00:05.0/0000:03:00.0/net/eth1':
KERNEL=="eth1"
SUBSYSTEM=="net"
DRIVER==""
ATTR{mtu}=="1500"
ATTR{type}=="1"
ATTR{netdev_group}=="0"
ATTR{flags}=="0x1003"
ATTR{speed}=="10000"
ATTR{dormant}=="0"
ATTR{addr_assign_type}=="0"
ATTR{dev_id}=="0x0"
ATTR{duplex}=="full"
ATTR{iflink}=="3"
ATTR{addr_len}=="6"
ATTR{address}=="00:1b:21:6e:6c:10"
ATTR{operstate}=="up"
ATTR{broadcast}=="ff:ff:ff:ff:ff:ff"
ATTR{tx_queue_len}=="1000"
ATTR{ifalias}==""
ATTR{ifindex}=="3"
ATTR{link_mode}=="0"
ATTR{carrier}=="1"
looking at parent device '/devices/pci0000:00/0000:00:05.0/0000:03:00.0/net':
KERNELS=="net"
SUBSYSTEMS==""
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:05.0/0000:03:00.0':
KERNELS=="0000:03:00.0"
SUBSYSTEMS=="pci"
DRIVERS=="ixgbe"
ATTRS{irq}=="26"
ATTRS{subsystem_vendor}=="0x8086"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x020000"
ATTRS{consistent_dma_mask_bits}=="64"
ATTRS{modalias}=="pci:v00008086d000010FBsv00008086sd00000003bc02sc00i00"
ATTRS{dma_mask_bits}=="64"
ATTRS{local_cpus}=="00000000,00000000,00000000,0000ffff"
ATTRS{device}=="0x10fb"
ATTRS{enable}=="1"
ATTRS{msi_bus}==""
ATTRS{local_cpulist}=="0-15"
ATTRS{vendor}=="0x8086"
ATTRS{subsystem_device}=="0x0003"
ATTRS{numa_node}=="-1"
looking at parent device '/devices/pci0000:00/0000:00:05.0':
KERNELS=="0000:00:05.0"
SUBSYSTEMS=="pci"
DRIVERS=="pcieport"
ATTRS{irq}=="66"
ATTRS{subsystem_vendor}=="0x8086"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x060400"
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{modalias}=="pci:v00008086d0000340Csv00008086sd000034DEbc06sc04i00"
ATTRS{dma_mask_bits}=="32"
ATTRS{local_cpus}=="00000000,00000000,00000000,0000ffff"
ATTRS{device}=="0x340c"
ATTRS{enable}=="2"
ATTRS{msi_bus}=="1"
ATTRS{local_cpulist}=="0-15"
ATTRS{vendor}=="0x8086"
ATTRS{subsystem_device}=="0x34de"
ATTRS{numa_node}=="-1"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
ATTRS{uevent}==""
[-- Attachment #5: eth1_rename.log --]
[-- Type: text/x-log, Size: 2491 bytes --]
Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/pci0000:00/0000:00:01.0/0000:01:00.0/net/eth1_rename':
KERNEL=="eth1_rename"
SUBSYSTEM=="net"
DRIVER==""
ATTR{mtu}=="1500"
ATTR{type}=="1"
ATTR{netdev_group}=="0"
ATTR{flags}=="0x1002"
ATTR{addr_assign_type}=="0"
ATTR{dev_id}=="0x0"
ATTR{iflink}=="4"
ATTR{addr_len}=="6"
ATTR{address}=="00:15:17:aa:eb:e8"
ATTR{operstate}=="down"
ATTR{broadcast}=="ff:ff:ff:ff:ff:ff"
ATTR{tx_queue_len}=="1000"
ATTR{ifalias}==""
ATTR{ifindex}=="4"
ATTR{link_mode}=="0"
looking at parent device '/devices/pci0000:00/0000:00:01.0/0000:01:00.0/net':
KERNELS=="net"
SUBSYSTEMS==""
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:01.0/0000:01:00.0':
KERNELS=="0000:01:00.0"
SUBSYSTEMS=="pci"
DRIVERS=="igb"
ATTRS{irq}=="40"
ATTRS{subsystem_vendor}=="0x8086"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x020000"
ATTRS{consistent_dma_mask_bits}=="64"
ATTRS{modalias}=="pci:v00008086d000010A7sv00008086sd000034DEbc02sc00i00"
ATTRS{dma_mask_bits}=="64"
ATTRS{local_cpus}=="00000000,00000000,00000000,0000ffff"
ATTRS{device}=="0x10a7"
ATTRS{enable}=="1"
ATTRS{msi_bus}==""
ATTRS{local_cpulist}=="0-15"
ATTRS{vendor}=="0x8086"
ATTRS{subsystem_device}=="0x34de"
ATTRS{numa_node}=="-1"
looking at parent device '/devices/pci0000:00/0000:00:01.0':
KERNELS=="0000:00:01.0"
SUBSYSTEMS=="pci"
DRIVERS=="pcieport"
ATTRS{irq}=="64"
ATTRS{subsystem_vendor}=="0x8086"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x060400"
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{modalias}=="pci:v00008086d00003408sv00008086sd000034DEbc06sc04i00"
ATTRS{dma_mask_bits}=="32"
ATTRS{local_cpus}=="00000000,00000000,00000000,0000ffff"
ATTRS{device}=="0x3408"
ATTRS{enable}=="2"
ATTRS{msi_bus}=="1"
ATTRS{local_cpulist}=="0-15"
ATTRS{vendor}=="0x8086"
ATTRS{subsystem_device}=="0x34de"
ATTRS{numa_node}=="-1"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
ATTRS{uevent}==""
[-- Attachment #6: eth3.log --]
[-- Type: text/x-log, Size: 2575 bytes --]
Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/pci0000:00/0000:00:05.0/0000:03:00.1/net/eth3':
KERNEL=="eth3"
SUBSYSTEM=="net"
DRIVER==""
ATTR{mtu}=="1500"
ATTR{type}=="1"
ATTR{netdev_group}=="0"
ATTR{flags}=="0x1003"
ATTR{speed}=="65535"
ATTR{dormant}=="0"
ATTR{addr_assign_type}=="0"
ATTR{dev_id}=="0x0"
ATTR{duplex}=="full"
ATTR{iflink}=="5"
ATTR{addr_len}=="6"
ATTR{address}=="00:1b:21:6e:6c:11"
ATTR{operstate}=="down"
ATTR{broadcast}=="ff:ff:ff:ff:ff:ff"
ATTR{tx_queue_len}=="1000"
ATTR{ifalias}==""
ATTR{ifindex}=="5"
ATTR{link_mode}=="0"
ATTR{carrier}=="0"
looking at parent device '/devices/pci0000:00/0000:00:05.0/0000:03:00.1/net':
KERNELS=="net"
SUBSYSTEMS==""
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:05.0/0000:03:00.1':
KERNELS=="0000:03:00.1"
SUBSYSTEMS=="pci"
DRIVERS=="ixgbe"
ATTRS{irq}=="25"
ATTRS{subsystem_vendor}=="0x8086"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x020000"
ATTRS{consistent_dma_mask_bits}=="64"
ATTRS{modalias}=="pci:v00008086d000010FBsv00008086sd00000003bc02sc00i00"
ATTRS{dma_mask_bits}=="64"
ATTRS{local_cpus}=="00000000,00000000,00000000,0000ffff"
ATTRS{device}=="0x10fb"
ATTRS{enable}=="1"
ATTRS{msi_bus}==""
ATTRS{local_cpulist}=="0-15"
ATTRS{vendor}=="0x8086"
ATTRS{subsystem_device}=="0x0003"
ATTRS{numa_node}=="-1"
looking at parent device '/devices/pci0000:00/0000:00:05.0':
KERNELS=="0000:00:05.0"
SUBSYSTEMS=="pci"
DRIVERS=="pcieport"
ATTRS{irq}=="66"
ATTRS{subsystem_vendor}=="0x8086"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x060400"
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{modalias}=="pci:v00008086d0000340Csv00008086sd000034DEbc06sc04i00"
ATTRS{dma_mask_bits}=="32"
ATTRS{local_cpus}=="00000000,00000000,00000000,0000ffff"
ATTRS{device}=="0x340c"
ATTRS{enable}=="2"
ATTRS{msi_bus}=="1"
ATTRS{local_cpulist}=="0-15"
ATTRS{vendor}=="0x8086"
ATTRS{subsystem_device}=="0x34de"
ATTRS{numa_node}=="-1"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
ATTRS{uevent}==""
[-- Attachment #7: eth4.log --]
[-- Type: text/x-log, Size: 2570 bytes --]
Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/pci0000:00/0000:00:09.0/0000:07:00.0/net/eth4':
KERNEL=="eth4"
SUBSYSTEM=="net"
DRIVER==""
ATTR{mtu}=="1500"
ATTR{type}=="1"
ATTR{netdev_group}=="0"
ATTR{flags}=="0x1003"
ATTR{speed}=="1000"
ATTR{dormant}=="0"
ATTR{addr_assign_type}=="0"
ATTR{dev_id}=="0x0"
ATTR{duplex}=="full"
ATTR{iflink}=="7"
ATTR{addr_len}=="6"
ATTR{address}=="00:15:17:ba:4f:30"
ATTR{operstate}=="up"
ATTR{broadcast}=="ff:ff:ff:ff:ff:ff"
ATTR{tx_queue_len}=="1000"
ATTR{ifalias}==""
ATTR{ifindex}=="7"
ATTR{link_mode}=="0"
ATTR{carrier}=="1"
looking at parent device '/devices/pci0000:00/0000:00:09.0/0000:07:00.0/net':
KERNELS=="net"
SUBSYSTEMS==""
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:09.0/0000:07:00.0':
KERNELS=="0000:07:00.0"
SUBSYSTEMS=="pci"
DRIVERS=="igb"
ATTRS{irq}=="32"
ATTRS{subsystem_vendor}=="0x0000"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x020000"
ATTRS{consistent_dma_mask_bits}=="64"
ATTRS{modalias}=="pci:v00008086d000010C9sv00000000sd00003550bc02sc00i00"
ATTRS{dma_mask_bits}=="64"
ATTRS{local_cpus}=="00000000,00000000,00000000,0000ffff"
ATTRS{device}=="0x10c9"
ATTRS{enable}=="1"
ATTRS{msi_bus}==""
ATTRS{local_cpulist}=="0-15"
ATTRS{vendor}=="0x8086"
ATTRS{subsystem_device}=="0x3550"
ATTRS{numa_node}=="-1"
looking at parent device '/devices/pci0000:00/0000:00:09.0':
KERNELS=="0000:00:09.0"
SUBSYSTEMS=="pci"
DRIVERS=="pcieport"
ATTRS{irq}=="68"
ATTRS{subsystem_vendor}=="0x8086"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x060400"
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{modalias}=="pci:v00008086d00003410sv00008086sd000034DEbc06sc04i00"
ATTRS{dma_mask_bits}=="32"
ATTRS{local_cpus}=="00000000,00000000,00000000,0000ffff"
ATTRS{device}=="0x3410"
ATTRS{enable}=="2"
ATTRS{msi_bus}=="1"
ATTRS{local_cpulist}=="0-15"
ATTRS{vendor}=="0x8086"
ATTRS{subsystem_device}=="0x34de"
ATTRS{numa_node}=="-1"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
ATTRS{uevent}==""
[-- Attachment #8: eth5.log --]
[-- Type: text/x-log, Size: 2570 bytes --]
Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/pci0000:00/0000:00:09.0/0000:07:00.1/net/eth5':
KERNEL=="eth5"
SUBSYSTEM=="net"
DRIVER==""
ATTR{mtu}=="1500"
ATTR{type}=="1"
ATTR{netdev_group}=="0"
ATTR{flags}=="0x1003"
ATTR{speed}=="1000"
ATTR{dormant}=="0"
ATTR{addr_assign_type}=="0"
ATTR{dev_id}=="0x0"
ATTR{duplex}=="full"
ATTR{iflink}=="8"
ATTR{addr_len}=="6"
ATTR{address}=="00:15:17:ba:4f:31"
ATTR{operstate}=="up"
ATTR{broadcast}=="ff:ff:ff:ff:ff:ff"
ATTR{tx_queue_len}=="1000"
ATTR{ifalias}==""
ATTR{ifindex}=="8"
ATTR{link_mode}=="0"
ATTR{carrier}=="1"
looking at parent device '/devices/pci0000:00/0000:00:09.0/0000:07:00.1/net':
KERNELS=="net"
SUBSYSTEMS==""
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:09.0/0000:07:00.1':
KERNELS=="0000:07:00.1"
SUBSYSTEMS=="pci"
DRIVERS=="igb"
ATTRS{irq}=="42"
ATTRS{subsystem_vendor}=="0x0000"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x020000"
ATTRS{consistent_dma_mask_bits}=="64"
ATTRS{modalias}=="pci:v00008086d000010C9sv00000000sd00003550bc02sc00i00"
ATTRS{dma_mask_bits}=="64"
ATTRS{local_cpus}=="00000000,00000000,00000000,0000ffff"
ATTRS{device}=="0x10c9"
ATTRS{enable}=="1"
ATTRS{msi_bus}==""
ATTRS{local_cpulist}=="0-15"
ATTRS{vendor}=="0x8086"
ATTRS{subsystem_device}=="0x3550"
ATTRS{numa_node}=="-1"
looking at parent device '/devices/pci0000:00/0000:00:09.0':
KERNELS=="0000:00:09.0"
SUBSYSTEMS=="pci"
DRIVERS=="pcieport"
ATTRS{irq}=="68"
ATTRS{subsystem_vendor}=="0x8086"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x060400"
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{modalias}=="pci:v00008086d00003410sv00008086sd000034DEbc06sc04i00"
ATTRS{dma_mask_bits}=="32"
ATTRS{local_cpus}=="00000000,00000000,00000000,0000ffff"
ATTRS{device}=="0x3410"
ATTRS{enable}=="2"
ATTRS{msi_bus}=="1"
ATTRS{local_cpulist}=="0-15"
ATTRS{vendor}=="0x8086"
ATTRS{subsystem_device}=="0x34de"
ATTRS{numa_node}=="-1"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
ATTRS{uevent}==""
[-- Attachment #9: eth6.log --]
[-- Type: text/x-log, Size: 2570 bytes --]
Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/pci0000:00/0000:00:0a.0/0000:0a:00.0/net/eth6':
KERNEL=="eth6"
SUBSYSTEM=="net"
DRIVER==""
ATTR{mtu}=="1500"
ATTR{type}=="1"
ATTR{netdev_group}=="0"
ATTR{flags}=="0x1003"
ATTR{speed}=="1000"
ATTR{dormant}=="0"
ATTR{addr_assign_type}=="0"
ATTR{dev_id}=="0x0"
ATTR{duplex}=="full"
ATTR{iflink}=="9"
ATTR{addr_len}=="6"
ATTR{address}=="00:15:17:ba:4f:32"
ATTR{operstate}=="up"
ATTR{broadcast}=="ff:ff:ff:ff:ff:ff"
ATTR{tx_queue_len}=="1000"
ATTR{ifalias}==""
ATTR{ifindex}=="9"
ATTR{link_mode}=="0"
ATTR{carrier}=="1"
looking at parent device '/devices/pci0000:00/0000:00:0a.0/0000:0a:00.0/net':
KERNELS=="net"
SUBSYSTEMS==""
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:0a.0/0000:0a:00.0':
KERNELS=="0000:0a:00.0"
SUBSYSTEMS=="pci"
DRIVERS=="igb"
ATTRS{irq}=="33"
ATTRS{subsystem_vendor}=="0x0000"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x020000"
ATTRS{consistent_dma_mask_bits}=="64"
ATTRS{modalias}=="pci:v00008086d000010C9sv00000000sd00003550bc02sc00i00"
ATTRS{dma_mask_bits}=="64"
ATTRS{local_cpus}=="00000000,00000000,00000000,0000ffff"
ATTRS{device}=="0x10c9"
ATTRS{enable}=="1"
ATTRS{msi_bus}==""
ATTRS{local_cpulist}=="0-15"
ATTRS{vendor}=="0x8086"
ATTRS{subsystem_device}=="0x3550"
ATTRS{numa_node}=="-1"
looking at parent device '/devices/pci0000:00/0000:00:0a.0':
KERNELS=="0000:00:0a.0"
SUBSYSTEMS=="pci"
DRIVERS=="pcieport"
ATTRS{irq}=="69"
ATTRS{subsystem_vendor}=="0x8086"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x060400"
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{modalias}=="pci:v00008086d00003411sv00008086sd000034DEbc06sc04i00"
ATTRS{dma_mask_bits}=="32"
ATTRS{local_cpus}=="00000000,00000000,00000000,0000ffff"
ATTRS{device}=="0x3411"
ATTRS{enable}=="2"
ATTRS{msi_bus}=="1"
ATTRS{local_cpulist}=="0-15"
ATTRS{vendor}=="0x8086"
ATTRS{subsystem_device}=="0x34de"
ATTRS{numa_node}=="-1"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
ATTRS{uevent}==""
[-- Attachment #10: eth7.log --]
[-- Type: text/x-log, Size: 2572 bytes --]
Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/pci0000:00/0000:00:0a.0/0000:0a:00.1/net/eth7':
KERNEL=="eth7"
SUBSYSTEM=="net"
DRIVER==""
ATTR{mtu}=="1500"
ATTR{type}=="1"
ATTR{netdev_group}=="0"
ATTR{flags}=="0x1003"
ATTR{speed}=="1000"
ATTR{dormant}=="0"
ATTR{addr_assign_type}=="0"
ATTR{dev_id}=="0x0"
ATTR{duplex}=="full"
ATTR{iflink}=="10"
ATTR{addr_len}=="6"
ATTR{address}=="00:15:17:ba:4f:33"
ATTR{operstate}=="up"
ATTR{broadcast}=="ff:ff:ff:ff:ff:ff"
ATTR{tx_queue_len}=="1000"
ATTR{ifalias}==""
ATTR{ifindex}=="10"
ATTR{link_mode}=="0"
ATTR{carrier}=="1"
looking at parent device '/devices/pci0000:00/0000:00:0a.0/0000:0a:00.1/net':
KERNELS=="net"
SUBSYSTEMS==""
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:0a.0/0000:0a:00.1':
KERNELS=="0000:0a:00.1"
SUBSYSTEMS=="pci"
DRIVERS=="igb"
ATTRS{irq}=="31"
ATTRS{subsystem_vendor}=="0x0000"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x020000"
ATTRS{consistent_dma_mask_bits}=="64"
ATTRS{modalias}=="pci:v00008086d000010C9sv00000000sd00003550bc02sc00i00"
ATTRS{dma_mask_bits}=="64"
ATTRS{local_cpus}=="00000000,00000000,00000000,0000ffff"
ATTRS{device}=="0x10c9"
ATTRS{enable}=="1"
ATTRS{msi_bus}==""
ATTRS{local_cpulist}=="0-15"
ATTRS{vendor}=="0x8086"
ATTRS{subsystem_device}=="0x3550"
ATTRS{numa_node}=="-1"
looking at parent device '/devices/pci0000:00/0000:00:0a.0':
KERNELS=="0000:00:0a.0"
SUBSYSTEMS=="pci"
DRIVERS=="pcieport"
ATTRS{irq}=="69"
ATTRS{subsystem_vendor}=="0x8086"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x060400"
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{modalias}=="pci:v00008086d00003411sv00008086sd000034DEbc06sc04i00"
ATTRS{dma_mask_bits}=="32"
ATTRS{local_cpus}=="00000000,00000000,00000000,0000ffff"
ATTRS{device}=="0x3411"
ATTRS{enable}=="2"
ATTRS{msi_bus}=="1"
ATTRS{local_cpulist}=="0-15"
ATTRS{vendor}=="0x8086"
ATTRS{subsystem_device}=="0x34de"
ATTRS{numa_node}=="-1"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
ATTRS{uevent}==""
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Reordered network interface names
2014-02-03 9:47 Reordered network interface names Arkadiusz Bubała
@ 2014-02-03 12:44 ` Arkadiusz Bubała
0 siblings, 0 replies; 2+ messages in thread
From: Arkadiusz Bubała @ 2014-02-03 12:44 UTC (permalink / raw)
To: linux-hotplug
Hello,
thank you for your response.
On 03.02.2014 13:02, Tom Gundersen wrote:
> > Rarely after reboot interfaces are reordered and one of them is named
>
> > eth1_rename (about 20 reboots is needed to reproduce this issue). I
> > tried to update udev but this didn't resolve this issue. I also tried
> > running udev with debug-trace but it caused that only eth0 didn't have
> > "_rename" suffix.
>
> This is a known problem, when trying to rename interfaces in the
> kernel namespace (ethX). It is fixed in recent versions of udev (what
> versions did you try?) by udev automatically renaming all the
> interfaces in a deterministic way (google for predictable interface
> names).
>
I understand. I tried the latest udev which compile on this system
(udev-137 downloaded from pkgs.fedoraproject.org). But now I know that
it's fixed in version 197. I'll try to resolve this issue manually.
Thank you for your help.
>
> I suggest you either use the most recent udev, or call your interfaces
> something else, lanX, say.
>
> HTH,
>
> Tom
>
Best regards,
Arkadiusz
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-02-03 12:44 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-02-03 9:47 Reordered network interface names Arkadiusz Bubała
2014-02-03 12:44 ` Arkadiusz Bubała
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).