From: Artem Bityutskiy <dedekind1@gmail.com>
To: Marek Vasut <marex@denx.de>
Cc: Fabio Estevam <fabio.estevam@freescale.com>,
Huang Shijie <b32955@freescale.com>,
linux-mtd@lists.infradead.org
Subject: Re: GPMI NAND crashes with UBIFS
Date: Wed, 17 Oct 2012 16:12:09 +0300 [thread overview]
Message-ID: <1350479529.5769.155.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <201210111355.33836.marex@denx.de>
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
On Thu, 2012-10-11 at 13:55 +0200, Marek Vasut wrote:
> Dear Artem Bityutskiy,
>
> > On Fri, 2012-10-05 at 03:45 +0200, Marek Vasut wrote:
> > > Hello guys,
> > >
> > > I tried integck from mtd-utils 1.5.0 on GPMI NAND driver since I suspect
> > > it still has issues with UBI. See the outcome for yourself, log
> > > attached. Any suggestions would be very appreciated.
> > >
> > > :~/mtd-utils-1.5.0/tests/fs-tests/integrity# ./integck /media
> >
> > Wait, you have power-cut emulation enabled, did you deliberately enable
> > it via UBIFS debugfs files?
>
> I enabled this:
> echo 1 > /sys/kernel/debug/ubifs/tst_recovery
Then this is expected behavior. You can run integck with -p, then it
will be aware for the power-cut emulation and will continue running.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-10-17 13:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 1:45 GPMI NAND crashes with UBIFS Marek Vasut
2012-10-11 11:25 ` Artem Bityutskiy
2012-10-11 11:55 ` Marek Vasut
2012-10-17 13:12 ` Artem Bityutskiy [this message]
2012-10-17 13:16 ` Marek Vasut
2012-10-17 13:21 ` Artem Bityutskiy
2012-10-17 18:28 ` Ezequiel Garcia
2012-10-18 7:43 ` 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=1350479529.5769.155.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=b32955@freescale.com \
--cc=fabio.estevam@freescale.com \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@denx.de \
/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