[eepro100] No resources, can't fill rx buffer
Jim Reese
jreese@google.com
Tue, 12 Jun 2001 18:07:54 -0700
A number of our machines are having problems with the eepro100 hanging
under moderate to high network load. Here's a sample of the messages:
May 28 13:17:45 google12 kernel: eth0: card reports no resources.
May 28 13:19:37 google12 kernel: eth0: can't fill rx buffer (force 0)!
May 28 13:19:37 google12 kernel: eth0: restart the receiver after a possible hang.
May 28 13:19:37 google12 kernel: eth0: card reports no resources.
May 28 13:20:26 google12 kernel: 0: 14 00000000.
May 28 13:20:26 google12 kernel: eth0: can't fill rx buffer (force 1)!
May 28 13:20:26 google12 kernel: eth0: card reports no resources.
mii-diag reports:
Using the default interface 'eth0'.
Basic registers of MII PHY #1: 3000 782d 02a8 0154 05e1 41e1 0001 0000.
The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
Basic mode control register 0x3000: Auto-negotiation enabled.
You have link beat, and everything is working OK.
Your link partner advertised 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
End of basic transceiver informaion.
While eepro100-diag says:
Index #1: Found a Intel i82557/8/9 EtherExpressPro100 adapter at 0xde80.
The driver is 1.20.2.10.
Any help with fixing this would be appreciated.
Jim Reese
Chief Operations Engineer
Google, Inc.
jim@google.com