From: Stephen Hemminger <shemminger@osdl.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Ethernet packet loss - frame errors
Date: Mon, 16 Oct 2006 20:00:18 +0000 [thread overview]
Message-ID: <20061016130018.387835d3@freekitty> (raw)
In-Reply-To: <452F4DA6.8030505@expertron.co.za>
On Sat, 14 Oct 2006 15:18:32 +0200
Justin Schoeman <justin@expertron.co.za> wrote:
> Stephen Hemminger wrote:
> > On Fri, 13 Oct 2006 10:26:14 +0200
> > Justin Schoeman <justin@expertron.co.za> wrote:
> >
> >> Hi all,
> >>
> >> I have the following problem. A Linux box configured as a bridge. One
> >> interface connects to the router via a crossover cable, the other
> >> connects to a switch via the cable that used to go to the router.
> >>
> >> Now I get the following:
> >>
> >> [root@localhost net]# ifconfig eth3
> >> eth3 Link encap:Ethernet HWaddr 00:03:2D:07:61:5D
> >> UP BROADCAST MULTICAST MTU:1500 Metric:1
> >> RX packets:1969134 errors:0 dropped:0 overruns:0 frame:176459
> >> TX packets:2186662 errors:0 dropped:0 overruns:0 carrier:0
> >> collisions:0 txqueuelen:1000
> >> RX bytes:492595115 (469.7 Mb) TX bytes:579725462 (552.8 Mb)
> >> Interrupt:17
> >>
> >> eth3 is the interface that connects to the switch. As you can see, 1 in
> >> 10 rx packets are framing errors.
> >>
> >> What are possible causes for this? The cable is a constant, so is not
> >> likely to cause problems, so what else can possibly cause such a high
> >> number of frame errors?
> >>
> >> Any help appreciated.
> >>
> >> Thanks,
> >>
> >> Justin
> >>
> >
> > What speed and driver?
>
> sky 2 driver, hardcoded for 100Mbps full duplex.
>
In that driver, frame errors come from receiving fragments. Fragments
are any packet shorter 64 bytes and has an invalid CRC.
These might occur if you have got a duplex mismatch.
--
Stephen Hemminger <shemminger@osdl.org>
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-10-16 20:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 8:26 [LARTC] Ethernet packet loss - frame errors Justin Schoeman
2006-10-13 8:34 ` Andrei Sandu
2006-10-13 8:44 ` Justin Schoeman
2006-10-13 19:10 ` Stephen Hemminger
2006-10-14 13:18 ` Justin Schoeman
2006-10-16 14:09 ` Justin Schoeman
2006-10-16 20:00 ` Stephen Hemminger [this message]
2006-11-01 19:47 ` Stephen Hemminger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061016130018.387835d3@freekitty \
--to=shemminger@osdl.org \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.