All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Erno Kuusela <erno@gulp.u--3.com>
Cc: debian-arm@lists.debian.org, linux-mtd@lists.infradead.org
Subject: Re: UBIFS fails & crashes on SheevaPlug
Date: Fri, 24 Jul 2009 17:38:27 +0300	[thread overview]
Message-ID: <4A69C763.1070008@gmail.com> (raw)
In-Reply-To: <20090724131241.GC1792@gulp.u--3.com>

On 07/24/2009 04:12 PM, Erno Kuusela wrote:
> Ah, ok. I did google for that error message but searching for
> "ubi_io_write: error -5" doesn't yield anything useful for the first
> screenful of results..
>
> So workaround would be to disable CONFIG_MTD_NAND_VERIFY_WRITE or to
> follow the "ignore sub pages" entry from the faq...
>
> Indeed the latter seems to work, if I give --vid-hdr-offset 2048 option
> to the ubinize, ubiformat&  ubiattach commands. Thanks!

It should work without this. Your flash driver reports that your flash
supports 512-byte sub-pages. This means you may save your flash space
and put both UBI headers to the first NAND page. See this explanation:

http://www.linux-mtd.infradead.org/doc/ubi.html#L_overhead

If you follow links from this little section, you should grasp the picture.

So, disabling this option should help without the --vid-hdr-offset 2048
stuff. If it does not, then you should fix your driver.

> Maybe it would be better to disable the verify&  subpages combo
> until the bug is fixed? Especially since it crashes the kernel...

May be, but it is better to just fix this.

> Also, ubiformat mentioned 1400+ "bad" eraseblocks, what should I make of
> that? Is it really failed flash cells, just some blocks reserved for
> u-boot and stuff, or blocks traumatized from my earlier misadventures
> with ubiformat parameters?

Hmm, this is not normal. What is the version of ubiformat you use? Could
you try the latest one from the git tree:

http://www.linux-mtd.infradead.org/doc/ubi.html#L_usptools

Just in case, here are mtd-utils compile issues FAQ:
http://www.linux-mtd.infradead.org/faq/ubifs.html#L_mkfs_ubifs_comp
or you may always cd to ubi-utils and compile only UBI utils.

And what UBI is printing? See "UBI: number of bad PEBs:" message.

And please, send the exact ubiformat pritns.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

  reply	other threads:[~2009-07-24 14:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-23 18:59 UBIFS fails & crashes on SheevaPlug erno
2009-07-23 20:08 ` Adrian Hunter
2009-07-23 21:28   ` Corentin Chary
2009-07-23 21:52     ` erno
2009-07-24  5:53 ` Artem Bityutskiy
2009-07-24 13:12   ` Erno Kuusela
2009-07-24 14:38     ` Artem Bityutskiy [this message]
2009-07-26 15:35       ` Erno Kuusela
2009-08-09  4:56         ` Artem Bityutskiy
2009-07-26 11:07     ` Artem Bityutskiy
2009-07-24 21:00 ` Nicolas Pitre

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=4A69C763.1070008@gmail.com \
    --to=dedekind1@gmail.com \
    --cc=debian-arm@lists.debian.org \
    --cc=erno@gulp.u--3.com \
    --cc=linux-mtd@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.