Skip to contentSkip to conversation

2.6.20/2.6.20-rc7 : ethX renumbered

PATCH In review Paul Rolland 6 participants 9 messages Feb 11, 2007 1 message not in the archive Networking

lore
Share & tools
lore
#0 lore raw

Hello,

I'm facing something quite strange... When booting one of these kernels (it's a new machine, I've not been running older kernels), the boot message says :

ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 19 (level, low) -> IRQ 19 sky2 v1.10 addr 0xff8fc000 irq 19 Yukon-EC (0xb6) rev 2 sky2 eth0: addr 00:18:f3:e0:5d:d4
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 16 (level, low) -> IRQ 16 sky2 v1.10 addr 0xff7fc000 irq 16 Yukon-EC (0xb6) rev 2 sky2 eth1: addr 00:18:f3:e0:36:fd

So, I'm expecting two interfaces : eth0 and eth1

Unfortunately, at the end of the boot process, I can find eth1 and eth2, something/somewhat/someone has renumbered them ;

eth1 Link encap:Ethernet HWaddr 00:18:F3:E0:36:FD
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) Interrupt:16

eth2 Link encap:Ethernet HWaddr 00:18:F3:E0:5D:D4

          inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::218:f3ff:fee0:5dd4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:42780 errors:0 dropped:0 overruns:0 frame:0
          TX packets:25519 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:61859841 (58.9 MiB)  TX bytes:2031644 (1.9 MiB)
          Interrupt:19 

This does also occurs when I boot in single user mode, so I did a quick check at the processes running then, and found udevd, but there is no reference to ethX in the configuration files, only veth :

root@riri:/Kernels/External# cd /etc/udev/
root@riri:/etc/udev# grep -r eth *
rules.d/90-modprobe.rules:ENV{VIO_TYPE}=="network",
RUN+="/sbin/modprobe -Qba ibmveth"
rules.d/90-modprobe.rules:ENV{VIO_TYPE}=="vlan",
RUN+="/sbin/modprobe -Qba iseries_veth"

Is it something expected ? Or is it because Sky2 is still EXPERIMENTAL ?

Regards,
Paul

#1 lore raw

PATCH 1/1 keep track of network interface renaming

Quoted 11 lines · Paul Rolland

I'm facing something quite strange... When booting one of these kernels (it's a new machine, I've not been running older kernels), the boot message says :

ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 19 (level, low) -> IRQ 19 sky2 v1.10 addr 0xff8fc000 irq 19 Yukon-EC (0xb6) rev 2 sky2 eth0: addr 00:18:f3:e0:5d:d4
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 16 (level, low) -> IRQ 16 sky2 v1.10 addr 0xff7fc000 irq 16 Yukon-EC (0xb6) rev 2 sky2 eth1: addr 00:18:f3:e0:36:fd

Quoted 3 lines

So, I'm expecting two interfaces : eth0 and eth1

Unfortunately, at the end of the boot process, I can find eth1 and eth2,

Unfortunately, this patch was not applied to mainline last year. Maybe this year.

Keep track about which network interface names were renamed after the network device driver printed its banner.

