From: Artem Bityutskiy <dedekind1@gmail.com>
To: Steve B <steve@baconbits.demon.co.uk>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBI/UBFS: ubi_eba_read_leb() reporting unmapped LEB
Date: Mon, 20 Oct 2014 16:35:27 +0300 [thread overview]
Message-ID: <1413812127.7906.282.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1410101444510.2556@ubuntu>
On Fri, 2014-10-10 at 14:45 +0100, Steve B wrote:
> Our test setup has the facility of pulling the power on the unit if a GPIO line
> is toggled, with this we can test sensitive areas of the code, can anyone suggest
> where would be a good place to perform this action.
Did you perform testing with UBI/UBIFS debug messages on? Or the
messages in this e-mail were enable after the corruption happened?
Artem.
next prev parent reply other threads:[~2014-10-20 13:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 13:45 UBI/UBFS: ubi_eba_read_leb() reporting unmapped LEB Steve B
2014-10-20 8:54 ` Steve B
2014-10-20 13:35 ` Artem Bityutskiy [this message]
2014-10-20 13:48 ` Steve B
2014-10-20 14:05 ` Artem Bityutskiy
2014-10-20 14:51 ` Steve B
2014-10-20 15:19 ` Artem Bityutskiy
2014-10-20 15:25 ` Steve B
2014-10-20 15:47 ` Artem Bityutskiy
2014-10-20 16:33 ` Steve B
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=1413812127.7906.282.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=steve@baconbits.demon.co.uk \
/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