From: Artem Bityutskiy <dedekind@infradead.org>
To: Subramani Venkatesh <subbu31mani@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBI attach and mounting problem after rebooting
Date: Thu, 19 Feb 2009 18:10:18 +0200 [thread overview]
Message-ID: <1235059818.17790.373.camel@localhost.localdomain> (raw)
In-Reply-To: <25dd9bf10902190658p4e0adea3s8f8bba6f5cfd01d6@mail.gmail.com>
Hi,
On Thu, 2009-02-19 at 09:58 -0500, Subramani Venkatesh wrote:
> UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB
> 798:0, read 64 bytes
> UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB
> 799:0, read 64 bytes
> UBI error: ubi_read_volume_table: the layout volume was not found
> UBI error: ubi_init: cannot attach mtd4
> UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
-71 is -EBADMSG which means that ECC error occurred. IOW, your NAND
driver reports that it cannot read 64 bytes from eraseblock 798,
offset 0, and UBI has nothing else to do but stopping.
You should look closer at what your driver do. I think it might be
not handling sub-pages correctly. You may experiment and force UBI
not to use sub-pages, and if it helps, you have your problem a little
bit narrowed down.
I've just created a FAQ entry which tells how to force UBI
not to use sub-pages:
http://www.linux-mtd.infradead.org/faq/ubi.html#L_force_no_subpage
Also, you may try to attach an empty flash and play with it. If it
works fine, this may be something to do with how you flash your
initial images. Indeed, the program you use for flashing may screw
up ECCs somehow.
HTH.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2009-02-19 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 14:58 UBI attach and mounting problem after rebooting Subramani Venkatesh
2009-02-19 16:10 ` Artem Bityutskiy [this message]
2009-02-19 22:14 ` Yang, Xiaopeng
2009-02-19 22:39 ` Subramani Venkatesh
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=1235059818.17790.373.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=subbu31mani@gmail.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