MPC5200 FEC problems

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

Hello Gary,

Yeah, I know this one :(

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

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

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