From: Wolfgang Denk <wd@denx.de>
To: David Jander <david.jander@protonic.nl>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Which way to store log in flash on mpc8xx?
Date: Tue, 20 Sep 2005 20:07:58 +0200 [thread overview]
Message-ID: <20050920180758.9020C353AB3@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 20 Sep 2005 11:17:39 +0200." <200509201117.40454.david.jander@protonic.nl>
In message <200509201117.40454.david.jander@protonic.nl> you wrote:
>
> Is there something like memtest86 for linux-ppc (i.e. written in portable C)?
Yes, there is. Run the system with root file system mounted over NFS,
and then put some load on the system, like by compiling the linux
kernel on the target. Anything else which adds DMA load does not
hurt, either. In such a situation, with a lots of context switches,
stress on the memory management system and having a lots of DMA
traffic going on you may see some memory problems. Unfortunately none
of the standard memory tests will catch thse, as the tests usually
provide only plain read / write accesses, while the problems show up
only in burst mode, i. e. when filling the caches and/or doing DMA.
There is an attempt of a burst mode memory test in the U-Boot code,
but I have to admit that I didn't work to show the exact problem on
the system it was written for.
> Hmm, but.... there is no data corruption. I have not seen one file on flash
> that had other data than intended, and that inspite of the GC freaking out.
Maybe there is no corruption of the data in flash. But are you sure
that correct data are loaded to and read from RAM? We had a similar
problem on a board where data got corrupted only when doing a lot of
transfers flash->RAM.
> That commit only changed 3 files, non of them directly related to jffs2 code,
This is correct.
> and only seemed to add support for FUJITSU flash chips. What am I missing?
> MTD developers say that cvs from march-2005 _is_ broken, so there must be some
Yes, of course it's broken. Like all computer code. There are a
couple of known issues (especially with NAND flash), but I don't
think they could explain the type of problems you are seeing.
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
Einstein argued that there must be simplified explanations of nature,
because God is not capricious or arbitrary. No such faith comforts
the software engineer. - Fred Brooks, Jr.
next prev parent reply other threads:[~2005-09-20 18:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-19 9:55 Which way to store log in flash on mpc8xx? David Jander
2005-09-19 15:09 ` Frank
2005-09-19 15:37 ` Wolfgang Denk
2005-09-19 17:26 ` David Jander
2005-09-19 19:21 ` Wolfgang Denk
2005-09-20 9:17 ` David Jander
2005-09-20 18:07 ` Wolfgang Denk [this message]
2005-11-29 1:06 ` David Ho
2005-11-29 14:17 ` David Jander
2005-09-19 18:40 ` Shawn Jin
2005-09-19 19:07 ` Jörn Engel
2005-09-19 19:29 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2005-09-20 20:25 Eli Brin
2005-11-29 15:37 Fillod Stephane
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=20050920180758.9020C353AB3@atlas.denx.de \
--to=wd@denx.de \
--cc=david.jander@protonic.nl \
--cc=linuxppc-embedded@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).