public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Ben Dooks <ben-linux@fluff.org>
To: Michal Ludvig <mludvig@logix.net.nz>
Cc: linux-mtd@lists.infradead.org, Ben Dooks <ben-linux@fluff.org>
Subject: Re: nandwrite/ubi memory corruption?
Date: Thu, 16 Oct 2008 22:56:16 +0100	[thread overview]
Message-ID: <20081016215616.GE22711@trinity.fluff.org> (raw)
In-Reply-To: <48F7B59D.9000200@logix.net.nz>

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.
 
> Michal

-- 
-- 
Ben

Q:      What's a light-year?
A:      One-third less calories than a regular year.

  reply	other threads:[~2008-10-16 21:56 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 [this message]
2008-10-16 23:01       ` Michal Ludvig
2008-10-17  2:06         ` Michal Ludvig
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=20081016215616.GE22711@trinity.fluff.org \
    --to=ben-linux@fluff.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mludvig@logix.net.nz \
    /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