From: Angelo Dureghello <angelo70@gmail.com>
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: UBI ECC errors on kernel 3.16.2
Date: Wed, 01 Oct 2014 23:35:44 +0200 [thread overview]
Message-ID: <542C73B0.7000602@gmail.com> (raw)
In-Reply-To: <CAFLxGvz0cKDdUNjQHyNcW3VbtQGW5FkamSJv+vx786TRBqDCkA@mail.gmail.com>
On 01/10/2014 22:51, Richard Weinberger wrote:
>
> Do mtd and ubi tests pass?
>
I have successfully executed all mtd tests under old kernel 3.5.1.
Now, with this new kernel 3.16.2 i can't boot, and i don't know how i
could test it.
Only thing that i can do is to minimally verify the flashed image from
u-boot
U-Boot > ubi part rootfs 2048
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
UBI: volume 0 ("rootfs") re-sized from 205 to 472 LEBs
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=6"
UBI: MTD device size: 60 MiB
UBI: number of good PEBs: 480
UBI: number of bad PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 0
UBI: total number of reserved PEBs: 480
UBI: number of PEBs reserved for bad PEB handling: 4
UBI: max/mean erase counter: 1/0
U-Boot >
It seems sane.
Also, once loaded the system and get the errors, the ubi get damaged
(check from U.boot shows ecc errors
Regards
next prev parent reply other threads:[~2014-10-01 21:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 20:41 UBI ECC errors on kernel 3.16.2 Angelo Dureghello
2014-10-01 20:51 ` Richard Weinberger
2014-10-01 21:35 ` Angelo Dureghello [this message]
2014-10-02 9:19 ` Fwd: " Angelo Dureghello
2014-10-02 17:26 ` Angelo Dureghello
2014-10-03 8:15 ` Richard Weinberger
2014-10-06 4:49 ` Pekon Gupta
2014-10-06 9:02 ` Angelo Dureghello
2014-10-06 20:13 ` pekon
2014-10-06 20:31 ` Angelo Dureghello
2014-10-06 20:35 ` Angelo Dureghello
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=542C73B0.7000602@gmail.com \
--to=angelo70@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).