From: David Jander <david.jander@protonic.nl>
To: dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: Current mainline (3.6-rc3) UBIFS errors
Date: Thu, 23 Aug 2012 11:27:32 +0200 [thread overview]
Message-ID: <20120823112732.32ed62d5@archvile> (raw)
In-Reply-To: <1345711673.2848.214.camel@sauron.fi.intel.com>
On Thu, 23 Aug 2012 11:47:53 +0300
Artem Bityutskiy <dedekind1@gmail.com> wrote:
> On Thu, 2012-08-23 at 10:39 +0200, David Jander wrote:
> > On Thu, 23 Aug 2012 11:10:08 +0300
> > Artem Bityutskiy <dedekind1@gmail.com> wrote:
> >
> > > On Thu, 2012-08-23 at 09:50 +0200, David Jander wrote:
> > > > [ 4.069409] UBI warning: ubi_io_read: error -74 (ECC error) while
> > > > reading 160 bytes from PEB 5616:87112, read only 160 bytes
> > >
> > > Hi, looks like a problem with your driver. For some reasons it returns
> > > ECC errors when reading small amount of data (160 bytes). Did you run
> > > mtd tests - to they pass?
> >
> > I thought so at first, but this error appeared on two different hardware
> > platforms at the same time, when upgrading to latest mainline. I am coming
> > from kernel 3.1, which worked fine on the MPC5121e. The ARM platform also
> > worked without problems on a previous version (I think it was 3.4-something,
> > not so sure right now). The only common piece of hardware/driver is the actual
> > NAND flash chip on both boards (Samsung K9K8G08... SLC 8Gbit NAND), so I
> > thought this had to be a (temporary) issue in current mainline code.
>
> A change in the mtd layer probably caused this.
>
> > > So UBI just tells that it cannot read, the root-cause is in the driver.
> >
> > Two different drivers... same issue!?
>
> Quite possible if there is a bug in mtd layer. First try to find out the
> latest working kernel release.
Ok, sounds reasonable.
I found kernel 3.5 works fine. Now bisecting...
> > Can you tell if I am supposed to be able to mount a UBIFS device formatted
> > with 3.1 on latest mainline without trouble? Is there a chance OOB layout may
> > have changed, or something similar? I tried reformatting with 3.6-rc2 just in
> > case, but the problem remained.
>
> Absolutely yes, we maintain on-flash format compatibility and you do not
> have to re-format your flash.
Good to know! I had such an issue before, when upgrading our customer from
Freescale's 2.6.25 kernel to 3.1 mainline. Freescale had a different OOB/ECC
layout. The upgrade procedure was a PITA and involved making a filesystem
backup/restore to a USB device :-(
Best regards,
--
David Jander
Protonic Holland.
next prev parent reply other threads:[~2012-08-23 9:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 7:50 Current mainline (3.6-rc3) UBIFS errors David Jander
2012-08-23 8:10 ` Artem Bityutskiy
2012-08-23 8:39 ` David Jander
2012-08-23 8:47 ` Artem Bityutskiy
2012-08-23 9:27 ` David Jander [this message]
2012-08-23 10:18 ` Artem Bityutskiy
2012-08-23 15:15 ` David Jander
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=20120823112732.32ed62d5@archvile \
--to=david.jander@protonic.nl \
--cc=dedekind1@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).