From: Ben Hutchings <bhutchings@solarflare.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:05:30 +0100 [thread overview]
Message-ID: <1224079530.3984.180.camel@achroite> (raw)
In-Reply-To: <76366b180810150640h230ee681wd9cb474dbe4c7045@mail.gmail.com>
On Wed, 2008-10-15 at 14:40 +0100, Andrew Paprocki wrote:
> Does anyone know if these status values imply what is wrong? Could
> this be caused by a faulty cable?
Looking at the code around this message, it appears that least
over/under-length, framing and CRC errors (and maybe others) can trigger
this. A faulty cable could certainly result in these sorts of errors,
most likely CRC errors.
"grep -r . /sys/class/net/eth0/statistics/" will show you detailed error
statistics for eth0.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2008-10-15 14:05 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 [this message]
2008-10-15 22:53 ` 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=1224079530.3984.180.camel@achroite \
--to=bhutchings@solarflare.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).