From: Artem Bityutskiy <dedekind1@gmail.com>
To: Shivdas Gujare <shivdas.tech@gmail.com>
Cc: beagleboard@googlegroups.com, linux-mtd@lists.infradead.org
Subject: Re: ubifs errors for BeagleBoard
Date: Tue, 16 Feb 2010 10:25:48 +0200 [thread overview]
Message-ID: <1266308748.11659.183.camel@localhost> (raw)
In-Reply-To: <cf70f0211002150053w29f690bj542c4f7c3e9dc626@mail.gmail.com>
On Mon, 2010-02-15 at 00:53 -0800, Shivdas Gujare wrote:
> Hi All,
Good morning,
> I am trying to use UBIFS on Omap3 BeagleBoard (kernel version 2.6.33)
> I am quite new to flash filesystems & ubifs.
>
> currently for ubiattach I am getting following error,
>
> uncorrectable error :
> UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB
> 198:512, read 512 bytes
> [<c002e444>] (unwind_backtrace+0x0/0xdc) from [<c0217ddc>]
> (ubi_io_read+0x20c/0x2ec)
> [<c0217ddc>] (ubi_io_read+0x20c/0x2ec) from [<c0218048>]
> (ubi_io_read_vid_hdr+0x94/0x294)
> [<c0218048>] (ubi_io_read_vid_hdr+0x94/0x294) from [<c021cbf4>]
> (ubi_scan+0xa50/0x1094)
> [<c021cbf4>] (ubi_scan+0xa50/0x1094) from [<c02122f4>]
> (ubi_attach_mtd_dev+0x624/0xd6c)
> [<c02122f4>] (ubi_attach_mtd_dev+0x624/0xd6c) from [<c0212cd8>]
> (ctrl_cdev_ioctl+0xe8/0x1a4)
> [<c0212cd8>] (ctrl_cdev_ioctl+0xe8/0x1a4) from [<c00aa590>]
> (vfs_ioctl+0x2c/0x70)
> [<c00aa590>] (vfs_ioctl+0x2c/0x70) from [<c00aacc4>] (do_vfs_ioctl+0x518/0x55c)
> [<c00aacc4>] (do_vfs_ioctl+0x518/0x55c) from [<c00aad3c>] (sys_ioctl+0x34/0x54)
> [<c00aad3c>] (sys_ioctl+0x34/0x54) from [<c0028de0>] (ret_fast_syscall+0x0/0x2c)
-74 is -EBADMSG, which means an non-correctable ECC error.
>
> and for "mount -t ubifs /dev/ubi0_0 /mnt" it gives following error,
>
> uncorrectable error :
> UBI error: ubi_io_read: error -74 while reading 188 bytes from PEB
> 220:8304, read 188 bytes
> [<c002e444>] (unwind_backtrace+0x0/0xdc) from [<c0217ddc>]
> (ubi_io_read+0x20c/0x2ec)
> [<c0217ddc>] (ubi_io_read+0x20c/0x2ec) from [<c0216fd4>]
> (ubi_eba_read_leb+0x2e4/0x3e8)
> [<c0216fd4>] (ubi_eba_read_leb+0x2e4/0x3e8) from [<c0214c24>]
> (ubi_leb_read+0x100/0x15c)
> [<c0214c24>] (ubi_leb_read+0x100/0x15c) from [<c015d604>]
> (ubifs_read_node+0x1b4/0x340)
> [<c015d604>] (ubifs_read_node+0x1b4/0x340) from [<c017d9b0>]
> (ubifs_load_znode+0xd0/0x5c0)
> [<c017d9b0>] (ubifs_load_znode+0xd0/0x5c0) from [<c016136c>]
> (ubifs_lookup_level0+0x114/0x2dc)
> [<c016136c>] (ubifs_lookup_level0+0x114/0x2dc) from [<c0162e74>]
> (ubifs_tnc_locate+0x40/0x170)
> [<c0162e74>] (ubifs_tnc_locate+0x40/0x170) from [<c0158d00>]
> (ubifs_iget+0xb0/0x7e4)
> [<c0158d00>] (ubifs_iget+0xb0/0x7e4) from [<c015aa08>]
> (ubifs_fill_super+0x15d4/0x1664)
> [<c015aa08>] (ubifs_fill_super+0x15d4/0x1664) from [<c015ad20>]
> (ubifs_get_sb+0x288/0x2fc)
> [<c015ad20>] (ubifs_get_sb+0x288/0x2fc) from [<c009fd24>]
> (vfs_kern_mount+0x4c/0xd0)
> [<c009fd24>] (vfs_kern_mount+0x4c/0xd0) from [<c009fdec>]
> (do_kern_mount+0x34/0xd8)
> [<c009fdec>] (do_kern_mount+0x34/0xd8) from [<c00b4640>] (do_mount+0x5ec/0x64c)
> [<c00b4640>] (do_mount+0x5ec/0x64c) from [<c00b4724>] (sys_mount+0x84/0xc4)
> [<c00b4724>] (sys_mount+0x84/0xc4) from [<c0028de0>] (ret_fast_syscall+0x0/0x2c)
The same symptoms.
> Does anyone encountered similar kind of error?
Yes in general, dunno if for beagleboard.
Please, start with validating your flash using mtd-tests. You have
issues somewhere on the NAND driver level. Please, find the tests here:
http://www.linux-mtd.infradead.org/doc/general.html#L_mtd_tests
> Also would like to know, does user space - ubitools read only 64 bytes
> each from mtd drivers(while scan or format)
Yes.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-02-16 8:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 8:53 ubifs errors for BeagleBoard Shivdas Gujare
2010-02-16 8:25 ` Artem Bityutskiy [this message]
2010-02-23 0:49 ` Shivdas Gujare
2010-03-30 13: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=1266308748.11659.183.camel@localhost \
--to=dedekind1@gmail.com \
--cc=beagleboard@googlegroups.com \
--cc=linux-mtd@lists.infradead.org \
--cc=shivdas.tech@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 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.