linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: pieterg <pieterg@gmx.com>
To: openpxa-users@lists.sourceforge.net
Cc: "Bjørn Forsman" <bjorn.forsman@gmail.com>, linux-mtd@lists.infradead.org
Subject: Re: [Openpxa-users] PXA310: double bit errors on NAND
Date: Mon, 8 Nov 2010 23:18:21 +0100	[thread overview]
Message-ID: <201011082318.21748.pieterg@gmx.com> (raw)
In-Reply-To: <AANLkTin86UQe8Q4PNqSnU7M0x4kVPUehcBRpS0HhHKRh@mail.gmail.com>

On Monday, November 08, 2010 15:54:43 Bjørn Forsman wrote:
> I get "double bit error @ page" messages while working with NAND on a
> Colibri PXA310 module. Basically, when I write an UBI image to NAND,
> either with U-Boot "nand write" or "nandwrite" from mtd-utils,
> everything is OK on the *first* mount. But on the second mount I get
> several "double bit error @ page" messages and mount fails.

You are not erase-block padding your image, when you write it?
That's the mistake I made (with jffs2 in my case), in that openpxa-users
thread you mention.
As soon as I found out my image was eraseblock padded, and fixed that,
the number of single/double bit errors was reduced dramatically, 
but some errors remained.

I haven't yet had the time to further investigate this, my preliminary 
conclusion is that the Samsung K9K's, though advertised as SLC, 
are very poor quality, and they probably need a better ecc than 
Hamming (as the pxa nand controller implements).
And also that jffs2 seems to care less than ubi(fs) when double bit errors 
do happen.(ubifs often refused to even mount when biterrors occurred, 
jffs2 so far always continued with what remained)
That's the reason why I'm using jffs2 for the time being, a non-booting 
device is worse than a device with a corrupted file.
(from a theoretical point of view however both are equally bad of course, 
this issue does need to be resolved)

Rgds, Pieter

  parent reply	other threads:[~2010-11-08 22:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-08 14:54 PXA310: double bit errors on NAND Bjørn Forsman
2010-11-08 16:54 ` Bjørn Forsman
2010-11-08 22:18 ` pieterg [this message]
2010-11-09  9:15   ` [Openpxa-users] " Bjørn Forsman
2010-11-09  9:58     ` pieterg
2011-01-15 17:01       ` Bjørn Forsman
2011-01-16 21:53         ` Ricard Wanderlof
2011-01-17 11:27           ` Bjørn Forsman

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=201011082318.21748.pieterg@gmx.com \
    --to=pieterg@gmx.com \
    --cc=bjorn.forsman@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=openpxa-users@lists.sourceforge.net \
    /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).