From: Michal Ludvig <mludvig@logix.net.nz>
To: Ben Dooks <ben-linux@fluff.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: nandwrite/ubi memory corruption?
Date: Fri, 17 Oct 2008 15:06:56 +1300 [thread overview]
Message-ID: <48F7F340.5040804@logix.net.nz> (raw)
In-Reply-To: <48F7C7E5.9070107@logix.net.nz>
Michal Ludvig wrote:
> Ben Dooks wrote:
>> On Fri, Oct 17, 2008 at 10:43:57AM +1300, Michal Ludvig wrote:
>>> Ben Dooks wrote:
>>>> On Thu, Oct 16, 2008 at 11:10:29PM +1300, Michal Ludvig wrote:
>>>>> Hi all,
>>>>>
>>>>> I've got an ARM board with 64MB of NAND flash with 3 logical partitions
>>>>> and am experiencing (probably) memory corruption of UBI/UBIFS on
>>>>> /dev/mtd2 after writing data with nandwrite to /dev/mtd1.
>>>>> [...]
>>>>> s3c2410-nand s3c2410-nand: clock idle support enabled
>>>> hmm, could you try disabling the clock-idle support?
>>> How do I do that?
>> there should be a Kconfig entry to do it when the s3c2410 nand driver
>> is selected.
>
> Ah, I see. OK, with clock-idle off nandwrite didn't corrupt ubi/ubifs
> but the kernel still wouldn't boot:
It looks like if nandwrite writes some nonsense onto the flash.
I did:
~ # nanddump -o -b -f dump.pre-nandwrite /dev/mtd1
~ # nandwrite -p /dev/mtd1 uimage26
~ # nanddump -o -b -f dump.post-nandwrite /dev/mtd1
dump.post-nandwrite is different from dump.pre-nandwrite but doesn't
seem to have much in common with uimage26.
OTOH dump.pre-nandwrite contains the kernel image that has been stored
by u-boot's nandw. So the /dev/mtd1 offset is probably OK.
Any ideas on what's wrong?
Michal
next prev parent reply other threads:[~2008-10-17 2:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 10:10 nandwrite/ubi memory corruption? Michal Ludvig
2008-10-16 14:49 ` Artem Bityutskiy
2008-10-16 14:56 ` Artem Bityutskiy
2008-10-16 22:10 ` Michal Ludvig
2008-10-17 11:02 ` Artem Bityutskiy
2008-10-17 12:09 ` Artem Bityutskiy
2008-10-18 20:34 ` Michal Ludvig
2008-10-17 12:06 ` Artem Bityutskiy
2008-10-16 15:01 ` Ben Dooks
2008-10-16 21:43 ` Michal Ludvig
2008-10-16 21:56 ` Ben Dooks
2008-10-16 23:01 ` Michal Ludvig
2008-10-17 2:06 ` Michal Ludvig [this message]
2008-10-17 11:03 ` Artem Bityutskiy
2008-10-17 13:42 ` Ben Dooks
2008-10-17 13:44 ` Artem Bityutskiy
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=48F7F340.5040804@logix.net.nz \
--to=mludvig@logix.net.nz \
--cc=ben-linux@fluff.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.