net/core/dev.c +4 -0
@@ -749,7 +749,11 @@ int dev_change_name(struct net_device *d
 	else if (__dev_get_by_name(newname))
 		return -EEXIST;
 	else
+	{
+		if (strncmp(newname, dev->name, IFNAMSIZ))
+			printk(KERN_INFO "%s renamed to %s\n", dev->name, newname);
 		strlcpy(dev->name, newname, IFNAMSIZ);
+	}
 
 	err = class_device_rename(&dev->class_dev, dev->name);
 	if (!err) {
#2 lore raw

RE: [PATCH] keep track of network interface renaming

Excellent Olaf !

Yes, I got a "eth0 renamed to eth2".

Quoted 2 lines

Unfortunately, this patch was not applied to mainline last year. Maybe this year.

Seconded, you have my vote for this !

Regards,
Paul

maintainer
#3 lore raw

Re: [PATCH] keep track of network interface renaming

In reply to Olaf Hering

From: Olaf Hering <[email protected]>
Date: Sun, 11 Feb 2007 13:54:23 +0100

Quoted 4 lines

Keep track about which network interface names were renamed after the network device driver printed its banner.

This is kernel log clutter.

You can ask the kernel for the list of interfaces, and use even ethtool to ask what driver each interface is associated with.

The patch wasn't applied because it really is not necessary.

A message that is not in the archive (sent off-list or not yet received): [email protected]

maintainer
#5 lore raw

Re: [PATCH] keep track of network interface renaming

From: Jason Lunz <[email protected]>
Date: Sun, 11 Feb 2007 13:27:05 -0500

Quoted 7 lines · David Miller
Quoted 6 lines

This is kernel log clutter.

You can ask the kernel for the list of interfaces, and use even ethtool to ask what driver each interface is associated with.

Quoted 7 lines
Quoted 1 line

The patch wasn't applied because it really is not necessary.

I disagree completely. I'm working right now on a udev-based system that does ethernet device renaming. It's quite difficult when working with udev to tell exactly when and why each interface was renamed, since it's typically done within initramfs where it's difficult to enable debug messages. This printk helps immensely.

You can listen on a netlink socket for these events if you want to see when they occur.

There is no need for this log message, it is superfluous.

#6 lore raw

Re: [PATCH] keep track of network interface renaming

Am 11.02.2007 19:28 schrieb David Miller:

Quoted 17 lines

From: Jason Lunz <[email protected]>
Date: Sun, 11 Feb 2007 13:27:05 -0500

Quoted 7 lines · David Miller
Quoted 6 lines

This is kernel log clutter.

You can ask the kernel for the list of interfaces, and use even ethtool to ask what driver each interface is associated with.

Quoted 6 lines
Quoted 1 line

The patch wasn't applied because it really is not necessary.

I disagree completely. I'm working right now on a udev-based system that does ethernet device renaming. It's quite difficult when working with udev to tell exactly when and why each interface was renamed, since it's typically done within initramfs where it's difficult to enable debug messages. This printk helps immensely.

Quoted 4 lines

You can listen on a netlink socket for these events if you want to see when they occur.

There is no need for this log message, it is superfluous.

I disagree. This message can be very helpful. The problem of network interfaces being renamed is a real and frequent one. A single message per interface is tolerable even if you don't actually need it. My kernel log currently produces well over 400 messages per boot, so if you want to reduce kernel log clutter, there are lots of other candidates.

Signature · 4 lines
Tilman Schmidt                          E-Mail: [email protected]
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
#7 lore raw
In reply to Paul Rolland
Quoted 13 lines · Paul Rolland

Hello,

I'm facing something quite strange... When booting one of these kernels (it's a new machine, I've not been running older kernels), the boot message says :

ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 19 (level, low) -> IRQ 19 sky2 v1.10 addr 0xff8fc000 irq 19 Yukon-EC (0xb6) rev 2 sky2 eth0: addr 00:18:f3:e0:5d:d4
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 16 (level, low) -> IRQ 16 sky2 v1.10 addr 0xff7fc000 irq 16 Yukon-EC (0xb6) rev 2 sky2 eth1: addr 00:18:f3:e0:36:fd

Quoted 4 lines

So, I'm expecting two interfaces : eth0 and eth1

Unfortunately, at the end of the boot process, I can find eth1 and eth2, something/somewhat/someone has renumbered them ;

usually distro enable persistent interface naming with udev, check /etc/iftab and see if you have something like /etc/udev/something-iftab.rules

regards,

Benoit

#8 lore raw

Hello Benoit,

Quoted 3 lines

usually distro enable persistent interface naming with udev, check /etc/iftab and see if you have something like /etc/udev/something-iftab.rules

Found this :
# This file assigns persistent names to network interfaces. # See iftab(5) for syntax.

eth0 mac 00:11:d8:a9:c0:c2 arp 1
ra0 mac 00:11:d8:b9:27:7e arp 1

As these are no MAC on my machine, I suspect this is the reason for the renaming.

I'm trying Olaf's patch to check the message is printed, and next boot is without this crap in this /etc/iftab file.

Regards,
Paul

#9 lore raw

Thanks Benoit, that was it ! Removing the entry in the iftab file stopped the renaming of the interface !

Regards,
Paul