From: Artem Bityutskiy <dedekind1@gmail.com>
To: Sergej.Stepanov@ids.de
Cc: scottwood@freescale.com, linux-mtd@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org, dwmw2@infradead.org,
Rolf.Riehle@ids.de
Subject: Re: [PATCH][v2] Fixing the garbage collector problem after NAND-flash image record in u-boot
Date: Mon, 29 Nov 2010 16:53:26 +0200 [thread overview]
Message-ID: <1291042406.2141.14.camel@koala> (raw)
In-Reply-To: <4206182445660643B9AEB8D4E55BBD0A106A0AA93A@HERMES2>
On Tue, 2010-11-23 at 18:38 +0100, Sergej.Stepanov@ids.de wrote:
> This patch should fix the following problem:
> 1. the jffs2-image update in the u-boot was ok
> 2. first restart and first mount of the NAND-flash-partition was also ok
> 3. before the restart of controller there are no any activity on NAND-flash except of the jffs2_gcd_mtdX-process ...
> 4. BUT after the second restart the NAND-flash-partition could not be really used after the second mount,
> dmesg filled with messages:
> ...
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x03ce0000: 0xc0ff instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x03d00000: 0xc0ff instead
> ....
> Just for for info:
> the behaviour observed on mpc8313-based board with the large-page NAND.
> The only activity on NAND-flash was the garbage collector process, that looks for CLEANMARKER-nodes
>
> As Scott said it was broken by commit 3ab8f2a2e7011c5e83363b42950757e46ef06824
>
> Signed-off-by: Sergej Stepanov <Sergej.Stepanov@ids.de>
> Cc: Rolf Riehle <Rolf.Riehle@ids.de>
> Cc: Scott Wood <scottwood@freescale.com>
> Cc: David Woodhouse <dwmw2@infradead.org>
Pusehd to l2-mtd-2.6.git, thanks.
--
Best Regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2010-11-29 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 17:38 [PATCH][v2] Fixing the garbage collector problem after NAND-flash image record in u-boot Sergej.Stepanov
2010-11-29 14:53 ` Artem Bityutskiy [this message]
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=1291042406.2141.14.camel@koala \
--to=dedekind1@gmail.com \
--cc=Rolf.Riehle@ids.de \
--cc=Sergej.Stepanov@ids.de \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.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;
as well as URLs for NNTP newsgroup(s).