From: Angelo Dureghello <angelo70@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: UBI ECC errors on kernel 3.16.2
Date: Wed, 01 Oct 2014 22:41:15 +0200 [thread overview]
Message-ID: <542C66EB.5000105@gmail.com> (raw)
Dear all,
i am working on an embedded system: arm TI AM1808 cpu with a nand flash
mt29f1g08abb.
The flash is 128MB, no-subages, pages as 2048bytes, OOB 64 bytes
Type: nand
Eraseblock size: 131072 bytes, 128.0 KiB
Amount of eraseblocks: 480 (62914560 bytes, 60.0 MiB)
Minimum input/output unit size: 2048 bytes
Sub-page size: 512 bytes
OOB size: 64 bytes
Character device major/minor: 90:12
Bad blocks are allowed: true
Device is writable: true
I had UBI/UBIFS working fine with kernel 3.5.1 (flashing it through u.boot).
As ecclayout, from my board.c, i was setting up a custom one:
/* NAND ECC modified to reflect the DaVinci RBL layout (i.e. 512B rather
than 2kB)
* patch from http://processors.wiki.ti.com/index.php/DM365_Nand_ECC_layout
*/
static struct nand_ecclayout ipam390_nand_ecclayout = {
.eccbytes = 40,
.eccpos = {6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
22, 23, 24, 25, 26, 27, 28, 29, 30, 31,
38, 39, 40, 41, 42, 43, 44, 45, 46, 47,
54, 55, 56, 57, 58, 59, 60, 61, 62, 63,
},
.oobfree = {{2, 4}, {16, 6}, {32, 6}, {48, 6} },
};
Now i am moving to kernel 3.16.2.
With quite same config, the same UBI image now produces several errors
platform barix-ipam390.0: Driver barix-ipam390 requests probe deferral
UBI: scanning is finished
UBI: volume 0 ("rootfs") re-sized from 205 to 456 LEBs
UBI: attached mtd6 (name "rootfs", size 60 MiB) to ubi0
UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 512
UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
UBI: good PEBs: 480, bad PEBs: 0, corrupted PEBs: 0
UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
UBI: max/mean erase counter: 1/0, WL threshold: 4096, image sequence
number: 1641262122
UBI: available PEBs: 0, total reserved PEBs: 480, PEBs reserved for bad
PEB handling: 20
UBI: background thread "ubi_bgt0d" started, PID 1025
davinci_emac 1e20000.ethernet: failed to get EMAC clock
davinci_emac: probe of 1e20000.ethernet failed with error -16
davinci_emac davinci_emac.1: Runtime PM disabled, clock forced on.
davinci_emac davinci_emac.1: Runtime PM disabled, clock forced on.
davinci_emac davinci_emac.1: Runtime PM disabled, clock forced on.
barix-ipam390 barix-ipam390.0: ASoC: platform davinci-pcm-audio not
registered
gpio-keys gpio-keys.0: Unable to get irq number for GPIO 126, error -6
platform barix-ipam390.0: Driver barix-ipam390 requests probe deferral
omap_rtc da830-rtc: setting system clock to 2014-10-01 18:55:35 UTC
(1412189735)
ALSA device list:
No soundcards found.
UBI warning: ubi_io_read: error -74 (ECC error) while reading 4096 bytes
from PEB 2:4096, read only 4096 bytes, retry
UBI warning: ubi_io_read: error -74 (ECC error) while reading 4096 bytes
from PEB 2:4096, read only 4096 bytes, retry
UBI warning: ubi_io_read: error -74 (ECC error) while reading 4096 bytes
from PEB 2:4096, read only 4096 bytes, retry
UBI error: ubi_io_read: error -74 (ECC error) while reading 4096 bytes
from PEB 2:4096, read 4096 bytes
UBIFS: background thread "ubifs_bgt0_0" started, PID 1032
I tred also to boot a jffs2 file system and had similar ECC errors.
I suspect something in the mtd/ecc part is changed in a way that my
custom ecc is no more valid.
Every help is very appreciated.
Thanks
Regards,
Angelo
next reply other threads:[~2014-10-01 20:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 20:41 Angelo Dureghello [this message]
2014-10-01 20:51 ` UBI ECC errors on kernel 3.16.2 Richard Weinberger
2014-10-01 21:35 ` Angelo Dureghello
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=542C66EB.5000105@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 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.