From: Richard Weinberger <richard@nod.at>
To: Roshni Shah <roshni.shah@timesys.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
han.xu@freescale.com
Subject: Re: UBIFS corruptions on NOR-Flash
Date: Fri, 18 Sep 2015 23:50:10 +0200 [thread overview]
Message-ID: <55FC8712.5040905@nod.at> (raw)
In-Reply-To: <CA+-FG62nCCaK_GEGSqBJ4ROvqgVPZdsh7pyEsnq2C0AXZrnkjw@mail.gmail.com>
Am 18.09.2015 um 23:36 schrieb Roshni Shah:
> Thanks. I tried 4.1 Kernel ran UBI tests and mounting the UBIFS on
> Vybrid TWR. I see a different error, however corruptions & UBI test
> failures still persist.
>
> Flash chip: s25fl128s (same as above).
>
> # uname -r
> 4.1.5
>
> Following are the results:
[...]
> ubi0 warning: ubi_eba_read_leb: CRC error: calculated 0x8f7714b9, must
> be 0x31a3fc87
> ubi0 warning: vol_cdev_write: volume 0 on UBI device 0 is corrupted
> ubi0 warning: ubi_eba_read_leb: CRC error: calculated 0xd1882123, must
So, reading data using UBI does not work as expected.
One thing MTD drivers sometimes get wrong is that UBI is using vmalloc'ed buffers
and drivers cannot deal with that.
Adding Han Xu, maybe he has an idea.
Thanks,
//richard
next prev parent reply other threads:[~2015-09-18 21:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 16:50 UBIFS corruptions on NOR-Flash Roshni
2015-09-18 17:23 ` Richard Weinberger
2015-09-18 19:45 ` Roshni Shah
2015-09-18 19:53 ` Richard Weinberger
2015-09-18 20:05 ` Roshni Shah
2015-09-18 20:08 ` Richard Weinberger
2015-09-18 21:36 ` Roshni Shah
2015-09-18 21:50 ` Richard Weinberger [this message]
2015-09-23 18:21 ` Han Xu
2015-09-23 18:28 ` Roshni Shah
2015-09-24 19:09 ` Roshni Shah
2015-09-25 18:07 ` Richard Weinberger
2015-09-25 18:11 ` Han Xu
2015-10-09 16:33 ` Roshni Shah
2015-10-14 14:33 ` Roshni Shah
2015-10-14 22:17 ` Richard Weinberger
2015-10-15 2:20 ` Han Xu
2015-10-15 7:39 ` Richard Weinberger
2015-10-22 22:43 ` Han Xu
2015-09-18 18:19 ` Fabio Estevam
2015-09-18 19:51 ` Roshni Shah
2015-09-18 20:02 ` Fabio Estevam
2015-09-18 21:06 ` Roshni Shah
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=55FC8712.5040905@nod.at \
--to=richard@nod.at \
--cc=han.xu@freescale.com \
--cc=linux-mtd@lists.infradead.org \
--cc=roshni.shah@timesys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox