From: Wolfgang Denk <wd@denx.de>
To: Sylvain Munaut <tnt@246tNt.com>
Cc: Asier Llano Palacios <a.llano@ziv.es>,
John Rigby <jrigby@freescale.com>,
linuxppc-embedded@ozlabs.org
Subject: Re: Stability of MPC5200 FEC
Date: Sat, 11 Feb 2006 17:08:25 +0100 [thread overview]
Message-ID: <20060211160825.DBDCA35262C@atlas.denx.de> (raw)
In-Reply-To: Your message of "Sat, 11 Feb 2006 16:28:26 +0100." <43EE029A.5040504@246tNt.com>
In message <43EE029A.5040504@246tNt.com> you wrote:
>
> > had before the Platform Device rework. But the problem is that we are
> > experiencing that the FEC stops working after a long uptime.
>
> Did you ever observe that behavior on a lite5200 ?
> What is 'long uptime' and do you have sustained transfer during that
> period ? (To try reproduice the problem).
This is a well-known problem, I'm afraid. To trigger it, it is
usually (*) sufficient to transfer a large file (700 MB or so) over
FTP to the target. Note that I've encountered the problem in the
context of the 2.4 kernel.
(*) In some cases you can run several such transfers in a row without
problem. Power-cycling the board will bring it back to "normal" mode.
It's probably Bestcomm related. See the previous discussions with
Freescale about known issues with the 2.6 Bestcomm code.
> Also, what are the 'symptoms' ? (anything in dmesg ?)
No, nothing.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Like winter snow on summer lawn, time past is time gone.
next prev parent reply other threads:[~2006-02-11 16:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 17:20 Stability of MPC5200 FEC Asier Llano Palacios
2006-02-10 18:22 ` John Rigby
2006-02-11 15:28 ` Sylvain Munaut
2006-02-11 16:08 ` Wolfgang Denk [this message]
2006-02-13 8:08 ` Asier Llano Palacios
2006-02-14 17:35 ` John Rigby
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=20060211160825.DBDCA35262C@atlas.denx.de \
--to=wd@denx.de \
--cc=a.llano@ziv.es \
--cc=jrigby@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=tnt@246tNt.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;
as well as URLs for NNTP newsgroup(s).