From: "Paul Rolland" <rol@witbe.net>
To: "'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>
Cc: <rol@as2917.net>
Subject: 2.6.20/2.6.20-rc7 : ethX renumbered
Date: Sun, 11 Feb 2007 12:28:37 +0100 [thread overview]
Message-ID: <011001c74dcf$c60c1c80$2101a8c0@donald> (raw)
[-- Attachment #1: Type: text/plain, Size: 2064 bytes --]
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
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3715 bytes --]
next reply other threads:[~2007-02-11 12:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-11 11:28 Paul Rolland [this message]
2007-02-11 12:54 ` [PATCH] keep track of network interface renaming Olaf Hering
2007-02-11 13:29 ` Paul Rolland
2007-02-11 17:55 ` David Miller
[not found] ` <20070211182704.GA14021@avocado.homenet>
2007-02-11 18:28 ` David Miller
2007-02-11 22:35 ` Tilman Schmidt
2007-02-11 13:04 ` 2.6.20/2.6.20-rc7 : ethX renumbered Benoit Boissinot
2007-02-11 13:14 ` Paul Rolland
2007-02-11 13:35 ` Paul Rolland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='011001c74dcf$c60c1c80$2101a8c0@donald' \
--to=rol@witbe.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rol@as2917.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome