From: pieterg@gmx.com (pieterg)
To: linux-arm-kernel@lists.infradead.org
Subject: pxa3xx_nand issues
Date: Wed, 22 Sep 2010 19:12:24 +0200 [thread overview]
Message-ID: <201009221912.24905.pieterg@gmx.com> (raw)
In my search for the cause of the huge number of single/double bit errors
I'm experiencing on colibri pxa320/310 devices, I've come across this
commit
http://git.kernel.org/?p=linux/kernel/git/ycmiao/pxa-linux-2.6.git;a=commit;h=7f9938d0fd6c778bd0ce296a3e3b50266de2b892
According to the commitlog, it attempts to work around an issue regarding
non-page-aligned reads.
The workaround seems to force page-aligned access, by dropping the offset
within the page (column address bytes).
However, in my setup (with a jffs2 filesystem on nand), non-page-aligned
reads never occur, but non-page-aligned writes occur very frequently.
(during the jffs2 gc).
These are also affected by this commit, while the commitlog does not state
whether or not the same issue would occur for the program command, and in
that case, whether or not the same workaround would apply.
I've tried to revert the commit, but unfortunately this doesn't reduce the
huge number of single/double bit errors (and jffs2 crc errors as a result)
I'm getting.
But having these non-aligned writes during GC, would that indicate a problem
with my jffs2 image parameters perhaps?
(though I cannot imagine this could actually cause double bit errors)
Rgds, Pieter
next reply other threads:[~2010-09-22 17:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 17:12 pieterg [this message]
2010-09-23 6:05 ` pxa3xx_nand issues Eric Miao
2010-09-23 11:32 ` pieterg
2010-09-23 15:29 ` pieterg
2010-09-23 18:03 ` Matt Reimer
2010-09-25 2:50 ` Haojian Zhuang
2010-09-27 11:38 ` pieterg
2010-09-26 14:32 ` Lei Wen
2010-09-27 11:54 ` pieterg
2010-09-27 12:22 ` Lei Wen
2010-09-27 13:50 ` pieterg
2010-09-27 17:39 ` pieterg
2010-10-01 0:15 ` Marek Vasut
2010-10-01 6:55 ` pieterg
2010-10-01 7:25 ` Marek Vasut
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=201009221912.24905.pieterg@gmx.com \
--to=pieterg@gmx.com \
--cc=linux-arm-kernel@lists.infradead.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.