linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Angelo Dureghello <angelo70@gmail.com>
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Fwd: Re: UBI ECC errors on kernel 3.16.2
Date: Thu, 02 Oct 2014 11:19:50 +0200	[thread overview]
Message-ID: <542D18B6.3020906@gmail.com> (raw)
In-Reply-To: <542C73B0.7000602@gmail.com>

I have some additional info:
i added some traces in the mtd nand driver, and see that until a certain
point of the boot, mtddriver reads without any ecc error.

Then, after some other driver inits, the same offset read gives ecc error.


nand_davinci_read_buf: buf c791588c, len 64
nand_davinci_read_buf: buf c883d000, len 512
nand_davinci_read_buf: buf c883d200, len 512
nand_davinci_read_buf: buf c883d400, len 512
nand_davinci_read_buf: buf c883d600, len 512
nand_davinci_read_buf: buf c791588c, len 64
nand_davinci_read_buf: buf c883d800, len 512
nand_davinci_read_buf: buf c883da00, len 512
nand_davinci_read_buf: buf c883dc00, len 512
nand_davinci_read_buf: buf c883de00, len 512
nand_davinci_read_buf: buf c791588c, len 64
nand_davinci_read_buf: buf c883e000, len 512
nand_davinci_read_buf: buf c883e200, len 512
nand_davinci_read_buf: buf c883e400, len 512
nand_davinci_read_buf: buf c883e600, len 512
nand_read(): ret=0
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.
gpio-keys gpio-keys.0: Unable to get irq number for GPIO 126, error -6
omap_rtc da830-rtc: setting system clock to 2014-10-02 09:06:57 UTC 
(1412240817)
barix-ipam390 barix-ipam390.0: ASoC: platform davinci-pcm-audio not 
registered
ALSA device list:
   No soundcards found.
platform barix-ipam390.0: Driver barix-ipam390 requests probe deferral
nand_davinci_read_buf: buf c791588c, len 64
nand_davinci_read_buf: buf c791b000, len 512
nand_davinci_read_buf: buf c791b200, len 512
nand_davinci_read_buf: buf c791b400, len 512
nand_davinci_read_buf: buf c791b600, len 512
ecc_failed !!
nand_davinci_read_buf: buf c791588c, len 64
nand_davinci_read_buf: buf c791b800, len 512
nand_davinci_read_buf: buf c791ba00, len 512
nand_davinci_read_buf: buf c791bc00, len 512
nand_davinci_read_buf: buf c791be00, len 512
nand_read(): ret=-74


So seems some of the latest driver probe or the ubi attach someway mess 
up the next mtd read.

Regards
angelo

  reply	other threads:[~2014-10-02  9:20 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
2014-10-02  9:19     ` Angelo Dureghello [this message]
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=542D18B6.3020906@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).