[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: mii-diag returns strange errors

2006/11/14, Nate Duehr <nate@natetech.com>:
Any CRC errors in ifconfig ?
mothing :

         RX packets:396500237 errors:0 dropped:0 overruns:0 frame:0
         TX packets:407722478 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:3367117297 (3211.1 Mb)  TX bytes:2546303903 (2428.3 Mb)
         Base address:0xef80 Memory:dffe0000-e0000000

Has the Cisco ever been rebooted while the Linux box stayed up?
(Instant errors there...)

no - cisco is _always_ up ..

Can you look at the error counters on your port in the Cisco or get
someone else to send them to you?

i've sent message about that problem to my isp...

Check that both sides are hard-coded to 100/Full or whatever you're
using.  Autonegotiation can be problematic between some manufacturers.

Smells like a bad cable.

mii-diag --verbose --debug :
here is eth0 http://paste.debian.net/16624
here is eth1 http://paste.debian.net/16625
eth1 and eth0 are onboard gigabit intel cards (i have an intel entry
server board that model i don't remember)
eth2 - is a cheap 10$ NIC - this is the only NIC that seems to be
clean - main traffic goes through this card :

I'll check the cable - i don't see any errors and users don't report
any problems except acces to the machine that has theese eth's
onboard... (transfer is breaking sometimes)

... any help will be appreciated ...
Wojciech Ziniewicz            |  jid:zeth@chrome.pl
http://silenceproject.org       | http://zetho.wordpress.com

Reply to: