From: Brian Foster <brian.foster@maxim-ic.com>
To: <linux-mtd@lists.infradead.org>
Cc: kpa_info@yahoo.fr, matthieu.castet@parrot.com
Subject: Re: UBI: infinite error loop
Date: Fri, 24 Feb 2012 17:16:02 +0100 [thread overview]
Message-ID: <201202241717.04475.brian.foster@maxim-ic.com> (raw)
matthieu.castet@parrot.com wrote:
> Patrick a écrit :
> > When I am doing an the ubiattach -p /dev/mtd4 command
> > I have the following infinite error loop:
>[ ... ]
> Look like it doesn't handle subpage reading :
> you have ecc error when reading 512 bytes at offset 512.
Also, keep in mind read-after-write checks don't work with subpages,
http://www.linux-mtd.infradead.org/faq/ubi.html#L_subpage_verify_fail
───────────────────────────────────────────────────────────
I get "ubi_io_write: error -5 while writing 512 bytes to PEB 5:512"
If you have a 2048 bytes per NAND page device, and have
CONFIG_MTD_NAND_VERIFY_WRITE enabled in your kernel,
you will need to turn it off. The code does not currently
(as of 2.6.26) perform verification of sub-page writes
correctly. As UBI is one of the few users of sub-page
writes, not much else seems to be affected by this bug.
───────────────────────────────────────────────────────────
YES, I realize that is not your error, but this was
something that badly tripped us up until an intense
search-engine session .... ;-\ (I have no idea if
this has since been fixed or not?)
cheers!
-blf-
--
Brian Foster
Principal MTS, Software | La Ciotat, France
Maxim Integrated Products | Web: http://www.maxim-ic.com/
next reply other threads:[~2012-02-24 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 16:16 Brian Foster [this message]
2012-03-09 9:26 ` UBI: infinite error loop Artem Bityutskiy
-- strict thread matches above, loose matches on Subject: below --
2012-02-24 13:35 Patrick
2012-02-24 13:52 ` Matthieu CASTET
2012-03-09 9:07 ` Artem Bityutskiy
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=201202241717.04475.brian.foster@maxim-ic.com \
--to=brian.foster@maxim-ic.com \
--cc=kpa_info@yahoo.fr \
--cc=linux-mtd@lists.infradead.org \
--cc=matthieu.castet@parrot.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