From: Stephen Hemminger <shemminger@vyatta.com>
To: "Andrew Paprocki" <andrew@ishiboo.com>
Cc: netdev@vger.kernel.org
Subject: Re: sky2 rx errors printing to the console
Date: Wed, 15 Oct 2008 15:53:42 -0700 [thread overview]
Message-ID: <20081015155342.3deba033@speedy> (raw)
In-Reply-To: <76366b180810150640h230ee681wd9cb474dbe4c7045@mail.gmail.com>
On Wed, 15 Oct 2008 14:40:58 +0100
"Andrew Paprocki" <andrew@ishiboo.com> wrote:
> sky2 eth0: rx error, status 0xba0202 length 186
> sky2 eth0: rx error, status 0xba0220 length 186
> sky2 eth0: rx error, status 0xba0202 length 186
> sky2 eth0: rx error, status 0xba0202 length 186
> sky2 eth0: rx error, status 0x1390202 length 313
> sky2 eth0: rx error, status 0x1680202 length 360
> sky2 eth0: rx error, status 0xba0202 length 186
> sky2 eth0: rx error, status 0xf40202 length 244
> sky2 eth0: rx error, status 0xba0202 length 186
The status field is:
+------------+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 length | | | | | | | | | | | | | | |
+------------+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^
| | | | | | | | | | | | | +- Rx FIFO Overflow
| | | | | | | | | | | | +--- CRC Error
| | | | | | | | | | | +-----
| | | | | | | | | | +------- Fragment
| | | | | | | | | +--------- Too Long
| | | | | | | | +----------- MII Error
| | | | | | | +------------- Bad flow control
| | | | | | +--------------- Good flow control
| | | | | +----------------- Rx Ok
| | | | +------------------- Broadcast
| | | +--------------------- Multicast
| | +----------------------- Runt
| +------------------------ Jabber
+------------------------- VLAN
Your packets have ehtther CRC error or MII Error set
prev parent reply other threads:[~2008-10-15 22:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 13:40 sky2 rx errors printing to the console Andrew Paprocki
2008-10-15 14:05 ` Ben Hutchings
2008-10-15 22:53 ` Stephen Hemminger [this message]
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=20081015155342.3deba033@speedy \
--to=shemminger@vyatta.com \
--cc=andrew@ishiboo.com \
--cc=netdev@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.