[eepro100] Driver Problem with Compaq DL 360

[Wolfgang Breyha]

Hi!

My configuriations are the following:

four pieces of
Compaq Proliant DL-360 Single P3/866 128MB
2x Onboard Etherexpress 100
RedHat 7.0
Kernel 2.2.18 (compliled with kgcc), no modules, everything compiled directly into kernel itself

eepro100.c is the original supplied with 2.2.18.

Cards are both configured static.
eth0 is 10.1.65.54 to 10.1.65.57
eth1 is 192.168.0.2 to 192.168.0.5

All four have the same problem:
kernel reports the following bootmsg:
--------
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:50:8B:E0:2F:CF, IRQ 5.
  Board assembly 727095-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).
  Receiver lock-up workaround activated.
eth1: OEM i82557/i82558 10/100 Ethernet, 00:50:8B:E0:2F:DF, IRQ 7.
  Board assembly 727095-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).
  Receiver lock-up workaround activated.
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
----------
then when the cards get initialized system reports:
Jan  5 13:15:16 lvsroute2 network: Bringing up interface lo:  succeeded
Jan  5 13:15:16 lvsroute2 network: Bringing up interface eth0:  succeeded
Jan  5 13:15:16 lvsroute2 network: Bringing up interface eth1:  succeeded

and in about 50%(!) of initialization one of the two cards reports:
ethx: card reports no RX buffers
ethx: eepro100: cmd_wait for(0xfffffff0) timedout with(0xfffffff0)!
.
.
.

The last one repeats until a network restart.
I've also seen messages with values (0xffffff80) and (0x70). But most time it is (0xfffffff0).

Any suggestions?
If you need more infos, tell me!

Regards, Wolfgang Breyha

-- 
 /     Um ein tadelloses Mitglied einer Schafherde      \
/    sein zu können, muß man vor allem ein Schaf sein    \
\ Wolfgang Breyha <wbreyha@gmx.net> - http://mash.nwy.at /
 \     Operations Center - Netway Communications AG     /