[eepro100] collision problem
Marco Di Folco
marco.difolco@coresecure.com
Mon Mar 4 05:06:00 2002
This is a multi-part message in MIME format.
------=_NextPart_000_0023_01C1C36C.602E5CE0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Hello,
I am having ethernet connection issues with a Dell PowerEdge 2450 server, it
has two Intel NICs.
The system is running Red Hat Linux 6.2 with all updates applied.
The kernel version is 2.2.19 from Red Hat.
The eepro100 driver version is $Revision: 1.20.2.10 $ 2000/05/31.
Both NICs are connected to a 10/100 mbps Cisco switch.
Here are my problems:
- the NICs seem to be running at 10 mbps, half-duplex.
- ifconfig reports a huge number of collisions for both NICs.
I have lately upgraded the kernel from 2.2.14 to 2.2.19.
I think I was having the same problems before the kernel upgrade, I just
didn't notice them...
Also, close to this server, there is a Dell PowerEdge 1550 box, it also has
two Intel NICs connected to the same Cisco switch, and they are running just
fine at 100 mbps full-duplex with no collisions at all!
Though this other server is running Red Hat Linux 7.2 and kernel 2.4.9 from
Red Hat.
I attached a text file with the output of ifconfig, dmesg, mii-diag,
eepro-diag, pci-config in order to help diagnose my connection problems with
the 2450 server.
How can I force the NICs to run at 100 mbps full-duplex?
How can I get rid of the collisions?
Thanks in advance,
Marco.
------=_NextPart_000_0023_01C1C36C.602E5CE0
Content-Type: text/plain;
name="dell_2450_connection_problems.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="dell_2450_connection_problems.txt"
ifconfig output (I replaced the Internet IP with XXX...):
eth0 Link encap:Ethernet HWaddr 00:02:B3:0A:06:7E =20
inet addr:XXX.XXX.XXX.XXX Bcast:XXX.XXX.XXX.XXX =
Mask:255.255.255.240
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:30929056 errors:0 dropped:0 overruns:0 frame:0
TX packets:35314266 errors:0 dropped:0 overruns:0 carrier:0
collisions:1916335 txqueuelen:100=20
Interrupt:22 Base address:0xecc0=20
eth1 Link encap:Ethernet HWaddr 00:B0:D0:68:54:D2 =20
inet addr:10.2.1.12 Bcast:10.2.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:35432594 errors:0 dropped:0 overruns:0 frame:0
TX packets:55868203 errors:0 dropped:0 overruns:0 carrier:0
collisions:32751600 txqueuelen:100=20
Interrupt:16 Base address:0xccc0=20
dmesg ouput:
eepro100.c:v1.09j-t 9/29/99 Donald Becker =
http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
eepro100.c: $Revision: 1.20.2.10 $ 2000/05/31 Modified by Andrey V. =
Savochkin <saw@saw.sw.com.sg> and others
eepro100.c: VA Linux custom, Dragan Stancevic <visitor@valinux.com> =
2000/11/15
eth0: OEM i82557/i82558 10/100 Ethernet, 00:02:B3:0A:06:7E, I/O at =
0xecc0, IRQ 22.
Board assembly a08922-002, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0x04f4518b).
eth1: Intel PCI EtherExpress Pro100 82557, 00:B0:D0:68:54:D2, I/O at =
0xccc0, IRQ 16.
Receiver lock-up bug exists -- enabling work-around.
Board assembly 07195d-000, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0x04f4518b).
Receiver lock-up workaround activated.
cat uses obsolete /proc/pci interface
mmi-diag output:
# mii-diag eth0
Basic registers of MII PHY #1: 0000 780d 02a8 0154 05e1 0000 0000 0000.
Basic mode control register 0x0000: Auto-negotiation disabled, with
Speed fixed at 10 mbps, half-duplex.
You have link beat, and everything is working OK.
Link partner information is not exchanged when in fixed speed mode.
End of basic transceiver information.
# mii-diag eth1
Basic registers of MII PHY #1: 0000 780d 02a8 0154 05e1 41e1 0001 0000.
The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
Basic mode control register 0x0000: Auto-negotiation disabled, with
Speed fixed at 10 mbps, half-duplex.
You have link beat, and everything is working OK.
Your link partner advertised 41e1: 100baseTx-FD 100baseTx 10baseT-FD =
10baseT.
End of basic transceiver information.
eepro-diag output:
# eepro100-diag -f -aa
eepro100-diag.c:v2.05 6/13/2001 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Index #1: Found a Intel i82557/8/9 EtherExpressPro100 adapter at 0xecc0.
i82557 chip registers at 0xecc0:
0c000050 1f7ba0e4 00000000 00080002 18250000 00000600
No interrupt sources are pending.
The transmit unit state is 'Suspended'.
The receive unit state is 'Ready'.
This status is normal for an activated but idle interface.
The Command register has an unprocessed command 0c00(?!).
Index #2: Found a Intel i82557/8/9 EtherExpressPro100 adapter at 0xccc0.
i82557 chip registers at 0xccc0:
0c000050 1f7320e4 00000000 00080002 182541e1 00000600
No interrupt sources are pending.
The transmit unit state is 'Suspended'.
The receive unit state is 'Ready'.
This status is normal for an activated but idle interface.
The Command register has an unprocessed command 0c00(?!).
# eepro100-diag -f -ee
eepro100-diag.c:v2.05 6/13/2001 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Index #1: Found a Intel i82557/8/9 EtherExpressPro100 adapter at 0xecc0.
EEPROM contents, size 64x16:
00: 0200 0ab3 7e06 0503 0000 0201 4701 0000
0x08: a089 2202 4882 100c 8086 0000 0000 0000
...
0x30: 002c 0000 0000 0000 0000 0000 0000 0000
0x38: 0000 0000 0000 0000 0000 0000 0000 4631
The EEPROM checksum is correct.
Intel EtherExpress Pro 10/100 EEPROM contents:
Station address 00:02:B3:0A:06:7E.
Board assembly a08922-002, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
Sleep mode is enabled. This is not recommended.
Under high load the card may not respond to
PCI requests, and thus cause a master abort.
Index #2: Found a Intel i82557/8/9 EtherExpressPro100 adapter at 0xccc0.
EEPROM contents, size 64x16:
00: b000 68d0 d254 0400 0000 0201 4701 0000
0x08: 0719 5d00 48a2 009b 1028 0000 0000 0000
...
0x30: 0020 0000 0000 0000 0000 0000 0000 0000
0x38: 0000 0000 0000 0000 0000 0000 0000 c4f6
The EEPROM checksum is correct.
Intel EtherExpress Pro 10/100 EEPROM contents:
Station address 00:B0:D0:68:54:D2.
Receiver lock-up bug exists. (The driver work-around *is* =
implemented.)
Board assembly 07195d-000, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
Sleep mode is enabled. This is not recommended.
Under high load the card may not respond to
PCI requests, and thus cause a master abort.
# eepro100-diag -f -m
eepro100-diag.c:v2.05 6/13/2001 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Index #1: Found a Intel i82557/8/9 EtherExpressPro100 adapter at 0xecc0.
Index #2: Found a Intel i82557/8/9 EtherExpressPro100 adapter at 0xccc0.
pci-config output:
# pci-config=20
pci-config.c:v2.02 1/8/2001 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Device #1 at bus 0 device/function 0/0, 00091166.
Device #2 at bus 0 device/function 0/1, 00091166.
Device #3 at bus 0 device/function 8/0, 12298086.
Device #4 at bus 0 device/function 14/0, 47591002.
Device #5 at bus 0 device/function 15/0, 02001166.
Device #6 at bus 0 device/function 15/1, 02111166.
Device #7 at bus 0 device/function 15/2, 02201166.
------=_NextPart_000_0023_01C1C36C.602E5CE0--