<div class="gmail_quote">On Sun, Jan 10, 2010 at 11:37 AM, Frank Merrill <span dir="ltr"><<a href="mailto:fmerrill1@gmail.com">fmerrill1@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5">
</div></div>I see that you have already RMA'd this board.<br>
One thing I would have made certain of is that you don't have a Duplex mismatch.<br>
I'm guessing that on the ZOTAC board the network tools are setting the<br>
interface to Autonegotiation or Full-duplex.<br>
You can use 'ethtool eth0' to see what it is currently set to.<br>
<br>
In any case, if that interface is trying to autonegotiate, but your<br>
switch doesn't do that (or maybe doesn't do it properly) you could<br>
have a duplex mismatch.<br>
If a 100Mbs interface on the switch is trying to autonegotiate, but it<br>
can't, it would, by standards, fall back to the default of<br>
100/Half-duplex.<br>
If the switch is for whatever reason setting itself to<br>
100/Half-duplex, then you would get the errors you are seeing, and<br>
they would increment a lot more rapidly under higher loads. This<br>
would occur if the Zotac was at 100/FD and the switch could have some<br>
of it's transmit traffic 'stepped on' by the Zotac, causing frames<br>
that are damaged in some way.<br>
The Zotac would then see those frames as being receive errors.<br>
Basically if one side is not the same as the other, you will see<br>
errors on at least one end.<br>
So, what this comes down to is that if you have the same issues on the<br>
new board, then maybe the problem is the switchport being at<br>
Half-duplex.<br>
Whether you can change that on your switch or not, I have no idea.<br>
If your USB adapter doesn't show the issue, maybe it is running at<br>
Half-duplex, or maybe it is autonegotiating correctly with the switch<br>
port?<br>
<br>
Of course, it most definitely could still have been the hardware on the board.<br>
Almost all such cases I have seen in 22 years have been<br>
non-intentional mis-configuration.<br>
If the problem does recur, you can always try checking the Zotac<br>
interface, and if it is set to Full-duplex, instead set it to<br>
Half-duplex and see if the issue ceases. If so, then you may want to<br>
see if the switch is configurable to get both sides at Full-duplex.<br>
<br>
Here's hoping you get the new board and it 'Just Works'.<br>
<font color="#888888"><br>
Frank<br>
</font><div><div><br></div></div></blockquote><div><br></div></div>Thanks for the response Frank. I actually downloaded and played with ethtool during my troubleshooting before RMA'ing the board. It was set to full-duplex and I tried to use ethtool to adjust the settings but for some reason it wouldn't let me change anything. I tried forcing to half-duplex, I tried turning autoneg off, and I tried forcing to 100mbps or even 10mbps, every time it told me that it could not set the values. Oh well, we'll just have to see what the new board brings.<br>
<br>-Greg<br>