All of lore.kernel.org
 help / color / mirror / Atom feed
From: borasah@gmail.com
To: linux-mtd@lists.infradead.org
Cc: Ricard Wanderlof <ricard.wanderlof@axis.com>
Subject: Re: NAND flash write goes wrong
Date: Mon, 21 May 2007 12:30:12 +0300	[thread overview]
Message-ID: <200705211230.12829.borasah@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0705140852340.3951@lnxricardw.se.axis.com>


Hi,

[Snip]

Thanks for the infos...

> >> Blocks (nand flash terminology rejects the name 'sectors' in favor of
> >> 'blocks' and 'pages') can go bad with time, but we're talking about
> >> thousands if not tens of thousands of erase/write cycles here. So it
> >> seems there's something wrong here.
> >
> > Yes, I think too. Now ~140 bad sector is reported during the boot. I just
> > did at most 50 read/write...
>
> You sound far from wearing the chip out. There must be another problem
> there somewhere.

Hmm...

> >> There was a patch posted just a week or so ago here which fixed a
> >> problem with bad block marking and recognition when not using a
> >> flash-based bad block table.
> >
> > I'm new to the list. Is this Artem's patch? I applied it, but no
> > success... Maybe
> > http://lists.infradead.org/pipermail/linux-mtd/2007-May/018087.html?
>
> By Thomas Knobloch I believe, but yes, that's the patch I was thinking of.

I applied it but no success...

------------

I tried K9F1208U0A with linux-2.6.20 -> JFFS2 file system. I successfully used 
the part. 

Secondly, I tried yaffs with that part in the linux-2.6.11. It was successful 
too.

--
Bora SAHIN

  reply	other threads:[~2007-05-21  9:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10 18:50 NAND flash write goes wrong borasah
2007-05-10 19:16 ` Josh Boyer
2007-05-10 21:37   ` borasah
2007-05-10 22:15     ` Thomas Gleixner
2007-05-10 22:42       ` borasah
2007-05-11  6:36 ` Ricard Wanderlof
2007-05-11  6:57   ` Artem Bityutskiy
2007-05-11  7:16     ` Matthieu CASTET
2007-05-11  7:42       ` Artem Bityutskiy
2007-05-11  7:49         ` Artem Bityutskiy
2007-05-11 13:56   ` borasah
2007-05-11 14:31     ` Ricard Wanderlof
2007-05-11 17:58       ` borasah
2007-05-14  6:56         ` Ricard Wanderlof
2007-05-21  9:30           ` borasah [this message]
     [not found] <42E999AD7A0E4647BF159F467EE4FBCB017B5155@BLR-SGM-MSG01.wipro.com>
2007-05-14  7:39 ` Ricard Wanderlof

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=200705211230.12829.borasah@gmail.com \
    --to=borasah@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=ricard.wanderlof@axis.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 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.