RTAI-v1.3 tulip conflict

[William Montgomery <william@opinicus.com>]

I am having a problem with rtai-1.3 conflicting with the tulip network
driver.  The CPU is a dual PIII 700MHz with 128M RAM, the kernel is 2.2.15.
The network is fine after boot up - I can ping, rlogin, nfs and others.
As soon as I do ldmod (loading basic rtai modules) the network stops
responding.  This seems to be related to SMP only, I have a CPU from the
same manufacturer with same chipsets but single processor which works
fine with rtai-1.3.  I am including dmesg output below:

[..]
PPP line discipline registered.
PPP BSD Compression module registered
tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov
eth0: Digital DS21143 Tulip rev 65 at 0xec00, 00:10:6F:02:1F:4E, IRQ 19.
eth0:  EEPROM default media type Autosense.
eth0:  Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block.
eth0:  Index #1 - Media 10baseT-FD (#4) described by a 21142 Serial PHY (2) block.
eth0:  Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY (4) block.
eth0:  Index #3 - Media 100baseTx-FD (#5) described by a 21143 SYM PHY (4) block.
eth0: Using user-specified media 10baseT(forced).

=================
Network is working fine...
./ldmod
=================

==== RT memory manager v0.2 Loaded. ====


***** STARTING THE REAL TIME SCHEDULER WITH NO LINUX *****
***** FP SUPPORT AND READY FOR A PERIODIC TIMER *****
***<> LINUX TICK AT 120 (HZ) <>***
***<> CALIBRATED CPU FREQUENCY 698803742 (HZ) <>***
***<> CALIBRATED APIC_INTERRUPT-TO-SCHEDULER LATENCY 3001 (ns) <>***
***<> CALIBRATED ONE SHOT APIC SETUP TIME 499 (ns) <>***


***** RTAI NEWLY MOUNTED (MOUNT COUNT 1) ******

eth0: 21140 transmit timed out, status f06980c5, SIA 000052ca ffff0001 fff8ffff 8ffd0008, resetting...
eth0: 21140 transmit timed out, status f06980c7, SIA 000052ca ffff0001 fff8ffff 8ffd0008, resetting...
eth0: 21140 transmit timed out, status f06980c7, SIA 000052ca ffff0001 fff8ffff 8ffd0008, resetting...

=============
Network is now broken.

Anybody have ideas?

I have also tried Donald Becker's latest tulip driver v0.92 with same
results.  The tulip driver is compiled as a kernel module.
I can recover the network by doing:
  ifconfig eth0 down
  rmmod tulip
  remod
  insmod tulip
  /etc/rc.d/rc.inet1

Suggestions welcome.

William Montgomery