SIOCADDRT: Invalid argument bug?

[Brian Wong]

I am running RedHat Linux 5.2 on a 486DX-100 with three network cards:

eth0: 3c59x (Vortex) card, 10bT, using the 3c59x driver
eth1: 3c905b (Cyclone) card, 100b-TX, using the 3c59x driver
eth2: DEC DC21041, 10Mb/s, using the tulip driver

The Cyclone is plugged into a LinkSys 10/100 5-port hub, and services
Pentium/PII Win95 machines which also have 3c905b's.  The Vortex is a
combo card and services a 10base-2 segment.  The DEC plugs into a cable
modem.

The 3c59x driver is compiled into the kernel.  When the system starts
up, the following net messages appear:

Swansea University Computer Society IPX 0.34 for NET3.035
IPX Portions Copyright (c) 1995 Caldera, Inc.
Appletalk 0.17 for Linux NET3.035
3c59x.c:v0.99H 11/17/98 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
eth0: 3Com 3c590 Vortex 10Mbps at 0xff80,  00:a0:24:4e:b7:8b, IRQ 11
  32K byte-wide RAM 1:1 Rx:Tx split, 10base2 interface.
  Media override to transceiver type 3 (10base2).
eth0: Overriding PCI latency timer (CFLT) setting of 64, new value is
248.
eth1: 3Com 3c905B Cyclone 100baseTx at 0xfc80,  00:10:5a:e5:c0:eb, IRQ 9

  8K byte-wide RAM 5:3 Rx:Tx split, 100baseTX interface.
  Media override to transceiver type 0 (10baseT).
  Enabling bus-master transmits and whole-frame receives.
SIOCADDRT: Invalid argument
tulip.c:v0.89H 5/23/98 becker@cesdis.gsfc.nasa.gov
eth2: Digital DC21041 Tulip at 0xfc00, 21041 mode, 00 80 c8 4d b6 f7,
IRQ 12.
eth2:21041 Media information at 30, default media 0800 (Autosense).
eth2:  21041 media #0, 10baseT.
eth2:  21041 media #0, 10baseT.
Using DHCP for eth2... Local host is cr25463-a...done.

I've tried both versions 0.99E and 0.99H of the 3c59x driver, but the IO
error message stays there.  It is definitely connected with the Cyclone
card.  I disabled each interface in turn and restarted the server; the
error goes away when eth1 is disabled. Does anyone else get this? I'm
thinking this error might have something to do with the card's
initialization problems.

I also have another problem.  While copying files 3MB or larger from
Win95 to the Linux box (using FTP or Samba), errors are introduced into
the files.  This is not the fault of the hard drive, Win95, FTP, or
Samba.  I know this information is a little vague, but I'm wondering if
anyone else has seen this happen.