public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Jackson <mpfj-list@mimc.co.uk>
To: dedekind1@gmail.com
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>,
	adrian.hunter@intel.com
Subject: Re: MTD : Kernel oops when remounting ubifs as read/write
Date: Thu, 14 Mar 2013 09:54:02 +0000	[thread overview]
Message-ID: <51419E3A.8030007@mimc.co.uk> (raw)
In-Reply-To: <1363252425.11441.94.camel@sauron.fi.intel.com>

On 14/03/13 09:13, Artem Bityutskiy wrote:
> On Wed, 2013-03-13 at 11:12 +0000, Mark Jackson wrote:
>> Sorry ... this just locks up the unit.
> 
> OK, I've reproduced the issue with 3.9-rc2 in nandsim, see the details
> below. The patch I proposed did not get the error path correctly, but it
> does fix the issue.
> 
> I think what you treat as "lockup" is the fixup process. UBIFS basically
> reads the entire UBI volume and writes it back. And it uses the atomic
> change UBI service, which means it also calculates CRC of everything it
> writes. And this all just takes a lot of time. This has to be done only
> once on the first mount.

Okay ... I've retried, but how long is "a lot of time" ?

I've waited 15 minutes and still nothing.

And I can see that there's no activity on the NAND chip select !?!

I'll put some debug info into the fixup routines to see if I can trace what's going on.

Regards
Mark J.


  reply	other threads:[~2013-03-14  9:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-04 16:42 MTD : Kernel oops when remounting ubifs as read/write Mark Jackson
2013-03-12 11:25 ` Artem Bityutskiy
2013-03-13 11:12   ` Mark Jackson
2013-03-13 11:20     ` Artem Bityutskiy
2013-03-13 11:21       ` Mark Jackson
2013-03-14  9:13     ` Artem Bityutskiy
2013-03-14  9:54       ` Mark Jackson [this message]
2013-03-14 10:30         ` Artem Bityutskiy
2013-03-14 11:15           ` Mark Jackson
2013-03-14 11:23             ` Artem Bityutskiy
2013-03-14 12:02               ` Mark Jackson
2013-03-14 12:18                 ` Artem Bityutskiy
2013-03-14 12:23                   ` Artem Bityutskiy
2013-03-14 13:40                     ` Mark Jackson
2013-03-14 13:55                       ` Mark Jackson
2013-03-15  8:40                       ` Artem Bityutskiy
2013-03-15 11:03                       ` AM335x crc32 oops ? Mark Jackson
2013-03-15  8:42       ` MTD : Kernel oops when remounting ubifs as read/write 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=51419E3A.8030007@mimc.co.uk \
    --to=mpfj-list@mimc.co.uk \
    --cc=adrian.hunter@intel.com \
    --cc=dedekind1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-omap@vger.kernel.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