All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang@pengutronix.de>
To: Gary Thomas <gary@mlbassoc.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: MPC5200 FEC problems
Date: Tue, 26 Aug 2008 08:18:41 +0200	[thread overview]
Message-ID: <20080826061841.GA4253@pengutronix.de> (raw)
In-Reply-To: <48B2D167.40008@mlbassoc.com>

[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]

Hello Gary,

On Mon, Aug 25, 2008 at 09:36:07AM -0600, Gary Thomas wrote:

> 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

Yeah, I know this one :(

> 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.

In deed, the manual seems not very helpful. The description of the set FIFO
status bit did not help me that much.

> 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.

I'm not sure if this is really of importance, but do the boards have
different PHYs?

> Note that I don't have any trouble with this platform running RedBoot
> or eCos, just Linux :-(
Try this patch and please report if it worked for you:

http://www.nabble.com/-PATCH--MPC52XX:-Don't-touch-pipelining-for-MPC5200B-td19028341.html

All the best,

   Wolfram

-- 
  Dipl.-Ing. Wolfram Sang | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2008-08-26  6:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-25 15:36 MPC5200 FEC problems Gary Thomas
2008-08-26  6:18 ` Wolfram Sang [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=20080826061841.GA4253@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --cc=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 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.