From: Norbert van Bolhuis <nvbolhuis@aimvalley.nl>
To: enrico benetti <enrico.benetti@bluewind.it>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS: power cut test on 2.6.35 + NOR
Date: Thu, 27 Jun 2013 11:32:02 +0200 [thread overview]
Message-ID: <51CC0692.6010507@aimvalley.nl> (raw)
In-Reply-To: <51CBDF47.709@bluewind.it>
On 06/27/13 08:44, enrico benetti wrote:
> Hi All,
> I'd need a hint on the best way to go on with my development.
>
> I'm working on a custom target based on 2.6.35.3 kernel with NOR device.
>
> UBIFS R/W partitions seem not robust against power cut tests: I'm using
> integck 1.4.9 and I can have unrecoverable errors on tested volume when
> performing real power cuts.
>
> First of all, I've done several MTD stress tests to validate the low
> level driver.
> I've checked git repos, and
> http://git.infradead.org/users/dedekind/ubifs-v2.6.35.git/ <http://git.infradead.org/users/dedekind/ubifs-v2.6.35.git/shortlog>
> is updated to 08/2012 (that is approx 3.7.1 kernel revision) and no more
> supported.
>
> From several discussions on the list I think the best way to solve (or
> at least to have a better behaviour with ubi/ubifs) could be to get the
> patches from this repo and merge them with my sources.
>
> Do you agree or is it better to do more investigation on current issues?
>
> Thanks in advance for your support,
> Enrico
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
>
yes, use http://git.infradead.org/users/dedekind/ubifs-v2.6.35.git to update.
it has several "NOR power cut" fixes, for example:
http://git.infradead.org/users/dedekind/ubifs-v2.6.35.git/commit/152780c61d65b0cc5cd5cc974e926a9c47534d5e
http://git.infradead.org/users/dedekind/ubifs-v2.6.35.git/commit/9258edaca1d7b36abd0e23661579c35fe9c4f00f
http://git.infradead.org/users/dedekind/ubifs-v2.6.35.git/commit/e5d7669e2fa0797c0c110fa9bf3e51b013ba399b
which I doubt are in 2.6.35.3
Btw. we used the (no longer available) http://git.infradead.org/users/dedekind/ubifs-v2.6.29.git
(that has been kept up-to-date with mainline till June 2011) to update our sources, and we see
no NOR power cut issues.
---
N. van Bolhuis.
next prev parent reply other threads:[~2013-06-27 9:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 6:44 UBIFS: power cut test on 2.6.35 + NOR enrico benetti
2013-06-27 9:32 ` Norbert van Bolhuis [this message]
2013-06-27 10:47 ` Mats Kärrman
2013-06-27 12:56 ` enrico benetti
2013-06-27 13:01 ` Mats Kärrman
2013-06-28 13:36 ` enrico benetti
2013-06-28 15:03 ` enrico benetti
2013-06-29 2:08 ` Brian Norris
2013-07-01 2:23 ` Huang Shijie
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=51CC0692.6010507@aimvalley.nl \
--to=nvbolhuis@aimvalley.nl \
--cc=enrico.benetti@bluewind.it \
--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.