linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Danesh Daroui <Danesh.Daroui@ascom.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Failure on MTD sub-page test
Date: Fri, 14 Oct 2016 17:38:39 +0300	[thread overview]
Message-ID: <1476455919.2342.950.camel@gmail.com> (raw)
In-Reply-To: <39BC08CB3FF4C84CB6397533D4FC7909015DE2F7@SEGOTEXCH02.ascom-Resource.ads>

On Fri, 2016-10-14 at 14:13 +0000, Danesh Daroui wrote:
> Hi Artem,
> 
> Thanks for your reply. I can unmount the device and run the tests,
> but then how can we make sure whether the problem is in UBI/UBIFS
> layers or only MTD layer? Anyway, if we update the kernel, then both
> MTD drivers and UBI/UBIFS will be updated, am I right?

You are experiencing some issues with UBIFS, I suppose. Naturally, you
want to fix it.

But the SW you are dealing with is sandwich, and you want to narrow
down the problem to a specific layer, if possible.

The first step we usually recommend to do is to start validating the
low level - MTD. You use MTD tests for that. If they fail, you know
there is something wrong at this layer, and you go and fix that. If
they do not fail, the problem is probably somewhere above MTD.

Artem.

  reply	other threads:[~2016-10-14 14:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-11 11:11 Failure on MTD sub-page test Danesh Daroui
2016-10-14 12:41 ` Artem Bityutskiy
2016-10-14 14:13   ` Danesh Daroui
2016-10-14 14:38     ` Artem Bityutskiy [this message]
2016-10-24 11:58     ` Danesh Daroui

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=1476455919.2342.950.camel@gmail.com \
    --to=dedekind1@gmail.com \
    --cc=Danesh.Daroui@ascom.com \
    --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 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).