From: Kumar Gala <galak@kernel.crashing.org>
To: Scott Coulter <scott.coulter@cyclone.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Gianfar tx-babbling-errors
Date: Wed, 18 Feb 2009 11:03:34 -0600 [thread overview]
Message-ID: <F122E3A2-3054-4BC9-9C06-0ADE590A8AFC@kernel.crashing.org> (raw)
In-Reply-To: <43EB80E07C42E1408726E4905FB96B04C0769D@CYBORG3.cyclone.com>
On Feb 18, 2009, at 10:16 AM, Scott Coulter wrote:
>
> Hi all,
>
> As a simple stress test for my board with an MPC8572E and an
> MPC8568E on
> it, I setup both processors to boot linux 2.6.27.6 with an NFS root
> and
> then perform repeated native compiles of a linux kernel over NFS.
> After
> running for 4 days straight or so with between 250-300 build cycles
> per
> processor, I stopped the builds and ran ethtool to look for any odd
> statistics. Both processors reported non-zero values for
> tx-babbling-errors. Both processors reported around 1300
> tx-babbling-errors out of about 80,000,000 Tx packets. Should I be
> concerned about the tx-babbling-errors? What conditions would cause
> these errors to be reported?
>
> Thanks,
> Scott
I'm told this will occur when:
Transmitted frame > MAXFRM and MACCFG2[Huge En] = 0.
- k
next prev parent reply other threads:[~2009-02-18 17:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 16:16 Gianfar tx-babbling-errors Scott Coulter
2009-02-18 17:03 ` Kumar Gala [this message]
2009-02-18 17:22 ` Scott Coulter
2009-02-18 17:29 ` Kumar Gala
2009-02-18 20:45 ` Scott Coulter
2009-02-19 16:17 ` Scott Coulter
2009-02-19 16:29 ` Kumar Gala
2009-02-19 16:38 ` Scott Coulter
2009-02-19 16:48 ` sjoyeau
2009-02-19 17:03 ` Kumar Gala
2009-02-19 17:29 ` Scott Coulter
2009-02-20 19:16 ` Haruki Dai-R35557
2009-02-20 20:59 ` Scott Coulter
2009-02-20 21:32 ` Haruki Dai-R35557
2009-02-24 16:58 ` Scott Coulter
2009-03-03 16:33 ` Scott Coulter
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=F122E3A2-3054-4BC9-9C06-0ADE590A8AFC@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=scott.coulter@cyclone.com \
/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