RE: 2.6.20/2.6.20-rc7 : ethX renumbered

2007-02-11 Thread Paul Rolland
Thanks Benoit, that was it ! Removing the entry in the iftab file
stopped the renaming of the interface !

Regards,
Paul

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


RE: 2.6.20/2.6.20-rc7 : ethX renumbered

2007-02-11 Thread Paul Rolland
Hello Benoit,

> 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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: 2.6.20/2.6.20-rc7 : ethX renumbered

2007-02-11 Thread Benoit Boissinot

On 2/11/07, Paul Rolland <[EMAIL PROTECTED]> wrote:

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 :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 :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 ;


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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


2.6.20/2.6.20-rc7 : ethX renumbered

2007-02-11 Thread 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 :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 :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 :
 
[EMAIL PROTECTED]:/Kernels/External# cd /etc/udev/
[EMAIL PROTECTED]:/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


smime.p7s
Description: S/MIME cryptographic signature


2.6.20/2.6.20-rc7 : ethX renumbered

2007-02-11 Thread 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 :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 :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 :
 
[EMAIL PROTECTED]:/Kernels/External# cd /etc/udev/
[EMAIL PROTECTED]:/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


smime.p7s
Description: S/MIME cryptographic signature


Re: 2.6.20/2.6.20-rc7 : ethX renumbered

2007-02-11 Thread Benoit Boissinot

On 2/11/07, Paul Rolland [EMAIL PROTECTED] wrote:

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 :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 :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 ;


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
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


RE: 2.6.20/2.6.20-rc7 : ethX renumbered

2007-02-11 Thread Paul Rolland
Hello Benoit,

 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


-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


RE: 2.6.20/2.6.20-rc7 : ethX renumbered

2007-02-11 Thread Paul Rolland
Thanks Benoit, that was it ! Removing the entry in the iftab file
stopped the renaming of the interface !

Regards,
Paul

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/