I’m seeing some strange Ethernet behavior on my lan.
I have to systems that communicate fine over 100TX
Netgear FA 310Tx cards. There are also a few other
10baseT cards on the next that work fine. I’ve had
this problem with two different 10/100 hubs.
The problem is when I’ve tried to work with a
test embedded system. The drivers load, but the
communications are spotty to impossible. In some
cases I can copy a file, but only if initiated
from a specific node. This has happened with
an Adastra board, and now a Crystal rackmount
system. The chips on these boards are completely
different, but the results are the same.
The strangest part is that the problem is only
between one of the 100TX Netgear systems.
The only thing unique about the system that
has the problem is that it is very fast,
a 650Mhz PIII.
Anyone seen anything like this before?
Mitchell Schoenbrun --------- maschoen@pobox.com
Mitchell Schoenbrun wrote:
I’m seeing some strange Ethernet behavior on my lan.
I have to systems that communicate fine over 100TX
Netgear FA 310Tx cards. There are also a few other
10baseT cards on the next that work fine. I’ve had
this problem with two different 10/100 hubs.
The problem is when I’ve tried to work with a
test embedded system. The drivers load, but the
communications are spotty to impossible. In some
cases I can copy a file, but only if initiated
from a specific node. This has happened with
an Adastra board, and now a Crystal rackmount
system. The chips on these boards are completely
different, but the results are the same.
The strangest part is that the problem is only
between one of the 100TX Netgear systems.
The only thing unique about the system that
has the problem is that it is very fast,
a 650Mhz PIII.
Anyone seen anything like this before?
Mitchell Schoenbrun --------- > maschoen@pobox.com
Hi Mitchell,
We have been having similar problems. I made a posting last week on the
matter (Occasional missed deadlines on QNX4) where we see “hitches” in
our simulations as one subsystem fails to report on time. Correlated
with these misses a netinfo messages that normally I would have
attributed to hardware. But we are having this same behavior on two
different sets of hardware. The computer that shows the network
problems is also fast, 733Mhz. Perhaps this is what you are seeing?
Dean