Re: mii-diag returns strange errors
2006/11/16, Wojciech Ziniewicz <wojciech.ziniewicz@gmail.com>:
There are many of theese in dmesg ... this bad checksums are generated
by p2p software (looking on the ports) but i'm not shure if it is a
hardware problem or the bad soft that is not respecting
isos/rfc's/other norms...
What is very interesing - i've renegotiated link few times and the
error count was the same.., now I did mii-diag --reset --verbose eth0
few times and the error counts are interesting - look :
beta wojtek # mii-diag --verbose --reset eth1 | grep error
Receive errors 56821
Rx symbol errors 0.
Rx 10Mbps Early End-Of-Frame errors 2128.
Rx 100Mbps Early End-Of-Frame errors 1300.
Tx jabber errors 0.
beta wojtek # mii-diag --verbose --reset eth1 | grep error
Receive errors 56565
Rx symbol errors 0.
Rx 10Mbps Early End-Of-Frame errors 2128.
Rx 100Mbps Early End-Of-Frame errors 1300.
Tx jabber errors 0.
beta wojtek # mii-diag --verbose --reset eth1 | grep error
Receive errors 56821
Rx symbol errors 0.
Rx 10Mbps Early End-Of-Frame errors 2128.
Rx 100Mbps Early End-Of-Frame errors 1300.
Tx jabber errors 0.
beta wojtek #
I dont't understand that....
Cisco shows nothing, i changed the patchcord to a really good one ,
finally i'll change the kernel (vanilla 2.6.15 + p-o-m ) to a newer
2.6.17 (the newest that supports imq) ...
--
Wojciech Ziniewicz | jid:zeth@chrome.pl
http://silenceproject.org | http://zetho.wordpress.com
Reply to: