From: Richard Weinberger <richard@nod.at>
To: Yan Kong <ykong@sierrawireless.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: UBI errors when "ls -l"
Date: Mon, 15 Dec 2014 09:36:48 +0100 [thread overview]
Message-ID: <548E9DA0.8070407@nod.at> (raw)
In-Reply-To: <740E8392C144C64FA5300E5E696A179BB97FEBBAE9@carmd-exchmb01.sierrawireless.local>
Hi!
Am 15.12.2014 um 04:30 schrieb Yan Kong:
> Hi Richard,
>
> The FAE tell me that now mtd driver doesn't support only write OOB area, but not write data area. So mtd_oobtest.
This sentence does not parse.
> But they are not sure if it is related to the UBI error. What do you think about it?
Fact is that mtd_read() returns less bytes than requested. This must not happen and is most
likely a driver issue.
I'd start investigating here.
Almost all "UBI issues" I inspect for customers turn out to be plain mtd driver bugs.
> Another thing is that, I tried to enable nandsim in my Kernel, but saw that "Sub-page size" and "OOB size" of nandsim partition are different from local mtd partition's.
> The parameter of nandsim are as follows, which is copied from boot up logs.
> Command of insmod nandsim is:
> modprobe nandsim first_id_byte=0x2c second_id_byte=0xac third_id_byte=0x90 fourth_id_byte=0x26
> Is the parameter I used wrong?
If the ID bytes are correct everything work fine.
Thanks,
//richard
next prev parent reply other threads:[~2014-12-15 8:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 9:34 UBI errors when "ls -l" Yan
2014-12-10 10:40 ` Richard Weinberger
2014-12-10 13:10 ` Yan Kong
2014-12-10 13:24 ` Richard Weinberger
2014-12-10 13:51 ` Yan Kong
2014-12-10 13:55 ` Richard Weinberger
2014-12-12 8:03 ` Yan Kong
2014-12-12 8:21 ` Richard Weinberger
2014-12-15 3:30 ` Yan Kong
2014-12-15 8:36 ` Richard Weinberger [this message]
2014-12-15 8:53 ` Yan Kong
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=548E9DA0.8070407@nod.at \
--to=richard@nod.at \
--cc=linux-mtd@lists.infradead.org \
--cc=ykong@sierrawireless.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