My network engineers tell me that when they sniff the packets sent between devboard_82’s that there is no crc in the frame
And wonder what a crc error means in this case. Can you shed any light on this?
How long is your network cable? If the cable is short I am afraid that there may be a hardware
problem on your card. I have been running huge amount of network traffic to a devboard 82
during the last two days and I only got 3 errors so far.
I had a chance to add some debugging info in the Ethernet driver.
What I’m seeing are crc errors.
Driver version is 18.104.22.168 2003/03/31
Everything is definitely hooking up as 100-FD
Which version of arch/cris/drivers/ethernet.c are you using? There has been a problem where UDP
performance was bad but I don't think that would cause frame errors to be reported. Are the errors
reported on transmit or receive? Does the problem occur with several different devboards? I can't
say that I have seen the problem but I don't know if I ever have checked the frame error counters
when using UDP.
Try the following:
1. Check that the driver gets the correct duplex (in e100_chec_duplex). Should probably be full
if you use a switch.
2. Find out which error that occurs by adding debug in e100nw_interrupt, update_rx_stats and
has a udp based application that runs on the axis/axis82 platforms running on
all versions of the dev env. Among other thing we track packet loss. We're
seeing a number of dropped