linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: linuxppc-dev@ozlabs.org
Subject: MPC5200 FEC problems
Date: Mon, 25 Aug 2008 09:36:07 -0600	[thread overview]
Message-ID: <48B2D167.40008@mlbassoc.com> (raw)

I'm adding the Analogue & Micro Boa (MPC5200/B) platform to the
public 2.6.26 tree.  Under heavy network load (sometimes even
not so heavy!), I get this error:
   net eth0: FEC_IEVENT_RFIFO_ERROR
I've read the thread about how this leads to an incorrect call
to the PHY code in the ISR.  It's good to know that part of the
problem is being worked on.

My question is - what exactly does this error imply?  Looking at
the MPC5200 manual doesn't give much info - just that there was
a Rx FIFO error.

I'm also perplexed by the fact that I have two slightly different
Boa boards (same CPU rev, speed, etc).  About the only thing that's
different is the SDRAM setup.  One board is rock solid while the
other gets this error almost immediately.

Also, I sometimes get a Tx timeout on this platform (the one that
fails as above).
   net eth0: transmit timed out
Note that I don't have any trouble with this platform running RedBoot
or eCos, just Linux :-(

Here's the basic info on my platform:

root@ppc_target:~ cat /proc/cpuinfo
processor       : 0
cpu             : G2_LE
clock           : 396.000000MHz
revision        : 1.4 (pvr 8082 2014)
bogomips        : 49.40
timebase        : 24750000

Ideas?  Any help graciously accepted.

n.b. I'm not currently subscribed to this list, so please CC
me on any replies.

Thanks

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

             reply	other threads:[~2008-08-25 15:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-25 15:36 Gary Thomas [this message]
2008-08-26  6:18 ` MPC5200 FEC problems Wolfram Sang

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=48B2D167.40008@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=linuxppc-dev@ozlabs.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).