From: Richard Weinberger <richard@nod.at>
To: Roshni Shah <roshni.shah@timesys.com>, Han Xu <xhnjupt@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"han.xu@freescale.com" <han.xu@freescale.com>
Subject: Re: UBIFS corruptions on NOR-Flash
Date: Thu, 15 Oct 2015 00:17:49 +0200 [thread overview]
Message-ID: <561ED48D.5010002@nod.at> (raw)
In-Reply-To: <CA+-FG61mEsrOu_WGUuCm-xgKM4afxSrw2JyQUwCi8BPJU3gkQQ@mail.gmail.com>
Hi!
Am 14.10.2015 um 16:33 schrieb Roshni Shah:
> Hi Han, Richard,
>
> Any other ideas / tests that I could perform to help narrow down the
> issue further? I really appreciate you taking the time.
I don't have this hardware, so I cannot say much.
Does the dump of the corrupted data make sense?
IOW are only a few bits flipped or is it completely
garbage?
Han, have you ever tested this driver with UBI?
As I said UBI uses vmalloc'ed buffers. Maybe the driver
is "UBI unfriendly" and needs tamed.
Thanks,
//richard
next prev parent reply other threads:[~2015-10-14 22:18 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
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 [this message]
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=561ED48D.5010002@nod.at \
--to=richard@nod.at \
--cc=han.xu@freescale.com \
--cc=linux-mtd@lists.infradead.org \
--cc=roshni.shah@timesys.com \
--cc=xhnjupt@gmail.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