From: Roman Fietze <roman.fietze@telemotive.de>
To: linuxppc-dev@lists.ozlabs.org
Subject: MPC5200B FEC_IEVENT_RFIFO_ERROR leading to Link is Down
Date: Tue, 10 Nov 2009 13:47:33 +0100 [thread overview]
Message-ID: <200911101347.33837.roman.fietze@telemotive.de> (raw)
Hello,
When having high traffic on the MPC5200B ATA (MWDMA2), FEC (100MBit)
and LPC (MTD FLASH read) I will get the typical
=46EC_IEVENT_RFIFO_ERROR's.
Without the FLASH reads, that we use to stress the probably existing
LPC arbiter or MPC5200B silicon bug when running UDMA2+LPC, and which
should not happen using MWDMA2+LPC, I could not yet reproduce the
=46EC_IEVENT_RFIFO_ERROR.
Now comes the problem: since the PHY driver rework followed by John
Bonesio's fix (rev 37ccd92f55c6c6) to avoid accessing the DIO bus at
interrupt context, this now sometimes causes an irrecoverable link
down (PHY: f0003000:00 - Link is Down). This patch is of course
necessary to avoid a panic.
I can reproduce that on the current DENX/master using an own board
very close to the Lite5200B. This board runs fine under the old
2.4.25, of course also sometimes showing the FEC FIFO error.
Any ideas?
Roman
=2D-=20
Roman Fietze Telemotive AG B=FCro M=FChlhausen
Breitwiesen 73347 M=FChlhausen
Tel.: +49(0)7335/18493-45 http://www.telemotive.de
reply other threads:[~2009-11-10 12:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200911101347.33837.roman.fietze@telemotive.de \
--to=roman.fietze@telemotive.de \
--cc=linuxppc-dev@lists.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