public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Foster <brian.foster@maxim-ic.com>
Cc: kpa_info@yahoo.fr, linux-mtd@lists.infradead.org,
	matthieu.castet@parrot.com
Subject: Re: UBI: infinite error loop
Date: Fri, 09 Mar 2012 11:26:15 +0200	[thread overview]
Message-ID: <1331285175.22872.36.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <201202241717.04475.brian.foster@maxim-ic.com>

On Fri, 2012-02-24 at 17:16 +0100, Brian Foster wrote:
>  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?)

Well, no one cares enough to investigate this and fix the issue. I think
this article should be removed - may be this will inspire someone to
send a fix...

-- 
Best Regards,
Artem Bityutskiy

  reply	other threads:[~2012-03-09  9:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-24 16:16 UBI: infinite error loop Brian Foster
2012-03-09  9:26 ` Artem Bityutskiy [this message]
  -- 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=1331285175.22872.36.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=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