Weblog entry #2 for sneex
See all weblog entries made by sneex.
#2
My expedition into AMD64: Section 1
Posted by sneex on Tue 26 Jun 2007 at 14:09
Of the three 'identical' AMD64 servers, two say interface eth2 is 100MBits:
e100: eth2: e100_watchdog: link up, 100Mbps, full-duplex
eth0: Tigon3 [partno(BCM95704A7) rev 2100 PHY(5704)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet 00:e0:81:47:f9:24
eth1: Tigon3 [partno(BCM95704A7) rev 2100 PHY(5704)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet 00:e0:81:47:f9:25
One states that eth0 is 100MBits:
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
eth0: Tigon3 [partno(BCM95704A7) rev 2100 PHY(5704)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet 00:e0:81:48:31:f0
eth1: Tigon3 [partno(BCM95704A7) rev 2100 PHY(5704)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet 00:e0:81:48:31:f1
Question is 'Why?' Why would Debian 4, using the DVD iso installation method, detect the same hardware differently?
So, after further research I see (for srv0) -
dmesg |grep e100
PCI: Firmware left 0000:03:08.0 e100 interrupts enabled, disabling
e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
e100: eth0: e100_probe: addr 0xfeafb000, irq 201, MAC addr 00:E0:81:48:31:E4
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
However for srv1, I see -
dmesg |grep e100
PCI: Firmware left 0000:03:08.0 e100 interrupts enabled, disabling
e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
e100: eth0: e100_probe: addr 0xfeafb000, irq 177, MAC addr 00:E0:81:47:F9:96
e100: eth2: e100_watchdog: link up, 100Mbps, full-duplex
(NOTE: The 3rd server was hosed while researching why these first two systems do not agree as to the hardware interface; so it's not reported on this AMD64 Section.)
What I am getting at is this: The hardware is the same but the installer doesn't see the same interfaces. In the long run I guess it doesn't matter. I simply want the 1GBit interfaces to plumb-up to my internal/private routes and the 100MBit interfaces to plumb-up to the public/Internet routes. As I have never seen this behavior before it struck me as a little weird.
In summary -
Server 0:
Processors 4
Model Dual Core AMD Opteron(tm) Processor 280
CPU Speed 2.39 GHz
Cache Size 1024 KB
System Bogomips 19120.69
PCI Devices 00:07.1 IDE interface: Advanced Micro Devices [AMD] AMD-8111 IDE
00:07.2 SMBus: Advanced Micro Devices [AMD] AMD-8111 SMBus 2.0
00:0a.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X IOAPIC
00:0b.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X IOAPIC
01:03.0 RAID bus controller: 3ware Inc 9550SX SATA-RAID
02:09.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
02:09.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
03:05.0 Mass storage controller: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller
03:06.0 VGA compatible controller: ATI Technologies Inc Rage XL
03:08.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100]
IDE Devices hda: Slimtype DVDRW SSW-8015S
SCSI Devices AMCC 9550SX-4LP DISK (Direct-Access)
USB Devices Linux 2.6.18-4-amd64 ohci_hcd OHCI Host Controller
Linux 2.6.18-4-amd64 ohci_hcd OHCI Host Controller
Server 1:
Processors 4
Model Dual Core AMD Opteron(tm) Processor 280
CPU Speed 2.39 GHz
Cache Size 1024 KB
System Bogomips 19143.52
PCI Devices 00:07.1 IDE interface: Advanced Micro Devices [AMD] AMD-8111 IDE
00:07.2 SMBus: Advanced Micro Devices [AMD] AMD-8111 SMBus 2.0
00:0a.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X IOAPIC
00:0b.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X IOAPIC
01:03.0 RAID bus controller: 3ware Inc 9550SX SATA-RAID
02:09.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
02:09.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
03:05.0 Mass storage controller: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller
03:06.0 VGA compatible controller: ATI Technologies Inc Rage XL
03:08.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100]
IDE Devices hda: Slimtype DVDRW SSW-8015S
SCSI Devices AMCC 9550SX-4LP DISK (Direct-Access)
USB Devices Linux 2.6.18-4-amd64 ohci_hcd OHCI Host Controller
Linux 2.6.18-4-amd64 ohci_hcd OHCI Host Controller
Looks like the same system, I see the IRQs are different, but would that be enough to cause the 100MHz Ethernet interface show up differently?
e100: eth2: e100_watchdog: link up, 100Mbps, full-duplex
eth0: Tigon3 [partno(BCM95704A7) rev 2100 PHY(5704)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet 00:e0:81:47:f9:24
eth1: Tigon3 [partno(BCM95704A7) rev 2100 PHY(5704)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet 00:e0:81:47:f9:25
One states that eth0 is 100MBits:
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
eth0: Tigon3 [partno(BCM95704A7) rev 2100 PHY(5704)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet 00:e0:81:48:31:f0
eth1: Tigon3 [partno(BCM95704A7) rev 2100 PHY(5704)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet 00:e0:81:48:31:f1
Question is 'Why?' Why would Debian 4, using the DVD iso installation method, detect the same hardware differently?
So, after further research I see (for srv0) -
dmesg |grep e100
PCI: Firmware left 0000:03:08.0 e100 interrupts enabled, disabling
e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
e100: eth0: e100_probe: addr 0xfeafb000, irq 201, MAC addr 00:E0:81:48:31:E4
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
However for srv1, I see -
dmesg |grep e100
PCI: Firmware left 0000:03:08.0 e100 interrupts enabled, disabling
e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
e100: eth0: e100_probe: addr 0xfeafb000, irq 177, MAC addr 00:E0:81:47:F9:96
e100: eth2: e100_watchdog: link up, 100Mbps, full-duplex
(NOTE: The 3rd server was hosed while researching why these first two systems do not agree as to the hardware interface; so it's not reported on this AMD64 Section.)
What I am getting at is this: The hardware is the same but the installer doesn't see the same interfaces. In the long run I guess it doesn't matter. I simply want the 1GBit interfaces to plumb-up to my internal/private routes and the 100MBit interfaces to plumb-up to the public/Internet routes. As I have never seen this behavior before it struck me as a little weird.
In summary -
Server 0:
Processors 4
Model Dual Core AMD Opteron(tm) Processor 280
CPU Speed 2.39 GHz
Cache Size 1024 KB
System Bogomips 19120.69
PCI Devices 00:07.1 IDE interface: Advanced Micro Devices [AMD] AMD-8111 IDE
00:07.2 SMBus: Advanced Micro Devices [AMD] AMD-8111 SMBus 2.0
00:0a.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X IOAPIC
00:0b.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X IOAPIC
01:03.0 RAID bus controller: 3ware Inc 9550SX SATA-RAID
02:09.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
02:09.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
03:05.0 Mass storage controller: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller
03:06.0 VGA compatible controller: ATI Technologies Inc Rage XL
03:08.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100]
IDE Devices hda: Slimtype DVDRW SSW-8015S
SCSI Devices AMCC 9550SX-4LP DISK (Direct-Access)
USB Devices Linux 2.6.18-4-amd64 ohci_hcd OHCI Host Controller
Linux 2.6.18-4-amd64 ohci_hcd OHCI Host Controller
Server 1:
Processors 4
Model Dual Core AMD Opteron(tm) Processor 280
CPU Speed 2.39 GHz
Cache Size 1024 KB
System Bogomips 19143.52
PCI Devices 00:07.1 IDE interface: Advanced Micro Devices [AMD] AMD-8111 IDE
00:07.2 SMBus: Advanced Micro Devices [AMD] AMD-8111 SMBus 2.0
00:0a.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X IOAPIC
00:0b.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X IOAPIC
01:03.0 RAID bus controller: 3ware Inc 9550SX SATA-RAID
02:09.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
02:09.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
03:05.0 Mass storage controller: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller
03:06.0 VGA compatible controller: ATI Technologies Inc Rage XL
03:08.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100]
IDE Devices hda: Slimtype DVDRW SSW-8015S
SCSI Devices AMCC 9550SX-4LP DISK (Direct-Access)
USB Devices Linux 2.6.18-4-amd64 ohci_hcd OHCI Host Controller
Linux 2.6.18-4-amd64 ohci_hcd OHCI Host Controller
Looks like the same system, I see the IRQs are different, but would that be enough to cause the 100MHz Ethernet interface show up differently?
Comments on this Entry
Posted by Anonymous (2001:0xx:0xx:0xxx:0xxx:0xxx:xx) on Tue 26 Jun 2007 at 21:34
I think it has to do with a redesign of I/O in Linux kernel. Long time since I looked into this myself. You should prob. name your devices wan and lan instead of eth0 and eth1. I have done that myself. I don't remember which is the "Debian" way of those two files I have changed.
This is what I used:
and
This is what I used:
$ more /etc/udev/rules.d/010_local.rules
# /etc/010_local.rules pcn-2335
ACTION!="add", &nb sp; GOTO="local_rules_end"
SUBSYSTEM!="net", GOTO=" local_rules_end"
# Dell 3Com 3c905C-TX/TX-M [Tornad o] internal Ehernet
# hig-lan mac 00:B0:D0:23:A8:D2
# PCI bus 3Com 3c905 100BaseTX &nbs p;[Boomerang] card
# loc-lan mac 00:60:97:A7:F7:19
KERNEL=="eth*", SYSFS{address}=="00:b0:d0:23:a8:d2", &n bsp; NAME="hig-lan"
KERNEL=="eth*", SYSFS{address}=="00:60:97:a7:f7:19", &n bsp; NAME="loc-lan"
LABEL="local_rules_end"
# eofand
$ more /etc/udev/rules.d/z25_persistent-net.rules
# This file was automatically generated& nbsp;by the /lib/udev/write_net_rules
# program, probably run by the pers istent-net-generator.rules rules file.
#
# You can modify it, as long a s you keep each rule on a sing le line.
# PCI device 10b7:9050 (3c59x)
ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", SY SFS{address}=="00:60:97:a7:f7:19", NAME="loc-lan"
# PCI device 10b7:9200 (3c59x)
ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", SY SFS{address}=="00:b0:d0:23:a8:d2", NAME="hig-lan"
[ Parent | Reply to this comment ]
Posted by Anonymous (89.20.xx.xx) on Mon 16 Jul 2007 at 17:01
By now you have probably found /etc/ifup ? :)
[ Parent | Reply to this comment ]
Posted by Anonymous (89.20.xx.xx) on Mon 16 Jul 2007 at 17:03
*cough* /etc/iftab, was it
[ Parent | Reply to this comment ]