collisions 200% of Tx on 10BaseT (21140, .90q, Samsung SC1200-TX)

[Monty]

An update:

As it turns out, the collisions occur only between the machines on my
network using Xircom CEM 10/100 adapters and the Tulips.  Other cards
on the network have no collision problems talking to the Tulips.
Thus, this does not seem to be a Tulip problem.

I also bought a bunch of other Tulips to try this out with (they're
cheap, it's my budgeted hobby ;-) and all exhibit the same behavior
talking to the Xircoms.  The Xircoms can talk to any other machines on
the net without trouble.

So, this doesn't seem to be a Tulip problem.

I did notice one thing when pinging the Tulip-bearing server from the
Xircom-powered notebooks; the first (three?  My memory is a bit fuzzy
as I write this) pings are about 2ms; after that, pings drop into the
serious sub-millisecond range.  Happens every time I do it.  Could
either the Tulip or Xircom driver be 'pulling out all the stops' after
the first few packets, not allowing the other side to ack?  Actually,
looking at this, it seems logical that it would be the Xircom driver
doing this, not the Tulip.

>It seems important to me, that the same equipment (including the 3c509B
>NIC) worked fine under 2.0.x kernels.
>So it seems to me, that it's the tcpip driver in the 2.2 kernels that is 
>a bit too fast or something.

All my machines are 2.0 based at the moment, so this isn't (solely) a
2.2 issue.

Donald; I realize now that this is not a Tulip driver bug.  Does the
delay issue seem like a plausible thing to ping the Xircom driver
author about?  

Monty